Card Emulation (CE) NFC-V ST25R3918

[io]

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 

[Brian TIDAL · Accepted solution]

Hi,

ST25R3918 natively supports card emulation for NFC-A and NFC-F technologies. The RFAL includes definitions for listening in NFC-A, NFC-B, NFC-F, and NFC-AP2P and manages card emulation in NFC-A and NFC-F.

Some customer applications, such as Flipper Zero, have implemented an ISO/IEC 15693 card emulation using the ST25R3916 stream mode or transparent mode. See the Flipper Zero firmware source code on GitHub.

I cannot comment on additional reading distance.

Regards,
BT