Are there any UK based NFC developers interested in a Meet Up? I have started a group on Meet Ups over here: http://www.meetup.com/NFC-London

and it'd be really cool to talk about NFC with you in person!

Cheers!
Will

I've just registered here to tell you about some discovery. Me and my friend were stuck for like 3 hours digging what is wrong.
For support of ACS ACR122S (firmware 1.4) we downloaded latest svn commit r1314. When trying nfc-list we've seen that device returning not all characters, just pseudo apdu for SUCCESS "02 00 00 03". While sending manually command over serial was returning complete one with firmware bytes, as it was specified.
So here's the faii:

Index: libnfc/drivers/acr122s.c
===================================================================
--- libnfc/drivers/acr122s.c    (wersja 1314)
+++ libnfc/drivers/acr122s.c    (kopia robocza)
@@ -251,9 +251,9 @@
 acr122s_recv_frame(nfc_device *pnd, uint8_t *frame, size_t frame_size, void *abort_p, int timeout)
 {
   if (frame_size < 13)
-    pnd->last_error = NFC_EINVARG;
+  {  pnd->last_error = NFC_EINVARG;
     return pnd->last_error;
-
+    }
   int ret;
   serial_port port = DRIVER_DATA(pnd)->port;

Someone forgot the bloody brackets! :-D But that's not all. The leftover was a strange situation that we've seen about the command returned showing the success bytes result for pn53x_init, but it was claiming as fail.
Success was 0, so making negation of 0 gives 1, so True.

@@ -621,7 +621,7 @@
   }
 #endif
 
