The code written in the webinar for "developing Bluetooth Low Energy products using the nRF Connect SDK" does not work on my nRF5340DK

RE: The code written in the webinar for "developing Bluetooth Low Energy products using the nRF Connect SDK" does not work on my nRF5340DK

ByMuhendis — Mon, 20 Feb 2023 10:16:28 GMT

Hi,

I found what the problem was.
The first Semaphore number was entered incorrectly,
Where should be '0' is given as '1'.
Actually below.

Thank you for your interest and help.

Best regards,
Cemal

RE: The code written in the webinar for "developing Bluetooth Low Energy products using the nRF Connect SDK" does not work on my nRF5340DK

Marte Myrvold — Fri, 17 Feb 2023 09:26:09 GMT

Hi,

Do you have the complete log of when it fails?

Best regards,
Marte

RE: The code written in the webinar for "developing Bluetooth Low Energy products using the nRF Connect SDK" does not work on my nRF5340DK

ByMuhendis — Thu, 16 Feb 2023 11:04:53 GMT

When I program the program separately, I program the network kernel first. File 'hci_rpmsg' in 'build' directory, under 'Application' tab. This compilation completes without any problems.

When I program the application kernel, I get the following error on my terminal screen:

ninja: error: rebuild 'build.ninja': subcommand failed
FATAL ERROR: command exited with status 1: 'c:\ncs\v1.7.1\toolchain\opt\bin\cmake.EXE' --build 'c:\NordicProjects\bluetooth_remote\build'

best regards,

Cemal

RE: The code written in the webinar for "developing Bluetooth Low Energy products using the nRF Connect SDK" does not work on my nRF5340DK

Marte Myrvold — Thu, 16 Feb 2023 11:04:44 GMT

The network core sample is built as a child image of your application in your log. You can find this by looking for the following lines:

=== child image hci_rpmsg - CPUNET begin ===

=== child image hci_rpmsg - CPUNET end ===

Everything between these lines is the child image being built.

I also see that both cores are programmed. So when you use the build and flash actions in VS Code, you are automatically building the firmware for and programming both cores.

Are you still having issues with enabling Bluetooth?

Best regards,

Marte

RE: The code written in the webinar for "developing Bluetooth Low Energy products using the nRF Connect SDK" does not work on my nRF5340DK

ByMuhendis — Thu, 16 Feb 2023 08:47:13 GMT

Hello Marte,

The build directory under the 'Applications' tab in VS Code is as in the image below.

I compile the program and upload it to my nRF card as seen in the picture I added below.

The code in the CMakeList.txt file is as follows. I don't know how to make changes.

The output of the program is below.

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

Building bluetooth_remote
west build --build-dir c:\NordicProjects\bluetooth_remote\build c:\NordicProjects\bluetooth_remote

[0/1] Re-running CMake...
Including boilerplate (Zephyr base (cached)): C:/ncs/v1.7.1/zephyr/cmake/app/boilerplate.cmake { RED COLOR}
-- Application: C:/NordicProjects/bluetooth_remote
-- Zephyr version: 2.6.99 (C:/ncs/v1.7.1/zephyr), build: v2.6.99-ncs1-1
-- Found west (found suitable version "0.11.1", minimum required is "0.7.1")
-- Board: nrf5340dk_nrf5340_cpuapp
-- Cache files will be written to: C:/ncs/v1.7.1/zephyr/.cache
-- Found dtc: C:/ncs/v1.7.1/toolchain/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")
-- Found toolchain: gnuarmemb (c:/ncs/v1.7.1/toolchain/opt)
-- Found BOARD.dts: C:/ncs/v1.7.1/zephyr/boards/arm/nrf5340dk_nrf5340/nrf5340dk_nrf5340_cpuapp.dts
-- Generated zephyr.dts: C:/NordicProjects/bluetooth_remote/build/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: C:/NordicProjects/bluetooth_remote/build/zephyr/include/generated/devicetree_unfixed.h
-- Generated device_extern.h: C:/NordicProjects/bluetooth_remote/build/zephyr/include/generated/device_extern.h
-- Including generated dts.cmake file: C:/NordicProjects/bluetooth_remote/build/zephyr/dts.cmake
Parsing C:/ncs/v1.7.1/zephyr/Kconfig
Loaded configuration 'C:/NordicProjects/bluetooth_remote/build/zephyr/.config'
No change to configuration in 'C:/NordicProjects/bluetooth_remote/build/zephyr/.config'
No change to Kconfig header in 'C:/NordicProjects/bluetooth_remote/build/zephyr/include/generated/autoconf.h'
Adding 'hci_rpmsg' firmware as child image since CONFIG_BT_RPMSG_NRF53 is set to 'y' { RED COLOR}

