date:20231009

[VOTE] Apache NuttX 12.3.0 RC0 release

2023-10-09 Thread Alin Jerpelea

Hello all,
Apache NuttX 12.3.0 RC0 has been staged under [1] and it's
time to vote on accepting it for release. Voting will be open for 72hr.

A minimum of 3 binding +1 votes and more binding +1 than binding -1 are
required to pass.

The Apache requirements for approving a release can be found here [3]
"Before voting +1 PMC members are required to download the signed
source code package, compile it as provided, and test the resulting
executable on their own platform, along with also verifying that the
package meets the requirements of the ASF policy on releases."

A document to walk through some of this process has been published on
our project wiki and can be found here [4].

[ ] +1 accept (indicate what you validated - e.g. performed the non-RM
items in [4])
[ ] -1 reject (explanation required)

Thank you all,
Alin Jerpelea

SCM Information:
  Release tag: nuttx-12.3.0-RC0
  Hash for the release nuttx tag: 1d349a2a32f76de1b686099dd6e7e0ceeddb6a80
  Hash for the release nuttx-apps tag: 2d6d199c492196c4680ae7f5b97bb6e2a7b38649

[1] https://dist.apache.org/repos/dist/dev/nuttx/12.3.0-RC0/
[2] https://raw.githubusercontent.com/apache/nuttx/nuttx-12.3.0-RC0/ReleaseNotes
[3] https://www.apache.org/dev/release.html#approving-a-release
[4] 
https://cwiki.apache.org/confluence/display/NUTTX/Validating+a+staged+Release

Re: [VOTE] Apache NuttX 12.3.0 RC0 release

2023-10-09 Thread Lee, Lup Yuen

+1 for PinePhone and Star64

Minor Issue: Building on macOS shows "sed: illegal option -- r", probably
because macOS sed works differently from Linux. I'll track down the PR that
caused this.

Here are the sed messages:
https://gist.github.com/lupyuen/1c3f1f1d71993609bed3b31767595beb#file-pinephone-release-log-L282-L512

= PinePhone Compiler
+ aarch64-none-elf-gcc -v
Using built-in specs.
COLLECT_GCC=aarch64-none-elf-gcc
COLLECT_LTO_WRAPPER=/Applications/ArmGNUToolchain/11.3.rel1/aarch64-none-elf/bin/../libexec/gcc/aarch64-none-elf/11.3.1/lto-wrapper
Target: aarch64-none-elf
Configured with:
/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/src/gcc/configure
--target=aarch64-none-elf
--prefix=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/install
--with-gmp=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/host-tools
--with-mpfr=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/host-tools
--with-mpc=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/host-tools
--with-isl=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/host-tools
--disable-shared --disable-nls --disable-threads --disable-tls
--enable-checking=release --enable-languages=c,c++,fortran --with-newlib
--with-gnu-as --with-gnu-ld
--with-sysroot=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/install/aarch64-none-elf
--with-pkgversion='Arm GNU Toolchain 11.3.Rel1' --with-bugurl=
https://bugs.linaro.org/
Thread model: single
Supported LTO compression algorithms: zlib
gcc version 11.3.1 20220712 (Arm GNU Toolchain 11.3.Rel1)

= PinePhone Configuration
+ ./tools/configure.sh pinephone:nsh

= PinePhone Size
+ aarch64-none-elf-size nuttx
   text   databssdechex filename
 223895  12913  41612 278420  43f94 nuttx

= PinePhone NSH Info and Free
NuttShell (NSH) NuttX-12.3.0
nsh> uname -a
NuttX 12.3.0 1d349a2a32 Oct  9 2023 16:15:01 arm64 pinephone
nsh> free
   total   used   freelargest  nused  nfree
Umem:  133406712 551512  132855200  132855104 58  2

= Star64 Compiler
+ riscv64-unknown-elf-gcc -v
Using built-in specs.
COLLECT_GCC=riscv64-unknown-elf-gcc
COLLECT_LTO_WRAPPER=/Users/Luppy/riscv64-unknown-elf-toolchain-10.2.0-2020.12.8-x86_64-apple-darwin/bin/../libexec/gcc/riscv64-unknown-elf/10.2.0/lto-wrapper
Target: riscv64-unknown-elf
Configured with:
/scratch/jenkins/workspace/tpp-freedom-tools/tpp01--build-binary-packages--parameterized/obj/x86_64-apple-darwin/build/riscv64-unknown-elf-gcc/riscv-gcc/configure
--target=riscv64-unknown-elf
--prefix=/scratch/jenkins/workspace/tpp-freedom-tools/tpp01--build-binary-packages--parameterized/obj/x86_64-apple-darwin/install/riscv64-unknown-elf-gcc-10.2.0-2020.12.8-x86_64-apple-darwin
--with-pkgversion='SiFive GCC-Metal 10.2.0-2020.12.8' --with-bugurl=
https://github.com/sifive/freedom-tools/issues --disable-shared
--disable-threads --enable-languages=c,c++ --enable-tls --with-newlib
--with-sysroot=/scratch/jenkins/workspace/tpp-freedom-tools/tpp01--build-binary-packages--parameterized/obj/x86_64-apple-darwin/install/riscv64-unknown-elf-gcc-10.2.0-2020.12.8-x86_64-apple-darwin/riscv64-unknown-elf
--with-native-system-header-dir=/include --disable-libmudflap
--disable-libssp --disable-libquadmath --disable-libgomp --disable-nls
--disable-tm-clone-registry --src=../riscv-gcc --with-system-zlib
--enable-checking=yes --enable-multilib --with-abi=lp64d
--with-arch=rv64imafdc CFLAGS=-O2 CXXFLAGS=-O2 'CFLAGS_FOR_TARGET=-Os
-mcmodel=medany' 'CXXFLAGS_FOR_TARGET=-Os -mcmodel=medany'
Thread model: single
Supported LTO compression algorithms: zlib
gcc version 10.2.0 (SiFive GCC-Metal 10.2.0-2020.12.8)

