esb, shockburst, running on nrf5340dk's

[mej7000]

I have 3 nrf boards connected. 2x nrf52832 and 1x nrf5340.

esb_tx is running on nrf52832(682782977)
esb_rx is running on nrf52832(682497942) & nrf5340(1050025410)

west build -b nrf5340dk_nrf5340_cpunet -p builds correctly and flashes without error

PS C:\nrf\esb_prx> west flash -d build_1
-- west flash: rebuilding
ninja: no work to do.
-- west flash: using runner nrfjprog
There are multiple boards connected.
1. 1050025410
2. 682782977
Please select one with desired serial number (1-2): 1
-- runners.nrfjprog: Flashing file: build_1\zephyr\zephyr.hex
[ #################### ] 2.055s | Erase file - Done erasing
[ #################### ] 0.243s | Program file - Done programming
[ #################### ] 0.243s | Verify file - Done verifying
Applying pin reset.
-- runners.nrfjprog: Board with serial number 1050025410 flashed successfully.

esb_rx is working on the nrf52, but not on the nrf53.

... To be through, I powered down esb_tx_nrf52832(682782977) and flashed another nrf5340dk(1050077823) and programmed it to be esb_tx:

PS C:\nrf\esb_ptx> west flash -d build_1
-- west flash: rebuilding
ninja: no work to do.
-- west flash: using runner nrfjprog
There are multiple boards connected.
1. 1050025410
2. 1050077823
3. 682497942
Please select one with desired serial number (1-3): 2
-- runners.nrfjprog: Flashing file: build_1\zephyr\zephyr.hex
[ #################### ] 2.044s | Erase file - Done erasing
[ #################### ] 0.235s | Program file - Done programming
[ #################### ] 0.236s | Verify file - Done verifying
Applying pin reset.
-- runners.nrfjprog: Board with serial number 1050077823 flashed successfully.

Although 1050077823 (nrf5340-esb_tx) flashed correctly. Blinky continues to run (as it already had) on nrf5340-esb_tx, which probably makes sense, but I'm not getting any kind of esb response from either (nrf52832 or nrf5340) esb-rx.

There is something I am not understanding about how to flash to nrf5340_CPUNET? Maybe it's flashing correctly, but esb needs to be called from CPUAPP to start it working?? I'm close, but missing something...

Ultimately the goal is to have a network of nrf5340's in a Star configuration. I see that there is shared memory between CPUAPP and CPUNET. I assume somehow it's used to pass data from CPUAPP to CPUNET for transmission/reception. I don't exactly understand how that works either, but I figure the first step is to get the esb Sample to work on nrf5340dk's without modification. But, if there are additional samples that target this use case I would be interested in reviewing those too.

The final configuration goal is to have the center of the star network also be running BLE-UART (so the central esb in the Star Network will relay the esb data from the nodes to a BLE app). I am assuming that there is no problem running both esb and BLE at the same time.

esb_prx_ptx.zip

[ovrebekk]

Hi Michael

Does it work if you flash the empty app core sample on the nRF5340 appcore? 

Possibly you just miss the config on the app core side to enable the netcore:

CONFIG_BOARD_ENABLE_CPUNET=y

Regarding combining BLE and ESB on the nRF5340 I am working on an unofficial sample showing how to do this which you can have a look at here. 

You will find a separate sample for the nRF5340 netcore, while the prx and ptx sample can be built either for the nRF5340 appcore, or for one of the nRF52 devices. 

Best regards
Torbjørn

[mej7000]

Does it work if you flash the empty app core sample on the nRF5340 appcore?  Yes. empty app seems to work.

west build -b nrf5340dk_nrf5340_cpuapp -p

PS C:\nrf\empty_app_core> west build -b nrf5340dk_nrf5340_cpuapp -p
-- west build: making build dir C:\nrf\empty_app_core\build pristine
-- west build: generating a build system
Loading Zephyr default modules (Zephyr base).
-- Application: C:/nrf/empty_app_core
-- CMake version: 3.20.5
-- Using NCS Toolchain 2.5.20231017.848171396279 for building. (C:/ncs/toolchains/c57af46cb7/cmake)
CMake Deprecation Warning at C:/ncs/v2.5.1/zephyr/cmake/modules/FindDeprecated.cmake:121 (message):
'PYTHON_PREFER' variable is deprecated. Please use Python3_EXECUTABLE
instead.
Call Stack (most recent call first):
C:/ncs/v2.5.1/zephyr/cmake/modules/python.cmake:16 (find_package)
C:/ncs/v2.5.1/zephyr/cmake/modules/zephyr_default.cmake:129 (include)
C:/ncs/v2.5.1/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
C:/ncs/v2.5.1/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
CMakeLists.txt:9 (find_package)

-- Found Python3: C:/ncs/toolchains/c57af46cb7/opt/bin/python.exe (found suitable version "3.8.2", minimum required is "3.8") found components: Interpreter
-- Cache files will be written to: C:/ncs/v2.5.1/zephyr/.cache
-- Zephyr version: 3.4.99 (C:/ncs/v2.5.1/zephyr)
-- Found west (found suitable version "1.1.0", minimum required is "0.14.0")
-- Board: nrf5340dk_nrf5340_cpuapp
-- Found host-tools: zephyr 0.16.1 (C:/ncs/toolchains/c57af46cb7/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.16.1 (C:/ncs/toolchains/c57af46cb7/opt/zephyr-sdk)
-- Found Dtc: C:/ncs/toolchains/c57af46cb7/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")
-- Found BOARD.dts: C:/ncs/v2.5.1/zephyr/boards/arm/nrf5340dk_nrf5340/nrf5340dk_nrf5340_cpuapp.dts
-- Generated zephyr.dts: C:/nrf/empty_app_core/build/zephyr/zephyr.dts
-- Generated devicetree_generated.h: C:/nrf/empty_app_core/build/zephyr/include/generated/devicetree_generated.h
-- Including generated dts.cmake file: C:/nrf/empty_app_core/build/zephyr/dts.cmake

warning: THREAD_STACK_INFO (defined at kernel/Kconfig:189) was assigned the value 'n' but got the
value 'y'. See docs.zephyrproject.org/.../kconfig.html and/or
look up THREAD_STACK_INFO in the menuconfig/guiconfig interface. The Application Development Primer,
Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be
helpful too.

warning: BOOT_DELAY (defined at kernel/Kconfig:400) was assigned the value '0' but got the value ''.
Check these unsatisfied dependencies: MULTITHREADING (=n). See
docs.zephyrproject.org/.../kconfig.html and/or look up BOOT_DELAY in the
menuconfig/guiconfig interface. The Application Development Primer, Setting Configuration Values,
and Kconfig - Tips and Best Practices sections of the manual might be helpful too.

Parsing C:/ncs/v2.5.1/zephyr/Kconfig
Loaded configuration 'C:/ncs/v2.5.1/zephyr/boards/arm/nrf5340dk_nrf5340/nrf5340dk_nrf5340_cpuapp_defconfig'
Merged configuration 'C:/nrf/empty_app_core/prj.conf'
Configuration saved to 'C:/nrf/empty_app_core/build/zephyr/.config'
Kconfig header saved to 'C:/nrf/empty_app_core/build/zephyr/include/generated/autoconf.h'
-- Found GnuLd: c:/ncs/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe (found version "2.38")
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: C:/ncs/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc.exe
CMake Warning at C:/ncs/v2.5.1/zephyr/soc/arm/nordic_nrf/nrf53/CMakeLists.txt:13 (message):

Your application may be affected by the anomaly 160 that concerns the
nRF5340 SoC. The related workaround cannot be applied, because your
application has the system clock disabled (CONFIG_SYS_CLOCK_EXISTS=n).
Consider enabling the system clock to apply the workaround.

At your own risk, you can suppress this warning by setting
CONFIG_SOC_NRF53_ANOMALY_160_WORKAROUND_NEEDED=n.

-- Configuring done
-- Generating done
-- Build files have been written to: C:/nrf/empty_app_core/build
←[92m-- west build: building application
[2/106] Generating include/generated/version.h
-- Zephyr version: 3.4.99 (C:/ncs/v2.5.1/zephyr), build: v3.4.99-ncs1-1
[106/106] Linking C executable zephyr\zephyr.elf
Memory region Used Size Region Size %age Used
FLASH: 5272 B 1 MB 0.50%
RAM: 3316 B 448 KB 0.72%
IDT_LIST: 0 GB 2 KB 0.00%
PS C:\nrf\empty_app_core> west flash -d build
-- west flash: rebuilding
ninja: no work to do.
-- west flash: using runner nrfjprog
There are multiple boards connected.
1. 1050025410
2. 261010601
3. 682497942
Please select one with desired serial number (1-3): 1
-- runners.nrfjprog: Flashing file: build\zephyr\zephyr.hex
[ #################### ] 0.272s | Erase file - Done erasing
[ #################### ] 0.062s | Program file - Done programming
[ #################### ] 0.035s | Verify file - Done verifying
Applying pin reset.
-- runners.nrfjprog: Board with serial number 1050025410 flashed successfully.

flash nrf5340, all LEDs on

---

PS C:\nrf\blinky_NET> west build -b nrf5340dk_nrf5340_cpunet -p

-- west build: generating a build system
Loading Zephyr default modules (Zephyr base).
-- Application: C:/nrf/blinky_NET
-- CMake version: 3.20.5
-- Using NCS Toolchain 2.5.20231017.848171396279 for building. (C:/ncs/toolchains/c57af46cb7/cmake)
CMake Deprecation Warning at C:/ncs/v2.5.1/zephyr/cmake/modules/FindDeprecated.cmake:121 (message):
'PYTHON_PREFER' variable is deprecated. Please use Python3_EXECUTABLE
instead.
Call Stack (most recent call first):
C:/ncs/v2.5.1/zephyr/cmake/modules/python.cmake:16 (find_package)
C:/ncs/v2.5.1/zephyr/cmake/modules/zephyr_default.cmake:129 (include)
C:/ncs/v2.5.1/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
C:/ncs/v2.5.1/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
CMakeLists.txt:4 (find_package)

-- Found Python3: C:/ncs/toolchains/c57af46cb7/opt/bin/python.exe (found suitable version "3.8.2", minimum required is "3.8") found components: Interpreter
-- Cache files will be written to: C:/ncs/v2.5.1/zephyr/.cache
-- Zephyr version: 3.4.99 (C:/ncs/v2.5.1/zephyr)
-- Found west (found suitable version "1.1.0", minimum required is "0.14.0")
-- Board: nrf5340dk_nrf5340_cpunet
-- Found host-tools: zephyr 0.16.1 (C:/ncs/toolchains/c57af46cb7/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.16.1 (C:/ncs/toolchains/c57af46cb7/opt/zephyr-sdk)
-- Found Dtc: C:/ncs/toolchains/c57af46cb7/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")
-- Found BOARD.dts: C:/ncs/v2.5.1/zephyr/boards/arm/nrf5340dk_nrf5340/nrf5340dk_nrf5340_cpunet.dts
-- Generated zephyr.dts: C:/nrf/blinky_NET/build/zephyr/zephyr.dts
-- Generated devicetree_generated.h: C:/nrf/blinky_NET/build/zephyr/include/generated/devicetree_generated.h
-- Including generated dts.cmake file: C:/nrf/blinky_NET/build/zephyr/dts.cmake
Parsing C:/ncs/v2.5.1/zephyr/Kconfig
Loaded configuration 'C:/ncs/v2.5.1/zephyr/boards/arm/nrf5340dk_nrf5340/nrf5340dk_nrf5340_cpunet_defconfig'
Merged configuration 'C:/nrf/blinky_NET/prj.conf'
Configuration saved to 'C:/nrf/blinky_NET/build/zephyr/.config'
Kconfig header saved to 'C:/nrf/blinky_NET/build/zephyr/include/generated/autoconf.h'
-- Found GnuLd: c:/ncs/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe (found version "2.38")
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: C:/ncs/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc.exe
-- Configuring done
-- Generating done
-- Build files have been written to: C:/nrf/blinky_NET/build
←[92m-- west build: building application
[2/134] Generating include/generated/version.h
-- Zephyr version: 3.4.99 (C:/ncs/v2.5.1/zephyr), build: v3.4.99-ncs1-1
[134/134] Linking C executable zephyr\zephyr.elf
Memory region Used Size Region Size %age Used
FLASH: 19256 B 256 KB 7.35%
RAM: 4116 B 64 KB 6.28%
SRAM1: 0 GB 64 KB 0.00%
IDT_LIST: 0 GB 2 KB 0.00%
PS C:\nrf\blinky_NET> west flash -d build
-- west flash: rebuilding
ninja: no work to do.
-- west flash: using runner nrfjprog
There are multiple boards connected.
1. 1050025410
2. 261010601
3. 682497942
Please select one with desired serial number (1-3): 1
-- runners.nrfjprog: Flashing file: build\zephyr\zephyr.hex
[ ###### ] 0.000s | Erase file - Check image
[ ##### ] 0.000s | Check image validity - Initialize device info
[ ########## ] 0.000s | Check image validity - Check region 0 settings
[ ############### ] 0.000s | Check image validity - block 1 of 2
[ #################### ] 0.061s | Check image validity - Finished
[ ############# ] 0.000s | Erase file - Erasing
[ ########## ] 0.000s | Erasing non-volatile memory - block 1 of 1
[ #################### ] 0.000s | Erasing non-volatile memory - Erase successful
[ #################### ] 1.141s | Erase file - Done erasing

[ ###### ] 0.000s | Program file - Checking image
[ ##### ] 0.000s | Check image validity - Initialize device info
[ ########## ] 0.000s | Check image validity - Check region 0 settings
[ ############### ] 0.450s | Check image validity - block 1 of 2
[ #################### ] 0.012s | Check image validity - Finished
[ ############# ] 0.000s | Program file - Programming
[ ########## ] 0.000s | Programming image - block 1 of 1
[ #################### ] 0.000s | Programming image - Write successful
[ #################### ] 0.134s | Program file - Done programming

[ ###### ] 0.000s | Verify file - Check image
[ ##### ] 0.000s | Check image validity - Initialize device info
[ ########## ] 0.000s | Check image validity - Check region 0 settings
[ ############### ] 0.507s | Check image validity - block 1 of 2
[ #################### ] 0.011s | Check image validity - Finished
[ ############# ] 0.000s | Verify file - Verifying
[ ########## ] 0.000s | Verifying image - block 1 of 1
[ #################### ] 0.000s | Verifying image - Verify successful
[ #################### ] 0.130s | Verify file - Done verifying

Applying pin reset.
-- runners.nrfjprog: Board with serial number 1050025410 flashed successfully.

led0 blinks

[mej7000]

PS C:\nrf\esb_ptx_5340> west build -b nrf5340dk_nrf5340_cpunet -p

-- west build: generating a build system
Loading Zephyr default modules (Zephyr base).
-- Application: C:/nrf/esb_ptx_5340
-- CMake version: 3.20.5
-- Using NCS Toolchain 2.5.20231017.848171396279 for building. (C:/ncs/toolchains/c57af46cb7/cmake)
CMake Deprecation Warning at C:/ncs/v2.5.1/zephyr/cmake/modules/FindDeprecated.cmake:121 (message):
'PYTHON_PREFER' variable is deprecated. Please use Python3_EXECUTABLE
instead.
Call Stack (most recent call first):
C:/ncs/v2.5.1/zephyr/cmake/modules/python.cmake:16 (find_package)
C:/ncs/v2.5.1/zephyr/cmake/modules/zephyr_default.cmake:129 (include)
C:/ncs/v2.5.1/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
C:/ncs/v2.5.1/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
CMakeLists.txt:8 (find_package)

-- Found Python3: C:/ncs/toolchains/c57af46cb7/opt/bin/python.exe (found suitable version "3.8.2", minimum required is "3.8") found components: Interpreter
-- Cache files will be written to: C:/ncs/v2.5.1/zephyr/.cache
-- Zephyr version: 3.4.99 (C:/ncs/v2.5.1/zephyr)
-- Found west (found suitable version "1.1.0", minimum required is "0.14.0")
-- Board: nrf5340dk_nrf5340_cpunet
-- Found host-tools: zephyr 0.16.1 (C:/ncs/toolchains/c57af46cb7/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.16.1 (C:/ncs/toolchains/c57af46cb7/opt/zephyr-sdk)
-- Found Dtc: C:/ncs/toolchains/c57af46cb7/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")
-- Found BOARD.dts: C:/ncs/v2.5.1/zephyr/boards/arm/nrf5340dk_nrf5340/nrf5340dk_nrf5340_cpunet.dts
-- Generated zephyr.dts: C:/nrf/esb_ptx_5340/build/zephyr/zephyr.dts
-- Generated devicetree_generated.h: C:/nrf/esb_ptx_5340/build/zephyr/include/generated/devicetree_generated.h
-- Including generated dts.cmake file: C:/nrf/esb_ptx_5340/build/zephyr/dts.cmake

warning: BOARD_ENABLE_CPUNET (defined at
C:/ncs/v2.5.1/zephyr/boards/arm/nrf5340dk_nrf5340/Kconfig:23) was assigned the value 'y' but got the
value 'n'. Check these unsatisfied dependencies: (BOARD_NRF5340DK_NRF5340_CPUAPP ||
BOARD_NRF5340DK_NRF5340_CPUAPP_NS) (=n). See
docs.zephyrproject.org/.../kconfig.html and/or look up
BOARD_ENABLE_CPUNET in the menuconfig/guiconfig interface. The Application Development Primer,
Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be
helpful too.

Parsing C:/nrf/esb_ptx_5340/Kconfig
Loaded configuration 'C:/ncs/v2.5.1/zephyr/boards/arm/nrf5340dk_nrf5340/nrf5340dk_nrf5340_cpunet_defconfig'
Merged configuration 'C:/nrf/esb_ptx_5340/prj.conf'
Configuration saved to 'C:/nrf/esb_ptx_5340/build/zephyr/.config'
Kconfig header saved to 'C:/nrf/esb_ptx_5340/build/zephyr/include/generated/autoconf.h'
-- Found GnuLd: c:/ncs/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe (found version "2.38")
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: C:/ncs/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc.exe
CMake Warning at C:/ncs/v2.5.1/zephyr/CMakeLists.txt:1958 (message):
__ASSERT() statements are globally ENABLED

-- Configuring done
-- Generating done
-- Build files have been written to: C:/nrf/esb_ptx_5340/build
←[92m-- west build: building application
[2/143] Generating include/generated/version.h
-- Zephyr version: 3.4.99 (C:/ncs/v2.5.1/zephyr), build: v3.4.99-ncs1-1
[143/143] Linking C executable zephyr\zephyr.elf
Memory region Used Size Region Size %age Used
FLASH: 34898 B 256 KB 13.31%
RAM: 5340 B 64 KB 8.15%
SRAM1: 0 GB 64 KB 0.00%
IDT_LIST: 0 GB 2 KB 0.00%
PS C:\nrf\esb_ptx_5340>

build is successful, but I get a warning from CONFIG_BOARD_ENABLE_CPUNET=y

CONFIG_BOARD_ENABLE_CPUNET was assigned the value y, but got the value n. Missing dependencies:
BOARD_NRF5340DK_NRF5340_CPUAPP || BOARD_NRF5340DK_NRF5340_CPUAPP_NS
NRF53 Network MCU

Type: bool

Value: n

This option enables releasing the Network 'force off' signal, which as a consequence will power up the Network MCU during system boot. Additionally, the option allocates GPIO pins that will be used by UARTE of the Network MCU. Note: GPIO pin allocation can only be configured by the secure Application MCU firmware, so when this option is used with the non-secure version of the board, the application needs to take into consideration, that the secure firmware image must already have configured GPIO allocation for the Network MCU.

Value has changed in the build