Re: [VOTE] Apache NuttX 12.3.0 RC0 release

2023-10-16 Thread Tomek CEDRO 
I have double checked the build with GCC 8.4.0 and the fix is in place
(git master)!
Thank you!! :-)

% cu -l /dev/cuaU0 -s 115200
Connected
ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:4540
ho 0 tail 12 room 4
load:0x40078000,len:12344
ho 0 tail 12 room 4
load:0x40080400,len:4124
entry 0x40080680

NuttShell (NSH) NuttX-12.3.0-RC0
nsh> uname -a
NuttX 12.3.0-RC0 882afc885e Oct 16 2023 23:04:15 xtensa esp32-devkitc


% xtensa-esp32-elf-gcc --version
xtensa-esp32-elf-gcc (crosstool-NG esp-2021r2-patch5) 8.4.0
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

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

Re: [VOTE] Apache NuttX 12.3.0 RC0 release

2023-10-16 Thread Alin Jerpelea 
Don't worry
I will cherry-pick fixes and create rc1,
then the next release comes in 3 months.

Best regards

On Mon, 16 Oct 2023, 22:15 Daniel Appiagyei,
 wrote:

> Apologies for the typo Alin! :)
>
> On Mon, Oct 16, 2023 at 11:30 AM Alan C. Assis  wrote:
>
> > That was Alin :-)
> >
> > On 10/16/23, Daniel Appiagyei 
> > wrote:
> > > Hi Alan,
> > > Apologies for the delay. Please go ahead and make the RC1.
> > > The issue regards using DMA for UART in (at least) the IMXRT family of
> > > chips. I've created an issue here
> > >  and have a PR with an
> > > incomplete fix here .
> David
> > and
> > > I are trying to figure out the exact issue this week
> > > Best,
> > > --
> > >
> > >
> > > *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: [VOTE] Apache NuttX 12.3.0 RC0 release

2023-10-16 Thread Daniel Appiagyei 
Apologies for the typo Alin! :)

On Mon, Oct 16, 2023 at 11:30 AM Alan C. Assis  wrote:

> That was Alin :-)
>
> On 10/16/23, Daniel Appiagyei 
> wrote:
> > Hi Alan,
> > Apologies for the delay. Please go ahead and make the RC1.
> > The issue regards using DMA for UART in (at least) the IMXRT family of
> > chips. I've created an issue here
> >  and have a PR with an
> > incomplete fix here . David
> and
> > I are trying to figure out the exact issue this week
> > Best,
> > --
> >
> >
> > *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: [VOTE] Apache NuttX 12.3.0 RC0 release

2023-10-16 Thread Alan C. Assis 
That was Alin :-)

On 10/16/23, Daniel Appiagyei  wrote:
> Hi Alan,
> Apologies for the delay. Please go ahead and make the RC1.
> The issue regards using DMA for UART in (at least) the IMXRT family of
> chips. I've created an issue here
>  and have a PR with an
> incomplete fix here . David and
> I are trying to figure out the exact issue this week
> Best,
> --
>
>
> *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: [VOTE] Apache NuttX 12.3.0 RC0 release

2023-10-16 Thread Daniel Appiagyei 
Hi Alan,
Apologies for the delay. Please go ahead and make the RC1.
The issue regards using DMA for UART in (at least) the IMXRT family of
chips. I've created an issue here
 and have a PR with an
incomplete fix here . David and
I are trying to figure out the exact issue this week
Best,
-- 


*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: [VOTE] Apache NuttX 12.3.0 RC0 release

2023-10-16 Thread alin.jerpe...@sony.com 
Hi Daniel

Any updates on the patches?
I would like to continue with RC1

Best regards
Alin

From: Daniel Appiagyei 
Sent: den 9 oktober 2023 14:48
To: dev@nuttx.apache.org
Subject: Re: [VOTE] Apache NuttX 12.3.0 RC0 release

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
ZjQcmQRYFpfptBannerStart
Caution : This email originated from outside of Sony.
Do not click links or open any attachments unless you recognize the sender and 
know the content is safe. Please report phishing if unsure.
ZjQcmQRYFpfptBannerEnd

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 
mailto:jerpe...@gmail.com>> 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,

