<![CDATA[libnfc developers community — Questions and Requests]]> 2013-05-24T11:12:21Z PunBB http://www.libnfc.org/community/ <![CDATA[mingw32-make Error 2]]> Hello.

I'm trying to compile libnfc 1.7 for windows 7 and I've hit a snag after solving a couple of other problems. After configuring everything in cmake 2.8.11 I want to do a mingw32-make which produces the following error. I checked the code and it definitely IS declared. So every error in there is false but it won't ignore them. What to do?



C:\dev\libnfc-build>cmake-gui .

C:\dev\libnfc-build>cmake-gui .

C:\dev\libnfc-build>mingw32-make
Scanning dependencies of target nfc
[  1%] Building C object libnfc/CMakeFiles/nfc.dir/nfc.c.obj
[  3%] Building C object libnfc/CMakeFiles/nfc.dir/nfc-device.c.obj
[  5%] Building C object libnfc/CMakeFiles/nfc.dir/nfc-emulation.c.obj
[  7%] Building C object libnfc/CMakeFiles/nfc.dir/nfc-internal.c.obj
[  8%] Building C object libnfc/CMakeFiles/nfc.dir/conf.c.obj
[ 10%] Building C object libnfc/CMakeFiles/nfc.dir/iso14443-subr.c.obj
[ 12%] Building C object libnfc/CMakeFiles/nfc.dir/mirror-subr.c.obj
[ 14%] Building C object libnfc/CMakeFiles/nfc.dir/target-subr.c.obj
[ 15%] Building C object libnfc/CMakeFiles/nfc.dir/drivers/acr122_usb.c.obj
C:\dev\libnfc-read-only\libnfc\drivers\acr122_usb.c: In function 'acr122_usb_rec
eive':
C:\dev\libnfc-read-only\libnfc\drivers\acr122_usb.c:587:3: error: 'off_t' undecl
ared (first use in this function)
C:\dev\libnfc-read-only\libnfc\drivers\acr122_usb.c:587:3: note: each undeclared
 identifier is reported only once for each function it appears in
C:\dev\libnfc-read-only\libnfc\drivers\acr122_usb.c:587:9: error: expected ';' b
efore 'offset'
C:\dev\libnfc-read-only\libnfc\drivers\acr122_usb.c:630:20: error: 'offset' unde
clared (first use in this function)
libnfc\CMakeFiles\nfc.dir\build.make:249: recipe for target `libnfc/CMakeFiles/n
fc.dir/drivers/acr122_usb.c.obj' failed
mingw32-make[2]: *** [libnfc/CMakeFiles/nfc.dir/drivers/acr122_usb.c.obj] Error
1
CMakeFiles\Makefile2:79: recipe for target `libnfc/CMakeFiles/nfc.dir/all' faile
d
mingw32-make[1]: *** [libnfc/CMakeFiles/nfc.dir/all] Error 2
makefile:135: recipe for target `all' failed
mingw32-make: *** [all] Error 2

C:\dev\libnfc-build>
]]> http://www.libnfc.org/community/user/4348/ 2013-05-24T11:12:21Z http://www.libnfc.org/community/topic/990/mingw32make-error-2/new/posts/ <![CDATA[libllcp can't receive long data from phone]]> Hi,
my pn532 can only receive 42 bytes from phone by libllcp. I used libllcp/examples/npp-server/npp-server.c to receive data. How can I get more data from phone?

]]> http://www.libnfc.org/community/user/4141/ 2013-05-21T01:49:11Z http://www.libnfc.org/community/topic/988/libllcp-cant-receive-long-data-from-phone/new/posts/ <![CDATA[scl3711 anyone can help me]]> hello I do not get my reader scl3711 run in ubuntu, anyone can help me.
The project consists of an access control system with nfc reader, someone can tell me what language to use or devo do. I researched a lot but not as and where deveria start.
Thank you.

]]> http://www.libnfc.org/community/user/4286/ 2013-05-16T10:10:15Z http://www.libnfc.org/community/topic/987/scl3711-anyone-can-help-me/new/posts/ <![CDATA[How to receive the data by SNEP at ACR122.]]> I develop using Galaxy Nexus and ACR122.
I can't receive the data that the android terminal send in SNEP at ACR122.
Is there anyone knows how to do it?
Please show me.

Thank you,

]]> http://www.libnfc.org/community/user/4327/ 2013-05-13T20:35:58Z http://www.libnfc.org/community/topic/985/how-to-receive-the-data-by-snep-at-acr122/new/posts/ <![CDATA[Touch to Beam]]> The android terminal display the picture of "Touch to Beam",
when I send the data by SNEP at android terminal.
Can I prevent to display that picture?
Please show me how to do it.

Thank you,

]]> http://www.libnfc.org/community/user/4327/ 2013-05-13T20:30:39Z http://www.libnfc.org/community/topic/984/touch-to-beam/new/posts/ <![CDATA[activate the android terminal as card emulation mode]]> I develop using the android terminal.
Is there somthing method to activate the android terminal as card emulation mode?
I don't mind if there is no secure element.
Please show me how to activate it.

Thank you,

]]> http://www.libnfc.org/community/user/4327/ 2013-05-13T20:24:32Z http://www.libnfc.org/community/topic/983/activate-the-android-terminal-as-card-emulation-mode/new/posts/ <![CDATA[The connection of Android4.1 and ACR122]]> I develop using Galaxy Nexus and ACR122.
The version of Android is 4.1.
I have to connetct in LLCP, when I connect the android terminal and ACR122 in DEP.
I don't want to communicate with P2P mode.
Is there something method to communicate with the reader/writer mode in DEP?

My process is following.
-I connect ACR122 to the Windows PC by USB.
-I bump the android terminal to the ACR122.
-I execute TgInitAsTarget command of PN533 from the PC to ACR122.
I set DEP connection(0x40) in SEL_RES.
-Gi in ATR_REQ means LLCP connection in response of TgInitAsTarget.

Thank you,

]]> http://www.libnfc.org/community/user/4327/ 2013-05-13T20:18:49Z http://www.libnfc.org/community/topic/982/the-connection-of-android41-and-acr122/new/posts/ <![CDATA[pam-nfc segfaults (acr122U)]]> Hi

I'm trying to get ACR122U working on Ubuntu 12.04. I've installed libnfc-1.7.0-rc7 (also tested with libnfc-1.7.0-rc6 ) and pam_nfc-0.1.4 . Both installs go through fine and my nfc-list shows the device and tag:

$ sudo nfc-list
nfc-list uses libnfc 1.7.0-rc6
NFC device: ACS / ACR122U PICC Interface opened
1 ISO14443A passive target(s) found:
ISO/IEC 14443A (106 kbps) target:
    ATQA (SENS_RES): 00  04  
       UID (NFCID1): a6  14  34  fc  
      SAK (SEL_RES): 08

I should note here that running the command without sudo returns this:

nfc-list uses libnfc 1.7.0-rc6
error    libnfc.driver.acr122_usb    Unable to claim USB interface (Operation not permitted)
nfc-list: ERROR: Unable to open NFC device: acr122_usb:003:003

I've tried adding the nfc to blacklist in /etc/modprobe.d/, unfortunately without success.

If I try adding user to the tag 

sudo pam-nfc-add dejan

I get a segfault:

kernel: [ 2586.693391] pam-nfc-add[2640]: segfault at 0 ip 006e2848 sp bfbf6fa0 error 6 in libnfc.so.4.0.0[6df000+1b000]

Any suggestions? Is this procedure even correct for the acr122u? Thanks in advance for answers.

Best regards,

Dejan

]]> http://www.libnfc.org/community/user/4320/ 2013-05-09T13:06:01Z http://www.libnfc.org/community/topic/979/pamnfc-segfaults-acr122u/new/posts/ <![CDATA[Sending APDU's]]> Hi,

I'm trying to make a fuzzer for NFC (and libnfc in particular) using an Android device (with Cyanogenmod to be able to emulate tags). As far as I know at the moment, Android is only capable of using NFC using APDU's.

The PCD I'm using is a tikitag with firmware ACR122U1.

I've managed to communicate between the PCD and the 'tag' (thus, Android device) in Java using the smartcardio library on my PC (PCD-side). What I'm trying now is doing the same but with libnfc in C or C++. The problem is I don't know how to send APDU's (or something similar so the NFCAdapter in Android will pick up the frame) with libnfc.

The anti-collision in C works just fine, but when trying to send an InDataExchange, it stops and waits forever for a reply.

REQA          | 26
ATQA          | 04  00
SEL (all)     | 93  20
UID, BCC      | 08  b8  c3  15  66
SEL (tag)     | 93  70  08  b8  c3  15  66  1f  0f
SAK           | 60  f8  32
RATS          | e0  50
ATS           | 05  78  33  88  00  59  b2

A normal APDU for PCD to tag would be something like this:

0xFF, 0x00, 0x00, 0x00, 0x04, 0xD4, 0x40, 0x01, 0xBA

In this example, the first 4 bytes are a pseudo-APDU to make sure the APDU is sent directly to the tag. The next byte is the length of the APDU itself. The 0xD4 0x40 0x01 is the InDataExchange command, telling all following bytes are data to be exchanged with the tag.

Any help is appreciated.

]]> http://www.libnfc.org/community/user/4153/ 2013-05-06T12:59:56Z http://www.libnfc.org/community/topic/977/sending-apdus/new/posts/ <![CDATA[libllcp can't be used on Windows?]]> Libnfc can be installed on Windows, how about libllcp?
Thanks.

]]> http://www.libnfc.org/community/user/4141/ 2013-05-02T03:39:24Z http://www.libnfc.org/community/topic/971/libllcp-cant-be-used-on-windows/new/posts/ <![CDATA[Anti-collision doesn't work properly?]]> I have 2 tags,  nfc-list showed correctly when 1 tag was in field:

C:\libnfc-1.7.0-rc7\build\utils>nfc-list
nfc-list uses libnfc 1.7.0
NFC device: ACS ACR122 0 / ACR122U210 opened
1 ISO14443A passive target(s) found:
ISO/IEC 14443A (106 kbps) target:
    ATQA (SENS_RES): 00  44
       UID (NFCID1): 04  98  9b  8a  6b  2b  80
      SAK (SEL_RES): 00


But when I placed the other tag in field, the ATQA change:

C:\libnfc-1.7.0-rc7\build\utils>nfc-list
nfc-list uses libnfc 1.7.0
NFC device: ACS ACR122 0 / ACR122U210 opened
1 ISO14443A passive target(s) found:
ISO/IEC 14443A (106 kbps) target:
    ATQA (SENS_RES): 00  00
       UID (NFCID1): 04  98  9b  8a  6b  2b  80
      SAK (SEL_RES): 00

1 Jewel passive target(s) found:
Innovision Jewel (106 kbps) target:
    ATQA (SENS_RES): 0c  00
      4-LSB JEWELID: 5c  4e  a1  01

Is there anyone know what would cause this result? Thanks.
My OS is Windows XP sp3 32bit.

]]> http://www.libnfc.org/community/user/4297/ 2013-05-02T03:09:35Z http://www.libnfc.org/community/topic/970/anticollision-doesnt-work-properly/new/posts/ <![CDATA[Error compiling libnfc: linux/mod_devicetable.h: No such file]]> Hello,

I'm trying to compile libnfc-1.7.0-rc7 under debian and I got the following error:

$ make
make  all-recursive
make[1]: Entering directory `/home/user/src/libnfc-1.7.0-rc7'
Making all in libnfc
make[2]: Entering directory `/home/user/src/libnfc-1.7.0-rc7/libnfc'
Making all in chips
make[3]: Entering directory `/home/user/src/libnfc-1.7.0-rc7/libnfc/chips'
  CC     libnfcchips_la-pn53x.lo
  CCLD   libnfcchips.la
