How can i solved "failed to load freertos-rpmsg.elf" in vf61?

Technical Support
, ,
1

i want to load .elf file in to m4 but .elf is failed
this massage is display

root@colibri-vf://#  dmesg|grep remoteproc
[    1.555808]  remoteproc0: vf610_m4 is available
[    1.569159]  remoteproc0: Note: remoteproc is still under development and considered experimental.
[    1.595499]  remoteproc0: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
[    1.623920]  remoteproc0: Direct firmware load for freertos-rpmsg.elf failed with error -2
[    1.650312]  remoteproc0: failed to load freertos-rpmsg.elf
[    1.665169]  remoteproc0: powering up vf610_m4
[    1.679725]  remoteproc0: Direct firmware load for freertos-rpmsg.elf failed with error -2
[    1.705774]  remoteproc0: request_firmware failed: -2
2

Did you deploy a valid ELF binary as described here?

3

yes i follow same document as you suggest but i did not find problem there is no problem in generate .elf file

4

The error message shows that there is no such file or directory (errno -2).
Do you have the freertos-rpmsg.elf binary at /lib/firmware directory ? As mentioned in the same article:

“NOTE: remoteproc by default looks for freertos-rpmsg.elf binary in /lib/firmware. To load a custom .elf one can create a symlink so that freertos-rpmsg.elf points to the actual .elf.”

5

yes i create symlink “ln -s hellow_world.elf freertos-rpmsg.elf”

6

Can you provide the output of

ls -lah /lib/firmware
7

yes see

root@colibri-vf:/lib/firmware#  ls -lah
drwxr-xr-x    3 root     root        1.3K Dec  7 07:25 .
drwxr-xr-x    9 root     root        6.8K Dec  7 05:36 ..
-rw-r--r--    1 root     root        2.1K Sep 27 12:03 LICENCE.ralink-firmware.txt
-rw-r--r--    1 root     root        2.1K Sep 27 12:03 LICENCE.rtlwifi_firmware.txt
lrwxrwxrwx    1 root     root          15 Dec  7 07:25 freertos-rpmsg.elf -> hello_world.elf
-rwxr-xr-x    1 root     root       85.7K Dec  7 10:07 hello_world.elf
-rwxr-xr-x    1 root     root       92.6K Dec  7 06:41 rpmsg_pingpong_example.elf
-rw-r--r--    1 root     root        8.0K Sep 27 12:03 rt2561.bin
-rw-r--r--    1 root     root        8.0K Sep 27 12:03 rt2561s.bin
-rw-r--r--    1 root     root        8.0K Sep 27 12:03 rt2661.bin
-rw-r--r--    1 root     root        8.0K Sep 27 12:03 rt2860.bin
-rw-r--r--    1 root     root        8.0K Sep 27 12:03 rt2870.bin
lrwxrwxrwx    1 root     root          10 Sep 27 12:17 rt3070.bin -> rt2870.bin
-rw-r--r--    1 root     root        4.0K Sep 27 12:03 rt3071.bin
lrwxrwxrwx    1 root     root          10 Sep 27 12:17 rt3090.bin -> rt2860.bin
-rw-r--r--    1 root     root        4.0K Sep 27 12:03 rt3290.bin
-rw-r--r--    1 root     root        2.0K Sep 27 12:03 rt73.bin
drwxr-xr-x    2 root     root         472 Sep 27 12:17 rtlwifi
8

How exactly did you generate the hello_world.elf file? Can you download the one from examples given here and check?

Can you install the “file” utility using the below commands

opkg update
opkg install file

and provide the output of “file hello_world.elf”?

9

now i install file utility
and see “file hello_world.elf”

root@colibri-vf:/lib/firmware# file hello_world.elf
hello_world.elf: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, not stripped
10

thank you for your support

11

Did you compile remoteproc/rpmsg as modules?

You cannot use built-in drivers because at that time the root file system is not mounted, hence the firmware can not be found…