• State
  • Replies 37 replies
  • Subscribers 98 subscribers
  • Views 336 views
  • Users 0 members are here
Support feedback
Options
Options
Related

TMDS64EVM: Regarding user application startup when part of the user application (hs_fs) in flash is erased.

Kiyomasa Imaizumi
Intellectual 760 points
Part Number: TMDS64EVM
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

Hello TI support team.

If a portion of the flash area of the user application (hs_fs) is intentionally overwritten, will the SBL OSPI reject the user application?

Normally, CA53 and CR5 user applications can be launched from SBL OSPI.
The hs_fs size of the user application is about 9.6MB.
It is located in the OSPI FLASH area.

I created a program to clear the flash in the user application program.
As a test, I cleared (Flash_eraseBlk) a portion (128KB) of the flash area where the application (HS_FS) is written.
When I restarted, I expected SBL not to start the application.
I expected SBL to output "Some tests have failed!!" but it didn't.

However, SBL OSPI's Bootloader_parseMultiCoreAppImage succeeds.
SBL results in a data abort in the following function:
Bootloader_loadCpu(bootHandle, &bootImageInfo.cpuInfo[CSL_CORE_ID_A53SS0_0]);
A Data Abort is not the desired result.

If part of the user application(hs_fs) in flash is rewritten, is it possible for SBL to detect this and generate an error?
The SBL SDK uses mcu_plus_sdk_am64x_09_01_00_41.

Best regards,
Kiyomasa Imaizumi.

  • 0
    TI__Genius 11435 points

    Hi Kiyomasa,

    Could you check if Disable Auth for Application Image options is enabled in your SBL OSPI's sysconfig:

    Best Regards,

    Meet.

  • 0 in reply to Meet Thakar
    Intellectual 760 points

    Hello Meet Thakar

    Thank you for your reply.

    I unchecked the "Disable Auth For Application Image" checkbox and created the SBL OSPI again.

    However, an error occurs in
    Bootloader_verifyMulticoreImage
    Bootloader_socAuthImage(certLoadAddr).


    Upon further investigation,
    in the Sciclient_procBootAuthAndStart function,
    the return value of the Sciclient_service function is 0,
    but because respParam.flags is 0, retVal is SystemP_FAILURE.


    Do I need to configure something on the user application side as well?
    Changing the build options for the user application to authtype=0,1,2 did not improve the situation.

    The problem is still not solved.

    Best regards,
    Kiyomasa Imaizumi.

  • 0 in reply to Kiyomasa Imaizumi
    Intellectual 760 points


    I will add more information.

    This may be related, but I'll answer a question from Prashant Shivhare from a previous post:
    e2e.ti.com/.../5131217

    I checked the memory at 0x60080000 using CCS just before Bootloader_socAuthImage.
    The area around 0x60080000 is 0xFFFFFFFF.


    Best regard,
    Kiyomasa Imaizumi.

  • 0 in reply to Kiyomasa Imaizumi
    Intellectual 760 points

    I also took other people's questions into consideration.

    e2e.ti.com/.../5842977


    e2e.ti.com/.../5350965


    I just did the fix in the patch above but it didn't solve the problem.

    Best regards,
    Kiyomasa Imaizumi.

  • 0 in reply to Kiyomasa Imaizumi
    TI__Genius 11435 points

    Hi Kiyosama,

    I am not sure of what issue you are facing currently, as per my understanding you are trying to boot a corrupted image using SBL OSPI, ans you expected a failure from bootloader, which you were not observing previously due to the fact that "Disable Auth For Application Image" was checked in your case, this option would disable the authentication for appimage image and that is why SBL was not returning with a failure.

    Based upon your response, It seems that you are now observing the authentication failure for the corrupted image after unchecking "Disable Auth For Application Image" parameter, which is the expected result, so, could you elaborate the what is the issue now?

    Best Regards,

    Meet.

  • 0 in reply to Meet Thakar
    Intellectual 760 points

    Hello Meet Thakar.

    Let me explain the current problem.

    Originally, the user application would launch even if the flash area for the user application had been tampered with.
    I wanted to know if there was a way to use SBL OSPI to determine if the user application had been tampered with and prevent the user application from launching.

    So I checked the SBL and found that "Disable Auth For Application Image" was checked.
    I realized that this was why the SBL was not checking for tampering with the user application.

    So I unchecked "Disable Auth For Application Image" and
    wrote a new SBL and user application to the board.
    However, the user application no longer launched, even though it had not been tampered with.

    Currently, the problems I want to solve are as follows:

    - After unchecking Disable Auth For Application Image, the correct user application no longer launched.


    Best regards,
    Kiyomasa Imaizumi.

  • 0 in reply to Kiyomasa Imaizumi
    TI__Genius 11435 points
    Kiyomasa Imaizumi said:
    I checked the memory at 0x60080000 using CCS just before Bootloader_socAuthImage.
    The area around 0x60080000 is 0xFFFFFFFF.

    This is where your appimage is supposed to be, so ideally if you have flashed the image at this address, this shouldn't be possible.

    Have you flashed your application at am offset other than 0x80000, please also share the flashing logs.

  • 0 in reply to Meet Thakar
    Intellectual 760 points

    Hello Meet Thakar.


    How should I take flashing logs?
    The user application is set to be written to 0x100000 by DFU.

    Best regards,

    Kiyomasa Imaizumi

  • 0 in reply to Kiyomasa Imaizumi
    TI__Genius 11435 points

    Please share the contents of memory at address 0x60100000 in that case.

  • 0 in reply to Meet Thakar
    Intellectual 760 points

    This is the content of the memory image.
    Please check.

  • 0 in reply to Kiyomasa Imaizumi
    Intellectual 760 points

    mem_0x60100000.dat

    I've also attached a 128kB dump from 0x60100000.

  • 0 in reply to Kiyomasa Imaizumi
    TI__Genius 11435 points

    Please share your appimage as well, I will try to see If I can reproduce this at my end.

  • 0 in reply to Meet Thakar
    Intellectual 760 points

    I would like to send the binary file separately by email rather than attaching it to e2e.
    Please let me know your email address.
    I am using a custom board and the flash is IS25LX256.

    Best regards,

    Kiyomasa Imaizumi.

  • 0 in reply to Kiyomasa Imaizumi
    TI__Genius 11435 points

    If there is a privacy issue then you can share the image via a direct message to me.

  • 0 in reply to Meet Thakar
    Intellectual 760 points

    Thank you. How can I send you an direct message?

  • 0 in reply to Kiyomasa Imaizumi
    TI__Genius 11435 points

    I can not share my email on public forum, you can share it to me via a private E2E chat.

  • 0 in reply to Meet Thakar
    Intellectual 760 points

    So I'd like to have a private E2E chat.
    I sent the app image to Private Chat.

  • 0 in reply to Kiyomasa Imaizumi
    TI__Genius 11435 points

    Thanks for sharing the image, I see that you have shared an unsigned image ( .appimage file), I was expecting .appimage.hs_fs image as you have mentioned you are using a hs_fs device. Are you trying to boot the same?

    Because in this case it clarifies the issue, as you are trying to boot an unsigned image the authentication will fail as the device is HS-FS and you have now enabled the appimage authentication.

  • 0 in reply to Meet Thakar
    Intellectual 760 points

    I'm actually using an hs_fs image.
    I've attached that as well.

  • 0 in reply to Kiyomasa Imaizumi
    TI__Genius 11435 points

    Hi Kiyomasa,

    I am able to boot the appimage given by you using SBL OSPI, please find the boot logs:

    MSC Firmware Version 9.1.6--v09.01.06 (Kool Koala)                                                      
