certification nrf52840 ETSI EN 300 328 V2.2.2 spirous emission channel 0 and channel 79

RE: certification nrf52840 ETSI EN 300 328 V2.2.2 spirous emission channel 0 and channel 79

alexandre trilles — Thu, 09 Mar 2023 18:37:53 GMT

Dear Amanda,

Thank you very much for help good day

alexandre

RE: certification nrf52840 ETSI EN 300 328 V2.2.2 spirous emission channel 0 and channel 79

Amanda Hsieh — Thu, 09 Mar 2023 18:25:52 GMT

Hi,

[quote user="alexandre trilles "]where can we find information that explains the location of this initialization and how zephyr is launched?[/quote]

See Shell doc.

[quote user="alexandre trilles "]I understood the shell is a Zephyr's service then at what moment we load Zephyr and the shell (.conf, .overlay file )? [/quote]

This post might help.

-Amanda H.

RE: certification nrf52840 ETSI EN 300 328 V2.2.2 spirous emission channel 0 and channel 79

alexandre trilles — Thu, 09 Mar 2023 15:45:43 GMT

Dear Amanda,

you are right the UART is initialized by the shell,

But where can we find information that explains the location of this initialization and how zephyr is launched? I understood the shell is a Zephyr's service then at what moment we load Zephyr and the shell (.conf, .overlay file )?

thanks for help

Alexandre

RE: certification nrf52840 ETSI EN 300 328 V2.2.2 spirous emission channel 0 and channel 79

Amanda Hsieh — Thu, 09 Mar 2023 15:22:41 GMT

Hi,

Good job!

UART is initialized by shell.

-Amanda H.

RE: certification nrf52840 ETSI EN 300 328 V2.2.2 spirous emission channel 0 and channel 79

alexandre trilles — Thu, 09 Mar 2023 09:29:30 GMT

Dear Amanda,

1) I can connect to the board and run commands , the serail baudrate was 115200 !

2) I would like understand where is initialized the UART for the Zephyr's console ?

when I make a break debug on void main(void) the initialization UART is already make !

Thanks for help

Alexandre

RE: certification nrf52840 ETSI EN 300 328 V2.2.2 spirous emission channel 0 and channel 79

Amanda Hsieh — Wed, 08 Mar 2023 19:34:05 GMT

Hi,

[quote user="alexandre trilles "]1) Where are finding all parameters: ble_2Mbit, pattern_11110000..?[/quote]

See the User interface doc.

[quote user="alexandre trilles "]I'm having trouble seeing when UART is initialized for the Zephyr's console ?[/quote]

With the default radio_test, after flashing the sample, you can connect the terminal in the VSCode.

You could see the output like this. If not, try to press the reset button.

[quote user="alexandre trilles "]Do I have add any functions ?[/quote]

No.

-Amanda H.

RE: certification nrf52840 ETSI EN 300 328 V2.2.2 spirous emission channel 0 and channel 79

alexandre trilles — Wed, 08 Mar 2023 15:27:23 GMT

Dear Amanda,

in the apllication radio_test the main.c initialize only clock subsys with function void clock_init(void)

void main(void)

{

printk("Starting Radio Test example\n");

clock_init();

}

I don't understand I seems me when I send commands
data_rate ble_2Mbit, transmit_pattern pattern_11110000 and start_channel 40 I have a echo ?

Do I have add any functions ?

Thanks

alexandre

RE: certification nrf52840 ETSI EN 300 328 V2.2.2 spirous emission channel 0 and channel 79

alexandre trilles — Wed, 08 Mar 2023 12:54:54 GMT

Dear Amanda,

thank you very much the build result is OK.

In the radio test there is an user interface with commands, parameters link: Radio test (short-range) — nRF Connect SDK 2.3.99 documentation (nordicsemi.com)

1) Where are finding all parameters: ble_2Mbit, pattern_11110000..?

Set the data rate with the data_rate command to ble_2Mbit.

Set the transmission pattern with the transmit_pattern command to pattern_11110000.

Set the radio channel with the start_channel command to 40.

2) In the prj.conf Ifile, I see the following define but

CONFIG_CONSOLE_HANDLER=y

CONFIG_SHELL=y

CONFIG_DYNAMIC_INTERRUPTS=y

CONFIG_NRFX_TIMER0=y

CONFIG_ENTROPY_GENERATOR=y

I'm having trouble seeing when UART is initialized for the Zephyr's console ?

Thanks for help

Alexandre

RE: certification nrf52840 ETSI EN 300 328 V2.2.2 spirous emission channel 0 and channel 79

Amanda Hsieh — Tue, 07 Mar 2023 20:20:28 GMT

Hi,

Copy the fem folder under nrf\samples\bluetooth\direct_test_mode\src to C:/Users/atrilles/Nordic/work_at/dtm_axup/radio_test/src and modify Kconfig L.27 to

rsource "src/fem/Kconfig"

-Amanda H.

RE: certification nrf52840 ETSI EN 300 328 V2.2.2 spirous emission channel 0 and channel 79

alexandre trilles — Tue, 07 Mar 2023 16:52:54 GMT

