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.

TMDS64EVM: Time to start CA53 application

Part Number: TMDS64EVM

Hello TI support team.


I am developing a CA53 application with TMDS64EVM.
The hs_fs file for the CA53 application I created has a size of 27.6 MB.
I am using SBL OSPI to start the CA53 application from ROM.
However, it takes about 40 seconds from when the EVM is turned on until the CA53 main starts running.
Is it possible to shorten the time it takes to start up?

Best regards,
Kiyomasa Imaizumi.

  • Hello TI support team.

    I will include the debug output of SBL.

    [BOOTLOADER_PROFILE] Boot Media       : NOR SPI FLASH
    [BOOTLOADER_PROFILE] Boot Media Clock : 166.667 MHz
    [BOOTLOADER_PROFILE] Boot Image Size  : 28302 KB
    [BOOTLOADER_PROFILE] Cores present    :
    a530-0
    a530-1
    [BOOTLOADER PROFILE] SYSFW init                       :      12185us
    [BOOTLOADER PROFILE] System_init                      :     352158us
    [BOOTLOADER PROFILE] Drivers_open                     :        308us
    [BOOTLOADER PROFILE] Board_driversOpen                :      23032us
    [BOOTLOADER PROFILE] Sciclient Get Version            :       9929us
    [BOOTLOADER PROFILE] CPU Load                         :    4110090us
    [BOOTLOADER_PROFILE] SBL Total Time Taken             :    4507708us
    
    Image loading done, switching to application ...
    

    Best regards,

    Kiyomasa Imaizumi.

  • Hello Kiyomasa,

    However, it takes about 40 seconds from when the EVM is turned on until the CA53 main starts runnin

    I believe you mean it takes about 4 seconds as indicated in the shared logs. Please correct me if I am wrong.

    [BOOTLOADER_PROFILE] SBL Total Time Taken             :    4507708us

    Apart from this, may I know what MCU+ SDK version you are using & at what address your hello world appimage is flashed.

    Regards,

    Prashant

  • Approximately 40 seconds after "DMSC ABI revision 3.1" is displayed, "[BOOTLOADER_PROFILE] Boot Media : NOR SPI FLASH" will be displayed.

    DMSC Firmware Version 9.0.7--v09.00.07 (Kool Koala)
    DMSC Firmware revision 0x9
    DMSC ABI revision 3.1
    
     (Approximately 40 seconds required here.)
     
    [BOOTLOADER_PROFILE] Boot Media       : NOR SPI FLASH
    [BOOTLOADER_PROFILE] Boot Media Clock : 166.667 MHz
    [BOOTLOADER_PROFILE] Boot Image Size  : 28302 KB
    [BOOTLOADER_PROFILE] Cores present    :
    a530-0
    a530-1
    [BOOTLOADER PROFILE] SYSFW init                       :      12185us
    [BOOTLOADER PROFILE] System_init                      :     352158us
    [BOOTLOADER PROFILE] Drivers_open                     :        309us
    [BOOTLOADER PROFILE] Board_driversOpen                :      23107us
    [BOOTLOADER PROFILE] Sciclient Get Version            :       9924us
    [BOOTLOADER PROFILE] CPU Load                         :    4110674us
    [BOOTLOADER_PROFILE] SBL Total Time Taken             :    4508363us

    That's 40 seconds, not 4 seconds

    The address where the application is being flashed is 0x80000.

    Best regards,

    Kiyomasa Imaizumi.

  • Hello Kiyomasa,

    Thank you for the clarification.

    I note from the logs that you are using MCU+ SDK v09_00_00_35. I just tried booting the A53 Hello World application of size ~28MB using SBL OSPI and actually do see that it is taking around ~40 seconds as shown in the logs:

    [2024-03-04 13:21:33.103] DMSC Firmware Version 9.0.7--v09.00.07 (Kool Koala)
    [2024-03-04 13:21:33.108] DMSC Firmware revision 0x9
    [2024-03-04 13:21:33.110] DMSC ABI revision 3.1
    [2024-03-04 13:21:33.112] 
    [2024-03-04 13:22:15.396] [BOOTLOADER_PROFILE] Boot Media       : NOR SPI FLASH 
    [2024-03-04 13:22:15.402] [BOOTLOADER_PROFILE] Boot Media Clock : 166.667 MHz 
    [2024-03-04 13:22:15.406] [BOOTLOADER_PROFILE] Boot Image Size  : 28727 KB 
    [2024-03-04 13:22:15.412] [BOOTLOADER_PROFILE] Cores present    : 
    [2024-03-04 13:22:15.415] a530-0
    [2024-03-04 13:22:15.416] [BOOTLOADER PROFILE] SYSFW init                       :      12154us 
    [2024-03-04 13:22:15.422] [BOOTLOADER PROFILE] System_init                      :     349718us 
    [2024-03-04 13:22:15.428] [BOOTLOADER PROFILE] Drivers_open                     :        310us 
    [2024-03-04 13:22:15.435] [BOOTLOADER PROFILE] Board_driversOpen                :      22774us 
    [2024-03-04 13:22:15.442] [BOOTLOADER PROFILE] Sciclient Get Version            :       9921us 
    [2024-03-04 13:22:15.450] [BOOTLOADER PROFILE] CPU Load                         :    4703892us 
    [2024-03-04 13:22:15.455] [BOOTLOADER_PROFILE] SBL Total Time Taken             :    5098774us 
    [2024-03-04 13:22:15.461] 
    [2024-03-04 13:22:15.462] Image loading done, switching to application ...
    [2024-03-04 13:22:15.541] Hello World!

    However, I tried the same procedure with MCU+ SDK v09_01_00_41 and did not see that significant delay of ~40 seconds in booting. It only took ~3 seconds to boot the A53 Hello World application of size ~28MB using SBL OSPI as shown in the logs:

    [2024-03-04 13:29:22.390] DMSC Firmware Version 9.1.6--v09.01.06 (Kool Koala)
    [2024-03-04 13:29:22.394] DMSC Firmware revision 0x9
    [2024-03-04 13:29:22.397] DMSC ABI revision 3.1
    [2024-03-04 13:29:22.398] 
    [2024-03-04 13:29:24.387] [BOOTLOADER_PROFILE] Boot Media       : NOR SPI FLASH 
    [2024-03-04 13:29:24.392] [BOOTLOADER_PROFILE] Boot Media Clock : 166.667 MHz 
    [2024-03-04 13:29:24.399] [BOOTLOADER_PROFILE] Boot Image Size  : 28799 KB 
    [2024-03-04 13:29:24.402] [BOOTLOADER_PROFILE] Cores present    : 
    [2024-03-04 13:29:24.406] a530-0
    [2024-03-04 13:29:24.407] [BOOTLOADER PROFILE] SYSFW init                       :      12139us 
    [2024-03-04 13:29:24.413] [BOOTLOADER PROFILE] System_init                      :     349639us 
    [2024-03-04 13:29:24.419] [BOOTLOADER PROFILE] Drivers_open                     :        313us 
    [2024-03-04 13:29:24.427] [BOOTLOADER PROFILE] Board_driversOpen                :      22879us 
    [2024-03-04 13:29:24.435] [BOOTLOADER PROFILE] Sciclient Get Version            :      10029us 
    [2024-03-04 13:29:24.439] [BOOTLOADER PROFILE] CPU Load                         :    1988287us 
    [2024-03-04 13:29:24.446] [BOOTLOADER_PROFILE] SBL Total Time Taken             :    2383292us 
    [2024-03-04 13:29:24.453] 
    [2024-03-04 13:29:24.453] Image loading done, switching to application ...
    [2024-03-04 13:29:24.532] Hello World!

    So, can you also try the MCU+ SDK v09_01_00_41 and see if there is still significant delay in booting?

    Regards,

    Prashant

  • Hello Prashant Shivhare.

    Thank you for your reply.

    I tried MCU+ SDK v09_01_00_41.
    I wrote the sbl_ospi.release.hs_fs.tiimage located in the sbl_prebuilt folder to the EVM.
    Then it started up faster.
    Thank you very much.
    What was the cause?

    And your debug output is showing the timestamp.
    Please tell me how to do that too.

    Best regards,
    Kiyomasa Imaizumi.

  • Hello Kiyomasa,

    What was the cause?

    The root cause is the slower authentication algorithm in SysFw v9.0. In SysFw v9.1, which is used by MCU+ SDK v09_01_00_41, there is a improvement in authentication algorithm which significantly improves the authentication time.

    Please tell me how to do that too.

    I enabled the timestamps in Teraterm on Windows. If you are using Teraterm on Windows, you can start logging to a file with timestamps using "File -> Log" and then selecting at least the "Time stamp, Plain text" options as shown

    Once you click Save, the logging starts. The logs with timestamps will be saved in the chosen log file and can be seen with any text editor.

    Regards,

    Prashant