LP-AM243: Example resets after 3 mins

Frank Walzer

Part Number: LP-AM243
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

I am posting on behalf of my customer:

Seeking guidance regarding an issue I'm experiencing with the Sitara AM243x-LP device.

I'm currently using the SDK version 10.01.00.02, available at [TI GitHub SDK URL](https://github.com/TexasInstruments/mcupsdk-core), and I'm encountering a consistent malfunction. Specifically, every example I flash onto the device with the sbl_ospi_multi_partition setup malfunctions approximately 3 minutes after a reset.

Here are the details of my setup and the issue:

- Multi-Partition Example: https://github.com/TexasInstruments/mcupsdk-core/tree/next/examples/drivers/boot/sbl_ospi_multi_partition/am243x-lp/r5fss0-0_nortos

- Error Location The error appears in the code referenced in this section https://github.com/TexasInstruments/mcupsdk-core/blob/2a1be286566c7fc4e264fa48f002afabf4d4c628/examples/drivers/boot/sbl_ospi_multi_partition/am243x-lp/r5fss0-0_nortos/main.c#L192-L213.

Upon investigation, I've found that the issue is related to the Sciclient level, specifically during the Auth Image process. One of the message flags incorrectly shows 0 instead of 2 in the function here https://github.com/TexasInstruments/mcupsdk-core/blob/2a1be286566c7fc4e264fa48f002afabf4d4c628/source/drivers/sciclient/sciclient.c#L379, with the discrepancy occurring here https://github.com/TexasInstruments/mcupsdk-core/blob/2a1be286566c7fc4e264fa48f002afabf4d4c628/source/drivers/sciclient/sciclient.c#L529-L530.

Interestingly, the malfunction persists across power cycles, only resolving itself after the device has been off for an extended period. I discovered a mention of a 3-minute watchdog timer in the technical reference manual (page 2032), which the DMSC ROM sets up. However, it seems puzzling why a simple restart doesn't resolve the issue.

-------

regards, Frank

8 months ago

0 Swargam Anil 8 months ago

TI__Mastermind 45736 points

Hello Frank,

I am looking at your queries and you may expect reply in one or two days .

Regards,

Anil.

0 Prashant Shivhare 7 months ago in reply to Swargam Anil

TI__Guru 68771 points

Hello,

Frank Walzer said:
I'm currently using the SDK version 10.01.00.02, available at

This is not a released SDK tag.

Please ask the customer to test with the released SDK v10.1 & share the boot logs to better understand the issue.

https://www.ti.com/tool/download/MCU-PLUS-SDK-AM243X/10.01.00.32

Regards,

Prashant

0 Petr Kucera 7 months ago in reply to Prashant Shivhare

Prodigy 172 points

Hi Prashant,

I used SDK v10.1. I added simple log prints to monitor code behavior.

/* boot, i.e load and run CPUs not in self CPU cluster */
int32_t App_bootCpu(uint32_t bootDrvInstanceId, uint32_t cpuId)
{
    int32_t status = SystemP_FAILURE;
    Bootloader_BootImageInfo bootImageInfo;
    Bootloader_Params bootParams;
    Bootloader_Handle bootHandle;
    Bootloader_Config *bootConfig;

    Bootloader_Params_init(&bootParams);
    Bootloader_BootImageInfo_init(&bootImageInfo);

    bootHandle = Bootloader_open(bootDrvInstanceId, &bootParams);
    bootConfig = (Bootloader_Config *)bootHandle;
    bootConfig->scratchMemPtr = gAppimage;

    if(bootHandle == NULL){
      DebugP_log("[App_bootCpu()] bootHandle == NULL\r\n");
    }

    if(bootHandle != NULL)
    {
        status = Bootloader_parseMultiCoreAppImage(bootHandle, &bootImageInfo);
        DebugP_log("[App_bootCpu()] status_01: %d\r\n", status);
        if(status == SystemP_SUCCESS)
        {
            bootImageInfo.cpuInfo[cpuId].clkHz = Bootloader_socCpuGetClkDefault(cpuId);
            status = Bootloader_bootCpu(bootHandle, &bootImageInfo.cpuInfo[cpuId]);
            DebugP_log("[App_bootCpu()] status_02: %d\r\n", status);
        }
        Bootloader_close(bootHandle);
    }
    return status;
}

/* load but DONT run CPU in self CPU cluster, i.e R5FSS0-0 */
int32_t App_bootLoadSelfCpu(uint32_t bootDrvInstanceId, uint32_t cpuId)
{
    int32_t status = SystemP_FAILURE;
    Bootloader_BootImageInfo bootImageInfo;
    Bootloader_Handle bootHandle;
    Bootloader_Params bootParams;
    Bootloader_Config *bootConfig;

    Bootloader_Params_init(&bootParams);
    Bootloader_BootImageInfo_init(&bootImageInfo);

    bootHandle = Bootloader_open(bootDrvInstanceId, &bootParams);
    bootConfig = (Bootloader_Config *)bootHandle;
    bootConfig->scratchMemPtr = gAppimage;
    if(bootHandle != NULL)
    {
        status = Bootloader_parseMultiCoreAppImage(bootHandle, &bootImageInfo);
        if(status == SystemP_SUCCESS)
        {
            bootImageInfo.cpuInfo[cpuId].clkHz = Bootloader_socCpuGetClkDefault(cpuId);
            status = Bootloader_loadSelfCpu( bootHandle, &bootImageInfo.cpuInfo[cpuId], FALSE);
        }
        Bootloader_close(bootHandle);
    }
    return status;
}

int main(void)
{
    int32_t status = 0xFF;

    Bootloader_socWaitForFWBoot();

#ifndef DISABLE_WARM_REST_WA
    /* Warm Reset Workaround to prevent CPSW register lockup */
    if (!Bootloader_socIsMCUResetIsoEnabled())
    {
        Bootloader_socResetWorkaround();
    }
#endif
    if (!Bootloader_socIsMCUResetIsoEnabled())
    {
        /* Update devGrp to ALL to initialize MCU domain when reset isolation is
        not enabled */
        Sciclient_BoardCfgPrms_t boardCfgPrms_pm =
            {
                .boardConfigLow = (uint32_t)0,
                .boardConfigHigh = 0,
                .boardConfigSize = 0,
                .devGrp = DEVGRP_ALL,
            };

        status = Sciclient_boardCfgPm(&boardCfgPrms_pm);

        /* Enable MCU PLL. MCU PLL will not be enabled by DMSC when devGrp is set
        to Main in boardCfg */
        Bootloader_enableMCUPLL();
    }

    System_init();
    
    Bootloader_socOpenFirewalls();

    Bootloader_socNotifyFirewallOpen();

    Drivers_open();

    DebugP_log("\r\n");
    DebugP_log("Starting OSPI Multi-Partition Bootloader ... \r\n");

    DebugP_log("[LOG_01] %d\r\n", status);

    status = Board_driversOpen();
    DebugP_assert(status == SystemP_SUCCESS);

    DebugP_log("[LOG_02] %d\r\n", status);

    status = Sciclient_getVersionCheck(1);

    DebugP_log("[LOG_03] %d\r\n", status);

    if(SystemP_SUCCESS == status)
    {
        /* load and run all CPUs, if a application is not found, the core is run with a while(1); loop */
        uint32_t coreVariant = Bootloader_socGetCoreVariant();
        if((coreVariant == BOOTLOADER_DEVICE_VARIANT_QUAD_CORE) || (coreVariant == BOOTLOADER_DEVICE_VARIANT_DUAL_CORE))
        {
            if(status == SystemP_SUCCESS)
            {
                status = App_bootCpu( CONFIG_BOOTLOADER_FLASH_R5FSS1_0, CSL_CORE_ID_R5FSS1_0 );
                DebugP_log("[CPU R-1_0] %d\r\n", status);
            }
            if((Bootloader_socIsR5FSSDual(BOOTLOADER_R5FSS1) == TRUE) && (status == SystemP_SUCCESS))
            {
                status = App_bootCpu( CONFIG_BOOTLOADER_FLASH_R5FSS1_1, CSL_CORE_ID_R5FSS1_1 );
                DebugP_log("[CPU R-1_1] %d\r\n", status);
            }
        }
        if (!Bootloader_socIsMCUResetIsoEnabled())
        {
            if(SystemP_SUCCESS == status)
            {
                status = App_bootCpu( CONFIG_BOOTLOADER_FLASH_M4FSS0_0, CSL_CORE_ID_M4FSS0_0 );
                DebugP_log("[CPU M-0_0] %d\r\n", status);
            }
        }
        if(SystemP_SUCCESS == status)
        {
            status = App_bootLoadSelfCpu( CONFIG_BOOTLOADER_FLASH_R5FSS0_0, CSL_CORE_ID_R5FSS0_0 );
            DebugP_log("[CPU R-0_0] %d\r\n", status);
        }
        if(SystemP_SUCCESS == status)
        {
            status = App_bootLoadSelfCpu( CONFIG_BOOTLOADER_FLASH_R5FSS0_1, CSL_CORE_ID_R5FSS0_1 );
            DebugP_log("[CPU R-0_1] %d\r\n", status);
        }
        if(SystemP_SUCCESS == status)
        {
            /* Reset self cluster and run both the CPUs */
            status = Bootloader_socCpuResetReleaseSelf();
        }
    }
    if(status != SystemP_SUCCESS )
    {
        DebugP_log("Some tests have failed!!\r\n");
    }
    Drivers_close();
    System_deinit();

    return 0;
}

This is my log

First attempt:

Starting OSPI Multi-Partition Bootloader ... 
[LOG_01] 0
[LOG_02] 0

DMSC Firmware Version 10.0.8--v10.00.08 (Fiery Fox)
DMSC Firmware revision 0xa
DMSC ABI revision 4.0

[LOG_03] 0
[App_bootCpu()] status_01: 0
[App_bootCpu()] status_02: 0
[CPU R-1_0] 0
[App_bootCpu()] status_01: -1
[CPU R-1_1] -1
Some tests have failed!!

Second attempt:

Starting OSPI Multi-Partition Bootloader ... 
[LOG_01] 0
[LOG_02] 0

DMSC Firmware Version 10.0.8--v10.00.08 (Fiery Fox)
DMSC Firmware revision 0xa
DMSC ABI revision 4.0

[LOG_03] 0
[App_bootCpu()] status_01: 0
[App_bootCpu()] status_02: 0
[CPU R-1_0] 0
[App_bootCpu()] status_01: 0
[App_bootCpu()] status_02: 0
[CPU R-1_1] 0
[App_bootCpu()] status_01: 0
[App_bootCpu()] status_02: 0
[CPU M-0_0] 0
[CPU R-0_0] 0
[CPU R-0_1] -1
Some tests have failed!!

Third attempt:

Starting OSPI Multi-Partition Bootloader ... 
[LOG_01] 0
[LOG_02] 0

DMSC Firmware Version 10.0.8--v10.00.08 (Fiery Fox)
DMSC Firmware revision 0xa
DMSC ABI revision 4.0

[LOG_03] 0
[App_bootCpu()] status_01: -1
[CPU R-1_0] -1
Some tests have failed!!

I investigated it and found that problem is in auth process.

After Disable Auth For Application Image in BOOTLOADER in SysConfig, it works OK.

Could you suggest me any solution, please?

0 Prashant Shivhare 7 months ago in reply to Petr Kucera

TI__Guru 68771 points

Hello,

Petr Kucera said:
I investigated it and found that problem is in auth process.

This is a known SYSFW issue. It will be fixed in the next SYSFW release as part of the next SDK release.

For now, you may continue to boot the application by disabling the authentication.

Regards,

Prashant

0 Petr Kucera 7 months ago in reply to Prashant Shivhare

Prodigy 172 points

Alright, is there any known release date for the new version, even an approximate one? Like in two weeks or a month?"

0 Prashant Shivhare 7 months ago in reply to Petr Kucera

TI__Guru 68771 points

Hello,

The last SDK was released just few weeks back. So, it will be about 3 or 4 months before the next SDK release.

However, I already have the SYSFW binaries (hotfix) that fixes the issue. I will share them with Frank for him to share with you on private channel. Please test those binaries & let me know if it actually fixes the issue for you.

Regards,

Prashant

0 Petr Kucera 7 months ago in reply to Prashant Shivhare

Prodigy 172 points

Hi, I used your SYSFW binaries but the problem still persist. The program run for 3 mins OK, but after 3 mins can't auth images after reset.

There is a logs for multiple runs:

Starting OSPI Multi-Partition Bootloader ... 
[LOG_01] 0
[LOG_02] 0

DMSC Firmware Version 10.1.8-v10.01.08-2-gabffe (Fier
DMSC Firmware revision 0xa
DMSC ABI revision 4.0

[LOG_03] 0
[App_bootCpu()] status_01: 0
[App_bootCpu()] status_02: 0
[CPU R-1_0] 0
[App_bootCpu()] status_01: 0
[App_bootCpu()] status_02: 0
[CPU R-1_1] 0
[App_bootCpu()] status_01: 0
[App_bootCpu()] status_02: 0
[CPU M-0_0] 0
[CPU R-0_0] 0
[CPU R-0_1] 0
All tests have passed!!

Starting OSPI Multi-Partition Bootloader ... 
[LOG_01] 0
[LOG_02] 0

DMSC Firmware Version 10.1.8-v10.01.08-2-gabffe (Fier
DMSC Firmware revision 0xa
DMSC ABI revision 4.0

[LOG_03] 0
[App_bootCpu()] status_01: 0
[App_bootCpu()] status_02: 0
[CPU R-1_0] 0
[App_bootCpu()] status_01: 0
[App_bootCpu()] status_02: 0
[CPU R-1_1] 0
[App_bootCpu()] status_01: 0
[App_bootCpu()] status_02: 0
[CPU M-0_0] 0
[CPU R-0_0] 0
[CPU R-0_1] 0
All tests have passed!!

Starting OSPI Multi-Partition Bootloader ... 
[LOG_01] 0
[LOG_02] 0

DMSC Firmware Version 10.1.8-v10.01.08-2-gabffe (Fier
DMSC Firmware revision 0xa
DMSC ABI revision 4.0

[LOG_03] 0
[App_bootCpu()] status_01: 0
[App_bootCpu()] status_02: 0
[CPU R-1_0] 0
[App_bootCpu()] status_01: 0
[App_bootCpu()] status_02: 0
[CPU R-1_1] 0
[App_bootCpu()] status_01: 0
[App_bootCpu()] status_02: 0
[CPU M-0_0] 0
[CPU R-0_0] 0
[CPU R-0_1] 0
All tests have passed!!

Starting OSPI Multi-Partition Bootloader ... 
[LOG_01] 0
[LOG_02] 0

DMSC Firmware Version 10.1.8-v10.01.08-2-gabffe (Fier
DMSC Firmware revision 0xa
DMSC ABI revision 4.0

[LOG_03] 0
[App_bootCpu()] status_01: 0
[App_bootCpu()] status_02: 0
[CPU R-1_0] 0
[App_bootCpu()] status_01: 0
[App_bootCpu()] status_02: 0
[CPU R-1_1] 0
[App_bootCpu()] status_01: 0
[App_bootCpu()] status_02: 0
[CPU M-0_0] 0
[CPU R-0_0] 0
[CPU R-0_1] 0
All tests have passed!!

Starting OSPI Multi-Partition Bootloader ... 
[LOG_01] 0
[LOG_02] 0

DMSC Firmware Version 10.1.8-v10.01.08-2-gabffe (Fier
DMSC Firmware revision 0xa
DMSC ABI revision 4.0

[LOG_03] 0
[App_bootCpu()] status_01: 0
[App_bootCpu()] status_02: 0
[CPU R-1_0] 0
[App_bootCpu()] status_01: -1
[CPU R-1_1] -1
Some tests have failed!!

Starting OSPI Multi-Partition Bootloader ... 
[LOG_01] 0
[LOG_02] 0

DMSC Firmware Version 10.1.8-v10.01.08-2-gabffe (Fier
DMSC Firmware revision 0xa
DMSC ABI revision 4.0

[LOG_03] 0
[App_bootCpu()] status_01: -1
[CPU R-1_0] -1
Some tests have failed!!

0 Prashant Shivhare 7 months ago in reply to Petr Kucera

TI__Guru 68771 points

Petr Kucera said:
I used your SYSFW binaries but the problem still persist. The program run for 3 mins OK, but after 3 mins can't auth images after reset.

May I know what this program is? And why does it run for only 3 mins?

0 Petr Kucera 7 months ago in reply to Prashant Shivhare

Prodigy 172 points

Hi, problem is in this example: https://github.com/TexasInstruments/mcupsdk-core/tree/next/examples/drivers/boot/sbl_ospi_multi_partition/am243x-lp/r5fss0-0_nortos.

First boot runs correctly. When I reset device, program ends correctly again. But it I reset device after 3 min, the program failed. I guess that if I plug-out device and plug-in immediately, everything will work OK, but not. The problem has still occurred. If the devboard is without power for more than 10 mins, everything starts working again correctly to 3 mins limit.

0 Prashant Shivhare 7 months ago in reply to Petr Kucera

TI__Guru 68771 points

Hi, can you please enable the timestamp in the UART console you are using & share the captured logs to better relate the issue with these timings?

0 Petr Kucera 6 months ago in reply to Prashant Shivhare

Prodigy 172 points

Sure, this is log with timestamps.

16:58:09:115 -> Starting OSPI Multi-Partition Bootloader ... 
16:58:09:119 -> [LOG_01] 0
16:58:09:120 -> [LOG_02] 0
16:58:09:121 -> 
16:58:09:121 -> DMSC Firmware Version 10.1.8-v10.01.08-2-gabffe (Fier
16:58:09:126 -> DMSC Firmware revision 0xa
16:58:09:128 -> DMSC ABI revision 4.0
16:58:09:130 -> 
16:58:09:130 -> [LOG_03] 0
16:58:09:162 -> [App_bootCpu()] status_01: 0
16:58:09:166 -> [App_bootCpu()] status_02: 0
16:58:09:168 -> [CPU R-1_0] 0
16:58:09:200 -> [App_bootCpu()] status_01: 0
16:58:09:203 -> [App_bootCpu()] status_02: 0
16:58:09:205 -> [CPU R-1_1] 0
16:58:09:263 -> [App_bootCpu()] status_01: -1
16:58:09:265 -> [CPU M-0_0] -1
16:58:09:267 -> Some tests have failed!!

0 Prashant Shivhare 6 months ago in reply to Petr Kucera

TI__Guru 68771 points

Hello,

Can you please enable the SYSFW logs and share the same?

The Sysfw logs can be enabled as follows:

Change "#undef SYSFW_TRACE_ENABLE" to "#define SYSFW_TRACE_ENABLE" in source/drivers/sciclient/sciclient_default_boardcfg/am64x/sciclient_defaultBoardcfg.c.
Build the board configurations with: make -s -C tools/sysfw/boardcfg
Add another UART instance in the SBL for MAIN_UART1.
Build the SBL.

If the steps are followed correctly, you should see Sysfw logs on MAIN_UART1.

Regards,

Prashant

0 Petr Kucera 6 months ago in reply to Prashant Shivhare

Prodigy 172 points

Could you provide me more detail, please?

I changed #undef to #define as you mentioned

#define SYSFW_TRACE_ENABLE
// #undef SYSFW_TRACE_ENABLE

I build it with command gmake -s -C tools/sysfw/boardcfg SOC=am243x
Build libs with gmake -s -C libs
And build sbl with command gmake -s -C sbl
I created configuration for UART1

And flashed my device, but I can't see Sysfw log. Is possible that SYSFW log doesn't exists for AM243x, it's not mentioned here software-dl.ti.com/.../trace.html

0 Prashant Shivhare 5 months ago in reply to Petr Kucera

TI__Guru 68771 points

Hello,

Have you made sure the UART console is connected to the MAIN_UART1 port of the device?

In case the UART1 is not available, please try collecting the logs from memory buffer.

https://software-dl.ti.com/tisci/esd/latest/4_trace/trace.html?highlight=trace%20layer#trace-memory-buffer-location

Regards,

Prashant

0 Petr Kucera 5 months ago in reply to Prashant Shivhare

Prodigy 172 points

Hello Prashant,

I was relocated into different problem, so sorry for late response. But this problem is still actual for us. There is interpreted SYSFW Trace log that you motioned.

This is log when R0-0 failed

Configuring trace data version to: 0x03007
9002
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29000:   BasePort: Unknown Action: 0x03 MSG:0x029000
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29002:   BasePort: Unknown Action: 0x03 MSG:0x029002
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29000:   BasePort: Unknown Action: 0x03 MSG:0x029000
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29002:   BasePort: Unknown Action: 0x03 MSG:0x029002
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29000:   BasePort: Unknown Action: 0x03 MSG:0x029000
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29002:   BasePort: Unknown Action: 0x03 MSG:0x029002
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29000:   BasePort: Unknown Action: 0x03 MSG:0x029000
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29002:   BasePort: Unknown Action: 0x03 MSG:0x029002
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29000:   BasePort: Unknown Action: 0x03 MSG:0x029000
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29002:   BasePort: Unknown Action: 0x03 MSG:0x029002
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29000:   BasePort: Unknown Action: 0x03 MSG:0x029000
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29002:   BasePort: Unknown Action: 0x03 MSG:0x029002
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29000:   BasePort: Unknown Action: 0x03 MSG:0x029000
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29002:   BasePort: Unknown Action: 0x03 MSG:0x029002
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29000:   BasePort: Unknown Action: 0x03 MSG:0x029000
0xC200240xC20002
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x04003007:   BasePort: TRACE_DATA_VERSION(OSAL/Baseport trace data version): Trace version major: 0x03 Trace version minor: 0x007
0x04400A08:   BasePort:   SYSFW_VERSION(System Firmware version): version: 10 subversion: 0 patch: 8
0x00C2C000:   BasePort: Unknown Action: 0x03 MSG:0x02C000
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2010C:   BasePort: Unknown Action: 0x03 MSG:0x02010C
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x6180010C: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x0000010C
0x61C0007B: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 123 Clock ID: 0
0x612F7C86: Power Management: CLOCK_SET_RATE(Clock Frequency has been changed: significand * 2^Exponent Hz): Clock ID: 134 Clock Frequency{significand}: 95 Clock Frequency{Exponent}: 23
0x612F7C86: Power Management: CLOCK_SET_RATE(Clock Frequency has been changed: significand * 2^Exponent Hz): Clock ID: 134 Clock Frequency{significand}: 95 Clock Frequency{Exponent}: 23
0x00C20200:   BasePort: Unknown Action: 0x03 MSG:0x020200
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x61800200: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x00000200
0x61C0007B: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 123 Clock ID: 0
0x62000000: Power Management: MSG_PARAM_VAL(TI-SCI message content: value): Target Value: 0x00000000
0x00C2C400:   BasePort: Unknown Action: 0x03 MSG:0x02C400
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2C400:   BasePort: Unknown Action: 0x03 MSG:0x02C400
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2C100:   BasePort: Unknown Action: 0x03 MSG:0x02C100
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2C101:   BasePort: Unknown Action: 0x03 MSG:0x02C101
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C20200:   BasePort: Unknown Action: 0x03 MSG:0x020200
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x61800200: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x00000200
0x61C0007B: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 123 Clock ID: 0
0x62000002: Power Management: MSG_PARAM_VAL(TI-SCI message content: value): Target Value: 0x00000002
0x62C0A000: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 2 PD Usage Count: 8192
0x62C0005B: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 0 PD Usage Count: 91
0x64036000: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 13 Module Retention Count: 8192
0x64006003: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 1 Module Retention Count: 8195
0x62C0A001: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 2 PD Usage Count: 8193
0x6000007B: Power Management:     DEVICE_ON(Device has been Turned ON): Device ID: 123
0x63836000: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 13 Module Use Count: 8192
0x63806003: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 1 Module Use Count: 8195
0x00C2C400:   BasePort: Unknown Action: 0x03 MSG:0x02C400
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2C100:   BasePort: Unknown Action: 0x03 MSG:0x02C100
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2C101:   BasePort: Unknown Action: 0x03 MSG:0x02C101
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2C001:   BasePort: Unknown Action: 0x03 MSG:0x02C001
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2010E:   BasePort: Unknown Action: 0x03 MSG:0x02010E
0x00C20029:   BasePort: Unknown Action: 0x03 MSG:0x020029
0x6180010E: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x0000010E
0x61C0007B: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 123 Clock ID: 0
0x00C2010E:   BasePort: Unknown Action: 0x03 MSG:0x02010E
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x6180010E: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x0000010E
0x61C0007B: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 123 Clock ID: 0
0x00C2C400:   BasePort: Unknown Action: 0x03 MSG:0x02C400
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2C120:   BasePort: Unknown Action: 0x03 MSG:0x02C120
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024

This is the log when R0-0 runs OK

Configuring trace data version to: 0x03007
9002
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29000:   BasePort: Unknown Action: 0x03 MSG:0x029000
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29002:   BasePort: Unknown Action: 0x03 MSG:0x029002
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29000:   BasePort: Unknown Action: 0x03 MSG:0x029000
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29002:   BasePort: Unknown Action: 0x03 MSG:0x029002
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29000:   BasePort: Unknown Action: 0x03 MSG:0x029000
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29002:   BasePort: Unknown Action: 0x03 MSG:0x029002
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29000:   BasePort: Unknown Action: 0x03 MSG:0x029000
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29002:   BasePort: Unknown Action: 0x03 MSG:0x029002
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29000:   BasePort: Unknown Action: 0x03 MSG:0x029000
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29002:   BasePort: Unknown Action: 0x03 MSG:0x029002
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29000:   BasePort: Unknown Action: 0x03 MSG:0x029000
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29002:   BasePort: Unknown Action: 0x03 MSG:0x029002
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29000:   BasePort: Unknown Action: 0x03 MSG:0x029000
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29002:   BasePort: Unknown Action: 0x03 MSG:0x029002
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29000:   BasePort: Unknown Action: 0x03 MSG:0x029000
0xC200240xC20002
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x04003007:   BasePort: TRACE_DATA_VERSION(OSAL/Baseport trace data version): Trace version major: 0x03 Trace version minor: 0x007
0x04400A08:   BasePort:   SYSFW_VERSION(System Firmware version): version: 10 subversion: 0 patch: 8
0x00C2C000:   BasePort: Unknown Action: 0x03 MSG:0x02C000
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2010C:   BasePort: Unknown Action: 0x03 MSG:0x02010C
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x6180010C: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x0000010C
0x61C0007B: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 123 Clock ID: 0
0x612F7C86: Power Management: CLOCK_SET_RATE(Clock Frequency has been changed: significand * 2^Exponent Hz): Clock ID: 134 Clock Frequency{significand}: 95 Clock Frequency{Exponent}: 23
0x612F7C86: Power Management: CLOCK_SET_RATE(Clock Frequency has been changed: significand * 2^Exponent Hz): Clock ID: 134 Clock Frequency{significand}: 95 Clock Frequency{Exponent}: 23
0x00C20200:   BasePort: Unknown Action: 0x03 MSG:0x020200
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x61800200: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x00000200
0x61C0007B: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 123 Clock ID: 0
0x62000000: Power Management: MSG_PARAM_VAL(TI-SCI message content: value): Target Value: 0x00000000
0x00C2C400:   BasePort: Unknown Action: 0x03 MSG:0x02C400
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2C400:   BasePort: Unknown Action: 0x03 MSG:0x02C400
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2C100:   BasePort: Unknown Action: 0x03 MSG:0x02C100
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2C101:   BasePort: Unknown Action: 0x03 MSG:0x02C101
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C20200:   BasePort: Unknown Action: 0x03 MSG:0x020200
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x61800200: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x00000200
0x61C0007B: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 123 Clock ID: 0
0x62000002: Power Management: MSG_PARAM_VAL(TI-SCI message content: value): Target Value: 0x00000002
0x62C0A000: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 2 PD Usage Count: 8192
0x62C0005B: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 0 PD Usage Count: 91
0x64036000: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 13 Module Retention Count: 8192
0x64006003: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 1 Module Retention Count: 8195
0x62C0A001: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 2 PD Usage Count: 8193
0x6000007B: Power Management:     DEVICE_ON(Device has been Turned ON): Device ID: 123
0x63836000: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 13 Module Use Count: 8192
0x63806003: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 1 Module Use Count: 8195
0x00C2C400:   BasePort: Unknown Action: 0x03 MSG:0x02C400
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2C100:   BasePort: Unknown Action: 0x03 MSG:0x02C100
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2C101:   BasePort: Unknown Action: 0x03 MSG:0x02C101
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2C001:   BasePort: Unknown Action: 0x03 MSG:0x02C001
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2010E:   BasePort: Unknown Action: 0x03 MSG:0x02010E
0x00C20029:   BasePort: Unknown Action: 0x03 MSG:0x020029
0x6180010E: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x0000010E
0x61C0007B: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 123 Clock ID: 0
0x00C2010E:   BasePort: Unknown Action: 0x03 MSG:0x02010E
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x6180010E: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x0000010E
0x61C0007B: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 123 Clock ID: 0
0x00C2C400:   BasePort: Unknown Action: 0x03 MSG:0x02C400
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2C120:   BasePort: Unknown Action: 0x03 MSG:0x02C120
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2C000:   BasePort: Unknown Action: 0x03 MSG:0x02C000
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2010C:   BasePort: Unknown Action: 0x03 MSG:0x02010C
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x6180010C: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x0000010C
0x61C0007C: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 124 Clock ID: 0
0x612F7C86: Power Management: CLOCK_SET_RATE(Clock Frequency has been changed: significand * 2^Exponent Hz): Clock ID: 134 Clock Frequency{significand}: 95 Clock Frequency{Exponent}: 23
0x612F7C86: Power Management: CLOCK_SET_RATE(Clock Frequency has been changed: significand * 2^Exponent Hz): Clock ID: 134 Clock Frequency{significand}: 95 Clock Frequency{Exponent}: 23
0x00C20200:   BasePort: Unknown Action: 0x03 MSG:0x020200
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x61800200: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x00000200
0x61C0007C: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 124 Clock ID: 0
0x62000000: Power Management: MSG_PARAM_VAL(TI-SCI message content: value): Target Value: 0x00000000
0x00C2C400:   BasePort: Unknown Action: 0x03 MSG:0x02C400
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2C400:   BasePort: Unknown Action: 0x03 MSG:0x02C400
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2C100:   BasePort: Unknown Action: 0x03 MSG:0x02C100
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2C101:   BasePort: Unknown Action: 0x03 MSG:0x02C101
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C20200:   BasePort: Unknown Action: 0x03 MSG:0x020200
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x61800200: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x00000200
0x61C0007C: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 124 Clock ID: 0
0x62000002: Power Management: MSG_PARAM_VAL(TI-SCI message content: value): Target Value: 0x00000002
0x62C0A002: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 2 PD Usage Count: 8194
0x64038000: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 14 Module Retention Count: 0
0x64036001: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 13 Module Retention Count: 8193
0x62C0A003: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 2 PD Usage Count: 8195
0x6000007C: Power Management:     DEVICE_ON(Device has been Turned ON): Device ID: 124
0x63838000: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 14 Module Use Count: 0
0x63836001: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 13 Module Use Count: 8193
0x00C2C100:   BasePort: Unknown Action: 0x03 MSG:0x02C100
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2C101:   BasePort: Unknown Action: 0x03 MSG:0x02C101
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2C001:   BasePort: Unknown Action: 0x03 MSG:0x02C001
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2010E:   BasePort: Unknown Action: 0x03 MSG:0x02010E
0x00C2002B:   BasePort: Unknown Action: 0x03 MSG:0x02002B
0x6180010E: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x0000010E
0x61C0007C: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 124 Clock ID: 0
0x00C2010E:   BasePort: Unknown Action: 0x03 MSG:0x02010E
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x6180010E: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x0000010E
0x61C0007C: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 124 Clock ID: 0
0x00C2C000:   BasePort: Unknown Action: 0x03 MSG:0x02C000
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2010C:   BasePort: Unknown Action: 0x03 MSG:0x02010C
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x6180010C: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x0000010C
0x61C00409: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 9 Clock ID: 1
0x612D7CD9: Power Management: CLOCK_SET_RATE(Clock Frequency has been changed: significand * 2^Exponent Hz): Clock ID: 217 Clock Frequency{significand}: 95 Clock Frequency{Exponent}: 22
0x612D7CD9: Power Management: CLOCK_SET_RATE(Clock Frequency has been changed: significand * 2^Exponent Hz): Clock ID: 217 Clock Frequency{significand}: 95 Clock Frequency{Exponent}: 22
0x00C20200:   BasePort: Unknown Action: 0x03 MSG:0x020200
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x61800200: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x00000200
0x61C00009: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 9 Clock ID: 0
0x62000000: Power Management: MSG_PARAM_VAL(TI-SCI message content: value): Target Value: 0x00000000
0x00C20202:   BasePort: Unknown Action: 0x03 MSG:0x020202
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x61800202: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x00000202
0x61C00009: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 9 Clock ID: 0
0x62000001: Power Management: MSG_PARAM_VAL(TI-SCI message content: value): Target Value: 0x00000001
0x6350E001: Power Management:         SET_LOCAL_RESET(Set Local Reset): PSC ID: 1 Power domain ID: 3 Enable(1)/Disable(0): 1
0x00C20200:   BasePort: Unknown Action: 0x03 MSG:0x020200
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x61800200: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x00000200
0x61C00009: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 9 Clock ID: 0
0x62000002: Power Management: MSG_PARAM_VAL(TI-SCI message content: value): Target Value: 0x00000002
0x62D02000: Power Management:                 PD_GET(Power Domain Get): PSC ID: 1 Power domain ID: 0 PD Usage Count: 8192
0x62D00015: Power Management:                 PD_GET(Power Domain Get): PSC ID: 1 Power domain ID: 0 PD Usage Count: 21
0x6410E000: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 1 Power domain ID: 3 Module Retention Count: 8192
0x64106001: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 1 Power domain ID: 1 Module Retention Count: 8193
0x62D02001: Power Management:                 PD_GET(Power Domain Get): PSC ID: 1 Power domain ID: 0 PD Usage Count: 8193
0x608000DA: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 218
0x60000009: Power Management:     DEVICE_ON(Device has been Turned ON): Device ID: 9
0x6390E000: Power Management:                   MODULE_GET(Module Get): PSC ID: 1 LPSC ID: 3 Module Use Count: 8192
0x63906001: Power Management:                   MODULE_GET(Module Get): PSC ID: 1 LPSC ID: 1 Module Use Count: 8193
0x00C20202:   BasePort: Unknown Action: 0x03 MSG:0x020202
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x61800202: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x00000202
0x61C00009: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 9 Clock ID: 0
0x62000000: Power Management: MSG_PARAM_VAL(TI-SCI message content: value): Target Value: 0x00000000
0x6350E000: Power Management:         SET_LOCAL_RESET(Set Local Reset): PSC ID: 1 Power domain ID: 3 Enable(1)/Disable(0): 0
0x00C2C001:   BasePort: Unknown Action: 0x03 MSG:0x02C001
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2010E:   BasePort: Unknown Action: 0x03 MSG:0x02010E
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x6180010E: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x0000010E
0x61C00409: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 9 Clock ID: 1
0x00C2C000:   BasePort: Unknown Action: 0x03 MSG:0x02C000
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2010C:   BasePort: Unknown Action: 0x03 MSG:0x02010C
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x6180010C: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x0000010C
0x61C00079: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 121 Clock ID: 0
0x612F7C85: Power Management: CLOCK_SET_RATE(Clock Frequency has been changed: significand * 2^Exponent Hz): Clock ID: 133 Clock Frequency{significand}: 95 Clock Frequency{Exponent}: 23
0x612F7C85: Power Management: CLOCK_SET_RATE(Clock Frequency has been changed: significand * 2^Exponent Hz): Clock ID: 133 Clock Frequency{significand}: 95 Clock Frequency{Exponent}: 23
0x00C2C400:   BasePort: Unknown Action: 0x03 MSG:0x02C400
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2C100:   BasePort: Unknown Action: 0x03 MSG:0x02C100
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2010E:   BasePort: Unknown Action: 0x03 MSG:0x02010E
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x6180010E: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x0000010E
0x61C00079: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 121 Clock ID: 0
0x00C2C000:   BasePort: Unknown Action: 0x03 MSG:0x02C000
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2010C:   BasePort: Unknown Action: 0x03 MSG:0x02010C
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x6180010C: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x0000010C
0x61C0007A: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 122 Clock ID: 0
0x612F7C85: Power Management: CLOCK_SET_RATE(Clock Frequency has been changed: significand * 2^Exponent Hz): Clock ID: 133 Clock Frequency{significand}: 95 Clock Frequency{Exponent}: 23
0x612F7C85: Power Management: CLOCK_SET_RATE(Clock Frequency has been changed: significand * 2^Exponent Hz): Clock ID: 133 Clock Frequency{significand}: 95 Clock Frequency{Exponent}: 23
0x00C2C400:   BasePort: Unknown Action: 0x03 MSG:0x02C400
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2C100:   BasePort: Unknown Action: 0x03 MSG:0x02C100
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2010E:   BasePort: Unknown Action: 0x03 MSG:0x02010E
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x6180010E: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x0000010E
0x61C0007A: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 122 Clock ID: 0
0x00C2C400:   BasePort: Unknown Action: 0x03 MSG:0x02C400
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2C401:   BasePort: Unknown Action: 0x03 MSG:0x02C401
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00409030:   BasePort: TISCI_MSG_RECEIVED(TISCI Message interrupt handled): Queue ID: 0 Message ID: 9030
0x00800023:   BasePort: TISCI_MSG_SENDER_HOST_ID(Message from secure host received): Queue ID: 0 Host ID: 35
0x00C20202:   BasePort: Unknown Action: 0x03 MSG:0x020202
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x61800202: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x00000202
0x61C0007A: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 122 Clock ID: 0
0x62000001: Power Management: MSG_PARAM_VAL(TI-SCI message content: value): Target Value: 0x00000001
0x63432001: Power Management:         SET_LOCAL_RESET(Set Local Reset): PSC ID: 0 Power domain ID: 12 Enable(1)/Disable(0): 1
0x00C20202:   BasePort: Unknown Action: 0x03 MSG:0x020202
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x61800202: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x00000202
0x61C00079: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 121 Clock ID: 0
0x62000001: Power Management: MSG_PARAM_VAL(TI-SCI message content: value): Target Value: 0x00000001
0x63430001: Power Management:         SET_LOCAL_RESET(Set Local Reset): PSC ID: 0 Power domain ID: 12 Enable(1)/Disable(0): 1
0x00C2C101:   BasePort: Unknown Action: 0x03 MSG:0x02C101
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2C001:   BasePort: Unknown Action: 0x03 MSG:0x02C001
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2C001:   BasePort: Unknown Action: 0x03 MSG:0x02C001
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C20202:   BasePort: Unknown Action: 0x03 MSG:0x020202
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x61800202: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x00000202
0x61C00079: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 121 Clock ID: 0
0x62000000: Power Management: MSG_PARAM_VAL(TI-SCI message content: value): Target Value: 0x00000000
0x63430000: Power Management:         SET_LOCAL_RESET(Set Local Reset): PSC ID: 0 Power domain ID: 12 Enable(1)/Disable(0): 0
0x00C20202:   BasePort: Unknown Action: 0x03 MSG:0x020202
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x61800202: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x00000202
0x61C0007A: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 122 Clock ID: 0
0x62000000: Power Management: MSG_PARAM_VAL(TI-SCI message content: value): Target Value: 0x00000000
0x63432000: Power Management:         SET_LOCAL_RESET(Set Local Reset): PSC ID: 0 Power domain ID: 12 Enable(1)/Disable(0): 0
0x00C2010E:   BasePort: Unknown Action: 0x03 MSG:0x02010E
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x6180010E: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x0000010E
0x61C00079: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 121 Clock ID: 0
0x00C2010E:   BasePort: Unknown Action: 0x03 MSG:0x02010E
0x00C20026:   BasePort: Unknown Action: 0x03 MSG:0x020026
0x6180010E: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x0000010E
0x61C0007A: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 122 Clock ID: 0
0x00C20201:   BasePort: Unknown Action: 0x03 MSG:0x020201
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x61800201: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x00000201
0x61C00092: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 146 Clock ID: 0
0x00C20101:   BasePort: Unknown Action: 0x03 MSG:0x020101
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x61800101: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x00000101
0x61C00092: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 146 Clock ID: 0
0x00C20104:   BasePort: Unknown Action: 0x03 MSG:0x020104
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x61800104: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x00000104
0x61C00092: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 146 Clock ID: 0
0x00C20103:   BasePort: Unknown Action: 0x03 MSG:0x020103
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x61800103: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x00000103
0x61C00092: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 146 Clock ID: 0
0x00C20100:   BasePort: Unknown Action: 0x03 MSG:0x020100
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x61800100: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x00000100
0x61C00092: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 146 Clock ID: 0
0x62000000: Power Management: MSG_PARAM_VAL(TI-SCI message content: value): Target Value: 0x00000000
0x00C20102:   BasePort: Unknown Action: 0x03 MSG:0x020102
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x61800102: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x00000102
0x61C00092: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 146 Clock ID: 0
0x62000001: Power Management: MSG_PARAM_VAL(TI-SCI message content: value): Target Value: 0x00000001
0x00C2010D:   BasePort: Unknown Action: 0x03 MSG:0x02010D
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x6180010D: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x0000010D
0x61C00092: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 146 Clock ID: 0
0x61276CB2: Power Management: CLOCK_SET_RATE(Clock Frequency has been changed: significand * 2^Exponent Hz): Clock ID: 178 Clock Frequency{significand}: 91 Clock Frequency{Exponent}: 19
0x00C2010C:   BasePort: Unknown Action: 0x03 MSG:0x02010C
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x6180010C: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x0000010C
0x61C00092: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 146 Clock ID: 0
0x61276CB2: Power Management: CLOCK_SET_RATE(Clock Frequency has been changed: significand * 2^Exponent Hz): Clock ID: 178 Clock Frequency{significand}: 91 Clock Frequency{Exponent}: 19
0x61276CB2: Power Management: CLOCK_SET_RATE(Clock Frequency has been changed: significand * 2^Exponent Hz): Clock ID: 178 Clock Frequency{significand}: 91 Clock Frequency{Exponent}: 19
0x00C20201:   BasePort: Unknown Action: 0x03 MSG:0x020201
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x61800201: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x00000201
0x61C00092: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 146 Clock ID: 0
0x00C20200:   BasePort: Unknown Action: 0x03 MSG:0x020200
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x61800200: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x00000200
0x61C00092: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 146 Clock ID: 0
0x62000000: Power Management: MSG_PARAM_VAL(TI-SCI message content: value): Target Value: 0x00000000
0x60400092: Power Management:   DEVICE_OFF(Device has been Turned OFF): Device ID: 146
0x63C0004F: Power Management:                   MODULE_PUT(Module Put): PSC ID: 0 LPSC ID: 0 Module Use Count: 79
0x6440004F: Power Management:             RETENTION_PUT(Retention Put): LPSC ID: 0 Power domain ID: 0 Module Retention Count: 79
0x6300005C: Power Management:                 PD_PUT(Power Domain Put): PSC ID: 0 Power domain ID: 0 PD Usage Count: 92

0 Prashant Shivhare 5 months ago in reply to Petr Kucera

TI__Guru 68771 points

Hello,

These logs suggests the SYSFW version is 10.0.8 instead of the provided hotfix version.

If the hotfix SYSFW version is used, you would get the version like so:

0x04003007:   BasePort: TRACE_DATA_VERSION(OSAL/Baseport trace data version): Trace version major: 0x03 Trace version minor: 0x007
0x04400A18:   BasePort:   SYSFW_VERSION(System Firmware version): version: 10 subversion: 1 patch: 8

Please make sure you are using the provided hotfix SYSFW version.

Thanks!

0 Petr Kucera 5 months ago in reply to Prashant Shivhare

Prodigy 172 points

Thanks, I used provided binary and get this log with new information about SEC_BOOT.

Configuring trace data version to: 0x03007
9002
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29000:   BasePort: Unknown Action: 0x03 MSG:0x029000
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29002:   BasePort: Unknown Action: 0x03 MSG:0x029002
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29000:   BasePort: Unknown Action: 0x03 MSG:0x029000
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29002:   BasePort: Unknown Action: 0x03 MSG:0x029002
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29000:   BasePort: Unknown Action: 0x03 MSG:0x029000
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29002:   BasePort: Unknown Action: 0x03 MSG:0x029002
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29000:   BasePort: Unknown Action: 0x03 MSG:0x029000
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29002:   BasePort: Unknown Action: 0x03 MSG:0x029002
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29000:   BasePort: Unknown Action: 0x03 MSG:0x029000
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29002:   BasePort: Unknown Action: 0x03 MSG:0x029002
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29000:   BasePort: Unknown Action: 0x03 MSG:0x029000
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29002:   BasePort: Unknown Action: 0x03 MSG:0x029002
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29000:   BasePort: Unknown Action: 0x03 MSG:0x029000
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29002:   BasePort: Unknown Action: 0x03 MSG:0x029002
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C29000:   BasePort: Unknown Action: 0x03 MSG:0x029000
0xC200240xC20002
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x04003007:   BasePort: TRACE_DATA_VERSION(OSAL/Baseport trace data version): Trace version major: 0x03 Trace version minor: 0x007
0x04400A18:   BasePort:   SYSFW_VERSION(System Firmware version): version: 10 subversion: 1 patch: 8
0x00C2C000:   BasePort: Unknown Action: 0x03 MSG:0x02C000
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2010C:   BasePort: Unknown Action: 0x03 MSG:0x02010C
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x6180010C: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x0000010C
0x61C0007B: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 123 Clock ID: 0
0x612F7C86: Power Management: CLOCK_SET_RATE(Clock Frequency has been changed: significand * 2^Exponent Hz): Clock ID: 134 Clock Frequency{significand}: 95 Clock Frequency{Exponent}: 23
0x612F7C86: Power Management: CLOCK_SET_RATE(Clock Frequency has been changed: significand * 2^Exponent Hz): Clock ID: 134 Clock Frequency{significand}: 95 Clock Frequency{Exponent}: 23
0x00C20200:   BasePort: Unknown Action: 0x03 MSG:0x020200
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x61800200: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x00000200
0x61C0007B: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 123 Clock ID: 0
0x62000000: Power Management: MSG_PARAM_VAL(TI-SCI message content: value): Target Value: 0x00000000
0x00C2C400:   BasePort: Unknown Action: 0x03 MSG:0x02C400
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2C400:   BasePort: Unknown Action: 0x03 MSG:0x02C400
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2C100:   BasePort: Unknown Action: 0x03 MSG:0x02C100
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2C101:   BasePort: Unknown Action: 0x03 MSG:0x02C101
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C20200:   BasePort: Unknown Action: 0x03 MSG:0x020200
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x61800200: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x00000200
0x61C0007B: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 123 Clock ID: 0
0x62000002: Power Management: MSG_PARAM_VAL(TI-SCI message content: value): Target Value: 0x00000002
0x62C0A000: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 2 PD Usage Count: 8192
0x62C0005B: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 0 PD Usage Count: 91
0x64036000: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 13 Module Retention Count: 8192
0x64006003: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 1 Module Retention Count: 8195
0x62C0A001: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 2 PD Usage Count: 8193
0x6000007B: Power Management:     DEVICE_ON(Device has been Turned ON): Device ID: 123
0x63836000: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 13 Module Use Count: 8192
0x63806003: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 1 Module Use Count: 8195
0x00C2C400:   BasePort: Unknown Action: 0x03 MSG:0x02C400
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2C100:   BasePort: Unknown Action: 0x03 MSG:0x02C100
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2C101:   BasePort: Unknown Action: 0x03 MSG:0x02C101
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2C001:   BasePort: Unknown Action: 0x03 MSG:0x02C001
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2010E:   BasePort: Unknown Action: 0x03 MSG:0x02010E
0x00C20029:   BasePort: Unknown Action: 0x03 MSG:0x020029
0x6180010E: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x0000010E
0x61C0007B: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 123 Clock ID: 0
0x00C2010E:   BasePort: Unknown Action: 0x03 MSG:0x02010E
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x6180010E: Power Management:    MSG_RECEIVED(TI-SCI message received): Message ID: 0x0000010E
0x61C0007B: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 123 Clock ID: 0
0x00C2C400:   BasePort: Unknown Action: 0x03 MSG:0x02C400
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x00C2C120:   BasePort: Unknown Action: 0x03 MSG:0x02C120
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x20C00004:   Security: SEC_BOOT(Points of failures during secure boot api call): 0x01 => Certificate length > ASN1P_IMAX, 0x02 => Issue fetching certificate, 0x3 => Issue with Hash operation, 0x4 => Hash comparison fails: 0

0 Prashant Shivhare 5 months ago in reply to Petr Kucera

TI__Guru 68771 points

The issue is still random, right?

Since you are working on TI board, could you please share all the images for me to try them locally and see if the issue reproduces?

Thanks!

0 Petr Kucera 5 months ago in reply to Prashant Shivhare

Prodigy 172 points

Shure, there is a zip file with binaries, sources and makefile.

ti_am243x_booting_debug.zip

0 Petr Kucera 5 months ago in reply to Petr Kucera

Prodigy 172 points

A few runs will be OK. Wait for more then 3 mins, do no to power off the device and reset it. After that device will crash on image auth. The red color will indicate problem, green success boot.

0 Prashant Shivhare 4 months ago in reply to Petr Kucera

TI__Guru 68771 points

Hello,

Could you please change the OSPI settings in SBL as shown in the image and see if the issues still occurs?

Thanks!

0 Petr Kucera 4 months ago in reply to Prashant Shivhare

Prodigy 172 points

Hi, I changed Input Clock Frequency to 100000000, Enable DMA and Enable PHY Mode as you mentioned, and problem disappeared. Thanks, but could you explain my what cause this error and how frequency, DMA, and PHY Mode solve it?

I try investigate the problem to understand your solution. I reduced changes to change Input Clock Frequency only and it solved the problem. But I can't still understand why? How it is connect with 3 min and why you suggested this clock value?

0 Prashant Shivhare 4 months ago in reply to Petr Kucera

TI__Guru 68771 points

Hello,

I am not the OSPI expert. I suggested those configurations based on the SBL_OSPI bootloader configurations. The only explanation I have is the SYSFW may fail to incorrectly read the image from OSPI if it is not configured correctly. This incorrect read then leads to the authentication failure.

BR, Prashant

0 Petr Kucera 4 months ago in reply to Prashant Shivhare

Prodigy 172 points

Thanks for arguments. In my opinion it can be caused by overheat, but it is only guessing. Thanks for your support and fixing our problem.

0 Prashant Shivhare 4 months ago in reply to Petr Kucera

TI__Guru 68771 points

Please note you should migrate to the latest release SDK that comes with the latest SYSFW.

https://www.ti.com/tool/download/MCU-PLUS-SDK-AM243X/11.00.00.15

If you can not migrate then you should integrate the SYSFW binaries from the latest SDK to your SDK version instead of using the hotfix ones I previously provided.

0 Petr Kucera 4 months ago in reply to Prashant Shivhare

Prodigy 172 points

Thanks, we will.

Arm-based microcontrollers

Arm-based microcontrollers forum

LP-AM243: Example resets after 3 mins