TDA4VM: Questions about LPM mcu only mode

sui guoqing

Prodigy 180 points

Part Number: TDA4VM

Tool/software:

Hi,TI

5.24.1. MCU Only mode — Platform Development Kit (PDK) - JACINTO User Guide

I referred to this demo and conducted some tests on mcu1_0. There are some issues that require your help.

1.I called the Sciclient_service in mcu1_0 to reset the MAIN domain, expecting that mcu1_0 could continue to run. However, in reality, both the A core and mcu1_0 got stuck. Why was this so?

2.When I was migrating the PMIC from the ACTIVE state to the MCU only state, after writing to the FSM_NSLEEP_TRIGGERS register, I expected MCU1_0 to continue running. However, the phenomenon was that both MCU1_0 and A and got stuck. Please help analyze the reason.

3.The current startup mode we are using is SPL. To implement the MCU only mode and be able to switch back to the ACTIVE mode, can the startup mode of SPL be achieved? Are there any relevant reference materials?

I see that the startup mode used in the current demo is SBL, and when switching from mcu only mode to active mode, pulling up other core parts of the main domain again is missing

Regards,

Sui

2 months ago

0 Gibbs Shih 2 months ago

TI__Expert 5245 points

Hi, Dear Expert

Could we have your suggestion?

System Firmware (SYSFW) components runs on MCU 1_0 (MCUSS), I think it should be keep running even in MCU only mode.

https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/08_04_00_06/exports/docs/psdk_rtos/docs/user_guide/developer_notes_mcu1_0_sysfw.html?highlight=mcu

Should we miss any code for reset isolation between MCU/Main domain?

Thank You Very Much

Gibbs

0 sui guoqing 2 months ago in reply to Gibbs Shih

Prodigy 180 points

Hi,Dear Expert

I have discovered the following two problems:

1.When device_disable is called and dev is j721e_dev_ddr32ss_16ffc_ew_dv_wrap_main_0, MCU1_0 will enter HwiP_undefined_handler_c.

2. So I shielded and turned off j721e_dev_ddr32ss_16ffc_ew_dv_wrap_main_0, and continued the test. When soc_device_disable was called to disable WKUPMCU2MAIN bridge, MCU1_0 would enter HwiP_data_abort_handler.

Please also help analyze the reasons for the above two issues. Thank you very much.

Regards,

Sui

0 Karthikeyan S 2 months ago in reply to sui guoqing

TI__Genius 13170 points

Hi Sui,

sui guoqing said:
Please also help analyze the reasons for the above two issues. Thank you very much.

Could you please conform are you able to any get log from R5 Cores, if yes can you please share me the RTOS and Linux logs.

Regards,

Karthik

0 sui guoqing 2 months ago in reply to Karthikeyan S

Prodigy 180 points

Hi Karthik,

The log is as follows.

/cfs-file/__key/communityserver-discussions-components-files/791/2437.log.zip

The problems encountered above are those that occurred when the lpm sample code in pdk was transplanted into our code for operation.

Currently, in mcu1_0,ipc is not initialized.

Regarding the above-mentioned issue of closing the ddr device to enter undefined handler, I understand that it is because the code segment and data segment of our mcu1_0 are placed in the ddr. Shouldn't the data segment and code segment be placed in the OCM area?

When switching to the mcu only mode, do all the tasks accessing the main domain of the mcu have to stop?

Regards,

Sui

0 sui guoqing 2 months ago in reply to Karthikeyan S

Prodigy 180 points

Hi Karthik,

Has there been any progress? I'm really looking forward to your reply. Thank you!

Regards,

Sui

0 Gibbs Shih 2 months ago in reply to sui guoqing

TI__Expert 5245 points

Hi, Sui

I saw this thread already pending 5 days.

Does this issue still pending on your site?

Thanks

Gibbs

0 sui guoqing 2 months ago in reply to Gibbs Shih

Prodigy 180 points

Hi, Gibbs

yes,this issue still pending.

Thanks

Sui

0 Gibbs Shih 2 months ago in reply to sui guoqing

TI__Expert 5245 points

Hi, Sui

Base on current status, update few short comment from my side.

(1) Did yoiu ever run "LPM_example_freertos" on our TDA4VM EVB success even it's OSPI SBL boot?

(2) I try to search code in PDK that you post here, but I did not find any informain. Is it your customerzid code?

(3) It seems that crash happens when MCU is going to "MCU ONLY MODE" procedure, so that is no chance to run "wakeup up" stage, isn't?

