whywilson
Data frame POSTAMBLE error.
Hi everyone. I just want to say when i try to read an old card with :
[Offline] Unknown --> hw connect -p /dev/ttyS0 Connecting to device on port /dev/ttyS0 Device: PN532 [USB] PN532 --> hf mf rdbl --block 9 -k 4713055D5118 Block 9 Failed to read [USB] PN532 --> hf mf rdbl --block 9 -k 4713055D5118 Data frame POSTAMBLE error. Block 9 Failed to read
The cad type is:
1 ISO14443A passive target(s) found:
ISO/IEC 14443A (106 kbps) target:
ATQA (SENS_RES): 00 04
UID (NFCID1): 59 29 12 5d
SAK (SEL_RES): 08
I found this in this place: https://community.nxp.com/t5/NFC/PN532-corrupt-data-in-RS232-mode/m-p/1207669#M8037 which tells: ''' I think I already found out what the error is. I connected Vcc to 5V and the problem was the same. So I decided to connect the NFC module to a PC COM port and send the same frames, and it works very well, the module has no problems. Then I reconnected the logic analyzer, to see what the microcontroller sends to the PN532 on this occasion and I discovered that it sends more bytes than it should, for example the frame to read the tag should be like this: {00} {00} {FF} {04} {FC} {D4} {4A} {01} {00} {E1} {00} But it was actually sending this: {00} {00} {FF} {04} {FC} {D4} {4A} {01} {00} {E1} {00} {00} {00} {00} It is a problem with the microcontroller that although I disabled the interrupt by transmission in the last byte, it still transmitted 3 more bytes. By means of an auxiliary flag I have controlled the sending of bytes is correct and the module responds correctly. '''
so will be nice if is fixed. thanks
Could you try with debug mode and show the full data log here?
python script/pn532_cli_main.py --debug
hi @whywilson thanks for the response.
Connecting to device on port /dev/ttyS0 => 0000FF03FDD414011700 <= 0000FF02FED5151600 => 0000FF02FED4AA8200 Device: PN532 [USB] PN532 --> hf mf rdbl --block 9 -k 4713055D5118 => 0000FF03FDD414011700 <= 0000FF02FED5151600 => 0000FF04FCD44A0100E100 <= 0000FF0CF4D54B0101000408045929375DB800 => 0000FF0FF1D4400160094713055D51185929375D6A00 <= 0000FF03FDD54100EA00 => 0000FF05FBD440013009B200 Block 9 Failed to read [USB] PN532 --> hf mf rdbl --block 9 -k 4713055D5118 => 0000FF03FDD414011700 Data frame POSTAMBLE error. => 0000FF04FCD44A0100E100 <= 0000FF0CF4D54B0101000408045929375DB800 => 0000FF0FF1D4400160094713055D51185929375D6A00 <= 0000FF03FDD54100EA00 => 0000FF05FBD440013009B200 Block 9 Failed to rea
The key is correct. cos when i try this i get the full dump:
mfoc -O t -k 4713055D5118 The custom key 0x4713055d5118 has been added to the default keys Found Mifare Classic 1k tag ISO/IEC 14443A (106 kbps) target: ATQA (SENS_RES): 00 04
- UID size: single
- bit frame anticollision supported
UID (NFCID1): 59 29 37 5d
SAK (SEL_RES): 08 - Not compliant with ISO/IEC 14443-4
- Not compliant with ISO/IEC 18092
Fingerprinting based on MIFARE type Identification Procedure:
- MIFARE Classic 1K
- MIFARE Plus (4 Byte UID or 4 Byte RID) 2K, Security level 1
- SmartMX with MIFARE 1K emulation Other possible matches based on ATQA & SAK values:
Try to authenticate to all sectors with default keys... Symbols: '.' no key found, '/' A key found, '' B key found, 'x' both keys found [Key: 4713055d5118] -> [xxxxxxxxxxxxxxxx]
when i try with wrong key this ocurrs (if it helps):
[USB] PN532 --> hf mf rdbl --block 9 -k BADBADBADBAD => 0000FF03FDD414011700 Data frame POSTAMBLE error. => 0000FF04FCD44A0100E100 <= 0000FF0CF4D54B0101000408045929375DB800 => 0000FF0FF1D440016009BADBADBADBAD5929375DE800 <= 0000FF03FDD54114D600 Block 9 Failed to read [USB] PN532 --> hf mf rdbl --block 9 -k BADBADBADBAD => 0000FF03FDD414011700 <= 0000FF02FED5151600 => 0000FF04FCD44A0100E100 <= 0000FF0CF4D54B0101000408045929375DB800 => 0000FF0FF1D440016009BADBADBADBAD5929375DE800 <= 0000FF03FDD54114D600 Block 9 Failed to read
Thank you for the information. And do you have the full dump data of the sector 2? May be it is the issues of the access control byte.
here is it:
| sector 2 |_____________________________________________ 00 00 00 00 ff ff ff ff 00 00 00 00 ff 00 ff 00 00 00 00 00 ff ff ff ff 00 00 00 00 ff 00 ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 47 13 05 5d 51 18 ff 07 80 00 33 33 33 33 33 33
After testing with your sector data. It has no problem to read it with hf mf rdbl commands.