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.

CCS/AM3352: boot up problem with SYSBOOT=11001

Part Number: AM3352
Other Parts Discussed in Thread: TPS65217

Tool/software: Code Composer Studio

Hi experts,

I have three different type of boards using AM3352, and the SYSBOOT[4:0] setting is 11001 for all of them, which is SPI0, MMC0, EMAC1, UART0, and uboot will boot from SPI flash.

This setting worked well with the previous two products, I mean when AM3352 is power-up, the uboot will be up.

But for the latest one, I have to wait for about 4.5 minutes before uboot is up after power-on.

Can you tell me why I got this 4.5 minutes delay? It should boot from SPI flash firstly, but it seems like AM3352 boot from Ethernet firstly.

I did a search in website, in page28 of sprz360i, I copied it below, does it mean if there is Ethernet in boot sequence, then I have to wait for 4.5 minutes?

///////////////////////////////////////////

Advisory 1.0.25 Boot: System Boot Temporarily Stalls if an Attempt to Boot from Ethernet is Not Successful
Revisions Affected 2.1, 2.0, 1.0
Details The system is delayed for up to 4.5 minutes before continuing to the next boot device if an attempt to boot from Ethernet fails for any reason.

//////////////////////////////////////////

Thanks

Chris

  • By the way, I'm 100% sure of that the SYSBOOT setting is correct, as i can read from CONTROL register in CCS, which is 11001, same as my hardware setting.
  • Hi,

    Obviously your board skips SPI boot at the first attempt. I suggest that you check with an oscilloscope the SPI signals at initial boot attempt. It may be that the SPI flash is not ready at that time. In this case the ROM code will skip to the next devices in the boot list. You could also check by trying to boot from an SD card, if you have a card holder on MMC0.
  • Hi Biser,

    Thanks for quick response. I didn't have SD card on board, I'll check the SPI flash carefully and come back to you.

    Regards
    Chris
  • Hi Biser,

    Thanks for your valuable input, you helped me out one more time, I really appreciated that.

    In my board, I'm using TPS65217, while the 3.3V generated by it might not be able to provide enough current, so I used a separated IC to power SPI flash, when AM3352 wanted to boot from SPI flash for the first time, the power of SPI flash was not ready, that's the root cause.

    I still get another three simple questions about the AM3352, can you give me some comments?

    1) AM3352 will boot after receiving a valid PWRONRSTn, is that right?
    As I found that, even the 3.3V to power my SPI flash is will be ready about 15ms later than PWRONRSTn, but AM3352 can still boot up from SPI flash.

    2) After power-up, AM3352 will keep trying to boot from the device defined by SYSBOOT pins, I mean if the first round failed, then the second round, etc.

    3) what is the meaning of "CCCC" in terminal console before boot up?

    Thanks
    Chris
  • 1. Yes, the ROM bootloader starts execution right after PWRONRSTn release.
    2. The ROM bootloader tries to boot from all devices selected with the SYSBOOT configuration. If all devices fail the watchdog timer will issue a warm reset and the boot sequence will be executed again, and so on...
    3. The "CCCC..." sequence is issued by the ROM code over UART0 only when UART boot is tried.
  • Thanks a lot, it's really helpful.

    Regards
    Chris