1 Reply by 0blar

(8 replies, posted in NFCIP Peer 2 Peer)

Hello jason
Is it possible to post the nexus software you made for testing ?

Regards

Go to forum: NFCIP Peer 2 Peer

2 Reply by 0blar

(23 replies, posted in NXP MIFARE DESFire)

Dear

Can you upload it or may be send it for a try ?

Regards

Go to forum: NXP MIFARE DESFire

3 Reply by 0blar

(2 replies, posted in Hardware Trade Section)

First I want to thank you a bout your work

I wish to know if there are any problem to put all the coponents inside the antenna area ?
Does the performance of the antenna be affected ?

Regards

Go to forum: Hardware Trade Section

4 Reply by 0blar

(32 replies, posted in Hardware Devices)

Hello

Do you have any news regarding your open board project ?

Regards

Go to forum: Hardware Devices

5 Reply by 0blar

(64 replies, posted in MFOC, MFCUK, Crapto1, etc.)

Hi
I put the src folder of the 0.08 version to the first folder  and I successfuly compile the latest version
mfoc -h
mfoc 0.08
...
(ACS ACR122U 00 00 / ACR122U203 - PN532 v1.4 (0x07)=

I use mfoc -O test command with a blank card an is OK
When I use the same command with a non blanck card, I have the same issue
TX: ff  00  00  00  04  d4  06  63  05 
TX: ff  00  00  00  05  d4  08  63  05  40 
TX: ff  00  00  00  04  d4  32  01  00 
TX: ff  00  00  00  06  d4  32  05  00  00  00 
TX: ff  00  00  00  04  d4  06  63  02 
TX: ff  00  00  00  05  d4  08  63  02  b7 
TX: ff  00  00  00  04  d4  06  63  0d 
TX: ff  00  00  00  05  d4  08  63  0d  00 
TX: ff  00  00  00  04  d4  32  01  01 
TX: ff  00  00  00  04  d4  4a  01  00
!Error: tag has been removed

Any idea

Go to forum: MFOC, MFCUK, Crapto1, etc.

6 Reply by 0blar

(64 replies, posted in MFOC, MFCUK, Crapto1, etc.)

Hi
I just tested the 0.08 version with the following command ./autogen.sh --with-libnfc=/usr and I get

checking /usr/include/libnfc/libnfc.h usability... no
checking /usr/include/libnfc/libnfc.h presence... no
checking for /usr/include/libnfc/libnfc.h... no
Error! You need to have libnfc >= 1.2.1.

I didn't have this probleme with the version of the march 13

Any idea ?

Go to forum: MFOC, MFCUK, Crapto1, etc.

7 Reply by 0blar

(64 replies, posted in MFOC, MFCUK, Crapto1, etc.)

I use mfoc-new.tar posted on march 13 from http://code.google.com/p/micmd/downloads/list (with libnfc v318)

Go to forum: MFOC, MFCUK, Crapto1, etc.

8 Reply by 0blar

(64 replies, posted in MFOC, MFCUK, Crapto1, etc.)

I have an ACR122 with P/N ACR122U-WB-R and doesn't work etheir

Go to forum: MFOC, MFCUK, Crapto1, etc.

9 Reply by 0blar

(64 replies, posted in MFOC, MFCUK, Crapto1, etc.)

yes

Go to forum: MFOC, MFCUK, Crapto1, etc.

10 Reply by 0blar

(64 replies, posted in MFOC, MFCUK, Crapto1, etc.)

Any help ?

Go to forum: MFOC, MFCUK, Crapto1, etc.

11 Reply by 0blar

(64 replies, posted in MFOC, MFCUK, Crapto1, etc.)

Thanks for your reply

I saw the use of mfoc when I did mfoc -h
What I mean by documentation is how to get one key of a mifare card when I don't know it ?
I have a mifare card whitch is use for making photocopy but don't know the key used, my question is what is the procedure to get it ?

This is the result when I use mfoc -O test command with a blank card

Sector 00 -  UNKNOWN_KEY [A]  Sector 00 -  UNKNOWN_KEY (B)
.....
Sector 15 -  UNKNOWN_KEY [A]  Sector 15 -  UNKNOWN_KEY (B)

No sector encrypted with the default key has been found, exiting.


But when I use the mifare card for photocopy, I get
.....
.....
Sector 00 -  FOUND_KEY   [A]  Sector 00 -  UNKNOWN_KEY (B)
.....
Sector 15 -  UNKNOWN_KEY [A]  Sector 15 -  UNKNOWN_KEY (B)

Using sector 00 as an exploit sector
.....
....
TX: ff  00  00  00  04  d4  06  63  05
..... 
TX: ff  00  00  00  04  d4  4a  01  00

!Error: tag has been removed

Any idea on what happen (The tag is on the top of the reader )

Regards

Go to forum: MFOC, MFCUK, Crapto1, etc.

12 Reply by 0blar

(64 replies, posted in MFOC, MFCUK, Crapto1, etc.)

Thanks for your reply
I did ./autogen.sh --with-libnfc=/usr and ./configure --prefix=/usr --with-libnfc=/usr and mfoc compile OK (good work !)

Do you have any documentation on how to use mfoc ?

Regards

Go to forum: MFOC, MFCUK, Crapto1, etc.

13 Reply by 0blar

(64 replies, posted in MFOC, MFCUK, Crapto1, etc.)

Hello
With debian, libnfc r318 I try to compile mfoc-new.tar but I get Error! You need to have libnfc >= 1.2.1.

Go to forum: MFOC, MFCUK, Crapto1, etc.

14 Reply by 0blar

(22 replies, posted in NXP MIFARE Classic)

Following the instruction on the libfreefare website (thanks again)

1. Downloaded the code
2. autoreconf -vis
3. ./configure
4. make
5. sudo make install

Go to forum: NXP MIFARE Classic

15 Reply by 0blar

(2 replies, posted in Problems, Bugs and Fixes)

Thanks, now it is more clear

Go to forum: Problems, Bugs and Fixes

16 Topic by 0blar

(2 replies, posted in Problems, Bugs and Fixes)

Hi guys

Using libnfc (r317) on debian witout trouble, I wish to use libfreefare
I downloaded libfreefare r184 but I don't know how to compil it because I don't find any configure file on the folder

Can someone explain me how to compil and use it

Regards

Go to forum: Problems, Bugs and Fixes

17 Reply by 0blar

(30 replies, posted in NXP MIFARE Classic)

Dear

Thanks, I just compiled it and it works on Debian (vmware)

Regards

Go to forum: NXP MIFARE Classic

18 Reply by 0blar

(30 replies, posted in NXP MIFARE Classic)

Dear,

Is it possible to upload the latest source code (0.1.1) for linux

Regards

Go to forum: NXP MIFARE Classic

19 Reply by 0blar

(3 replies, posted in Problems, Bugs and Fixes)

Hello

Thanks for your response

I checked whith the older version of libnfc, and I confirm, I have to put a tag on the reader to be able to succed with the nfc-list command

Thanks again

Go to forum: Problems, Bugs and Fixes

20 Reply by 0blar

(3 replies, posted in Problems, Bugs and Fixes)

Any news ?

Go to forum: Problems, Bugs and Fixes

21 Topic by 0blar

(3 replies, posted in Problems, Bugs and Fixes)

Hello

following my problem on "Problems with new 1.3.0 release" topic, here is the result of the nfc-list command and debug mode enable

With the card on top of the reader:
localhost:~# nfc-list
nfc-list use libnfc 1.3.0 (r273)
DBG nfc.c:108: List avaible device using ACR122 driver
DBG acr122.c:157: PCSC reports following device(s):
DBG acr122.c:162: - ACS ACR122U 00 00 (pos=0)
DBG nfc.c:108: List avaible device using PN531_USB driver
DBG pn53x_usb.c:88: 0 busses
DBG pn53x_usb.c:90: 0 devices
DBG pn53x_usb.c:100: Checking device 04f2:b008 (04cc:0531)
DBG pn53x_usb.c:100: Checking device 04f2:b008 (054c:0193)
DBG pn53x_usb.c:100: Checking device 1d6b:0002 (04cc:0531)
DBG pn53x_usb.c:100: Checking device 1d6b:0002 (054c:0193)
DBG pn53x_usb.c:100: Checking device 072f:2200 (04cc:0531)
DBG pn53x_usb.c:100: Checking device 072f:2200 (054c:0193)
DBG pn53x_usb.c:100: Checking device 0e0f:0002 (04cc:0531)
DBG pn53x_usb.c:100: Checking device 0e0f:0002 (054c:0193)
DBG pn53x_usb.c:100: Checking device 1d6b:0001 (04cc:0531)
DBG pn53x_usb.c:100: Checking device 1d6b:0001 (054c:0193)
DBG pn53x_usb.c:145: Found 0 devices
DBG nfc.c:108: List avaible device using PN533_USB driver
DBG pn53x_usb.c:88: 0 busses
DBG pn53x_usb.c:90: 0 devices
DBG pn53x_usb.c:100: Checking device 04f2:b008 (04cc:2533)
DBG pn53x_usb.c:100: Checking device 04f2:b008 (04e6:5591)
DBG pn53x_usb.c:100: Checking device 1d6b:0002 (04cc:2533)
DBG pn53x_usb.c:100: Checking device 1d6b:0002 (04e6:5591)
DBG pn53x_usb.c:100: Checking device 072f:2200 (04cc:2533)
DBG pn53x_usb.c:100: Checking device 072f:2200 (04e6:5591)
DBG pn53x_usb.c:100: Checking device 0e0f:0002 (04cc:2533)
DBG pn53x_usb.c:100: Checking device 0e0f:0002 (04e6:5591)
DBG pn53x_usb.c:100: Checking device 1d6b:0001 (04cc:2533)
DBG pn53x_usb.c:100: Checking device 1d6b:0001 (04e6:5591)
DBG pn53x_usb.c:145: Found 0 devices
DBG nfc.c:108: List avaible device using PN532_UART driver
DBG pn532_uart.c:108: Trying to find PN532 device on serial port: /dev/ttyUSB0 at 115200 bauds.
DBG pn532_uart.c:128: Invalid serial port: /dev/ttyUSB0
DBG pn532_uart.c:108: Trying to find PN532 device on serial port: /dev/ttyUSB1 at 115200 bauds.
DBG pn532_uart.c:128: Invalid serial port: /dev/ttyUSB1
DBG pn532_uart.c:108: Trying to find PN532 device on serial port: /dev/ttyUSB2 at 115200 bauds.
DBG pn532_uart.c:128: Invalid serial port: /dev/ttyUSB2
DBG pn532_uart.c:108: Trying to find PN532 device on serial port: /dev/ttyUSB3 at 115200 bauds.
DBG pn532_uart.c:128: Invalid serial port: /dev/ttyUSB3
DBG pn532_uart.c:108: Trying to find PN532 device on serial port: /dev/ttyUSB4 at 115200 bauds.
DBG pn532_uart.c:128: Invalid serial port: /dev/ttyUSB4
DBG pn532_uart.c:108: Trying to find PN532 device on serial port: /dev/ttyUSB5 at 115200 bauds.
DBG pn532_uart.c:128: Invalid serial port: /dev/ttyUSB5
DBG pn532_uart.c:108: Trying to find PN532 device on serial port: /dev/ttyUSB6 at 115200 bauds.
DBG pn532_uart.c:128: Invalid serial port: /dev/ttyUSB6
DBG pn532_uart.c:108: Trying to find PN532 device on serial port: /dev/ttyUSB7 at 115200 bauds.
DBG pn532_uart.c:128: Invalid serial port: /dev/ttyUSB7
DBG pn532_uart.c:108: Trying to find PN532 device on serial port: /dev/ttyUSB8 at 115200 bauds.
DBG pn532_uart.c:128: Invalid serial port: /dev/ttyUSB8
DBG pn532_uart.c:108: Trying to find PN532 device on serial port: /dev/ttyUSB9 at 115200 bauds.
DBG pn532_uart.c:128: Invalid serial port: /dev/ttyUSB9
DBG pn532_uart.c:108: Trying to find PN532 device on serial port: /dev/ttyUSB10 at 115200 bauds.
DBG pn532_uart.c:128: Invalid serial port: /dev/ttyUSB10
DBG pn532_uart.c:108: Trying to find PN532 device on serial port: /dev/ttyUSB11 at 115200 bauds.
DBG pn532_uart.c:128: Invalid serial port: /dev/ttyUSB11
DBG pn532_uart.c:108: Trying to find PN532 device on serial port: /dev/ttyUSB12 at 115200 bauds.
DBG pn532_uart.c:128: Invalid serial port: /dev/ttyUSB12
DBG pn532_uart.c:108: Trying to find PN532 device on serial port: /dev/ttyUSB13 at 115200 bauds.
DBG pn532_uart.c:128: Invalid serial port: /dev/ttyUSB13
DBG pn532_uart.c:108: Trying to find PN532 device on serial port: /dev/ttyUSB14 at 115200 bauds.
DBG pn532_uart.c:128: Invalid serial port: /dev/ttyUSB14
DBG pn532_uart.c:108: Trying to find PN532 device on serial port: /dev/ttyUSB15 at 115200 bauds.
DBG pn532_uart.c:128: Invalid serial port: /dev/ttyUSB15
DBG nfc.c:117: No listing function avaible for ARYGON driver
DBG nfc.c:169: Looking for ACR122, found ACR122... Use it.
DBG acr122.c:203: Connecting to ACS ACR122U 00 00
DBG nfc.c:177: [ACS ACR122U 00 00 / ACR122U203] has been claimed.
TX: ff  00  00  00  02  d4  02 
RX: d5  03  32  01  04  07  90  00 
TX: ff  00  00  00  04  d4  06  63  3d 
RX: d5  07  00  90  00 
TX: ff  00  00  00  05  d4  08  63  3d  00 
RX: d5  09  90  00 
TX: ff  00  00  00  04  d4  06  63  02 
RX: d5  07  80  90  00 
TX: ff  00  00  00  05  d4  08  63  02  80 
RX: d5  09  90  00 
TX: ff  00  00  00  04  d4  06  63  03 
RX: d5  07  80  90  00 
TX: ff  00  00  00  05  d4  08  63  03  80 
RX: d5  09  90  00 
TX: ff  00  00  00  04  d4  06  63  0d 
RX: d5  07  20  90  00 
TX: ff  00  00  00  05  d4  08  63  0d  20 
RX: d5  09  90  00 
TX: ff  00  00  00  04  d4  06  63  38 
RX: d5  07  01  90  00 
TX: ff  00  00  00  05  d4  08  63  38  01 
RX: d5  09  90  00 
TX: ff  00  00  00  04  d4  06  63  05 
RX: d5  07  47  90  00 
TX: ff  00  00  00  05  d4  08  63  05  47 
RX: d5  09  90  00 
TX: ff  00  00  00  04  d4  06  63  3c 
RX: d5  07  10  90  00 
TX: ff  00  00  00  05  d4  08  63  3c  10 
RX: d5  09  90  00 
TX: ff  00  00  00  04  d4  32  01  00 
RX: d5  33  90  00 
TX: ff  00  00  00  06  d4  32  05  00  00  00 
RX: d5  33  90  00 
TX: ff  00  00  00  04  d4  06  63  02 
RX: d5  07  80  90  00 
TX: ff  00  00  00  05  d4  08  63  02  80 
RX: d5  09  90  00 
TX: ff  00  00  00  04  d4  06  63  03 
RX: d5  07  80  90  00 
TX: ff  00  00  00  05  d4  08  63  03  80 
RX: d5  09  90  00 
TX: ff  00  00  00  04  d4  06  63  0d 
RX: d5  07  20  90  00 
TX: ff  00  00  00  05  d4  08  63  0d  20 
RX: d5  09  90  00 
TX: ff  00  00  00  04  d4  32  01  01 
RX: d5  33  90  00 

Connected to NFC reader: ACS ACR122U 00 00 / ACR122U203 - PN532 v1.4 (0x07)

TX: ff  00  00  00  04  d4  4a  01  00 
RX: d5  4b  01  01  00  04  08  04  fc  4f  c3  9b  90  00 
The following (NFC) ISO14443A tag was found:

    ATQA (SENS_RES): 00  04 
       UID (NFCID1): fc  4f  c3  9b 
      SAK (SEL_RES): 08 
TX: ff  00  00  00  09  d4  4a  01  01  00  ff  ff  00  00 
RX: d5  4b  00  90  00 
TX: ff  00  00  00  09  d4  4a  01  02  00  ff  ff  00  00 
RX: d5  4b  00  90  00 
TX: ff  00  00  00  05  d4  4a  01  03  00 
RX: d5  4b  00  90  00 
TX: ff  00  00  00  04  d4  4a  01  04 
RX: d5  4b  00  90  00 
TX: ff  00  00  00  03  d4  44  00 
RX: d5  45  00  90  00 
TX: ff  00  00  00  04  d4  32  01  00 
RX: d5  33  90  00


Without the card on top of the reader:
localhost:~# nfc-list
nfc-list use libnfc 1.3.0 (r273)
DBG nfc.c:108: List avaible device using ACR122 driver
DBG acr122.c:157: PCSC reports following device(s):
DBG acr122.c:162: - ACS ACR122U 00 00 (pos=0)
DBG nfc.c:108: List avaible device using PN531_USB driver
DBG pn53x_usb.c:88: 0 busses
DBG pn53x_usb.c:90: 0 devices
DBG pn53x_usb.c:100: Checking device 04f2:b008 (04cc:0531)
DBG pn53x_usb.c:100: Checking device 04f2:b008 (054c:0193)
DBG pn53x_usb.c:100: Checking device 1d6b:0002 (04cc:0531)
DBG pn53x_usb.c:100: Checking device 1d6b:0002 (054c:0193)
DBG pn53x_usb.c:100: Checking device 072f:2200 (04cc:0531)
DBG pn53x_usb.c:100: Checking device 072f:2200 (054c:0193)
DBG pn53x_usb.c:100: Checking device 0e0f:0002 (04cc:0531)
DBG pn53x_usb.c:100: Checking device 0e0f:0002 (054c:0193)
DBG pn53x_usb.c:100: Checking device 1d6b:0001 (04cc:0531)
DBG pn53x_usb.c:100: Checking device 1d6b:0001 (054c:0193)
DBG pn53x_usb.c:145: Found 0 devices
DBG nfc.c:108: List avaible device using PN533_USB driver
DBG pn53x_usb.c:88: 0 busses
DBG pn53x_usb.c:90: 0 devices
DBG pn53x_usb.c:100: Checking device 04f2:b008 (04cc:2533)
DBG pn53x_usb.c:100: Checking device 04f2:b008 (04e6:5591)
DBG pn53x_usb.c:100: Checking device 1d6b:0002 (04cc:2533)
DBG pn53x_usb.c:100: Checking device 1d6b:0002 (04e6:5591)
DBG pn53x_usb.c:100: Checking device 072f:2200 (04cc:2533)
DBG pn53x_usb.c:100: Checking device 072f:2200 (04e6:5591)
DBG pn53x_usb.c:100: Checking device 0e0f:0002 (04cc:2533)
DBG pn53x_usb.c:100: Checking device 0e0f:0002 (04e6:5591)
DBG pn53x_usb.c:100: Checking device 1d6b:0001 (04cc:2533)
DBG pn53x_usb.c:100: Checking device 1d6b:0001 (04e6:5591)
DBG pn53x_usb.c:145: Found 0 devices
DBG nfc.c:108: List avaible device using PN532_UART driver
DBG pn532_uart.c:108: Trying to find PN532 device on serial port: /dev/ttyUSB0 at 115200 bauds.
DBG pn532_uart.c:128: Invalid serial port: /dev/ttyUSB0
DBG pn532_uart.c:108: Trying to find PN532 device on serial port: /dev/ttyUSB1 at 115200 bauds.
DBG pn532_uart.c:128: Invalid serial port: /dev/ttyUSB1
DBG pn532_uart.c:108: Trying to find PN532 device on serial port: /dev/ttyUSB2 at 115200 bauds.
DBG pn532_uart.c:128: Invalid serial port: /dev/ttyUSB2
DBG pn532_uart.c:108: Trying to find PN532 device on serial port: /dev/ttyUSB3 at 115200 bauds.
DBG pn532_uart.c:128: Invalid serial port: /dev/ttyUSB3
DBG pn532_uart.c:108: Trying to find PN532 device on serial port: /dev/ttyUSB4 at 115200 bauds.
DBG pn532_uart.c:128: Invalid serial port: /dev/ttyUSB4
DBG pn532_uart.c:108: Trying to find PN532 device on serial port: /dev/ttyUSB5 at 115200 bauds.
DBG pn532_uart.c:128: Invalid serial port: /dev/ttyUSB5
DBG pn532_uart.c:108: Trying to find PN532 device on serial port: /dev/ttyUSB6 at 115200 bauds.
DBG pn532_uart.c:128: Invalid serial port: /dev/ttyUSB6
DBG pn532_uart.c:108: Trying to find PN532 device on serial port: /dev/ttyUSB7 at 115200 bauds.
DBG pn532_uart.c:128: Invalid serial port: /dev/ttyUSB7
DBG pn532_uart.c:108: Trying to find PN532 device on serial port: /dev/ttyUSB8 at 115200 bauds.
DBG pn532_uart.c:128: Invalid serial port: /dev/ttyUSB8
DBG pn532_uart.c:108: Trying to find PN532 device on serial port: /dev/ttyUSB9 at 115200 bauds.
DBG pn532_uart.c:128: Invalid serial port: /dev/ttyUSB9
DBG pn532_uart.c:108: Trying to find PN532 device on serial port: /dev/ttyUSB10 at 115200 bauds.
DBG pn532_uart.c:128: Invalid serial port: /dev/ttyUSB10
DBG pn532_uart.c:108: Trying to find PN532 device on serial port: /dev/ttyUSB11 at 115200 bauds.
DBG pn532_uart.c:128: Invalid serial port: /dev/ttyUSB11
DBG pn532_uart.c:108: Trying to find PN532 device on serial port: /dev/ttyUSB12 at 115200 bauds.
DBG pn532_uart.c:128: Invalid serial port: /dev/ttyUSB12
DBG pn532_uart.c:108: Trying to find PN532 device on serial port: /dev/ttyUSB13 at 115200 bauds.
DBG pn532_uart.c:128: Invalid serial port: /dev/ttyUSB13
DBG pn532_uart.c:108: Trying to find PN532 device on serial port: /dev/ttyUSB14 at 115200 bauds.
DBG pn532_uart.c:128: Invalid serial port: /dev/ttyUSB14
DBG pn532_uart.c:108: Trying to find PN532 device on serial port: /dev/ttyUSB15 at 115200 bauds.
DBG pn532_uart.c:128: Invalid serial port: /dev/ttyUSB15
DBG nfc.c:117: No listing function avaible for ARYGON driver
DBG nfc.c:169: Looking for ACR122, found ACR122... Use it.
DBG acr122.c:203: Connecting to ACS ACR122U 00 00
No ACR122 firmware received, Error: 80100016
DBG nfc.c:211: No device found using driver: ACR122
DBG nfc.c:166: Looking for ACR122, found PN531_USB... Skip it.
DBG nfc.c:166: Looking for ACR122, found PN533_USB... Skip it.
DBG nfc.c:166: Looking for ACR122, found PN532_UART... Skip it.
DBG nfc.c:166: Looking for ACR122, found ARYGON... Skip it.
ERROR: Unable to connect to NFC device.

Regards

Go to forum: Problems, Bugs and Fixes

22 Reply by 0blar

(12 replies, posted in Problems, Bugs and Fixes)

Hello

I'm also using the 1.3.0 version with debian (vmware)
Compilling is OK
When I use  nfc-list command with a card on top of the reader I get
localhost:/home/libnfc-1.3.0# nfc-list
nfc-list use libnfc 1.3.0 (r273)

Connected to NFC reader: ACS ACR122U 00 00 / ACR122U203 - PN532 v1.4 (0x07)

The following (NFC) ISO14443A tag was found:

    ATQA (SENS_RES): 00  04 
       UID (NFCID1): fc  4f  c3  9b 
      SAK (SEL_RES): 08 

But when I remove the card fron the reader I get :

localhost:/home/libnfc-1.3.0# nfc-list
nfc-list use libnfc 1.3.0 (r273)
ERROR: Unable to connect to NFC device.

It didn't happen with the r254

Regards

Go to forum: Problems, Bugs and Fixes

23 Reply by 0blar

(4 replies, posted in Problems, Bugs and Fixes)

Thanks Romain

I will try to modify the necessary files as you said , and thanks again for replying me in the other post

Regards

Go to forum: Problems, Bugs and Fixes

24 Reply by 0blar

(4 replies, posted in Problems, Bugs and Fixes)

Hello

Sorry for asking but I"m not a developper

What kind of modification do we need to make mfoc and tk-libnfc compatible with the last libnfc API ?

Regards

Go to forum: Problems, Bugs and Fixes

25 Reply by 0blar

(6 replies, posted in Problems, Bugs and Fixes)

Hello
No
Where can I find the documentation to make this compatible with the latest libnfc ?
Can you expain me how to do this ?

Regards

Go to forum: Problems, Bugs and Fixes