PROCESSOR-SDK-AM62X: stog_r5

W Z

Expert 2350 points

Part Number: PROCESSOR-SDK-AM62X
Other Parts Discussed in Thread: SK-AM62

Tool/software:

MCU SDK version: mcu_plus_sdk_am62x_10_01_00_33

Test EVM: SK-AM62

CCS version: 12.8.1

I imported the example from C:\ti\mcu_plus_sdk_am62x_10_01_00_33\examples\sdl\stog_r5f\am62x-sk\system_nortos\

Then, I compiled the M4F and R5 projects and copied the generated appimage.hs_fs into the below path.

--file=sbl_prebuilt/am62x-sk/WZ_Debug/sdl_stog_r5f_am62x-sk_r5fss0-0_nortos_ti-arm-clang.appimage.hs_fs --operation=flash --flash-offset=0xA00000

--file=sbl_prebuilt/am62x-sk/WZ_Debug/sdl_stog_r5f_am62x-sk_m4fss0-0_nortos_ti-arm-clang.appimage.hs_fs --operation=flash --flash-offset=0x100000

I use the file below to flash the test examples

4011.default_sbl_ospi_hs_fs.cfg

Below is the UART log from SBL UART

There is no uart log can get from R5 or M4F uart

[08:45:06.741]收←◆
SYSFW Firmware Version 10.1.8--v10.01.08 (Fiery Fox)
SYSFW Firmware revision 0xa
SYSFW ABI revision 4.0


[08:45:06.772]收←◆[BOOTLOADER_PROFILE] Boot Media       : FLASH 
[BOOTLOADER_PROFILE] Boot Media Clock : 166.667 MHz 
[BOOTLOADER_PROFILE] Boot Image Size  : 165 KB 
[BOOTLOADER_PROFILE] Cores present    : 
m4f0-0
r5f0-0
[BOOTLOADER PROFILE] System_init                      :       5439us 
[BOOTLOADER PROFILE] Board_init                       :          0us 
[BOOTLOADER PROFILE] Drivers_open                     :        300us 
[BOOTLOADER PROFILE] Board_driversOpen                :       1265us 
[BOOTLOADER PROFILE] Sciclient Get Version            :      10203us 
[BOOTLOADER PROFILE] App_waitForMcuPbist              :       8653us 
[BOOTLOADER PROFILE] App_waitForMcuLbist              :       7689us 
[BOOTLOADER PROFILE] App_loadImages                   :       3123us 
[BOOTLOADER PROFILE] App_loadSelfcoreImage            :       4038us 
[BOOTLOADER_PROFILE] SBL Total Time Taken             :      40715us 

Image loading done, switching to application ...
Starting MCU-m4f and 2nd stage bootloader

SYSFW Firmware Version 10.1.8--v10.01.08 (Fiery Fox)
SYSFW Firmware revision 0xa
SYSFW ABI revision 4.0

[BOOTLOADER_PROFILE] Boot Media       : FLASH 
[BOOTLOADER_PROFILE] Boot Media Clock : 166.667 MHz 
[BOOTLOADER_PROFILE] Boot Image Size  : 384 KB 
[BOOTLOADER_PROFILE] Cores present    : 
hsm-m4f0-0
r5f0-0
a530-0
[BOOTLOADER PROFILE] System_init                      :       2805us 
[BOOTLOADER PROFILE] Board_init                       :          1us 
[BOOTLOADER PROFILE] Drivers_open                     
[08:45:06.931]收←◆:        388us 
[BOOTLOADER PROFILE] Board_driversOpen                :        140us 
[BOOTLOADER PROFILE] Sciclient Get Version            :      10218us 
[BOOTLOADER PROFILE] App_loadImages                   :       2694us 
[BOOTLOADER PROFILE] App_loadSelfcoreImage            :       5066us 
[BOOTLOADER PROFILE] App_loadA53Images                :       4219us 
[BOOTLOADER_PROFILE] SBL Total Time Taken             :      25534us 

Image loading done, switching to application ...
Starting RTOS/Baremetal applications
NOTICE:  BL31: v2.11.0(debug):REL.MCUSDK.K3.10.01.00.33
NOTICE:  BL31: Built : 04:52:15, Dec 19 2024
INFO:    GICv3 without legacy support detected.
INFO:    ARM GICv3 driver initialized in EL3
INFO:    Maximum SPI INTID supported: 287
INFO:    SYSFW ABI: 4.0 (firmware rev 0x000a '10.1.8--v10.01.08 (Fiery Fox)')

[08:45:08.004]收←◆ERROR:   Timeout waiting for thread SP_RESPONSE to fill
ERROR:   Thread SP_RESPONSE verification failed (-60)
ERROR:   Message receive failed (-60)
ERROR:   Failed to get response (-60)
ERROR:   Transfer send failed (-60)
WARNING: Unable to take system power reference
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for erratum 855873 was applied
INFO:    BL31: cortex_a53: CPU workaround for erratum 1530924 was applied