> mailto:daniel.appiag...@braincorp.com.invalid>>
>  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 
> > mailto:lu...@appkaki.com>> 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<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/<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

> &

Re: [VOTE] Apache NuttX 12.3.0 RC0 release

2023-10-12 Thread Tomek CEDRO 
On Thu, Oct 12, 2023 at 9:52 AM Alin Jerpelea wrote:
> the patch has been backported for RC1
> Thanks for reporting it
> Best regards
> Alin

Perfect! Thank you Alin! :-)

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

Re: [VOTE] Apache NuttX 12.3.0 RC0 release

2023-10-12 Thread Alin Jerpelea 
the patch has been backported for RC1

Thanks for reporting it
Best regards
Alin


On Thu, Oct 12, 2023 at 4:07 AM Xiang Xiao 
wrote:

> A recent change limits c++20 requirement to libcxx:
> https://github.com/apache/nuttx/pull/10860
> The owner of libcxx decided not to support the build of libcxx by
> an old compiler, It's very hard to sync with the last libcxx version, and
> keep the support of the old compiler at the same time in the long term.
>
>
> On Thu, Oct 12, 2023 at 7:31 AM Tomek CEDRO  wrote:
>
> > On Thu, Oct 12, 2023 at 12:19 AM Nathan Hartman wrote:
> > > On Wed, Oct 11, 2023 at 3:21 PM Tomek CEDRO wrote:
> > > > Hello world,
> > > > I have encountered a basic esp32:nsh build error in nuttx-12.3.0-RC0
> > > > related to xtensa g++ 8.4.0 compiler:
> > > > xtensa-esp32-elf-g++: error: unrecognized command line option
> > > > '-std=gnu++20'; did you mean '-std=gnu++2a'?
> > >
> > > This was changed in d6453cfc3cd4771a5221528cab3056660be4b1e3 (PR #
> 8244).
> > >
> > > See mail thread:
> > > https://lists.apache.org/thread/rkq99os8ql28bv1w8fy5mdqwl3h2vp6m
> > >
> > > The workaround is to set Kconfig CXX_STANDARD to gnu++2a instead of
> > gnu++20.
> >
> > Thank you Nathan :-)
> >
> > I am following the mailing list and github PRs so I know this was
> > recent change to make better compatibility with C++ and this is fine
> > to have this support. But this should not happen at the cost of
> > standard build setup and/or enforcing specific compilers / versions to
> > everyone by default (see inviolables). This probably also impacts
> > other platforms/architectures, especially the older ones. I am sure
> > this can be fixed easily.
> >
> > I am sorry for giving my first -1 as I know there are many new
> > features and improvements in the RC, but I am afraid if we don't fix
> > that compiler problem now then there will be no incentive to do this
> > in future.
> >
> >
> > > It would be nice if the build system could automatically detect the
> > > compiler version and set this value accordingly and automatically,
> > > without a Kconfig. IIRC there are programs in tools that determine
> > > compiler options based on the compiler and version. (Can't remember
> > > details off the top of my head at the moment.)
> >
> > Yes that would be perfect!
> >
> > Quick search shows that people do this in many ways by calling
> > compiler with a list of flags and checking return status for each flag
> > to see if it is supported.
> >
> > Current C++ standards supported by GCC and CLANG are listed here:
> > https://gcc.gnu.org/projects/cxx-status.html
> > https://clang.llvm.org/cxx_status.html
> >
> > Quote from GCC:
> > C++20 Support in GCC
> > GCC has experimental support for the latest revision of the C++
> > standard, which was published in 2020. The status of C++20 library
> > features is described in the library documentation.
> > C++20 features are available since GCC 8. To enable C++20 support, add
> > the command-line parameter -std=c++20 (use -std=c++2a in GCC 9 and
> > earlier) to your g++ command line. Or, to enable GNU extensions in
> > addition to C++20 features, add -std=gnu++20.
> >
> > Maybe a simple check can be added to a Makefile?
> >
> > Maybe a C++ support could be added as option that is disabled by
> > default (+compiler check)?
> >
> >
> > > > REMARKS:
> > > > 1. flock is a new system build dependency.
> > >
> > > I think documentation needs to be updated? I think not all systems
> > > have flock. Is it a Linux-only thing? (Non-BSD?)
> >
> > Not a big deal I guess :-) As compared to 12.2.1 in order to build
> > 12.3.0-RC0 I had to install additional "flock" application. It comes
> > from Linux and it is available on FreeBSD. On macOS (BSD) it is not
> > part of the base system too and it can be installed with brew. It
> > seems to be fairly old commit that fixes parallel build (which I also
> > use). Just a notice :-)
> >
> >
> >
> https://github.com/apache/nuttx-apps/blob/91a682f11bba1a537bd095cef45f17db57c9e7b9/Make.defs#L157
> >
> >
> https://github.com/apache/nuttx-apps/commit/f774e8ee7202a61bcf64a93b2f3ddfd240288cf1
> >
> > Thank you :-)
> > Tomek
> >
> > --
> > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> >
>

Re: [VOTE] Apache NuttX 12.3.0 RC0 release

2023-10-11 Thread Xiang Xiao 
A recent change limits c++20 requirement to libcxx:
https://github.com/apache/nuttx/pull/10860
The owner of libcxx decided not to support the build of libcxx by
an old compiler, It's very hard to sync with the last libcxx version, and
keep the support of the old compiler at the same time in the long term.


On Thu, Oct 12, 2023 at 7:31 AM Tomek CEDRO  wrote:

> On Thu, Oct 12, 2023 at 12:19 AM Nathan Hartman wrote:
> > On Wed, Oct 11, 2023 at 3:21 PM Tomek CEDRO wrote:
> > > Hello world,
> > > I have encountered a basic esp32:nsh build error in nuttx-12.3.0-RC0
> > > related to xtensa g++ 8.4.0 compiler:
> > > xtensa-esp32-elf-g++: error: unrecognized command line option
> > > '-std=gnu++20'; did you mean '-std=gnu++2a'?
> >
> > This was changed in d6453cfc3cd4771a5221528cab3056660be4b1e3 (PR # 8244).
> >
> > See mail thread:
> > https://lists.apache.org/thread/rkq99os8ql28bv1w8fy5mdqwl3h2vp6m
> >
> > The workaround is to set Kconfig CXX_STANDARD to gnu++2a instead of
> gnu++20.
>
> Thank you Nathan :-)
>
> I am following the mailing list and github PRs so I know this was
> recent change to make better compatibility with C++ and this is fine
> to have this support. But this should not happen at the cost of
> standard build setup and/or enforcing specific compilers / versions to
> everyone by default (see inviolables). This probably also impacts
> other platforms/architectures, especially the older ones. I am sure
> this can be fixed easily.
>
> I am sorry for giving my first -1 as I know there are many new
> features and improvements in the RC, but I am afraid if we don't fix
> that compiler problem now then there will be no incentive to do this
> in future.
>
>
> > It would be nice if the build system could automatically detect the
> > compiler version and set this value accordingly and automatically,
> > without a Kconfig. IIRC there are programs in tools that determine
> > compiler options based on the compiler and version. (Can't remember
> > details off the top of my head at the moment.)
>
> Yes that would be perfect!
>
> Quick search shows that people do this in many ways by calling
> compiler with a list of flags and checking return status for each flag
> to see if it is supported.
>
> Current C++ standards supported by GCC and CLANG are listed here:
> https://gcc.gnu.org/projects/cxx-status.html
> https://clang.llvm.org/cxx_status.html
>
> Quote from GCC:
> C++20 Support in GCC
> GCC has experimental support for the latest revision of the C++
> standard, which was published in 2020. The status of C++20 library
> features is described in the library documentation.
> C++20 features are available since GCC 8. To enable C++20 support, add
> the command-line parameter -std=c++20 (use -std=c++2a in GCC 9 and
> earlier) to your g++ command line. Or, to enable GNU extensions in
> addition to C++20 features, add -std=gnu++20.
>
> Maybe a simple check can be added to a Makefile?
>
> Maybe a C++ support could be added as option that is disabled by
> default (+compiler check)?
>
>
> > > REMARKS:
> > > 1. flock is a new system build dependency.
> >
> > I think documentation needs to be updated? I think not all systems
> > have flock. Is it a Linux-only thing? (Non-BSD?)
>
> Not a big deal I guess :-) As compared to 12.2.1 in order to build
> 12.3.0-RC0 I had to install additional "flock" application. It comes
> from Linux and it is available on FreeBSD. On macOS (BSD) it is not
> part of the base system too and it can be installed with brew. It
> seems to be fairly old commit that fixes parallel build (which I also
> use). Just a notice :-)
>
>
> https://github.com/apache/nuttx-apps/blob/91a682f11bba1a537bd095cef45f17db57c9e7b9/Make.defs#L157
>
> https://github.com/apache/nuttx-apps/commit/f774e8ee7202a61bcf64a93b2f3ddfd240288cf1
>
> Thank you :-)
> Tomek
>
> --
> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
>

