On Sun, Feb 8, 2026 at 3:11 PM Peter Barada <[email protected]> wrote:
> Nathan, > > What's strange is that same master source (nuttx hash > e83606732d5e71eb98a9eb544537dbbeb71aa58b, apps hash > d48b45000d1d083082f7a1650f351573c36a87d0) with INIT_STACKSIZE=2048 in the > default .config fails on nucleo-h743zi2 but passes on nucleo-h743zi2(run on > my nuclo-h753zi board) when I try "time ls". I turned on all the stack > checks just to be sure nuclo-f446re wasn't just "lucky". > and On Sun, Feb 8, 2026 at 5:23 PM Peter Barada <[email protected]> wrote: > Nathan, > > I believe you're misunderstanding me. I have two boards - nucleo-f446re > and nuclo-h753zi. I created two separate builds from the same source > hahses(nucleo-f446re:nsh and nucleo-h743zi2:nsh) using stock defconfigs > and then ran those builds on the corresponding boards. The > nucleo-f446re:nsh build ran on the nuclo-f446re("time ls" passes), while > the nucli-h743zi2:nsh build failed on the nucleo-h753zi board while > testing "time ls" at boot on each. > Yes I misunderstood partially, but that's okay because you answered my question: These are two separate configs. Whenever I encounter problems, I find it enlightening to compare files... I checked out the hashes you mentioned: $ cd nuttx $ git checkout e83606732d5e71eb98a9eb544537dbbeb71aa58b --force $ cd ../apps/ $ git checkout d48b45000d1d083082f7a1650f351573c36a87d0 --force $ cd ../nuttx/ Then I configured the two configs you mentioned: $ tools/configure.sh nucleo-f446re:nsh $ cp .config ../nucleo-f446re-config.txt $ make distclean $ tools/configure.sh nucleo-h743zi2:nsh $ cp .config ../nucleo-h743zi2-config.txt And then I made a comparison of the resulting .config files: $ diff ../nucleo-f446re-config.txt ../nucleo-h743zi2-config.txt Many of the differences found are expected, since these are slightly different architectures, have different peripherals, etc. But I think the following differences may be significant: f446re has: CONFIG_ARCH_HAVE_HEAPCHECK=y # CONFIG_HEAP_COLORATION is not set # CONFIG_DEBUG_SYMBOLS is not set # CONFIG_FRAME_POINTER is not set CONFIG_ARCH_HAVE_CUSTOMOPT=y # CONFIG_DEBUG_NOOPT is not set # CONFIG_DEBUG_CUSTOMOPT is not set CONFIG_DEBUG_FULLOPT=y In contrast, h743zi2 has: # CONFIG_ARCH_HAVE_HEAPCHECK is not set CONFIG_DEBUG_SYMBOLS=y CONFIG_DEBUG_SYMBOLS_LEVEL="-g" # CONFIG_FRAME_POINTER is not set CONFIG_ARCH_HAVE_CUSTOMOPT=y CONFIG_DEBUG_NOOPT=y # CONFIG_DEBUG_CUSTOMOPT is not set # CONFIG_DEBUG_FULLOPT is not set I haven't dug deeper into these debug options but I recommend to check whether some of them alter stack usage a bit. h743zi also has: CONFIG_STM32_APP_FORMAT_LEGACY=y and CONFIG_ARCH_FPU=y CONFIG_ARCH_DPFPU=y CONFIG_ARCH_HAVE_DPFPU=y And this looks like an interesting thing to check: f446re has: # # Interrupt options # CONFIG_ARCH_HAVE_INTERRUPTSTACK=y CONFIG_ARCH_INTERRUPTSTACK=2048 CONFIG_ARCH_HAVE_HIPRI_INTERRUPT=y # CONFIG_ARCH_HIPRI_INTERRUPT is not set while h743zi has: # # Interrupt options # CONFIG_ARCH_HAVE_INTERRUPTSTACK=y CONFIG_ARCH_INTERRUPTSTACK=0 CONFIG_ARCH_HAVE_HIPRI_INTERRUPT=y # CONFIG_ARCH_HIPRI_INTERRUPT is not set Thoughts? Nathan