DMSC Firmware revision 0x9                                                                               
DMSC ABI revision 3.1                                                                                    
                                                                                                         
[BOOTLOADER_PROFILE] Boot Media       : NOR SPI FLASH                                                    
[BOOTLOADER_PROFILE] Boot Media Clock : 166.667 MHz                                                      
[BOOTLOADER_PROFILE] Boot Image Size  : 3979 KB                                                          
[BOOTLOADER_PROFILE] Cores present    :                                                                  
a530-0                                                                                                   
a530-1                                                                                                   
[BOOTLOADER PROFILE] SYSFW init                       :      12170us                                     
[BOOTLOADER PROFILE] System_init                      :        551us                                     
[BOOTLOADER PROFILE] Drivers_open                     :        281us                                     
[BOOTLOADER PROFILE] Board_driversOpen                :      22036us                                     
[BOOTLOADER PROFILE] Sciclient Get Version            :       9895us                                     
[BOOTLOADER PROFILE] CPU Load                         :     300749us                                     
[BOOTLOADER_PROFILE] SBL Total Time Taken             :     345687us                                     
                                                                                                         
Image loading done, switching to application ...

    Are you using the default SBL OSPI or you have made any changes?

  • 0 in reply to Meet Thakar
    Intellectual 760 points

    Hello Meet Thakar.

    In SBL OSPI, the flash and OSPI settings have been changed.
    The SBL startup log looks like this.
    The result will differ depending on whether the Disable Auth For Application Image checkbox is selected.

    ["Disable Auth For Application Image" is ON]
-----
[New]Starting OSPI Bootloader ...

DMSC Firmware Version 9.1.6--v09.01.06 (Kool Koala)
DMSC Firmware revision 0x9
DMSC ABI revision 3.1

[BOOTLOADER_PROFILE] Boot Media       : NOR SPI FLASH
[BOOTLOADER_PROFILE] Boot Media Clock : 133.333 MHz
[BOOTLOADER_PROFILE] Boot Image Size  : 3979 KB
[BOOTLOADER_PROFILE] Cores present    :
a530-0
a530-1
[BOOTLOADER PROFILE] SYSFW init                       :      12178us
[BOOTLOADER PROFILE] System_init                      :     349084us
[BOOTLOADER PROFILE] Drivers_open                     :         86us
[BOOTLOADER PROFILE] Board_driversOpen                :       3751us
[BOOTLOADER PROFILE] Sciclient Get Version            :      10033us
[BOOTLOADER PROFILE] CPU Load                         :    3986747us
[BOOTLOADER_PROFILE] SBL Total Time Taken             :    4361882us

Image loading done, switching to application ...
------



["Disable Auth For Application Image" is OFF]
-----
[New]Starting OSPI Bootloader ...

DMSC Firmware Version 9.1.6--v09.01.06 (Kool Koala)
DMSC Firmware revision 0x9
DMSC ABI revision 3.1

Some tests have failed!!
-----

    I will attach the SBL OSPI project to the private chat.


    Best regards,
    Kiyomasa Imaizumi.

  • 0 in reply to Kiyomasa Imaizumi
    TI__Genius 11435 points

    Hi Kiyomasa,

    I assume you are using a custom board with a custom flash part as you mentioned changing the flash configuration, could you confirm the same? For me the boot was successful even when Disable Auth For Application Image checkbox is unchecked and I tested on TI EVM.

    Best Regards,

    Meet.

  • 0 in reply to Meet Thakar
    Intellectual 760 points

    Hello Meet Thakar

    Does "confirm the same" mean the following?
    Revert the flash settings from custom flash (IS25LX256) to the EVM flash (S28HS512T) and check whether it works correctly on the EVM with or without the "Disable Auth For Application Image" setting.

    Best regards,

    Kiyomasa Imaizumi.

  • 0 in reply to Kiyomasa Imaizumi
    TI__Genius 11435 points

    Hi Kiyomasa,

    Sorry for the confusion, So I tested with default TI EVM board and it works fine for me even with authentication enabled, in your case you are using a custom flash and seems to be facing the issue while authenticating the image, let me try to check what could lead to this authentication failure while using custom flash, you don't need to revert you flash settings.

    Best Regards,

    Meet.

  • 0 in reply to Meet Thakar
    Intellectual 760 points

    Hello Meet Thakar

    Thank you for investigating the custom flash.
    I hope you can resolve this as soon as possible.
    I also tested it and confirmed that it works on EVM.
    On EVM, the user application started regardless of whether SBL flash authentication was enabled or not.

    Best regards,
    Kiyomasa Imaizumi.

  • 0 in reply to Kiyomasa Imaizumi
    Intellectual 760 points

    An additional note regarding SBL OSPI operation on EVM.

    In the SBL OSPI settings, "Disable Auth For Application Image" is unchecked.
    When repeatedly turning the power on and off on an EVM,
    the return value of Bootloader_parseMultiCoreAppImage() may not be SystemP_SUCCESS, and user applications may fail to start.

    When this happens, the message "Some tests have failed" appears.
    It appears that user applications do not reliably start on EVM either.

    Best regards,

    Kiyomasa Imaizumi.

  • 0 in reply to Kiyomasa Imaizumi
    TI__Genius 11435 points

    It seems be working for me at my end.

    Kiyomasa Imaizumi said:
    When repeatedly turning the power on and off on an EVM,

    At what time intervals you are doing a power cycle on the EVM, also what is the failure rate for this? Do you only observe it once or is it reproducible?

  • 0 in reply to Meet Thakar
    Intellectual 760 points

    Hello Meet Thakar.


    I've attached a log of the debug output in Teraterm.
    It's turned on and off repeatedly every 1-2 seconds on EVM.
    When Bootloader_parseMultiCoreAppImage is successful, "parse is success" is output,
    and when it fails, "parse is failure!" is output.
    This is reproducible.

    Fullscreen 7848.teraterm.log Download 
    ----------------------------
