AM625: sbl boot cannot use the ipc function ？

Hello yu chai,

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

Regards,

S.Anil.

Hello yu chai,

For clarifying your question you should understand the below topics .

Please go through them.

Reset Isolation is a hardware mechanism used in multicore processors to isolate individual cores from one another. This allows each core to be reset independently, without affecting the operation of other cores in the system level. Reset isolation is crucial in a multicore processor as it helps to ensure the reliability and stability of the system.

Different types of isolations:

Partial Isolation:

1. It is possible to Monitor MCU Registers and MCU Peripherals from the MAIN Domain

 Full Isolation:

1. It is not possible to Monitor MCU Registers and MCU Peripherals from the MAIN Domain

Currently, in MCU+SDK, we support partial isolation, which means that only the reset path is isolated from the main domain and MCU peripherals can be accessed from the main domain or vice versa.

If MCU is configured in fully isolated mode, then the below understanding is correct.

yu chai said:

I noticed that the m-core manual mentioned that when the m-core runs independently, the peripherals and resources of the a-core cannot be used, including the ipc function. Would I like to confirm that this is true?

Can you please confirm if you are using MCU isolation software in your application?

yu chai said:

If so, the multinuclear heterogeneity loses its meaning. Will the problem be solved later? 

Sorry, I could not understand this point. Can you please briefly explain?

Regards,

S.Anil.

1 The m-core is commonly used as a protection and control function and does not want to receive the effect of an a A-core reset, so I do not know whether an a A-core reset can be achieved in sbl boot mode without affecting the m-core

2 If it can, then in sbl boot mode, I want to continue with ipc, is that ok? 

yu chai said:

The m-core is commonly used as a protection and control function and does not want to receive the effect of an a A-core reset, so I do not know whether an a A-core reset can be achieved in sbl boot mode without affecting the m-core

yu chai,

Based on the above point, you just wanted to isolate Reset from the M-core. So, in this case, there is no problem; you can still monitor all peripherals of the MCU domain from the main domain, or vice versa.

Please go through the below example for MCU core reset isolation.

C:\ti\mcu_plus_sdk_am62x_09_00_00_19\examples\drivers\safety\reset_isolation

Can you please explain what the use case of SBL here to better assist you ?

Regards,

S.Anil.

1 I want to keep the m4 core program free of the A 53 reset while retaining the ipc function. Can these two be achieved? 

I want to use the sbl boot mode because such that the A53 core no longer loads the m4 core so that the m4 core can separate from the effects of the A53 core

yu chai,

yu chai said:

1 I want to keep the m4 core program free of the A 53 reset while retaining the ipc function. Can these two be achieved? 

Based on the above point, I understand that you wanted to reset SOC after the IPC function is completed, and this reset is not propagated through M4.

Yes, this works and supports

yu chai said:

I want to use the sbl boot mode because such that the A53 core no longer loads the m4 core so that the m4 core can separate from the effects of the A53 core

if you use the sbl_ospi_linux boot mode, then SBL will skip loading the M4 core app image for every reset, and this is already taken care in the SBL.

Please look at the image below.

Regards,

S.Anil.

1 I use sbl ospi boot mode, m4 core burning the ipc_linux program and r5f core burning the ipc program. The m4, r5f, and A53 were initiated independently. 
2 When the reboot command is entered in the A53 cores, the m4 and r5 cores also restart. Did not reach the goal that the A53 cores reduction does not affect the operation of the m4 core .

3Please see the video for details on the operation process 

1 If I burn the 1 program safty-reset_isolation, although the a53 core reboot does not affect the m4 core, the ipc function is not available. Is that so? 

Hello yu chai,

For every 10 seconds, the R5F core initiates a warm reset; in this case, the A53 core and R5F will be reset, and the M4F core is still running.

Please try to explore these examples, and after that, you can add your ipc or other functions to the application.

yu chai said:

If I burn the 1 program safty-reset_isolation, although the a53 core reboot does not affect the m4 core, the ipc function is not available. Is that so? 

I am trying to understand the above point. You mean already, safety isolation examples are running, and when a reset operation is performed, the reset operation is not affected by the M4F core due to the fact that IPC functionality is not available. It is really confusing why IPC functionality is coming into the SBL every time. You don't need any IPC and already SBL code will take care to skip reinitializations of the M4F core for every reset in isolation, and the user no longer needs to create any IPC functionalities to run the M4F core without effecting the Reset operation.

Regards,

S.Anil.

1 I tested this programof safty-reset_isolation and it worked .

2 I wonder whether the ipc function will work properly on the basis of safe-reset_isolation? 

Hello yu chai,

Thanks for your reply .

yu chai said:

I wonder whether the ipc function will work properly on the basis of safe-reset_isolation? 

I understood that you wanted to enable ipc functionality in the Isolation software .

Please provide a reply to the below questions to better assist you.

Please tell me now if you want to transfer data between which cores. A53 to M4F, R5F to M4F, or vice versa?

Where are you adding IPC functionality in the SBL or application?

What is the use case here?

Regards,

S.Anil.

1  I want to transfer data from A53 to M4F, and from M4F to A53.
2 I didn t find this use case ,so I want to ask if enable ipc functionality in the isolation software?
3 In the official manual, it cannot be achieved simultaneously. So I want to confirm with you that the manual is correct.

4 If you say you can implement both ipc and safe-save _ isolation I can try modifying it

Hello yu chai,

Thanks for clarifying all my questions .

yu chai said:

3 In the official manual, it cannot be achieved simultaneously. So I want to confirm with you that the manual is correct.

This is not possible with the current isolation software. Please look at the image below.

I have highlighted below the yellow colors where bits are used to restrict cross-domain peripheral access.

So, you can't use ipc or access peripherals from MAIN to MCU or MCU to MAIN.

But, for your use case, you can keep the below bit as 0 instead of 1. So, reset isolation and ipc functionality should work.

pscMCU2MainDisable = 0;

Note: If you control this bit, it means your MCU domain is accessing the main domain and Reset is isolated.

If you want full isolation as the MCU domain can be configured as a safety controller , this bit should be 1.

Regards,

S.Anil.

ok! Later I ll write a program in your way and test it. If there is a problem. Let me create a new forum for the topic of the discussion.thanks again