(4) Pls share your linux log, becaue I can not see anything.

Hello, Karthik

Need your suggestion.

Do you think this is reset isolation issue?

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1387955/tda4vm-reset-isolation-ctrlmmr_wkup_main_vdom_ctrl/5539840?tisearch=e2e-quicksearch&keymatch=tda4vm%20isolation#5539840

Thank You.

Gibbs

0 sui guoqing 2 months ago in reply to Gibbs Shih

Prodigy 180 points

Hi, Gibbs

(1) I haven't run it on the TDA4VM EVB before, It seems to have no good reference value.

(2) Yes, It's the code I wrote by referring to the demo in PDK.

(3)Yes.

(4)I clicked the link to download and it opened normally.

0 Karthikeyan S 2 months ago in reply to sui guoqing

TI__Genius 13170 points

Hi,
Could you please share the changes you made to the .dts file in Linux?

Regards,
Karthik

0 sui guoqing 2 months ago in reply to Karthikeyan S

Prodigy 180 points

Hi,Karthik

/cfs-file/__key/communityserver-discussions-components-files/791/4118.dts.zip

Thanks

Sui

0 Gibbs Shih 1 month ago in reply to sui guoqing

TI__Expert 5245 points

Hello, Karthik

Could you give us any comment?

Thank You.

Gibss

0 Karthikeyan S 1 month ago in reply to Gibbs Shih

TI__Genius 13170 points

Hi Gibss,

I'm currently reviewing the .dts file and will get back to you shortly.

Regards,

Karthik

0 sui guoqing 1 month ago in reply to Karthikeyan S

Prodigy 180 points

Hi,Karthik

I'm really looking forward to your reply. Thank you!

Thanks

Sui

0 Gibbs Shih 1 month ago in reply to sui guoqing

TI__Expert 5245 points

Hi, Sui

Share what I observed so far from DTS

Did you change power domain from "TI_SCI_PD_EXCLUSIVE" to "TI_SCI_PD_SHARED"

https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/11_00_00_06/exports/docs/pdk_jacinto_11_00_00_21/docs/userguide/jacinto/modules/lpm/lpm_mcu_only_mode_jacinto.html

example,

