TDA4VM: mcu1_0 is not able to stop

Cherry Zhou

Part Number: TDA4VM

Hi team,

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

j721e_evm development board is used to debug. And /lib/firmware/j7-mcu-r5f0_0-fw link has been deleted, but the trace is still running. The customer would like to know how to stop it or how to update this firmware.

After linking the j7-mcu-r5f0_0-fw to new firmware, it still runs the original ipc demo.

root@j7-evm:~# cat /sys/kernel/debug/remoteproc/remoteproc3/trace0 
Starting Sciserver..... PASSED
IPC_echo_test (core : mcu1_0) .....
IPC Driver Revision: 01.00.00.01
mcu1_0 <--> mcu2_0, Ping- 10000, pong - 10000 completed
mcu1_0 <--> mcu3_0, Ping- 10000, pong - 10000 completed
root@j7-evm:~#

Could you help check this case? Thanks.

Best Regards,

Cherry

over 4 years ago

0 Suman Anna over 4 years ago

TI__Guru*** 126405 points

Hi Cherry,

The MCU1_0 is an essential boot core from SDK 7.1 onwards, and it's firmware is linked into the A72 tispl.bin binary. The MCU1_0 application firmware is started at the end of R5 SPL after the A72 cores have been launched.

A soft-link for the same firmware needs to be maintained in 7.x SDKs for the Linux remoteproc to retrieve the resource_table and establish IPC with MCU1_0. The softlink or presence in FS is no longer required on 8.x SDKs, as the driver follows a design-by-contract approach to find the .resource_table.

Please see MCU1_0 Application Development with SYSFW section of the RTOS SDK documentation, especially the SPL/uboot Loading section. You need to rebuilt U-Boot with your firmware to get the updates.

regards

Suman

Processors

Processors forum

TDA4VM: mcu1_0 is not able to stop