Good morning,

I take the project radio_test https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/peripheral/radio_test/README.html

and the build result indicate an CMake Error, I think I miss it a Kconfig option ? thanks for help

Including generated dts.cmake file: C:/Users/atrilles/Nordic/work_at/dtm_axup/radio_test/build/zephyr/dts.cmake
C:/Users/atrilles/ncs/v2.3.0/zephyr/scripts/kconfig/kconfig.py: C:/Users/atrilles/Nordic/work_at/dtm_axup/radio_test/Kconfig:27: 'C:/Users/atrilles/Nordic/work_at/dtm_axup/radio_test\../../bluetooth/direct_test_mode/src/fem/Kconfig' not found (in 'rsource "../../bluetooth/direct_test_mode/src/fem/Kconfig"'). Check that environment variables are set correctly (e.g. $srctree, which is set to 'C:/Users/atrilles/ncs/v2.3.0/zephyr'). Also note that unset environment variables expand to the empty string.
Parsing C:/Users/atrilles/Nordic/work_at/dtm_axup/radio_test/Kconfig
CMake Error at C:/Users/atrilles/ncs/v2.3.0/zephyr/cmake/modules/kconfig.cmake:328 (message):
command failed with return code: 1
Call Stack (most recent call first):
C:/Users/atrilles/ncs/v2.3.0/nrf/cmake/modules/kconfig.cmake:29 (include)
C:/Users/atrilles/ncs/v2.3.0/zephyr/cmake/modules/zephyr_default.cmake:108 (include)
C:/Users/atrilles/ncs/v2.3.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
C:/Users/atrilles/ncs/v2.3.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:97 (include_boilerplate)
CMakeLists.txt:32 (find_package)

 Executing task: nRF Connect: Build: radio_test/build (active) 

Building radio_test
west build --build-dir c:\Users\atrilles\Nordic\work_at\dtm_axup\radio_test\build c:\Users\atrilles\Nordic\work_at\dtm_axup\radio_test

