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-SOM-M1 boot problem

Other Parts Discussed in Thread: AM1808

Hi,

We are using the AM1808-SOM-M1 module on a custom baseboard that we made, which is similar to the evaluation module. We want to boot from the SPI flash, which is the default boot mode of the module. However, it appears that when the module is connected to our baseboard, something prevents the boot to complete correctly. It freezes when it seems to try to run from the DDR2, but since everything is embedded on the module, we don't know what could be the cause of this issue.

Here's a log from the uart console:

AM1808 initialization passed!
Booting TI User Boot Loader
    UBL Version: 1.65
    UBL Flashtype: SPI
Starting SPI Memory Copy...
Valid magicnum, 0x55424CBB, found at offset 0x00010000.
   DONE
Jumping to entry point at 0xC1080000.
ú[00]

When we use the same module on the evaluation board, it boots correctly!!?!
Any ideas?


Regards,

Yannick

  • Looks like it fails when U-boot starts. Have you rebuilt U-boot with modifications to your custom board? It may be searching for a component that doesn't exist on your board.

    Can you probe the UART bus and see if the baud rate changes once you enter U-boot? Does the chip crash or is it still running on the DDR2 region, if you have an emulator to connect?

    It would be helpful if you made a complete list of differences between your two base boards.

    Jeff

  • I have a similar problem in our custom DDR2 board.
    Then I use emulator and I found u-boot fails at somewhere in func board_init_f
    but when i load the u-boot elf to my board under ccs4 , u-boot start at 0xc1080000 still, but goes well.
    I don't use any gel file when i load u-boot elf because DDR2 is inited by UBL. and I didn't change any dvsdk u-boot code.

  • Yanbin, so you mean you boot the UBL which loads U-boot and then it crashes? And then when you connect, the DDR and clocks are already on without a GEL and you load U-boot through the emulator it works that time?

    How can you tell that it fails in board_init_f? Can you narrow down exactly which line it fails on?

    Jeff

  • Yes, you are right.

    Can you narrow down exactly which line it fails on? No I can't , it fails on different line every time. and then DDR2 memory can't be read any more..

    I add memory test code in my UBL and test passed.

    Today I managed to work around the problem.

    I init pll and ddr2 in ubl source code now, instead of in aisgen setting. May be DDR2 setting changed? I recaculated these values.

    I will check DDR2 settings again later.

  • Yes it sounds like it is the wrong DDR settings in the AISgen tool.

    Jeff