libllcp: "Invalid Received Frame" (13), returned error: "RF Transmission Error" (-20)) when receiving vcard

270 views
Skip to first unread message

Victor Palacio

unread,
May 21, 2014, 2:30:35 AM5/21/14
to nfc-too...@googlegroups.com
Hello,

I'm trying to send a vcard contact to a NFC reader using libllcp. The phone is a samsung S3 (GT-I9300).

I tested snep-server example application with 2 different readers; SCL3712 (PN53x driver) and ADRBv2 (arygon driver).

Both tests return same error when I touch to beam a contact:
...
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 03 fd d5 87 13 91 00
debug    libnfc.chip.pn53x    Chip error: "Invalid Received Frame" (13), returned error: "RF Transmission Error" (-20))
...
or
...
debug    libnfc.bus.uart    RX: 00 00 ff 03 fd
debug    libnfc.bus.uart    RX: d5 87
debug    libnfc.bus.uart    RX: 13
debug    libnfc.bus.uart    RX: 91 00
debug    libnfc.chip.pn53x    Chip error: "Invalid Received Frame" (13), returned error: "RF Transmission Error" (-20))
...

Can anybody give me a hint about this error?

Regards,

-----Logs obtained follows:

Trying to receive NFC vcard with libllcp (snep-server)

1 USB (SCL 3712):
sudo LIBNFC_LOG_LEVEL=3 ./examples/snep-server/snep-server -o ndef.txt
debug    libnfc.config    key: [log_level], value: [2]
debug    libnfc.config    Unable to open directory: /etc/nfc/devices.d
debug    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    0 device(s) defined by user
debug    libnfc.general    0 device(s) found using acr122_usb driver
debug    libnfc.driver.pn53x_usb    device found: Bus 007 Device 012
debug    libnfc.general    1 device(s) found using pn53x_usb driver
debug    libnfc.driver.pn53x_usb    3 element(s) have been decoded from "pn53x_usb:007:012"
debug    libnfc.driver.pn53x_usb    TX: 00 00 ff 00 ff 00
debug    libnfc.chip.pn53x    GetFirmwareVersion
debug    libnfc.driver.pn53x_usb    TX: 00 00 ff 02 fe d4 02 2a 00
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 06 fa d5 03 33 02 07 07 e5 00
error    libnfc.chip.pn53x    Unexpected PN53x reply!
debug    libnfc.driver.pn53x_usb    TX: 00 00 ff ff 00 00
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 06 fa d5 03 33 02 07 07 e5 00
debug    libnfc.chip.pn53x    GetFirmwareVersion
debug    libnfc.driver.pn53x_usb    TX: 00 00 ff 02 fe d4 02 2a 00
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 00 ff 00
debug    libnfc.chip.pn53x    PN53x ACKed
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 06 fa d5 03 33 02 07 07 e5 00
debug    libnfc.chip.pn53x    SetParameters
debug    libnfc.driver.pn53x_usb    TX: 00 00 ff 03 fd d4 12 14 06 00
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 00 ff 00
debug    libnfc.chip.pn53x    PN53x ACKed
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 02 fe d5 13 18 00
debug    libnfc.general    "SCM Micro / SCL3711-NFC&RW" (pn53x_usb:007:012) has been claimed.
debug    libnfc.chip.pn53x    ReadRegister
debug    libnfc.driver.pn53x_usb    TX: 00 00 ff 0c f4 d4 06 63 02 63 03 63 0d 63 38 63 3d b0 00
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 00 ff 00
debug    libnfc.chip.pn53x    PN53x ACKed
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 08 f8 d5 07 00 80 80 00 00 00 24 00
debug    libnfc.chip.pn53x    RFConfiguration
debug    libnfc.driver.pn53x_usb    TX: 00 00 ff 04 fc d4 32 01 00 f9 00
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 00 ff 00
debug    libnfc.chip.pn53x    PN53x ACKed
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 02 fe d5 33 f8 00
debug    libnfc.chip.pn53x    PN53X_SFR_P3 (Port 3 value)
debug    libnfc.chip.pn53x    ReadRegister
debug    libnfc.driver.pn53x_usb    TX: 00 00 ff 04 fc d4 06 ff b0 77 00
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 00 ff 00
debug    libnfc.chip.pn53x    PN53x ACKed
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 04 fc d5 07 00 3e e6 00
debug    libnfc.chip.pn53x    ReadRegister
debug    libnfc.driver.pn53x_usb    TX: 00 00 ff 08 f8 d4 06 63 05 63 38 63 3d 83 00
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 00 ff 00
debug    libnfc.chip.pn53x    PN53x ACKed
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 06 fa d5 07 00 00 00 00 24 00
debug    libnfc.chip.pn53x    PN53X_REG_CIU_TxAuto (Controls the settings of the antenna driver)
debug    libnfc.chip.pn53x    WriteRegister
debug    libnfc.driver.pn53x_usb    TX: 00 00 ff 05 fb d4 08 63 05 04 b8 00
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 00 ff 00
debug    libnfc.chip.pn53x    PN53x ACKed
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 03 fd d5 09 00 22 00
debug    libnfc.chip.pn53x    TgInitAsTarget
debug    libnfc.chip.pn53x    Timeout value: 5000
debug    libnfc.driver.pn53x_usb    TX: 00 00 ff 3b c5 d4 8c 03 08 00 12 34 56 40 01 fe 12 34 56 78 90 12 c0 c1 c2 c3 c4 c5 c6 c7 0f ab 00 01 02 03 04 05 06 07 08 09 14 46 66 6d 01 01 11 02 02 00 80 03 02 00 13 04 01 a0 07 01 03 00 75 00
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 00 ff 00
debug    libnfc.chip.pn53x    PN53x ACKed

< WAIT FOR PHONE 5000ms >

debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 21 df d5 8d 04 1e d4 00 10 e8 96 d4 04 7a ca 58 e7 30 00 00 00 32 46 66 6d 01 01 10 03 02 00 01 04 01 96 91 00
debug    libnfc.chip.pn53x    TgGetData
debug    libnfc.chip.pn53x    Timeout value: 3000
debug    libnfc.driver.pn53x_usb    TX: 00 00 ff 02 fe d4 86 a6 00
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 00 ff 00
debug    libnfc.chip.pn53x    PN53x ACKed
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 05 fb d5 87 00 11 20 73 00
debug    libnfc.chip.pn53x    TgSetData
debug    libnfc.driver.pn53x_usb    TX: 00 00 ff 04 fc d4 8e 00 00 9e 00
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 00 ff 00
debug    libnfc.chip.pn53x    PN53x ACKed
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 03 fd d5 8f 00 9c 00
debug    libnfc.chip.pn53x    TgGetData
debug    libnfc.chip.pn53x    Timeout value: 3000
debug    libnfc.driver.pn53x_usb    TX: 00 00 ff 02 fe d4 86 a6 00
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 00 ff 00
debug    libnfc.chip.pn53x    PN53x ACKed
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 05 fb d5 87 00 00 00 a4 00
debug    libnfc.chip.pn53x    TgSetData
debug    libnfc.driver.pn53x_usb    TX: 00 00 ff 0b f5 d4 8e 81 84 02 02 02 00 05 01 01 8c 00
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 00 ff 00
debug    libnfc.chip.pn53x    PN53x ACKed
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 03 fd d5 8f 00 9c 00
debug    libnfc.chip.pn53x    TgGetData
debug    libnfc.chip.pn53x    Timeout value: 3000
debug    libnfc.driver.pn53x_usb    TX: 00 00 ff 02 fe d4 86 a6 00
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 00 ff 00
debug    libnfc.chip.pn53x    PN53x ACKed
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 05 fb d5 87 00 00 00 a4 00
debug    libnfc.chip.pn53x    TgSetData
debug    libnfc.driver.pn53x_usb    TX: 00 00 ff 04 fc d4 8e 00 00 9e 00
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 00 ff 00
debug    libnfc.chip.pn53x    PN53x ACKed
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 03 fd d5 8f 00 9c 00
debug    libnfc.chip.pn53x    TgGetData
debug    libnfc.chip.pn53x    Timeout value: 3000
debug    libnfc.driver.pn53x_usb    TX: 00 00 ff 02 fe d4 86 a6 00
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 00 ff 00

<TOUCH TO BEAM>

debug    libnfc.chip.pn53x    PN53x ACKed
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 03 fd d5 87 13 91 00
debug    libnfc.chip.pn53x    Chip error: "Invalid Received Frame" (13), returned error: "RF Transmission Error" (-20))
debug    libnfc.driver.pn53x_usb    TX: 00 00 ff 00 ff 00
debug    libnfc.chip.pn53x    InRelease
debug    libnfc.driver.pn53x_usb    TX: 00 00 ff 03 fd d4 52 00 da 00
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 00 ff 00
debug    libnfc.chip.pn53x    PN53x ACKed
debug    libnfc.driver.pn53x_usb    RX: 00 00 ff 03 fd d5 53 00 d8 00


2 ttyUSB (ADRB):
sudo LIBNFC_LOG_LEVEL=3 ./examples/snep-server/snep-server -o ndef.txt
debug    libnfc.config    key: [allow_autoscan], value: [false]
debug    libnfc.config    Parse error on line #4:                      

debug    libnfc.config    key: [allow_intrusive_scan], value: [false]
debug    libnfc.config    Parse error on line #9:                             

debug    libnfc.config    key: [log_level], value: [2]
debug    libnfc.config    key: [device.name], value: [PORTICON RFID IN ADRBv2]
debug    libnfc.config    key: [device.connstring], value: [arygon:/dev/ttyUSB0]
debug    libnfc.config    Unable to open directory: /etc/nfc/devices.d
debug    libnfc.general    log_level is set to 3
debug    libnfc.general    allow_autoscan is set to false
debug    libnfc.general    allow_intrusive_scan is set to false
debug    libnfc.general    1 device(s) defined by user
debug    libnfc.general      #0 name: "PORTICON RFID IN ADRBv2", connstring: "arygon:/dev/ttyUSB0"
debug    libnfc.driver.arygon    Attempt to open: /dev/ttyUSB0 at 9600 bauds.
debug    libnfc.bus.uart    Serial port speed requested to be set to 9600 bauds.
debug    libnfc.bus.uart    TX: 30 61 72
debug    libnfc.bus.uart    RX: 46 46 30 30 30 30 30 30 0d 0a
debug    libnfc.bus.uart    TX: 30 61 76
debug    libnfc.bus.uart    RX: 46 46 30 30 30 30 30 36 30 30 56 37 2e 32 0d 0a
debug    libnfc.chip.pn53x    GetFirmwareVersion
debug    libnfc.bus.uart    TX: 32 00 00 ff 02 fe d4 02 2a 00
debug    libnfc.bus.uart    RX: 00 00 ff 00 ff 00
debug    libnfc.chip.pn53x    PN53x ACKed
debug    libnfc.bus.uart    RX: 00 00 ff 06 fa
debug    libnfc.bus.uart    RX: d5 03
debug    libnfc.bus.uart    RX: 32 01 06 07
debug    libnfc.bus.uart    RX: e8 00
debug    libnfc.chip.pn53x    SetParameters
debug    libnfc.bus.uart    TX: 32 00 00 ff 03 fd d4 12 14 06 00
debug    libnfc.bus.uart    RX: 00 00 ff 00 ff 00
debug    libnfc.chip.pn53x    PN53x ACKed
debug    libnfc.bus.uart    RX: 00 00 ff 02 fe
debug    libnfc.bus.uart    RX: d5 13
debug    libnfc.bus.uart    RX: 18 00
debug    libnfc.general    "arygon:/dev/ttyUSB0 00V7.2" (arygon:/dev/ttyUSB0) has been claimed.
debug    libnfc.chip.pn53x    ReadRegister
debug    libnfc.bus.uart    TX: 32 00 00 ff 0c f4 d4 06 63 02 63 03 63 0d 63 38 63 3d b0 00
debug    libnfc.bus.uart    RX: 00 00 ff 00 ff 00
debug    libnfc.chip.pn53x    PN53x ACKed
debug    libnfc.bus.uart    RX: 00 00 ff 07 f9
debug    libnfc.bus.uart    RX: d5 07
debug    libnfc.bus.uart    RX: 00 00 00 00 00
debug    libnfc.bus.uart    RX: 24 00
debug    libnfc.chip.pn53x    PN53X_REG_CIU_TxMode (Defines the transmission data rate and framing during transmission)
debug    libnfc.chip.pn53x    PN53X_REG_CIU_RxMode (Defines the transmission data rate and framing during receiving)
debug    libnfc.chip.pn53x    WriteRegister
debug    libnfc.bus.uart    TX: 32 00 00 ff 08 f8 d4 08 63 02 80 63 03 80 59 00
debug    libnfc.bus.uart    RX: 00 00 ff 00 ff 00
debug    libnfc.chip.pn53x    PN53x ACKed
debug    libnfc.bus.uart    RX: 00 00 ff 02 fe
debug    libnfc.bus.uart    RX: d5 09
debug    libnfc.bus.uart    RX: 22 00
debug    libnfc.chip.pn53x    RFConfiguration
debug    libnfc.bus.uart    TX: 32 00 00 ff 04 fc d4 32 01 00 f9 00
debug    libnfc.bus.uart    RX: 00 00 ff 00 ff 00
debug    libnfc.chip.pn53x    PN53x ACKed
debug    libnfc.bus.uart    RX: 00 00 ff 02 fe
debug    libnfc.bus.uart    RX: d5 33
debug    libnfc.bus.uart    RX: f8 00
debug    libnfc.chip.pn53x    ReadRegister
debug    libnfc.bus.uart    TX: 32 00 00 ff 08 f8 d4 06 63 05 63 38 63 3d 83 00
debug    libnfc.bus.uart    RX: 00 00 ff 00 ff 00
debug    libnfc.chip.pn53x    PN53x ACKed
debug    libnfc.bus.uart    RX: 00 00 ff 05 fb
debug    libnfc.bus.uart    RX: d5 07
debug    libnfc.bus.uart    RX: 00 00 00
debug    libnfc.bus.uart    RX: 24 00
debug    libnfc.chip.pn53x    PN53X_REG_CIU_TxAuto (Controls the settings of the antenna driver)
debug    libnfc.chip.pn53x    WriteRegister
debug    libnfc.bus.uart    TX: 32 00 00 ff 05 fb d4 08 63 05 04 b8 00
debug    libnfc.bus.uart    RX: 00 00 ff 00 ff 00
debug    libnfc.chip.pn53x    PN53x ACKed
debug    libnfc.bus.uart    RX: 00 00 ff 02 fe
debug    libnfc.bus.uart    RX: d5 09
debug    libnfc.bus.uart    RX: 22 00
debug    libnfc.chip.pn53x    TgInitAsTarget
debug    libnfc.chip.pn53x    Timeout value: 5000
debug    libnfc.bus.uart    TX: 32 00 00 ff 3b c5 d4 8c 03 08 00 12 34 56 40 01 fe 12 34 56 78 90 12 c0 c1 c2 c3 c4 c5 c6 c7 0f ab 00 01 02 03 04 05 06 07 08 09 14 46 66 6d 01 01 11 02 02 00 80 03 02 00 13 04 01 60 07 01 03 00 b5 00
debug    libnfc.bus.uart    RX: 00 00 ff 00 ff 00
debug    libnfc.chip.pn53x    PN53x ACKed
...
< WAIT FOR PHONE 5000ms >
...
debug    libnfc.bus.uart    RX: 00 00 ff 21 df
debug    libnfc.bus.uart    RX: d5 8d
debug    libnfc.bus.uart    RX: 04 1e d4 00 25 9d 9c 90 3c f9 6d a0 ac b3 00 00 00 32 46 66 6d 01 01 10 03 02 00 01 04 01 96
debug    libnfc.bus.uart    RX: 1b 00
debug    libnfc.chip.pn53x    TgGetData
debug    libnfc.chip.pn53x    Timeout value: 3000
debug    libnfc.bus.uart    TX: 32 00 00 ff 02 fe d4 86 a6 00
debug    libnfc.bus.uart    RX: 00 00 ff 00 ff 00
debug    libnfc.chip.pn53x    PN53x ACKed
debug    libnfc.bus.uart    RX: 00 00 ff 05 fb
debug    libnfc.bus.uart    RX: d5 87
debug    libnfc.bus.uart    RX: 00 11 20
debug    libnfc.bus.uart    RX: 73 00
debug    libnfc.chip.pn53x    TgSetData
debug    libnfc.bus.uart    TX: 32 00 00 ff 0b f5 d4 8e 81 84 02 02 02 00 05 01 01 8c 00
debug    libnfc.bus.uart    RX: 00 00 ff 00 ff 00
debug    libnfc.chip.pn53x    PN53x ACKed
debug    libnfc.bus.uart    RX: 00 00 ff 03 fd
debug    libnfc.bus.uart    RX: d5 8f
debug    libnfc.bus.uart    RX: 00
debug    libnfc.bus.uart    RX: 9c 00
debug    libnfc.chip.pn53x    TgGetData
debug    libnfc.chip.pn53x    Timeout value: 3000
debug    libnfc.bus.uart    TX: 32 00 00 ff 02 fe d4 86 a6 00
debug    libnfc.bus.uart    RX: 00 00 ff 00 ff 00
debug    libnfc.chip.pn53x    PN53x ACKed
debug    libnfc.bus.uart    RX: 00 00 ff 05 fb
debug    libnfc.bus.uart    RX: d5 87
debug    libnfc.bus.uart    RX: 00 00 00
debug    libnfc.bus.uart    RX: a4 00
debug    libnfc.chip.pn53x    TgSetData
debug    libnfc.bus.uart    TX: 32 00 00 ff 04 fc d4 8e 00 00 9e 00
debug    libnfc.bus.uart    RX: 00 00 ff 00 ff 00
debug    libnfc.chip.pn53x    PN53x ACKed
debug    libnfc.bus.uart    RX: 00 00 ff 03 fd
debug    libnfc.bus.uart    RX: d5 8f
debug    libnfc.bus.uart    RX: 00
debug    libnfc.bus.uart    RX: 9c 00
debug    libnfc.chip.pn53x    TgGetData
debug    libnfc.chip.pn53x    Timeout value: 3000
debug    libnfc.bus.uart    TX: 32 00 00 ff 02 fe d4 86 a6 00
debug    libnfc.bus.uart    RX: 00 00 ff 00 ff 00
...
<TOUCH TO BEAM>
...
debug    libnfc.chip.pn53x    PN53x ACKed
debug    libnfc.bus.uart    RX: 00 00 ff 03 fd
debug    libnfc.bus.uart    RX: d5 87
debug    libnfc.bus.uart    RX: 13
debug    libnfc.bus.uart    RX: 91 00
debug    libnfc.chip.pn53x    Chip error: "Invalid Received Frame" (13), returned error: "RF Transmission Error" (-20))
debug    libnfc.chip.pn53x    InRelease
debug    libnfc.bus.uart    TX: 32 00 00 ff 03 fd d4 52 00 da 00
debug    libnfc.bus.uart    RX: 00 00 ff 00 ff 00
debug    libnfc.chip.pn53x    PN53x ACKed
debug    libnfc.bus.uart    RX: 00 00 ff 03 fd
debug    libnfc.bus.uart    RX: d5 53
debug    libnfc.bus.uart    RX: 00
debug    libnfc.bus.uart    RX: d8 00

Victor Palacio

unread,
May 29, 2014, 3:48:15 AM5/29/14
to nfc-too...@googlegroups.com
I tried also libllcp branch 'socket', with same result.

I'm using libnfc 1.7.1.

Victor Palacio

unread,
May 29, 2014, 4:48:14 AM5/29/14
to nfc-too...@googlegroups.com
Here is libllcp log for this problem... Looks like an underlying libnfc problem, but i'm just guessing...



vpalacio@vpalacio-dev:~/libllcp-socket/libllcp$ examples/snep-server/snep-server -o ndef
libllcp.llc.link    service 0x8719890 bound to SAP 1
libllcp.llc.link    service 0x8719b58 bound to SAP 4
libllcp.mac.link    (arygon:/dev/ttyUSB0 00V7.2) Attempting to activate LLCP Link as target (blocking)
libllcp.mac.link    (arygon:/dev/ttyUSB0 00V7.2) LLCP Link activated (target)
libllcp.llc.link    llc_link_configure (0x87198e0, 0xbf8a9e4b, 10)
libllcp.llc.link    Version: 1.0 (remote)
libllcp.llc.link    Version: 1.0 (agreed)
libllcp.llc.link    WKS: 0x0001
libllcp.llc.link    LTO: 1500 ms (0x96)
libllcp.llc.link    socketpair
libllcp.llc.link    LLC Link started successfully
libllcp.mac.link    Waiting for MAC Link PDU exchange thread to exit
libllcp.llc.llc    (0xb7732b70) Link activated
libllcp.llc.llc    (0xb7732b70) socket recv+
libllcp.mac.link    Received 2 bytes
libllcp.mac.link    RX: 11 20
libllcp.mac.link    DSAP: 04, PTYPE: CONNECT(04), SSAP: 20
libllcp.mac.link    Received 2 PDU bytes
libllcp.llc.llc    (0xb7732b70) socket recv+ done
libllcp.llc.llc    (0xb7732b70) Received 2 bytes
libllcp.llc.llc    (0xb7732b70) Connect PDU
libllcp.llc.llc    (0xb7732b70) Spawning Data Link Connection [32 -> 4] accept routine
libllcp.llc.connection    socketpair
libllcp.llc.llc    (0xb7732b70) Data Link Connection [4 -> 32] accepted (no accept routine provided)
libllcp.llc.llc    (0xb7732b70) Data Link Connection [4 -> 32] accept routine launched (service 4)
libllcp.llc.llc    (0xb7732b70) Start handle datagram.
libllcp.llc.llc    (0xb7732b70) Start handle transmission.
libllcp.llc.llc    (0xb7732b70) Read 0 bytes from service 4
libllcp.llc.llc    (0xb7732b70) length =  0 service = 4
libllcp.llc.llc    (0xb7732b70) Data Link Connection [4 -> 32] accepted (service 4).  Sending CC
libllcp.llc.llc    (0xb7732b70) socket send+
libllcp.llc.llc    (0xb7732b70) Sent 9 bytes
libllcp.mac.link    Sending 9 bytes
libllcp.mac.link    Sending 9 bytes
libllcp.llc.llc    (0xb7732b70) socket recv+
libllcp.mac.link    TX: 81 84 02 02 02 00 05 01 01
libllcp.mac.link    DSAP: 20, PTYPE: CC(06), SSAP: 04
libllcp.mac.link    Received 2 bytes
libllcp.mac.link    RX: 00 00
libllcp.mac.link    DSAP: 00, PTYPE: SYMM(00), SSAP: 00
libllcp.mac.link    Received 2 PDU bytes
libllcp.llc.llc    (0xb7732b70) socket recv+ done
libllcp.llc.llc    (0xb7732b70) Received 2 bytes
libllcp.llc.llc    (0xb7732b70) Symmetry PDU
libllcp.llc.llc    (0xb7732b70) Start handle datagram.
libllcp.llc.llc    (0xb7732b70) Start handle transmission.
libllcp.llc.llc    (0xb7732b70) Read 0 bytes from service 4
libllcp.llc.llc    (0xb7732b70) length =  0 service = 4
libllcp.llc.llc    (0xb7732b70) socket send+
libllcp.llc.llc    (0xb7732b70) Nothing to send
libllcp.llc.llc    (0xb7732b70) socket recv+
libllcp.mac.link    Select timeout.
libllcp.mac.link    Sending 2 bytes
libllcp.mac.link    Sending 2 bytes
libllcp.mac.link    TX: 00 00
libllcp.mac.link    DSAP: 00, PTYPE: SYMM(00), SSAP: 00
libllcp.mac.link    MAC Level error on PDU reception (-20)
libllcp.mac.link    pdu_receive returned -1
libllcp.mac.link    NFC error: RF Transmission Error
libllcp.llc.link    Deactivating LLC Link
libllcp.llc.link    The LLC Link has an active MAC link
libllcp.mac.link    MAC Link deactivation requested (reason: 0)
libllcp.llc.link    Back to LLC Link deactivation
libllcp    Try to stop thread (-1217189008)
libllcp.llc.llc    (0xb7732b70) Thread quit
libllcp    Thread (-1217189008) stopped
libllcp.llc.link    Stopping Data Link Connection [244 -> 88]
libllcp.llc.connection    Stopping Data Link Connection [4 -> 32]
libllcp.llc.connection    connection killed by other threads.
libllcp    Try to stop thread (-1233974416)
libllcp    Thread (-1233974416) stopped
libllcp.llc.connection    Freeing Data Link Connection [4 -> 32]
libllcp.llc.link    Data Link Connection [244 -> 88] stopped
libllcp.llc.link    LLC Link deactivated
libllcp.mac.link    MAC Link exchange PDU exchange thread terminated (returned 0)
libllcp.llc.link    Freeing service 4
libllcp.llc.link    Freeing service 1

Jiapeng Li

unread,
May 30, 2014, 2:26:54 AM5/30/14
to nfc-too...@googlegroups.com
Could you first try snep-client, then try snep-server to see what happens?
> --
> You received this message because you are subscribed to the Google Groups
> "nfc-tools developers group" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to nfc-tools-dev...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



--
JiapengLi
Blog:jiapeng.me
GitHub: github.com/jiapengli
AboutMe: about.me/lich

Victor Palacio

unread,
Jun 2, 2014, 10:51:29 AM6/2/14
to nfc-too...@googlegroups.com
What Android app must I use to do this test? What is trying to send snep-client? Looks like a SmartPoster URL to me. I'm not sure how can Contacts App manage that info.

This is the log when I try to use Contacts while executing snep-client:

vpalacio@vpalacio-dev:~/libllcp-socket/libllcp$ ./examples/snep-client/snep-client
libllcp.llc.link    service 0x9a27728 bound to SAP 1
libllcp.llc.link    service 0x9a279f0 bound to SAP 32
libllcp.llc.connection    socketpair
libllcp.mac.link    (arygon:/dev/ttyUSB0 00V7.2) Attempting to activate LLCP Link as initiator
libllcp.mac.link    (arygon:/dev/ttyUSB0 00V7.2) nfc_initiator_init() succeeded
error    libnfc.driver.arygon    Unable to receive data. (RX)
error    libnfc.driver.arygon    Unable to receive data. (RX)
libllcp.mac.link    (arygon:/dev/ttyUSB0 00V7.2) nfc_initiator_poll_dep_target() succeeded
libllcp.mac.link    (arygon:/dev/ttyUSB0 00V7.2) LLCP Link activated (initiator)
libllcp.llc.link    llc_link_configure (0x9a27778, (nil), 0)

libllcp.llc.link    socketpair
libllcp.llc.link    LLC Link started successfully
libllcp.llc.llc    (0xb77dbb70) Link activated
libllcp.llc.llc    (0xb77dbb70) socket recv+
libllcp.llc.connection    socketpair
libllcp.mac.link    Sending 2 bytes
libllcp.mac.link    LTOs: 1000 ms (local), 100 ms (remote)
error    libnfc.driver.arygon    Unable to receive data. (RX)
libllcp.mac.link    Could not send 2 bytes

libllcp.mac.link    TX: 00 00
libllcp.mac.link    DSAP: 00, PTYPE: SYMM(00), SSAP: 00
libllcp.mac.link    Bootstrap failed.

libllcp.llc.link    Deactivating LLC Link
libllcp.llc.link    The LLC Link has an active MAC link
libllcp.mac.link    MAC Link deactivation requested (reason: 0)
libllcp.llc.link    Back to LLC Link deactivation
libllcp    Try to stop thread (-1216496784)
libllcp.llc.llc    (0xb77dbb70) Thread quit
libllcp    Thread (-1216496784) stopped
libllcp.llc.link    Stopping Data Link Connection [244 -> 240]
libllcp.llc.connection    Stopping Data Link Connection [32 -> 4]
libllcp.llc.connection    Freeing Data Link Connection [32 -> 4]
libllcp.llc.link    Data Link Connection [244 -> 240] stopped
libllcp.llc.link    LLC Link deactivated
libllcp.llc.link    Deactivating LLC Link
libllcp.llc.link    LLC Link deactivated
libllcp.llc.link    Freeing service 32
libllcp.llc.link    Freeing service 1
error    libnfc.driver.arygon    Unable to receive data. (RX)

Victor Palacio

unread,
Jun 16, 2014, 7:08:31 AM6/16/14
to nfc-too...@googlegroups.com
Maybe the problem is a response length limit?

When using command TgInitAsTarget, I assume MIFARE params and FELICA params does not apply.

General Bytes are; 14 (20 bytes) 46 66 6d 01 01 11 02 02 00 80 03 02 00 13 04 01 60 07 01 03... there are no TKBytes (TKLen = 0x00).

What are the meaning of this bytes?. Is there the reason for my problem? I cannot find nothing about general bytes in PN532 manual.

Regards,

Victor Palacio

unread,
Jun 20, 2014, 2:15:27 AM6/20/14
to nfc-too...@googlegroups.com
I succeded (somehow) to receive only short contacts.

¿There is a limit condition for data with snep-server example? I cannot find anything about that.

Regards,
Reply all
Reply to author
Forward
0 new messages