MPC5746C DSPI (slave SPI mode) lost one byte between frames if underflow occurred

cancel
Showing results for 
Search instead for 
Did you mean: 

MPC5746C DSPI (slave SPI mode) lost one byte between frames if underflow occurred

688 Views
wesleyxie
Contributor III

Hi, NXP guys

khumphriMandarDeactivated userdhavalRHinnenjimtrudeauMartinvladcentea

In our project, we configure MPC5746C DSPI to work in slave SPI mode,

the Master side clock is 5MHz, read 32byte with continuous chip select asserted.

I found that , it always lost the certain byte between 32-bytes frames if underflow occurred before MPC5746C switch to next DMA transfer (DMA interrupt take time to response and handle).

PS:

1. if I down the Master CLK to 1MHz (no underflow between DMA transfer), this issue disappeared.

2. if the Master side switched the CS to non-continuous mode (deassert CS each byte), still underflow between DMA transfer, but this issue disappeared. 

pastedImage_1.png

pastedImage_2.png

4 Replies

239 Views
davidtosenovjan
NXP TechSupport
NXP TechSupport

Hi,

if DSPI works as slave, PUSH into TxFIFO must be done in the moment SS is inactive (if you use polling mode).

 

Let’s have two DSPI's connected as Master-slave. Assume TX-FIFO had 1 entry and a transfer is initiated. When the last-bit is received, the slave's FIFO is empty, hence the internal state-machine moves to an "under-run detect stage" now if we the write the TX-FIFO at this moment the data will not be honored until the slave is de-selected (i.e. SS is de-asserted). If there are subsequent sck clock edges with SS asserted an under-run flag is set although we filled the TX-FIFO even before the next transfer was initiated.

 

So if TxFIFO is being filled by eDMA according to TFFF flag, TxFIFO will never get into state with 1 entry, so the issue does not happen. Note that XBAR priority for eDMA master must be set for higher value than the core, it is mandatory (just to prevent underflow). If underflow happens, the last byte is repeated as you can see on your screenshots.

Your workarounds are both OK, because both solve the issue I have described above.

239 Views
wesleyxie
Contributor III

hi David, 

Thanks for your reply.

but I am using eDMA to fill the slave TxFIFO, and the issue is still happen.

 

the issue can be reproduce as below:

1. master work at 5MHz, and keep clocking SCK of 32 bytes frame, with continuous CS asserted (CS deasserted between frames).

2. slave(MPC5746C) set the eDMA to transfer 10 bytes to DSPI, then set 25 bytes in eDMA completed ISR.

    this is to make sure there is a DSPI underflow occured in one 32 bytes reading frame. 

3. the certain byte between 32 bytes frame is always missed.

for example,

MPC5746C first transfer:

01 02 03 04 05 06 07 08 09 0A              (10 bytes, in first 32 bytes frame of master)

before eDMA start second transfer, underflow happen:

0A 0A 0A                                                (3 bytes, in first 32 bytes frame of master)

MPC5746C response eDMA completed ISR and start second transfer:

0B 0C 0D ~~~~~~  1D 1F 20                 (19 bytes in first 32 bytes frame of master, CS deasserted, 2 bytes in second 32 bytes frame)

the "1E" is missed, which should be the first byte in second 32 bytes frame.

 

/WX

0 Kudos

239 Views
davidtosenovjan
NXP TechSupport
NXP TechSupport

And your XBAR priority setting?

239 Views
wesleyxie
Contributor III

Hi, guys

khumphriMandar‌Deactivated user‌dhavalRHinnenjimtrudeauMartinvladcenteamarc.paquetteRChapman

any idea ?

/WX

0 Kudos