=== child image hci_rpmsg - CPUNET begin === { RED COLOR }
Including boilerplate (Zephyr base (cached)): C:/ncs/v1.7.1/zephyr/cmake/app/boilerplate.cmake { RED COLOR}
-- Application: C:/ncs/v1.7.1/zephyr/samples/bluetooth/hci_rpmsg
-- Zephyr version: 2.6.99 (C:/ncs/v1.7.1/zephyr), build: v2.6.99-ncs1-1
-- Found west (found suitable version "0.11.1", minimum required is "0.7.1")
-- Board: nrf5340dk_nrf5340_cpunet
-- Cache files will be written to: C:/ncs/v1.7.1/zephyr/.cache
-- Found dtc: C:/ncs/v1.7.1/toolchain/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")
-- Found toolchain: gnuarmemb (C:/ncs/v1.7.1/toolchain/opt)
-- Found BOARD.dts: C:/ncs/v1.7.1/zephyr/boards/arm/nrf5340dk_nrf5340/nrf5340dk_nrf5340_cpunet.dts
-- Generated zephyr.dts: C:/NordicProjects/bluetooth_remote/build/hci_rpmsg/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: C:/NordicProjects/bluetooth_remote/build/hci_rpmsg/zephyr/include/generated/devicetree_unfixed.h
-- Generated device_extern.h: C:/NordicProjects/bluetooth_remote/build/hci_rpmsg/zephyr/include/generated/device_extern.h
-- Including generated dts.cmake file: C:/NordicProjects/bluetooth_remote/build/hci_rpmsg/zephyr/dts.cmake
Parsing C:/ncs/v1.7.1/zephyr/Kconfig
Loaded configuration 'C:/NordicProjects/bluetooth_remote/build/hci_rpmsg/zephyr/.config'
No change to configuration in 'C:/NordicProjects/bluetooth_remote/build/hci_rpmsg/zephyr/.config'
No change to Kconfig header in 'C:/NordicProjects/bluetooth_remote/build/hci_rpmsg/zephyr/include/generated/autoconf.h'
-- libmetal version: 1.0.0 (C:/ncs/v1.7.1/zephyr/samples/bluetooth/hci_rpmsg)
-- Build type: { RED COLOR}
-- Host: Windows/AMD64 { RED COLOR}
-- Target: Generic/arm   { RED COLOR}
-- Machine: cortexm { RED COLOR}
-- open-amp version: 1.0.0 (C:/ncs/v1.7.1/modules/lib/open-amp/open-amp)
-- Host: Windows/AMD64 { RED COLOR}
-- Target: Generic/arm { RED COLOR}
-- Machine: cortexm   { RED COLOR}
-- C_FLAGS : -Wall -Wextra   { RED COLOR}
-- Configuring done
-- Generating done
-- Build files have been written to: C:/NordicProjects/bluetooth_remote/build/hci_rpmsg
=== child image hci_rpmsg - CPUNET end === { RED COLOR}

-- libmetal version: 1.0.0 (C:/NordicProjects/bluetooth_remote)
-- Build type: { RED COLOR}
-- Host: Windows/AMD64 { RED COLOR}
-- Target: Generic/arm { RED COLOR}
-- Machine: cortexm { RED COLOR}
-- open-amp version: 1.0.0 (C:/ncs/v1.7.1/modules/lib/open-amp/open-amp)
-- Host: Windows/AMD64 { RED COLOR}
-- Target: Generic/arm   { RED COLOR}
-- Machine: cortexm   { RED COLOR}
-- C_FLAGS : -Wall -Wextra   { RED COLOR}
CMake Warning at C:/ncs/v1.7.1/zephyr/CMakeLists.txt:1612 (message):
__ASSERT() statements are globally ENABLED   { RED COLOR}

-- Configuring done
-- Generating done
-- Build files have been written to: C:/NordicProjects/bluetooth_remote/build
[0/179] Performing build step for 'hci_rpmsg_subimage'
[1/162] Generating misc/generated/syscalls.json, misc/generated/struct_tags.json
[2/162] Building C object zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj
[3/162] Generating include/generated/offsets.h
[4/162] Building ASM object zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/swap_helper.S.obj
[5/162] Building C object zephyr/arch/common/CMakeFiles/isr_tables.dir/isr_tables.c.obj
[6/162] Building C object zephyr/arch/common/CMakeFiles/arch__common.dir/sw_isr_common.c.obj
[7/162] Building C object zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/swap.c.obj
[8/162] Building C object zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/irq_manage.c.obj
[9/162] Generating linker_zephyr_prebuilt.cmd
[10/162] Building C object zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/thread.c.obj
[11/162] Building C object zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/nmi.c.obj
[12/162] Building ASM object zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/isr_wrapper.S.obj
[13/162] Building C object zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/fatal.c.obj
[14/162] Building C object zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/prep_c.c.obj
[15/162] Linking C static library zephyr\arch\common\libisr_tables.a
[16/162] Building ASM object zephyr/arch/arch/arm/core/aarch32/cortex_m/CMakeFiles/arch__arm__core__aarch32__cortex_m.dir/reset.S.obj
[17/162] Building C object zephyr/arch/arch/arm/core/aarch32/cortex_m/CMakeFiles/arch__arm__core__aarch32__cortex_m.dir/irq_init.c.obj
[18/162] Building ASM object zephyr/arch/arch/arm/core/aarch32/cortex_m/CMakeFiles/arch__arm__core__aarch32__cortex_m.dir/exc_exit.S.obj
[19/162] Building C object zephyr/arch/arch/arm/core/aarch32/cortex_m/CMakeFiles/arch__arm__core__aarch32__cortex_m.dir/scb.c.obj
[20/162] Building C object zephyr/arch/arch/arm/core/aarch32/cortex_m/CMakeFiles/arch__arm__core__aarch32__cortex_m.dir/fault.c.obj
[21/162] Linking C static library zephyr\arch\common\libarch__common.a
[22/162] Linking C static library zephyr\arch\arch\arm\core\aarch32\libarch__arm__core__aarch32.a
[23/162] Building C object zephyr/arch/arch/arm/core/aarch32/cortex_m/CMakeFiles/arch__arm__core__aarch32__cortex_m.dir/debug.c.obj
[24/162] Building C object zephyr/arch/arch/arm/core/aarch32/cortex_m/CMakeFiles/arch__arm__core__aarch32__cortex_m.dir/fpu.c.obj
[25/162] Building C object zephyr/arch/arch/arm/core/aarch32/cortex_m/CMakeFiles/arch__arm__core__aarch32__cortex_m.dir/thread_abort.c.obj
[26/162] Building C object zephyr/arch/arch/arm/core/aarch32/cortex_m/cmse/CMakeFiles/arch__arm__core__aarch32__cortex_m__cmse.dir/arm_core_cmse.c.obj
[27/162] Building C object zephyr/lib/libc/minimal/CMakeFiles/lib__libc__minimal.dir/source/stdlib/exit.c.obj
[28/162] Building C object zephyr/arch/arch/arm/core/aarch32/mpu/CMakeFiles/arch__arm__core__aarch32__mpu.dir/arm_core_mpu.c.obj
[29/162] Building C object zephyr/lib/libc/minimal/CMakeFiles/lib__libc__minimal.dir/source/stdlib/abort.c.obj
[30/162] Building C object zephyr/arch/arch/arm/core/aarch32/mpu/CMakeFiles/arch__arm__core__aarch32__mpu.dir/arm_mpu.c.obj
[31/162] Linking C static library zephyr\arch\arch\arm\core\aarch32\cortex_m\libarch__arm__core__aarch32__cortex_m.a
[32/162] Building C object zephyr/lib/posix/CMakeFiles/lib__posix.dir/nanosleep.c.obj
[33/162] Building C object zephyr/lib/posix/CMakeFiles/lib__posix.dir/pthread_common.c.obj
[34/162] Building C object zephyr/lib/libc/minimal/CMakeFiles/lib__libc__minimal.dir/source/stdlib/malloc.c.obj
[35/162] Linking C static library zephyr\arch\arch\arm\core\aarch32\cortex_m\cmse\libarch__arm__core__aarch32__cortex_m__cmse.a
[36/162] Building C object zephyr/soc/arm/common/cortex_m/CMakeFiles/soc__arm__common__cortex_m.dir/arm_mpu_regions.c.obj
[37/162] Linking C static library zephyr\arch\arch\arm\core\aarch32\mpu\libarch__arm__core__aarch32__mpu.a
[38/162] Building C object modules/hal_nordic/nrfx/CMakeFiles/modules__hal_nordic__nrfx.dir/C_/ncs/v1.7.1/modules/hal/nordic/nrfx/drivers/src/nrfx_ipc.c.obj
[39/162] Building C object modules/hal_nordic/nrfx/CMakeFiles/modules__hal_nordic__nrfx.dir/nrfx_glue.c.obj
[40/162] Linking C static library zephyr\lib\posix\liblib__posix.a
[41/162] Linking C static library zephyr\lib\libc\minimal\liblib__libc__minimal.a
[42/162] Linking C static library zephyr\soc\arm\common\cortex_m\libsoc__arm__common__cortex_m.a
[43/162] Building C object modules/hal_nordic/nrfx/CMakeFiles/modules__hal_nordic__nrfx.dir/C_/ncs/v1.7.1/modules/hal/nordic/nrfx/drivers/src/nrfx_dppi.c.obj
[44/162] Building C object modules/libmetal/libmetal/lib/CMakeFiles/metal.dir/device.c.obj
[45/162] Building C object modules/libmetal/libmetal/lib/CMakeFiles/metal.dir/irq.c.obj
[46/162] Building C object modules/libmetal/libmetal/lib/CMakeFiles/metal.dir/dma.c.obj
[47/162] Building C object modules/hal_nordic/nrfx/CMakeFiles/modules__hal_nordic__nrfx.dir/C_/ncs/v1.7.1/modules/hal/nordic/nrfx/drivers/src/nrfx_gpiote.c.obj
[48/162] Building C object modules/libmetal/libmetal/lib/CMakeFiles/metal.dir/io.c.obj
[49/162] Building C object modules/libmetal/libmetal/lib/CMakeFiles/metal.dir/shmem.c.obj
[50/162] Building C object modules/libmetal/libmetal/lib/CMakeFiles/metal.dir/system/zephyr/alloc.c.obj
[51/162] Building C object modules/libmetal/libmetal/lib/CMakeFiles/metal.dir/softirq.c.obj
[52/162] Building C object modules/libmetal/libmetal/lib/CMakeFiles/metal.dir/system/zephyr/device.c.obj
[53/162] Building C object modules/libmetal/libmetal/lib/CMakeFiles/metal.dir/system/zephyr/condition.c.obj
[54/162] Linking C static library modules\hal_nordic\nrfx\libmodules__hal_nordic__nrfx.a
[55/162] Building C object modules/libmetal/libmetal/lib/CMakeFiles/metal.dir/system/zephyr/cortexm/sys.c.obj
[56/162] Building C object modules/libmetal/libmetal/lib/CMakeFiles/metal.dir/system/zephyr/irq.c.obj
[57/162] Building C object modules/libmetal/libmetal/lib/CMakeFiles/metal.dir/system/zephyr/time.c.obj
[58/162] Building C object modules/libmetal/libmetal/lib/CMakeFiles/metal.dir/system/zephyr/shmem.c.obj
[59/162] Building C object modules/libmetal/libmetal/lib/CMakeFiles/metal.dir/system/zephyr/log.c.obj
[60/162] Building C object modules/libmetal/libmetal/lib/CMakeFiles/metal.dir/system/zephyr/init.c.obj
[61/162] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/fdtable.c.obj
[62/162] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/thread_entry.c.obj
[63/162] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/notify.c.obj
[64/162] Building C object CMakeFiles/app.dir/src/main.c.obj
[65/162] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/sem.c.obj
[66/162] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/rb.c.obj
[67/162] Linking C static library modules\libmetal\libmetal\lib\libmetal.a
[68/162] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/printk.c.obj
[69/162] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/onoff.c.obj
[70/162] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/heap.c.obj
[71/162] Linking C static library app\libapp.a
[72/162] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/reboot.c.obj
[73/162] Building C object zephyr/CMakeFiles/zephyr.dir/soc/arm/nordic_nrf/nrf53/soc.c.obj
[74/162] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/bitarray.c.obj
[75/162] Building C object zephyr/CMakeFiles/zephyr.dir/soc/arm/nordic_nrf/validate_enabled_instances.c.obj
[76/162] Building C object zephyr/CMakeFiles/zephyr.dir/soc/arm/nordic_nrf/validate_base_addresses.c.obj
[77/162] Building C object zephyr/CMakeFiles/zephyr.dir/drivers/console/uart_console.c.obj
[78/162] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/heap-validate.c.obj
[79/162] Building C object zephyr/CMakeFiles/zephyr.dir/subsys/ipc/rpmsg_service/rpmsg_backend.c.obj
[80/162] Building C object zephyr/CMakeFiles/zephyr.dir/subsys/tracing/tracing_none.c.obj
[81/162] Building C object zephyr/CMakeFiles/zephyr.dir/subsys/ipc/rpmsg_service/rpmsg_service.c.obj
[82/162] Building C object zephyr/CMakeFiles/zephyr.dir/C_/ncs/v1.7.1/nrf/subsys/partition_manager/flash_map_partition_manager.c.obj
[83/162] Building C object zephyr/CMakeFiles/zephyr.dir/drivers/timer/nrf_rtc_timer.c.obj
[84/162] Building C object zephyr/CMakeFiles/zephyr.dir/drivers/timer/sys_clock_init.c.obj
[85/162] Building C object zephyr/CMakeFiles/zephyr.dir/drivers/clock_control/clock_control_nrf.c.obj
[86/162] Building C object modules/open-amp/open-amp/lib/CMakeFiles/open_amp.dir/virtio/virtio.c.obj
[87/162] Building C object modules/open-amp/open-amp/lib/CMakeFiles/open_amp.dir/virtio/virtqueue.c.obj
[88/162] Building C object modules/open-amp/open-amp/lib/CMakeFiles/open_amp.dir/rpmsg/rpmsg_virtio.c.obj
[89/162] Building C object modules/open-amp/open-amp/lib/CMakeFiles/open_amp.dir/remoteproc/remoteproc_virtio.c.obj
[90/162] Linking C static library zephyr\libzephyr.a
[91/162] Building C object modules/open-amp/open-amp/lib/CMakeFiles/open_amp.dir/rpmsg/rpmsg.c.obj
[92/162] Building C object modules/open-amp/open-amp/lib/CMakeFiles/open_amp.dir/remoteproc/elf_loader.c.obj
[93/162] Building C object modules/open-amp/open-amp/lib/CMakeFiles/open_amp.dir/remoteproc/remoteproc.c.obj
[94/162] Building C object modules/open-amp/open-amp/lib/CMakeFiles/open_amp.dir/remoteproc/rsc_table_parser.c.obj
[95/162] Building C object zephyr/kernel/CMakeFiles/kernel.dir/banner.c.obj
[96/162] Building C object zephyr/kernel/CMakeFiles/kernel.dir/device.c.obj
[97/162] Building C object zephyr/kernel/CMakeFiles/kernel.dir/fatal.c.obj
[98/162] Building C object zephyr/kernel/CMakeFiles/kernel.dir/thread.c.obj
[99/162] Building C object zephyr/kernel/CMakeFiles/kernel.dir/init.c.obj
[100/162] Building C object zephyr/kernel/CMakeFiles/kernel.dir/errno.c.obj
[101/162] Linking C static library modules\open-amp\open-amp\lib\libopen_amp.a
[102/162] Building C object zephyr/kernel/CMakeFiles/kernel.dir/mem_slab.c.obj
[103/162] Building C object zephyr/kernel/CMakeFiles/kernel.dir/mailbox.c.obj
[104/162] Building C object zephyr/kernel/CMakeFiles/kernel.dir/kheap.c.obj
[105/162] Building C object zephyr/kernel/CMakeFiles/kernel.dir/mutex.c.obj
[106/162] Building C object zephyr/kernel/CMakeFiles/kernel.dir/msg_q.c.obj
[107/162] Building C object zephyr/kernel/CMakeFiles/kernel.dir/idle.c.obj
[108/162] Building C object zephyr/kernel/CMakeFiles/kernel.dir/pipes.c.obj
[109/162] Building C object zephyr/kernel/CMakeFiles/kernel.dir/condvar.c.obj
[110/162] Building C object zephyr/kernel/CMakeFiles/kernel.dir/sem.c.obj
[111/162] Building C object zephyr/kernel/CMakeFiles/kernel.dir/queue.c.obj
[112/162] Building C object zephyr/kernel/CMakeFiles/kernel.dir/work.c.obj
[113/162] Building C object zephyr/kernel/CMakeFiles/kernel.dir/sched.c.obj
[114/162] Building C object zephyr/kernel/CMakeFiles/kernel.dir/stack.c.obj
[115/162] Building C object zephyr/kernel/CMakeFiles/kernel.dir/system_work_q.c.obj
[116/162] Building C object zephyr/kernel/CMakeFiles/kernel.dir/xip.c.obj
[117/162] Building C object zephyr/kernel/CMakeFiles/kernel.dir/timer.c.obj
[118/162] Building C object zephyr/kernel/CMakeFiles/kernel.dir/poll.c.obj
[119/162] Building C object zephyr/subsys/bluetooth/common/CMakeFiles/subsys__bluetooth__common.dir/log.c.obj
[120/162] Building C object zephyr/kernel/CMakeFiles/kernel.dir/mempool.c.obj
[121/162] Building C object zephyr/subsys/bluetooth/common/CMakeFiles/subsys__bluetooth__common.dir/rpa.c.obj
[122/162] Building C object zephyr/kernel/CMakeFiles/kernel.dir/timeout.c.obj
[123/162] Building C object zephyr/subsys/bluetooth/common/CMakeFiles/subsys__bluetooth__common.dir/dummy.c.obj
[124/162] Building C object zephyr/subsys/bluetooth/host/CMakeFiles/subsys__bluetooth__host.dir/hci_raw.c.obj
[125/162] Building C object zephyr/subsys/bluetooth/host/CMakeFiles/subsys__bluetooth__host.dir/hci_common.c.obj
[126/162] Building C object zephyr/subsys/bluetooth/host/CMakeFiles/subsys__bluetooth__host.dir/hci_ecc.c.obj
[127/162] Linking C static library zephyr\subsys\bluetooth\common\libsubsys__bluetooth__common.a
[128/162] Linking C static library zephyr\kernel\libkernel.a
[129/162] Building C object zephyr/subsys/random/CMakeFiles/subsys__random.dir/rand32_entropy_device.c.obj
[130/162] Building C object zephyr/subsys/net/CMakeFiles/subsys__net.dir/buf.c.obj
[131/162] Linking C static library zephyr\subsys\bluetooth\host\libsubsys__bluetooth__host.a
[132/162] Building C object zephyr/drivers/gpio/CMakeFiles/drivers__gpio.dir/gpio_nrfx.c.obj
[133/162] Linking C static library zephyr\subsys\random\libsubsys__random.a
[134/162] Building C object zephyr/drivers/serial/CMakeFiles/drivers__serial.dir/uart_nrfx_uarte.c.obj
[135/162] Building C object zephyr/drivers/entropy/CMakeFiles/drivers__entropy.dir/entropy_nrf5.c.obj
[136/162] Linking C static library zephyr\subsys\net\libsubsys__net.a
[137/162] Building C object zephyr/drivers/ipm/CMakeFiles/drivers__ipm.dir/ipm_nrfx_ipc.c.obj
[138/162] Linking C static library zephyr\drivers\gpio\libdrivers__gpio.a
[139/162] Building C object modules/nrf/lib/multithreading_lock/CMakeFiles/..__nrf__lib__multithreading_lock.dir/multithreading_lock.c.obj
[140/162] Linking C static library zephyr\drivers\serial\libdrivers__serial.a
[141/162] Building C object modules/nrf/lib/fatal_error/CMakeFiles/..__nrf__lib__fatal_error.dir/fatal_error.c.obj
[142/162] Linking C static library zephyr\drivers\ipm\libdrivers__ipm.a
[143/162] Linking C static library zephyr\drivers\entropy\libdrivers__entropy.a
[144/162] Linking C static library modules\nrf\lib\multithreading_lock\lib..__nrf__lib__multithreading_lock.a
[145/162] Building C object modules/nrf/subsys/bluetooth/controller/CMakeFiles/..__nrf__subsys__bluetooth__controller.dir/hci_driver.c.obj
[146/162] Building C object modules/nrf/subsys/mpsl/init/CMakeFiles/..__nrf__subsys__mpsl__init.dir/mpsl_init.c.obj
[147/162] Building C object modules/nrf/subsys/bluetooth/controller/CMakeFiles/..__nrf__subsys__bluetooth__controller.dir/hci_internal.c.obj
[148/162] Building C object modules/nrf/subsys/bluetooth/controller/CMakeFiles/..__nrf__subsys__bluetooth__controller.dir/crypto.c.obj
[149/162] Linking C static library modules\nrf\lib\fatal_error\lib..__nrf__lib__fatal_error.a
[150/162] Building C object modules/nrf/drivers/mpsl/clock_control/CMakeFiles/..__nrf__drivers__mpsl__clock_control.dir/nrfx_clock_mpsl.c.obj
[151/162] Linking C static library modules\nrf\subsys\mpsl\init\lib..__nrf__subsys__mpsl__init.a
[152/162] Linking C static library modules\nrf\drivers\mpsl\clock_control\lib..__nrf__drivers__mpsl__clock_control.a
[153/162] Linking C static library modules\nrf\subsys\bluetooth\controller\lib..__nrf__subsys__bluetooth__controller.a
[154/162] Linking C executable zephyr\zephyr_prebuilt.elf