@@ -550,7 +550,7 @@ cpts@3d000 {
        main_crypto: crypto@4e00000 {
                compatible = "ti,j721e-sa2ul";
                reg = <0x0 0x4e00000 0x0 0x1200>;
-               power-domains = <&k3_pds 264 TI_SCI_PD_EXCLUSIVE>;
+               power-domains = <&k3_pds 264 TI_SCI_PD_SHARED>;
                #address-cells = <2>;
                #size-cells = <2>;
                ranges = <0x0 0x04e00000 0x00 0x04e00000 0x0 0x30000>;

0 Karthikeyan S 1 month ago in reply to Gibbs Shih

TI__Genius 13170 points

Hi Sui,

Gibbs Shih said:
(3) It seems that crash happens when MCU is going to "MCU ONLY MODE" procedure, so that is no chance to run "wakeup up" stage, isn't?

The mcu_uart0 is still marked as "reserved" rather than "disabled" in your Linux device tree patch. So there's a possibility it may still be active elsewhere in the system, just not used by Linux. Could you please try disabling the mcu_uart0 as mentioned in the LPM guide?

Regards,

Karthik

0 sui guoqing 1 month ago in reply to Karthikeyan S

Prodigy 180 points

Hi,Gibbs,Karthik

5.24.1. MCU Only mode — Platform Development Kit (PDK) - JACINTO User Guide

Gibbs Shih said:
Did you change power domain from "TI_SCI_PD_EXCLUSIVE" to "TI_SCI_PD_SHARED"

I haven't change the power domain. Thank you for your reminder.

Karthikeyan S said:
The mcu_uart0 is still marked as "reserved" rather than "disabled" in your Linux device tree patch. So there's a possibility it may still be active elsewhere in the system, just not used by Linux. Could you please try disabling the mcu_uart0 as mentioned in the LPM guide?

I saw in chapter 5.24.1.11.3 that some devices were disabled in the device tree. After I disabled these devices, linux would get stuck when starting up. In fact, there are some devices that we need to use normally and cannot be disabled in the device tree. How should we handle this situation? For example, ospi0, mcu_cpsw, serdes0-serdes2.

Thanks

Sui

0 sui guoqing 1 month ago in reply to sui guoqing

Prodigy 180 points

Hi,Gibbs,Karthik

Could you help me think of a way?

Thanks

Sui

0 Doredla Sudheer Kumar 1 month ago in reply to sui guoqing

TI__Guru 63920 points

Hi,

Sorry for the delay, we are checking internally with the respective experts why a few MCU modules are disabled from the device tree.
As per my understanding, we do not need to disable modules used in A72 Linux from the device tree.

I believe you will be able to boot Linux when you have enabled the required modules from the device tree.

Best Regards,
Sudheer

0 sui guoqing 1 month ago in reply to Doredla Sudheer Kumar

Prodigy 180 points

Hi, Sudheer

Thank you. I'm really looking forward to your reply.

Could you please help confirm that when MCU1_0 executes SwResetMainDomain, should mcu1_0 stop all tasks accessing the resources of the main domain?

Thanks

Sui

0 Doredla Sudheer Kumar 1 month ago in reply to sui guoqing

TI__Guru 63920 points

Hi,

Sorry for delayed response.

sui guoqing said:
should mcu1_0 stop all tasks accessing the resources of the main domain

Yes, it is recommended to stop all main domain resources access from muc1_0 while executung main domain reset.

If not, it may lead to failure of main domain reset operations.

Doredla Sudheer Kumar said:
As per my understanding, we do not need to disable modules used in A72 Linux from the device tree.

It is not mandatory to disable modules using in A72. Care should be taken when modile is already enabled in using in MCU1_0 like MCU UART as it may lead to unpredictable outout when multiple cires trying to access without proper co-ordination.

Best Regards,

Sudheer

0 sui guoqing 1 month ago in reply to Doredla Sudheer Kumar

Prodigy 180 points

Hi, Sudheer

sui guoqing said:
1.When device_disable is called and dev is j721e_dev_ddr32ss_16ffc_ew_dv_wrap_main_0, MCU1_0 will enter HwiP_undefined_handler_c.

Even in the MCU only mode, our mcu1_0 still needs to use DDR. I skipped j721e_dev_ddr32ss_16ffc_ew_dv_wrap_main_0 in device_disable. Is this okay?

sui guoqing said:
2. So I shielded and turned off j721e_dev_ddr32ss_16ffc_ew_dv_wrap_main_0, and continued the test. When soc_device_disable was called to disable WKUPMCU2MAIN bridge, MCU1_0 would enter HwiP_data_abort_handler.

If we do not need to disable modules used in A72 Linux from the device tree, then what are the other reasons for this problem? Could you please help analyze it? Thank you.

Best Regards,

Sui

0 Karthikeyan S 24 days ago in reply to sui guoqing

TI__Genius 13170 points

Hi Sui,

Sorry for the delayed response.

We are also facing UART synchronization issue while testing LPM, so I have informed the development team. They are working on this issue, and I will let you know once they get back.

Regards,

Karthik

0 sui guoqing 24 days ago in reply to Karthikeyan S

Prodigy 180 points

Hi Karthik,

I'm really looking forward to your reply. Thank you!

Best Regards,

Sui

0 Doredla Sudheer Kumar 23 days ago in reply to sui guoqing

TI__Guru 63920 points

sui guoqing said:
sui guoqing said:
1.When device_disable is called and dev is j721e_dev_ddr32ss_16ffc_ew_dv_wrap_main_0, MCU1_0 will enter HwiP_undefined_handler_c.

Even in the MCU only mode, our mcu1_0 still needs to use DDR. I skipped j721e_dev_ddr32ss_16ffc_ew_dv_wrap_main_0 in device_disable. Is this okay?

It is not recommended to use DDR in the MCU Domain. As it is the Main domain resource.
Please refer to the SDK Documentation.

https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/latest/exports/docs/pdk_jacinto_11_00_00_21/docs/userguide/jacinto/modules/lpm/lpm_mcu_only_mode_jacinto.html#scope-of-work

sui guoqing said:
sui guoqing said:
2. So I shielded and turned off j721e_dev_ddr32ss_16ffc_ew_dv_wrap_main_0, and continued the test. When soc_device_disable was called to disable WKUPMCU2MAIN bridge, MCU1_0 would enter HwiP_data_abort_handler.

If we do not need to disable modules used in A72 Linux from the device tree, then what are the other reasons for this problem? Could you please help analyze it? Thank you.

Cross-domain usage will be the cause of the above problem.

Best Regards,
Sudheer

Processors

Processors forum

TDA4VM: Questions about LPM mcu only mode