[2025-09-10 13:48:29.056] [EVM]Starting OSPI Bootloader ... 
[2025-09-10 13:48:29.083] 
[2025-09-10 13:48:29.099] DMSC Firmware Version 9.1.6--v09.01.06 (Kool Koala)
[2025-09-10 13:48:29.099] DMSC Firmware revision 0x9
[2025-09-10 13:48:29.099] DMSC ABI revision 3.1
[2025-09-10 13:48:29.099] 
[2025-09-10 13:48:29.357] parse is success.
[2025-09-10 13:48:29.373] [BOOTLOADER_PROFILE] Boot Media       : NOR SPI FLASH 
[2025-09-10 13:48:29.393] [BOOTLOADER_PROFILE] Boot Media Clock : 166.667 MHz 
[2025-09-10 13:48:29.393] [BOOTLOADER_PROFILE] Boot Image Size  : 3979 KB 
[2025-09-10 13:48:29.393] [BOOTLOADER_PROFILE] Cores present    : 
[2025-09-10 13:48:29.405] a530-0
[2025-09-10 13:48:29.405] a530-1
[2025-09-10 13:48:29.405] [BOOTLOADER PROFILE] SYSFW init                       :      12174us 
[2025-09-10 13:48:29.405] [BOOTLOADER PROFILE] System_init                      :     349495us 
[2025-09-10 13:48:29.426] [BOOTLOADER PROFILE] Drivers_open                     :        321us 
[2025-09-10 13:48:29.426] [BOOTLOADER PROFILE] Board_driversOpen                :      26735us 
[2025-09-10 13:48:29.426] [BOOTLOADER PROFILE] Sciclient Get Version            :      10027us 
[2025-09-10 13:48:29.437] [BOOTLOADER PROFILE] CPU Load                         :     283894us 
[2025-09-10 13:48:29.437] [BOOTLOADER_PROFILE] SBL Total Time Taken             :     682652us 
[2025-09-10 13:48:29.437] 
[2025-09-10 13:48:29.437] Image loading done, switching to application ...
[2025-09-10 13:48:29.437] #BOOTER 0.21 / MAIN --- 2025/09/09 13:43:49 RUN..
[2025-09-10 13:48:29.468] Create Systimer st
----------------------------
[2025-09-10 13:48:30.774] ?
[2025-09-10 13:48:31.236] [EVM]Starting OSPI Bootloader ... 
[2025-09-10 13:48:31.268] 
[2025-09-10 13:48:31.285] DMSC Firmware Version 9.1.6--v09.01.06 (Kool Koala)
[2025-09-10 13:48:31.285] DMSC Firmware revision 0x9
[2025-09-10 13:48:31.285] DMSC ABI revision 3.1
[2025-09-10 13:48:31.285] 
[2025-09-10 13:48:31.540] parse is success.
[2025-09-10 13:48:31.556] [BOOTLOADER_PROFILE] Boot Media       : NOR SPI FLASH 
[2025-09-10 13:48:31.572] [BOOTLOADER_PROFILE] Boot Media Clock : 166.667 MHz 
[2025-09-10 13:48:31.572] [BOOTLOADER_PROFILE] Boot Image Size  : 3979 KB 
[2025-09-10 13:48:31.572] [BOOTLOADER_PROFILE] Cores present    : 
[2025-09-10 13:48:31.593] a530-0
[2025-09-10 13:48:31.593] a530-1
[2025-09-10 13:48:31.593] [BOOTLOADER PROFILE] SYSFW init                       :      12174us 
[2025-09-10 13:48:31.593] [BOOTLOADER PROFILE] System_init                      :     349496us 
[2025-09-10 13:48:31.603] [BOOTLOADER PROFILE] Drivers_open                     :        319us 
[2025-09-10 13:48:31.603] [BOOTLOADER PROFILE] Board_driversOpen                :      26806us 
[2025-09-10 13:48:31.603] [BOOTLOADER PROFILE] Sciclient Get Version            :      10029us 
[2025-09-10 13:48:31.619] [BOOTLOADER PROFILE] CPU Load                         :     284613us 
[2025-09-10 13:48:31.619] [BOOTLOADER_PROFILE] SBL Total Time Taken             :     683443us 
[2025-09-10 13:48:31.631] 
[2025-09-10 13:48:31.631] Image loading done, switching to application ...
[2025-09-10 13:48:31.631] #BOOTER 0.21 / MAIN --- 2025/09/09 13:43:49 RUN..
[2025-09-10 13:48:31.651] Create Systimer st
----------------------------
[2025-09-10 13:48:33.104] ?
[2025-09-10 13:48:33.567] [EVM]Starting OSPI Bootloader ... 
[2025-09-10 13:48:33.583] 
[2025-09-10 13:48:33.583] DMSC Firmware Version 9.1.6--v09.01.06 (Kool Koala)
[2025-09-10 13:48:33.599] DMSC Firmware revision 0x9
[2025-09-10 13:48:33.599] DMSC ABI revision 3.1
[2025-09-10 13:48:33.599] 
[2025-09-10 13:48:33.870] parse is success.
[2025-09-10 13:48:33.885] [BOOTLOADER_PROFILE] Boot Media       : NOR SPI FLASH 
[2025-09-10 13:48:33.885] [BOOTLOADER_PROFILE] Boot Media Clock : 166.667 MHz 
[2025-09-10 13:48:33.901] [BOOTLOADER_PROFILE] Boot Image Size  : 3979 KB 
[2025-09-10 13:48:33.901] [BOOTLOADER_PROFILE] Cores present    : 
[2025-09-10 13:48:33.901] a530-0
[2025-09-10 13:48:33.901] a530-1
[2025-09-10 13:48:33.901] [BOOTLOADER PROFILE] SYSFW init                       :      12174us 
[2025-09-10 13:48:33.925] [BOOTLOADER PROFILE] System_init                      :     349495us 
[2025-09-10 13:48:33.925] [BOOTLOADER PROFILE] Drivers_open                     :        320us 
[2025-09-10 13:48:33.925] [BOOTLOADER PROFILE] Board_driversOpen                :      26739us 
[2025-09-10 13:48:33.937] [BOOTLOADER PROFILE] Sciclient Get Version            :      10032us 
[2025-09-10 13:48:33.937] [BOOTLOADER PROFILE] CPU Load                         :     283885us 
[2025-09-10 13:48:33.949] [BOOTLOADER_PROFILE] SBL Total Time Taken             :     682651us 
[2025-09-10 13:48:33.949] 
[2025-09-10 13:48:33.949] Image loading done, switching to application ...
[2025-09-10 13:48:33.949] #BOOTER 0.21 / MAIN --- 2025/09/09 13:43:49 RUN..
[2025-09-10 13:48:33.965] Create Systimer st
----------------------------
[2025-09-10 13:48:35.425] ?
[2025-09-10 13:48:35.873] [EVM]Starting OSPI Bootloader ... 
[2025-09-10 13:48:35.888] 
[2025-09-10 13:48:35.888] DMSC Firmware Version 9.1.6--v09.01.06 (Kool Koala)
[2025-09-10 13:48:35.904] DMSC Firmware revision 0x9
[2025-09-10 13:48:35.904] DMSC ABI revision 3.1
[2025-09-10 13:48:35.904] 
[2025-09-10 13:48:35.920] parse is failure!
[2025-09-10 13:48:35.920] Some tests have failed!!
----------------------------
[2025-09-10 13:48:38.097] ?
[2025-09-10 13:48:38.548] [EVM]Starting OSPI Bootloader ... 
[2025-09-10 13:48:38.564] 
[2025-09-10 13:48:38.564] DMSC Firmware Version 9.1.6--v09.01.06 (Kool Koala)
[2025-09-10 13:48:38.580] DMSC Firmware revision 0x9
[2025-09-10 13:48:38.580] DMSC ABI revision 3.1
[2025-09-10 13:48:38.580] 
[2025-09-10 13:48:38.595] parse is failure!
[2025-09-10 13:48:38.595] Some tests have failed!!
----------------------------
[2025-09-10 13:48:40.960] ?
[2025-09-10 13:48:41.421] [EVM]Starting OSPI Bootloader ... 
[2025-09-10 13:48:41.427] 
[2025-09-10 13:48:41.456] DMSC Firmware Version 9.1.6--v09.01.06 (Kool Koala)
[2025-09-10 13:48:41.456] DMSC Firmware revision 0x9
[2025-09-10 13:48:41.456] DMSC ABI revision 3.1
[2025-09-10 13:48:41.456] 
[2025-09-10 13:48:41.459] parse is failure!
[2025-09-10 13:48:41.459] Some tests have failed!!
----------------------------
[2025-09-10 13:48:43.923] ?
[2025-09-10 13:48:44.368] [EVM]Starting OSPI Bootloader ... 
[2025-09-10 13:48:44.389] 
[2025-09-10 13:48:44.389] DMSC Firmware Version 9.1.6--v09.01.06 (Kool Koala)
[2025-09-10 13:48:44.389] DMSC Firmware revision 0x9
[2025-09-10 13:48:44.418] DMSC ABI revision 3.1
[2025-09-10 13:48:44.418] 
[2025-09-10 13:48:44.663] parse is success.
[2025-09-10 13:48:44.690] [BOOTLOADER_PROFILE] Boot Media       : NOR SPI FLASH 
[2025-09-10 13:48:44.690] [BOOTLOADER_PROFILE] Boot Media Clock : 166.667 MHz 
[2025-09-10 13:48:44.690] [BOOTLOADER_PROFILE] Boot Image Size  : 3979 KB 
[2025-09-10 13:48:44.706] [BOOTLOADER_PROFILE] Cores present    : 
[2025-09-10 13:48:44.706] a530-0
[2025-09-10 13:48:44.706] a530-1
[2025-09-10 13:48:44.706] [BOOTLOADER PROFILE] SYSFW init                       :      12174us 
[2025-09-10 13:48:44.706] [BOOTLOADER PROFILE] System_init                      :     349496us 
[2025-09-10 13:48:44.724] [BOOTLOADER PROFILE] Drivers_open                     :        319us 
[2025-09-10 13:48:44.724] [BOOTLOADER PROFILE] Board_driversOpen                :      26807us 
[2025-09-10 13:48:44.738] [BOOTLOADER PROFILE] Sciclient Get Version            :      10027us 
[2025-09-10 13:48:44.738] [BOOTLOADER PROFILE] CPU Load                         :     284617us 
[2025-09-10 13:48:44.738] [BOOTLOADER_PROFILE] SBL Total Time Taken             :     683447us 
[2025-09-10 13:48:44.754] 
[2025-09-10 13:48:44.754] Image loading done, switching to application ...
[2025-09-10 13:48:44.754] #BOOTER 0.21 / MAIN --- 2025/09/09 13:43:49 RUN..
[2025-09-10 13:48:44.786] Create Systimer st
----------------------------
[2025-09-10 13:48:46.851] ?
[2025-09-10 13:48:47.315] [EVM]Starting OSPI Bootloader ... 
[2025-09-10 13:48:47.315] 
[2025-09-10 13:48:47.342] DMSC Firmware Version 9.1.6--v09.01.06 (Kool Koala)
[2025-09-10 13:48:47.342] DMSC Firmware revision 0x9
[2025-09-10 13:48:47.342] DMSC ABI revision 3.1
[2025-09-10 13:48:47.342] 
[2025-09-10 13:48:47.345] parse is failure!
[2025-09-10 13:48:47.361] Some tests have failed!!
----------------------------
[2025-09-10 13:48:49.797] ?
[2025-09-10 13:48:50.242] [EVM]Starting OSPI Bootloader ... 
[2025-09-10 13:48:50.257] 
[2025-09-10 13:48:50.257] DMSC Firmware Version 9.1.6--v09.01.06 (Kool Koala)
[2025-09-10 13:48:50.275] DMSC Firmware revision 0x9
[2025-09-10 13:48:50.275] DMSC ABI revision 3.1
[2025-09-10 13:48:50.275] 
[2025-09-10 13:48:50.544] parse is success.
[2025-09-10 13:48:50.560] [BOOTLOADER_PROFILE] Boot Media       : NOR SPI FLASH 
[2025-09-10 13:48:50.560] [BOOTLOADER_PROFILE] Boot Media Clock : 166.667 MHz 
[2025-09-10 13:48:50.560] [BOOTLOADER_PROFILE] Boot Image Size  : 3979 KB 
[2025-09-10 13:48:50.576] [BOOTLOADER_PROFILE] Cores present    : 
[2025-09-10 13:48:50.576] a530-0
[2025-09-10 13:48:50.576] a530-1
[2025-09-10 13:48:50.576] [BOOTLOADER PROFILE] SYSFW init                       :      12174us 
[2025-09-10 13:48:50.576] [BOOTLOADER PROFILE] System_init                      :     349497us 
[2025-09-10 13:48:50.592] [BOOTLOADER PROFILE] Drivers_open                     :        319us 
[2025-09-10 13:48:50.592] [BOOTLOADER PROFILE] Board_driversOpen                :      26878us 
[2025-09-10 13:48:50.608] [BOOTLOADER PROFILE] Sciclient Get Version            :      10037us 
[2025-09-10 13:48:50.608] [BOOTLOADER PROFILE] CPU Load                         :     284539us 
[2025-09-10 13:48:50.608] [BOOTLOADER_PROFILE] SBL Total Time Taken             :     683450us 
[2025-09-10 13:48:50.623] 
[2025-09-10 13:48:50.623] Image loading done, switching to application ...
[2025-09-10 13:48:50.623] #BOOTER 0.21 / MAIN --- 2025/09/09 13:43:49 RUN..
[2025-09-10 13:48:50.651] Create Systimer st
----------------------------
[2025-09-10 13:48:52.723] ?
[2025-09-10 13:48:53.181] [EVM]Starting OSPI Bootloader ... 
[2025-09-10 13:48:53.218] 
[2025-09-10 13:48:53.218] DMSC Firmware Version 9.1.6--v09.01.06 (Kool Koala)
[2025-09-10 13:48:53.218] DMSC Firmware revision 0x9
[2025-09-10 13:48:53.218] DMSC ABI revision 3.1
[2025-09-10 13:48:53.218] 
[2025-09-10 13:48:53.483] parse is success.
[2025-09-10 13:48:53.499] [BOOTLOADER_PROFILE] Boot Media       : NOR SPI FLASH 
[2025-09-10 13:48:53.499] [BOOTLOADER_PROFILE] Boot Media Clock : 166.667 MHz 
[2025-09-10 13:48:53.515] [BOOTLOADER_PROFILE] Boot Image Size  : 3979 KB 
[2025-09-10 13:48:53.515] [BOOTLOADER_PROFILE] Cores present    : 
[2025-09-10 13:48:53.515] a530-0
[2025-09-10 13:48:53.515] a530-1
[2025-09-10 13:48:53.515] [BOOTLOADER PROFILE] SYSFW init                       :      12174us 
[2025-09-10 13:48:53.531] [BOOTLOADER PROFILE] System_init                      :     349497us 
[2025-09-10 13:48:53.531] [BOOTLOADER PROFILE] Drivers_open                     :        318us 
[2025-09-10 13:48:53.531] [BOOTLOADER PROFILE] Board_driversOpen                :      26808us 
[2025-09-10 13:48:53.551] [BOOTLOADER PROFILE] Sciclient Get Version            :      10026us 
[2025-09-10 13:48:53.551] [BOOTLOADER PROFILE] CPU Load                         :     284619us 
[2025-09-10 13:48:53.564] [BOOTLOADER_PROFILE] SBL Total Time Taken             :     683449us 
[2025-09-10 13:48:53.564] 
[2025-09-10 13:48:53.564] Image loading done, switching to application ...
[2025-09-10 13:48:53.564] #BOOTER 0.21 / MAIN --- 2025/09/09 13:43:49 RUN..
[2025-09-10 13:48:53.582] Create Systimer st
----------------------------
[2025-09-10 13:48:55.782] ?
[2025-09-10 13:48:56.220] [EVM]Starting OSPI Bootloader ... 
[2025-09-10 13:48:56.251] 
[2025-09-10 13:48:56.251] DMSC Firmware Version 9.1.6--v09.01.06 (Kool Koala)
[2025-09-10 13:48:56.251] DMSC Firmware revision 0x9
[2025-09-10 13:48:56.267] DMSC ABI revision 3.1
[2025-09-10 13:48:56.267] 
[2025-09-10 13:48:56.524] parse is success.
[2025-09-10 13:48:56.538] [BOOTLOADER_PROFILE] Boot Media       : NOR SPI FLASH 
[2025-09-10 13:48:56.557] [BOOTLOADER_PROFILE] Boot Media Clock : 166.667 MHz 
[2025-09-10 13:48:56.557] [BOOTLOADER_PROFILE] Boot Image Size  : 3979 KB 
[2025-09-10 13:48:56.557] [BOOTLOADER_PROFILE] Cores present    : 
[2025-09-10 13:48:56.582] a530-0
[2025-09-10 13:48:56.582] a530-1
[2025-09-10 13:48:56.582] [BOOTLOADER PROFILE] SYSFW init                       :      12174us 
[2025-09-10 13:48:56.582] [BOOTLOADER PROFILE] System_init                      :     349496us 
[2025-09-10 13:48:56.589] [BOOTLOADER PROFILE] Drivers_open                     :        318us 
[2025-09-10 13:48:56.589] [BOOTLOADER PROFILE] Board_driversOpen                :      26808us 
[2025-09-10 13:48:56.589] [BOOTLOADER PROFILE] Sciclient Get Version            :      10028us 
[2025-09-10 13:48:56.604] [BOOTLOADER PROFILE] CPU Load                         :     284613us 
[2025-09-10 13:48:56.604] [BOOTLOADER_PROFILE] SBL Total Time Taken             :     683444us 
[2025-09-10 13:48:56.619] 
[2025-09-10 13:48:56.619] Image loading done, switching to application ...
[2025-09-10 13:48:56.619] #BOOTER 0.21 / MAIN --- 2025/09/09 13:43:49 RUN..
[2025-09-10 13:48:56.643] Create Systimer st
----------------------------
[2025-09-10 13:48:58.189] ?
[2025-09-10 13:48:58.649] [EVM]Starting OSPI Bootloader ... 
[2025-09-10 13:48:58.689] 
[2025-09-10 13:48:58.689] DMSC Firmware Version 9.1.6--v09.01.06 (Kool Koala)
[2025-09-10 13:48:58.689] DMSC Firmware revision 0x9
[2025-09-10 13:48:58.689] DMSC ABI revision 3.1
[2025-09-10 13:48:58.689] 
[2025-09-10 13:48:58.959] parse is success.
[2025-09-10 13:48:58.967] [BOOTLOADER_PROFILE] Boot Media       : NOR SPI FLASH 
[2025-09-10 13:48:58.967] [BOOTLOADER_PROFILE] Boot Media Clock : 166.667 MHz 
[2025-09-10 13:48:58.983] [BOOTLOADER_PROFILE] Boot Image Size  : 3979 KB 
[2025-09-10 13:48:58.983] [BOOTLOADER_PROFILE] Cores present    : 
[2025-09-10 13:48:58.983] a530-0
[2025-09-10 13:48:58.983] a530-1
[2025-09-10 13:48:58.983] [BOOTLOADER PROFILE] SYSFW init                       :      12174us 
[2025-09-10 13:48:58.998] [BOOTLOADER PROFILE] System_init                      :     349496us 
[2025-09-10 13:48:58.998] [BOOTLOADER PROFILE] Drivers_open                     :        319us 
[2025-09-10 13:48:58.998] [BOOTLOADER PROFILE] Board_driversOpen                :      26808us 
[2025-09-10 13:48:59.023] [BOOTLOADER PROFILE] Sciclient Get Version            :      10028us 
[2025-09-10 13:48:59.023] [BOOTLOADER PROFILE] CPU Load                         :     284613us 
[2025-09-10 13:48:59.030] [BOOTLOADER_PROFILE] SBL Total Time Taken             :     683444us 
[2025-09-10 13:48:59.030] 
[2025-09-10 13:48:59.030] Image loading done, switching to application ...
[2025-09-10 13:48:59.030] #BOOTER 0.21 / MAIN --- 2025/09/09 13:43:49 RUN..
[2025-09-10 13:48:59.050] Create Systimer st
----------------------------
[2025-09-10 13:49:00.788] ?
[2025-09-10 13:49:01.268] [EVM]Starting OSPI Bootloader ... 
[2025-09-10 13:49:01.289] 
[2025-09-10 13:49:01.300] DMSC Firmware Version 9.1.6--v09.01.06 (Kool Koala)
[2025-09-10 13:49:01.300] DMSC Firmware revision 0x9
[2025-09-10 13:49:01.300] DMSC ABI revision 3.1
[2025-09-10 13:49:01.300] 
[2025-09-10 13:49:01.568] parse is success.
[2025-09-10 13:49:01.584] [BOOTLOADER_PROFILE] Boot Media       : NOR SPI FLASH 
[2025-09-10 13:49:01.600] [BOOTLOADER_PROFILE] Boot Media Clock : 166.667 MHz 
[2025-09-10 13:49:01.600] [BOOTLOADER_PROFILE] Boot Image Size  : 3979 KB 
[2025-09-10 13:49:01.600] [BOOTLOADER_PROFILE] Cores present    : 
[2025-09-10 13:49:01.616] a530-0
[2025-09-10 13:49:01.616] a530-1
[2025-09-10 13:49:01.616] [BOOTLOADER PROFILE] SYSFW init                       :      12174us 
[2025-09-10 13:49:01.616] [BOOTLOADER PROFILE] System_init                      :     349497us 
[2025-09-10 13:49:01.633] [BOOTLOADER PROFILE] Drivers_open                     :        319us 
[2025-09-10 13:49:01.633] [BOOTLOADER PROFILE] Board_driversOpen                :      26809us 
[2025-09-10 13:49:01.633] [BOOTLOADER PROFILE] Sciclient Get Version            :      10033us 
[2025-09-10 13:49:01.649] [BOOTLOADER PROFILE] CPU Load                         :     284609us 
[2025-09-10 13:49:01.649] [BOOTLOADER_PROFILE] SBL Total Time Taken             :     683446us 
[2025-09-10 13:49:01.666] 
[2025-09-10 13:49:01.666] Image loading done, switching to application ...
[2025-09-10 13:49:01.666] #BOOTER 0.21 / MAIN --- 2025/09/09 13:43:49 RUN..
[2025-09-10 13:49:01.681] Create Systimer st
----------------------------
[2025-09-10 13:49:03.287] ?
[2025-09-10 13:49:03.735] [EVM]Starting OSPI Bootloader ... 
[2025-09-10 13:49:03.769] 
[2025-09-10 13:49:03.769] DMSC Firmware Version 9.1.6--v09.01.06 (Kool Koala)
[2025-09-10 13:49:03.769] DMSC Firmware revision 0x9
[2025-09-10 13:49:03.782] DMSC ABI revision 3.1
[2025-09-10 13:49:03.782] 
[2025-09-10 13:49:04.037] parse is success.
[2025-09-10 13:49:04.053] [BOOTLOADER_PROFILE] Boot Media       : NOR SPI FLASH 
[2025-09-10 13:49:04.069] [BOOTLOADER_PROFILE] Boot Media Clock : 166.667 MHz 
[2025-09-10 13:49:04.069] [BOOTLOADER_PROFILE] Boot Image Size  : 3979 KB 
[2025-09-10 13:49:04.069] [BOOTLOADER_PROFILE] Cores present    : 
[2025-09-10 13:49:04.085] a530-0
[2025-09-10 13:49:04.085] a530-1
[2025-09-10 13:49:04.085] [BOOTLOADER PROFILE] SYSFW init                       :      12174us 
[2025-09-10 13:49:04.085] [BOOTLOADER PROFILE] System_init                      :     349495us 
[2025-09-10 13:49:04.105] [BOOTLOADER PROFILE] Drivers_open                     :        320us 
[2025-09-10 13:49:04.105] [BOOTLOADER PROFILE] Board_driversOpen                :      26878us 
[2025-09-10 13:49:04.105] [BOOTLOADER PROFILE] Sciclient Get Version            :      10040us 
[2025-09-10 13:49:04.120] [BOOTLOADER PROFILE] CPU Load                         :     284538us 
[2025-09-10 13:49:04.120] [BOOTLOADER_PROFILE] SBL Total Time Taken             :     683451us 
[2025-09-10 13:49:04.135] 
[2025-09-10 13:49:04.135] Image loading done, switching to application ...
[2025-09-10 13:49:04.135] #BOOTER 0.21 / MAIN --- 2025/09/09 13:43:49 RUN..
[2025-09-10 13:49:04.164] Create Systimer st
----------------------------
[2025-09-10 13:49:05.977] ?
[2025-09-10 13:49:06.439] [EVM]Starting OSPI Bootloader ... 
[2025-09-10 13:49:06.468] 
[2025-09-10 13:49:06.468] DMSC Firmware Version 9.1.6--v09.01.06 (Kool Koala)
[2025-09-10 13:49:06.468] DMSC Firmware revision 0x9
[2025-09-10 13:49:06.468] DMSC ABI revision 3.1
[2025-09-10 13:49:06.468] 
[2025-09-10 13:49:06.739] parse is success.
[2025-09-10 13:49:06.739] [BOOTLOADER_PROFILE] Boot Media       : NOR SPI FLASH 
[2025-09-10 13:49:06.755] [BOOTLOADER_PROFILE] Boot Media Clock : 166.667 MHz 
[2025-09-10 13:49:06.755] [BOOTLOADER_PROFILE] Boot Image Size  : 3979 KB 
[2025-09-10 13:49:06.755] [BOOTLOADER_PROFILE] Cores present    : 
[2025-09-10 13:49:06.771] a530-0
[2025-09-10 13:49:06.771] a530-1
[2025-09-10 13:49:06.771] [BOOTLOADER PROFILE] SYSFW init                       :      12174us 
[2025-09-10 13:49:06.771] [BOOTLOADER PROFILE] System_init                      :     349496us 
[2025-09-10 13:49:06.800] [BOOTLOADER PROFILE] Drivers_open                     :        318us 
[2025-09-10 13:49:06.800] [BOOTLOADER PROFILE] Board_driversOpen                :      26809us 
[2025-09-10 13:49:06.800] [BOOTLOADER PROFILE] Sciclient Get Version            :      10026us 
[2025-09-10 13:49:06.817] [BOOTLOADER PROFILE] CPU Load                         :     284617us 
[2025-09-10 13:49:06.817] [BOOTLOADER_PROFILE] SBL Total Time Taken             :     683446us 
[2025-09-10 13:49:06.821] 
[2025-09-10 13:49:06.821] Image loading done, switching to application ...
[2025-09-10 13:49:06.821] #BOOTER 0.21 / MAIN --- 2025/09/09 13:43:49 RUN..
[2025-09-10 13:49:06.836] Create Systimer st
----------------------------
[2025-09-10 13:49:07.951] ?
[2025-09-10 13:49:08.400] [EVM]Starting OSPI Bootloader ... 
[2025-09-10 13:49:08.432] 
[2025-09-10 13:49:08.432] DMSC Firmware Version 9.1.6--v09.01.06 (Kool Koala)
[2025-09-10 13:49:08.432] DMSC Firmware revision 0x9
[2025-09-10 13:49:08.448] DMSC ABI revision 3.1
[2025-09-10 13:49:08.448] 
[2025-09-10 13:49:08.448] parse is failure!
[2025-09-10 13:49:08.464] Some tests have failed!!
----------------------------
[2025-09-10 13:49:10.041] ?
[2025-09-10 13:49:10.486] [EVM]Starting OSPI Bootloader ... 
[2025-09-10 13:49:10.503] 
[2025-09-10 13:49:10.503] DMSC Firmware Version 9.1.6--v09.01.06 (Kool Koala)
[2025-09-10 13:49:10.503] DMSC Firmware revision 0x9
[2025-09-10 13:49:10.503] DMSC ABI revision 3.1
[2025-09-10 13:49:10.503] 
[2025-09-10 13:49:10.776] parse is success.
[2025-09-10 13:49:10.804] [BOOTLOADER_PROFILE] Boot Media       : NOR SPI FLASH 
[2025-09-10 13:49:10.804] [BOOTLOADER_PROFILE] Boot Media Clock : 166.667 MHz 
[2025-09-10 13:49:10.804] [BOOTLOADER_PROFILE] Boot Image Size  : 3979 KB 
[2025-09-10 13:49:10.824] [BOOTLOADER_PROFILE] Cores present    : 
[2025-09-10 13:49:10.824] a530-0
[2025-09-10 13:49:10.824] a530-1
[2025-09-10 13:49:10.824] [BOOTLOADER PROFILE] SYSFW init                       :      12174us 
[2025-09-10 13:49:10.824] [BOOTLOADER PROFILE] System_init                      :     349495us 
[2025-09-10 13:49:10.836] [BOOTLOADER PROFILE] Drivers_open                     :        320us 
[2025-09-10 13:49:10.836] [BOOTLOADER PROFILE] Board_driversOpen                :      26808us 
[2025-09-10 13:49:10.852] [BOOTLOADER PROFILE] Sciclient Get Version            :      10030us 
[2025-09-10 13:49:10.852] [BOOTLOADER PROFILE] CPU Load                         :     284612us 
[2025-09-10 13:49:10.852] [BOOTLOADER_PROFILE] SBL Total Time Taken             :     683446us 
[2025-09-10 13:49:10.868] 
[2025-09-10 13:49:10.868] Image loading done, switching to application ...
[2025-09-10 13:49:10.868] #BOOTER 0.21 / MAIN --- 2025/09/09 13:43:49 RUN..
[2025-09-10 13:49:10.884] Create Systimer st
----------------------------
[2025-09-10 13:49:12.072] ?
[2025-09-10 13:49:12.521] [EVM]Starting OSPI Bootloader ... 
[2025-09-10 13:49:12.553] 
[2025-09-10 13:49:12.553] DMSC Firmware Version 9.1.6--v09.01.06 (Kool Koala)
[2025-09-10 13:49:12.569] DMSC Firmware revision 0x9
[2025-09-10 13:49:12.569] DMSC ABI revision 3.1
[2025-09-10 13:49:12.569] 
[2025-09-10 13:49:12.826] parse is success.
[2025-09-10 13:49:12.858] [BOOTLOADER_PROFILE] Boot Media       : NOR SPI FLASH 
[2025-09-10 13:49:12.858] [BOOTLOADER_PROFILE] Boot Media Clock : 166.667 MHz 
[2025-09-10 13:49:12.858] [BOOTLOADER_PROFILE] Boot Image Size  : 3979 KB 
[2025-09-10 13:49:12.874] [BOOTLOADER_PROFILE] Cores present    : 
[2025-09-10 13:49:12.874] a530-0
[2025-09-10 13:49:12.874] a530-1
[2025-09-10 13:49:12.874] [BOOTLOADER PROFILE] SYSFW init                       :      12174us 
[2025-09-10 13:49:12.874] [BOOTLOADER PROFILE] System_init                      :     349497us 
[2025-09-10 13:49:12.890] [BOOTLOADER PROFILE] Drivers_open                     :        319us 
[2025-09-10 13:49:12.890] [BOOTLOADER PROFILE] Board_driversOpen                :      26809us 
[2025-09-10 13:49:12.907] [BOOTLOADER PROFILE] Sciclient Get Version            :      10034us 
[2025-09-10 13:49:12.907] [BOOTLOADER PROFILE] CPU Load                         :     284606us 
[2025-09-10 13:49:12.907] [BOOTLOADER_PROFILE] SBL Total Time Taken             :     683444us 
[2025-09-10 13:49:12.923] 
[2025-09-10 13:49:12.923] Image loading done, switching to application ...
[2025-09-10 13:49:12.923] #BOOTER 0.21 / MAIN --- 2025/09/09 13:43:49 RUN..
[2025-09-10 13:49:12.939] Create Systimer st
----------------------------
[2025-09-10 13:49:14.155] ?
[2025-09-10 13:49:14.604] [EVM]Starting OSPI Bootloader ... 
[2025-09-10 13:49:14.637] 
[2025-09-10 13:49:14.637] DMSC Firmware Version 9.1.6--v09.01.06 (Kool Koala)
[2025-09-10 13:49:14.637] DMSC Firmware revision 0x9
[2025-09-10 13:49:14.637] DMSC ABI revision 3.1
[2025-09-10 13:49:14.637] 
[2025-09-10 13:49:14.907] parse is success.
[2025-09-10 13:49:14.938] [BOOTLOADER_PROFILE] Boot Media       : NOR SPI FLASH 
[2025-09-10 13:49:14.938] [BOOTLOADER_PROFILE] Boot Media Clock : 166.667 MHz 
[2025-09-10 13:49:14.955] [BOOTLOADER_PROFILE] Boot Image Size  : 3979 KB 
[2025-09-10 13:49:14.955] [BOOTLOADER_PROFILE] Cores present    : 
[2025-09-10 13:49:14.955] a530-0
[2025-09-10 13:49:14.955] a530-1
[2025-09-10 13:49:14.955] [BOOTLOADER PROFILE] SYSFW init                       :      12174us 
[2025-09-10 13:49:14.971] [BOOTLOADER PROFILE] System_init                      :     349496us 
[2025-09-10 13:49:14.971] [BOOTLOADER PROFILE] Drivers_open                     :        318us 
[2025-09-10 13:49:14.971] [BOOTLOADER PROFILE] Board_driversOpen                :      26808us 
[2025-09-10 13:49:14.973] [BOOTLOADER PROFILE] Sciclient Get Version            :      10025us 
[2025-09-10 13:49:14.973] [BOOTLOADER PROFILE] CPU Load                         :     284618us 
[2025-09-10 13:49:15.005] [BOOTLOADER_PROFILE] SBL Total Time Taken             :     683446us 
[2025-09-10 13:49:15.005] 
[2025-09-10 13:49:15.005] Image loading done, switching to application ...
[2025-09-10 13:49:15.005] #BOOTER 0.21 / MAIN --- 2025/09/09 13:43:49 RUN..
[2025-09-10 13:49:15.006] Create Systimer st

    Best regards,

    Kiyomasa Imaizumi.

  • 0 in reply to Kiyomasa Imaizumi
    Intellectual 760 points

    Hello Meet Thakar.

    What is the progress on the investigation into custom flash?
    If you find any solution, please let me know as soon as possible.

    Best regards,
    Kiyomasa Imaizumi.

  • 0 in reply to Kiyomasa Imaizumi
    Intellectual 760 points

    Hello Meet Thakar.

    I haven't received a reply for over two weeks. What's the progress?

    Please tell me how to resolve the issue.

    Best regards,

    Kiyomasa Imaizumi.

  • 0 in reply to Kiyomasa Imaizumi
    TI__Genius 11435 points

    Hi,
    Apologies for the delay, Let's focus on the issue you face on your custom board for now. Could you enable the TIFS logs and share those with me? This might provide some insight on the issue, please refer to this on how to enable them: [FAQ] AM64x/AM243 : How to enable SYSFW trace on AM64x/AM243 devices 

    Best Regards,
    Meet.

  • 0 in reply to Meet Thakar
    Intellectual 760 points

    Hello Meet Thakar.

    I captured the output from UART1 when SYSFW TRACE was enabled.
    I've attached the file.

    Fullscreen SYSFW_TRACE_ENABLE.txt Download 
    0xC20101
