AM6442: ISOLATED RESET

Berlam Karli

Part Number: AM6442

Tool/software:

Hello experts,

I am trying to test reset_isolation_ipc example in the last version of Mcu Sdk.

When I try the test code on EVM board, it works without any problems. But when I try it on my custom board , m4 core cannot pass the SOC_waitForFwlUnlock() function.
But the R5 core resets and starts running as expected.
My first question is which hardware difference can cause this problem?
My second question is, when I debugged the SBL code, I noticed that when I pass the Bootloader_socNotifyFirewallOpen() function, the m4 core still continues to read the magic number as 0.
When the SBL code runs out, m4 core can read magic number as expected and continues running. Which step of my r5 core allows that my m4 core to pass SOC_waitForFwlUnlock() function?

Thanks for your helps,

Regards.

over 2 years ago

0 Tushar Thakur over 2 years ago

TI__Guru 64038 points

Hello Berlam,

Thanks for your query.

Can you please tell us which MCU+SDK version are you using?

Regards,

Tushar

0 Berlam Karli over 2 years ago in reply to Tushar Thakur

Intellectual 340 points

Hello Tushar

Version 09.02.01.05

Regards,

0 Tushar Thakur over 2 years ago

TI__Guru 64038 points

Hello Berlam,

Thanks for sharing the above details.

Berlam Karli said:
When the SBL code runs out, m4 core can read magic number as expected and continues running. Which step of my r5 core allows that my m4 core to pass SOC_waitForFwlUnlock() function?

Thanks for your helps,

Regards.

In the SBL code we are opening the Firewall by using Bootloader_socOpenFirewalls() API and the same is notified to other core by calling Bootloader_socNotifyFirewallOpen() API. After this steps M4F would be able to pass the SOC_waitForFwlUnlock() function.

Regards,

Tushar

0 Berlam Karli over 2 years ago in reply to Tushar Thakur

Intellectual 340 points

Hello,

As i mentioned above, i see the magic number at 0x00000000 (psram) if i look memory browser from R5 core. But i cant see it from M4 core at 0x00000000 or 0x80000000 after Bootloader_socNotifyFirewallOpen() function.

0 Swargam Anil over 2 years ago in reply to Berlam Karli

TI__Guru 54928 points

Hello Berlam,

Berlam Karli said:
My first question is which hardware difference can cause this problem?

There is no HW dependency for this issue .

Can you please confirm you are trying to use any M4F domain peripherals from the MAIN domain with your customer Hw Test case?

Can you please confirm with the EVM how you did load examples ?

Either it is from CCS or flash ?

With the custom Hw, how did you load the examples from CCS or Flash ?

Regards,

Anil.

Processors

Processors forum

AM6442: ISOLATED RESET