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 16 Jun 2006 06:03 AM by  burelllil
M5485CFE: LoLo issues on watchdog reboot?
 1 Replies
Sort:
You are not authorized to post a reply.
Author Messages
burelllil
New Member
New Member
Posts:


--
16 Jun 2006 05:10 AM
    Hello,
    I am trying to debug an issue I get when the 5485 reboots due to the watchdog expiring. [I know this should never happen, but that's another matter...).

    We are using the latest Logic LinuxBSP and LoLo 2.0.6. The problem is that sometimes the uC reboots but hangs before entering (or inside) LoLo, as no messages are output by the serial port (I have a boot script in the E2PROM starting with VOLO so that normally I see what's going on). Notes:

    - I'm sure the micro reboots, because output pins do not force the logic levels anymore (they get back to input). I will shortly test the RSTOUT pin to be certain.

    - The problem occurs much more often (almost everytime) the flash devices are mounted R/W when rebooting. It has, however, happened also when the flash chips are mounted R/O.

    - We are not using PCI, USB or video output.

    What I suspect is that since in the board the RSTOUT pin is not tied to anything, the flash chips (or some other device onboard) may be in an unknown, not-clean state when LoLo boots.
    Has anybody had this problem before, or has any clue on the subject? Is it possible to have a debug version of LoLo that is more verbose so I can pinpoint the problem source?

    Thanks a lot!
    Luca
    burelllil
    New Member
    New Member
    Posts:


    --
    16 Jun 2006 06:03 AM
    Addenda:
    - We have identified a RSTOUT via on the CFE board (when the reset button is pressed, it stays low for as long as RSTIN is low + 2ms).
    - This pin is however NOT brought down by the watchdog reset of the 5485. So is there no way to find out when the uC is reset, other than with, say, a pull-down always forced to one by software? Seems like a huge mistake from Freescale to me.

    (However the original LoLo questions still hold).
    Thanks again,
    Luca
    You are not authorized to post a reply.