Testing direction finding beacon in nRF Connect SDK v1.5.0

RE: Testing direction finding beacon in nRF Connect SDK v1.5.0

Simonr — Mon, 12 Apr 2021 08:25:09 GMT

The Getting Started assistant should be a sufficient guide for installing master branch of the nRFConnect SDK as well, as long as you remember using "git checkout master & west update". We don't have a specific guide to install the master branch.

I see that your current west version is v0.9.0, which indeed is outdated as the master branch requires v0.10.1. As the toolchain manager is only updated for NCS v1.5.0 as of yet, the West version it installs will be v0.9.0.

Updating your west version here should be sufficient.

Best regards,

Simon

RE: Testing direction finding beacon in nRF Connect SDK v1.5.0

choehyunho — Sun, 11 Apr 2021 12:41:03 GMT

I managed to build successfully after copying 'toolchain' directory from v1.5.0 to latest, and upgrade some python packages.

But still not sure whether this is the correct installation.

Please let me know if there is some specific guide about installing master branch.

When I followed the official documentation, I got the above errors during my first sample build.

Maybe caused by parallel installation both 'nRFConnect Toolchain manager' way and manual way.

RE: Testing direction finding beacon in nRF Connect SDK v1.5.0

choehyunho — Fri, 09 Apr 2021 12:42:31 GMT

Hi Simonr,

I understood, but have trouble to install/test master branch properly.

Somewhat off the topic here, but I'll continue here.

Previously, I already installed NCS 1.5.0 with nRFConnect for Desktop -> Toolchain Manager.

Now, I followed the install guideline in Installing the nRF Connect SDK manually, and master branch seems to be properly installed.

But, I tried my project build in command line, build failed because west version is too low, which referenced the one in v1.5.0 tree.

The error messages as follows:

How should I install master branch in parallel with released ones?

C:\Users\firebird\source\repos\ncs\latest\projects\beacon>west build -b nrf52833dk_nrf52833
-- west build: generating a build system
Including boilerplate (Zephyr base (cached)): C:/Users/firebird/source/repos/ncs/latest/zephyr/cmake/app/boilerplate.cmake
-- Application: C:/Users/firebird/source/repos/ncs/latest/projects/beacon
-- Using NCS Toolchain 1.5.0 for building. (C:/Users/firebird/source/repos/ncs/v1.5.0/toolchain/cmake)
-- Zephyr version: 2.5.99 (C:/Users/firebird/source/repos/ncs/latest/zephyr)
-- Found west (found suitable version "0.9.0", minimum required is "0.7.1")
WARNING: west v0.10 or later is required by the manifest
  West version: v0.9.0
  Manifest file: C:\Users\firebird\source\repos\ncs\latest\nrf\west.yml
  This should work, but most commands won't.
  To silence this warning, upgrade west.
CMake Error at C:/Users/firebird/source/repos/ncs/latest/zephyr/cmake/zephyr_module.cmake:61 (message):
  Traceback (most recent call last):

    File "C:\Users\firebird\source\repos\ncs\v1.5.0\toolchain\opt\bin\Lib\site-packages\west\manifest.py", line 1226, in __init__
      validate(source_data)
    File "C:\Users\firebird\source\repos\ncs\v1.5.0\toolchain\opt\bin\Lib\site-packages\west\manifest.py", line 420, in validate
      raise ManifestVersionError(min_version_str)

  west.manifest.ManifestVersionError: ('0.10', None)



  The above exception was the direct cause of the following exception:



  Traceback (most recent call last):

    File "C:/Users/firebird/source/repos/ncs/latest/zephyr/scripts/zephyr_module.py", line 378, in <module>
      main()
    File "C:/Users/firebird/source/repos/ncs/latest/zephyr/scripts/zephyr_module.py", line 283, in main
      manifest = Manifest.from_file()
    File "C:\Users\firebird\source\repos\ncs\v1.5.0\toolchain\opt\bin\Lib\site-packages\west\manifest.py", line 1084, in from_file
      return Manifest(**kwargs)
    File "C:\Users\firebird\source\repos\ncs\v1.5.0\toolchain\opt\bin\Lib\site-packages\west\manifest.py", line 1228, in __init__
      raise ManifestVersionError(mv.version, file=source_file) from mv

  west.manifest.ManifestVersionError: ('0.10',
  WindowsPath('C:/Users/firebird/source/repos/ncs/latest/nrf/west.yml'))

