However, got a new problem now which I've not figured out yet:
The binary loader does not load the elf if the program is a built-in
app... very strange..
It does not even try to load the elf file from file-system, it directly
goes to the built-in app.
That means that it failed to load the app on the file system. It should
check in this order"
- Load file from file system if possible
- If not, run built-in application if possible
- If not, run NSH command line command if possible
- If not, report that the command was not found
so if you are seeing the second action, it means that the first
failed. You can load FS and Binary loader error debug output to see.
Funnily, it does try to load the nsh embedded tools:
exec_spawn: ERROR: Failed to load program 'ls':
-2
yes, this is normal behavior. Se you can see from the steps above, ALL
commands will try to load from the various locations and you will see
the errors. But they are not "real" errors.
If I do not compile the app as a built-in app, the binary loader will
load it:
load_absmodule: Loading
/mnt/ramdisk/Neo_Ledtest
elf_loadbinary: Loading file:
/mnt/ramdisk/Neo_Ledtest
elf_init: filename: /mnt/ramdisk/Neo_Ledtest loadinfo: 0x2000a4cc
Which shows that the CONFIG_BINFMT_EXEPATH=y and CONFIG_PATH_INITIAL ar
e correctly set, and the elf file is also working correctly..
I never had this situation before...
It shouldn't work that way
