In zephyr,i use direction rx and tx,in tx there a error code (-134),but i can't solve it,this problem occur in ncs direction.where is the problem?

[swz_nordic]

I use the zephyr version 3.0.9,when i build the hci_rpmsg project,it have serial error.then i chnange the onfigruation by  add some new definition.

I add some configurations to nrf5340dk_nrf5340_cpunet.conf files which is in C:\Users\Administrator\zephyrproject\zephyr\samples\bluetooth\hci_rpmsg\boards.

CONFIG_BT_PER_ADV_SYNC=y

# Limit number of possible connection to decrease memory usage
CONFIG_BT_MAX_CONN=1

# Required to enable BT_PER_ADV_SYNC_MAX
CONFIG_BT_PER_ADV_SYNC=y
CONFIG_BT_OBSERVER=y

CONFIG_BT_CTLR=y
CONFIG_BT_LL_SW_SPLIT=y

CONFIG_BT_CTLR_ADV_EXT=y
CONFIG_BT_CTLR_SYNC_PERIODIC=y

CONFIG_BT_MAX_CONN=1
CONFIG_BT_EXT_ADV=y

then i build the rx and tx ,in putty teminator,there is a error.

*** Booting Zephyr OS build v2.7.99-ncs1  ***

Starting Direction Finding periodic advertising Beacon Demo

Bluetooth initialization...success

Advertising set create...success

Update CTE params...failed (err -134)

I try to solve the problem by all kinds of way to,but it don't matter.where is the problem ?or do the procedures have problem?

[Øyvind]

Hello,

I'm somewhat confused. What version of nRF Connect SDK are you working on? 

Have you tested with a standard sample from the nRF Connect SDK v1.9.1 e.g. nRF5340: Multiprotocol RPMsg

Kind regards,
Øyvind

[swz_nordic]

Yes，thanks for your reply.i use the zephyr project. as zepyer describled.I don't make a try about nRF5340: Multiprotocol RPMsg.

I use NCS 1.9.0 for my project,but it have the error -134.I use the diffrent boards to flash this example,unforchunately,it has the same err.may it be your design problem.do you have a try?

[Øyvind]

swz_nordic said:

The zepyer has no child _image,we should use hci_rpmsg as network core,i  build  the network core and apliacation cor in C:\NCS\v1.9.1\zephyr\samples\bluetooth\hci_rpmsg and C:\NCS\v1.9.1\zephyr\samples\bluetooth\direction_finding_connectionless_tx .

Please use the samples found in under C:\NCS\v1.9.1\nrf\samples, as stated in our documentation.

Bluetooth: Direction finding connectionless locator

Bluetooth: Direction finding connectionless beacon

nRF Connect SDK is based on the Zephyr project. Please install the nRF Connect SDK and focus on its environment. The Segger Embedded Studio is bundled with the Toolchain Manager found in nRF Connect for Desktop. Note that from version 2.0.0 of NCS, the VS Code extension is recommended.

[Øyvind]

swz_nordic said:

The zepyer has no child _image,we should use hci_rpmsg as network core,i  build  the network core and apliacation cor in C:\NCS\v1.9.1\zephyr\samples\bluetooth\hci_rpmsg and C:\NCS\v1.9.1\zephyr\samples\bluetooth\direction_finding_connectionless_tx .

Please use the samples found in under C:\NCS\v1.9.1\nrf\samples, as stated in our documentation.

Bluetooth: Direction finding connectionless locator

Bluetooth: Direction finding connectionless beacon

nRF Connect SDK is based on the Zephyr project. Please install the nRF Connect SDK and focus on its environment. The Segger Embedded Studio is bundled with the Toolchain Manager found in nRF Connect for Desktop. Note that from version 2.0.0 of NCS, the VS Code extension is recommended.

[swz_nordic]

thank,i have solve my problem.i can't get the VS Code extension in my computer.it doesn't  work well.i notice this problem some days ago.The link is here.

i think that my NCS envirment has some problems.can you help me?look forward to your reply.

[MPDeveloper89]

Hello,

I countered a similar issue using zephyr for nRF5340.

First issue regarding the advertsing set error hase been fixed with this topic.

Then I updated hci_rpmsg.conf like overlay-aoa.conf but issue (error -134) is still present.

Corrisponding *.conf file are:

direction_finding_connectionless_tx - prj.conf 

CONFIG_BT=y
CONFIG_BT_DEVICE_NAME="DF Connectionless Beacon App"

CONFIG_BT_CTLR_PHY_CODED=y
CONFIG_BT_EXT_ADV=y
CONFIG_BT_USER_PHY_UPDATE=y

CONFIG_BT_PER_ADV=y
CONFIG_BT_BROADCASTER=y

# Enable Direction Finding Feature including AoA and AoD
CONFIG_BT_DF=y
CONFIG_BT_DF_CONNECTIONLESS_CTE_TX=y

direction_finding_connectionless_tx - overlay-aoa.conf 

# Disable AoD Feature (antenna switching) in Tx mode
CONFIG_BT_CTLR_DF_ANT_SWITCH_TX=n

child_image/hci_rpmsg.conf

#
# Copyright (c) 2021 Nordic Semiconductor
#
# SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
#

CONFIG_BT_EXT_ADV=y
CONFIG_BT_CTLR_ADV_EXT=y
CONFIG_BT_CTLR_PHY_CODED=y

# Disable AoD Feature (antenna switching) in Tx mode
CONFIG_BT_CTLR_DF_ANT_SWITCH_TX=n

Do you have some suggestion?

Thank you in advance.

[swz_nordic]

how many antennas do you use?i think lt is the configuration problem.sorry,i don't solve the problem.You can give the configuration information to Nordic support.

"Error -134 can be found in errno.h - e.g. zephyr\lib\libc\minimal\include\errno.h, which states:

#define ENOTSUP 134         /**< Unsupported value */

Please verify your configurations and let me know if this helps."

I now use the nrf52833dk,i can get the IQ sample in this.

[MPDeveloper89]

Hello,

I'm using an antenna.

Issue is reported during app execution: