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?

RE: 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?

MPDeveloper89 — Tue, 27 Sep 2022 20:40:20 GMT

Hello,

I'm using an antenna.

Issue is reported during app execution:

RE: 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 — Sat, 24 Sep 2022 07:32:29 GMT

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.

RE: 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?

MPDeveloper89 — Tue, 20 Sep 2022 21:41:56 GMT

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.

RE: 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 — Thu, 21 Apr 2022 11:28:24 GMT

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.

RE: 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?

Øyvind — Wed, 06 Apr 2022 10:43:29 GMT

[quote user="swz_nordic5340"]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 .[/quote]

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.

RE: 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?

Øyvind — Wed, 06 Apr 2022 10:43:25 GMT

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

RE: 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 — Wed, 06 Apr 2022 01:55:56 GMT

I know your meaning,but there is a some diffrent bettwen nrf and zephyr.

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 .

but there is no output .

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

in nrf, there is the same as previous.err -134.

besides,i alone install zephbyr enviroment, but now i can't use SES IDE

do you know this problem?

thn link is here.https://devzone.nordicsemi.com/f/nordic-q-a/86516/open-nrf-sdk-project-failed-syntaxeroor-uable-to-parse-json-string-how-to-solve-it

RE: 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?

Øyvind — Mon, 04 Apr 2022 09:01:09 GMT

Thanks for clarifying. nRF Connect SDK (NCS) v1.9.0 uses Zephyr v2.7.99.

[quote user=""]C:\Users\Administrator\zephyrproject\zephyr\samples\bluetooth\hci_rpmsg\boards.[/quote]

This is the stand alone version of the Zephyr Project, while NCS should be installed (using Toolchain Manager) under e.g. C:\Users\Administrator\NCS. Note that we do recommend installing NCS to a shorter path i.e. C:\NCS, or similar.

[quote user=""]I add some configurations to nrf5340dk_nrf5340_cpunet.conf files which is in C:\Users\Administrator\zephyrproject\zephyr\samples\bluetooth\hci_rpmsg\boards.[/quote]

As stated in the NCS Bluetooth: Direction finding connectionless beacon:

To build this sample for nRF5340 DK, with angle of arrival mode only, add content of overlay-aoa.conf file to child_image/hci_rpmsg.conf file.

This is referring to nrf\samples\bluetooth\direction_finding_connectionless_tx\child_image\hci_rpmsg.conf

[quote user="swz_nordic5340"]but it have the error -134[/quote]

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.

Kind regards,
Øyvind

RE: 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 — Sat, 02 Apr 2022 06:22:59 GMT

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?

RE: 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?

Øyvind — Fri, 01 Apr 2022 14:11:26 GMT

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