Topic: mfoc error: nfc_initiator_transceive_bytes: Invalid Parameter

I'm trying to get mfoc working on a MIFARE Classic card. I'm using the latest stable libnfc and nfc-tools with a touchatag on Fedora 13.

mfoc first says "Auth with all sectors succeeded, dumping keys to a file!" and then starts printing out keys. However, there are about 5 lines throughout that say "nfc_initiator_transceive_bytes: Invalid Parameter". Any ideas what this means, or how to fix? Also, I couldn't find any docs on how to use the tolerance switch. I changed the values, but it doesn't seem to do anything.

Edit: I'm also getting this same error using micmd, so I suspect it's a problem with libnfc 1.3.9 and maybe the touchatag.

Last edited by timmerk (2010-10-17 04:55:22)

Re: mfoc error: nfc_initiator_transceive_bytes: Invalid Parameter

Hey,

timmerk wrote:

mfoc first says "Auth with all sectors succeeded, dumping keys to a file!" and then starts printing out keys. However, there are about 5 lines throughout that say "nfc_initiator_transceive_bytes: Invalid Parameter".

This is an error that comes from internal NFC chip (PN53x).

timmerk wrote:

Any ideas what this means

It does mean that nfc_initiator_transceive_bytes() have provided Invalid parameter (range, format, …) to PN53x.

timmerk wrote:

, or how to fix?

Switch in libnfc in debug mode, look at the trace and attempt to extract which command sent to the pn53x return an error.
Note: it's difficult to do that without PN53x documentation...

timmerk wrote:

Edit: I'm also getting this same error using micmd, so I suspect it's a problem with libnfc 1.3.9 and maybe the touchatag.

IMHO, it's not a libnfc 1.3.9's problem: before 1.3.9 all works same way except the error wasn't catched and wasn't showed up. So, if there is a libnfc's problem, it's quite older smile

Romuald Conty

Re: mfoc error: nfc_initiator_transceive_bytes: Invalid Parameter

Please see http://code.google.com/p/libnfc/issues/detail?id=132 for more information.

Romuald Conty