TDA4VM: A dead loop occurs when entering mcu_only mode

Cherry Zhou

Part Number: TDA4VM

Hi team,

Here's an issue from the customer may need your help:

When TDA4 enters mcu_only mode, write the customer's own code with reference to the content in mcu_only_app.c in the SDK. It was found that when the function Sciclient_service was called, the program would get stuck. This issue is also found on the development board after validation with the development board.

SDK: Version 7.1, Startup Mode: SBL, just added some of its own log printout compared to the reference code. Below are the final log and some of the related code:

MCu1_0 was verified to be running on DDR, and after changing the operating area to OCMC_RAM, it worked properly. However, due to the limited OCMC_RAM capacity, it is only 512K and not enough. Can mcu1_0 continue to run on DDR without turning off the DDR function while reset main domain?

Could you help check this case? Thanks.

Best Regards,

Cherry

over 4 years ago

0 Cherry Zhou over 4 years ago

TI__Mastermind 22235 points

Hi,

May I know is there any updates?

Thanks and regards,

Cherry

0 Karan Saxena over 4 years ago

TI__Guru* 78165 points

Hi Cherry,

Is the issue that when you are running MCU1_0 application from DDR then after the Sciclient_service() for TISCI_SYS_RESET there are no more logs?

If so, then this is expected as the DDR is in MAIN domain and will get reset when you call the TISCI_SYS_RESET for the MAIN domain using the Sciclient_service().

In an MCU only mode, the MAIN domain will be powered off and hence you can not run code out of DDR. You need to use the MCU domain memories when in MCU only mode - these memories include OCMC RAM (1MB) or you can XIP from the OSPI flash. Please note that XIP from OSPI flash is not tested so I won't recommend that right away.

Regards

Karan

0 Karan Saxena over 4 years ago in reply to Karan Saxena

TI__Guru* 78165 points

Additionally the demo you are referring to is from a very old release. Please refer the latest demo which is now a part of PDK.

https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/08_02_00_05/exports/docs/pdk_jacinto_08_02_00_21/docs/userguide/jacinto/modules/lpm/lpm_mcu_only_mode_jacinto.html

Regards

Karan

0 bingxian lu over 4 years ago in reply to Karan Saxena

Intellectual 640 points

Hi Karan,

1.OCMC RAM resources are insufficient for our use in our project. If DDR cannot be used in MCU ONLY mode, could TI recommend a solution?

2.Does SDK8.2 support automatic cores loading when Mcu_only mode is switched to ACTIVE mode?

Regards

bingxian

0 Cherry Zhou over 4 years ago in reply to bingxian lu

TI__Mastermind 22235 points

Hi Karan,

Thanks for your help and bingxian is the customer, I believe you could directly discuss this issue here, and if you need any more assistance please let me know.

Hi bingxian,

If you need more assistance feel free to let me know.

Thanks and regards,

Cherry

0 bingxian lu over 4 years ago in reply to Karan Saxena

Intellectual 640 points

Hi Karan,

May I know is there any updates?

Thanks and regards,

bingxian

0 Karan Saxena over 4 years ago in reply to bingxian lu

TI__Guru* 78165 points

Hi bingxian

bingxian lu said:
1.OCMC RAM resources are insufficient for our use in our project. If DDR cannot be used in MCU ONLY mode, could TI recommend a solution?

1. There is an option to execute code in XIP from the OSPI flash. But this is not integrated in the demo currently and also no plan to do this as of now.

2. Can you explain your use case to me? Why are you planning to use MCU only mode?

The reason for my question is because if you plan to use DDR then MCU only mode is not a good option.

3. How much memory is required to be used in MCU Only mode?

Regards

Karan

0 bingxian lu over 4 years ago in reply to Karan Saxena

Intellectual 640 points

Hi Karan,

Thanks for your help, MCU ONLY really cannot meet our requirements for low power consumption, We already have other ways to achieve low power consumption

bingxian

Processors

Processors forum

TDA4VM: A dead loop occurs when entering mcu_only mode