snyc terminated when using AOD examples. nrf52811 as a beacon and nrf52833 as a reciever

I am working on direction finding connectionless locator/beacon(AOD). We designed beacon board with nrf52811(build option is nrf52840 DK nrf52811) and antenna array, use a nrf52833 demo board (nrf52833 carrying a Bluetooth antenna). Software examples are direction_finding_connectionless_rx and direction_finding_connectionless_tx from nRF connect sdk v2.0.0

For the locator, in console ti shows Waiting for periodic sync... sync terminated and after a few cycles, the software shows err -11 and err -5. log are as follows

For nrf52833 locator, in prj.conf i set CONFIG_BT_DF_CTE_RX_AOA=y.

For nrf52811 beacon, i just set nrf52840dk_nrf52811.overlay as follows

 &radio {
	status = "okay";
	/* This is a number of antennas that are available on antenna matrix
	 * designed by Nordic. For more information see README.rst.
	 */
	dfe-antenna-num = <7>;
	/* This is a setting that enables antenna 12 (in antenna matrix designed
	 * by Nordic) for Tx PDU. For more information see README.rst.
	 */
	dfe-pdu-antenna = <0x1>;

	/* These are GPIO pin numbers that are provided to
	 * Radio peripheral. The pins will be acquired by Radio to
	 * drive antenna switching when AoD is enabled.
	 * Pin numbers are selected to drive switches on antenna matrix
	 * desinged by Nordic. For more information see README.rst.
	 */
	dfegpio0-gpios = <&gpio0 2 0>;
	dfegpio1-gpios = <&gpio0 3 0>;
	dfegpio2-gpios = <&gpio0 4 0>;
	dfegpio3-gpios = <&gpio0 5 0>;
};

In prj.conf I set CONFIG_BT_DF_CTE_TX_AOD=y.

in readme file, it shows to set nrf5340dk_nrf5340_cpunet.overlay and nrf5340dk_nrf5340_cpuapp.overlay. I didn't do any of that because of using nrf52811, does it matters? 

For sync terminated, can I debug by watching registers? Which registers should I pay attention to? 

Thanks

Parents
  • Hello,

    I just went through what you were trying to do.. I would like to point out that it is not possible to use the nRF52840-DK to emulate the nRF52811 for Direction finding.. the nRF52840 doesn't support CTE and hence why the application fails.. Apart from the nRF5340-DK, the only DK in the 52 series that supports CTE/direction finding is the nRF52833-DK.

    Best Regards,

    Swathy

Reply
  • Hello,

    I just went through what you were trying to do.. I would like to point out that it is not possible to use the nRF52840-DK to emulate the nRF52811 for Direction finding.. the nRF52840 doesn't support CTE and hence why the application fails.. Apart from the nRF5340-DK, the only DK in the 52 series that supports CTE/direction finding is the nRF52833-DK.

    Best Regards,

    Swathy

Children
  • I just tried to use nrf52833 as beacon and nrf52833 as receiver for AOA example, but the log still shows sync terminated and err -11. Now I set 

    CONFIG_BT_CTLR_DF_ANT_SWITCH_TX=n

    CONFIG_BT_DF_CTE_TX_AOD=n
    00> *** Booting Zephyr OS build v3.0.99-ncs1  ***
    00> 
    00> Starting Connectionless Locator Demo
    00> 
    00> Bluetooth initialization...[00:00:00.001,892] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
    00> [00:00:00.001,922] <inf> bt_hci_core: HW Variant: nRF52x (0x0002)
    00> [00:00:00.001,922] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 3.0 Build 99
    00> [00:00:00.002,624] <inf> bt_hci_core: Identity: DC:69:F4:20:2F:62 (random)
    00> [00:00:00.002,655] <inf> bt_hci_core: HCI: version 5.3 (0x0c) revision 0x0000, manufacturer 0x05f1
    00> [00:00:00.002,655] <inf> bt_hci_core: LMP: version 5.3 (0x0c) subver 0xffff
    00> success
    00> 
    00> Scan callbacks register...success.
    00> 
    00> Periodic Advertising callbacks register...success.
    00> 
    00> Start scanning...success
    00> 
    00> Waiting for periodic advertising...[DEVICE]: 13:FC:DF:3E:38:4F (random), AD evt type 5, Tx Pwr: 127, RSSI -58 DF Connectionless Beacon App C:0 S:0 D:0 SR:0 E:1 Prim: LE 1M, Secn: LE 2M, Interval: 0x0780 (2400 ms), SID: 0
    00> 
    00> ing.
    00> 
    00> [DEVICE]: 13:FC:DF:3E:38:4F (random), AD evt type 5, Tx Pwr: 127, RSSI -57 DF Connectionless Beacon App C:0 S:0 D:0 SR:0 E:1 Prim: LE 1M, Secn: LE 2M, Interval: 0x0780 (2400 ms), SID: 0
    00> 
    00> failed (err -11)
    00> 
    00> test
    00> 
    00> Deleting Periodic Advertising Sync...[00:00:18.149,688] <wrn> bt_hci_core: opcode 0x2045 status 0x0c
    00> failed (err -5)
    00> 
    00> PER_ADV_SYNC[0]: [DEVICE]: 13:FC:DF:3E:38:4F (random) sync terminated
    00> 
    00> [DEVICE]: 13:FC:DF:3E:38:4F (random), AD evt type 5, Tx Pwr: 127, RSSI -54 DF Connectionless Beacon App C:0 S:0 D:0 SR:0 E:1 Prim: LE 1M, Secn: LE 2M, Interval: 0x0780 (2400 ms), SID: 0
    00> 
    00> [DEVICE]: 13:FC:DF:3E:38:4F (random), AD evt type 5, Tx Pwr: 127, RSSI -53 DF Connectionless Beacon App C:0 S:0 D:0 SR:0 E:1 Prim: LE 1M, Secn: LE 2M, Interval: 0x0780 (2400 ms), SID: 0
    00> 
    00> [DEVICE]: 13:FC:DF:3E:38:4F (random), AD evt type 5, Tx Pwr: 127, RSSI -53 DF Connectionless Beacon App C:0 S:0 D:0 SR:0 E:1 Prim: LE 1M, Secn: LE 2M, Interval: 0x0780 (2400 ms), SID: 0
    How can I debug it.
    Best Regards,
    Cheng
  • I also want to ask whether the synsucceeds is related to the antenna array, thanks

  • read termination reason(bt_le_per_adv_sync_term_info *info) , the info->reason shows 62, could you tell me want does it mean, thanks.

Related