AM625: /sys/class/remoteproc/remoteproc0# echo start > state -sh: echo: write error: Invalid argument

Part Number: AM625


I compiled the "helloword" program for "am62x-sk_m4fss0-0_freeertos" using CCS. I intended to test the M core, but I encountered the "Invalid argument" error.

image.png

root@myd-am62x-emmc:/sys/class/remoteproc/remoteproc0# echo stop > state

root@myd-am62x-emmc:/sys/class/remoteproc/remoteproc0# echo "am62-mcu-m4f0_0-fw" > firmware
root@myd-am62x-emmc:/sys/class/remoteproc/remoteproc0# echo start > state
root@myd-am62x-emmc:/sys/class/remoteproc/remoteproc0# echo "hello_world_am62x-sk_m4fss0-0_freertos_ti-arm-clang.out" > firmware
-sh: echo: write error: Device or resource busy
root@myd-am62x-emmc:/sys/class/remoteproc/remoteproc0# echo "hello_world_am62x-sk_m4fss0-0_freertos_ti-arm-clang.out" > firmwareC^C
root@myd-am62x-emmc:/sys/class/remoteproc/remoteproc0# echo stop > state
root@myd-am62x-emmc:/sys/class/remoteproc/remoteproc0# echo "hello_world_am62x-sk_m4fss0-0_freertos_ti-arm-clang.out" > firmware
root@myd-am62x-emmc:/sys/class/remoteproc/remoteproc0# echo start > state
-sh: echo: write error: Invalid argument

 

Is it because the firmware type is incorrect? Are there any other places that need to be revised?

/media/gyx/work/TI/example$ file ../mcu_example/hello_world_am62x-sk_m4fss0-0_freertos_ti-arm-clang.out 
../mcu_example/hello_world_am62x-sk_m4fss0-0_freertos_ti-arm-clang.out: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, with debug_info, not stripped