-  if (!pn53x_init(pnd)) {
+  if (pn53x_init(pnd)) {
     log_put(LOG_CATEGORY, NFC_PRIORITY_ERROR, "%s", "Failed initializing PN532 chip.");
     acr122s_close(pnd);
     return NULL;

After all that I was surprised, because with the lib mfoc was able to recover all keys. Unlike my previous trial with ACR122U (firmware 1.6) with Input/Output error while exploting, but I think it still might be fixed :-)

We would like to inform you about our site where you can buy preprogrammed NFC tags http://www.nfctagwriter.com
This might come in handy for some of you.
Also we offer smaller amounts of (unwritten) tags for good prices, please send us an email if interested in that: info@nfctagwriter.com

best regards,

Bart

The TRF7970A uses either an SPI or parallel interface.

Gus S. Calabrese
99guspuppet

Working on Win XP SP3 and MacOSX:

Getting the revision R62, executing the win 32 binary from old-bin directory, works fine.
Compiling mfcuk using libnfc-1.5.1 dones not get any keys, on Win32 and MacOSX.

Anyone share the same experience ?

Regards,

We're a group of engineering students working on an NFC graduation project. We've been working with the SCM SCL3711 device, and trying to communicate with a Galaxy Nexus running Android 4.0. We've been using both libnfc, libnfc-llcp and tried nfcpy. So far, we haven't been able to exchange NDEF messages between the two devices.

We really want to use libnfc and libnfc-llcp to transfer short messages between two devices.
So far we have installed the AndroidBeam sample program on the phone, which pushes NDEF messages to any nearby Beam-compatible (LLCP?) devices, and tried to run the sample "nexus-get-tag" example program in the libnfc-llcp bundle.

Both devices recognize each other as LLCP devices which is encouraging, but there is no transfer of data.
The following is the LLCP log (running nexus-get-tag):

Connecting to NFC device
Found device
[stdout] TRACE    libnfc-llcp.llc.link - service 0x8396d08 bound to SAP 1
Allocated link structure
Created NPP service
Set link properties
[stdout] TRACE    libnfc-llcp.llc.link - service 0x8396ed0 bound to SAP 16
Bound link and service
Created mac link
Activated mac link as target
[stdout] INFO     libnfc-llcp.mac.link - (SCM Micro / SCL3711-NFC&RW - PN533 v2.7 (0x07)) Attempting to activate LLCP Link as target (blocking)
[stdout] INFO     libnfc-llcp.mac.link - (SCM Micro / SCL3711-NFC&RW - PN533 v2.7 (0x07)) LLCP Link activated (target)
[stdout] TRACE    libnfc-llcp.llc.link - llc_link_configure (0x839ad58, 0xbfa9a925, 10)
[stdout] DEBUG    libnfc-llcp.llc.link - Version: 1.0 (remote)
[stdout] DEBUG    libnfc-llcp.llc.link - Version: 1.0 (agreed)
[stdout] DEBUG    libnfc-llcp.llc.link - WKS: 0x0001
[stdout] DEBUG    libnfc-llcp.llc.link - LTO: 1500 ms (0x96)
[stdout] DEBUG    libnfc-llcp.llc.link - mq_open (/libnfc-llcp-28044-0x839ad58-up)
[stdout] DEBUG    libnfc-llcp.llc.link - mq_open (/libnfc-llcp-28044-0x839ad58-down)
[stdout] INFO     libnfc-llcp.llc.link - LLC Link started successfully
[stdout] INFO     libnfc-llcp.llc.llc - (0xb775db70) Link activated
[stdout] TRACE    libnfc-llcp.llc.llc - (0xb775db70) mq_receive+
[stdout] TRACE    libnfc-llcp.mac.link - Received 2 bytes
[stdout] TRACE    libnfc-llcp.mac.link - Received 2 bytes
[stdout] TRACE    libnfc-llcp.mac.link - Sending 2 bytes
[stdout] TRACE    libnfc-llcp.mac.link - Sending 2 bytes
[stdout] TRACE    libnfc-llcp.llc.llc - (0xb775db70) Received 2 bytes
[stdout] TRACE    libnfc-llcp.llc.llc - (0xb775db70) Symmetry PDU
[stdout] TRACE    libnfc-llcp.llc.llc - (0xb775db70) mq_send+
[stdout] TRACE    libnfc-llcp.llc.llc - (0xb775db70) Nothing to send
[stdout] TRACE    libnfc-llcp.llc.llc - (0xb775db70) mq_receive+
[stdout] FATAL    libnfc-llcp.mac.link - MAC Level error on PDU reception
[stdout] WARN     libnfc-llcp.mac.link - pdu_receive returned -1
[stdout] ERROR    libnfc-llcp.mac.link - NFC error: Target Released
[stdout] TRACE    libnfc-llcp.mac.link - Waiting for MAC Link PDU exchange thread to exit
[stdout] TRACE    libnfc-llcp.mac.link - MAC Link exchange PDU exchange thread terminated (returned 0)
[stdout] INFO     libnfc-llcp.llc.link - Freeing service 16
[stdout] INFO     libnfc-llcp.llc.link - Freeing service 1

Especially the following line concerns us:

[stdout] FATAL    libnfc-llcp.mac.link - MAC Level error on PDU reception

The way we know it's not working, is that it's supposed to write the NDEF message to a file, which it isn't.

I realize this seems to be more of a question to libnfc-llcp than libnfc, but this seems the best place to ask. Does anyone have any experience with this setup, or have an idea what could be wrong? This problem has been hassling us for months, and is quite critical in our project.

Thanks for your time!

the PN533 user manual (PN533 User Manual UM0801-03) can be downloaded now without password from the NXP website:

http://www.nxp.com/#/pip/pip=[pip=158231,jp=DesignSupport]|pp=[t=pip,i=158231]

This document describes the firmware V2.7 embedded in the PN533

Cheers and have fun,
Fozzybear

I am using Mifare classic 1K card in one of my RFID based project for college.
I want to store register number of the student in the tag , so that the reader should read this number for authentication & link to his database in back-end PC .

I tried to change the ID of the Tag its not possible to change . reader will always reads the deafault ID (58C4E09C) .

How can I store the data in the  tag so that the reader  will read at the data ( register number )whatever i stored during authentication time.

Please help...
Regards,
Girish Kuamr

Secondly, if thats the case, does anyone know if emulation could occur through a serial interfaced to an NFC chipset instead?

Also, a side question, does anyone know somewhere that sells PN53x chips in realtively low quanities? DigiKey seems to only sell them in the hundreds, so not really very helpful for this kind of thing.

Thanks to any and al replies

Any pointers on troubleshooting from here?

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?

I don't know if it's the good place to ask these questions but I'll try anyway

I am trying to implement a P2P communication between two Android phones (one of them will be replaced by an independent device in the end). I have seen that Android 4 supports SNEP which is published by the NFC forum and should be available on non-android devices.

I have following the Google tutorial for NFC P2P (http://developer.android.com/guide/topi … c.html#p2p) and I can send some information from one phone to the other, but I have a few questions:

1. Android Beam is just a name for NFC or it is an Android protocol working over SNEP/NPP ? If it's a protocol, how to do NFC P2P without Beam ?
2. How to set the use of SNEP ?
3. How to send a response to the other device when the connection is initialized (first message received) ?

Thank you for your help !!!

1. I have just purchased a Sony RC-S370 as I saw RC-S360 seems to be supported by libnfc.
I can tell from the material that you need a PN53x chip on the card reader so as to be supported,
but cannot find webpages that claim the existence of such chips in RC-S370 except for some
Japanese developer's blog.
wonder if Sony ever reveal it, or anyone know if RC-S370 is supported. Thank you.

2. my second question is that I am reading through the example provided here:
http://www.libnfc.org/api/examples_page.html

I saw the definition of "nmMifare" and the usage of "if (nfc_initiator_select_passive_target (pnd, PM_ISO14443A_106, NULL, 0, &nti)) {"

from my shallow knowledge I find that the "PM_ISO14443A_106" is of "pn53x_modulation_t" type, while the
"bool nfc_initiator_select_passive_target" function require its second parameter to be "nfc_modulation_t" type.
anyone who actually run the program? I came through this when I was reading the beginner level material.
Thank you all!