DRA829J: When Update SDK7.0.3, boot from SD fail

yan yan

Part Number: DRA829J

Hi Ti expert,

When i update SDK7.0.3, I met some problems with boot from SD card.

tiboot3 tispl and u-boot which need regenerated after mcu1_0 update. When i use mcu demo ipc_echo_testb_mcu1_0_release_strip.xer5f as mcu1_0 firmware image, our system can boot.

But when i use other demo like can_profile_app_mcu1_0_release.xer5f and sciserver_testapp_mcu1_0_release.xer5f as mcu1_0 firmware image, it can't boot.

When use sciserver_testapp_mcu1_0_release.xer5f, A72 UART log is

R5F mcu1_0 UART log is

It seems that R5 core has boot but A72 not boot.

Please help to solve this problem. Thanks!

over 4 years ago

0 Suman Anna over 4 years ago

TI__Guru** 112645 points

Hi Yan,

I am assuming you meant SDK 7.3 and not 7.0.3. MCU1_0 is booted with ATCM disabled and BTCM enabled. So, you cannot use any firmware that is designed to boot out of ATCM. This is the difference between ipc_echo_testb_mcu1_0_release_strip.xer5f vs the other IPC echo test examples like ipc_echo_test_mcu2_0_release_strip.xer5f.

So, use the appropriate linker cmd file to generate BTCM-compliant firmware images.

regards

Suman

0 yan yan over 4 years ago in reply to Suman Anna

Prodigy 215 points

Hi Anna,

Yes, SDK version is 7.3.

Demo firmware can_profile_app_mcu1_0_release.xer5f and sciserver_testapp_mcu1_0_release.xer5f don't use ATCM. I checked their link file and map file that they are not using ATCM. And i tried again, still only demo ipc_echo_testb_mcu1_0_release_strip.xer5f works well.

1. Do you have other recommended demo mcu i can try on our board?

2. Is their any other hints need to consider when i use other mcu1_0 firmware?

regards

yan

0 yan yan over 4 years ago in reply to yan yan

Prodigy 215 points

Demo firmware ipc_echo_testb_mcu1_0_release.xer5f failed either.

strip file seems more smaller. Does DM file have requirement on file type or file size

0 yan yan over 4 years ago in reply to Suman Anna

Prodigy 215 points

Hi Suman,

I found that in demo ipc_echo_testb_mcu1_0_release_strip.xer5f has a unique section name .resource_table (a0100000)

Does this section need to add in MCU firmware?

regards

yan

0 Suman Anna over 4 years ago in reply to yan yan

TI__Guru** 112645 points

Hi Yan,

Yes, the .resource_table section is a mandatory requirement for Linux kernel remoteproc. This needs to be at 0xa0100000 for MCU1_0.

The non-stripped firmwares are large in size and are sub-optimal for early-boot. The larger file sizes will cause larger latency to load and boot the remote processors, so please always use stripped firmware images for early-boot.

There is a current bug in U-Boot code that causes R5 SPL to corrupt the DM firmware when you use unstripped firmware images. This will be fixed in the next SDK (8.1) release.

Please see https://patchwork.ozlabs.org/project/uboot/patch/20210814064901.3840-1-s-anna@ti.com/ for details.

If you want to use unstripped MCU1_0 firmware images for now, please cherry-pick the following commit from Upstream U-Boot,

https://source.denx.de/u-boot/u-boot/-/commit/7d67334dfe9ce6a9f5ef3e9b95dd87ef482002b0

regards

Suman

0 yan yan over 4 years ago in reply to Suman Anna

Prodigy 215 points

Hi Suman,

Can you give a description about .resource_table. I tried to intergrate this section in demo mcu sciserver_testapp_mcu1_0_release_strip.xer5f and it did't boot either.

1. Do you have other recommended demo mcu i can try on our board?

2. Is their any other hints need to consider when i use other mcu1_0 firmware?

regards

yan

0 Suman Anna over 4 years ago in reply to yan yan

TI__Guru** 112645 points

Hi Yan,

Resource Table

Please see the kernel documentation to understand what a resource table is.

You can also refer to the following FAQ: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1012138/faq-tda4vm-resource-table-for-ipc

For K3 platforms, you mainly need a RSC_VDEV entry and an optional RSC_TRACE entry to dump the traces on the Linux debugfs using a circular buffer.

MCU1_0 Software

Are you able to run with the stripped firmware image?

Please refer to the following in the RTOS SDK documentation for the requirements on MCU1_0 firmwares:

https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/07_03_00_07/exports/docs/psdk_rtos/docs/user_guide/developer_notes_mcu1_0_sysfw.html

regards

Suman

0 yan yan over 4 years ago in reply to Suman Anna

Prodigy 215 points

Hi Suman,

Are you able to run with the stripped firmware image?

I have tried various demo stripped firmware images including sciserver_testapp_mcu1_0_release_strip.xer5f can_profile_app_mcu1_0_release_strip.xer5f and ipc_echo_testb_mcu1_0_release_strip.xer5f. Only ipc_echo_testb_mcu1_0_release_strip.xer5f can work well.

We want to know

1. Why other images can't boot except ipc_echo_testb_mcu1_0_release_strip.xer5f ?

2. When use sciserver_testapp_mcu1_0_release_striip.xer5f, main domain UART log is

mcu domain UART log is

regards

Yan

0 Suman Anna over 4 years ago in reply to yan yan

TI__Guru** 112645 points

Hi Yan,

Did you rebuild the above firmware images to add the ".resource_table" sections or are you running the firmware images built as is?

Please provide the readelf -l output for both the above images.

regards

Suman

Processors

Processors forum

DRA829J: When Update SDK7.0.3, boot from SD fail