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 <sath...@touchenergy.in> 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 <acas...@gmail.com> > 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 <sath...@touchenergy.in> 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 >> >>> >> >> >> > >> >