Call Stack (most recent call first):
  C:/Users/firebird/source/repos/ncs/latest/zephyr/cmake/app/boilerplate.cmake:183 (include)
  C:/Users/firebird/source/repos/ncs/latest/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:24 (include)
  C:/Users/firebird/source/repos/ncs/latest/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:40 (include_boilerplate)
  CMakeLists.txt:22 (find_package)


-- Configuring incomplete, errors occurred!
FATAL ERROR: command exited with status 1: 'C:\Program Files\CMake\bin\cmake.EXE' '-DWEST_PYTHON=c:\users\firebird\appdata\local\programs\python\python37\python.exe' '-BC:\Users\firebird\source\repos\ncs\latest\projects\beacon\build' '-SC:\Users\firebird\source\repos\ncs\latest\projects\beacon' -GNinja -DBOARD=nrf52833dk_nrf52833

RE: Testing direction finding beacon in nRF Connect SDK v1.5.0

Simonr — Fri, 09 Apr 2021 09:15:25 GMT

Hi again

Sorry, I misunderstood your issue in the initial ticket. I spoke to one of the devs about this, and you won't be able to backport this example to NCS v1.5.0, as this example is only supported in the master branch or the next tag release.

BT_FEAT_LE_CONNECTIONLESS_CTE_TX is enabled by the Zephyr Controller Subsystem in the master branch.

Best regards,

Simon

RE: Testing direction finding beacon in nRF Connect SDK v1.5.0

choehyunho — Fri, 09 Apr 2021 06:42:02 GMT

First, I already mentioned that I "backported" the sample from latest (not released) repository to SDK 1.5.0.

Please notice.

During backporting, I changed "dfe-antenna-num" to "dfe-ant-num", and removed dfe-pdu-antenna property in devicetree.

And applied AOA configuration by default, for testing.

And about BT_FEAT_LE_CONNECTIONLESS_CTE_TX(), I know it is defined in hci.h

But, it is evaluated in directions.c as below.

int bt_df_set_adv_cte_tx_param(struct bt_le_ext_adv *adv,
				const struct bt_df_adv_cte_tx_param *params)
{
	__ASSERT_NO_MSG(adv);
	__ASSERT_NO_MSG(params);

	int err;

	if (!BT_FEAT_LE_CONNECTIONLESS_CTE_TX(bt_dev.le.features)) {
		return -ENOTSUP;
	}
...

I want to know how to enable this feature.

RE: Testing direction finding beacon in nRF Connect SDK v1.5.0

Simonr — Fri, 09 Apr 2021 05:49:22 GMT

Can you provide some information on what these "slight modifications" are that you did to the sample? Do you get the EINVAL error if you try building and programming the unmodified project?

BT_FEAT_LE_CONNECTIONLESS_CTE_TX() is defined in the hci.h header file, have you included this in your project?

Best regards,

Simon

RE: Testing direction finding beacon in nRF Connect SDK v1.5.0

choehyunho — Wed, 07 Apr 2021 16:29:36 GMT

In direction.c, BT_FEAT_LE_CONNECTIONLESS_CTE_TX() is not enabled, and it causes ENOTSUP error.

How can I enable this feature myself? Or, is this configured in SoftDevice?

RE: Testing direction finding beacon in nRF Connect SDK v1.5.0

choehyunho — Wed, 07 Apr 2021 08:43:23 GMT

It returns error 22: EINVAL...:(

RE: Testing direction finding beacon in nRF Connect SDK v1.5.0

Simonr — Wed, 07 Apr 2021 05:44:40 GMT

Have you enabled the transmission of CTE using the bt_df_adv_cte_tx_enable()? It should be sufficient to follow the guide to build and run the sample from our documentation.

Best regards,

Simon

RE: Testing direction finding beacon in nRF Connect SDK v1.5.0

Simonr — Tue, 06 Apr 2021 14:28:11 GMT

We're currently working through our backlog after the Easter vacation here in Norway, I will get back to you tomorrow. Thank you for your patience.

Best regards,

Simon