get the DEVICEADDR from the advertising packet?

RE: get the DEVICEADDR from the advertising packet?

Pablo — Tue, 01 Nov 2016 15:49:07 GMT

Ok. Now yes i see the same. Thank you!

RE: get the DEVICEADDR from the advertising packet?

Sigurd — Tue, 01 Nov 2016 15:47:26 GMT

Feel free to mark the answer as correct, if you think I have answered your question.

RE: get the DEVICEADDR from the advertising packet?

Sigurd — Tue, 01 Nov 2016 15:35:19 GMT

Also, you should not use %u when printing hex values, use %08X instead.

E.g. printf("adviceaddr0: %08X\n", NRF_FICR->DEVICEADDR[0]);

RE: get the DEVICEADDR from the advertising packet?

Sigurd — Tue, 01 Nov 2016 15:28:52 GMT

Example:

On the central I get advertisement packet with: “Address 0xE104D4DAF4F9”

This is in LSB format, so in MSB format this is: F9:F4:DA:DF:04:E1.

On the peripheral I have this:

DEVICEADDR[0]: 0xDAD404E1 -> DA:D4:04:E1

DEVICEADDR[1]: 0x2B8679F4 -> 2B:86:79:F4

The reason why "79" becomes "F9" is because the specification says that the 2 MSBit of the address must be set '11' . E.g. 79 binary -> 01:11:10:01 We set ‘11’ as the MSBit -> 11:11:10:01 -> F9

RE: get the DEVICEADDR from the advertising packet?

Pablo — Tue, 01 Nov 2016 14:47:48 GMT

This number should be the same that i print in the slave if i execute this lines:

printf("adviceaddr0: %u", NFR_FICR->DEVICEADDR[0]); printf("adviceaddr1: %u", NFR_FICR->DEVICEADDR[1]);

RE: get the DEVICEADDR from the advertising packet?

Sigurd — Tue, 01 Nov 2016 12:22:46 GMT

You can read it directly from the advertisement packet. You can do it like this:

static void on_adv_report(ble_evt_t * p_ble_evt)
{
    uint32_t              err_code;
    const ble_gap_evt_t * p_gap_evt = &p_ble_evt->evt.gap_evt;

    
    const ble_gap_evt_adv_report_t * p_adv_report = &p_gap_evt->params.adv_report;
            
    const ble_gap_addr_t peer_addr = p_adv_report->peer_addr;
    
    printf("Address %02x%02x%02x%02x%02x%02x\r\n",
                             peer_addr.addr[0],
                             peer_addr.addr[1],
                             peer_addr.addr[2],
                             peer_addr.addr[3],
                             peer_addr.addr[4],
                             peer_addr.addr[5]
                             );
}