Google Code Exporter

``` - CRC and parity disabling capability - Manual-made anticol / raw bits sending capability - Timed functions available ``` Original comment by `[email protected]` on 12 Jul 2011 at 7:52

``` - bugs (e.g. for PN531 using InDataExchange with ISO14443-4 card “If parameter P3 (from C-APDU in DataOut[]) is greater than 0xFA (250 bytes), the C-APDU command is not sent...

Original comment by `[email protected]` on 4 Feb 2011 at 5:34 - Changed title: **Drivers could be loaded as plugins** - Changed state: **Feedback**

``` We maybe could use the new HAL architecture to wrote a driver which do one (or more) .so load. ``` Original comment by `[email protected]` on 6 Mar 2011 at...

``` Please provide a trace of the execution with: LIBNFC_LOG_LEVEL=3 mifare_classic_authenticate I don't have such card so I cannot test myself. ``` Original comment by `[email protected]` on 20 Dec 2013...

``` debug libnfc.chip.pn53x InDataExchange debug libnfc.chip.pn53x No timeout debug libnfc.driver.acr122_usb TX: 6f 14 00 00 00 00 00 00 00 00 ff 00 00 00 0f d4 40 01 60...

``` For regular Mifare Classic card it's a little bit different: debug libnfc.chip.pn53x InDataExchange debug libnfc.chip.pn53x No timeout debug libnfc.driver.acr122_usb TX: 6f 14 00 00 00 00 00 00 00...

``` Ok I figured out that this issue is a duplicate of https://code.google.com/p/libnfc/issues/detail?id=229 I added: nfc_set_property_bool(pnd, NP_AUTO_ISO14443_4, false) before calling mifare_classic_connect and it fixed my problem ``` Original comment by...

``` As mifare_classic_connect() implies connecting to MIFARE Classic, which is not a ISO14443-4 card, we maybe could disable NP_AUTO_ISO14443_4 feature in libfreefare ? Note: we will need to re-enable it...

``` This makes sense to me, yes. Note that at the moment current examples mifare-classic-format etc are also buggy. ``` Original comment by `[email protected]` on 20 Dec 2013 at 11:31