Re: [VOTE] Apache NuttX 10.1.0 (incubating) RC1 release
+1 On 5/6/21, alin.jerpe...@sony.com wrote: > Hi all, > > 72h have passed > Can we get some votes to finish the 10.1 release? > > Thanks > Alin > > > -Original Message- > From: alin.jerpe...@sony.com > Sent: den 3 maj 2021 17:17 > To: dev@nuttx.apache.org > Subject: RE: [VOTE] Apache NuttX 10.1.0 (incubating) RC1 release > > Hello all, > > This is the latest tarball > > I am sorry for the confusion > > Thanks > Alin > > > -Original Message- > From: Nathan Hartman > Sent: den 3 maj 2021 17:14 > To: dev@nuttx.apache.org > Subject: Re: [VOTE] Apache NuttX 10.1.0 (incubating) RC1 release > > On Mon, May 3, 2021 at 1:22 AM Alin Jerpelea wrote: >> >> Hello all, >> Apache NuttX (Incubating) 10.1.0 RC1 has been staged under [1] and >> it's time to vote on accepting it for release. If approved we will >> seek final release approval from the IPMC. 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 [P]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-10.1.0-RC1 >> Hash for the release incubating-nuttx tag: >> 3130ff691e386934eb276587a24d1efacf3bb30b >> Hash for the release incubating-nuttx-apps tag: >> 4348d91d1356335483089c3865282d80f13bedcd >> >> [1] >> https://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/inc >> ubator/nuttx/10.1.0-RC1/__;!!JmoZiZGBv3RvKRSx!u7bO_5TgIUsO429c5U2xXTz4 >> HI0T2TqnSm836Wse15R0SGxhUdWk3viAcBF0cM9oFQ$ >> [2]https://urldefense.com/v3/__https://raw.githubusercontent.com/apach >> e/incubator-nuttx/nuttx-10.1.0-RC1/ReleaseNotes__;!!JmoZiZGBv3RvKRSx!u >> 7bO_5TgIUsO429c5U2xXTz4HI0T2TqnSm836Wse15R0SGxhUdWk3viAcBELDkRTXA$ >> [3] >> https://urldefense.com/v3/__https://www.apache.org/dev/release.html*ap >> proving-a-release__;Iw!!JmoZiZGBv3RvKRSx!u7bO_5TgIUsO429c5U2xXTz4HI0T2 >> TqnSm836Wse15R0SGxhUdWk3viAcBGKE_xsSw$ >> [4]https://urldefense.com/v3/__https://cwiki.apache.org/confluence/dis >> play/NUTTX/Validating*a*staged*Release__;Kysr!!JmoZiZGBv3RvKRSx!u7bO_5 >> TgIUsO429c5U2xXTz4HI0T2TqnSm836Wse15R0SGxhUdWk3viAcBE_QwknXQ$ > > > Just to be sure I don't misunderstand, this is the latest release candidate > to be tested now? > > In the future, I recommend to increment the -RC numbers each time there are > new tarballs, to avoid any potential confusion. > > If this is indeed the latest RC, I'll try to test it today. > > Thanks for all your hard work!! > > Cheers, > Nathan >
Re: [VOTE] Apache NuttX 10.1.0 (incubating) RC1 release
+1, test with sim+wsl2 On Sat, May 1, 2021 at 2:50 PM Alin Jerpelea wrote: > Hello all, > Apache NuttX (Incubating) 10.1.0 RC1 has been staged under [1] and it's > time to vote on accepting it for release. If approved we will seek > final release approval from the IPMC. 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 [P]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-10.1.0-RC1 > Hash for the release incubating-nuttx tag: > 4348d91d1356335483089c3865282d80f13bedcd > Hash for the release incubating-nuttx-apps tag: > 112d709609e4916b21e435152679cd0b5f3177fb > > [1] https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.1.0-RC1/ > [2] > https://raw.githubusercontent.com/apache/incubator-nuttx/nuttx-10.1.0-RC1/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 10.1.0 (incubating) RC1 release
This is the final sizes for ESP32-Devkitc and STM32F4Discovery tested on Ubuntu 20.04: ESP32: $ ./tools/configure.sh esp32-devkitc:nsh $ xtensa-esp32-elf-size nuttx textdata bss dec hex filename 70576 924976 75644 1277c nuttx $ ls -l nuttx.bin -rwxrwxr-x 1 alan alan 123856 May 7 11:36 nuttx.bin gcc version 8.2.0 (crosstool-NG esp-2020r2) NuttShell (NSH) NuttX-10.1.0 nsh> free total used freelargest Umem: 327536 5792 321744 190576 nsh> STM32F407: $ ./tools/configure.sh stm32f4discovery:nsh $ arm-none-eabi-size nuttx textdata bss dec hex filename 68516 961732 70344 112c8 nuttx $ ls -l nuttx.bin -rwxrwxr-x 1 alan alan 68612 May 7 11:39 nuttx.bin gcc version 9.2.1 20191025 (release) [ARM/arm-9-branch revision 277599] (15:9-2019-q4-0ubuntu1) NuttShell (NSH) NuttX-10.1.0 nsh> free total used freelargest Umem: 193408 5664 187744 127280 nsh> On 5/7/21, Alan Carvalho de Assis wrote: > +1 > > On 5/6/21, alin.jerpe...@sony.com wrote: >> Hi all, >> >> 72h have passed >> Can we get some votes to finish the 10.1 release? >> >> Thanks >> Alin >> >> >> -Original Message- >> From: alin.jerpe...@sony.com >> Sent: den 3 maj 2021 17:17 >> To: dev@nuttx.apache.org >> Subject: RE: [VOTE] Apache NuttX 10.1.0 (incubating) RC1 release >> >> Hello all, >> >> This is the latest tarball >> >> I am sorry for the confusion >> >> Thanks >> Alin >> >> >> -Original Message- >> From: Nathan Hartman >> Sent: den 3 maj 2021 17:14 >> To: dev@nuttx.apache.org >> Subject: Re: [VOTE] Apache NuttX 10.1.0 (incubating) RC1 release >> >> On Mon, May 3, 2021 at 1:22 AM Alin Jerpelea wrote: >>> >>> Hello all, >>> Apache NuttX (Incubating) 10.1.0 RC1 has been staged under [1] and >>> it's time to vote on accepting it for release. If approved we will >>> seek final release approval from the IPMC. 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 [P]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-10.1.0-RC1 >>> Hash for the release incubating-nuttx tag: >>> 3130ff691e386934eb276587a24d1efacf3bb30b >>> Hash for the release incubating-nuttx-apps tag: >>> 4348d91d1356335483089c3865282d80f13bedcd >>> >>> [1] >>> https://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/inc >>> ubator/nuttx/10.1.0-RC1/__;!!JmoZiZGBv3RvKRSx!u7bO_5TgIUsO429c5U2xXTz4 >>> HI0T2TqnSm836Wse15R0SGxhUdWk3viAcBF0cM9oFQ$ >>> [2]https://urldefense.com/v3/__https://raw.githubusercontent.com/apach >>> e/incubator-nuttx/nuttx-10.1.0-RC1/ReleaseNotes__;!!JmoZiZGBv3RvKRSx!u >>> 7bO_5TgIUsO429c5U2xXTz4HI0T2TqnSm836Wse15R0SGxhUdWk3viAcBELDkRTXA$ >>> [3] >>> https://urldefense.com/v3/__https://www.apache.org/dev/release.html*ap >>> proving-a-release__;Iw!!JmoZiZGBv3RvKRSx!u7bO_5TgIUsO429c5U2xXTz4HI0T2 >>> TqnSm836Wse15R0SGxhUdWk3viAcBGKE_xsSw$ >>> [4]https://urldefense.com/v3/__https://cwiki.apache.org/confluence/dis >>> play/NUTTX/Validating*a*staged*Release__;Kysr!!JmoZiZGBv3RvKRSx!u7bO_5 >>> TgIUsO429c5U2xXTz4HI0T2TqnSm836Wse15R0SGxhUdWk3viAcBE_QwknXQ$ >> >> >> Just to be sure I don't misunderstand, this is the latest release >> candidate >> to be tested now? >> >> In the future, I recommend to increment the -RC numbers each time there >> are >> new tarballs, to avoid any potential confusion. >> >> If this is indeed the latest RC, I'll try to test it today. >> >> Thanks for all your hard work!! >> >> Cheers, >> Nathan >> >
CAN example crashes
Hi, SAMA5D27 (custom board) - trying to complete the port and also check that the CAN interface works on the board, so I'm trying to use the CAN example app. The drivers appear to be registered (I see /dev/can0 and /dev/can1) but the CAN example app crashes when trying to open /dev/can0 and I can't see why. I am hindered in debugging this fully as yet since: a. I am new to Nuttx and haven't yet sussed how to enable any low level debug-type stuff (I have used menuconfig to enable anything that seems to be related but I'm sure I missed stuff) b. I haven't yet coerced my Eclipse IDE (under Windows 10, but code configured and compiled using Windows WSL) to "see" the source code properly to enable me to insert breakpoints (Segger J-link). Not wedded to Eclipse, but it is a known entity for me and at least downloads/runs/debugs the board!) Can anyone point me in the direction of why, or a way to find out why, the call to open the device would crash the board rather than return an error? Other devices (such as Flexcom USARTs open OK and work - well, after I fixed some arch issues for Flexcoms on the SAMA5 anyway!!). The board-specific code (sam_can.c) I am using is based on the code for the sama5d2-xult board and seems pretty trivial, and largely similar to many other architectures and boards. Many thanks, Tim.
Re: CAN example crashes
Hi Tim, Try to enable the debug in the menuconfig: Build Setup ---> Debug Options ---> [*] Enable Debug Features [*] Enable Error Output [*] Enable Warnings Output [*] Enable Informational Debug Output [*] CAN Debug Features [*] CAN Error Output [*] CAN Warnings Output [*] CAN Informational Output BR, Alan On 5/7/21, Tim wrote: > Hi, > > > > SAMA5D27 (custom board) - trying to complete the port and also check that > the CAN interface works on the board, so I'm trying to use the CAN example > app. > > > > The drivers appear to be registered (I see /dev/can0 and /dev/can1) but the > CAN example app crashes when trying to open /dev/can0 and I can't see why. > > > > I am hindered in debugging this fully as yet since: > > > > a.I am new to Nuttx and haven't yet sussed how to enable any low level > debug-type stuff (I have used menuconfig to enable anything that seems to > be > related but I'm sure I missed stuff) > b.I haven't yet coerced my Eclipse IDE (under Windows 10, but code > configured and compiled using Windows WSL) to "see" the source code > properly > to enable me to insert breakpoints (Segger J-link). Not wedded to Eclipse, > but it is a known entity for me and at least downloads/runs/debugs the > board!) > > > > Can anyone point me in the direction of why, or a way to find out why, the > call to open the device would crash the board rather than return an error? > Other devices (such as Flexcom USARTs open OK and work - well, after I > fixed > some arch issues for Flexcoms on the SAMA5 anyway!!). The board-specific > code (sam_can.c) I am using is based on the code for the sama5d2-xult board > and seems pretty trivial, and largely similar to many other architectures > and boards. > > > > Many thanks, > > > > Tim. > > > >
Re: CAN example crashes
Thanks Alan - those are already set but don't seem to produce any output on the console so may be the error output itself isn't configured right. I'll take a look. On 07/05/2021, 18:49, "Alan Carvalho de Assis" wrote: >Hi Tim, >Try to enable the debug in the menuconfig: > Build Setup ---> > Debug Options ---> >[*] Enable Debug Features >[*] Enable Error Output >[*] Enable Warnings Output >[*] Enable Informational Debug Output > >[*] CAN Debug Features >[*] CAN Error Output >[*] CAN Warnings Output >[*] CAN Informational Output >>On 5/7/21, Tim wrote: >> Hi, >> >> >> >> SAMA5D27 (custom board) - trying to complete the port and also check that >> the CAN interface works on the board, so I'm trying to use the CAN example >> app. >> >> >> >> The drivers appear to be registered (I see /dev/can0 and /dev/can1) but >> the >> CAN example app crashes when trying to open /dev/can0 and I can't see why. >> > >> >> I am hindered in debugging this fully as yet since: >> >> >> >> a. I am new to Nuttx and haven't yet sussed how to enable any low level >> debug-type stuff (I have used menuconfig to enable anything that seems to >> be >> related but I'm sure I missed stuff) >> b. I haven't yet coerced my Eclipse IDE (under Windows 10, but code >> configured and compiled using Windows WSL) to "see" the source code >> properly >> to enable me to insert breakpoints (Segger J-link). Not wedded to Eclipse, >> but it is a known entity for me and at least downloads/runs/debugs the >> board!) >> >> >> >> Can anyone point me in the direction of why, or a way to find out why, the >> call to open the device would crash the board rather than return an error? >> Other devices (such as Flexcom USARTs open OK and work - well, after I >> fixed >> some arch issues for Flexcoms on the SAMA5 anyway!!). The board-specific >> code (sam_can.c) I am using is based on the code for the sama5d2-xult >> board >> and seems pretty trivial, and largely similar to many other architectures >> and boards.
Re: [VOTE] Apache NuttX 10.1.0 (incubating) RC1 release
+1 with caveat that I need to backport the compiler patch. Toolchain: clang version 13.0.0 (g...@github.com:jacobly0/llvm-project.git ff3f5b865edbac826fdd251f810da833dda775de) Target: ez80-none-unknown-elf Thread model: posix - LICENSE, NOTICE, README.md, DISCLAIMER-WIP present in both repositories. - Build for eZ80 using commit ID 9d4742af00 backported from master, plus patch for Z80 ELF support (PR to happen when tested adequately) - Build size is 253,610 text (down from 257,713 bytes for RC0), 197 bytes in data (unchanged from RC0) NuttShell (NSH) NuttX-10.1.0 nsh> free total used freelargest Umem: 253856 66272 187584 184736 -- bje On Tue, May 4, 2021 at 1:25 AM Alan Carvalho de Assis wrote: > Hi Everyone, please submit some information when you test it: > > - Used toolchain: i.e. last line of "gcc -v" is enough > - ELF nuttx size: i.e. "arm-none-eabi-size nuttx" > - Result of internal nsh free command. > > It will help us to track the size increase from a release to another. > > BR, > > Alan > > On 5/3/21, alin.jerpe...@sony.com wrote: > > Hello all, > > > > This is the latest tarball > > > > I am sorry for the confusion > > > > Thanks > > Alin > > > > > > -Original Message- > > From: Nathan Hartman > > Sent: den 3 maj 2021 17:14 > > To: dev@nuttx.apache.org > > Subject: Re: [VOTE] Apache NuttX 10.1.0 (incubating) RC1 release > > > > On Mon, May 3, 2021 at 1:22 AM Alin Jerpelea wrote: > >> > >> Hello all, > >> Apache NuttX (Incubating) 10.1.0 RC1 has been staged under [1] and > >> it's time to vote on accepting it for release. If approved we will > >> seek final release approval from the IPMC. 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 [P]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-10.1.0-RC1 > >> Hash for the release incubating-nuttx tag: > >> 3130ff691e386934eb276587a24d1efacf3bb30b > >> Hash for the release incubating-nuttx-apps tag: > >> 4348d91d1356335483089c3865282d80f13bedcd > >> > >> [1] > >> https://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/inc > >> ubator/nuttx/10.1.0-RC1/__;!!JmoZiZGBv3RvKRSx!u7bO_5TgIUsO429c5U2xXTz4 > >> HI0T2TqnSm836Wse15R0SGxhUdWk3viAcBF0cM9oFQ$ > >> [2]https://urldefense.com/v3/__https://raw.githubusercontent.com/apach > >> e/incubator-nuttx/nuttx-10.1.0-RC1/ReleaseNotes__;!!JmoZiZGBv3RvKRSx!u > >> 7bO_5TgIUsO429c5U2xXTz4HI0T2TqnSm836Wse15R0SGxhUdWk3viAcBELDkRTXA$ > >> [3] > >> https://urldefense.com/v3/__https://www.apache.org/dev/release.html*ap > >> proving-a-release__;Iw!!JmoZiZGBv3RvKRSx!u7bO_5TgIUsO429c5U2xXTz4HI0T2 > >> TqnSm836Wse15R0SGxhUdWk3viAcBGKE_xsSw$ > >> [4]https://urldefense.com/v3/__https://cwiki.apache.org/confluence/dis > >> play/NUTTX/Validating*a*staged*Release__;Kysr!!JmoZiZGBv3RvKRSx!u7bO_5 > >> TgIUsO429c5U2xXTz4HI0T2TqnSm836Wse15R0SGxhUdWk3viAcBE_QwknXQ$ > > > > > > Just to be sure I don't misunderstand, this is the latest release > candidate > > to be tested now? > > > > In the future, I recommend to increment the -RC numbers each time there > are > > new tarballs, to avoid any potential confusion. > > > > If this is indeed the latest RC, I'll try to test it today. > > > > Thanks for all your hard work!! > > > > Cheers, > > Nathan > > >
