AM2434: SecureBoot - appimage authentication fails - firewall configuration?

Mark Orkenyi

Part Number: AM2434

Tool/software:

Hi,
We're trying to test out Secureboot on our own hardware and platform. I managed to do successful tests on the LP-AM243x.

I ran into an issue where the signed (hs-se) SBL boots up, however it fails to boot the application.

By debugging we found that it fails at the following part:

Sciclient_procBootGetProcessorState

retVal = Sciclient_service(&reqParam, &respParam);
if((retVal != SystemP_SUCCESS) ||
    ((respParam.flags & TISCI_MSG_FLAG_ACK) != TISCI_MSG_FLAG_ACK))
{
    retVal = SystemP_FAILURE;
}
return retVal;

the return value of Sciclient_service is SystemP_SUCCESS, however the flags are not valid.

Our best guess at the moment is the firewall configuration.

Could you please provide an example or guide on how and with which parameters to configure the firewalls to enable image authentication?

As a side note, we also had to enable direct access on the OSPI, so that the bootloader can read the certificate from the flash directly.This was also not mentioned anywhere in the documentation.

Thanks,

Mark

over 1 year ago

0 Prashant Shivhare over 1 year ago

TI__Guru 70231 points

Hi Mark,

I am not able to connect the dots in your query.

You are mentioning about the image authentication failure but then reporting the issue occurs in Sciclient_procBootGetProcessorState. These two are not related. Could you please clarify the issue?

Regards,

Prashant

0 Mark Orkenyi over 1 year ago in reply to Prashant Shivhare

Prodigy 60 points

Hi Prashant,

My bad, I wrote the wrong function name, sorry for the confusion.
It's the Sciclient_procBootAuthAndStart()
Apart from that, it's the same code part.
Attached the call stack, that might help explain where i'm standing at.

Thanks,

Mark

0 Prashant Shivhare over 1 year ago in reply to Mark Orkenyi

TI__Guru 70231 points

Hi Mark,

Thanks for the clarification!!

Could you please enable and share the Sysfw logs? This should give us the reason of authentication failure.

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 Mark Orkenyi over 1 year ago in reply to Prashant Shivhare

Prodigy 60 points

Hi Prashant,

Thanks, I'm using our own hardware and platform with another toolchain, so I will need some time to do this.

Is there any way to get those sysfw logs into the terminal in CCS through the XDS110?

Mark

0 Prashant Shivhare over 1 year ago in reply to Mark Orkenyi

TI__Guru 70231 points

Hi Mark,

Changing and rebuilding the board configuration is necessary. As for the UART, you may collect the logs from Memory Buffer also as described here

https://software-dl.ti.com/tisci/esd/latest/4_trace/trace.html#trace-memory-buffer-location

Regards,

Prashant

0 Mark Orkenyi over 1 year ago in reply to Prashant Shivhare

Prodigy 60 points

Hi Prashant,