Re: [VOTE] Apache NuttX 12.3.0 RC0 release

2023-10-11 Thread Tomek CEDRO 
On Thu, Oct 12, 2023 at 12:19 AM Nathan Hartman wrote:
> On Wed, Oct 11, 2023 at 3:21 PM Tomek CEDRO wrote:
> > Hello world,
> > I have encountered a basic esp32:nsh build error in nuttx-12.3.0-RC0
> > related to xtensa g++ 8.4.0 compiler:
> > xtensa-esp32-elf-g++: error: unrecognized command line option
> > '-std=gnu++20'; did you mean '-std=gnu++2a'?
>
> This was changed in d6453cfc3cd4771a5221528cab3056660be4b1e3 (PR # 8244).
>
> See mail thread:
> https://lists.apache.org/thread/rkq99os8ql28bv1w8fy5mdqwl3h2vp6m
>
> The workaround is to set Kconfig CXX_STANDARD to gnu++2a instead of gnu++20.

Thank you Nathan :-)

I am following the mailing list and github PRs so I know this was
recent change to make better compatibility with C++ and this is fine
to have this support. But this should not happen at the cost of
standard build setup and/or enforcing specific compilers / versions to
everyone by default (see inviolables). This probably also impacts
other platforms/architectures, especially the older ones. I am sure
this can be fixed easily.

I am sorry for giving my first -1 as I know there are many new
features and improvements in the RC, but I am afraid if we don't fix
that compiler problem now then there will be no incentive to do this
in future.


> It would be nice if the build system could automatically detect the
> compiler version and set this value accordingly and automatically,
> without a Kconfig. IIRC there are programs in tools that determine
> compiler options based on the compiler and version. (Can't remember
> details off the top of my head at the moment.)

Yes that would be perfect!

Quick search shows that people do this in many ways by calling
compiler with a list of flags and checking return status for each flag
to see if it is supported.

Current C++ standards supported by GCC and CLANG are listed here:
https://gcc.gnu.org/projects/cxx-status.html
https://clang.llvm.org/cxx_status.html

Quote from GCC:
C++20 Support in GCC
GCC has experimental support for the latest revision of the C++
standard, which was published in 2020. The status of C++20 library
features is described in the library documentation.
C++20 features are available since GCC 8. To enable C++20 support, add
the command-line parameter -std=c++20 (use -std=c++2a in GCC 9 and
earlier) to your g++ command line. Or, to enable GNU extensions in
addition to C++20 features, add -std=gnu++20.

Maybe a simple check can be added to a Makefile?

Maybe a C++ support could be added as option that is disabled by
default (+compiler check)?


> > REMARKS:
> > 1. flock is a new system build dependency.
>
> I think documentation needs to be updated? I think not all systems
> have flock. Is it a Linux-only thing? (Non-BSD?)

Not a big deal I guess :-) As compared to 12.2.1 in order to build
12.3.0-RC0 I had to install additional "flock" application. It comes
from Linux and it is available on FreeBSD. On macOS (BSD) it is not
part of the base system too and it can be installed with brew. It
seems to be fairly old commit that fixes parallel build (which I also
use). Just a notice :-)