[155/162] Generating linker.cmd
[156/162] Generating isr_tables.c, isrList.bin
[157/162] Generating dev_handles.c
[158/162] Building C object zephyr/CMakeFiles/zephyr_final.dir/isr_tables.c.obj
[159/162] Building C object zephyr/CMakeFiles/zephyr_final.dir/dev_handles.c.obj
[160/162] Linking C executable zephyr\zephyr.elf
Memory region Used Size Region Size %age Used
FLASH: 160280 B 256 KB 61.14%
SRAM: 44672 B 64 KB 68.16%
SRAM1: 0 GB 64 KB 0.00%
IDT_LIST: 0 GB 2 KB 0.00%
[161/162] Generating zephyr/app.hex
[162/162] Generating zephyr/merged_CPUNET.hex
[168/179] Linking C executable zephyr\zephyr_prebuilt.elf

[174/179] Linking C executable zephyr\zephyr.elf
Memory region Used Size Region Size %age Used
FLASH: 103480 B 1 MB 9.87%
SRAM: 25006 B 448 KB 5.45%
IDT_LIST: 0 GB 2 KB 0.00%
[176/177] Generating zephyr/merged.hex
[177/177] Generating zephyr/merged_domains.hex
* Terminal will be reused by tasks, press any key to close it.

