Re: 答复: [External Mail]Re: heap malloc when executing binary/elf file

So, in current git HEAD [1], what is the search order now? Is it back to: - Elf - Built-in - NSH Or is it: - Built-in - Elf - NSH It is not so clean and well partitioned.  It is more like: o IF Built-in available   - Elf   - IF NOT Elf     Built-in o Elf o NSH The logic is spread across

Re: 答复: [External Mail]Re: heap malloc when executing binary/elf file

> > > 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

Re: 答复: [External Mail]Re: heap malloc when executing binary/elf file

So, in current git HEAD [1], what is the search order now? Is it back to: - Elf - Built-in - NSH Or is it: - Built-in - Elf - NSH It is not so clean and well partitioned.  It is more like: o IF Built-in available - Elf - IF NOT Elf Built-in o Elf o NSH The logic is spread across a

Re: 答复: [External Mail]Re: heap malloc when executing binary/elf file

On Mon, May 18, 2020 at 10:38 AM Gregory Nutt wrote: > >> Yes, the best solution is to extend ELF with stack and priority info. > >> But before that happen, gathering this info from the built-in app > >> table is workable alternative: > >> 1.Keep the trying order(file system, built-in and nsh comm

Re: 答复: [External Mail]Re: heap malloc when executing binary/elf file

Yes, the best solution is to extend ELF with stack and priority info. But before that happen, gathering this info from the built-in app table is workable alternative: 1.Keep the trying order(file system, built-in and nsh command) 2.And get the stack/priority from built-in app table for file s

Re: 答复: [External Mail]Re: heap malloc when executing binary/elf file

Yes, the best solution is to extend ELF with stack and priority info. But before that happen, gathering this info from the built-in app table is workable alternative: 1.Keep the trying order(file system, built-in and nsh command) 2.And get the stack/priority from built-in app table for file sys

Re: 答复: [External Mail]Re: heap malloc when executing binary/elf file

On Mon, May 18, 2020 at 9:07 PM Gregory Nutt wrote: > > > > OK, by now I'll keep using the alternative to use another name for the > > elf app/FILE_APPS, as seemingly intended by > > chao.an in his commit. > No, that was an error. The requirements have always supported > replacement of built-in a

Re: 答复: [External Mail]Re: heap malloc when executing binary/elf file

OK, by now I'll keep using the alternative to use another name for the elf app/FILE_APPS, as seemingly intended by chao.an in his commit. No, that was an error.  The requirements have always supported replacement of built-in applications with ELF applications.  That is a recommended way for u

Re: 答复: [External Mail]Re: heap malloc when executing binary/elf file

2300  28.1%  /system/bin/nsh > 3     2 100 FIFO Task--- Waiting  Signal > 020464 019528  95.4%! hello > > It is make sense to use the builtin attribute for applications if we > enabled the BUILTIN_APPS / FILE_APPS at the same time. > > BRs, > __

答复: [External Mail]Re: heap malloc when executing binary/elf file

发件人: Gregory Nutt 发送时间: 2020年5月18日 6:59 收件人: dev@nuttx.apache.org 主题: [External Mail]Re: heap malloc when executing binary/elf file Hi, Brennan, >>> I just created incubator-nuttx-apps PR 255 that should restore the >>> correct behavior: >

Re: heap malloc when executing binary/elf file

Hi, Brennan, I just created incubator-nuttx-apps PR 255 that should restore the correct behavior: https://github.com/apache/incubator-nuttx-apps/pull/255 This is a major bug and, if we release do a bugfix release sometime, this should be included. I was thinking the same. I created a label ba

Re: heap malloc when executing binary/elf file

On Sun, May 17, 2020, 3:50 PM Gregory Nutt wrote: > > > I just created incubator-nuttx-apps PR 255 that should restore the > > correct behavior: > https://github.com/apache/incubator-nuttx-apps/pull/255 > > This is a major bug and, if we release do a bugfix release sometime, > this should be incl

Re: heap malloc when executing binary/elf file

I just created incubator-nuttx-apps PR 255 that should restore the correct behavior: https://github.com/apache/incubator-nuttx-apps/pull/255 This is a major bug and, if we release do a bugfix release sometime, this should be included.

Re: heap malloc when executing binary/elf file

I just created incubator-nuttx-apps PR 255 that should restore the correct behavior: https://github.com/apache/incubator-nuttx-apps/pull/255 On 5/17/2020 3:33 PM, Gregory Nutt wrote: Mystery solved. It does not even try to load the elf file from file-system, it directly goes to the built-in ap

Re: heap malloc when executing binary/elf file

Mystery solved. 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 possibl

Re: heap malloc when executing binary/elf file

Hi Greg and Alan, > > 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 bu

Re: heap malloc when executing binary/elf file

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

Re: heap malloc when executing binary/elf file

Hi Florian, Does this problem only occur in version 9.0.0? Or is it happening to the current master as well? Are you following this tutorial: https://www.youtube.com/watch?v=oL6KAgkTb8M Also you can increase the debug level (include warn and info). BR, Alan On 5/16/20, Florian Wehmeyer wrote

Re: heap malloc when executing binary/elf file

Hi Alan,  updated it again to 9.0.0 and also good! 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

Re: heap malloc when executing binary/elf file

Hi Florian, Nice to know you got if fixed. It should be nice if you can test it again using the nuttx-9.0.0 release. BR, Alan On 5/16/20, Florian Wehmeyer wrote: > Hi all, > just to let you know, the heap problem was solved after pulling the > latest commit from master.. > Now I can use very

Re: heap malloc when executing binary/elf file

Hi all,  just to let you know, the heap problem was solved after pulling the latest commit from master.. Now I can use very much of it, also I was able to use a lot more features in the config, as cmd line history etc... So, the available memory of 256K was not the problem, @Greg.  @Nathan:  now ma

Re: heap malloc when executing binary/elf file

OK Greg,  could be that I was using too much.. using 64KB of ramdisk also.. I disabled some of the comfortable features like cmd line history etc, and was already able to alloc quite a bit more than before.. Will further improve the sram usage.. Also, I missed the commit  mm/mm_heap: fix mm_heap no

Re: heap malloc when executing binary/elf file

On Mon, May 11, 2020 at 5:01 PM Gregory Nutt wrote: > That part has 256Kb of SRAM. That is more that many, but it could be > that you are using too much SRAM and just cannot run ELF reliably. It > does want a lot of SRAM. If there isn't enough memory, I wonder why malloc doesn't return NULL? Ha

Re: heap malloc when executing binary/elf file

No custom board, it's the  tm4c1294-launchpad. Seems no general problem with heap allocation, so I guess it's not in the linker script, it's rather directly linked to the usage of the elf- binary loader, and there are only two configs in the nuttx repo which use the CONFIG_ELF stuff. That pa

Re: heap malloc when executing binary/elf file

No custom board, it's the  tm4c1294-launchpad. Seems no general problem with heap allocation, so I guess it's not in the linker script, it's rather directly linked to the usage of the elf- binary loader, and there are only two configs in the nuttx repo which use the CONFIG_ELF stuff. That par

Re: heap malloc when executing binary/elf file

Thanks Nathan,  I'll check on that.. No custom board, it's the  tm4c1294-launchpad. Seems no general problem with heap allocation, so I guess it's not in the linker script, it's rather directly linked to the usage of the elf- binary loader, and there are only two configs in the nuttx repo which use

Re: heap malloc when executing binary/elf file

On Mon, May 11, 2020 at 2:05 PM Florian Wehmeyer wrote: > OK I already saw that simply increasing the heap is no solution, > because it's already maximum size: > mm_initialize: Heap: start=0x20008924 > size=227036 > mm_addregion: Region 1: base=0x20008924 size=227024 Tricky problem. Is this for

Re: heap malloc when executing binary/elf file

OK I already saw that simply increasing the heap is no solution, because it's already maximum size:  mm_initialize: Heap: start=0x20008924 size=227036    mm_addregion: Region 1: base=0x20008924 size=227024 -- Florian Wehmeyer TFW Tech-Solutions On Seg, 2020-05-11 at 14

Re: heap malloc when executing binary/elf file

looking more into the memory allocation debug, there is a lot more dynamic allocation (obviously)  when loading the elf program than when loading the same program as built-in.. So, seems the problem is due to a high heap fragmentation, what explains that a call to dmesg can also make the system cra