• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 101 subscribers
  • Views 949 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

AM1808 Booting from nand

veranith LY
Prodigy 40 points
Other Parts Discussed in Thread: AM1808, OMAP-L138

Hi,

I am working on an AM1808 based custom board we designed (inspired from Hawkboard + AM1808 evm from LogicPD).

We have a nand memory : MT29F8G08ADBDAH4 which seems to be working :

We are able to boot from UART (using AISGen + OMAP-L138 UART Boot Host utility) and launch u-boot

In here, we are successfully able to play with the nand memory (nand erase/write/read works and data is still there after a hard reset).

We have been generating a u-boot AIS-signed for NAND boot and trying to write it to block 1 of nand, but after reset (and the correct boot mode selected), we were unable to see u-boot console.

--> in u-boot :

tftp C0700000 u-boot_nand.ais (u-boot_nand.ais is 190KB)

nand erase 20000 40000

nand write C0700000 20000 40000

...then power cycle the board in nand boot mode...

We did  that exact same procedure, with the exact same u-boot file on our hawkboard which booted correctly (we have the same DDR2 as in the Hawkboard.

We have also done the exact same procedure on our AM1808 EVM with the same u-boot (but AIS signed for the EVM, which have an mDDR...), it booted successfully from nand.

We have also been trying the Serial boot and flash loading utility for OMAP-L138 (http://processors.wiki.ti.com/index.php/Serial_Boot_and_Flash_Loading_Utility_for_OMAP-L138), which works perfectly with our EVM (still with the same signed u-boot file)

We have been able to customize it (the SFH utility) and recompile for our board (wa have a DDR2 memory). with this, it worked well with the Hawkboard but not with ours : the utility fails to write our nand memory.

Could anyone enlighten us ? Is there something we missed ? 

Thanks in advance.

Veranith

  • 0
    TI__Mastermind 27585 points

    Hi Veranth,

    Can you first see if the NAND boot succeeded or not? Use the debug gel file in CCS after booting to see the ROM status. Does it show any errors, or does it show that it finished and you see the PC in the 0xCxxxxxxx DDR memory region?

    If you see an error, can you show it here? If not, it may be another issue.

    For the serial flasher, use the "-v" option and see if it gives any other information.

    Thanks,

    Jeff

  • 0 in reply to jc-ti
    Prodigy 40 points

    Hi Jeff,

    Thanks for your reply.

    Unfortunately, we don't have CCS  and cannot use its debugging tools (we need a JTAG for that, right ?) .

    It was quite difficult to investigate at this level without these tools, but we finally managed to find out the cause of the problem, which was hardware.

    the CS of our NAND was wired to CS0 of AM1808 in our prototype. The trace being routed in layer 4 (out of 8)  we just forced it to GND (in parallel) (in this condition, we were able to play with the nand in u-boot and linux), which was not enough (and not quite healthy for the CS0 output). After being able to cut the trace and reroute the nand's CS to CS3 manually, everything worked correctly.

    Thanks,

    Veranith