Build failed in Jenkins: NuttX-Nightly-Build #119

See Changes: -- Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H27 (ubuntu) in workspace

Re: errno feature branch

I have just create a branch called 'errno' in both incubator_nuttx and incubator_nuttx_apps.  This is where we will be implementing new errno support as documented in Issue #986 "Userspace errno" (https://github.com/apache/incubator-nuttx/issues/986) The implementation is not so complex tha

stm32_allocateheap.c and CONFIG_MM_REGIONS

As part of the port to the STM32G4, I'm in stm32_allocateheap.c and trying to understand the correct definitions for this chip. As a starting point, I am following the patterns elsewhere in this file. In terms of RAM, the STM32G47xx has: * 96KiB of internal RAM in 2 banks * 32 KiB of CCM

Re: Espressif noting NuttX as target platform for ESP32

On Thu, May 7, 2020 at 6:18 PM Matias N. wrote: > I just found this: https://www.linkedin.com/jobs/view/1825702551/ > > One of the target responsibilities is: > "1. Develop and improve support for Espressif chips in RTOSes (such as > Zephyr, NuttX) and frameworks (MicroPython, Arduino)." > > Mayb

Espressif noting NuttX as target platform for ESP32

I just found this: https://www.linkedin.com/jobs/view/1825702551/ One of the target responsibilities is: "1. Develop and improve support for Espressif chips in RTOSes (such as Zephyr, NuttX) and frameworks (MicroPython, Arduino)." Maybe this will mean that WiFi/Bluetooth access should be possibl

Re: New unused variables warning in nx_start()

The PR is #996. https://github.com/apache/incubator-nuttx/pull/996 Cheers, Nathan

Re: New unused variables warning in nx_start()

I have some new insights about what happened here. The compiler warnings in nx_start.c that were the reason I started this thread: init/nx_start.c: In function 'nx_start': init/nx_start.c:552:14: warning: unused variable 'heap_size' [-Wunused-variable] size_t heap_size; ^

Re: New unused variables warning in nx_start()

On Thu, May 7, 2020 at 1:30 PM Gregory Nutt wrote: > > On 5/7/2020 11:29 AM, Nathan Hartman wrote: > > On Thu, May 7, 2020 at 12:49 PM Gregory Nutt wrote: > >> No.. this code was broken with with commit > >> eca70597858bc619d3114901d16e4a30f1ebffbe . There is no point trying to > >> make sense o

Re: Adding support for STM32G474RET6

On Thu, May 7, 2020 at 1:18 PM raiden00pl . wrote: > A new branch is a good idea, but I think we should squash as many commits > as possible before PRs to > avoid noise in the git history. Especially when it comes to new chip > specific files. Agreed. I was thinking to squash the chip support int

Re: New unused variables warning in nx_start()

On 5/7/2020 11:29 AM, Nathan Hartman wrote: On Thu, May 7, 2020 at 12:49 PM Gregory Nutt wrote: No.. this code was broken with with commit eca70597858bc619d3114901d16e4a30f1ebffbe . There is no point trying to make sense out of this. It is just broken and needs to be fixed. (snip) So there

Re: New unused variables warning in nx_start()

On Thu, May 7, 2020 at 12:49 PM Gregory Nutt wrote: > No.. this code was broken with with commit > eca70597858bc619d3114901d16e4a30f1ebffbe . There is no point trying to > make sense out of this. It is just broken and needs to be fixed. (snip) > So there is not a lot of sense in us discussing

Re: Adding support for STM32G474RET6

> STM32L4R also has DMAMUX with two DMAx controllers. Maybe it is closer match for STM32G4 than H7. Yes, you are right. STM32L4R is definitely a better choice. > Can we put my stm32g474 branch into the main NuttX repository (as a > branch, not in master) and split the work? I have ~50 commits and

Re: New unused variables warning in nx_start()

When doing a FLAT build, do we ever build nx_start.c twice, once with __KERNEL__ and once without? (In my configuration, it is built only once.) No Regarding the code: /* Initialize the memory manager */ { FAR void *heap_start; size_t heap_size; #ifdef MM_KERNEL_USRHE

Re: New unused variables warning in nx_start()

On Thu, May 7, 2020 at 12:21 PM Gregory Nutt wrote: > In the build, we build both user space code and internal OS code. > __KERNEL__, if defined means that we are currently building the internal > OS code. That allows the same files to be build differently depending > on if it is inside our outsi

Re: New unused variables warning in nx_start()

But I don't understand this logic: When does !defined(CONFIG_BUILD_KERNEL) && defined(__KERNEL__) happen? In the build, we build both user space code and internal OS code.  __KERNEL__, if defined means that we are currently building the internal OS code.  That allows the same files to be build

Re: New unused variables warning in nx_start()

On Thu, May 7, 2020 at 1:48 AM Xiang Xiao wrote: > > Yes, I remove #if/#endif intentionally because it doesn't make sense that > user disable all three method which provide the critical memory info to OS. > > -Original Message- > From: Abdelatif Guettouche > Sent: Thursday, May 7, 2020 1

errno feature branch

FYI.. I have just create a branch called 'errno' in both incubator_nuttx and incubator_nuttx_apps.  This is where we will be implementing new errno support as documented in Issue #986 "Userspace errno" (https://github.com/apache/incubator-nuttx/issues/986) The implementation is not so comple

Re: Adding support for STM32G474RET6

On Thu, May 7, 2020 at 1:25 AM raiden00pl . wrote: > I got my NUCLEO-G431RB so I can help. How shall we proceed? Can we put my stm32g474 branch into the main NuttX repository (as a branch, not in master) and split the work? I have ~50 commits and ~7000 lines so far. I think it will be better to

Re: Adding support for STM32G474RET6

Hello, STM32L4R also has DMAMUX with two DMAx controllers. Maybe it is closer match for STM32G4 than H7. Check: https://github.com/apache/incubator-nuttx/blob/master/arch/arm/src/stm32l4/stm32l4xrxx_dma.c https://github.com/apache/incubator-nuttx/blob/master/arch/arm/src/stm32l4/hardware/stm