make[3]: Leaving directory `/home/user/src/libnfc-1.7.0-rc7/libnfc/chips'
Making all in buses
make[3]: Entering directory `/home/user/src/libnfc-1.7.0-rc7/libnfc/buses'
  CC     libnfcbuses_la-spi.lo
  CC     libnfcbuses_la-uart.lo
  CC     libnfcbuses_la-usbbus.lo
In file included from usbbus.h:37:0,
                 from usbbus.c:36:
/usr/local/include/usb.h:4:35: fatal error: linux/mod_devicetable.h: No such file or directory
compilation terminated.
make[3]: *** [libnfcbuses_la-usbbus.lo] Error 1
make[3]: Leaving directory `/home/user/src/libnfc-1.7.0-rc7/libnfc/buses'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/user/src/libnfc-1.7.0-rc7/libnfc'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/user/src/libnfc-1.7.0-rc7'
make: *** [all] Error 2

File mod_devicetable.h exists only in 

/usr/src/linux-headers-3.2.0-4-common/include/linux/

When I tried to include this directory using 

./configure CPPFLAGS=-I/usr/src/linux-headers-3.2.0-4-common/include/

I got the following:

$ make
make  all-recursive
make[1]: Entering directory `/home/user/src/libnfc-1.7.0-rc7'
Making all in libnfc
make[2]: Entering directory `/home/user/src/libnfc-1.7.0-rc7/libnfc'
Making all in chips
make[3]: Entering directory `/home/user/src/libnfc-1.7.0-rc7/libnfc/chips'
  CC     libnfcchips_la-pn53x.lo
  CCLD   libnfcchips.la
