search

timmerk / mfoc

Automatically exported from code.google.com/p/mfoc
GNU General Public License v2.0
1 stars 0 forks source link

nfc_initiator_mifare_cmd always returns Timeout #9

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. git clone nfclib / compile / install / test

#nfc-list 
nfc-list uses libnfc libnfc-1.7.0-51-g7b7f506
NFC device: SCM Micro / SCL3711-NFC&RW opened
1 ISO14443A passive target(s) found:
ISO/IEC 14443A (106 kbps) target:
    ATQA (SENS_RES): 00  04  
       UID (NFCID1): 37  08  xx  xx  
      SAK (SEL_RES): 88

>> nfc lib is working

2. git clone mfoc / autoconf / make
3. run mfoc

What is the expected output? What do you see instead?

+ running mfoc
> old version was running (was in early 2013)
instead error occurs: nfc_initiator_mifare_cmd: Timeout

What version of the product are you using? On what operating system?
libnfc libnfc-1.7.0-51-g7b7f506
mfoc head (23.01.2014 git: 290a0759567d)
ubuntu 13.10
reader SCM Micro / SCL3711 (USB dongle)

Please provide any additional information below.

# mfoc -O test
ISO/IEC 14443A (106 kbps) target:
    ATQA (SENS_RES): 00  04  
* UID size: single
* bit frame anticollision supported
       UID (NFCID1): 37  08  xx  xx  
      SAK (SEL_RES): 88  
* Not compliant with ISO/IEC 14443-4
* Not compliant with ISO/IEC 18092

Fingerprinting based on MIFARE type Identification Procedure:
* SmartMX with MIFARE 1K emulation
Other possible matches based on ATQA & SAK values:
* Mifare Classic 1K Infineon

Try to authenticate to all sectors with default keys...
Symbols: '.' no key found, '/' A key found, '\' B key found, 'x' both keys found
[Key: ffffffffffff] -> [xnfc_initiator_mifare_cmd: Timeout

Original issue reported on code.google.com by schroedl...@googlemail.com on 23 Jan 2014 at 9:51

GoogleCodeExporter commented 9 years ago 
I did some further investigation.

If I blacklist linux modules 'nfc' and 'pn533' everything is working.
If I load linux modules 'nfc' and 'pn533' and unload it, i have this issue.

pull off and plug in of usb-dongle can repair this behavior.

Another possibility to trigger this issue is to cancel the computing on keys.

>> conclusion: it seems the dongle isn't setup correctly and shutdown on 
program end.
>> don't know if it is a mfoc or libnfc task

Original comment by schroedl...@googlemail.com on 30 Jan 2014 at 9:17