[VOTE] Apache NuttX 10.1.0 (incubating) RC0 release
Hello all, Apache NuttX (Incubating) 10.1.0 RC0 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-RC0 Hash for the release incubating-nuttx tag: f380c919f04d5ee88e0a83f5632cc83af503664f Hash for the release incubating-nuttx-apps tag: 4348d91d1356335483089c3865282d80f13bedcd [1] https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.1.0-RC0/ [2]https://raw.githubusercontent.com/apache/incubator-nuttx/nuttx-10.1.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: SPI driver is not working in S32K144 EVB
Hi Alan, Thanks for your support. We are using S32K144EVB with BCC 33771 as the AFE (14S). WIth this we had to include the software Chip select logic on the GPIO pin to make the SPI read work. Now we are debugging the SPI TX which is not yet fully working. Thanks, Sathish On Fri, 16 Apr 2021 at 22:24, Alan Carvalho de Assis wrote: > Hi Sathish, > > Are you using a supported S32K1xx board or a custom board? > > There are support to LPSPIx i then EVB boards directory, so I'm > assuming it was tested/validated. > > Maybe someone from NXP could confirm/deny it. > > Do you have analyzed the SPI pins? if you don't implement the Chip > Select logic correctly on your board it will not work. Normally NuttX > doesn't use the HW SPI CS. > > It is obvious for us, but could be something new for you. > > BR, > > Alan > > On 4/16/21, Sathish Touch energy wrote: > >> > >> > >>> Hello, > >>> We are trying to check SPI driver functionality for our application on > >>> NUTTX-10.0.0 baseline. > >>> On the supported platform link ( > >>> > https://nuttx.apache.org/docs/latest/introduction/detailed_support.html#other-armv4 > ) > >>> of nuttx we see the support for SPI driver is available for S32K146 & > >>> S32K148. We adapted the code to have the correct SPI clock but still > the > >>> receive data is not fully working. Any clue on how to proceed on this. > >>> > >>> Regards, > >>> Sathish > >>> > >> > > >
Re: SPI driver is not working in S32K144 EVB
Hi Sathish, Are you using a battery solution similar to this board: https://mouser.com/new/nxp-semiconductors/nxp-rd33771cntrevm-reference-design/ I suggest you to used an logic analyzer to verify if the signals are correct. You can do it manually, but a LA will save your time. BR, Alan On 4/18/21, Sathish Touch energy wrote: > Hi Alan, > Thanks for your support. We are using S32K144EVB with BCC 33771 as the > AFE (14S). > WIth this we had to include the software Chip select logic on the GPIO pin > to make the SPI read work. > Now we are debugging the SPI TX which is not yet fully working. > > > Thanks, > Sathish > > On Fri, 16 Apr 2021 at 22:24, Alan Carvalho de Assis > wrote: > >> Hi Sathish, >> >> Are you using a supported S32K1xx board or a custom board? >> >> There are support to LPSPIx i then EVB boards directory, so I'm >> assuming it was tested/validated. >> >> Maybe someone from NXP could confirm/deny it. >> >> Do you have analyzed the SPI pins? if you don't implement the Chip >> Select logic correctly on your board it will not work. Normally NuttX >> doesn't use the HW SPI CS. >> >> It is obvious for us, but could be something new for you. >> >> BR, >> >> Alan >> >> On 4/16/21, Sathish Touch energy wrote: >> >> >> >> >> >>> Hello, >> >>> We are trying to check SPI driver functionality for our application >> >>> on >> >>> NUTTX-10.0.0 baseline. >> >>> On the supported platform link ( >> >>> >> https://nuttx.apache.org/docs/latest/introduction/detailed_support.html#other-armv4 >> ) >> >>> of nuttx we see the support for SPI driver is available for S32K146 & >> >>> S32K148. We adapted the code to have the correct SPI clock but still >> the >> >>> receive data is not fully working. Any clue on how to proceed on >> >>> this. >> >>> >> >>> Regards, >> >>> Sathish >> >>> >> >> >> > >> >
Re: [VOTE] Apache NuttX 10.1.0 (incubating) RC0 release
Is it just me or there is an issue with the checksum of the apps tar? On Sun, Apr 18, 2021 at 3:06 PM Alin Jerpelea wrote: > > Hello all, > Apache NuttX (Incubating) 10.1.0 RC0 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-RC0 > Hash for the release incubating-nuttx tag: > f380c919f04d5ee88e0a83f5632cc83af503664f > Hash for the release incubating-nuttx-apps tag: > 4348d91d1356335483089c3865282d80f13bedcd > > [1] https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.1.0-RC0/ > [2]https://raw.githubusercontent.com/apache/incubator-nuttx/nuttx-10.1.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 10.1.0 (incubating) RC0 release
On Sun, Apr 18, 2021 at 9:38 AM Abdelatif Guettouche wrote: > > Is it just me or there is an issue with the checksum of the apps tar? > Alin, Can you check this an re-upload. You can verify locally as I showed here https://gist.github.com/btashton/ee474723013a7040186c91d41a4c7fad#check-the-release-artifacts After it is uploaded you can also run this script against the uploaded files, which is where we see the bad checksum. ❯ ./tools/checkrelease.sh --url https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.1.0-RC0 Downloading release files from https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.1.0-RC0/ gpg: directory '/tmp/nuttx-checkrelease/.gnupg' created gpg: keybox '/tmp/nuttx-checkrelease/.gnupg/pubring.kbx' created gpg: /tmp/nuttx-checkrelease/.gnupg/trustdb.gpg: trustdb created gpg: key E1B6E30DB05D6280: public key "Brennan Ashton " imported gpg: key 9E711BAD3264C061: public key "Alin Jerpelea " imported gpg: Total number processed: 2 gpg: imported: 2 OK: https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.1.0-RC0/../KEYS is imported. Checking apache-nuttx-10.1.0-incubating.tar.gz sha512... OK: apache-nuttx-10.1.0-incubating.tar.gz sha512 hash matches. Checking apache-nuttx-10.1.0-incubating.tar.gz GPG signature: gpg: Signature made Sun 18 Apr 2021 07:03:03 AM PDT gpg:using RSA key C26CE5B1F2F08DBC0C4DE2409E711BAD3264C061 gpg: Good signature from "Alin Jerpelea " [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: C26C E5B1 F2F0 8DBC 0C4D E240 9E71 1BAD 3264 C061 OK: apache-nuttx-10.1.0-incubating.tar.gz gpg signature matches. Checking apache-nuttx-10.1.0-incubating.tar.gz for required files: OK: all required files exist in nuttx. Checking apache-nuttx-apps-10.1.0-incubating.tar.gz sha512... sha512sum: WARNING: 1 computed checksum did NOT match apache-nuttx-apps-10.1.0-incubating.tar.gz: FAILED - apache-nuttx-apps-10.1.0-incubating.tar.gz sha512 hash does not match. Checking apache-nuttx-apps-10.1.0-incubating.tar.gz GPG signature: gpg: Signature made Sun 18 Apr 2021 07:03:03 AM PDT gpg:using RSA key C26CE5B1F2F08DBC0C4DE2409E711BAD3264C061 gpg: Good signature from "Alin Jerpelea " [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: C26C E5B1 F2F0 8DBC 0C4D E240 9E71 1BAD 3264 C061 OK: apache-nuttx-apps-10.1.0-incubating.tar.gz gpg signature matches. Checking apache-nuttx-apps-10.1.0-incubating.tar.gz for required files: OK: all required files exist in apps. Trying to build nuttx sim:nsh...
Re: [VOTE] Apache NuttX 10.1.0 (incubating) RC0 release
Hi all, The sum is reuploaded now seems to be ok Thansk for reporing it Regards Alin On Sun, Apr 18, 2021 at 7:25 PM Brennan Ashton wrote: > On Sun, Apr 18, 2021 at 9:38 AM Abdelatif Guettouche > wrote: > > > > Is it just me or there is an issue with the checksum of the apps tar? > > > > Alin, > Can you check this an re-upload. You can verify locally as I showed here > > https://gist.github.com/btashton/ee474723013a7040186c91d41a4c7fad#check-the-release-artifacts > > After it is uploaded you can also run this script against the uploaded > files, which is where we see the bad checksum. > > ❯ ./tools/checkrelease.sh --url > https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.1.0-RC0 > Downloading release files from > https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.1.0-RC0/ > gpg: directory '/tmp/nuttx-checkrelease/.gnupg' created > gpg: keybox '/tmp/nuttx-checkrelease/.gnupg/pubring.kbx' created > gpg: /tmp/nuttx-checkrelease/.gnupg/trustdb.gpg: trustdb created > gpg: key E1B6E30DB05D6280: public key "Brennan Ashton > " imported > gpg: key 9E711BAD3264C061: public key "Alin Jerpelea > " imported > gpg: Total number processed: 2 > gpg: imported: 2 > OK: > https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.1.0-RC0/../KEYS > is imported. > Checking apache-nuttx-10.1.0-incubating.tar.gz sha512... > OK: apache-nuttx-10.1.0-incubating.tar.gz sha512 hash matches. > > Checking apache-nuttx-10.1.0-incubating.tar.gz GPG signature: > gpg: Signature made Sun 18 Apr 2021 07:03:03 AM PDT > gpg:using RSA key C26CE5B1F2F08DBC0C4DE2409E711BAD3264C061 > gpg: Good signature from "Alin Jerpelea " > [unknown] > gpg: WARNING: This key is not certified with a trusted signature! > gpg: There is no indication that the signature belongs to the > owner. > Primary key fingerprint: C26C E5B1 F2F0 8DBC 0C4D E240 9E71 1BAD 3264 C061 > OK: apache-nuttx-10.1.0-incubating.tar.gz gpg signature matches. > > Checking apache-nuttx-10.1.0-incubating.tar.gz for required files: > OK: all required files exist in nuttx. > > Checking apache-nuttx-apps-10.1.0-incubating.tar.gz sha512... > sha512sum: WARNING: 1 computed checksum did NOT match > apache-nuttx-apps-10.1.0-incubating.tar.gz: FAILED > - apache-nuttx-apps-10.1.0-incubating.tar.gz sha512 hash does not match. > > Checking apache-nuttx-apps-10.1.0-incubating.tar.gz GPG signature: > gpg: Signature made Sun 18 Apr 2021 07:03:03 AM PDT > gpg:using RSA key C26CE5B1F2F08DBC0C4DE2409E711BAD3264C061 > gpg: Good signature from "Alin Jerpelea " > [unknown] > gpg: WARNING: This key is not certified with a trusted signature! > gpg: There is no indication that the signature belongs to the > owner. > Primary key fingerprint: C26C E5B1 F2F0 8DBC 0C4D E240 9E71 1BAD 3264 C061 > OK: apache-nuttx-apps-10.1.0-incubating.tar.gz gpg signature matches. > > Checking apache-nuttx-apps-10.1.0-incubating.tar.gz for required files: > OK: all required files exist in apps. > > Trying to build nuttx sim:nsh... >
Re: [VOTE] Apache NuttX 10.1.0 (incubating) RC0 release
Thanks Alin & Brennan. +1 for me: - LICENSE, NOTICE and DISCLAIMER files exit in both repos. - Signatures and checksums valid. - Can build from source. On Sun, Apr 18, 2021 at 6:41 PM Alin Jerpelea wrote: > > Hi all, > > The sum is reuploaded now seems to be ok > Thansk for reporing it > > Regards > Alin > > > On Sun, Apr 18, 2021 at 7:25 PM Brennan Ashton > wrote: > > > On Sun, Apr 18, 2021 at 9:38 AM Abdelatif Guettouche > > wrote: > > > > > > Is it just me or there is an issue with the checksum of the apps tar? > > > > > > > Alin, > > Can you check this an re-upload. You can verify locally as I showed here > > > > https://gist.github.com/btashton/ee474723013a7040186c91d41a4c7fad#check-the-release-artifacts > > > > After it is uploaded you can also run this script against the uploaded > > files, which is where we see the bad checksum. > > > > ❯ ./tools/checkrelease.sh --url > > https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.1.0-RC0 > > Downloading release files from > > https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.1.0-RC0/ > > gpg: directory '/tmp/nuttx-checkrelease/.gnupg' created > > gpg: keybox '/tmp/nuttx-checkrelease/.gnupg/pubring.kbx' created > > gpg: /tmp/nuttx-checkrelease/.gnupg/trustdb.gpg: trustdb created > > gpg: key E1B6E30DB05D6280: public key "Brennan Ashton > > " imported > > gpg: key 9E711BAD3264C061: public key "Alin Jerpelea > > " imported > > gpg: Total number processed: 2 > > gpg: imported: 2 > > OK: > > https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.1.0-RC0/../KEYS > > is imported. > > Checking apache-nuttx-10.1.0-incubating.tar.gz sha512... > > OK: apache-nuttx-10.1.0-incubating.tar.gz sha512 hash matches. > > > > Checking apache-nuttx-10.1.0-incubating.tar.gz GPG signature: > > gpg: Signature made Sun 18 Apr 2021 07:03:03 AM PDT > > gpg:using RSA key C26CE5B1F2F08DBC0C4DE2409E711BAD3264C061 > > gpg: Good signature from "Alin Jerpelea " > > [unknown] > > gpg: WARNING: This key is not certified with a trusted signature! > > gpg: There is no indication that the signature belongs to the > > owner. > > Primary key fingerprint: C26C E5B1 F2F0 8DBC 0C4D E240 9E71 1BAD 3264 C061 > > OK: apache-nuttx-10.1.0-incubating.tar.gz gpg signature matches. > > > > Checking apache-nuttx-10.1.0-incubating.tar.gz for required files: > > OK: all required files exist in nuttx. > > > > Checking apache-nuttx-apps-10.1.0-incubating.tar.gz sha512... > > sha512sum: WARNING: 1 computed checksum did NOT match > > apache-nuttx-apps-10.1.0-incubating.tar.gz: FAILED > > - apache-nuttx-apps-10.1.0-incubating.tar.gz sha512 hash does not match. > > > > Checking apache-nuttx-apps-10.1.0-incubating.tar.gz GPG signature: > > gpg: Signature made Sun 18 Apr 2021 07:03:03 AM PDT > > gpg:using RSA key C26CE5B1F2F08DBC0C4DE2409E711BAD3264C061 > > gpg: Good signature from "Alin Jerpelea " > > [unknown] > > gpg: WARNING: This key is not certified with a trusted signature! > > gpg: There is no indication that the signature belongs to the > > owner. > > Primary key fingerprint: C26C E5B1 F2F0 8DBC 0C4D E240 9E71 1BAD 3264 C061 > > OK: apache-nuttx-apps-10.1.0-incubating.tar.gz gpg signature matches. > > > > Checking apache-nuttx-apps-10.1.0-incubating.tar.gz for required files: > > OK: all required files exist in apps. > > > > Trying to build nuttx sim:nsh... > >
RE: [EXT] Re: SPI driver is not working in S32K144 EVB
Hi Sathish, Colleagues of mine, have worked on the BMS-772 (S32K144 + MC33772B) which also runs NuttX. To get the BCC working we've applied some patches that yet have to upstreamed to NuttX. But you can check out the source code here https://github.com/NXPHoverGames/RDDRONE-BMS772 Furthermore they gave a nice introduction to our BMS-772 in combination with NuttX during the NuttX online workshop. https://youtu.be/CIpa3_70PCY?t=17135 -Original Message- From: Alan Carvalho de Assis Sent: Sunday, April 18, 2021 6:32 PM To: dev@nuttx.apache.org Subject: [EXT] Re: SPI driver is not working in S32K144 EVB Caution: EXT Email Hi Sathish, Are you using a battery solution similar to this board: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmouser.com%2Fnew%2Fnxp-semiconductors%2Fnxp-rd33771cntrevm-reference-design%2F&data=04%7C01%7Cpeter.vanderperk%40nxp.com%7Cea24695cc7cb4ca2830b08d90287783f%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637543603148196566%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=KYnEZIJfc1BGMxO3dShoOwntMA9anGaOavPagk3tw9A%3D&reserved=0 I suggest you to used an logic analyzer to verify if the signals are correct. You can do it manually, but a LA will save your time. BR, Alan On 4/18/21, Sathish Touch energy wrote: > Hi Alan, > Thanks for your support. We are using S32K144EVB with BCC 33771 as the > AFE (14S). > WIth this we had to include the software Chip select logic on the GPIO > pin to make the SPI read work. > Now we are debugging the SPI TX which is not yet fully working. > > > Thanks, > Sathish > > On Fri, 16 Apr 2021 at 22:24, Alan Carvalho de Assis > > wrote: > >> Hi Sathish, >> >> Are you using a supported S32K1xx board or a custom board? >> >> There are support to LPSPIx i then EVB boards directory, so I'm >> assuming it was tested/validated. >> >> Maybe someone from NXP could confirm/deny it. >> >> Do you have analyzed the SPI pins? if you don't implement the Chip >> Select logic correctly on your board it will not work. Normally NuttX >> doesn't use the HW SPI CS. >> >> It is obvious for us, but could be something new for you. >> >> BR, >> >> Alan >> >> On 4/16/21, Sathish Touch energy wrote: >> >> >> >> >> >>> Hello, >> >>> We are trying to check SPI driver functionality for our >> >>> application on >> >>> NUTTX-10.0.0 baseline. >> >>> On the supported platform link ( >> >>> >> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fnut >> tx.apache.org%2Fdocs%2Flatest%2Fintroduction%2Fdetailed_support.html% >> 23other-armv4&data=04%7C01%7Cpeter.vanderperk%40nxp.com%7Cea24695 >> cc7cb4ca2830b08d90287783f%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0% >> 7C637543603148196566%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQ >> IjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Yim%2BRrY >> fyZu4r%2FyN%2F9Kgvfibqw375eJcUwZ0Sx50ju0%3D&reserved=0 >> ) >> >>> of nuttx we see the support for SPI driver is available for >> >>> S32K146 & S32K148. We adapted the code to have the correct SPI >> >>> clock but still >> the >> >>> receive data is not fully working. Any clue on how to proceed on >> >>> this. >> >>> >> >>> Regards, >> >>> Sathish >> >>> >> >> >> > >> >
