• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 734 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM3517 fails to boot: hangs at "Starting OS Bootloader..."

Michael Kagalenko
Prodigy 180 points
Other Parts Discussed in Thread: AM3517

Hello,

while trying to reflash NAND on  AM3517 board (SP-860 from Adlink), I, it seems, accidentally erased u-boot and now boot process stops before getting to the u-boot prompt

Texas Instruments X-Loader 1.45 (Feb  7 2012 - 17:12:02)
System Boot: 0c!
mfr:ad
id:da
Starting OS Bootloader...
(stops here)

The board is connected to Linux host via USB-serial adapter, DIP switches are set to the manufacturer's default boot sequence "EMAC -> USB -> MMC1 -> NAND"

There's MMC card inserted into the board, with proper images in place (used to boot from it with no problem)

I would greatly appreciate any tips on restoring the system

Thanks,

Michael

  • 0
    TI__Expert 5960 points

    Hi Michael,

    Whether or not NAND is corrupted, you should be able to boot from MMC. If I mess up NAND, I would use an SD card to get into u-boot to and re-flash NAND.

    Have you tried to rebuild the SD card?

    What boot args are you using?

  • 0 in reply to Jeff L
    Prodigy 180 points

    Hi, Jeff

    > Whether or not NAND is corrupted, you should be able to boot from MMC. If I mess up NAND, I would use an SD card to get into u-boot to and re-flash NAND.

    That's what I would think too. The thing is, with default DIP settings the boot stops at  "Starting OS Bootloader...". Now, Adlink tech

    support sent me DIP settings to boot from SD card only, which is "Off, On, Off, Off, On, On".  With those settings, I can boot from SD

    card and do the steps specified by Adlink to reflash the NAND. However, when I return DIP switches to manufacturer's default,

    the boot stops at exact same place. But there's difference, too - now boot begins both with and without SD card. So I know that I *did*

    flash something at least partially correct to NAND. Note also, that MMC card is before NAND in default boot sequence. So, I don't understand

    what is going on. It seems like there's some non-volatile settings associated with boot from eMAC or USB, and those did get corrupted.

    Unfortunately, Adlink does not povide board schematics.

  • 0 in reply to Michael Kagalenko
    TI__Expert 5960 points

    Hi Michael,

    If it is the NAND that is causing you issues, you can erase the entire NAND and see if that is what is causing the issue:

    From u-boot:

    nand erase.chip

    For your failed boot mode, I'm not 100% clear what are the sysboot setting. Could you read back the control_status register? it is at address 0x44E10040.

    Below is what I read back for factory settings.

    U-Boot# md.l 0x44E10040 1
    44e10040: 00400301 ..@.

  • 0 in reply to Jeff L
    Prodigy 180 points

    The problem was not getting u-boot prompt at all - boot stopped before that

    Eventually, Adlink support sent me an image of boot SD card, which fixed the issue. I am still not entirely sure what was going on. Perhaps,

    the SD card was not entirely correct