ay, October 16, 2020 11:32 PM
> > To: dev@nuttx.apache.org
> > Subject: Re: Cannot build H7 configuration using Ubuntu for Windows 10
> >
> > I debugged and found what my problem was. I am using a custom
> configuration for a custom board and did not notice that the
> > M
ndows.
> -Original Message-
> From: Eduard Niesner
> Sent: Friday, October 16, 2020 11:32 PM
> To: dev@nuttx.apache.org
> Subject: Re: Cannot build H7 configuration using Ubuntu for Windows 10
>
> I debugged and found what my problem was. I am using a custom configuration
&g
I debugged and found what my problem was. I am using a custom configuration
for a custom board and did not notice that the Make.defs and flash.ld
changed for H7 between Nuttx 9.0 and Nuttx 9.1. My configuration was still
using the old ones from 9.0.
This is why even though the build worked it was c
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
This is debug output from arch/arm/src/stm32h7/start.c. The hang occurs
somewhere after line 412 ( showprogress('E');), and prob
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 i
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.
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 tom
I am glad that you found the issue.
Thanks for your patience and support!
Edi
On Wed, Oct 14, 2020 at 1:15 AM 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
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 i
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.
Thanks!
On Wed, Oct 14, 2020 at 12:50 AM Abdelatif
It looks like the extension got messed up. If that's the case
renaming mkconfig.exe to mkconfig should at least build.
Either that, or configure.sh and/or sethost.sh set up for the wrong
host. When you select Ubuntu with the -u option, sethost.sh should set
the host to Windows, but the env
It looks like the extension got messed up. If that's the case
renaming mkconfig.exe to mkconfig should at least build.
On Tue, Oct 13, 2020 at 10:45 PM Eduard Niesner wrote:
>
> Yeah, there is definitely something wrong - I just tried again (ubuntu for
> windows 10).
>
>1. Cleaned everythin
Yeah, there is definitely something wrong - I just tried again (ubuntu for
windows 10).
1. Cleaned everything (git clean and make distclean)
2. checked that the *mkconfig.exe* or any other *mkconfig *binary does
not exist in the tools folder
3. called './tools/configure.sh -u nucleo-h
I used 'make V=1' and I saw that mkconfig is being built successfully.
root@edi-laptop:/mnt/d/Work/Development/Git/GitHub/nuttx# make V=1
make -C tools -f Makefile.host mkconfig.exe
make[1]: Entering directory
'/mnt/d/Work/Development/Git/GitHub/nuttx/tools'
No, the binary tools/mkconfig
I used 'make V=1' and I saw that mkconfig is being built successfully.
root@edi-laptop:/mnt/d/Work/Development/Git/GitHub/nuttx# make V=1
make -C tools -f Makefile.host mkconfig.exe
make[1]: Entering directory
'/mnt/d/Work/Development/Git/GitHub/nuttx/tools'
No, the binary tools/mkconfig is
> root@edi-laptop:/mnt/d/Work/Development/Git/GitHub/nuttx# make V=1
> make -C tools -f Makefile.host mkconfig.exe
> I also checked the tools directory and there is a mkconfig.exe
When you build using Ubuntu for Windows 10 you get a *.exe file?
The error is that tools/mkconfig is not found. This
I used 'make V=1' and I saw that mkconfig is being built successfully.
> root@edi-laptop:/mnt/d/Work/Development/Git/GitHub/nuttx# make V=1
> make -C tools -f Makefile.host mkconfig.exe
> make[1]: Entering directory
> '/mnt/d/Work/Development/Git/GitHub/nuttx/tools'
>
I also checked the too
/bin/sh: 1: tools/mkconfig: not found
tools/Makefile.unix:247: recipe for target 'include/nuttx/config.h' failed
make: *** [include/nuttx/config.h] Error 127
Your problem is not that kconfig-frontends is not being built, but
rathter that tools/mkconfig is not being built. That should happen
Thank you for your suggestion.
I already had kconfig-frontends installed because the build works with no
issues on older versions of Nuttx (tag 8.1 and tag 9.0 for example). It
stopped working on tag 9.1.
I tried to reinstall kconfig-frontends using the link you provided and I
run the three steps
On Tue, Oct 13, 2020, 9:08 AM Eduard Niesner
wrote:
> Hi all,
>
> I am getting some build issues when I try to build nucleo-h743zi
> configuration using Ubuntu for Windows 10.
>
> I used to execute the following commands in order to build Nuttx. But
> starting Nuttx 9.1 I am getting the following
20 matches
Mail list logo
