I'm new to working with FeliCa, but I decided to purchase some tags (which I received today) from Japan, and begin researching this rather mysterious, obscure, and seemingly regionally-isolated technology - since I was getting bored with MiFare, and haven't much progress on interfacing with my Maxim ISO/IEC 14443-B sample cards.

I believe that FeliCa's anticollision mechanism is based upon a "timeslot" mechanism, and documented in various public PDFs.

With that mind, I've noticed that LibNFC and the ACS card readers (especially the ACR122U variants) will only report the NFCID2 of the first tag to respond to a poll at 212 kbps (regardless of how tags are stacked, or distance), when testing the nfc-list utility.

For example - with 2 tags on the reader, the following is reported:

tyson@UmBongo:~/nfc-tools-read-only/nfcd$ nfc-list -v
nfc-list uses libnfc 1.5.1 (r1236)
Connected to NFC device: ACS ACR122U 00 00 / ACR122U103 - PN532 v1.6 (0x07)
0 ISO14443A passive target(s) found.

1 Felica (212 kbps) passive target(s) found:
        ID (NFCID2): 01  27  00  5d  1a  05  88  cd  
    Parameter (PAD): 00  f0  00  00  02  06  03  00  
   System Code (SC): 88  b4  

1 Felica (424 kbps) passive target(s) found:
        ID (NFCID2): 01  27  00  5d  1a  05  88  cd  
    Parameter (PAD): 00  f0  00  00  02  06  03  00  
   System Code (SC): 88  b4  

With a single tag held above the reader, the following is reported:

tyson@UmBongo:~/nfc-tools-read-only/nfcd$ nfc-list -v
nfc-list uses libnfc 1.5.1 (r1236)
Connected to NFC device: ACS ACR122U 00 00 / ACR122U103 - PN532 v1.6 (0x07)
0 ISO14443A passive target(s) found.

0 Felica (212 kbps) passive target(s) found.

1 Felica (424 kbps) passive target(s) found:
        ID (NFCID2): 01  27  00  5d  1a  05  8a  cd  
    Parameter (PAD): 00  f0  00  00  02  06  03  00  
   System Code (SC): 88  b4  

Additionally, I've noticed that nfc-list will sometimes claim that no tags are present - when in fact, two FeliCa tags are; and sometimes, only the 212 kbps bitrate is reported for a tag. I've also been able to "drown out" FeliCa tags by stacking ISO/IEC 14443-A and 14443-B tags on top.

Out of curiosity - are these issues related to missing functionality, or bugs in LibNFC? Or are they related to limitations of the (implementation of the) chipset in this family of readers? If the former is true, are there any plans to implement support for this functionality? (Or is it just a case of "whoever's interested enough should implement it"?)

Thanks,

Tyson.

The web site says:
"To support the development of NFC Forum Type 3 Tag enabled products, Sony has initiated a campaign to distribute 100 sample kits upon request to interested companies free of charge. The sample kit campaign aims at providing interested parties with a set of NFC Forum Tag Type 3 compatible cards as well as an NFC USB external reader. Using this kit, developers will be able to test their devices with NFC Forum Type 3 Tag compatible cards, as well as to change the NDEF formatted content on those using the supplied NFC reader."

The sample kit includes an NFC reader, 10 FeliCa Lite and 10 FeliCa cards all NDEF formatted.

/Stephen

I have install libnfc in my PC.

I can use the sample "nfc-anticol" and PN532 board to test ISO14443A card. But can not find a sample for FeliCa card.

Could libnfc provide FeliCa example ?

My problem is that I cannot get the Felica RC-S965 to function as NFC Forum Type 3 tag. So far I've been able to encode the tag so that I'm able to select system code 12FCh after I changed the memory configuration code's system option from 00h to 01h (Block 88h, Byte 3). I wonder what should I do next to get the tag function as NFC Forum Type 3 tag with Nokia 6212 Classic for example? The tag isn't yet detected as NFC tag by the 6212. My goal would be to encode NDEF Message of type NFC Smart Poster on the tag.

Any help?