• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 99 subscribers
  • Views 432 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.

CCS/TDA2EG-17: Startup sequence

mmyan
Intellectual 705 points

Part Number: TDA2EG-17

Tool/software: Code Composer Studio

Hi ti expert,

During development, I encountered a problem about the boot sequence of the device, and I was moved and confused.

Use the board of our own device to configure the startup into a small mode:

When configuring the hardware, use the configuration in the red box above.

Check the chip RTM, romboot from the external memory, the order of searching for MLO is as indicated by the red box in the figure above.

However, in the actual test, it is found that when there is no MLO in the qspi flash, the system is stuck, and it will not find the boot image from the SD card.

At this time, there is already a normal startup MLO image in the fat partition of the SD card. Why doesn't it automatically load the startup image from the SD card?

Thanks!

  • 0
    TI__Guru**** 169400 points

    Hi,

    I will check with our RoM code experts and get back to you early next week.

    Thanks,
    Keerthy

  • 0 in reply to Keerthy J
    Intellectual 705 points

    Thank you!

    There is another question to ask. I divided two partitions to store the MLO image. The first is 0x0-0x40000, and the second is 0x40000-0x80000.

    After the content of the first area is damaged, romboot can start from the second. Partition to load MLO, but in fact, when I erase the first partition,

    romboot can't start.

    Remember that I used other ti serial chips before, romboot has this function, does tda2x system romboot have this function? How can I use it?

  • 0 in reply to mmyan
    Intellectual 705 points

    Hi ti expert,

    My question has not been answered exactly, can I still get the correct answer?

  • 0 in reply to mmyan
    TI__Guru**** 169400 points

    Hi,

    The suggestion from our RoM expert is to make sure all redundant boot offsets that ROM attempts should be 0x0 or 0xFF for ROM to skip QSPI flash.

    Best Regards,
    Keerthy

  • 0 in reply to Keerthy J
    Intellectual 705 points

    Hi,

    My first question, what is the reason? Cannot skip to the next boot device after qspi fails to boot

    Thanks！

  • 0 in reply to mmyan
    TI__Guru**** 169400 points

    Hi,

    The reason being RoM code checks for all the redundant boot offsets.
    File: "arch/arm/boot/dts/dra7-evm-common.dtsi"

    /* MTD partition table.
    * The ROM checks the first four physical blocks
    * for a valid file to boot and the flash here is
    * 64KiB block size.
    */
    partition@0 {
    label = "QSPI.SPL";
    reg = <0x00000000 0x000010000>;
    };
    partition@1 {
    label = "QSPI.SPL.backup1";
    reg = <0x00010000 0x00010000>;
    };
    partition@2 {
    label = "QSPI.SPL.backup2";
    reg = <0x00020000 0x00010000>;
    };
    partition@3 {
    label = "QSPI.SPL.backup3";
    reg = <0x00030000 0x00010000>;

    Hope i am clear now.

    Best Regards,
    Keerthy