https://github.com/apache/nuttx-apps/blob/91a682f11bba1a537bd095cef45f17db57c9e7b9/Make.defs#L157
https://github.com/apache/nuttx-apps/commit/f774e8ee7202a61bcf64a93b2f3ddfd240288cf1

Thank you :-)
Tomek

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

Re: [VOTE] Apache NuttX 12.3.0 RC0 release

2023-10-11 Thread Nathan Hartman 
Hi Tomek,

On Wed, Oct 11, 2023 at 3:21 PM Tomek CEDRO  wrote:
>
> Hello world,
>
> I have encountered a basic esp32:nsh build error in nuttx-12.3.0-RC0
> related to xtensa g++ 8.4.0 compiler:
>
> xtensa-esp32-elf-g++: error: unrecognized command line option
> '-std=gnu++20'; did you mean '-std=gnu++2a'?

This was changed in d6453cfc3cd4771a5221528cab3056660be4b1e3 (PR # 8244).

See mail thread:
https://lists.apache.org/thread/rkq99os8ql28bv1w8fy5mdqwl3h2vp6m

The workaround is to set Kconfig CXX_STANDARD to gnu++2a instead of gnu++20.

It would be nice if the build system could automatically detect the
compiler version and set this value accordingly and automatically,
without a Kconfig. IIRC there are programs in tools that determine
compiler options based on the compiler and version. (Can't remember
details off the top of my head at the moment.)

More below:

> Therefore -1 from me at this point. This does not happen in 12.2.1. If
> a minimum required version of a compiler is required then this must be
> somehow clearly stated. This would break older setups. Looks like a
> breaking change. I do not even use C++. Can we please make this
> optional? Details below.
>
> BUILD HOST:
> FreeBSD octagon 13.2-RELEASE-p4 FreeBSD 13.2-RELEASE-p4 GENERIC amd64
>
> REMARKS:
> 1. flock is a new system build dependency.

I think documentation needs to be updated? I think not all systems
have flock. Is it a Linux-only thing? (Non-BSD?)

Cheers,
Nathan

Re: [VOTE] Apache NuttX 12.3.0 RC0 release

2023-10-11 Thread Tomek CEDRO 
Hello world,

I have encountered a basic esp32:nsh build error in nuttx-12.3.0-RC0
related to xtensa g++ 8.4.0 compiler:

xtensa-esp32-elf-g++: error: unrecognized command line option
'-std=gnu++20'; did you mean '-std=gnu++2a'?

Therefore -1 from me at this point. This does not happen in 12.2.1. If
a minimum required version of a compiler is required then this must be
somehow clearly stated. This would break older setups. Looks like a
breaking change. I do not even use C++. Can we please make this
optional? Details below.

BUILD HOST:
FreeBSD octagon 13.2-RELEASE-p4 FreeBSD 13.2-RELEASE-p4 GENERIC amd64

REMARKS:
1. flock is a new system build dependency.
2. ESP32 CoreMark builds fine.
3. ESP32 NSH fails to build (xtensa-esp32-elf-g++: error: unrecognized
command line option '-std=gnu++20'; did you mean '-std=gnu++2a'?).

TARGETS:
1. ESP32.

1. ESP32

1.1. COMPILER.

% xtensa-esp32-elf-gcc --version
xtensa-esp32-elf-gcc (crosstool-NG esp-2021r2-patch5) 8.4.0
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

1.2. COREMARK.

% /usr/bin/time -h ./tools/configure.sh -B -a ../nuttx-apps.git
esp32-devkitc:coremark
1,45s real 0,65s user 1,02s sys

% /usr/bin/time -h gmake -j8 V=1
17,23s real 54,60s user 32,36s sys

% /usr/bin/time -h gmake flash
2,47s real 1,54s user 1,06s sys

% cu -l /dev/cuaU0 -s 115200
can't open log file /var/log/aculog.
Connected
ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:4540
ho 0 tail 12 room 4
load:0x40078000,len:12344
ho 0 tail 12 room 4
load:0x40080400,len:4124
entry 0x40080680
Running CoreMark...
2K performance run parameters for coremark.
CoreMark Size: 666
Total ticks  : 12180
Total time (secs): 12.18
Iterations/Sec   : 985.221675
Iterations   : 12000
Compiler version : GCC8.4.0
Compiler flags   : -O3 -fno-strict-aliasing -fomit-frame-pointer
-ffunction-sections -fdata-sections
Parallel PThreads : 2
Memory location  : Stack
seedcrc  : 0xe9f5
[0]crclist   : 0xe714
[1]crclist   : 0xe714
[0]crcmatrix : 0x1fd7
[1]crcmatrix : 0x1fd7
[0]crcstate  : 0x8e3a
[1]crcstate  : 0x8e3a
[0]crcfinal  : 0xa14c
[1]crcfinal  : 0xa14c
Correct operation validated. See README.md for run and reporting rules.
CoreMark 1.0 : 985.221675 / GCC8.4.0 -O3 -fno-strict-aliasing
-fomit-frame-pointer -ffunction-sections -fdata-sections / Stack /
2:PThreads

1.3. NSH

% /usr/bin/time -h ./tools/configure.sh -B -a ../nuttx-apps.git
esp32-devkitc:nsh
3,17s real  1,48s user  1,93s sys

% /usr/bin/time -h gmake -j8 V=1
(..)
/XXX/nuttx.git/tools/mkdeps --obj-path . --obj-suffix .o --dep-path
libcxxmini "xtensa-esp32-elf-g++" -- -fno-common -nostdinc++ -Wall
-Wshadow -Wundef -Wno-attributes -Wno-unknown-pragmas -Wno-psabi
-std="gnu++20" -fno-exceptions -fcheck-new -fno-rtti -Os
-fno-strict-aliasing -fomit-frame-pointer -ffunction-sections
-fdata-sections -mlongcalls -isystem /XXX/nuttx.git/include/cxx
-isystem /XXX/nuttx.git/include -D__NuttX__ -DNDEBUG -D__KERNEL__
-pipe -- libcxxmini/libxx_newa.cxx > libxx_newa.ddx
xtensa-esp32-elf-g++: error: unrecognized command line option
'-std=gnu++20'; did you mean '-std=gnu++2a'?
xtensa-esp32-elf-g++: error: unrecognized command line option
'-std=gnu++20'; did you mean '-std=gnu++2a'?
xtensa-esp32-elf-g++: error: unrecognized command line option
'-std=gnu++20'; did you mean '-std=gnu++2a'?
xtensa-esp32-elf-g++: error: unrecognized command line option
'-std=gnu++20'; did you mean '-std=gnu++2a'?
xtensa-esp32-elf-g++: error: unrecognized command line option
'-std=gnu++20'; did you mean '-std=gnu++2a'?
xtensa-esp32-elf-g++: error: unrecognized command line option
'-std=gnu++20'; did you mean '-std=gnu++2a'?
xtensa-esp32-elf-g++: error: unrecognized command line option
'-std=gnu++20'; did you mean '-std=gnu++2a'?
xtensa-esp32-elf-g++: error: unrecognized command line option
'-std=gnu++20'; did you mean '-std=gnu++2a'?
if [ -z "libxx_cxa_guard.ddx libxx_cxapurevirtual.ddx libxx_delete.ddx
libxx_delete_sized.ddx libxx_deletea.ddx libxx_deletea_sized.ddx
libxx_new.ddx libxx_newa.ddx" ]; then echo '' >  Make.dep; else cat
libxx_cxa_guard.ddx libxx_cxapurevirtual.ddx libxx_delete.ddx
libxx_delete_sized.ddx libxx_deletea.ddx libxx_deletea_sized.ddx
libxx_new.ddx libxx_newa.ddx >  Make.dep; fi
rm -f  libxx_cxa_guard.ddx libxx_cxapurevirtual.ddx libxx_delete.ddx
libxx_delete_sized.ddx libxx_deletea.ddx libxx_deletea_sized.ddx
libxx_new.ddx libxx_newa.ddx
gmake[2]: Leaving directory '/XXX/nuttx.git/libs/libxx'
touch .depend
gmake[1]: Leaving directory '/XXX/nuttx.git/libs/libxx'
7,41s real  15,67s user 15,37s sys

Any hints welcome!

-- 
CeDeROM,

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: [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: [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

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: [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

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 
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:
>

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

[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