2026-04-16 11:53 PM
Dear Ulysses,
Sorry to bother you again.
code :
Solved! Go to Solution.
2026-04-21 5:18 AM
Hi,
as communicated in previous posts: Go step by step! First verify your CRC and parity and bit oriented sending is working using a well-known command without crypto. E.g. use a T2T and perform a read block using the mentioned methods. Only then move to your crypto.
BR, Ulysses
2026-04-17 12:09 AM
Hi,
Yes, you can also transfer 4 bits.
Ulysses
2026-04-17 6:38 PM
RFAL has to use st25r200WriteFifo to send data which can only send full bytes. I don't think RFAL can send bits.
I'm trying reading block data from M1 card which need encoded parity. When encoded parity is the same as normal parity and use rfalTransceiveBlockingTxRx and RFAL_TXRX_FLAGS_PAR_TX_AUTO, I can read data successfully. So encoding is correct. Nothing is wrong but sending 36 bits data ifself.
Could you help check whether my code is wrong or RFAL doesn't support incomplete bytes sending?
code:
2026-04-19 11:53 PM
Hi,
yes, only full bytes are written into FIFO. But nbtx bits tell how many bits to transmit from the last byte.
There is no need to call rfalIsTransceiveInTx() or rfalTransceiveBlockingRx(). Just wait until rfalGetTransceiveStatus() does not return RFAL_ERR_BUSY anymore.
From a first glimpse the rest look correct.
BR, Ulysses
2026-04-20 11:17 PM
2026-04-21 5:18 AM
Hi,
as communicated in previous posts: Go step by step! First verify your CRC and parity and bit oriented sending is working using a well-known command without crypto. E.g. use a T2T and perform a read block using the mentioned methods. Only then move to your crypto.
BR, Ulysses