0xC20024
0x61800101
0x61C0008A
0xC20104
0xC20024
0x61800104
0x61C0008A
0xC20100
0xC20024
0x61800100
0x61C0008A
0x62000000
0xC2010D
0xC20024
0x6180010D
0x61C0008A
0x612D7C83
0xC2010C
0xC20024
0x6180010C
0x61C0008A
0x612D7C83
0x612D7C83
0xC20002
0xC20024
0x4003007
0x4400916
0xC20201
0xC20024
0x61800201
0x61C00051
0xC20200
0xC20024
0x61800200
0x61C00051
0x62000002
0x62C18000
0x64078000
0x6400C004
0x62C18001
0x6080009D
0x6080009F
0x60000051
0x63878000
0x6380C004
0xC20202
0xC20024
0x61800202
0x61C00051
0x62000000
0xC20101
0xC20024
0x61800101
0x61C00051
0xC20104
0xC20024
0x61800104
0x61C00051
0xC20103
0xC20024
0x61800103
0x61C00051
0xC20100
0xC20024
0x61800100
0x61C00051
0x62000000
0x60C0009D
0xC20102
0xC20024
0x61800102
0x61C00051
0x62000001
0xC2010D
0xC20024
0x6180010D
0x61C00051
0x612B7C91
0xC2010C
0xC20024
0x6180010C
0x61C00051
0x612B7C91
0x612B7C91
0xC20201
0xC20024
0x61800201
0x61C00052
0xC20200
0xC20024
0x61800200
0x61C00052
0x62000002
0x62C1C000
0x6407C000
0x6400C005
0x62C1C001
0x6080009E
0x608000A0
0x60000052
0x6387C000
0x6380C005
0xC20202
0xC20024
0x61800202
0x61C00052
0x62000000
0xC20101
0xC20024
0x61800101
0x61C00052
0xC20104
0xC20024
0x61800104
0x61C00052
0xC20103
0xC20024
0x61800103
0x61C00052
0xC20100
0xC20024
0x61800100
0x61C00052
0x62000000
0x60C0009E
0xC20102
0xC20024
0x61800102
0x61C00052
0x62000001
0xC2010D
0xC20024
0x6180010D
0x61C00052
0x612B7C91
0xC2010C
0xC20024
0x6180010C
0x61C00052
0x612B7C91
0x612B7C91
0xC2C120
0xC20024
0x20C00003
0x20C00002

    When SBL OSPI works on the custom board,
    Bootloader_parseMultiCoreAppImage returns -1,
    and the message "Some test have failed!" appears.

    Best regards,

    Kiyomasa Imaizumi.

  • 0 in reply to Kiyomasa Imaizumi
    TI__Genius 11435 points

    Hi Kiyomasa,

    I see you are using an older 9.1 SDK, Could you please try to test this once with the latest SDK version (11.1).

    Best Regards,

    Meet.

  • 0 in reply to Meet Thakar
    Intellectual 760 points

    Hello Meet Thakar.


    As you said, the SDK version I'm using is mcu_plus_sdk_am64x_09_01_00_41.

    In SDK 9.1, I was able to enable SYSFW_TRACE_ENABLE in sciclient_defaultBoardcfg.c,
    but sciclient_defaultBoardcfg.c is not available in SDK 11.1.
    What changes should I make to the SDK?

    Also, is it okay for only SBL OSPI to use the latest SDK (11.1)?
    User applications must use the older SDK version (mcu_plus_sdk_am64x_08_06_00_45).
    This is because that is the version that was started when the application was developed.

    Best regards,

    Kiyomasa Imaizumi.

  • 0 in reply to Kiyomasa Imaizumi
    Intellectual 760 points

    Additional note: I found the file in the following path:

    C:\ti\mcu_plus_sdk_am64x_11_01_00_17\source\drivers\sciclient\sciclient_default_boardcfg\am64x\sciclient_defaultBoardcfg.c
    I'll try building sysfw with SYSFW_TRACE_ENABLE enabled.

  • 0 in reply to Kiyomasa Imaizumi
    Intellectual 760 points

    When I try to build it, I get the following error:

    c:\ti\mcu_plus_sdk_am64x_11_01_00_17>gmake -s -C .\tools\sysfw\boardcfg SOC=am64x
