Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

libllcp error coming #4

Open
RatneshFlash opened this issue May 17, 2015 · 0 comments
Open

libllcp error coming #4

RatneshFlash opened this issue May 17, 2015 · 0 comments

Comments

@RatneshFlash
Copy link

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant