Hi, all:
NuttX nightly build is coming now:
https://builds.apache.org/job/NuttX-Nightly-Build/
Now it's a freestyle project CI job. It could switch to pipeline CI job
later which is more functional as Miguel has proposaled.
Nightly build job schedule settings as below:
a. Build Triggers:
The j
HI all,
On my S32K148EVB board I'm trying to compile the "C++ test program" using the
gcc-arm-none-eabi-7-2017-q4-major toolchain. however I'm running C++ header
issues. I've checked the "integrating with newlib" documentation (located at
https://cwiki.apache.org/confluence/display/NUTTX/Integr
Hi Peter,
There could be many reasons, for example if your
CONFIG_NSH_DISABLE_ITEF is enable, etc...
$ cd apps/
$ git grep "not valid in this context"
nshlib/nsh_parse.c:const char g_fmtcontext[]= "nsh: %s: not
valid in this context\n";
Please take a look, this is a good exercise to mast
Now the nightly build include all most boards under arm, mips, risc-v,
sim and x86, there is still some improvement need from community:
1.Some boards under arm, risc-v and sim still can't pass the build,
you can see the full list here(start with -):
https://github.com/apache/incubator-nuttx-
As I remember correctly, Brennan want to take the release manager role
to finish the first release.
On Thu, Feb 27, 2020 at 9:24 AM Nathan Hartman wrote:
>
> On Wed, Feb 26, 2020 at 8:05 PM Justin Mclean
> wrote:
> > Where is the project at in moving forward to make it’s next release?
>
> I thi
xiaoxiang781216 opened a new pull request #10: Revert "fulllist: remove
sim:mtdpart and sim:mtdrwb configs"
URL: https://github.com/apache/incubator-nuttx-testing/pull/10
since INFRA fix this issue:
https://github.com/apache/infrastructure-p6/pull/258
---
xiaoxiang781216 commented on issue #4: Add prebuilt gperf needed in
kconfig-frontends configure
URL:
https://github.com/apache/incubator-nuttx-testing/pull/4#issuecomment-591956401
Create a JIRA for gperf:
https://issues.apache.org/jira/browse/INFRA-19896
--
With the nightly build in place, we would want to wait for some clean
builds to consider a release.
We want to make sure that the code is stable enough.
However, we can make progress by taking care of some of Apache's requirements.
Justin, summarized what we should do in an earlier thread. [1]
Fir
I am unclear about the build status and what has been added and if all the
configs are in the test list. As I read the email from Xiang Xiao - all the
builds do not build yet. I thought in the past ALL the builds were built
before a release.
-Original Message-
From: Abdelatif Guettouche
However, we can make progress by taking care of some of Apache's requirements.
Justin, summarized what we should do in an earlier thread. [1]
First thing is to created DISCLAIMER, LICENSE and NOTICE files.
I created a draft PR
(https://github.com/apache/incubator-nuttx/pull/392) where I added
t
Yes, it's better to let all config pass the build before release, now
we still has 77(total 582) config not add to the nightly build list,
because:
1.Fail to compile
2.Depends on the 3rd party library
3.Can't find the toolchain
4.Need Windows
Since we don't work on these arch/host, it's better to t
On Thu, Feb 27, 2020 at 8:15 AM Abdelatif Guettouche
wrote:
> We also need to define our release process.
> Something like:
> Create a branch from master that will serve as a release candidate.
> Make the necessary modifications in preparation of a release (update
> release notes, documentation, e
On Thu, Feb 27, 2020 at 8:55 AM Gregory Nutt wrote:
> The existing ChangeLog and ReleaseNotes files will not be maintained;
> they may as well be deleted as well.
I don't understand. Don't projects usually have a CHANGES file and
release notes? We should tell people what's so great about this
rel
Hi,
I'm working trying to get NuttX working on the SAMA5D2-XULT board. I can't
seem to get the UART1 serial port working with NuttX, or the FLEXCOM
USARTs.
NuttX seems to boot ok... I can load code via J-Link, and in the debugger
it lands in nsh_main. But there's no output on the serial console.
Hi Alan,
yes I looked in the source code and I think the reality clashes with the
documentation, which says about loops: "...These work from the command line
but are primarily intended for use within NSH scripts".
I think the code expects loops only in scripts files and not directly in
console, be
I would look closely at the pins on the schematic and carefully verify
how you have the Tx/Rx pins configured.
I'm working trying to get NuttX working on the SAMA5D2-XULT board. I can't
seem to get the UART1 serial port working with NuttX, or the FLEXCOM
USARTs.
NuttX seems to boot ok... I can l
yes I looked in the source code and I think the reality clashes with the
documentation, which says about loops: "...These work from the command line
but are primarily intended for use within NSH scripts".
I think the code expects loops only in scripts files and not directly in
console, because
> but we need to determine how
> many minimum PPMC / IPMC signatures are required to release.
Do we need to determine the number of signatures? Doesn't the RM's
signature suffice?
(I believe I read this in the documentation, but it's kind of hard to
go back and retrieve the relevant article).
The
On Thu, Feb 27, 2020 at 5:43 PM Abdelatif Guettouche
wrote:
>
> > but we need to determine how
> > many minimum PPMC / IPMC signatures are required to release.
> Do we need to determine the number of signatures? Doesn't the RM's
> signature suffice?
> (I believe I read this in the documentation, b
I'm still happy to do this. I have just not been available the last few
weeks. I'll set aside some time this weekend though to at least get the
disclaimer and notice in, as well as some low hanging fruit around the
license headers.
--Brennan
On Thu, Feb 27, 2020, 3:16 AM Xiang Xiao wrote:
> As
Greg,
Thanks, will check that again. I used the Flexcoms that are labeled on the
board itself (Flexcom 0, 3, and 4) and looked at the pinouts. I also used
the debug UART1 that works with U-Boot and Linux...
I'll also try using a logic analyzer to see if there is any output at all.
-adam
On Thu,
Thanks, will check that again. I used the Flexcoms that are labeled on the
board itself (Flexcom 0, 3, and 4) and looked at the pinouts. I also used
the debug UART1 that works with U-Boot and Linux...
Not good enough. you also have to set the pin multiplexing in the
board.h header file. You hav
Thanks. Will do this.
-adam
On Thu, Feb 27, 2020 at 5:13 PM Gregory Nutt wrote:
> > Thanks, will check that again. I used the Flexcoms that are labeled on
> the
> > board itself (Flexcom 0, 3, and 4) and looked at the pinouts. I also used
> > the debug UART1 that works with U-Boot and Linux...
Hi,
I noticed that both the armv7m and x86 port of nuttx's signal sending
procedure cannot handle nested signals.
I am wondering that in the up_sigdeliver functions.
A task A, being signaled, is possibile to be switch-out because of
1. calling syslog via sinfo
2. interrupts
A newly switched in
Hi, Justin,
I have noticed the latest NuttX nightly build in
https://builds.apache.org/job/NuttX-Nightly-Build/46/console which build
breaks and sent email log as below.
But the dev maillist hasn't got the jenkins fail email notice. Could you
please help look into this or should we ask help from
25 matches
Mail list logo
