> > > That is true. The assumption is that the stack size of the built-in > application will be big enough for the replacement ELF application. > That might not be true. But in the case of replacing a built-in > application with an ELF application, the rule is that we cannot > modify > the base ROM logic. Imagine that I have 100,000 products in the > field > and I want to replace a built-in. That is pretty easy to do by just > writing the ELF file to the some local file system. You would like > to > avoid replacing the entire FLASH image.
Yep, that's pretty clear, that's the idea of using the elf file instead of entire flash image. This is why I think all the stack sizes should be set according to any increased needs of updated elf files.. I merged Xiang's change. Please try the changes in the repository now if you can make the time (without changing the name of hello). At least seems you got a communication problem here, because nobody had a notion about the impact of Chaos commit. tested with commit 8997213c2aca8fae0f5537833014f9e016b51dd2 : nsh> hello Hello, World ELF!! nsh> dmesg load_absmodule: Loading /mnt/ramdisk/hello elf_loadbinary: Loading file: /mnt/ramdisk/hello elf_init: filename: /mnt/ramdisk/hello loadinfo: 0x20009f2c elf_read: Read 52 bytes from offset 0 ...... ==> working again as supposed. Thanks & BR, Florian