= Star64 Configuration
+ ./tools/configure.sh star64:nsh

= Star64 Size
+ riscv64-unknown-elf-size nuttx
   text   databssdechex filename
 168996641  23984 193621  2f455 nuttx

= Star64 NSH Info and Free
NuttShell (NSH) NuttX-12.3.0
nsh> uname -a
NuttX 12.3.0 1d349a2a32 Oct  9 2023 17:08:13 risc-v star64
nsh> free
   total   used   freelargest  nused  nfree
Kmem:2065400  1460020508002049440 50  3
Page:   20971520 643072   20328448   20328448

PinePhone Release Script:
https://gist.github.com/lupyuen/fbc2d0b7fb5dfbc62b4f9b3aae8626ea

PinePhone Release Log:
https://gist.github.com/lupyuen/1c3f1f1d71993609bed3b31767595beb

Star64 Release Script:
https://gist.github.com/lupyuen/f19eb54140a1d09811d42ed143810b36

Star64 Release Log:
https://gist.github.com/lupyuen/0ea8f3ac61e07d8b6e308e31ed5f7734

Lup

On Mon, Oct 9, 2023 at 3:27 PM Alin Jerpelea  wrote:

> Hello all,
> Apache NuttX 12.3.0 RC0 has been staged under [1] and it's
> time to vote on accepting it for release. Voting will be open for 72hr.
>
> A minimum of 3 binding +1 votes and more binding +1 than binding -1 are
> required to pa

RE: IMXRT: LPUART IDLE character Kconfig setting request

2023-10-09 Thread David Sidrane

What about adding it per [LP]U[S]ART in the Kconfig here
https://github.com/apache/nuttx/tree/master/drivers/serial

Then any arch can use it.

David

-Original Message-
From: Daniel Appiagyei 
Sent: Monday, October 9, 2023 12:51 AM
To: dev@nuttx.apache.org
Subject: IMXRT: LPUART IDLE character Kconfig setting request

Hi,
The IMXRT's LPUARTs have support for configuring the number of idle
characters it receives over UART before setting the STAT register's IDLE
flag. The setting is in CTRL[IDLECFG].
Are anyone imxrt users already planning to add support for this in master?
I will do so if not.
Will place the appropriate configs in
https://github.com/apache/nuttx/blob/master/arch/arm/src/imxrt/Kconfig

Best,

Daniel

Re: IMXRT: LPUART IDLE character Kconfig setting request

2023-10-09 Thread Petro Karashchenko

I think ESP32 also has IDLE cycles configuration for UART, so adding it as
serial generic config makes sense to me.

пн, 9 жовт. 2023 р. о 12:51 David Sidrane  пише:

> What about adding it per [LP]U[S]ART in the Kconfig here
> https://github.com/apache/nuttx/tree/master/drivers/serial
>
> Then any arch can use it.
>
> David
>
> -Original Message-
> From: Daniel Appiagyei 
> Sent: Monday, October 9, 2023 12:51 AM
> To: dev@nuttx.apache.org
> Subject: IMXRT: LPUART IDLE character Kconfig setting request
>
> Hi,
> The IMXRT's LPUARTs have support for configuring the number of idle
> characters it receives over UART before setting the STAT register's IDLE
> flag. The setting is in CTRL[IDLECFG].
> Are anyone imxrt users already planning to add support for this in master?
> I will do so if not.
> Will place the appropriate configs in
> https://github.com/apache/nuttx/blob/master/arch/arm/src/imxrt/Kconfig
>
> Best,
>
> Daniel
>

Re: [VOTE] Apache NuttX 12.3.0 RC0 release

2023-10-09 Thread Daniel Appiagyei

Hi all,
Is there a publicly available schedule of future releases?

Additionally, there are some bugs in master for my chip’s (IMXRT) DMA
serial driver I had planned to address later this week. Would it be
possible for that to make an RC1 release?

On Mon, Oct 9, 2023 at 2:24 AM Lee, Lup Yuen  wrote:

> +1 for PinePhone and Star64
>
> Minor Issue: Building on macOS shows "sed: illegal option -- r", probably
> because macOS sed works differently from Linux. I'll track down the PR that
> caused this.
>
> Here are the sed messages:
>
> https://gist.github.com/lupyuen/1c3f1f1d71993609bed3b31767595beb#file-pinephone-release-log-L282-L512
>
> = PinePhone Compiler
> + aarch64-none-elf-gcc -v
> Using built-in specs.
> COLLECT_GCC=aarch64-none-elf-gcc
>
> COLLECT_LTO_WRAPPER=/Applications/ArmGNUToolchain/11.3.rel1/aarch64-none-elf/bin/../libexec/gcc/aarch64-none-elf/11.3.1/lto-wrapper
> Target: aarch64-none-elf
> Configured with:
> /Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/src/gcc/configure
> --target=aarch64-none-elf
>
> --prefix=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/install
>
> --with-gmp=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/host-tools
>
> --with-mpfr=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/host-tools
>
> --with-mpc=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/host-tools
>
> --with-isl=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/host-tools
> --disable-shared --disable-nls --disable-threads --disable-tls
> --enable-checking=release --enable-languages=c,c++,fortran --with-newlib
> --with-gnu-as --with-gnu-ld
>
> --with-sysroot=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/install/aarch64-none-elf
> --with-pkgversion='Arm GNU Toolchain 11.3.Rel1' --with-bugurl=
> https://bugs.linaro.org/
> Thread model: single
> Supported LTO compression algorithms: zlib
> gcc version 11.3.1 20220712 (Arm GNU Toolchain 11.3.Rel1)
>
> = PinePhone Configuration
> + ./tools/configure.sh pinephone:nsh
>
> = PinePhone Size
> + aarch64-none-elf-size nuttx
>text   databssdechex filename
>  223895  12913  41612 278420  43f94 nuttx
>
> = PinePhone NSH Info and Free
> NuttShell (NSH) NuttX-12.3.0
> nsh> uname -a
> NuttX 12.3.0 1d349a2a32 Oct  9 2023 16:15:01 arm64 pinephone
> nsh> free
>total   used   freelargest  nused  nfree
> Umem:  133406712 551512  132855200  132855104 58  2
>
> = Star64 Compiler
> + riscv64-unknown-elf-gcc -v
> Using built-in specs.
> COLLECT_GCC=riscv64-unknown-elf-gcc
>
> COLLECT_LTO_WRAPPER=/Users/Luppy/riscv64-unknown-elf-toolchain-10.2.0-2020.12.8-x86_64-apple-darwin/bin/../libexec/gcc/riscv64-unknown-elf/10.2.0/lto-wrapper
> Target: riscv64-unknown-elf
> Configured with:
>
> /scratch/jenkins/workspace/tpp-freedom-tools/tpp01--build-binary-packages--parameterized/obj/x86_64-apple-darwin/build/riscv64-unknown-elf-gcc/riscv-gcc/configure
> --target=riscv64-unknown-elf
>
> --prefix=/scratch/jenkins/workspace/tpp-freedom-tools/tpp01--build-binary-packages--parameterized/obj/x86_64-apple-darwin/install/riscv64-unknown-elf-gcc-10.2.0-2020.12.8-x86_64-apple-darwin
> --with-pkgversion='SiFive GCC-Metal 10.2.0-2020.12.8' --with-bugurl=
> https://github.com/sifive/freedom-tools/issues --disable-shared
> --disable-threads --enable-languages=c,c++ --enable-tls --with-newlib
>
> --with-sysroot=/scratch/jenkins/workspace/tpp-freedom-tools/tpp01--build-binary-packages--parameterized/obj/x86_64-apple-darwin/install/riscv64-unknown-elf-gcc-10.2.0-2020.12.8-x86_64-apple-darwin/riscv64-unknown-elf
> --with-native-system-header-dir=/include --disable-libmudflap
> --disable-libssp --disable-libquadmath --disable-libgomp --disable-nls
> --disable-tm-clone-registry --src=../riscv-gcc --with-system-zlib
> --enable-checking=yes --enable-multilib --with-abi=lp64d
> --with-arch=rv64imafdc CFLAGS=-O2 CXXFLAGS=-O2 'CFLAGS_FOR_TARGET=-Os
> -mcmodel=medany' 'CXXFLAGS_FOR_TARGET=-Os -mcmodel=medany'
> Thread model: single
> Supported LTO compression algorithms: zlib
> gcc version 10.2.0 (SiFive GCC-Metal 10.2.0-2020.12.8)
>
> = Star64 Configuration
> + ./tools/configure.sh star64:nsh
>
> = Star64 Size
> + riscv64-unknown-elf-size nuttx
>text   databssdechex filename
>  168996641  23984 193621  2f455 nuttx
>
> = Star64 NSH Info and Free
> NuttShell (NSH) NuttX-12.3.0
> nsh> uname -a
> NuttX 12.3.0 1d349a2a32 Oct  9 2023 17:08:13 risc-v star64
> nsh> free
>total   used   freelargest  nused  nfree
> Kmem:2065400  1460020508002049440 50  3
> Page:   20971520 643072   20328448   20328448
>
> PinePhone Release Script:
> https://gist.github.com/lupyuen/fbc2d0b7fb5dfbc62b4f9b3aae8626ea
>
> PinePhone Release Log:
> https://gist.github.com/lupyuen/1c3

Re: [VOTE] Apache NuttX 12.3.0 RC0 release

2023-10-09 Thread Alin Jerpelea

Hi,
my aim is to do a release every 3 months
if you have the patches ready this week I would gladly do a MR1
Best regards
Alin

On Mon, 9 Oct 2023, 14:37 Daniel Appiagyei,
 wrote:

> Hi all,
> Is there a publicly available schedule of future releases?
>
> Additionally, there are some bugs in master for my chip’s (IMXRT) DMA
> serial driver I had planned to address later this week. Would it be
> possible for that to make an RC1 release?
>
> On Mon, Oct 9, 2023 at 2:24 AM Lee, Lup Yuen  wrote:
>
> > +1 for PinePhone and Star64
> >
> > Minor Issue: Building on macOS shows "sed: illegal option -- r", probably
> > because macOS sed works differently from Linux. I'll track down the PR
> that
> > caused this.
> >
> > Here are the sed messages:
> >
> >
> https://gist.github.com/lupyuen/1c3f1f1d71993609bed3b31767595beb#file-pinephone-release-log-L282-L512
> >
> > = PinePhone Compiler
> > + aarch64-none-elf-gcc -v
> > Using built-in specs.
> > COLLECT_GCC=aarch64-none-elf-gcc
> >
> >
> COLLECT_LTO_WRAPPER=/Applications/ArmGNUToolchain/11.3.rel1/aarch64-none-elf/bin/../libexec/gcc/aarch64-none-elf/11.3.1/lto-wrapper
> > Target: aarch64-none-elf
> > Configured with:
> > /Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/src/gcc/configure
> > --target=aarch64-none-elf
> >
> >
> --prefix=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/install
> >
> >
> --with-gmp=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/host-tools
> >
> >
> --with-mpfr=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/host-tools
> >
> >
> --with-mpc=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/host-tools
> >
> >
> --with-isl=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/host-tools
> > --disable-shared --disable-nls --disable-threads --disable-tls
> > --enable-checking=release --enable-languages=c,c++,fortran --with-newlib
> > --with-gnu-as --with-gnu-ld
> >
> >
> --with-sysroot=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/install/aarch64-none-elf
> > --with-pkgversion='Arm GNU Toolchain 11.3.Rel1' --with-bugurl=
> > https://bugs.linaro.org/
> > Thread model: single
> > Supported LTO compression algorithms: zlib
> > gcc version 11.3.1 20220712 (Arm GNU Toolchain 11.3.Rel1)
> >
> > = PinePhone Configuration
> > + ./tools/configure.sh pinephone:nsh
> >
> > = PinePhone Size
> > + aarch64-none-elf-size nuttx
> >text   databssdechex filename
> >  223895  12913  41612 278420  43f94 nuttx
> >
> > = PinePhone NSH Info and Free
> > NuttShell (NSH) NuttX-12.3.0
> > nsh> uname -a
> > NuttX 12.3.0 1d349a2a32 Oct  9 2023 16:15:01 arm64 pinephone
> > nsh> free
> >total   used   freelargest  nused  nfree
> > Umem:  133406712 551512  132855200  132855104 58  2
> >
> > = Star64 Compiler
> > + riscv64-unknown-elf-gcc -v
> > Using built-in specs.
> > COLLECT_GCC=riscv64-unknown-elf-gcc
> >
> >
> COLLECT_LTO_WRAPPER=/Users/Luppy/riscv64-unknown-elf-toolchain-10.2.0-2020.12.8-x86_64-apple-darwin/bin/../libexec/gcc/riscv64-unknown-elf/10.2.0/lto-wrapper
> > Target: riscv64-unknown-elf
> > Configured with:
> >
> >
> /scratch/jenkins/workspace/tpp-freedom-tools/tpp01--build-binary-packages--parameterized/obj/x86_64-apple-darwin/build/riscv64-unknown-elf-gcc/riscv-gcc/configure
> > --target=riscv64-unknown-elf
> >
> >
> --prefix=/scratch/jenkins/workspace/tpp-freedom-tools/tpp01--build-binary-packages--parameterized/obj/x86_64-apple-darwin/install/riscv64-unknown-elf-gcc-10.2.0-2020.12.8-x86_64-apple-darwin
> > --with-pkgversion='SiFive GCC-Metal 10.2.0-2020.12.8' --with-bugurl=
> > https://github.com/sifive/freedom-tools/issues --disable-shared
> > --disable-threads --enable-languages=c,c++ --enable-tls --with-newlib
> >
> >
> --with-sysroot=/scratch/jenkins/workspace/tpp-freedom-tools/tpp01--build-binary-packages--parameterized/obj/x86_64-apple-darwin/install/riscv64-unknown-elf-gcc-10.2.0-2020.12.8-x86_64-apple-darwin/riscv64-unknown-elf
> > --with-native-system-header-dir=/include --disable-libmudflap
> > --disable-libssp --disable-libquadmath --disable-libgomp --disable-nls
> > --disable-tm-clone-registry --src=../riscv-gcc --with-system-zlib
> > --enable-checking=yes --enable-multilib --with-abi=lp64d
> > --with-arch=rv64imafdc CFLAGS=-O2 CXXFLAGS=-O2 'CFLAGS_FOR_TARGET=-Os
> > -mcmodel=medany' 'CXXFLAGS_FOR_TARGET=-Os -mcmodel=medany'
> > Thread model: single
> > Supported LTO compression algorithms: zlib
> > gcc version 10.2.0 (SiFive GCC-Metal 10.2.0-2020.12.8)
> >
> > = Star64 Configuration
> > + ./tools/configure.sh star64:nsh
> >
> > = Star64 Size
> > + riscv64-unknown-elf-size nuttx
> >text   databssdechex filename
> >  168996641  23984 193621  2f455 nuttx
> >
> > = Star64 NSH Info and Free
> > NuttShell (NSH) NuttX-12.3.0
> > nsh> uname -a
> > NuttX 12.3.0 1d349a2a32

Re: [VOTE] Apache NuttX 12.3.0 RC0 release

2023-10-09 Thread Daniel Appiagyei

Thanks, Alin
I will branch off the 12.3.0 RC0 branch and have a fix up within the week

On Mon, Oct 9, 2023 at 5:40 AM Alin Jerpelea  wrote:

> Hi,
> my aim is to do a release every 3 months
> if you have the patches ready this week I would gladly do a MR1
> Best regards
> Alin
>
> On Mon, 9 Oct 2023, 14:37 Daniel Appiagyei,
>  wrote:
>
> > Hi all,
> > Is there a publicly available schedule of future releases?
> >
> > Additionally, there are some bugs in master for my chip’s (IMXRT) DMA
> > serial driver I had planned to address later this week. Would it be
> > possible for that to make an RC1 release?
> >
> > On Mon, Oct 9, 2023 at 2:24 AM Lee, Lup Yuen  wrote:
> >
> > > +1 for PinePhone and Star64
> > >
> > > Minor Issue: Building on macOS shows "sed: illegal option -- r",
> probably
> > > because macOS sed works differently from Linux. I'll track down the PR
> > that
> > > caused this.
> > >
> > > Here are the sed messages:
> > >
> > >
> >
> https://gist.github.com/lupyuen/1c3f1f1d71993609bed3b31767595beb#file-pinephone-release-log-L282-L512
> > >
> > > = PinePhone Compiler
> > > + aarch64-none-elf-gcc -v
> > > Using built-in specs.
> > > COLLECT_GCC=aarch64-none-elf-gcc
> > >
> > >
> >
> COLLECT_LTO_WRAPPER=/Applications/ArmGNUToolchain/11.3.rel1/aarch64-none-elf/bin/../libexec/gcc/aarch64-none-elf/11.3.1/lto-wrapper
> > > Target: aarch64-none-elf
> > > Configured with:
> > > /Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/src/gcc/configure
> > > --target=aarch64-none-elf
> > >
> > >
> >
> --prefix=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/install
> > >
> > >
> >
> --with-gmp=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/host-tools
> > >
> > >
> >
> --with-mpfr=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/host-tools
> > >
> > >
> >
> --with-mpc=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/host-tools
> > >
> > >
> >
> --with-isl=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/host-tools
> > > --disable-shared --disable-nls --disable-threads --disable-tls
> > > --enable-checking=release --enable-languages=c,c++,fortran
> --with-newlib
> > > --with-gnu-as --with-gnu-ld
> > >
> > >
> >
> --with-sysroot=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/install/aarch64-none-elf
> > > --with-pkgversion='Arm GNU Toolchain 11.3.Rel1' --with-bugurl=
> > > https://bugs.linaro.org/
> > > Thread model: single
> > > Supported LTO compression algorithms: zlib
> > > gcc version 11.3.1 20220712 (Arm GNU Toolchain 11.3.Rel1)
> > >
> > > = PinePhone Configuration
> > > + ./tools/configure.sh pinephone:nsh
> > >
> > > = PinePhone Size
> > > + aarch64-none-elf-size nuttx
> > >text   databssdechex filename
> > >  223895  12913  41612 278420  43f94 nuttx
> > >
> > > = PinePhone NSH Info and Free
> > > NuttShell (NSH) NuttX-12.3.0
> > > nsh> uname -a
> > > NuttX 12.3.0 1d349a2a32 Oct  9 2023 16:15:01 arm64 pinephone
> > > nsh> free
> > >total   used   freelargest  nused  nfree
> > > Umem:  133406712 551512  132855200  132855104 58  2
> > >
> > > = Star64 Compiler
> > > + riscv64-unknown-elf-gcc -v
> > > Using built-in specs.
> > > COLLECT_GCC=riscv64-unknown-elf-gcc
> > >
> > >
> >
> COLLECT_LTO_WRAPPER=/Users/Luppy/riscv64-unknown-elf-toolchain-10.2.0-2020.12.8-x86_64-apple-darwin/bin/../libexec/gcc/riscv64-unknown-elf/10.2.0/lto-wrapper
> > > Target: riscv64-unknown-elf
> > > Configured with:
> > >
> > >
> >
> /scratch/jenkins/workspace/tpp-freedom-tools/tpp01--build-binary-packages--parameterized/obj/x86_64-apple-darwin/build/riscv64-unknown-elf-gcc/riscv-gcc/configure
> > > --target=riscv64-unknown-elf
> > >
> > >
> >
> --prefix=/scratch/jenkins/workspace/tpp-freedom-tools/tpp01--build-binary-packages--parameterized/obj/x86_64-apple-darwin/install/riscv64-unknown-elf-gcc-10.2.0-2020.12.8-x86_64-apple-darwin
> > > --with-pkgversion='SiFive GCC-Metal 10.2.0-2020.12.8' --with-bugurl=
> > > https://github.com/sifive/freedom-tools/issues --disable-shared
> > > --disable-threads --enable-languages=c,c++ --enable-tls --with-newlib
> > >
> > >
> >
> --with-sysroot=/scratch/jenkins/workspace/tpp-freedom-tools/tpp01--build-binary-packages--parameterized/obj/x86_64-apple-darwin/install/riscv64-unknown-elf-gcc-10.2.0-2020.12.8-x86_64-apple-darwin/riscv64-unknown-elf
> > > --with-native-system-header-dir=/include --disable-libmudflap
> > > --disable-libssp --disable-libquadmath --disable-libgomp --disable-nls
> > > --disable-tm-clone-registry --src=../riscv-gcc --with-system-zlib
> > > --enable-checking=yes --enable-multilib --with-abi=lp64d
> > > --with-arch=rv64imafdc CFLAGS=-O2 CXXFLAGS=-O2 'CFLAGS_FOR_TARGET=-Os
> > > -mcmodel=medany' 'CXXFLAGS_FOR_TARGET=-Os -mcmodel=medany'
> > > Thread model: single
> > > Supported LTO compression algorithms: zlib
> > > gcc ve

Re: IMXRT: LPUART IDLE character Kconfig setting request

2023-10-09 Thread Daniel Appiagyei

Great idea,
Will add it to the uart, usart, and lpuart kconfigs

On Mon, Oct 9, 2023 at 2:53 AM Petro Karashchenko <
petro.karashche...@gmail.com> wrote:

> I think ESP32 also has IDLE cycles configuration for UART, so adding it as
> serial generic config makes sense to me.
>
> пн, 9 жовт. 2023 р. о 12:51 David Sidrane  пише:
>
> > What about adding it per [LP]U[S]ART in the Kconfig here
> > https://github.com/apache/nuttx/tree/master/drivers/serial
> >
> > Then any arch can use it.
> >
> > David
> >
> > -Original Message-
> > From: Daniel Appiagyei 
> > Sent: Monday, October 9, 2023 12:51 AM
> > To: dev@nuttx.apache.org
> > Subject: IMXRT: LPUART IDLE character Kconfig setting request
> >
> > Hi,
> > The IMXRT's LPUARTs have support for configuring the number of idle
> > characters it receives over UART before setting the STAT register's IDLE
> > flag. The setting is in CTRL[IDLECFG].
> > Are anyone imxrt users already planning to add support for this in
> master?
> > I will do so if not.
> > Will place the appropriate configs in
> > https://github.com/apache/nuttx/blob/master/arch/arm/src/imxrt/Kconfig
> >
> > Best,
> >
> > Daniel
> >
>

Re: [VOTE] Apache NuttX 12.3.0 RC0 release

2023-10-09 Thread Tomek CEDRO

On Mon, Oct 9, 2023 at 2:47 PM Daniel Appiagyei wrote:
> Thanks, Alin
> I will branch off the 12.3.0 RC0 branch and have a fix up within the week

Does this mean RC0 is frozen until patches are ready? :-)

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info

Re: Enforcing C++ compatibility with C code in CI/CD

2023-10-09 Thread Daniel Appiagyei

Good solution.
I'm not too knowledgeable about makefiles, but if you could set that part
up then I can do the work to make the files compatible?

On Sun, Oct 8, 2023 at 10:44 PM Xiang Xiao 
wrote:

> We can add a simple test like this:
>
>1. Create a context target in Makefile to generate a .cxx file which
>list and include all header files in nuttx/include
>2. Add the generated file to CXXSRCS
>
> If we just want to ensure the public nuttx header files are compatible with
> c++ syntax.
>
> On Mon, Oct 9, 2023 at 9:47 AM Daniel Appiagyei
>  wrote:
>
> > Late follow up, sorry
> >
> > Thanks guys, I do understand that only headers need to be compatible,
> > however, the GCC check I mentioned above does not discriminate between
> > headers and source files. If we don't have some sort of automated check
> for
> > C++ compatibility, then we will run into issues in the future like I
> > mentioned above. The nuttx style guide mentions that all C code must be
> C89
> > compliant. As long as C++ compatibility doesn't interfere with that
> > standard then we won't be losing much.
> > Are there any other ideas on how to automatically enforce headers being
> c++
> > comaptible?
> > Best,
> > Daniel
> >
> > On Sun, Sep 17, 2023 at 12:56 PM Petro Karashchenko <
> > petro.karashche...@gmail.com> wrote:
> >
> > > Since C++ most likely will never be used in the kernel I see that
> > > compatibility border should stay in the "include" folder in nuttx repo.
> > The
> > > nuttx-apps headers should be C++ compatible as we can mix things at
> > > application level.
> > >
> >
> >
> > --
> >
> >
> > *Daniel Appiagyei | Embedded Software Engineer *Email:
> > daniel.appiag...@braincorp.com
> > *Brain*
> > * Corp™ *10182 Telesis Ct, Suite 100
> > San Diego, CA 92121
> >
> > (858)-689-7600
> > www.braincorp.com
> >
>


-- 


*Daniel Appiagyei | Embedded Software Engineer *Email:
daniel.appiag...@braincorp.com
*Brain*
* Corp™ *10182 Telesis Ct, Suite 100
San Diego, CA 92121

(858)-689-7600
www.braincorp.com

Updated the wiki section about validating a staged release;

2023-10-09 Thread Tiago Medicci Serrano

Hi!

I've found some issues with verifying the signatures of the last release
candidate. After I fixed it locally, I updated the wiki content about it:

https://cwiki.apache.org/confluence/display/NUTTX/Validating+a+staged+Release

Please let me know if you find any issues regarding this. I hope this helps
everyone trying to test the new release candidate ;)

Best regards,
-- 
Tiago Medicci Serrano

Embedded Software Engineer
MSc Electronics/Microelectronics
m: +55 (19) 981403886 <+55+(19)+981403886>
e: tiago.medi...@gmail.com
a: Campinas, Brazil
Follow me:

Re: [VOTE] Apache NuttX 12.3.0 RC0 release

2023-10-09 Thread Tiago Medicci Serrano

+1

