Iso 14443-4 Pdf

0 views

Skip to first unread message

Emmanuel Des Meaux

unread,

Aug 3, 2024, 1:29:14 PM8/3/24

to nickskimpardi

During the connection protocol some parameters are exchanged that you can use to determine the card's capabilities. For example, the SAK byte will inform the reader whether the card is ISO 14443-4, and even if it is MIFARE Plus (there is an NXP document explaining which bits you have to read).Then you have ATS (Answer To Select), which contains a lot of useful information about the card. Have a look at ISO 14443-4 and at ISO 7816-4.

On top of it there are implemented interfaces of different cards and if both sides: card - carddriver are compatible they will communicate. If not, there will be errors on that level. So you know you will need to use different card driver.

Point is your communication has to succed on all levels so don't worry to try to communicate with card by not compatible protocol - if you (by some miracle) will not get error on CardProtocol level you will definitely get one on your application level and result will be same. Good Luck!

I'm trying to read and write values to an STmicro tag(ST25TA02KB-D, ISO 14443-4) using the X-Nucleo board from a python program. I've tried a number of approaches(waveshare pi hat, standalone PN532 modules, using libnfc and adafruit libraries, to list) but none really work and it's honestly a little out of my depth.

What we're trying to do is automate the process of reading the memory and writing a short text file- essentially a model number. Unfortunately we're locked into the ST25TA at this point, and revising the board isn't a possibility, though there are some alternative options to interface with it, namely a waveshare PN532 NFC hat, or a standalone PN532 module.

it seems GPIO7 cannot be allocated by our nfc application. Likely someone else is using it. You could investigate (/sys, gpio tools) who is using the device and likely it will give you hints how to disable the blocking function. However I don't have all the tools currently at hand to guide you in detail through the process.

We're using a raspberry pi 4 with Raspbian 11, as the version used in the documentation isn't supported by our pi. After following the updated readme(thank you) and a few restarts we no longer get the GPIO error. The program runs and the led's(F, B, A, and TX) on the nucleo board begin flashing.

However, it doesn't seem to be picking up any of the nfc tags(known good ST25's and mifare fobs) placed on the antenna pcb. This doesn't return any sort of error to diagnose, it just continues scanning.

I would suggest to check that ST25R3916 is properly connected to RPi GPIO 7 (CE1). If using an ARPI600 interposer, make sure to have the proper jumper configuration (ARPI600 A0 should be connected to RPi CE1). Do you use an ARPI600 interposer or "flying" wires?

I also suggest to define ST25R_SELFTEST in your build: this define adds extra checking during initialization of the ST25R3916. In particular, this checks the proper handling of the ST25R396 IRQ: see st25r3916Initialize (an ERR_TIMEOUT error is returned if the IRQ i not properly handled)

I've tried both of these approaches, editing cmake, then platform.h- shown below:Neither produces any visible change, but I may be doing it wrong. I made a build with "cmake -DCMAKE_BUILD_TYPE=Debug .." per the readme file, here's what I see in the GDB text ui

Hello. I need to read 14443-4A card in mifare classic mode. I can to do that. NXP Reader Library always activates card in 14443-4 mode because of Sak bit 6 =1. SAK of needed card is 0x38. Does anybody have any ideas how to activate such card like MifareClassic?

you need to activate just the layer 3 of the ISO 14443. if you are using an example that detects the card and activate it depending on the card responses, like the discovery loop examples in the NFC library. the best here would be that you use only the example for Mifare classic available in the NFC reader library. so the card only works in Classic mode, as you may know mifare plus can be activated in layer 4 in SL1 ( classic mode).

Hello. I need to read 14443-4A card in mifare classic mode. I can not do that. NXP Reader Library always activates card in 14443-4 mode because of Sak bit 6 =1. SAK of needed card is 0x38. Does anybody have any ideas how to activate such card like MifareClassic?

All of the models in the YubiKey 5 (FIPS/CSPN) Series provide a USB 2.0 interface, regardless of the form factor of the USB connector. The YubiKey presents itself as a USB composite device in addition to each individual USB interface.

When connecting the YubiKey 5Ci through Lightning, the interfaces enabled setting is common to both USB-C and Lightning. Enabling or disabling an interface applies to both connections.

The NFC-capable hardware security keys from Yubico (YubiKey 5 NFC, YubiKey 5C NFC, YubiKey 5 NFC FIPS, YubiKey 5C NFC FIPS, Security Key NFC, Security Key C NFC) provide an NFC wireless interface in addition to USB. These models include the RFID standard specific to the ISO/IEC 14443-A and ISO/IEC 14443-4 NFC format. RFID implementations not included in the listed ISO standards are not supported.

For operations that require a touch, all touch requests within the first 20 seconds of the operation succeed. To help prevent unintended access, a YubiKey placed on a desktop NFC reader might power down unless the NFC reader has power-cycled, which prevents the YubiKey from powering down. To regain connectivity with an NFC reader, remove the YubiKey from the reader and reposition it on the reader.