Update CTE params...failed (err -134) in 'direction_finding_connectionless_tx'

Hi

I'm working with the sample 'ncs1.7.1\nrf\samples\bluetooth\direction_finding_connectionless_tx' on nRF5340,  I followed this page and built with AoA mode, then added content of overlay-aoa.conf file to child_image/hci_rpmsg.conf file, ran this code:

G:\ncs_v1.7.1\ncs1.7.1\nrf\samples\bluetooth\direction_finding_connectionless_tx>west build -b nrf5340dk_nrf5340_cpuapp -- -DCMAKE_BUILD_TYPE=overlay-aoa.conf

Build and flash seems correct,  but output in putty is wrong:

*** Booting Zephyr OS build v2.6.99-ncs1-1  ***
Starting Connectionless Beacon Demo
Bluetooth initialization...success
Advertising set create...success
Update CTE params...failed (err -134)

 I tried as Amanda said, erased the kit before flash, but it doesn't help. How to solve this problem? Thanks in advance.

Best regards,

Majoris

Parents Reply Children
  • Hey again Majoris!

    Hmm that is a bit odd, though we have only recently started supporting the nRF5340 with our direction finding samples, there might be some compatibility hurdles we have to make our way through. Could you try the Zephyr samples and see if they give a similar error?

    Best regards,

    Elfving

  • Hi Elfving

    With zephyr sample I get this:

    PER_ADV_SYNC[0]: [DEVICE]: 18:83:EC:9A:52:8D (random), tx_power 127, RSSI -36, CTE AOA, data length 0, data: 
    CTE[59]: samples count 168, cte type Unknown, slot durations: 0 [us], packet status CRC OK, RSSI 0

    The CTE[x], samples count [x], cte type, slot durations seems wrong. I really hope to fix it.

    And I noticed that in zephyr sample, line 91, the function is pocket_status2str(uint8_t status), but in nrf sample it is packet_status2str(uint8_t status), maybe it is just a clerical error. 

    Best regards,

    Majrois

Related