* Executing task: nRF Connect: Flash: bluetooth_remote/build (active)

Flashing build to nRF5340DK
west flash -d c:\NordicProjects\bluetooth_remote\build --skip-rebuild -r nrfjprog --snr 960147008

-- west flash: using runner nrfjprog
-- runners.nrfjprog: Flashing file: C:\NordicProjects\bluetooth_remote\build\zephyr\merged_domains.hex
-- runners.nrfjprog: C:\NordicProjects\bluetooth_remote\build\zephyr\merged_domains.hex targets both nRF53 coprocessors; splitting it into: C:\NordicProjects\bluetooth_remote\build\zephyr\GENERATED_CP_NETWORK_merged_domains.hex and C:\NordicProjects\bluetooth_remote\build\zephyr\GENERATED_CP_APPLICATION_merged_domains.hex
[ #################### ] 9.698s | Erase file - Done erasing
[ #################### ] 1.103s | Program file - Done programming
WARNING: A programming operation has been performed without --verify. { RED COLOR}
WARNING: Programming can fail without error. { RED COLOR}
[ #################### ] 3.931s | Erase file - Done erasing
[ #################### ] 0.736s | Program file - Done programming { RED COLOR}
WARNING: A programming operation has been performed without --verify. { RED COLOR}
WARNING: Programming can fail without error.
Applying pin reset.
-- runners.nrfjprog: Board with serial number 960147008 flashed successfully.
* Terminal will be reused by tasks, press any key to close it.

Best regards,

RE: The code written in the webinar for "developing Bluetooth Low Energy products using the nRF Connect SDK" does not work on my nRF5340DK

Marte Myrvold — Mon, 13 Feb 2023 08:19:07 GMT

Hi Cemal,

If your build directory under the 'Applications' tab in VS Code contains both the application core and the network core, as in the picture below, you will program both cores by selecting the 'Flash' action in VS Code.

In this case, the sample for the network core is added as a child image. This is done by default in the nRF Connect SDK samples.
You might have to add the network core sample as a child image in your project. To do this, edit the project CMakeLists.txt and add the child image. Make sure that the path to the network core sample is correct. Here is an example:

set(CHILD_IMAGE_NAME "hci_rpmsg")
set(CHILD_IMAGE_PATH "${ZEPHYR_BASE}/samples/bluetooth/hci_rpmsg")

add_child_image(
  NAME ${CHILD_IMAGE_NAME}
  SOURCE_DIR ${CHILD_IMAGE_PATH}
  DOMAIN "CPUNET"
  BOARD ${CONFIG_DOMAIN_CPUNET_BOARD}
  )

Best regards,
Marte

RE: The code written in the webinar for "developing Bluetooth Low Energy products using the nRF Connect SDK" does not work on my nRF5340DK

ByMuhendis — Mon, 13 Feb 2023 06:36:47 GMT

Hi Marte,

First off, I don't know how Cores are programmed at the same time. Can you help me with this?

Best regards,

Cemal

RE: The code written in the webinar for "developing Bluetooth Low Energy products using the nRF Connect SDK" does not work on my nRF5340DK

Marte Myrvold — Tue, 07 Feb 2023 10:00:43 GMT

Hi Cemal,

If you program the cores separately, you must first program the network core. Please try this and see if the issue persists.

Best regards,
Marte

RE: The code written in the webinar for "developing Bluetooth Low Energy products using the nRF Connect SDK" does not work on my nRF5340DK

ByMuhendis — Mon, 06 Feb 2023 10:33:57 GMT

Hello Marte,

I am programming the DK with VS Code, just like I learned in the tutorial video. I program the kernels individually: First I program by selecting nrf5340dk_nrf5340_cpuapp in VS Code, test, then I program and test by selecting nrf5340dk_nrf5340_cpunet.

Kind regards,
Cemal

RE: The code written in the webinar for "developing Bluetooth Low Energy products using the nRF Connect SDK" does not work on my nRF5340DK

Marte Myrvold — Mon, 06 Feb 2023 10:19:26 GMT

Hi,

How are you programming the DK? Are you using command line or VS Code. Do you program the cores separately, and if so, which core do you program first?

Best regards,
Marte

RE: The code written in the webinar for "developing Bluetooth Low Energy products using the nRF Connect SDK" does not work on my nRF5340DK

ByMuhendis — Sat, 04 Feb 2023 08:22:41 GMT

Even though I converted the nRF Connect SDK version to v1.7.1, the result did not change. I compiled the code and uploaded it to my nrf5340dk_nrf5340_cpuapp card. I can't see it broadcasting from my Android device. Output on terminal screen:
**Bootloding Zephyr OS build v2.6.99-ncs1-1 ***
[00:00:00.433,532] <inf> app: Hello World! nrf5340dk_nrf5340_cpuapp

[00:00:00.433,532] <inf> remote: Initializing bluetooth...
[00:00:00.440,185] <err> remote: Couldn't start advertising (err = -11)
[00:00:00.440,216] <err> app: bt_enable returned -11
[00:00:00.440,216] <inf> app: Running...

When I select and install the code nrf5340dk_nrf5340_cpunet, it shows up on my Android device, but no data is exchanged. Text in terminal:
*** Booting Zephyr OS build v2.6.99-ncs1-1 ***
[00:00:00.254,913] <inf> app: Hello World! nrf5340dk_nrf5340_cpuapp

[00:00:00.255,035] <inf> remote: Initializing bluetooth...

Version of my nRF5340 DK: 0.11.0

RE: The code written in the webinar for "developing Bluetooth Low Energy products using the nRF Connect SDK" does not work on my nRF5340DK

Marte Myrvold — Fri, 03 Feb 2023 07:46:02 GMT

Hi,

Based on your log, you are using nRF Connect SDK v2.2.0. The project in the webinar was developed in v1.7.1, so the failure to enable Bluetooth can be due to the project being incompatible with the version of nRF Connect SDK that you are using. I would recommend using the latest tagged release of the SDK, which in this case is v2.2.0, but in your case, I would recommend downloading v1.7.1 and building the project there to verify that it works with your board. After this, you can look into migrating the project to v2.2.0.

What version is your nRF5340 DK? There should be a sticker on the board, and the version number should be on the line directly under PCA10095.

Best regards,

Marte