make[3]: Leaving directory `/home/user/src/libnfc-1.7.0-rc7/libnfc/chips'
Making all in buses
make[3]: Entering directory `/home/user/src/libnfc-1.7.0-rc7/libnfc/buses'
  CC     libnfcbuses_la-spi.lo
In file included from /usr/src/linux-headers-3.2.0-4-common/include/linux/spi/spidev.h:25:0,
                 from spi.h:42,
                 from spi.c:37:
/usr/src/linux-headers-3.2.0-4-common/include/linux/types.h:13:2: warning: #warning is a GCC extension [enabled by default]
/usr/src/linux-headers-3.2.0-4-common/include/linux/types.h:13:2: warning: #warning "Attempt to use kernel headers from user space, see kernelnewbies KernelHeaders" [-Wcpp]
In file included from /usr/src/linux-headers-3.2.0-4-common/include/linux/stddef.h:4:0,
                 from /usr/src/linux-headers-3.2.0-4-common/include/linux/posix_types.h:4,
                 from /usr/src/linux-headers-3.2.0-4-common/include/linux/types.h:17,
                 from /usr/src/linux-headers-3.2.0-4-common/include/linux/spi/spidev.h:25,
                 from spi.h:42,
                 from spi.c:37:
/usr/src/linux-headers-3.2.0-4-common/include/linux/compiler.h:35:32: warning: ISO C does not permit named variadic macros [-Wvariadic-macros]
  CC     libnfcbuses_la-uart.lo
  CC     libnfcbuses_la-usbbus.lo