Logs:

   - esp32s3-devkit:wifi (built with `nxdiag`):
  - Build command:
  ```
  make -j distclean && ./tools/configure.sh esp32s3-devkit:wifi && \
    2 ✘
  kconfig-tweak -e ESP32S3_MERGE_BINS && \
  kconfig-tweak -e CONFIG_DEBUG_ASSERTIONS && \
  kconfig-tweak -e CONFIG_DEBUG_ERROR && \
  kconfig-tweak -e CONFIG_DEBUG_FEATURES && \
  kconfig-tweak -e CONFIG_SYSTEM_NXDIAG && \
  kconfig-tweak -e CONFIG_SYSTEM_NXDIAG_ESPRESSIF && \
  make olddefconfig -s -j && \
  make -j bootloader && make ESPTOOL_BINDIR=./ -s -j && \
  esptool.py -c esp32s3 -p /dev/ttyUSB0 -b 921600 --after no_reset
  write_flash -fs detect -fm dio 0x0 nuttx.merged.bin && \
  minicom -D /dev/ttyUSB0
  ```
  - NSH:
  ```
  ESP-ROM:esp32s3-20210327
  Build:Mar 27 2021
  rst:0x1 (POWERON),boot:0x8 (SPI_FAST_FLASH_BOOT)
  SPIWP:0xee
  mode:DIO, clock div:1
  load:0x3fce3818,len:0x1664
  load:0x403c9700,len:0x4
  load:0x403c9704,len:0xb74
  load:0x403cc700,len:0x2e8c
  entry 0x403c98fc
  I (27) boot: ESP-IDF v5.1-dev-3972-g1559b6309f 2nd stage bootloader
  I (27) boot: compile time Mar 15 2023 12:14:10
  I (28) boot: chip revision: v0.1
  I (31) boot.esp32s3: Boot SPI Speed : 80MHz
  I (36) boot.esp32s3: SPI Mode   : DIO
  I (41) boot.esp32s3: SPI Flash Size : 4MB
  I (46) boot: Enabling RNG early entropy source...
  I (51) boot: Partition Table:
  I (55) boot: ## LabelUsage  Type ST Offset
  Length
  I (62) boot:  0 factory  factory app  00 00 0001
  0010
  I (69) boot: End of partition table
  I (74) esp_image: segment 0: paddr=00010020 vaddr=3c070020
  size=17bf4h ( 97268) map
  I (100) esp_image: segment 1: paddr=00027c1c vaddr=3fc999c0
  size=01fech (  8172) load
  I (102) esp_image: segment 2: paddr=00029c10 vaddr=40374000
  size=06408h ( 25608) load
  I (111) esp_image: segment 3: paddr=00030020 vaddr=4220
  size=6eb68h (453480) map
  I (195) esp_image: segment 4: paddr=0009eb90 vaddr=4037a408
  size=00c78h (  3192) load
  I (204) boot: Loaded app from partition at offset 0x1
  I (204) boot: Disabling RNG early entropy source...
  AB
  NuttShell (NSH) NuttX-12.3.0
  nsh> nxdiag --all
  Nxdiag Report:

  NuttX RTOS info:
  Hostname:
  Release: 12.3.0
  Build: 1d349a2a32 Oct  9 2023 16:24:41
  Arch: xtensa
  Defconfig: esp32s3-devkit:wifi-dirty

  Host system OS:
  Linux tiago-latitude5430 6.1.55-1-MANJARO #1 SMP
  PREEMPT_DYNAMIC Sat Sep 23 12:13:56 UTC 2023 x86_64

  Espressif specific information:

  Bootloader version:
  esp32: Bootloader image not found
  esp32s2: Bootloader image not found
  esp32s3: v5.1-dev-3972-g1559b6309f
  esp32c2: Bootloader image not found
  esp32c3: Bootloader image not found
  esp32c6: Bootloader image not found
  esp32h2: Bootloader image not found

  Toolchain version:
  clang: clang version 16.0.6
  gcc: gcc (GCC) 13.2.1 20230801
  xtensa-esp32-elf-gcc: xtensa-esp32-elf-gcc (crosstool-NG
  esp-12.2.0_20230208) 12.2.0
  xtensa-esp32s2-elf-gcc: xtensa-esp32s2-elf-gcc (crosstool-NG
  esp-12.2.0_20230208) 12.2.0
  xtensa-esp32s3-elf-gcc: xtensa-esp32s3-elf-gcc (crosstool-NG
  esp-12.2.0_20230208) 12.2.0
  riscv32-esp-elf-gcc: riscv32-esp-elf-gcc (crosstool-NG
  esp-12.2.0_20230208) 12.2.0
  riscv64-unknown-elf-gcc: riscv64-unknown-elf-gcc (SiFive
  GCC-Metal 10.2.0-2020.12.8) 10.2.0

  Esptool version: 4.6.1

  HAL version: sync/release_v5.1.c-nuttx-20230814-28-g45c33111b4

  nsh>
  ```
   - esp32c3-generic:nsh (built with `nxdiag`):
   - Build command:
  ```
  make -j distclean && ./tools/configure.sh esp32c3-generic:nsh && \
    2 ✘
  kconfig-tweak -e ESPRESSIF_MERGE_BINS && \
  kconfig-tweak -e CONFIG_DEBUG_ASSERTIONS && \
  kconfig-tweak -e CONFIG_DEBUG_ERROR && \
  kconfig-tweak -e CONFIG_DEBUG_FEATURES && \
  kconfig-tweak -e CONFIG_SYSTEM_NXDIAG && \
  kconfig-tweak -e CONFIG_SYSTEM_NXDIAG_ESPRESSIF && \
  make olddefconfig -s -j && \
  make -j bootloader && make ESPTOOL_BINDIR=./ -s -j && \
  esptool.py -c esp32c3 -p /dev/ttyUSB0 -b 921600 --after no_reset
  write_flash -fs detect -fm dio 0x0 nuttx.merged.bin && \
  minicom -D /dev/ttyUSB0
  ```
  - NSH:
  ```
  ESP-ROM:esp32c3-api1-20210207
  Build:Feb  7 2021
  rst:0x1 (POWERON),boot:0xc (SPI_FAST_FLASH_BOOT)
  SPIWP:0xee
  mode:DIO, clock div:1
  load:0x3

Re: [VOTE] Apache NuttX 12.3.0 RC0 release

2023-10-09 Thread Alin Jerpelea

Hi,
I think that it is better if we will continue with the RC0 release testing
and make sure that there are no issues.
RC1 will include just fixes and testing should be trivial.
Best Regards
Alin

On Mon, 9 Oct 2023, 18:16 Tomek CEDRO,  wrote:

> On Mon, Oct 9, 2023 at 2:47 PM Daniel Appiagyei wrote:
> > Thanks, Alin
> > I will branch off the 12.3.0 RC0 branch and have a fix up within the week
>
> Does this mean RC0 is frozen until patches are ready? :-)
>
> --
> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>

Re: Updated the wiki section about validating a staged release;

2023-10-09 Thread Nathan Hartman

On Mon, Oct 9, 2023 at 3:03 PM Tiago Medicci Serrano <
tiago.medi...@gmail.com> wrote:

> Hi!
>
> I've found some issues with verifying the signatures of the last release
> candidate. After I fixed it locally, I updated the wiki content about it:
>
>
> https://cwiki.apache.org/confluence/display/NUTTX/Validating+a+staged+Release
>
> Please let me know if you find any issues regarding this. I hope this helps
> everyone trying to test the new release candidate ;)
>
> Best regards,
> --
> Tiago Medicci Serrano
>
> Embedded Software Engineer
> MSc Electronics/Microelectronics
> m: +55 (19) 981403886 <+55+(19)+981403886>
> e: tiago.medi...@gmail.com
> a: Campinas, Brazil
> Follow me:
> 
> 
>

Hello Tiago,

The changes look very good. Thank you for taking care of this!

Cheers
Nathan

Re: [VOTE] Apache NuttX 12.3.0 RC0 release

2023-10-09 Thread Tomek CEDRO

On Mon, Oct 9, 2023 at 9:56 PM Alin Jerpelea wrote:
> I think that it is better if we will continue with the RC0 release testing
> and make sure that there are no issues.
> RC1 will include just fixes and testing should be trivial.

ACK :-)

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info

Re: Enforcing C++ compatibility with C code in CI/CD

2023-10-09 Thread Xiang Xiao

Let' me find some time to write a test, please wait for a moment.

On Tue, Oct 10, 2023 at 2:53 AM Daniel Appiagyei
 wrote:

> Good solution.
> I'm not too knowledgeable about makefiles, but if you could set that part
> up then I can do the work to make the files compatible?
>
> On Sun, Oct 8, 2023 at 10:44 PM Xiang Xiao 
> wrote:
>
> > We can add a simple test like this:
> >
> >1. Create a context target in Makefile to generate a .cxx file which
> >list and include all header files in nuttx/include
> >2. Add the generated file to CXXSRCS
> >
> > If we just want to ensure the public nuttx header files are compatible
> with
> > c++ syntax.
> >
> > On Mon, Oct 9, 2023 at 9:47 AM Daniel Appiagyei
> >  wrote:
> >
> > > Late follow up, sorry
> > >
> > > Thanks guys, I do understand that only headers need to be compatible,
> > > however, the GCC check I mentioned above does not discriminate between
> > > headers and source files. If we don't have some sort of automated check
> > for
> > > C++ compatibility, then we will run into issues in the future like I
> > > mentioned above. The nuttx style guide mentions that all C code must be
> > C89
> > > compliant. As long as C++ compatibility doesn't interfere with that
> > > standard then we won't be losing much.
> > > Are there any other ideas on how to automatically enforce headers being
> > c++
> > > comaptible?
> > > Best,
> > > Daniel
> > >
> > > On Sun, Sep 17, 2023 at 12:56 PM Petro Karashchenko <
> > > petro.karashche...@gmail.com> wrote:
> > >
> > > > Since C++ most likely will never be used in the kernel I see that
> > > > compatibility border should stay in the "include" folder in nuttx
> repo.
> > > The
> > > > nuttx-apps headers should be C++ compatible as we can mix things at
> > > > application level.
> > > >
> > >
> > >
> > > --
> > >
> > >
> > > *Daniel Appiagyei | Embedded Software Engineer *Email:
> > > daniel.appiag...@braincorp.com
> > > *Brain*
> > > * Corp™ *10182 Telesis Ct, Suite 100
> > > San Diego, CA 92121
> > >
> > > (858)-689-7600
> > > www.braincorp.com
> > >
> >
>
>
> --
>
>
> *Daniel Appiagyei | Embedded Software Engineer *Email:
> daniel.appiag...@braincorp.com
> *Brain*
> * Corp™ *10182 Telesis Ct, Suite 100
> San Diego, CA 92121
>
> (858)-689-7600
> www.braincorp.com
>

Re: Enforcing C++ compatibility with C code in CI/CD

2023-10-09 Thread Daniel Appiagyei

No rush at all, thanks

On Mon, Oct 9, 2023 at 8:23 PM Xiang Xiao  wrote:

> Let' me find some time to write a test, please wait for a moment.
>
> On Tue, Oct 10, 2023 at 2:53 AM Daniel Appiagyei
>  wrote:
>
> > Good solution.
> > I'm not too knowledgeable about makefiles, but if you could set that part
> > up then I can do the work to make the files compatible?
> >
> > On Sun, Oct 8, 2023 at 10:44 PM Xiang Xiao 
> > wrote:
> >
> > > We can add a simple test like this:
> > >
> > >1. Create a context target in Makefile to generate a .cxx file which
> > >list and include all header files in nuttx/include
> > >2. Add the generated file to CXXSRCS
> > >
> > > If we just want to ensure the public nuttx header files are compatible
> > with
> > > c++ syntax.
> > >
> > > On Mon, Oct 9, 2023 at 9:47 AM Daniel Appiagyei
> > >  wrote:
> > >
> > > > Late follow up, sorry
> > > >
> > > > Thanks guys, I do understand that only headers need to be compatible,
> > > > however, the GCC check I mentioned above does not discriminate
> between
> > > > headers and source files. If we don't have some sort of automated
> check
> > > for
> > > > C++ compatibility, then we will run into issues in the future like I
> > > > mentioned above. The nuttx style guide mentions that all C code must
> be
> > > C89
> > > > compliant. As long as C++ compatibility doesn't interfere with that
> > > > standard then we won't be losing much.
> > > > Are there any other ideas on how to automatically enforce headers
> being
> > > c++
> > > > comaptible?
> > > > Best,
> > > > Daniel
> > > >
> > > > On Sun, Sep 17, 2023 at 12:56 PM Petro Karashchenko <
> > > > petro.karashche...@gmail.com> wrote:
> > > >
> > > > > Since C++ most likely will never be used in the kernel I see that
> > > > > compatibility border should stay in the "include" folder in nuttx
> > repo.
> > > > The
> > > > > nuttx-apps headers should be C++ compatible as we can mix things at
> > > > > application level.
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > >
> > > > *Daniel Appiagyei | Embedded Software Engineer *Email:
> > > > daniel.appiag...@braincorp.com
> > > > *Brain*
> > > > * Corp™ *10182 Telesis Ct, Suite 100
> > > > San Diego, CA 92121
> > > >
> > > > (858)-689-7600
> > > > www.braincorp.com
> > > >
> > >
> >
> >
> > --
> >
> >
> > *Daniel Appiagyei | Embedded Software Engineer *Email:
> > daniel.appiag...@braincorp.com
> > *Brain*
> > * Corp™ *10182 Telesis Ct, Suite 100
> > San Diego, CA 92121
> >
> > (858)-689-7600
> > www.braincorp.com
> >
>

[VOTE] Apache NuttX 12.3.0 RC0 release

Re: [VOTE] Apache NuttX 12.3.0 RC0 release

RE: IMXRT: LPUART IDLE character Kconfig setting request

Re: IMXRT: LPUART IDLE character Kconfig setting request

Re: [VOTE] Apache NuttX 12.3.0 RC0 release

Re: [VOTE] Apache NuttX 12.3.0 RC0 release

Re: [VOTE] Apache NuttX 12.3.0 RC0 release

Re: IMXRT: LPUART IDLE character Kconfig setting request

Re: [VOTE] Apache NuttX 12.3.0 RC0 release

Re: Enforcing C++ compatibility with C code in CI/CD

Updated the wiki section about validating a staged release;

Re: [VOTE] Apache NuttX 12.3.0 RC0 release

Re: [VOTE] Apache NuttX 12.3.0 RC0 release

Re: Updated the wiki section about validating a staged release;

Re: [VOTE] Apache NuttX 12.3.0 RC0 release

Re: Enforcing C++ compatibility with C code in CI/CD

Re: Enforcing C++ compatibility with C code in CI/CD

17 matches

Site Navigation

Mail list logo

Footer information