Firmware currently stuck in the anti collision loop

[maxieds]

Firmware currently stuck in the anti collision loop

[maxieds]

I have a good update: The DESFire emulation in the current firmware is functional with a sane KAOS RevG device. For some reason, maybe RF interference the always-on BT connection on a different device blocked transmission of bits while in the anti-collision loop. It works well now:

$ nfc-anticol
NFC reader: SCM Micro / SCL3711-NFC&RW opened

Sent bits:     26 (7 bits)
Received bits: 44  03  
Sent bits:     93  20  
Received bits: 88  6d  50  74  c1  
Sent bits:     93  70  88  6d  50  74  c1  40  d8  
Sent bits:     50  00  57  cd  

Found tag with
 UID: 886d5074
ATQA: 0344
 SAK: 88

The next plan of attack is to test the rest of the device functionality starting with AES authenticate commands. Then I have some more implementation work to do and test. Then we shall post asking for eager users to help with a more detailed testing procedure elsewhere. 😀

[lvandenb]

Great! I could have a try from end of this week, if there is access to the repo ?
I'm using omnikey readers with built in 14443a protocol handling.
So my experience is in the next layer using Native + AES security.

[maxieds]

I have resolved this issue. Also, native instructions without an initial anti collision loop is working well. Closing this historical first issue. 😃