• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 97 subscribers
  • Views 346 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.

AM3351: NAND boot issue

Lawrence Wong
Genius 15760 points
Part Number: AM3351

Customer currently in production is trying to qualify device from a different NAND supplier MX30LF2G18AC.  Current Bootmode worked for older device 00100.  However new device does not work, Boot ROM is attempting XIP boot.  If Bootmode switched to 10011 then AM3351 can boot from the MX30.  However if the NAND is corrupted then there is no way to reprogram the system from SD Card.  Other bootmode takes longer to boot up from.

Anyway to fix/workaround this with Bootmode 00100?

  • 0
    TI__Guru* 85990 points
    Hi Lawrence,
    I'm not sure i have a good workaround for you, but I can probably give you the reason why it is getting stuck in XIP boot. The boot order for 00100 is UART0, XIP w/ WAIT, MMC0, NAND. For XIP boot, the ROM has a fairly simplistic failure mechanism to detect a valid XIP image. It reads the first location from XIP memory at 0x08000000, and if it is something other than 0x00000000 or 0xFFFFFFFF, the ROM thinks a valid image is present and attempts to boot from XIP memory. Because it believes it is a valid image, it will not attempt to boot from other sources in the boot order.

    For some reason, the MX30 device is affecting one or more of the data signals on the GPMC bus during this initial read by the ROM. Has anything else changed on the board other than swapping the NAND devices?

    REgards,
    James