"Build Board Configuration Obj Files"
process_begin: CreateProcess(NULL, C:/ti/ccs2020/ccs/utils/cygwin/mkdir -p c:/ti/mcu_plus_sdk_am64x_11_01_00_17/tools/sysfw/boardcfg/obj, ...) failed.
make (e=2): 指定されたファイルが見つかりません。
makefile:199: recipe for target 'c:/ti/mcu_plus_sdk_am64x_11_01_00_17/tools/sysfw/boardcfg/obj/sciclient_defaultBoardcfg_security_hex.o' failed
gmake: *** [c:/ti/mcu_plus_sdk_am64x_11_01_00_17/tools/sysfw/boardcfg/obj/sciclient_defaultBoardcfg_security_hex.o] Error 2

c:\ti\mcu_plus_sdk_am64x_11_01_00_17>

  • 0 in reply to Kiyomasa Imaizumi
    TI__Genius 11435 points
    Kiyomasa Imaizumi said:
    but sciclient_defaultBoardcfg.c is not available in SDK 11.1.

    It's available in 11.1 as well.

    Kiyomasa Imaizumi said:
    When I try to build it, I get the following error:

    For SDK version 11.1, CCS version recommended is 20.2, Please use the same version to avoid this error.

    Kiyomasa Imaizumi said:
    Also, is it okay for only SBL OSPI to use the latest SDK (11.1)?
    User applications must use the older SDK version (mcu_plus_sdk_am64x_08_06_00_45).

    We usually recommend to use the latest SDK versions as it will have the latest bug fixes, first I want to check if using the latest SDK resolves this issue or not, so for testing this should be fine for now.

    Best Regards,
    Meet.