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

See Changes: -- [...truncated 304.48 KB...] Cleaning... Configuring... Copy files Select C

Re: [DISCUSS] NuttX 9.1 RC1

On Fri, Jul 3, 2020 at 7:44 PM Brennan Ashton wrote: > > Haitao, > Thanks for catching that. I suspect this might have been around for a > while in the zip releases. > The release script checks out a tag to make sure we are getting what > we expect so I dont think we cut the wrong code > > What l

Re: [DISCUSS] NuttX 9.1 RC1

Haitao, Thanks for catching that. I suspect this might have been around for a while in the zip releases. The release script checks out a tag to make sure we are getting what we expect so I dont think we cut the wrong code What looks to be going on is we have files in .gitignore that are being str

Re: SVD -> header generator

I just added support for bitfields. It defines the _SHIFT, _MASK and specific value definitions, as well as description as a comment. I tried to be clever about when not to print obvious values and to maintain a reasonable formatting. I think it works pretty well. You can see the output for RADI

Re: [DISCUSS] NuttX 9.1 RC1

I have just downloaded https://dist.apache.org/repos/dist/dev/incubator/nuttx/9.1.0-RC1/ and built sim:nsh which reports rcS missing as below. But I checked the release/9.1 branch with rcS change inside. So I wonder if the 9.1.0-RC1 is not align to the latest 9.1 branch code. make[1]: Entering dir

Re: SVD -> header generator

I agree with your understanding. I followed the same reasoning. If this data is on a public datasheet, the header is indistinguishable from one manually created from the SVD. Unless the text description of each register is considered some kind of original artwork, but that could be even omitted i

Re: SVD -> header generator

I just looked at that header and looks like a "no warranty" disclaimer. Does not impose any restriction on generation code based on that file. I am not an attorney and not qualified to give a legal opinion. But that has never stopped me before. A copyright covers the presentation of a mat

Re: SVD -> header generator

Both of these I also linked are far more restrictive: https://raw.githubusercontent.com/posborne/cmsis-svd/master/data/STMicro/License.html TI is another example with further restrictions. https://github.com/posborne/cmsis-svd/blob/master/data/TexasInstruments/TM4C123GH6ZRB.svd --Brennan On Fr

Re: SVD -> header generator

I just looked at that header and looks like a "no warranty" disclaimer. Does not impose any restriction on generation code based on that file. On Fri, Jul 3, 2020, at 18:25, Brennan Ashton wrote: > Just a warning on generating code from these files. Many of the have > explicit restrictions on us

RE: SVD -> header generator

Hi Matias, > I thought about doing this for a long time Yes So many times...Thank you for doing it! David -Original Message- From: Matias N. [mailto:mat...@imap.cc] Sent: Friday, July 03, 2020 1:45 PM To: dev@nuttx.apache.org Subject: SVD -> header generator Hi, I thought about doing t

Re: SVD -> header generator

It seems really strange to me that the output file of a code generator tool is something that would be within the scope of a license of the SVD file itself. If I were to write that same output myself by hand what would be different? Anyway, we can look further into the validity of that licensing

Re: SVD -> header generator

Brennan, Ah, I see. The data files all have their own individual licenses, yes, some are not open source. Ugh. Yeah, I wouldn't use a tool to generate it unless the data file was using a compatible license... -adam On Fri, Jul 3, 2020 at 3:30 PM Brennan Ashton wrote: > They are not all Apache

Re: SVD -> header generator

They are not all Apache 2.0. The NXP ones are a mixed bag, some call out BSD, some just liability disclaimer, looks like the example I gave was not the best one. For STM this file is restricted in a way that is not compatible. Personally I think that is a mistake on the part of STM, but here we ar

Re: SVD -> header generator

Brennan, All the files in this repo are Apache 2.0 licensed: https://github.com/posborne/cmsis-svd/blob/master/LICENSE-APACHE Doesn't that cover the license issue? The header is only a liability disclaimer. -adam On Fri, Jul 3, 2020 at 2:25 PM Brennan Ashton wrote: > Just a warning on gene

Re: SVD -> header generator

Just a warning on generating code from these files. Many of the have explicit restrictions on using them which may not be compatible with BSD or Apache. For example NXP https://github.com/posborne/cmsis-svd/blob/master/data/NXP/LPC1102_4_v4.svd I'm not sure on the legal side about this but it is

Re: SVD -> header generator

Very good Matias! Indeed, registers definition is a boring part of creating a new NuttX port, your tool makes it a breeze! BR, Alan On 7/3/20, Adam Feuer wrote: > Matias, > > This looks like it would be a lot of help bringing NuttX up on a new > microprocessor. Thanks! > > -adam > > On Fri, Ju

Re: SVD -> header generator

That's a great one! Does it do bitfields? I gave it a quick try and I only got register definitions. Regardless, that could be a great time saver! On Fri, Jul 3, 2020 at 9:57 PM Adam Feuer wrote: > > Matias, > > This looks like it would be a lot of help bringing NuttX up on a new > microprocess

Re: SVD -> header generator

Matias, This looks like it would be a lot of help bringing NuttX up on a new microprocessor. Thanks! -adam On Fri, Jul 3, 2020 at 1:46 PM Matias N. wrote: > Hi, > I thought about doing this for a long time and I just did it, wasn't > really hard. > If you're not aware, CMSIS-SVD file format is