In file included from /usr/local/include/usb.h:4:0,
                 from usbbus.h:37,
                 from usbbus.c:36:
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:18:2: error: unknown type name '__u32'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:19:2: error: unknown type name '__u32'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:20:2: error: unknown type name '__u32'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:21:2: error: unknown type name 'kernel_ulong_t'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:31:2: error: unknown type name '__u32'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:32:2: error: unknown type name '__u32'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:33:2: error: unknown type name '__u32'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:34:2: error: unknown type name '__u32'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:35:2: error: unknown type name '__u32'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:36:2: error: unknown type name 'kernel_ulong_t'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:37:33: error: 'kernel_ulong_t' undeclared here (not in a function)
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:37:3: error: requested alignment is not an integer constant
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:100:2: error: unknown type name '__u16'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:103:2: error: unknown type name '__u16'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:104:2: error: unknown type name '__u16'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:105:2: error: unknown type name '__u16'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:106:2: error: unknown type name '__u16'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:109:2: error: unknown type name '__u8'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:110:2: error: unknown type name '__u8'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:111:2: error: unknown type name '__u8'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:114:2: error: unknown type name '__u8'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:115:2: error: unknown type name '__u8'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:116:2: error: unknown type name '__u8'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:119:2: error: expected specifier-qualifier-list before 'kernel_ulong_t'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:137:2: error: unknown type name '__u16'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:138:2: error: unknown type name '__u16'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:139:2: error: unknown type name '__u32'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:140:2: error: unknown type name '__u32'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:141:2: error: expected specifier-qualifier-list before 'kernel_ulong_t'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:147:2: error: unknown type name '__u16'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:149:2: error: unknown type name '__u16'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:150:2: error: unknown type name '__u16'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:151:2: error: unknown type name '__u8'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:152:2: error: unknown type name '__u8'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:154:2: error: expected specifier-qualifier-list before 'kernel_ulong_t'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:164:2: error: unknown type name '__u16'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:165:2: error: unknown type name '__u8'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:166:2: error: unknown type name '__u8'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:167:2: error: unknown type name '__u32'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:168:2: error: expected specifier-qualifier-list before 'kernel_ulong_t'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:175:2: error: unknown type name '__u8'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:176:2: error: unknown type name '__u8'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:177:2: error: unknown type name '__u16'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:178:2: error: unknown type name '__u32'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:179:2: error: expected specifier-qualifier-list before 'kernel_ulong_t'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:186:2: error: unknown type name '__u8'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:187:2: error: expected specifier-qualifier-list before 'kernel_ulong_t'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:194:2: error: unknown type name '__u8'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:195:2: error: expected specifier-qualifier-list before 'kernel_ulong_t'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:199:2: error: unknown type name '__u8'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:200:2: error: expected specifier-qualifier-list before 'kernel_ulong_t'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:210:2: error: unknown type name '__u8'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:211:2: error: unknown type name '__u8'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:212:2: error: unknown type name '__u8'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:213:2: error: unknown type name '__u8'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:227:2: error: expected specifier-qualifier-list before 'kernel_ulong_t'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:240:2: error: unknown type name '__u16'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:242:2: error: unknown type name '__u16'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:243:2: error: unknown type name '__u16'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:245:2: error: unknown type name '__u8'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:248:2: error: unknown type name '__u8'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:251:2: error: unknown type name '__u8'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:253:2: error: unknown type name '__u32'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:254:33: error: '__u32' undeclared here (not in a function)
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:254:3: error: requested alignment is not an integer constant
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:260:2: error: expected specifier-qualifier-list before 'kernel_ulong_t'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:314:2: error: expected specifier-qualifier-list before 'kernel_ulong_t'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:341:2: error: expected specifier-qualifier-list before 'kernel_ulong_t'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:347:2: error: unknown type name '__u8'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:348:2: error: unknown type name '__u8'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:349:2: error: unknown type name '__u16'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:350:2: error: expected specifier-qualifier-list before '__u32'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:363:2: error: unknown type name '__u8'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:364:2: error: unknown type name '__u16'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:365:2: error: unknown type name '__u16'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:366:2: error: expected specifier-qualifier-list before 'kernel_ulong_t'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:372:2: error: unknown type name '__u16'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:373:2: error: unknown type name '__u16'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:374:2: error: unknown type name '__u8'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:387:2: error: unknown type name '__u16'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:388:2: error: unknown type name '__u16'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:389:2: error: unknown type name '__u8'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:390:2: error: unknown type name '__u8'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:403:2: error: expected specifier-qualifier-list before '__u32'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:412:2: error: unknown type name '__u8'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:413:2: error: expected specifier-qualifier-list before 'kernel_ulong_t'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:424:2: error: expected specifier-qualifier-list before 'kernel_ulong_t'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:435:2: error: expected specifier-qualifier-list before 'kernel_ulong_t'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:470:2: error: expected specifier-qualifier-list before 'kernel_ulong_t'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:499:2: error: expected specifier-qualifier-list before 'kernel_ulong_t'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:525:2: error: expected specifier-qualifier-list before '__u32'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:530:2: error: expected specifier-qualifier-list before '__u32'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:542:2: error: expected specifier-qualifier-list before 'kernel_ulong_t'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:551:2: error: unknown type name '__u16'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:552:2: error: unknown type name '__u16'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:553:2: error: unknown type name '__u16'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:554:2: error: unknown type name '__u16'
/usr/src/linux-headers-3.2.0-4-common/include/linux/mod_devicetable.h:555:2: error: expected specifier-qualifier-list before 'kernel_ulong_t'
In file included from /usr/src/linux-headers-3.2.0-4-common/include/linux/usb/ch9.h:36:0,
                 from /usr/local/include/usb.h:5,
                 from usbbus.h:37,
                 from usbbus.c:36:
/usr/src/linux-headers-3.2.0-4-common/include/linux/types.h:13:2: warning: #warning "Attempt to use kernel headers from user space, see kernelnewbies KernelHeaders" [-Wcpp]
usbbus.c: In function 'usb_prepare':
usbbus.c:49:3: warning: implicit declaration of function 'getenv' [-Wimplicit-function-declaration]
usbbus.c:49:25: warning: initialization makes pointer from integer without a cast [enabled by default]
usbbus.c:52:3: warning: implicit declaration of function 'atoi' [-Wimplicit-function-declaration]
usbbus.c:53:5: warning: implicit declaration of function 'setenv' [-Wimplicit-function-declaration]
usbbus.c:57:3: warning: implicit declaration of function 'usb_init' [-Wimplicit-function-declaration]
usbbus.c:64:3: warning: implicit declaration of function 'usb_find_busses' [-Wimplicit-function-declaration]
usbbus.c:71:3: warning: implicit declaration of function 'usb_find_devices' [-Wimplicit-function-declaration]
make[3]: *** [libnfcbuses_la-usbbus.lo] Error 1
make[3]: Leaving directory `/home/user/src/libnfc-1.7.0-rc7/libnfc/buses'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/user/src/libnfc-1.7.0-rc7/libnfc'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/user/src/libnfc-1.7.0-rc7'
make: *** [all] Error 2

Any clues how to resolve this issue? Thanks in advance

]]> http://www.libnfc.org/community/user/4293/ 2013-04-30T21:53:05Z http://www.libnfc.org/community/topic/969/error-compiling-libnfc-linuxmoddevicetableh-no-such-file/new/posts/ <![CDATA[student aid]]> hi i am student and I have a problem Spanish'm in the final project, and I have considered making a nfc access control.

I have scl3711 nfc reader, I have recommended to do so in php as it will aceder to a database with an interface in html or php. I can not find php library for nfc. By fovor someone can tell me that I have to install on ubuntu so you can operate the reader.

Thank you very much.

]]> http://www.libnfc.org/community/user/4286/ 2013-04-26T11:52:13Z http://www.libnfc.org/community/topic/966/student-aid/new/posts/ <![CDATA[Elecfreaks RFID/NFC Breakout Board + libnfc]]> Hello, everyone, I have the aforementioned Elecfreaks RFID/NFC Breakout Board and am trying to get it to work through libnfc for my project at my university. I have first experimented in Windows, but it turned out to be too difficult, so I moved on to a Vmware Workshop virtual Ubuntu 12.10 where I managed to "make" and install every necessary component and am now stuck at a similar situation like the sticky post above.

I am trying to connect to the Board through UART via a FTDI USB-to Serial modified to be USB-to UART TTL. I am connected with TX, RX, PWR and GND.

I still can't detect the device, both "nfc-list" and "nfc-scan-device -i -v" say "No NFC device found." I am using libnfc 1.7.0-rc5 as I had some difficulties with rc6 which remained unsolved. I installed libusb, made the fix of moving libnfc.conf to the devices.d directory, tried renaming the conf to pn532_uart.conf, modified its contents to:

#device.name = "Elecfreaks BB"
#device.connstring = "pn532_uart:=dev/ttyUSB0"

I tried switching around the TX-RX ports, trying different PCs, different USB ports but nothing helped. LIBNFC_LOG_LEVEL=3 nfc-list says:

debug libnfc.general log_level is set to 3
debug libnfc.general allow_autoscan is set to true
debug libnfc.general allow_instrusive_scan is set to false
debug libnfc.general 0 device(s) defined by user
nfc-list uses libnfc 1.7.0-rc5
no NFC device found.

Can someone please help me? I would very much appreciate it as my deadline approaches...

]]> http://www.libnfc.org/community/user/4227/ 2013-04-22T13:47:29Z http://www.libnfc.org/community/topic/961/elecfreaks-rfidnfc-breakout-board-libnfc/new/posts/ <![CDATA[Unable to open NFC device: pn532_uart:/dev/ttyAMA0 [update:now can!]]]> Hello everybody, I was falled into a error during running nfc-list. I have read topic "No NFC device found with libnfc-1.7.0-rc4 on raspberry pi" and do as washmachine and rconty said, but the problem was still here, may you can help me :)

My reader is ACR122U103 and the libnfc version is 1.7.0-rc7. I have created the /usr/local/etc/nfc/libnfc.conf and /usr/local/etc/nfc/devices.d/pn532_uart_on_rpi.conf as follow:

#libnfc.conf file
# allow_autoscan = true
# allow_intrusive_autoscan = false
# log_level = debug
device.name = "microBuilder.eu"
device.connstring = "pn532_uart:/dev/ttyAMA0"
#pn532_uart_on_rpi.conf file
name = "PN532 board via UART"
connstring = "pn532_uart:/dev/ttyAMA0"

When I run nfc-list, the error log was showed:

~$ sudo nfc-list 
debug    libnfc.config    key: [device.name], value: [microBuilder.eu]
debug    libnfc.config    key: [device.connstring], value: [pn532_uart:/dev/ttyAMA0]
debug    libnfc.config    key: [device.name], value: [PN532 board via UART]
debug    libnfc.config    key: [device.connstring], value: [pn532_uart:/dev/ttyAMA0]
unknown    libnfc.general    log_level is set to 3
debug    libnfc.general    allow_autoscan is set to true
debug    libnfc.general    allow_intrusive_scan is set to false
debug    libnfc.general    2 device(s) defined by user
debug    libnfc.general      #0 name: "microBuilder.eu", connstring: "pn532_uart:/dev/ttyAMA0"
debug    libnfc.general      #1 name: "PN532 board via UART", connstring: "pn532_uart:/dev/ttyAMA0"
nfc-list uses libnfc 1.7.0-rc7
debug    libnfc.driver.pn532_uart    Attempt to open: /dev/ttyAMA0 at 115200 bauds.
error    libnfc.driver.pn532_uart    Invalid serial port: /dev/ttyAMA0
debug    libnfc.general    Unable to open "pn532_uart:/dev/ttyAMA0".
nfc-list: ERROR nfc-list.c:128
nfc-list:     Unable to open NFC device: pn532_uart:/dev/ttyAMA0
debug    libnfc.driver.pn532_uart    Attempt to open: /dev/ttyAMA0 at 115200 bauds.
error    libnfc.driver.pn532_uart    Invalid serial port: /dev/ttyAMA0
debug    libnfc.general    Unable to open "pn532_uart:/dev/ttyAMA0".
nfc-list: ERROR nfc-list.c:128
nfc-list:     Unable to open NFC device: pn532_uart:/dev/ttyAMA0

I tried to modified the libnfc.conf device.connstring = "pn532_uart:/dev/ttyAMA0" to device.connstring = "pn532_uart:/dev/ttyUSB0", but the error was still showed.
Also, there is no include "ttyAMA" in my  /libnfc/buses/uart.c. So what's wrong with me and my libnfc?
Thanks!

]]> http://www.libnfc.org/community/user/4141/ 2013-04-20T19:31:51Z http://www.libnfc.org/community/topic/960/unable-to-open-nfc-device-pn532uartdevttyama0-updatenow-can/new/posts/