You are right. I used your changes and build using -u and I still have the same issue (the board does not bootup). This is what I can see on the serial port:
ADE > up_assert: Assertion failed at file:mm_heap/mm_malloc.c line: 262 task: > Idle Task Will start to debug - there might be a problem in my configuration. Thanks for fixing the build on Ubuntu! Edi On Wed, Oct 14, 2020 at 6:13 AM Xiang Xiao <xiaoxiang781...@gmail.com> wrote: > The fix is here: > https://github.com/apache/incubator-nuttx/pull/1986 > But Edi, can you boot the image built with -u option? I don't think there > is any real difference between -u option and -l option in Ubuntu On > Windows. If the image built with -l can't work, the image with -u should > not work too. > > On Wed, Oct 14, 2020 at 6:24 AM Gregory Nutt <spudan...@gmail.com> wrote: > > > I created issue: https://github.com/apache/incubator-nuttx/issues/1985 > > > > On 10/13/2020 4:15 PM, Gregory Nutt wrote: > > > > > >> Yes, renaming the mkconfig*.exe* to mkconfig did the trick. > > >> I had the same problem with mkversion*.exe* - renamed it to mkversion > > and > > >> the build worked fine. > > >> > > >> If I get some time tomorrow, I will try to find the commit that messed > > up > > >> the extension. > > > > > > Got it! Okay, this was easy once you know it is only the HOSTEXEXT > > > that is screwed up. That is defined in tools/Config.mk and the > > > definition there in WRONG! > > > > > > 116 ifeq ($(CONFIG_HOST_WINDOWS),y) > > > 117 HOSTEXEEXT ?= .exe > > > 118 endif > > > > > > When Ubuntu it selects CONFIG_HOST_WINDOWS=y but the HOSTEXEEXT should > > > be an empty string, not .exe. That is the root cause of the problem. > > > > > > This is commit 567962bd626 introduced the error > > > > > > commit 567962bd6263bf8809fb63c739f6ec668c69c416 > > > Author: Xiang Xiao <xiaoxi...@xiaomi.com> > > > Date: Tue May 19 18:29:28 2020 +0800 > > > > > > build: Move the extension definition to common place > > > > > > Signed-off-by: Xiang Xiao <xiaoxi...@xiaomi.com> > > > > > > This should be fixed in the 10.0 release. I will open an issue. > > > > > > Thanks for your patience in getting to the bottom of this, Ed, > > > > > > Greg > > > > > > > > > > > > > > > > >