Unfortunately I don't have UART1 routed out, so can't access that. I enabled the SYSFW_TRACE_ENABLE macro, powered up the board, I can see the data in the memory browser, (0x44043000 for am243x if I'm right), but how to parse that?
I found a sysfw trace parser script in the sdk, but it is not parsing that dat file.
Could you please help to understand that log?

Mark
memdump.dat

0 Prashant Shivhare over 1 year ago in reply to Mark Orkenyi

TI__Guru 70231 points

Hi Mark,

I think you have saved the data using CCS in "TI RAW" something format. Could you instead save the data as binary?

If in doubt, you can just simply include this function and call after the Bootloader_parseMulticoreAppimage function in the SBL's main file. This function reads the logs from the memory and dumps it on the same UART as the normal logs.

void dump_tifs_logs()
{
    #define TIFS_LOGS_BUFFER_ADDR 0x44043000
    #define TIFS_LOGS_BUFFER_SIZE 0x0FE0

    uint8_t* ptr = (uint8_t*)TIFS_LOGS_BUFFER_ADDR;

    DebugP_log("\r\n<<TIFS_LOGS\r\n");

    for(int32_t i = 0; i < TIFS_LOGS_BUFFER_SIZE; i++)
    {
        DebugP_log("%c", *ptr);
        ptr++;
    }

    DebugP_log("\r\nTIFS_LOGS\r\n");
}

Regards,

Prashant

0 Mark Orkenyi over 1 year ago in reply to Prashant Shivhare

Prodigy 60 points

Hi,

Thanks for the quick reply!
Yes, saving it as binary worked. I've attached the logs, but based on that I guess the cause of failure is: "Issue with Hash operation"

Unfortunately I don't understand what this means, could you please provide more context about this message?

Fullscreen 4442.out.txt Download

Configuring trace data version to: 0x03007
x4F80001A
0x4380001A: Resource Management: UDMAP_TX_CH_CFG(NavSS UDMAP TX channel configuration): UDMA device ID: 26
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
0x61C0008D: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 141 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
0x61C00050: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 80 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
0x61C00050: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 80 Clock ID: 0
0x62000002: Power Management: MSG_PARAM_VAL(TI-SCI message content: value): Target Value: 0x00000002
0x62C0005B: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 0 PD Usage Count: 91
0x64024000: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 9 Module Retention Count: 0
0x6400C003: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 3 Module Retention Count: 3
0x62C0005C: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 0 PD Usage Count: 92
0x60000050: Power Management:     DEVICE_ON(Device has been Turned ON): Device ID: 80
0x63824000: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 9 Module Use Count: 0
0x6380C003: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 3 Module Use Count: 3
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
0x61C00050: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 80 Clock ID: 0
0x62000000: Power Management: MSG_PARAM_VAL(TI-SCI message content: value): Target Value: 0x00000000
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
0x61C00037: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 55 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
0x61C00037: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 55 Clock ID: 0
0x62000002: Power Management: MSG_PARAM_VAL(TI-SCI message content: value): Target Value: 0x00000002
0x62C0005D: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 0 PD Usage Count: 93
0x6402C000: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 11 Module Retention Count: 0
0x64028000: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 10 Module Retention Count: 0
0x6400C004: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 3 Module Retention Count: 4
0x62C0005E: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 0 PD Usage Count: 94
0x62C0005F: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 0 PD Usage Count: 95
0x60000037: Power Management:     DEVICE_ON(Device has been Turned ON): Device ID: 55
0x6382C000: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 11 Module Use Count: 0
0x63828000: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 10 Module Use Count: 0
0x6380C004: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 3 Module Use Count: 4
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
0x61C00037: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 55 Clock ID: 0
0x62000000: Power Management: MSG_PARAM_VAL(TI-SCI message content: value): Target Value: 0x00000000
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
0x61C0008A: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 138 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
0x61C0008A: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 138 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
0x61C0008A: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 138 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
0x61C0008A: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 138 Clock ID: 0
0x62000000: Power Management: MSG_PARAM_VAL(TI-SCI message content: value): Target Value: 0x00000000
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
0x61C0008A: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 138 Clock ID: 0
0x612D7C83: Power Management: CLOCK_SET_RATE(Clock Frequency has been changed: significand * 2^Exponent Hz): Clock ID: 131 Clock Frequency{significand}: 95 Clock Frequency{Exponent}: 22
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
0x61C0008A: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 138 Clock ID: 0
0x612D7C83: Power Management: CLOCK_SET_RATE(Clock Frequency has been changed: significand * 2^Exponent Hz): Clock ID: 131 Clock Frequency{significand}: 95 Clock Frequency{Exponent}: 22
0x612D7C83: Power Management: CLOCK_SET_RATE(Clock Frequency has been changed: significand * 2^Exponent Hz): Clock ID: 131 Clock Frequency{significand}: 95 Clock Frequency{Exponent}: 22
0x00C20002:   BasePort: Unknown Action: 0x03 MSG:0x020002
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
0x04400916:   BasePort:   SYSFW_VERSION(System Firmware version): version: 9 subversion: 1 patch: 6
0x00C20002:   BasePort: Unknown Action: 0x03 MSG:0x020002
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
0x04400916:   BasePort:   SYSFW_VERSION(System Firmware version): version: 9 subversion: 1 patch: 6
0x00C2C120:   BasePort: Unknown Action: 0x03 MSG:0x02C120
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x20C00003:   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: 3
0x00C2C120:   BasePort: Unknown Action: 0x03 MSG:0x02C120
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x20C00003:   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: 3
0x00C2C120:   BasePort: Unknown Action: 0x03 MSG:0x02C120
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x20C00003:   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: 3
000
0x62C0004C: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 0 PD Usage Count: 76
0x6380C003: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 3 Module Use Count: 3
0x6400C003: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 3 Module Retention Count: 3
0x63820003: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 8 Module Use Count: 3
0x64020003: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 8 Module Retention Count: 3
0x63838001: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 14 Module Use Count: 1
0x64038001: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 14 Module Retention Count: 1
0x63860003: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 24 Module Use Count: 3
0x64060003: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 24 Module Retention Count: 3
0x63864002: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 25 Module Use Count: 2
0x64064002: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 25 Module Retention Count: 2
0x6300004D: Power Management:                 PD_PUT(Power Domain Put): PSC ID: 0 Power domain ID: 0 PD Usage Count: 77
0x63010007: Power Management:                 PD_PUT(Power Domain Put): PSC ID: 0 Power domain ID: 4 PD Usage Count: 7
0x63018001: Power Management:                 PD_PUT(Power Domain Put): PSC ID: 0 Power domain ID: 6 PD Usage Count: 1
0x6301C001: Power Management:                 PD_PUT(Power Domain Put): PSC ID: 0 Power domain ID: 7 PD Usage Count: 1
0x63024001: Power Management:                 PD_PUT(Power Domain Put): PSC ID: 0 Power domain ID: 9 PD Usage Count: 1
0x6000008C: Power Management:     DEVICE_ON(Device has been Turned ON): Device ID: 140
0x6390000B: Power Management:                   MODULE_GET(Module Get): PSC ID: 1 LPSC ID: 0 Module Use Count: 11
0x6410000B: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 1 Power domain ID: 0 Module Retention Count: 11
0x63908000: Power Management:                   MODULE_GET(Module Get): PSC ID: 1 LPSC ID: 2 Module Use Count: 0
0x64108000: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 1 Power domain ID: 2 Module Retention Count: 0
0x63904001: Power Management:                   MODULE_GET(Module Get): PSC ID: 1 LPSC ID: 1 Module Use Count: 1
0x64104001: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 1 Power domain ID: 1 Module Retention Count: 1
0x62D00012: Power Management:                 PD_GET(Power Domain Get): PSC ID: 1 Power domain ID: 0 PD Usage Count: 18
0x6390C001: Power Management:                   MODULE_GET(Module Get): PSC ID: 1 LPSC ID: 3 Module Use Count: 1
0x6410C001: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 1 Power domain ID: 3 Module Retention Count: 1
0x63910001: Power Management:                   MODULE_GET(Module Get): PSC ID: 1 LPSC ID: 4 Module Use Count: 1
0x64110001: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 1 Power domain ID: 4 Module Retention Count: 1
0x63100013: Power Management:                 PD_PUT(Power Domain Put): PSC ID: 1 Power domain ID: 0 PD Usage Count: 19
0x60800024: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 36
0x6080007E: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 126
0x60800064: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 100
0x6000008D: Power Management:     DEVICE_ON(Device has been Turned ON): Device ID: 141
0x63800042: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 0 Module Use Count: 66
0x62C0004C: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 0 PD Usage Count: 76
0x64000042: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 0 Module Retention Count: 66
0x60800025: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 37
0x6080007F: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 127
0x60800065: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 101
0x6000008E: Power Management:     DEVICE_ON(Device has been Turned ON): Device ID: 142
0x63800043: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 0 Module Use Count: 67
0x62C0004D: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 0 PD Usage Count: 77
0x64000043: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 0 Module Retention Count: 67
0x60800026: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 38
0x60800080: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 128
0x60800066: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 102
0x6000008F: Power Management:     DEVICE_ON(Device has been Turned ON): Device ID: 143
0x63800044: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 0 Module Use Count: 68
0x62C0004E: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 0 PD Usage Count: 78
0x64000044: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 0 Module Retention Count: 68
0x60800027: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 39
0x60800081: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 129
0x60800067: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 103
0x60000090: Power Management:     DEVICE_ON(Device has been Turned ON): Device ID: 144
0x63800045: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 0 Module Use Count: 69
0x62C0004F: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 0 PD Usage Count: 79
0x64000045: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 0 Module Retention Count: 69
0x60800028: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 40
0x60800082: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 130
0x60800068: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 104
0x60000091: Power Management:     DEVICE_ON(Device has been Turned ON): Device ID: 145
0x63800046: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 0 Module Use Count: 70
0x62C00050: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 0 PD Usage Count: 80
0x64000046: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 0 Module Retention Count: 70
0x608000B2: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 178
0x608000B9: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 185
0x60000092: Power Management:     DEVICE_ON(Device has been Turned ON): Device ID: 146
0x63800047: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 0 Module Use Count: 71
0x62C00051: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 0 PD Usage Count: 81
0x64000047: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 0 Module Retention Count: 71
0x608000C5: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 197
0x608000D1: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 209
0x608000CF: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 207
0x60000093: Power Management:     DEVICE_ON(Device has been Turned ON): Device ID: 147
0x6390000C: Power Management:                   MODULE_GET(Module Get): PSC ID: 1 LPSC ID: 0 Module Use Count: 12
0x62D00012: Power Management:                 PD_GET(Power Domain Get): PSC ID: 1 Power domain ID: 0 PD Usage Count: 18
0x6410000C: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 1 Power domain ID: 0 Module Retention Count: 12
0x608000C6: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 198
0x608000D2: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 210
0x608000D0: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 208
0x60000094: Power Management:     DEVICE_ON(Device has been Turned ON): Device ID: 148
0x6390000D: Power Management:                   MODULE_GET(Module Get): PSC ID: 1 LPSC ID: 0 Module Use Count: 13
0x62D00013: Power Management:                 PD_GET(Power Domain Get): PSC ID: 1 Power domain ID: 0 PD Usage Count: 19
0x6410000D: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 1 Power domain ID: 0 Module Retention Count: 13
0x60000095: Power Management:     DEVICE_ON(Device has been Turned ON): Device ID: 149
0x6390000E: Power Management:                   MODULE_GET(Module Get): PSC ID: 1 LPSC ID: 0 Module Use Count: 14
0x62D00014: Power Management:                 PD_GET(Power Domain Get): PSC ID: 1 Power domain ID: 0 PD Usage Count: 20
0x6410000E: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 1 Power domain ID: 0 Module Retention Count: 14
0x60000096: Power Management:     DEVICE_ON(Device has been Turned ON): Device ID: 150
0x63800048: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 0 Module Use Count: 72
0x62C00052: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 0 PD Usage Count: 82
0x64000048: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 0 Module Retention Count: 72
0x60000097: Power Management:     DEVICE_ON(Device has been Turned ON): Device ID: 151
0x63800049: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 0 Module Use Count: 73
0x62C00053: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 0 PD Usage Count: 83
0x64000049: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 0 Module Retention Count: 73
0x608000B3: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 179
0x608000BA: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 186
0x60000098: Power Management:     DEVICE_ON(Device has been Turned ON): Device ID: 152
0x6380004A: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 0 Module Use Count: 74
0x62C00054: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 0 PD Usage Count: 84
0x6400004A: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 0 Module Retention Count: 74
0x608000B4: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 180
0x608000BB: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 187
0x60000099: Power Management:     DEVICE_ON(Device has been Turned ON): Device ID: 153
0x6380004B: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 0 Module Use Count: 75
0x62C00055: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 0 PD Usage Count: 85
0x6400004B: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 0 Module Retention Count: 75
0x608000B5: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 181
0x608000BC: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 188
0x6000009A: Power Management:     DEVICE_ON(Device has been Turned ON): Device ID: 154
0x6380004C: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 0 Module Use Count: 76
0x62C00056: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 0 PD Usage Count: 86
0x6400004C: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 0 Module Retention Count: 76
0x608000B6: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 182
0x608000BD: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 189
0x6000009B: Power Management:     DEVICE_ON(Device has been Turned ON): Device ID: 155
0x6380004D: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 0 Module Use Count: 77
0x62C00057: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 0 PD Usage Count: 87
0x6400004D: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 0 Module Retention Count: 77
0x608000B7: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 183
0x608000BE: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 190
0x6000009C: Power Management:     DEVICE_ON(Device has been Turned ON): Device ID: 156
0x6380004E: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 0 Module Use Count: 78
0x62C00058: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 0 PD Usage Count: 88
0x6400004E: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 0 Module Retention Count: 78
0x6080003E: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 62
0x608000DB: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 219
0x608000E0: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 224
0x608000E1: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 225
0x6080003A: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 58
0x608000C1: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 193
0x608000CD: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 205
0x60800040: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 64
0x60800041: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 65
0x60800042: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 66
0x60800043: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 67
0x60800044: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 68
0x60800045: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 69
0x6080002C: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 44
0x6080002D: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 45
0x60800005: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 5
0x6080000D: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 13
0x60800014: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 20
0x60800016: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 22
0x60800018: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 24
0x6080001A: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 26
0x6080001C: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 28
0x6080001E: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 30
0x60800020: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 32
0x60800021: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 33
0x60800022: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 34
0x608000C0: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 192
0x6000009D: Power Management:     DEVICE_ON(Device has been Turned ON): Device ID: 157
0x608000B8: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 184
0x608000BF: Power Management:   CLOCK_ENABLE(Clock has been Turned ON): Clock ID: 191
0x6000009E: Power Management:     DEVICE_ON(Device has been Turned ON): Device ID: 158
0x6380004F: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 0 Module Use Count: 79
0x62C00059: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 0 PD Usage Count: 89
0x6400004F: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 0 Module Retention Count: 79
0x600000A0: Power Management:     DEVICE_ON(Device has been Turned ON): Device ID: 160
0x6390000F: Power Management:                   MODULE_GET(Module Get): PSC ID: 1 LPSC ID: 0 Module Use Count: 15
0x62D00015: Power Management:                 PD_GET(Power Domain Get): PSC ID: 1 Power domain ID: 0 PD Usage Count: 21
0x6410000F: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 1 Power domain ID: 0 Module Retention Count: 15
0x600000A3: Power Management:     DEVICE_ON(Device has been Turned ON): Device ID: 163
0x63808001: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 2 Module Use Count: 1
0x62C0005A: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 0 PD Usage Count: 90
0x64008001: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 2 Module Retention Count: 1
0x600000A4: Power Management:     DEVICE_ON(Device has been Turned ON): Device ID: 164
0x63808002: Power Management:                   MODULE_GET(Module Get): PSC ID: 0 LPSC ID: 2 Module Use Count: 2
0x62C0005B: Power Management:                 PD_GET(Power Domain Get): PSC ID: 0 Power domain ID: 0 PD Usage Count: 91
0x64008002: Power Management:             RETENTION_GET(Retention Get): LPSC ID: 0 Power domain ID: 2 Module Retention Count: 2
0x63D00010: Power Management:                   MODULE_PUT(Module Put): PSC ID: 1 LPSC ID: 0 Module Use Count: 16
0x64500010: Power Management:             RETENTION_PUT(Retention Put): LPSC ID: 1 Power domain ID: 0 Module Retention Count: 16
0x63D08001: Power Management:                   MODULE_PUT(Module Put): PSC ID: 1 LPSC ID: 2 Module Use Count: 1
0x63D04002: Power Management:                   MODULE_PUT(Module Put): PSC ID: 1 LPSC ID: 1 Module Use Count: 2
0x64508001: Power Management:             RETENTION_PUT(Retention Put): LPSC ID: 1 Power domain ID: 2 Module Retention Count: 1
0x63100016: Power Management:                 PD_PUT(Power Domain Put): PSC ID: 1 Power domain ID: 0 PD Usage Count: 22
0x64504002: Power Management:             RETENTION_PUT(Retention Put): LPSC ID: 1 Power domain ID: 1 Module Retention Count: 2
0x63D0C002: Power Management:                   MODULE_PUT(Module Put): PSC ID: 1 LPSC ID: 3 Module Use Count: 2
0x6450C002: Power Management:             RETENTION_PUT(Retention Put): LPSC ID: 1 Power domain ID: 3 Module Retention Count: 2
0x63D10002: Power Management:                   MODULE_PUT(Module Put): PSC ID: 1 LPSC ID: 4 Module Use Count: 2
0x64510002: Power Management:             RETENTION_PUT(Retention Put): LPSC ID: 1 Power domain ID: 4 Module Retention Count: 2
0x63C00050: Power Management:                   MODULE_PUT(Module Put): PSC ID: 0 LPSC ID: 0 Module Use Count: 80
0x64400050: Power Management:             RETENTION_PUT(Retention Put): LPSC ID: 0 Power domain ID: 0 Module Retention Count: 80
0x04003007:   BasePort: TRACE_DATA_VERSION(OSAL/Baseport trace data version): Trace version major: 0x03 Trace version minor: 0x007
0x04400916:   BasePort:   SYSFW_VERSION(System Firmware version): version: 9 subversion: 1 patch: 6
0x63C04001: Power Management:                   MODULE_PUT(Module Put): PSC ID: 0 LPSC ID: 1 Module Use Count: 1
0x64404001: Power Management:             RETENTION_PUT(Retention Put): LPSC ID: 0 Power domain ID: 1 Module Retention Count: 1
0x6300005C: Power Management:                 PD_PUT(Power Domain Put): PSC ID: 0 Power domain ID: 0 PD Usage Count: 92
0x63C08003: Power Management:                   MODULE_PUT(Module Put): PSC ID: 0 LPSC ID: 2 Module Use Count: 3
0x64408003: Power Management:             RETENTION_PUT(Retention Put): LPSC ID: 0 Power domain ID: 2 Module Retention Count: 3
0x63C0C004: Power Management:                   MODULE_PUT(Module Put): PSC ID: 0 LPSC ID: 3 Module Use Count: 4
0x6440C004: Power Management:             RETENTION_PUT(Retention Put): LPSC ID: 0 Power domain ID: 3 Module Retention Count: 4
0x63C20004: Power Management:                   MODULE_PUT(Module Put): PSC ID: 0 LPSC ID: 8 Module Use Count: 4
0x64420004: Power Management:             RETENTION_PUT(Retention Put): LPSC ID: 0 Power domain ID: 8 Module Retention Count: 4
0x63C38002: Power Management:                   MODULE_PUT(Module Put): PSC ID: 0 LPSC ID: 14 Module Use Count: 2
0x64438002: Power Management:             RETENTION_PUT(Retention Put): LPSC ID: 0 Power domain ID: 14 Module Retention Count: 2
0x63C60004: Power Management:                   MODULE_PUT(Module Put): PSC ID: 0 LPSC ID: 24 Module Use Count: 4
0x64460004: Power Management:             RETENTION_PUT(Retention Put): LPSC ID: 0 Power domain ID: 24 Module Retention Count: 4
0x63C64003: Power Management:                   MODULE_PUT(Module Put): PSC ID: 0 LPSC ID: 25 Module Use Count: 3
0x64464003: Power Management:             RETENTION_PUT(Retention Put): LPSC ID: 0 Power domain ID: 25 Module Retention Count: 3
0x68400000: Power Management: PM_DEV_INIT(Power Management device Initialization): Device ID: 0 error_code: 0
0x60C000A3: Power Management: CLOCK_DISABLE(Clock has been Turned OFF): Clock ID: 163
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
0x61C0184B: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 75 Clock ID: 6
0x62000007: Power Management: MSG_PARAM_VAL(TI-SCI message content: value): Target Value: 0x00000007
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
0x61C0184B: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 75 Clock ID: 6
0x612B7C88: Power Management: CLOCK_SET_RATE(Clock Frequency has been changed: significand * 2^Exponent Hz): Clock ID: 136 Clock Frequency{significand}: 95 Clock Frequency{Exponent}: 21
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
0x61C0184B: Power Management: MSG_PARAM_DEV_CLK_ID(TI-SCI message content: dev/clk-ids): Device ID: 75 Clock ID: 6
0x612B7C88: Power Management: CLOCK_SET_RATE(Clock Frequency has been changed: significand * 2^Exponent Hz): Clock ID: 136 Clock Frequency{significand}: 95 Clock Frequency{Exponent}: 21
0x612B7C88: Power Management: CLOCK_SET_RATE(Clock Frequency has been changed: significand * 2^Exponent Hz): Clock ID: 136 Clock Frequency{significand}: 95 Clock Frequency{Exponent}: 21
0x00C21110:   BasePort: Unknown Action: 0x03 MSG:0x021110
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x41070000: Resource Management:     RING_CONFIGURE(Configure NavSS ring): upper 16-bits of valid_params: 0x0000
0x410800BF: Resource Management:     RING_CONFIGURE(Configure NavSS ring): lower 16-bits of valid_params: 0x00BF
0x4F8A00FF: Resource Management: DEVGRP_VALIDATE(Validating device group of resource): Device group given in RM boardcfg message: 0x00FF
0x4F8B0001: Resource Management: DEVGRP_VALIDATE(Validating device group of resource): Device group of configured resource: 0x0001
0x4F80001A: Resource Management: DEVGRP_VALIDATE(Validating device group of resource): Device ID being validated: 26
0x4100001A: Resource Management:     RING_CONFIGURE(Configure NavSS ring): RA device ID: 26
0x4F01000C: Resource Management: RESASG_VALIDATE_RESOURCE(RM validate resource against board configuration): Resource index: 12
0x4F06068D: Resource Management: RESASG_VALIDATE_RESOURCE(RM validate resource against board configuration): Resource assignment utype: 0x068D
0x4F0A0024: Resource Management: RESASG_VALIDATE_RESOURCE(RM validate resource against board configuration): host: 36
0x4101000C: Resource Management:     RING_CONFIGURE(Configure NavSS ring): index: 12
0x410C0001: Resource Management:     RING_CONFIGURE(Configure NavSS ring): size: 1
0x410D7002: Resource Management:     RING_CONFIGURE(Configure NavSS ring): upper 16-bits of addr_lo: 0x7002
0x410E6800: Resource Management:     RING_CONFIGURE(Configure NavSS ring): lower 16-bits of addr_lo: 0x6800
0x410F0000: Resource Management:     RING_CONFIGURE(Configure NavSS ring): upper 4-bits of count: 0x0
0x41100001: Resource Management:     RING_CONFIGURE(Configure NavSS ring): lower 16-bits of count: 0x0001
0x41110000: Resource Management:     RING_CONFIGURE(Configure NavSS ring): order_id: 0
0x4F8A00FF: Resource Management: DEVGRP_VALIDATE(Validating device group of resource): Device group given in RM boardcfg message: 0x00FF
0x4F8B0001: Resource Management: DEVGRP_VALIDATE(Validating device group of resource): Device group of configured resource: 0x0001
0x4F80001A: Resource Management: DEVGRP_VALIDATE(Validating device group of resource): Device ID being validated: 26
0x4100001A: Resource Management:     RING_CONFIGURE(Configure NavSS ring): RA device ID: 26
0x4F8A00FF: Resource Management: DEVGRP_VALIDATE(Validating device group of resource): Device group given in RM boardcfg message: 0x00FF
0x4F8B0001: Resource Management: DEVGRP_VALIDATE(Validating device group of resource): Device group of configured resource: 0x0001
0x4F80001A: Resource Management: DEVGRP_VALIDATE(Validating device group of resource): Device ID being validated: 26
0x4100001A: Resource Management:     RING_CONFIGURE(Configure NavSS ring): RA device ID: 26
0x41070000: Resource Management:     RING_CONFIGURE(Configure NavSS ring): upper 16-bits of valid_params: 0x0000
0x410800BF: Resource Management:     RING_CONFIGURE(Configure NavSS ring): lower 16-bits of valid_params: 0x00BF
0x4F8A00FF: Resource Management: DEVGRP_VALIDATE(Validating device group of resource): Device group given in RM boardcfg message: 0x00FF
0x4F8B0001: Resource Management: DEVGRP_VALIDATE(Validating device group of resource): Device group of configured resource: 0x0001
0x4F80001A: Resource Management: DEVGRP_VALIDATE(Validating device group of resource): Device ID being validated: 26
0x4100001A: Resource Management:     RING_CONFIGURE(Configure NavSS ring): RA device ID: 26
0x00C21205:   BasePort: Unknown Action: 0x03 MSG:0x021205
0x00C20024:   BasePort: Unknown Action: 0x03 MSG:0x020024
0x43870001: Resource Management: UDMAP_TX_CH_CFG(NavSS UDMAP TX channel configuration): upper 16-bits of valid_params: 0x0001
0x43887FFF: Resource Management: UDMAP_TX_CH_CFG(NavSS UDMAP TX channel configuration): lower 16-bits of valid_params: 0x7FFF
0x4F8A00FF: Resource Management: DEVGRP_VALIDATE(Validating device group of resource): Device group given in RM boardcfg message: 0x00FF
0x4F8B0001: Resource Management: DEVGRP_VALIDATE(Validating device group of resource): Device group of configured resource: 0x0001
0x4F80001A: Resource Management: DEVGRP_VALIDATE(Validating device group of resource): Device ID being validated: 26
0x4380001A: Resource Management: UDMAP_TX_CH_CFG(NavSS UDMAP TX channel configuration): UDMA device ID: 26
0x4F01000C: Resource Management: RESASG_VALIDATE_RESOURCE(RM validate resource against board configuration): Resource index: 12
0x4F0606A0: Resource Management: RESASG_VALIDATE_RESOURCE(RM validate resource against board configuration): Resource assignment utype: 0x06A0
0x4F0A0024: Resource Management: RESASG_VALIDATE_RESOURCE(RM validate resource against board configuration): host: 36
0x4381000C: Resource Management: UDMAP_TX_CH_CFG(NavSS UDMAP TX channel configuration): index: 12
0x438A0000: Resource Management: UDMAP_TX_CH_CFG(NavSS UDMAP TX channel configuration): pause on error: 0
0x43A00000: Resource Management: UDMAP_TX_CH_CFG(NavSS UDMAP TX channel configuration): filter einfo: 0
0x43A10000: Resource Management: UDMAP_TX_CH_CFG(NavSS UDMAP TX channel configuration): filter pswords: 0
0x438B0000: Resource Management: UDMAP_TX_CH_CFG(NavSS UDMAP TX channel configuration): atype: 0
0x438C000C: Resource Management: UDMAP_TX_CH_CFG(NavSS UDMAP TX channel configuration): type: 12
0x43A20000: Resource Management: UDMAP_TX_CH_CFG(NavSS UDMAP TX channel configuration): teardown packet suppression: 0
0x438D0000: Resource Management: UDMAP_TX_CH_CFG(NavSS UDMAP TX channel configuration): fetch size: 0
0x43A30000: Resource Management: UDMAP_TX_CH_CFG(NavSS UDMAP TX channel configuration): credit count: 0
0x43A40000: Resource Management: UDMAP_TX_CH_CFG(NavSS UDMAP TX channel configuration): fdepth: 0
0x438F0004: Resource Management: UDMAP_TX_CH_CFG(NavSS UDMAP TX channel configuration): priority: 4
0x43900000: Resource Management: UDMAP_TX_CH_CFG(NavSS UDMAP TX channel configuration): QOS: 0
0x43910000: Resource Management: UDMAP_TX_CH_CFG(NavSS UDMAP TX channel configuration): order ID: 0
0x43920001: Resource Management: UDMAP_TX_CH_CFG(NavSS UDMAP TX channel configuration): scheduling priority: 1
0x439F0001: Resource Management: UDMAP_TX_CH_CFG(NavSS UDMAP TX channel configuration): burst size: 1
0x43A50000: Resource Management: UDMAP_TX_CH_CFG(NavSS UDMAP TX channel configuration): tdtype: 0
0x43A60001: Resource Management: UDMAP_TX_CH_CFG(NavSS UDMAP TX channel configuration): extended_ch_type: 1
0x4F8A00FF: Resource Management: DEVGRP_VALIDATE(Validating device group of resource): Device group given in RM boardcfg message: 0x00FF
0x4F8B0001: Resource Management: DEVGRP_VALIDATE(Validating device group of resource): Device group of configured resource: 0x0001
0

Mark

0 Prashant Shivhare over 1 year ago in reply to Mark Orkenyi

TI__Guru 70231 points

Hi Mark,

Mark Orkenyi said:
I guess the cause of failure is: "Issue with Hash operation"

This seems to be some internal issue with the SA2UL probably it getting timed out or something.

Are you seeing this issue on each reset or just randomly? If it is the former then it is possible something is wrong with the way flash is configured otherwise the debugging is gonna be complex.

On another note, why are there three PROC_AUTH_BOOT messages? And so much processing after the those messages?

Regards,

Prashant

0 Mark Orkenyi over 1 year ago in reply to Prashant Shivhare

Prodigy 60 points

Hi,

"This seems to be some internal issue with the SA2UL probably it getting timed out or something."
I had worked with SA2UL previously and for that I had to separately configure firewalls. So my original question remains, what are the required firewall configuration for authentication to work?

"Are you seeing this issue on each reset or just randomly? "

It's happening every time. the application never starts.

"On another note, why are there three PROC_AUTH_BOOT messages? And so much processing after the those messages?"

I have no idea. We are creating the appimage with the multicoreImageGen.js out of rprc's. (script is provided in the sdk)
This is working fine if authentication is not enabled.

Mark

0 Prashant Shivhare over 1 year ago in reply to Mark Orkenyi

TI__Guru 70231 points

Mark Orkenyi said:
I had worked with SA2UL previously and for that I had to separately configure firewalls. So my original question remains, what are the required firewall configuration for authentication to work?

The System Firmware owns the SA2UL and has full access to it so this should not be a firewall issue.

Mark Orkenyi said:
It's happening every time. the application never starts.

I am suspecting something wrong with with flash.

What is the size of the appimage being authenticated? And do you have any RAM large enough on the board where we could read the image from flash and then request for authentication. If it is successful, this should strongly mean something wrong with the reading from flash in DAC mode by Sysfw.

Mark Orkenyi said:
I have no idea. We are creating the appimage with the multicoreImageGen.js out of rprc's. (script is provided in the sdk)

If there is only one appimage being booted then there should be only one PROC_AUTH_BOOT message in the logs. Could you once evaluate why the Bootloader_socAuthImage is being three times if there is only one appimage?

Regards,

Prashant

0 Mark Orkenyi over 1 year ago in reply to Prashant Shivhare

Prodigy 60 points

Hi Prashant,

Prashant Shivhare said:
Could you once evaluate why the Bootloader_socAuthImage is being three times if there is only one appimage?

We're using our own bootloader based on the sbl_ospi one, and the 3 PROC_AUTH_BOOT messages were caused by our modifications. Fixed that, but of course it's not the cause.

Prashant Shivhare said:
What is the size of the appimage being authenticated? And do you have any RAM large enough on the board where we could read the image from flash and then request for authentication. If it is successful, this should strongly mean something wrong with the reading from flash in DAC mode by Sysfw.

Yes, the image can fit into PSRAM, so i'm currently trying to test that out. I will get back once I have more info.

Thanks for the support!

Mark

0 Prashant Shivhare over 1 year ago in reply to Mark Orkenyi

TI__Guru 70231 points

Hi Mark,

Mark Orkenyi said:
Yes, the image can fit into PSRAM, so i'm currently trying to test that out. I will get back once I have more info.

Sure. Let me know if any help is needed!!

Regards,

Prashant

0 Mark Orkenyi over 1 year ago in reply to Prashant Shivhare

Prodigy 60 points

Hi Prashant,

I was able to move the image to PSRAM, then modify our bootloader to use that address for authenticating the image. It was successful this way and the image booted afterwards.

So I assume based on your comment that it might a flash-related issue. We are using an OSPI flash.

Do you have any idea what to check or what could be the cause of this issue and how to solve it?

Thanks,

Mark

0 Prashant Shivhare over 1 year ago in reply to Mark Orkenyi

TI__Guru 70231 points

Hi Mark,

Mark Orkenyi said:
Do you have any idea what to check or what could be the cause of this issue and how to solve it?

Are you already running the flash at its maximum configurations like PHY enables, running at maximum clock, protocol 8D-8D-8D, etc.

Also, I hope you have DAC enabled throughtout the bootloader driver so that the SYSFW could do memory mapped reads to OSPI. This actually is a known bug and will be fixed in the next release v10.0.

am64x, am243x: bootloader: Fix DAC mode not enabled in ospi bootloaders · TexasInstruments/mcupsdk-core@82faf8f · GitHub

Regards,

Prashant

Arm-based microcontrollers

Arm-based microcontrollers forum

AM2434: SecureBoot - appimage authentication fails - firewall configuration?