[FAQ] TDA4VM Enable MCU_R5F lockstep using SPL and SBL

Hi Xie,

Do you want to boot SBL in lockstep mode? 

I think SBL boots up in split mode, but later on, BootApplication boots in lockstep mode. 

Regards,

Brijesh

Hi,Brijesh

    I want to enable Lockstep in SBL, and I see that the SBL code in SDK7.03 already supports it. So the question is how can we create the MCU1_SMP_ID?

 Regards,

Xie

Hi Xie,

SBL is already started running on mcu1 core, which can be locked or in split mode, even for SBL. 

The core id is input to this API, so the caller of this API should pass appropriate id.

Regards,

Brijesh

Hi,Brijesh

Brijesh Jadav said:

SBL is already started running on mcu1 core, which can be locked or in split mode, even for SBL.

So you mean to turn on lockstep before SBL starts the app?

Brijesh Jadav said:

The core id is input to this API, so the caller of this API should pass appropriate id.

But this Core ID should be read from the app.image file, not specified by the user

Regards,

Xie

Hello Xie,

I am sorry i am not getting the exact requirement. Do you want to run SBL in lockstep mode or the next example like BootApp in the lockstep mode?

SBL can change lockstep mode for the next application, but if you want to run SBL in lockstep mode, it would require different changes.

Regards,

Brijesh

Hi,Brijesh

     I want to run the next example like BootApp in lockstep mode.

Brijesh Jadav said:

SBL can change lockstep mode for the next application

   So what shoule we do?

  Regards,

Xie

Hello Xie,

For BootApp, can you add below line in the file ti-processor-sdk-rtos-j721e-evm-07_01_00_11\mcusw\mcuss_demos\mcusw_mcuss_demos.mk, at around line no 225, just before statement "export can_boot_app_mcu_rtos_SBL_APPIMAGEGEN"?

can_boot_app_mcu_rtos_APP_SMP_CONFIG = yes

This will select MCU1_SMP_ID id for the mcu1_0 and will configure R5F in lockstep mode in bootapp.

Regards,

Brijesh

Hi,Brijesh

   I compiled can_boot_app_mcu_rtos according to the method you said, and I also turned on the lockstep mode of SBL. The phenomenon is as follows

  1.I used two spinlocks in SBL, one before executing SBL_SciClientInit() and one after SBL_SciClientIni(),

  2.When I start with OSPI and connect to the debugger when I stop at the first spinlock, I can see from the          CTRLMMR_MCUSEC_CLSTR0_CFG register that the Lockstep mode is enabled.

  3.When stopping at the second spinlock, the value of the CTRLMMR_MCUSEC_CLSTR0_CFG register is cleared (whether it means Lockstep is disabled？).

  4.When booting to can_boot_app_mcu_rtos, the CTRLMMR_MCUSEC_CLSTR0_CFG register is also disabled by connecting to the debugger through CCS. So has the Lockstep mode been turned on in the current state? How to judge whether the Lockstep mode is successfully turned on?

 Regards,

Xie

Hello Mr Xie,

Can you change value of R5_STARTUP_MODE to EFUSE_DEFAULT in the file ti-processor-sdk-rtos-j721e-evm-07_02_00_06/pdk_jacinto_07_01_05_14/packages/ti/boot/sbl/build/sbl_img.mk, rebuild SBL and then try it? 

Currently SBL changes the R5 to split mode. if device supports lockstep mode and it is enabled in efuse, then this change will make R5 in lockstep mode even in SBL. Can you try above change?

Regards,

Brijesh