[nRF Connect SDK]How to use custom NFC tag to connect?

Target nRF52832(nrf52dk_nrf52832)
SDK NCS v1.9.1

We are preparing NFC with classic tag.(Not connected to nrf52832, separated custom tag)
Recently I found that android cannot connect to BLE until BLE scan is done once.
(Of course NFC tagging and connection works well after BLE scan)

Q1. In case we use classic tag, can I connect to BLE without BLE scan? (in my test, I know that it is not easy)

Q2. If we change classic tag to BLE tag, can we connect BLE without scan?

Q3. I'm testing custom BLE tag for test, and I found I cannot make bonding. (sample peripheral_hids_keyboard)
Do you have any idea? I'm not sure if it is from SW or wrong programmed tag.
 
Security failed: F8:F1:E6:2F:79:5C (public) level 1 err 1
E: reason 0x4
Security failed: F8:F1:E6:2F:79:5C (public) level 1 err 1
E: reason 0x4
Security failed: F8:F1:E6:2F:79:5C (public) level 1 err 1
E: reason 0x4
Security failed: F8:F1:E6:2F:79:5C (public) level 1 err 1
Disconnected from F8:F1:E6:2F:79:5C (public) (reason 19) 

Parents Reply
  • Hello.

    I already checked that sample.
    As I told you, we're using custom tag not attached to nordic chip.
    How can I use it as BLE tag?

    in addition. it seems security level is mismatch. I'm expecting mode 4 but actually 1. Can I change it?
    00> HS connected
    00> HS Connected 56:50:EA:BC:F4:C3 (random)
    00> pairing_accept conn: 56:50:EA:BC:F4:C3 (random)
    00> io_capability: 4
    00> auth_req: 2d
    00> E: reason 0x4
    00> Security failed: 56:50:EA:BC:F4:C3 (random) level 1 err 1
    00> Pairing failed conn: 56:50:EA:BC:F4:C3 (random), reason 1 Disconnected: 56:50:EA:BC:F4:C3 (random) (reason 22)

Children
Related