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 the CONFIG_ELF stuff.. But, I will double-check the elf linker script, maybe something wrong with that! BR,
-- Florian Wehmeyer TFW Tech-Solutions On Seg, 2020-05-11 at 16:24 -0400, Nathan Hartman wrote: > On Mon, May 11, 2020 at 2:05 PM Florian Wehmeyer <flo...@gmx.net> > 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 a custom board or an existing configuration? If an > existing configuration, which one? > > If it's for a custom board, then the place I would recommend to check > is the linker script, Kconfig options, and compiler options. Perhaps > try to find an existing configuration in the NuttX tree that is as > close as possible to yours, and compare the various files (linker > files, defconfig, etc) and see whether any differences that you find > will affect heap allocations. > > Hopefully someone else here can chime in with some more specific > items to check. > > Nathan
