The S32K344 + 33664 requires LPSPI to be configured in slave mode. After configuring the S32DS SPI as a slave, how does the MCU retrieve data after the 33664 sends data back? Which APIs need to be called?
It has been tested that using Lpspi_Ip_AsyncTransmit() can receive data. I wanted to call this function again in the callback function of Lpspi_Ip_AsyncTransmit() to trigger the reception of the second frame of data replied by MC33664. However, since MC33664 replied with two frames of data, the interval between the two CS is only 2.6us . The callback function of Lpspi_Ip_AsyncTransmit() cannot process it in time, resulting in the data of the second CS not being received. How can I handle this?
Hi @RRR123
As you are configuring the slave to use DMA, call Lpspi_Ip_AsyncTransmit().
Also, as a starting point, you may find the following demo applications useful references:
- S32K344 + MC33664 + MC33775 : RTD 3.0.0 : BMS SDK 1.0.2
- S32K344 + MC33664 + MC33774 : RTD 3.0.0 : BMS SDK 1.0.2
BR, VaneB
Hi @RRR123
As a recommendation, please consider using the PHY_664 driver available in the BMS SDK for MC33664 communication. The PHY_664 driver was specifically designed to manage communication with the MC33664 transceiver.
NXP Battery Management Software Development Kit and Toolchain