Search

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 26 Oct 2010 03:31 AM by  uku
Board begins to power cycle
 7 Replies
Sort:
You are not authorized to post a reply.
Author Messages

aaron.oreilly



New Member


Posts:
New Member


--
16 Nov 2009 08:46 AM
    At the end of our first day of using the new board, it has started to power cycle itself after just a few seconds from being powered up. Left it over the weekend and Monday, could power it up for ~40 seconds. Sounds like the battery may not be charging(?)

    Any advise.

    richard.laborde@logicpd.com



    Basic Member


    Posts:247
    Basic Member


    --
    18 Nov 2009 08:12 AM
    Aaron,

    Do you have the SD card plugged in? If so, unplug it and send the LoLo boot terminal log to Ask A Question. The Torpedo is capable of booting from a dead battery and charging the battery, but LoLo has to boot to do it. (the PMIC needs to be set up for charging) If the screen is initialized (like in the Autoboot CE script) then it will draw too much power before the charging circuit can kick in.

    Thanks

    aaron.oreilly



    New Member


    Posts:
    New Member


    --
    18 Nov 2009 08:23 AM
    There was no SD card inserted, the LOLO could barely come up before the power cycle. We inspected the board and noticed that some of the resistors in the charging cct were not fully soldered down, thus the dead battery.

    Thanks for the help.

    glennj@logicpd.com



    New Member


    Posts:
    New Member


    --
    09 Apr 2010 02:33 PM
    The re-booting OMAP35x Torpedo kit happens when the battery is not
    connected or has too low a charge. This causes a timeout to reboot
    the system. There is a charging circuit that may not be enabled. The
    following procedures should enable the circuit:

    These steps are performed with the LCD removed.
    1) Remove the battery
    2) Bring up LoLo
    3) Plug in the battery

    also:
    4) Enter the "losh> ifconfig SM0 DHCP" command.
    5) Bring up WinCE (if using WinCE)

    Steps 4 and 5 will increase the charging rate to the battery.
    After the board has run a while to permit the battery to hold a charge,
    turn off the kit, leave the battery connected, add the LCD back (if
    needed) and re-power the OMAP35x Torpedo kit.

    -- Basic effective recharge time for a low battery is c.3 hours. Overnight should also fully recharge the battery.

    Anonymous





    Posts:


    --
    21 May 2010 10:05 AM
    I am experiencing significant issues with battery charging. I am working with the linux demo image and will be working with a linux platform. I tried to follow your directions. With power to the kit off I removed the display, unplugged the battery and then turned power on to bring up LoLo, however LoLo never came up and no LED indicators came on.

    Am I missing something?

    We have created a work around to externally charge the battery. I have also noticed that I can also install the SD card with the WinCE demo and charging will occur however everything I had copied to non-volatile memory is gone when I go back to my linux environment. Batteries charge fine externally.

    uku



    New Member


    Posts:
    New Member


    --
    25 Oct 2010 10:10 AM
    I'm having problems with booting the system as well. I have connected the 5V-Power-Supply and set Jumper JP1 to 1-2 (PWR), the SD-Card and the Display have been removed. If I power the system on with no battery pack attached, nothing happens, no LED's light up, no messages are sent via the serial connection. If I connect the battery pack, the system seems to reboot permanently and it gets stuck during the pre-boot procedure (NoLo):

    NoLo Version : 2.4.9-OMAP3503 0001
    NoLo Build : LPD386 Fri Sep 4 13:21:20 CDT 2009
    NoLo Compiler: gcc version 4.2.1

    After the last line, it starts all over again.
    Anything I can do about that?

    Greetings, Uli

    richard.laborde@logicpd.com



    Basic Member


    Posts:247
    Basic Member


    --
    25 Oct 2010 01:11 PM
    LoLo 2.4.9 did not have a high enough charge setting to be able to recover from a fully drained battery.

    If you can get the kit to boot, you should immediately update the LoLo to a newer version.
    One thing that I have heard customers being able to do is to boot with the Sys Boot 5 button held down.
    This should force the kit to boot from SD or NAND (before uart, serial, USB etc.) and should allow enough time to get charging set up.

    Some versions of the Kit have different capabilities of booting without the battery plugged in. You can try to boot without the battery, if it goes, then you can follow the update suggestions in the LoLo release notes. Generally speaking, booting from SD with the same LoLo version you will be updating to is the best method.

    If you have registered your kit you can always submit questions like this to the Ask A Question system for additional assistance.

    uku



    New Member


    Posts:
    New Member


    --
    26 Oct 2010 03:31 AM
    Hi,

    thanks for the help, this worked fine. After a nights rest, the system booted once more and I was able to update to the newest Nolo/Lolo Version 2.4.13P1. Now after booting, I cannot see the Nolo-Boot messages anymore, only the Lolo messages are visible at the terminal. Is that normal behaviour? (Same thing happened, when I booted 2.4.13P1 from SD)
    The boot procedure seems to be successful anyway, the "losh>"-prompt appears and I can type commands.

    Regards, Uli
    You are not authorized to post a reply.