Philippe Teuwen

Testing `hf felica raw` I guess there are errors in your testing instructions, `hf felica raw 06 00 ff ff 00 00` needs `-c` and IDm is bytes 5-12. *...

May I suggest to add "sniffing" to the list of planned features? It can help debugging issues e.g. when comparing frames transmitted by libnfc or a phone to the ones...

ok I'll test. FTR RC-S888 and RC-S886 is what's engraved on the tags, RC-S962 and RC-S965 is how NXP TagInfo identifies them on my phone.

no much to see, timeout ``` #db# FeliCa_sendraw Enter #db# Start iso18092_setup #db# No card selection #db# Transmit Frame (no CRC shown): #db# b2 4d 06 00 ff ff 00...

sniff works but truncates tag response to first 16 bytes (and crc info is wrong if answer is longer)

ok it seems to be a modulation/antenna problem. With the original dual antenna on tags 3 and 4, even when I sniff my phone I typically only see the reader...

FYI apparently NXP TagInfo is polling FeliCa cards with the equivalent of these commands: ``` hf felica raw 08 00 ff ff 01 00 3a 10 -c hf felica raw...

As I sniffed the commands sent by NXP TagInfo and could replay them against the cards, I'm pretty sure it's not a logical problem of malformed frames.

maybe add an option to `felica raw` to automatically add the first length byte ? `hf felica raw 06 00 ff ff 00 00 -c` => `hf felica raw 00...

@7homasSutter the key argument in the example is 8 bytes and the command seems to accept only 8 and 12 bytes. How to provide 16 and 24 bytes 3DES keys...