nfc-tools / libllcp Goto Github PK

When i run npp-server on ubuntu16.04, the terminal shows "core dump" if I take my Huawei closed to PN532. I don't know how to with it. Could you help me ?

npp-client seems not work with my nexus 4. 
snep seems to be supported better.

Details in attachment.

Original issue reported on code.google.com by [email protected] on 7 Dec 2013 at 8:39

Attachments:

• add-snep-client-and-server.patch

Hi,
I am trying to communicate nfc module with Android mobile.
I used itead nfc module interface with rasberry pi.
And using libnfc1.7.1 and libllcp for communicate with mobile.

After run libllcp client example,
$ LIBNFC_LOG_LEVEL=3 ./examples/snep-client/snep-client
I get this error
"error libnfc.driver.pn532_spi Unable to wait for SPI data. (RX)
libllcp.mac.link Could not send 2 bytes"

Log:=
debug libnfc.bus.spi RX: 00
debug libnfc.bus.spi TX: 02
debug libnfc.bus.spi RX: 00
debug libnfc.bus.spi TX: 02
debug libnfc.bus.spi RX: 00
debug libnfc.bus.spi TX: 02
debug libnfc.bus.spi RX: 01
debug libnfc.bus.spi TX: 03
debug libnfc.bus.spi RX: 00 00 ff 20
debug libnfc.bus.spi RX: e0
debug libnfc.bus.spi TX: 03
debug libnfc.bus.spi RX: d5
debug libnfc.bus.spi TX: 03
debug libnfc.bus.spi RX: 57
debug libnfc.bus.spi RX: 00
debug libnfc.bus.spi TX: 03
debug libnfc.bus.spi RX: 01 df 0b 63 89 dc 35 50 ec 59 a2 00 00 00 0e 32 46 66 6d 01 01 11 03 02 00 13 04 01 96
debug libnfc.bus.spi RX: 96
debug libnfc.bus.spi TX: 03
debug libnfc.bus.spi RX: 00
libllcp.mac.link (pn532_spi:/dev/spidev0.0) nfc_initiator_poll_dep_target() succeeded
libllcp.mac.link (pn532_spi:/dev/spidev0.0) LLCP Link activated (initiator)
libllcp.llc.link llc_link_configure (0x143d80, (nil), 0)
libllcp.llc.link mq_open (/libllcp-2532-0x143d80-up)
libllcp.llc.link mq_open (/libllcp-2532-0x143d80-down)
libllcp.llc.link LLC Link started successfully
libllcp.mac.link Sending 2 bytes
libllcp.mac.link LTOs: 1000 ms (local), 100 ms (remote)
debug libnfc.chip.pn53x InDataExchange
debug libnfc.chip.pn53x Timeout value: 1100libllcp.llc.llc (0xb6d16470) Link activated
libllcp.llc.llc (0xb6d16470) mq_receive+

debug libnfc.bus.spi TX: 01 00 00 ff 05 fb d4 40 01 00 00 eb
debug libnfc.bus.spi TX: 02
debug libnfc.bus.spi RX: 01
debug libnfc.bus.spi TX: 03
debug libnfc.bus.spi RX: 00 00 ff 00 ff 00
debug libnfc.chip.pn53x PN53x ACKed
debug libnfc.bus.spi TX: 02
debug libnfc.bus.spi RX: 00
debug libnfc.bus.spi TX: 02
debug libnfc.bus.spi RX: 00
.
.
.
.
* AFTER SOME SAME LOG****
.
.
.

debug libnfc.bus.spi RX: 00
debug libnfc.bus.spi TX: 02
debug libnfc.bus.spi RX: 00
debug libnfc.bus.spi TX: 02
debug libnfc.bus.spi RX: 00
debug libnfc.bus.spi TX: 02
debug libnfc.bus.spi RX: 00
debug libnfc.bus.spi TX: 02
debug libnfc.bus.spi RX: 00
error libnfc.driver.pn532_spi Unable to wait for SPI data. (RX)
libllcp.mac.link Could not send 2 bytes

Questions:
I used pn532(itead nfc) module to communicate with android 4.3 (samsung S3).
Is there any problem in libllcp which cause libllcp.mac.link error?
Is this right to use libllcp library and snep protocol to send my NDEF massage to android?

libllcp does not support g++ toolchain. Add macros to let it do.

Usage:

cd libllcp
patch -p1 < add_cpp_support.patch

Original issue reported on code.google.com by [email protected] on 2 Dec 2013 at 10:11

Attachments:

• add_cpp_support.patch

What steps will reproduce the problem?
1. Use npp-server example to receive a vCard from an Android phone

What is the expected output? What do you see instead?
Expect a dump of the NDEF message with the vcard data.  Get nothing.  Running 
under strace suggests that it needs to fragment the message when putting it in 
the message queue:
[pid 22867] mq_timedsend(4, "C 
\0\1\0\0\0\1\1\0\0\0\256\322\f\237text/x-vcardBEGI"..., 187, 0, NULL) = -1 
EMSGSIZE (Message too long)


What version of the product are you using? On what operating system?
Git head (29907cacab0c), Debian testing x86_64, ACR122U


Please provide any additional information below.
Blindly going in and making wild increases to the mq_msgsize parameter when 
creating the message queues works around the problem, but some form of message 
fragmentation seems like it would be a more durable solution.

Original issue reported on code.google.com by [email protected] on 19 Jul 2013 at 3:04

When building the project on mac osx, I get the error:

checking for mqueue.h... no
configure: error: mqueue.h is requiered.

Is it possible to build/run libllcp on mac osx?