SVD -> header generator

Hi, I thought about doing this for a long time and I just did it, wasn't really hard. If you're not aware, CMSIS-SVD file format is an XML based definitions of peripherals and registers available in a given MCU. This is typically used for debugging but it is quite useful for generating header de

Re: Scheduling work from a worker using the same work_s

Ok great, thanks Greg! On Fri, Jul 3, 2020 at 1:13 PM Gregory Nutt wrote: > > > I have a few spots in my code where I am doing something, and I'm just > now > > realizing I'm not explicitly sure if it's supported or not. > > > > Here is my question: > > > > Can work_queue be called from within

Re: Scheduling work from a worker using the same work_s

I have a few spots in my code where I am doing something, and I'm just now realizing I'm not explicitly sure if it's supported or not. Here is my question: Can work_queue be called from within a worker function that uses the same work_s struct? Yes. The documentation only says that if there

Re: BBC MicroBit (nRF51822) running NuttX

On Fri, Jul 3, 2020, at 13:32, Alan Carvalho de Assis wrote: > Hi Saito-san, > > You did an amazing work! > > I found you project by chance, I was searching for NuttX on Twitter > and found it. > > Maybe the I2C and SPI from nRF51 are similar to nRF52, so we could to > reuse it. I didn't compare

Re: BBC MicroBit (nRF51822) running NuttX

Hi Saito-san, You did an amazing work! I found you project by chance, I was searching for NuttX on Twitter and found it. Maybe the I2C and SPI from nRF51 are similar to nRF52, so we could to reuse it. I didn't compare them yet. Matias, did you? BR, Alan On 7/3/20, saito yutaka wrote: > Hello

Re: BBC MicroBit (nRF51822) running NuttX

Hello Saito, I just tested your code on my nrf51822 module and, after changing RX/TX pin definitions, I get console output. So I confirm your port is functional on real board. It would be cool if you could submit a PR against NuttX with your changes. I could try to work on it a bit as well, sinc

Scheduling work from a worker using the same work_s

Hi, I have a few spots in my code where I am doing something, and I'm just now realizing I'm not explicitly sure if it's supported or not. Here is my question: Can work_queue be called from within a worker function that uses the same work_s struct? The documentation only says that if there is e

Re: BBC MicroBit (nRF51822) running NuttX

Hello. Thanks for mail about my project. I don't have much knowledge of the real time os, so I'm writing code while looking it up. I've been able to confirm that Hello World works on micro:bit. And I could debug on micro:bit using gdb and pyocd. I haven't done other things such as lighting of t

Re: BBC MicroBit (nRF51822) running NuttX

Hi, I can take a look and see if this would work on my nrf51822. Stil, it would be better to have the code author prepare a PR against NuttX. I see recent commits so it appears an actively maintained WIP. On a related subject: I have ordered an NRF52832 board and module, for which my ultimate i

Re: Problem booting when using Nuttx on Qemu x86_64

Hi, I have tested it on my machine. Using commit deb3b13759fe08 , I can successfully boot into nsh. For your reference, the following are my environments. Build machine: - Windows10 WSL2 18.04 - gcc (Ubuntu 9.3.0-11ubuntu0~18.04.1) 9.3.0 Execute machine: - Ubuntu 18.04 - Xeon 2650 v4 / 16G

Re: How to debug DEBUGASSERT in shed?

Hi, Alan. Thanks for the feedback. Found out that I'm still get DEBUGASSERT(pholder != NULL) in function nxsem_allocholder in file semaphore/sem_holder.c after DEBUGASSERT(sem->semcount: > Hi Oleg, > > I just responded your issue. > > I hope to have shed some light there. > > BR, > > Alan > > On

Re: Problem booting when using Nuttx on Qemu x86_64

In addition, may I have your processor model please. The Intel processors feature set varys quite a lot. Maybe some feature settings are considered improper for your processor, causing a GP. BR, -- Yang Chung Fan (楊宗凡) (ヤン　ゾン　ファン)

Re: Problem booting when using Nuttx on Qemu x86_64

Hi, Good to hear more people trying our nuttx on x86_64. > I am trying to run nuttx in a Qemu x86_64 VM but seem to be hitting some > issue during early boot (as far as I can tell). I am using commit > deb3b13759fe08 ("Udate TODO List") from yesterday. That's quite new. I was recently working wi

Re: How to debug DEBUGASSERT in shed?

Hi Olev, I just responded your issue. I hope to have shed some light there. BR, Alan On 7/3/20, Oleg Evseev wrote: > Regarding to can driver, from some moment I started getting > DEBUGASSERT(sem->semcount in sem_post.c. Found the bug > https://github.com/apache/incubator-nuttx/issues/1354 > >

Re: How to debug DEBUGASSERT in shed?

Regarding to can driver, from some moment I started getting DEBUGASSERT(sem->semcounthttps://github.com/apache/incubator-nuttx/issues/1354 I don't know, was DEBUGASSERT(pholder != NULL) a different appearance of the same bug or it is something else. -- With regards, Oleg. вт, 30 июн. 2020 г. в