-- west build: generating a build system
Loading Zephyr default modules (Zephyr base (cached)).
-- Application: C:/Users/atrilles/Nordic/work_at/dtm_axup/radio_test
-- Cache files will be written to: C:/Users/atrilles/ncs/v2.3.0/zephyr/.cache
-- Zephyr version: 3.2.99 (C:/Users/atrilles/ncs/v2.3.0/zephyr)
-- Found west (found suitable version "0.14.0", minimum required is "0.7.1")
-- Board: nrf52840dk_nrf52840
-- Found host-tools: zephyr 0.15.2 (C:/Users/atrilles/ncs/toolchains/v2.3.0/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.15.2 (C:/Users/atrilles/ncs/toolchains/v2.3.0/opt/zephyr-sdk)
-- Found BOARD.dts: C:/Users/atrilles/ncs/v2.3.0/zephyr/boards/arm/nrf52840dk_nrf52840/nrf52840dk_nrf52840.dts
-- Found devicetree overlay: C:/Users/atrilles/Nordic/work_at/dtm_axup/radio_test/nrf52840dk_nrf52840.overlay
-- Generated zephyr.dts: C:/Users/atrilles/Nordic/work_at/dtm_axup/radio_test/build/zephyr/zephyr.dts
-- Generated devicetree_generated.h: C:/Users/atrilles/Nordic/work_at/dtm_axup/radio_test/build/zephyr/include/generated/devicetree_generated.h
-- Including generated dts.cmake file: C:/Users/atrilles/Nordic/work_at/dtm_axup/radio_test/build/zephyr/dts.cmake
C:/Users/atrilles/ncs/v2.3.0/zephyr/scripts/kconfig/kconfig.py: C:/Users/atrilles/Nordic/work_at/dtm_axup/radio_test/Kconfig:27: 'C:/Users/atrilles/Nordic/work_at/dtm_axup/radio_test\../../bluetooth/direct_test_mode/src/fem/Kconfig' not found (in 'rsource "../../bluetooth/direct_test_mode/src/fem/Kconfig"'). Check that environment variables are set correctly (e.g. $srctree, which is set to 'C:/Users/atrilles/ncs/v2.3.0/zephyr'). Also note that unset environment variables expand to the empty string.
Parsing C:/Users/atrilles/Nordic/work_at/dtm_axup/radio_test/Kconfig
CMake Error at C:/Users/atrilles/ncs/v2.3.0/zephyr/cmake/modules/kconfig.cmake:328 (message):
  command failed with return code: 1
Call Stack (most recent call first):
  C:/Users/atrilles/ncs/v2.3.0/nrf/cmake/modules/kconfig.cmake:29 (include)
  C:/Users/atrilles/ncs/v2.3.0/zephyr/cmake/modules/zephyr_default.cmake:108 (include)
  C:/Users/atrilles/ncs/v2.3.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
  C:/Users/atrilles/ncs/v2.3.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:97 (include_boilerplate)
  CMakeLists.txt:32 (find_package)


-- Configuring incomplete, errors occurred!
FATAL ERROR: command exited with status 1: 'c:\Users\atrilles\ncs\toolchains\v2.3.0\opt\bin\cmake.EXE' '-DWEST_PYTHON=c:\Users\atrilles\ncs\toolchains\v2.3.0\opt\bin\python.exe' '-Bc:\Users\atrilles\Nordic\work_at\dtm_axup\radio_test\build' -GNinja '-Sc:\Users\atrilles\Nordic\work_at\dtm_axup\radio_test'

 *  The terminal process terminated with exit code: 1. 
 *  Terminal will be reused by tasks, press any key to close it. 

 *  Executing task: nRF Connect: Build: radio_test/build (active) 

Building radio_test
west build --build-dir c:\Users\atrilles\Nordic\work_at\dtm_axup\radio_test\build c:\Users\atrilles\Nordic\work_at\dtm_axup\radio_test

-- west build: generating a build system
Loading Zephyr default modules (Zephyr base (cached)).
-- Application: C:/Users/atrilles/Nordic/work_at/dtm_axup/radio_test
-- Cache files will be written to: C:/Users/atrilles/ncs/v2.3.0/zephyr/.cache
-- Zephyr version: 3.2.99 (C:/Users/atrilles/ncs/v2.3.0/zephyr)
-- Found west (found suitable version "0.14.0", minimum required is "0.7.1")
-- Board: nrf52840dk_nrf52840
-- Found host-tools: zephyr 0.15.2 (C:/Users/atrilles/ncs/toolchains/v2.3.0/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.15.2 (C:/Users/atrilles/ncs/toolchains/v2.3.0/opt/zephyr-sdk)
-- Found BOARD.dts: C:/Users/atrilles/ncs/v2.3.0/zephyr/boards/arm/nrf52840dk_nrf52840/nrf52840dk_nrf52840.dts
-- Found devicetree overlay: C:/Users/atrilles/Nordic/work_at/dtm_axup/radio_test/nrf52840dk_nrf52840.overlay
-- Generated zephyr.dts: C:/Users/atrilles/Nordic/work_at/dtm_axup/radio_test/build/zephyr/zephyr.dts
-- Generated devicetree_generated.h: C:/Users/atrilles/Nordic/work_at/dtm_axup/radio_test/build/zephyr/include/generated/devicetree_generated.h
-- Including generated dts.cmake file: C:/Users/atrilles/Nordic/work_at/dtm_axup/radio_test/build/zephyr/dts.cmake
C:/Users/atrilles/ncs/v2.3.0/zephyr/scripts/kconfig/kconfig.py: C:/Users/atrilles/Nordic/work_at/dtm_axup/radio_test/Kconfig:27: 'C:/Users/atrilles/Nordic/work_at/dtm_axup/radio_test\../../bluetooth/direct_test_mode/src/fem/Kconfig' not found (in 'rsource "../../bluetooth/direct_test_mode/src/fem/Kconfig"'). Check that environment variables are set correctly (e.g. $srctree, which is set to 'C:/Users/atrilles/ncs/v2.3.0/zephyr'). Also note that unset environment variables expand to the empty string.
Parsing C:/Users/atrilles/Nordic/work_at/dtm_axup/radio_test/Kconfig
CMake Error at C:/Users/atrilles/ncs/v2.3.0/zephyr/cmake/modules/kconfig.cmake:328 (message):
  command failed with return code: 1
Call Stack (most recent call first):
  C:/Users/atrilles/ncs/v2.3.0/nrf/cmake/modules/kconfig.cmake:29 (include)
  C:/Users/atrilles/ncs/v2.3.0/zephyr/cmake/modules/zephyr_default.cmake:108 (include)
  C:/Users/atrilles/ncs/v2.3.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
  C:/Users/atrilles/ncs/v2.3.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:97 (include_boilerplate)
  CMakeLists.txt:32 (find_package)


-- Configuring incomplete, errors occurred!
FATAL ERROR: command exited with status 1: 'c:\Users\atrilles\ncs\toolchains\v2.3.0\opt\bin\cmake.EXE' '-DWEST_PYTHON=c:\Users\atrilles\ncs\toolchains\v2.3.0\opt\bin\python.exe' '-Bc:\Users\atrilles\Nordic\work_at\dtm_axup\radio_test\build' -GNinja '-Sc:\Users\atrilles\Nordic\work_at\dtm_axup\radio_test'

 *  The terminal process terminated with exit code: 1. 
 *  Terminal will be reused by tasks, press any key to close it.

RE: certification nrf52840 ETSI EN 300 328 V2.2.2 spirous emission channel 0 and channel 79

alexandre trilles — Tue, 07 Mar 2023 08:06:38 GMT

Hi,

ok thanks for information, it's good for me

good day

Alexandre

RE: certification nrf52840 ETSI EN 300 328 V2.2.2 spirous emission channel 0 and channel 79

Amanda Hsieh — Mon, 06 Mar 2023 13:44:50 GMT

Hi,

You can use the radio test.

NCS: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/peripheral/radio_test/README.html or
nRF5: https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.1.0/nrf_radio_test_example.html

Regards,
Amanda H.