J721S2XSOMXEVM: DDR ... SBL+OSPI, MCU1_0 demo stuck in LPDDR4 initialization

Hi  Champs：

The memory we use is MT53E2G32D4 AAT_LPDDR4_2Gb32_AECQ_Micron (16GB).

This problem is very urgent, please help reply as soon as possible.

Thank you very much!

BR,

Js Zhang

Hi,

This is the same part number as the EVM right?
Have you tried any other app in SDK? Just want to rule out if this is just an issue with mcusw boot app

Regards,
Parth

It's the same.

Can you tell me why it's stuck here.

Can you release the guidance for debugging multi-core booting?

Hi  Parth：

Any update? waiting for your reply!

    Thanks a lot.

Hi  Parth:

5635.board_ddrRegInit.h

The memory configuration file, "board_ddrRegInit.h" has been uploaded to the attachment. How to modify the refresh time and impedance parameters using SPRACU8A_Jacinto7_DDRSS_RegConfigTool.xlsm tool?

Thank you!

BR,

js

Hi JS,

js zhang said:

The memory configuration file, "board_ddrRegInit.h" has been uploaded to the attachment. How to modify the refresh time and impedance parameters using SPRACU8A_Jacinto7_DDRSS_RegConfigTool.xlsm tool?

For this, please refer to this application note: https://www.ti.com/lit/pdf/spracu8

Parth Nagpal said:

Have you tried any other app in SDK? Just want to rule out if this is just an issue with mcusw boot app

It is important that you answer this question as well and continue the debug in the right direction.

Regards
Karthik

Hi  Karthik:

       Thanks for  your reply.

          Have you tried any other app in SDK? Just want to rule out if this is just an issue with mcusw boot app

         It is important that you answer this question as well and continue the debug in the right direction.

     For This, I have tried to use  ti-processor-sdk-rtos-j721s2-evm-08_06_00_11/pdk_j721s2_08_06_00_31/packages/ti/boot/sbl/example/boot_app , but it's also failed. Log stuck "Board_flashOpen failed!". And I noticed that boot_app and boot_app_mcu_rtos code flow is different. For example, 

boot_app_mcu_rtos has MainDomainBootSetup process, and ddr initialization is performed inside this function, but boot_app does not have MainDomainBootSetup process.

      Because we need to use boot_app_mcu_rtos with can_fast_response to start the multicore.

BR,

Js

Hi  Karthik:

     We found that mcusw/mcuss_demos/boot_app_mcu_rtos in the original sdk did not compile, indicating a missing file. So we found 0001-Patch-for-fast_can_resp-feature-on-J7AEP.patch on the forum, and it should compile. I uploaded this patch in the attachment.We're not sure if this patch will work.

2055.0001-Patch-for-fast_can_resp-feature-on-J7AEP.zip

BR,

Js

Hi Js,

Can you please try any app other than boot app?
Try a simpler app like udma example and just see if you are able to boot it.

To build the example run the following command:

1) cd <PDK>/packages/ti/build
2) make BOARD=j721s2_evm CORE=mcu1_0 udma_memcpy_testapp_freertos

Try running this test with the SBL.

Also, can you please share detailed steps to reproduce this issue on our end?

Regards,
Parth

Hi  Parth:

     Thanks for  your reply.

     I look at the packages/ti/DRV udma/examples/udma_memcpy_test directory of the code, and found that there is no start multi-core code process. How should I try to test this example?

     Here's what happens:

     We need to start the multicore using mcu1_0. Here's how we do it:

     1. cp  -rf  ti-processor-sdk-rtos-j721s2-evm-08_06_00_11\mcusw\mcuss_demos\boot_app_mcu_rtos  ti-processor-sdk-rtos-j721s2-evm-08_06_00_11\mcusw\mcuss_demos\profiling\

         cd  ti-processor-sdk-rtos-j721s2-evm-08_06_00_11\mcusw\mcuss_demos\profiling\

         mv boot_app_mcu_rtos  can

     2. cd ti-processor-sdk-rtos-j721s2-evm-08_06_00_11\mcusw\build

         make -s -j4 can_profile_app BOARD=j721s2_evm SOC=j721s2 BUILD_PROFILE=release CORE=mcu1_0 BUILD_OS_TYPE=freertos

     3. Burn the can_profile_app_freertos_mcu1_0_release.appimage object file into ospi.

     4. Start up our custom board.

      Below is the log:

BR,

Js

Hi Js,

Can you please remove BOARD_INIT_DDR flag from your Board_Init call in bootApp and try? DDR will anyway be initialized by SBL, you don't need to initialize it again.

Regards,
Parth

Hi  Parth:

When I remove BOARD_INIT_DDR flag, it stops at Board_flashOpen failed!.  Should I need to configure ospi flash?

Below is the log. 

BR,

Js

Hi Js,

Look like MCUSW boot app has some known issues. Can you please mention your use case here? Do you have any specific requirement for boot app or you are just looking for a way to run multicore tests. If you want to run a multi-core test, you can use the combined app image tool available at <PDK>\packages\ti\boot\sbl\tools\combined_appimage

Regards,
Parth

Hi  Parth:

      Thanks for  your reply.

      We need to start multi-core by using ospi flash. Can we only use boot app code under pdk or boot app code under mcusw? The ospi flash device id used for our custom board is 5B1A. Should we need to configure this flash?

BR,

Js

Hi Js,

js zhang said:

Can we only use boot app code under pdk or boot app code under mcusw?

Not sure if I am understanding this clearly. Do you have a specific need for boot App? You can start multi core by using combined appimage too as well.

Regards,
Parth