No NFC device found PN532_UART last build

[GoogleCodeExporter]

What steps will reproduce the problem?
1.
Installed PL2303 Usb to serial adapter
Attached the pn532 via UART

2.
git clone
autoreconf -is
./configure --with-drivers=pn532_uart
make 
make install
ldconfig

3.
What is the expected output? 
when I do a nfc-list the device should be listed (like in libnfc-1.6.0rc1 
DONLOADABLE package)

What do you see instead?

fopen: No such file or directory
unkown  libnfc.general  log_level is set to 1
nfc-list uses libnfc libnfc-1.6.0-rc1-165-g2651cdc
No NFC device found.

What version of the product are you using? On what operating system?
Linux bt 3.2.6 #1 SMP Fri Feb 17 10:40:05 EST 2012 i686 GNU/Linux
Backtrack 5r3 under vmware viewer

Please provide any additional information below.
also created udev rule file in /lib/udev/rules.d/

this is udev rule file content:

# PN532-UART
ATTRS{idVendor}=="067b", ATTRS{idProduct}=="2303", MODE="0664", GROUP="plugdev"

Original issue reported on code.google.com by swanaw...@gmail.com on 3 Dec 2012 at 2:34

[GoogleCodeExporter]

UPDATE:

if i do an export LIBNFC_INTRUSIVE_SCAN=yes I now get:

fopen: No such file or directory
unkown  libnfc.general  log_level is set to 1
nfc-list uses libnfc libnfc-1.6.0-rc1-165-g2651cdc
error   libnfc.driver.pn532_uart        Unable to read ACK
error   libnfc.driver.pn532_uart        Unable to read ACK
NFC device: pn532_uart:/dev/ttyUSB0 opened
1 ISO14443A passive target(s) found:
ISO/IEC 14443A (106 kbps) target:
    ATQA (SENS_RES): 00  04
       UID (NFCID1): 8a  24  7b  b7
      SAK (SEL_RES): 08

so something related to bus scanning/timing ...

Original comment by swanaw...@gmail.com on 3 Dec 2012 at 3:03

[GoogleCodeExporter]

Hello,
Thanks for reporting.

Some improvements have been made for this kind of devices : you can now setup a 
device in libnfc.conf and/or device configuration directory 
(/etc/nfc/devices.d/)

Please check latest commits.

BTW, some improvements have to be made to enhance display: fopen and the two 
errors are really disturbing for user...

Thanks!

Nevertheless, your udev rule is useless as the detected usb device at udev 
level is a simple USB to UART dongle and should not need to be assign to 
plugdev.

Original comment by neomil...@gmail.com on 5 Dec 2012 at 12:31

[GoogleCodeExporter]

Display is now fixed in ra3a3fa284840f2a8a65111f736d75c766e86cd3d

Original comment by romu...@libnfc.org on 5 Dec 2012 at 5:39

• Changed state: Invalid
• Added labels: OpSys-Linux