Re: nuttx\arch\arm\src\stm32h7\stm32_spi.c uses txresult even when SPI_DMA is not defined

2020-10-16 Thread Eduard Niesner
oticed that the "nxsem_wait_uninterruptible(&priv->txsem)" is > already inside a "#ifdef CONFIG_STM32H7_SPI_DMA", so your modification > will make the logic symmetric. > > You just need to create a fork, do your modification and submit a PR. > > BR, > > Alan

Re: nuttx\arch\arm\src\stm32h7\stm32_spi.c uses txresult even when SPI_DMA is not defined

2020-10-16 Thread Eduard Niesner
t to .txt to get it here. > > BTW, you can submit a Pull Request directly to > https://github.com/apache/incubator-nuttx and we could review it. > > BR, > > Alan > > On 10/16/20, Eduard Niesner wrote: > > Hi all, > > > > I am not familiar with the cod

Re: Cannot build H7 configuration using Ubuntu for Windows 10

2020-10-16 Thread Eduard Niesner
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

nuttx\arch\arm\src\stm32h7\stm32_spi.c uses txresult even when SPI_DMA is not defined

2020-10-16 Thread Eduard Niesner
Hi all, I am not familiar with the code from nuttx\arch\arm\src\stm32h7\stm32_spi.c but I believe that there is an issue. "txresult" is defined and used only if the CONFIG_STM32H7_SPI_DMA is defined. But in the spi_interrupt function, the txresult is used regardless of whether CONFIG_STM32H7_SPI_D

Re: Cannot build H7 configuration using Ubuntu for Windows 10

2020-10-14 Thread Eduard Niesner
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

Re: Cannot build H7 configuration using Ubuntu for Windows 10

2020-10-13 Thread Eduard Niesner
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

Re: Cannot build H7 configuration using Ubuntu for Windows 10

2020-10-13 Thread Eduard Niesner
Guettouche < abdelatif.guettou...@gmail.com> wrote: > 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

Re: Cannot build H7 configuration using Ubuntu for Windows 10

2020-10-13 Thread Eduard Niesner
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

Re: Cannot build H7 configuration using Ubuntu for Windows 10

2020-10-13 Thread Eduard Niesner
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

Re: Cannot build H7 configuration using Ubuntu for Windows 10

2020-10-13 Thread Eduard Niesner
Any other suggestions? Edi On Tue, Oct 13, 2020 at 7:14 PM Brennan Ashton wrote: > 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

Cannot build H7 configuration using Ubuntu for Windows 10

2020-10-13 Thread Eduard Niesner
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 error. This is also reproducible on the current master. 1. ma

Re: Debugging Nuttx

2020-04-06 Thread Eduard Niesner
, 2020 at 12:29 AM Eduard Niesner wrote: > Thank you, Alexander! I will try your script in the next few days. > > I used objdump to generate the debug information for the libnuttx.a and > libapps.a and this is how the paths from the debug information look like: > >- Ubuntu

Re: Debugging Nuttx

2020-04-06 Thread Eduard Niesner
< a.oryshche...@gmail.com> wrote: > Hi Eduard, > > Sure > > just go to nuttx directory and apply it: > git apply 0001-Replace-Linux-symlinks-with-junction-on-WSL.diff > > I do it right after clone/checkout of Nuttx source > > -Alexander > > On Mon, Apr 6, 2020 a

Re: Debugging Nuttx

2020-04-06 Thread Eduard Niesner
ry and > > copy. But I have no idea about your first question. > > > > -Alexander > > > > вс, 5 апр. 2020 г., 23:12 Eduard Niesner : > > > >> Hi Alexander, > >> > >> I debug my application using Visual Studio and when I try to step-in a > >&

Re: Debugging Nuttx

2020-04-05 Thread Eduard Niesner
are accessible > under WSL (but at least for me inaccessible in Windows). But why do you > need to copy something here? > > -Alexander > > On Sat, Apr 4, 2020 at 11:39 PM Eduard Niesner > wrote: > > > Hi all, > > > > I am using the Nuttx build as a static library (*.

Debugging Nuttx

2020-04-04 Thread Eduard Niesner
Hi all, I am using the Nuttx build as a static library (*.a file) in my application and in order to debug Nuttx I have to do some steps that I did not have to do in the past: 1. Copy Nuttx and Apps folders to the following directory C:\SysGCC\arm-eabi\mnt\d\work\NuttxH7 - I know that