Solved
Card Emulation (CE) NFC-V ST25R3918
Hello ST Community,
I found this forum and the example code to our custom hardware very helpful and are successfully reading both NFC-A/NFC-V and emulating NFC-A on ST25R3918.
During testing, I've noticed that NFC-V tags with NDEF messages can also trigger background reads on both iOS and Android. Since NFC-V have longer ranges, would it be better to do CE using this format?
At the moment the code is using demoT4T to respond to readers in NFC-A CE (RFAL_NFC_LISTEN_TECH_A) in the rfalNfcDiscoverParam.
do
{
rfalNfcWorker();
switch( rfalNfcGetState() )
{
case RFAL_NFC_STATE_ACTIVATED:
transceiveBlocking( NULL, 0, &rxData, &rcvLen, &err, 0, false);
break;
case RFAL_NFC_STATE_DATAEXCHANGE:
case RFAL_NFC_STATE_DATAEXCHANGE_DONE:
txLen = demoCeT4T( rxData, *rcvLen, txBuf, sizeof(txBuf));
transceiveBlocking( txBuf, txLen, &rxData, &rcvLen, &err, RFAL_FWT_NONE, false );
break;
case RFAL_NFC_STATE_START_DISCOVERY:
return;
case RFAL_NFC_STATE_LISTEN_SLEEP:
default:
break;
}
}
while( (err == RFAL_ERR_NONE) || (err == RFAL_ERR_SLEEP_REQ) );Is there sample code where I can push NDEF messages to NFC-V tags? How hard is it to implement and would it be worth the additional range (if there is any)?
Kind Regards,
Maximilian