[08:45:09.055]收←◆ERROR:   Timeout waiting for thread SP_RESPONSE to fill
ERROR:   Thread SP_RESPONSE verification failed (-60)
ERROR:   Message receive failed (-60)
ERROR:   Failed to get response (-60)
ERROR:   Transfer send failed (-60)
ERROR:   Unable to query firmware capabilities (-60)
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x80080000
INFO:    SPSR = 0x3c9

Question: How to make this system stog example run?

24 days ago

0 W Z 20 days ago

Expert 2350 points

Could a TI expert help?

0 W Z 19 days ago in reply to W Z

Expert 2350 points

This ticket needs help.

+1 TommySong 19 days ago in reply to W Z

TI__Genius 9520 points

Seems there is no DM FW running on DMR5 core that cause the error in the log.

The suggestion for development is to load the example image through JTAG to run. Here is the steps: https://software-dl.ti.com/mcu-plus-sdk/esd/AM62X/latest/exports/docs/api_guide_am62x/CCS_LAUNCH_PAGE.html

For production code, the application code that need to integrate along with DM FW functionality. Please refer below page: https://software-dl.ti.com/mcu-plus-sdk/esd/AM62X/latest/exports/docs/api_guide_am62x/DEVELOP_AND_DEBUG_DMR5.html

0 W Z 19 days ago in reply to TommySong

Expert 2350 points

I did not see any wrong steps of my flash software process. All steps follow TI's instructions.

And I have not debugged this DM software, I flash them into the flash and run.

Could you please help reproduce it from your side? I think there is a bug in the example.

0 W Z 19 days ago in reply to W Z

Expert 2350 points

TI FAE yong-zhang@ti.com also has the same issue as me when he tried the example on his AM62X-LP EVM board.

0 Yong Zhang 19 days ago in reply to W Z

TI__Genius 16711 points

Dear Zheng.

Sorry, this example need be run with CCS.

for more detail, please check this link.

AM62Ax MCU+ SDK: SDL STOG Example

thanks a lot!

yong

0 W Z 19 days ago in reply to Yong Zhang

Expert 2350 points

I use the default_sbl_null_hs_fs.cfg to flash the default TI software.

Then use CCS to load R5 sdl_stog_r5f_am62x-sk_r5fss0-0_nortos_ti-arm-clang and run.

Then use CCS to load M4F sdl_stog_r5f_am62x-sk_m4fss0-0_nortos_ti-arm-clang and run.

The log is below.

[MAIN_Cortex_R5_0_0] Sciclient direct init..... SUCCESS
Enter R5 DM application

 Init MCU ESM complete 

SDL_TOG_setIntrEnable complete 

SDL_TOG_init.timeout complete 

SDL_TOG_start complete 
[BLAZAR_Cortex_M4F_0] Enter M4F application
[MAIN_Cortex_R5_0_0] 
SDL_TOG_stop complete 

All tests have passed.

0 TommySong 18 days ago in reply to W Z

TI__Genius 9520 points

That's great, thanks for the update.

Will close this ticket~

Br, Tommy

0 W Z 18 days ago in reply to TommySong

Expert 2350 points

But when I migrate the R5 sdl_stog_r5f_am62x-sk_r5fss0-0_nortos_ti-arm-clang into hello_world_am62x-sk_r5fss0-0_freertos_ti-arm-clang.

It still cannot work.

UART Log from R5 core, it seems that waits for the M4F trigger the interrupt. I also use the CCS to load M4F sdl_stog_r5f_am62x-sk_m4fss0-0_nortos_ti-arm-clang.

But the Uart log from R5 does not show anything.

We expect that "SDL_TOG_stop complete" and "All tests have passed" should show.

Are there any migration notes that need to be taken care of?

Enter R5 APP 
Hello World!

TOG Sample Example 

 Init MCU ESM complete 

SDL_TOG_setIntrEnable complete 

SDL_TOG_init.timeout complete 

SDL_TOG_start complete

Code of hello_world_am62x-sk_r5fss0-0_freertos_ti-arm-clang

void main_thread(void *args)
{
    int32_t status = SystemP_SUCCESS;

    /* Open drivers */
    Drivers_open();
    /* Open flash and board drivers */
    status = Board_driversOpen();
    DebugP_assert(status==SystemP_SUCCESS);
    DebugP_log("\nEnter R5 APP \r\n");

    /* Init LPM specific data */
//    Sciclient_initDeviceManagerLPMData(&gDMLPMData);
//
//    sciServer_init();

    hello_world_main(NULL);
    tog_test_main(NULL);
    DebugP_log("\nExit R5 \r\n");

    /* Close board and flash drivers */
    Board_driversClose();
    /* Close drivers */
    Drivers_close();

    vTaskDelete(NULL);
}

0 Nihar Potturu 17 days ago in reply to W Z

TI__Mastermind 20266 points

Hello,

I will retry to reproduce the issue and let you know. I will post my update by EOD.

Regards,

Nihar Potturu

+1 W Z 17 days ago in reply to Nihar Potturu

Expert 2350 points

Thanks, Nihar, I already fixed it. It is a problem due to migration. We can close this ticket!

Should take care of linker.cmd and symbols.

Processors

Processors forum

PROCESSOR-SDK-AM62X: stog_r5