RE: Issues with getting scan request peer address though BLE_GAP_EVT_SCAN_REQ_REPORT event

aeozyalcin — Mon, 09 Mar 2020 03:01:07 GMT

That was it! For some reason, the MAC address reported by scan_req_report.peer_addr was backwards. peer_addr.addr[5] ended up being 0xDC. Thank you for the idea!

RE: Issues with getting scan request peer address though BLE_GAP_EVT_SCAN_REQ_REPORT event

Edvin — Fri, 06 Mar 2020 12:43:39 GMT

Hello,

First of all, as you probably noticed, the dongle is not really ideal for development, as it doesn't have any debug capabilities, nor logging backend support. I can really recommend you to get hold of an nRF52840 DK for development, and then you can flash the application to the dongle once it is working.

That being said, back to your question. How do you know that the Bluetooth address of the RPi is DC:A6:... ?

I have noticed that some devices report their addresses in different order (LSB/MSB). Try to check if (peer_addr.addr[5] = 0xDC)

(you can use "0x20" instead of 220.

As you say, since the LED is turned on if you move it outside the if-check, the event apparently occurs, so if you'd had a debugger, you could either have logged the addresses of the devices or set a breakpoint and checked the address.

Best regards,

Edvin