This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Unable to Receive Directed Advertisements

For some reason I'm not able to receive directed advertisements on the nRF51 development kit. I verified my nRF51 peripheral is sending the direct advertisement packets using the Sniffer tool, but the I don't see any BLE_GAP_EVT_ADV_REPORTS being generated on the central while its scanning.

The central does however see the advertisements if I configure them on the peripheral as connectable undirected.

I'm using SDK 10.0.0 for the peripheral and Windows BLE Driver 0.5.0 for the Central.

Thanks

Parents
  • Currently I have the address of the Central, 0xDE05F038D922, hard-coded in the Peripheral:

    gap_addr->addr_type = 1;
    gap_addr->addr[0] = 0x22;
    gap_addr->addr[1] = 0xD9;
    gap_addr->addr[2] = 0x38;
    gap_addr->addr[3] = 0xF0;
    gap_addr->addr[4] = 0x05;
    gap_addr->addr[5] = 0xDE;
    

    And I acquired the Central address using the sd_ble_gap_address_get API in the Central and dumping it to the console output:

    [0]=22 [1]=D9 [2]=38 [3]=F0 [4]=05 [5]=DE type=1
    

    Again I verified the address is being sent over the air in the direct advertisement packet by using the sniffer tool.

Reply
  • Currently I have the address of the Central, 0xDE05F038D922, hard-coded in the Peripheral:

    gap_addr->addr_type = 1;
    gap_addr->addr[0] = 0x22;
    gap_addr->addr[1] = 0xD9;
    gap_addr->addr[2] = 0x38;
    gap_addr->addr[3] = 0xF0;
    gap_addr->addr[4] = 0x05;
    gap_addr->addr[5] = 0xDE;
    

    And I acquired the Central address using the sd_ble_gap_address_get API in the Central and dumping it to the console output:

    [0]=22 [1]=D9 [2]=38 [3]=F0 [4]=05 [5]=DE type=1
    

    Again I verified the address is being sent over the air in the direct advertisement packet by using the sniffer tool.

Children
No Data
Related