• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 97 subscribers
  • Views 257 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.

DM365 Alternate Booting Methods

MRI
Expert 1130 points

I set the env variables to do a tftp boot with a nand filesystem. When I booted I got a bunch of 'Too many NAND ECC errors' messages. I'm reluctant to try the boot from FLASH method since I clobbered the board and we had to restore the FLASH using a JTAG/Code composer setup. Can someone confirm that the boot methods described in the wiki work? I know the tftp boot with an nfs filesystem works fine.

  • 0
    TI__Mastermind 41665 points

    The booting from NAND flash entirely with both kernel and file system as described here does work, this is how the boards are configured when they are shipped from production. However this will only work if your NAND flash has the proper components burned into it, namely a compatible UBL, U-Boot, uImage (kernel), and filesystem, if you have an early adopter board than these components may not have been in place at the time your board shipped so you may have to restore them as described on that same wiki page if you want to boot entirely from flash. The commands must be handled carefully though, since you are actually erasing portions of the flash, if you accidentally overwrote your UBL and/or U-Boot images you would need to use JTAG/CCS to recover. Personally I have not gone through the restore sequence yet, as I really only use TFTP/NFS since I am always in a sort of 'development' state, however the instructions there were tested by the developers.