Read debugs from nrf52840 dongle on nrf52840 DK

RE: Read debugs from nrf52840 dongle on nrf52840 DK

Naing — Thu, 21 Jul 2022 02:59:56 GMT

Hi Simon,

Yes you are right. I just uploaded the original bootloader and it's working fine now. Moreover, I've started to use SES as my IDE instead of VS code which gives me a better experience debugging. Thanks for all your help. I'd be happy if you would change this post back to public so other ppl can benefit as well, of course with my delivery details deleted.

[UPDATE] i have edited my reply of sensitive data. So no need to delete it anymore.

Cheers,

Naing

RE: Read debugs from nrf52840 dongle on nrf52840 DK

Simonr — Fri, 08 Jul 2022 08:09:38 GMT

Yes it should be possible to "save" the bootloader. I think what has happened is that you haven't built the application for the Dongle. That will set the BOARD_HAS_NRF5_BOOTLOADER=y for example, which will build the zephyr-app to start after the bootloader (at 0x1000). As long as you use NCS v1.7.0 or newer.

Best regards,

Simon

RE: Read debugs from nrf52840 dongle on nrf52840 DK

Naing — Thu, 07 Jul 2022 01:33:40 GMT

Ok that makes sense. I'll revert it back to production bootloader and try again. Is there a way to avoid removing the bootloader when flashing the program?

Regards

RE: Read debugs from nrf52840 dongle on nrf52840 DK

Simonr — Wed, 06 Jul 2022 13:35:50 GMT

It seems like the application built correctly, but that you erased the bootloader in the process, meaning that you have to revert it to the production bootloader as explained in the Dongle Programming tutorial to be able to program it again.

If it was indeed programmed with your "blinky_newest" application it should run that when powered. The reason you might not see any blinking LED is that the pin configured to blink is an unassigned GPIO on the Dongle compared to on one of your DKs.

Best regards,

Simon

RE: Read debugs from nrf52840 dongle on nrf52840 DK

Naing — Wed, 06 Jul 2022 06:59:59 GMT

Hi Simon, I just got a chance to try it out now. I did as you outlined here. I shorted SB47 and connected the dongle only with the dk's Debug Out Connector. When I turn it on, it was flashing red. However, I opened up the vs code and build the default blinky project, choose a build option for the nrfdongle board, then flash it using the vscode "flash" in "nrf connect vs code extension". It asked me to erase full memory and I clicked yes. Then the red flash on the dongle stopped. After that nothing happens. I disconnected the dongle from the dk board and plugged into usb port for power but it didn't turn on either even if I press the boot button.

Here's the log of the program flashing. Any more ideas?

Building blinky_newest
west build --build-dir c:\Users\DESKTOP-DAIN-03\Desktop\roobuck-scratch-repo\nordic_dev\blinky_newest\build c:\Users\DESKTOP-DAIN-03\Desktop\roobuck-scratch-repo\nordic_dev\blinky_newest --pristine --board nrf52840dongle_nrf52840 -- -DNCS_TOOLCHAIN_VERSION:STRING="NONE" -DCONFIG_DEBUG_OPTIMIZATIONS=y -DCONFIG_DEBUG_THREAD_INFO=y

-- west build: generating a build system
Including boilerplate (Zephyr base): C:/Users/DESKTOP-DAIN-03/ncs/v1.9.1/zephyr/cmake/app/boilerplate.cmake
-- Application: C:/Users/DESKTOP-DAIN-03/Desktop/roobuck-scratch-repo/nordic_dev/blinky_newest
-- Zephyr version: 2.7.99 (C:/Users/DESKTOP-DAIN-03/ncs/v1.9.1/zephyr), build: v2.7.99-ncs1-1
-- Found Python3: C:/Users/DESKTOP-DAIN-03/ncs/v1.9.1/toolchain/opt/bin/python.exe (found suitable exact version "3.8.2") found components: Interpreter 
-- Found west (found suitable version "0.12.0", minimum required is "0.7.1")
-- Board: nrf52840dongle_nrf52840
-- Cache files will be written to: C:/Users/DESKTOP-DAIN-03/ncs/v1.9.1/zephyr/.cache
-- Found dtc: C:/Users/DESKTOP-DAIN-03/ncs/v1.9.1/toolchain/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")
-- Found toolchain: gnuarmemb (c:/Users/DESKTOP-DAIN-03/ncs/v1.9.1/toolchain/opt)
-- Found BOARD.dts: C:/Users/DESKTOP-DAIN-03/ncs/v1.9.1/zephyr/boards/arm/nrf52840dongle_nrf52840/nrf52840dongle_nrf52840.dts
-- Generated zephyr.dts: C:/Users/DESKTOP-DAIN-03/Desktop/roobuck-scratch-repo/nordic_dev/blinky_newest/build/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: C:/Users/DESKTOP-DAIN-03/Desktop/roobuck-scratch-repo/nordic_dev/blinky_newest/build/zephyr/include/generated/devicetree_unfixed.h
-- Generated device_extern.h: C:/Users/DESKTOP-DAIN-03/Desktop/roobuck-scratch-repo/nordic_dev/blinky_newest/build/zephyr/include/generated/device_extern.h
-- Including generated dts.cmake file: C:/Users/DESKTOP-DAIN-03/Desktop/roobuck-scratch-repo/nordic_dev/blinky_newest/build/zephyr/dts.cmake
Parsing C:/Users/DESKTOP-DAIN-03/ncs/v1.9.1/zephyr/Kconfig
Loaded configuration 'C:/Users/DESKTOP-DAIN-03/ncs/v1.9.1/zephyr/boards/arm/nrf52840dongle_nrf52840/nrf52840dongle_nrf52840_defconfig'
Merged configuration 'C:/Users/DESKTOP-DAIN-03/Desktop/roobuck-scratch-repo/nordic_dev/blinky_newest/prj.conf'
Merged configuration 'C:/Users/DESKTOP-DAIN-03/Desktop/roobuck-scratch-repo/nordic_dev/blinky_newest/build/zephyr/misc/generated/extra_kconfig_options.conf'
Configuration saved to 'C:/Users/DESKTOP-DAIN-03/Desktop/roobuck-scratch-repo/nordic_dev/blinky_newest/build/zephyr/.config'
Kconfig header saved to 'C:/Users/DESKTOP-DAIN-03/Desktop/roobuck-scratch-repo/nordic_dev/blinky_newest/build/zephyr/include/generated/autoconf.h'
-- The C compiler identification is GNU 9.2.1
-- The CXX compiler identification is GNU 9.2.1
-- The ASM compiler identification is GNU
-- Found assembler: C:/Users/DESKTOP-DAIN-03/ncs/v1.9.1/toolchain/opt/bin/arm-none-eabi-gcc.exe
-- Configuring done
-- Generating done
-- Build files have been written to: C:/Users/DESKTOP-DAIN-03/Desktop/roobuck-scratch-repo/nordic_dev/blinky_newest/build
-- west build: building application
[1/156] Generating misc/generated/syscalls.json, misc/generated/struct_tags.json
[2/156] Generating include/generated/driver-validation.h
[3/156] Generating include/generated/kobj-types-enum.h, include/generated/otype-to-str.h, include/generated/otype-to-size.h
[4/156] Generating include/generated/syscall_dispatch.c, include/generated/syscall_list.h
[5/156] Building C object zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj
[6/156] Generating include/generated/offsets.h
[7/156] Building ASM object zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/cpu_idle.S.obj
[8/156] Building ASM object zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/swap_helper.S.obj
[9/156] Building ASM object zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/nmi_on_reset.S.obj
[10/156] Building ASM object zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/isr_wrapper.S.obj
[11/156] Building C object zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/nmi.c.obj
[12/156] Building C object zephyr/arch/common/CMakeFiles/arch__common.dir/sw_isr_common.c.obj
[13/156] Building C object zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/thread.c.obj
[14/156] Building C object zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/prep_c.c.obj
[15/156] Building C object zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/swap.c.obj
[16/156] Generating linker_zephyr_pre1.cmd
[17/156] Building C object zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/irq_manage.c.obj
[18/156] Building C object zephyr/lib/posix/CMakeFiles/lib__posix.dir/pthread_common.c.obj
[19/156] Building ASM object zephyr/arch/arch/arm/core/aarch32/cortex_m/CMakeFiles/arch__arm__core__aarch32__cortex_m.dir/reset.S.obj
[20/156] Generating linker_zephyr_pre0.cmd
[21/156] Building ASM object zephyr/arch/arch/arm/core/aarch32/cortex_m/CMakeFiles/arch__arm__core__aarch32__cortex_m.dir/exc_exit.S.obj
[22/156] Building C object zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/fatal.c.obj
[23/156] Building ASM object zephyr/arch/arch/arm/core/aarch32/cortex_m/CMakeFiles/arch__arm__core__aarch32__cortex_m.dir/vector_table.S.obj
[24/156] Building C object zephyr/arch/common/CMakeFiles/isr_tables.dir/isr_tables.c.obj
[25/156] Building ASM object zephyr/arch/arch/arm/core/aarch32/cortex_m/CMakeFiles/arch__arm__core__aarch32__cortex_m.dir/fault_s.S.obj
[26/156] Building C object zephyr/arch/arch/arm/core/aarch32/cortex_m/CMakeFiles/arch__arm__core__aarch32__cortex_m.dir/irq_init.c.obj
[27/156] Building C object zephyr/lib/libc/minimal/CMakeFiles/lib__libc__minimal.dir/source/stdout/fprintf.c.obj
[28/156] Building C object zephyr/arch/arch/arm/core/aarch32/cortex_m/CMakeFiles/arch__arm__core__aarch32__cortex_m.dir/fpu.c.obj
[29/156] Building C object zephyr/arch/arch/arm/core/aarch32/cortex_m/CMakeFiles/arch__arm__core__aarch32__cortex_m.dir/thread_abort.c.obj
[30/156] Building C object zephyr/lib/libc/minimal/CMakeFiles/lib__libc__minimal.dir/source/stdlib/strtoul.c.obj
[31/156] Building C object zephyr/lib/libc/minimal/CMakeFiles/lib__libc__minimal.dir/source/time/gmtime.c.obj
[32/156] Building C object zephyr/arch/arch/arm/core/aarch32/cortex_m/CMakeFiles/arch__arm__core__aarch32__cortex_m.dir/scb.c.obj
[33/156] Building C object zephyr/lib/libc/minimal/CMakeFiles/lib__libc__minimal.dir/source/stdlib/atoi.c.obj
[34/156] Building C object zephyr/arch/arch/arm/core/aarch32/mpu/CMakeFiles/arch__arm__core__aarch32__mpu.dir/arm_core_mpu.c.obj
[35/156] Building C object zephyr/arch/arch/arm/core/aarch32/cortex_m/CMakeFiles/arch__arm__core__aarch32__cortex_m.dir/fault.c.obj
[36/156] Building C object zephyr/arch/arch/arm/core/aarch32/mpu/CMakeFiles/arch__arm__core__aarch32__mpu.dir/arm_mpu.c.obj
[37/156] Building C object zephyr/lib/libc/minimal/CMakeFiles/lib__libc__minimal.dir/source/stdlib/strtol.c.obj
[38/156] Linking C static library zephyr\arch\arch\arm\core\aarch32\libarch__arm__core__aarch32.a
[39/156] Building C object zephyr/lib/libc/minimal/CMakeFiles/lib__libc__minimal.dir/source/stdlib/bsearch.c.obj
[40/156] Linking C static library zephyr\arch\common\libisr_tables.a
[41/156] Building C object zephyr/lib/libc/minimal/CMakeFiles/lib__libc__minimal.dir/source/stdlib/qsort.c.obj
[42/156] Building C object zephyr/lib/libc/minimal/CMakeFiles/lib__libc__minimal.dir/source/string/strstr.c.obj
[43/156] Building C object zephyr/lib/libc/minimal/CMakeFiles/lib__libc__minimal.dir/source/stdlib/exit.c.obj
[44/156] Building C object zephyr/lib/libc/minimal/CMakeFiles/lib__libc__minimal.dir/source/stdlib/abort.c.obj
[45/156] Building C object zephyr/lib/libc/minimal/CMakeFiles/lib__libc__minimal.dir/source/string/string.c.obj
[46/156] Building C object zephyr/lib/libc/minimal/CMakeFiles/lib__libc__minimal.dir/source/string/strncasecmp.c.obj
[47/156] Building C object zephyr/lib/libc/minimal/CMakeFiles/lib__libc__minimal.dir/source/stdout/sprintf.c.obj
[48/156] Building C object zephyr/lib/libc/minimal/CMakeFiles/lib__libc__minimal.dir/source/string/strspn.c.obj
[49/156] Linking C static library zephyr\arch\arch\arm\core\aarch32\mpu\libarch__arm__core__aarch32__mpu.a
[50/156] Building C object zephyr/lib/libc/minimal/CMakeFiles/lib__libc__minimal.dir/source/stdout/stdout_console.c.obj
[51/156] Building C object zephyr/lib/libc/minimal/CMakeFiles/lib__libc__minimal.dir/source/stdlib/malloc.c.obj
[52/156] Linking C static library zephyr\arch\common\libarch__common.a
[53/156] Linking C static library zephyr\arch\arch\arm\core\aarch32\cortex_m\libarch__arm__core__aarch32__cortex_m.a
[54/156] Building C object zephyr/soc/arm/common/cortex_m/CMakeFiles/soc__arm__common__cortex_m.dir/arm_mpu_regions.c.obj
[55/156] Building C object zephyr/lib/posix/CMakeFiles/lib__posix.dir/nanosleep.c.obj
[56/156] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/cbprintf.c.obj
[57/156] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/crc16_sw.c.obj
[58/156] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/crc32c_sw.c.obj
[59/156] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/crc32_sw.c.obj
[60/156] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/cbprintf_packaged.c.obj
[61/156] Building C object zephyr/soc/arm/nordic_nrf/nrf52/CMakeFiles/soc__arm__nordic_nrf__nrf52.dir/soc.c.obj
[62/156] Building C object zephyr/boards/arm/nrf52840dongle_nrf52840/CMakeFiles/boards__arm__nrf52840dongle_nrf52840.dir/board.c.obj
[63/156] Building C object zephyr/soc/arm/nordic_nrf/nrf52/CMakeFiles/soc__arm__nordic_nrf__nrf52.dir/power.c.obj
[64/156] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/crc8_sw.c.obj
[65/156] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/crc7_sw.c.obj
[66/156] Linking C static library zephyr\lib\posix\liblib__posix.a
[67/156] Linking C static library zephyr\soc\arm\common\cortex_m\libsoc__arm__common__cortex_m.a
[68/156] Building C object CMakeFiles/app.dir/src/main.c.obj
[69/156] Linking C static library zephyr\lib\libc\minimal\liblib__libc__minimal.a
[70/156] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/dec.c.obj
[71/156] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/hex.c.obj
[72/156] Linking C static library zephyr\soc\arm\nordic_nrf\nrf52\libsoc__arm__nordic_nrf__nrf52.a
[73/156] Linking C static library zephyr\boards\arm\nrf52840dongle_nrf52840\libboards__arm__nrf52840dongle_nrf52840.a
[74/156] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/notify.c.obj
[75/156] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/fdtable.c.obj
[76/156] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/printk.c.obj
[77/156] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/onoff.c.obj
[78/156] Linking C static library app\libapp.a
[79/156] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/heap.c.obj
[80/156] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/timeutil.c.obj
[81/156] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/sem.c.obj
[82/156] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/thread_entry.c.obj
[83/156] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/heap-validate.c.obj
[84/156] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/reboot.c.obj
[85/156] Building C object zephyr/CMakeFiles/zephyr.dir/misc/generated/configs.c.obj
[86/156] Building ASM object zephyr/CMakeFiles/zephyr.dir/soc/arm/nordic_nrf/common/soc_nrf_common.S.obj
[87/156] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/rb.c.obj
[88/156] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/multi_heap.c.obj
[89/156] Building C object zephyr/CMakeFiles/zephyr.dir/soc/arm/nordic_nrf/validate_base_addresses.c.obj
[90/156] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/cbprintf_complete.c.obj
[91/156] Building C object zephyr/CMakeFiles/zephyr.dir/subsys/debug/thread_info.c.obj
[92/156] Building C object zephyr/CMakeFiles/zephyr.dir/soc/arm/nordic_nrf/validate_enabled_instances.c.obj
[93/156] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/bitarray.c.obj
[94/156] Building C object zephyr/CMakeFiles/zephyr.dir/subsys/pm/policy/residency.c.obj
[95/156] Building C object zephyr/CMakeFiles/zephyr.dir/subsys/pm/constraint.c.obj
[96/156] Building C object zephyr/CMakeFiles/zephyr_pre0.dir/misc/empty_file.c.obj
[97/156] Building C object zephyr/CMakeFiles/zephyr.dir/subsys/pm/pm.c.obj
[98/156] Building C object zephyr/CMakeFiles/zephyr.dir/C_/Users/DESKTOP-DAIN-03/ncs/v1.9.1/nrfxlib/crypto/nrf_cc310_platform/src/nrf_cc3xx_platform_abort_zephyr.c.obj
[99/156] Building C object zephyr/drivers/timer/CMakeFiles/drivers__timer.dir/sys_clock_init.c.obj
[100/156] Building C object zephyr/CMakeFiles/zephyr.dir/subsys/tracing/tracing_none.c.obj
[101/156] Building C object zephyr/CMakeFiles/zephyr.dir/C_/Users/DESKTOP-DAIN-03/ncs/v1.9.1/nrfxlib/crypto/nrf_cc310_platform/src/nrf_cc3xx_platform_mutex_zephyr.c.obj
[102/156] Building C object zephyr/drivers/gpio/CMakeFiles/drivers__gpio.dir/gpio_nrfx.c.obj
[103/156] Building C object modules/nrf/lib/fatal_error/CMakeFiles/..__nrf__lib__fatal_error.dir/fatal_error.c.obj
[104/156] Building C object zephyr/drivers/clock_control/CMakeFiles/drivers__clock_control.dir/clock_control_nrf.c.obj
[105/156] Building C object modules/hal_nordic/nrfx/CMakeFiles/modules__hal_nordic__nrfx.dir/C_/Users/DESKTOP-DAIN-03/ncs/v1.9.1/modules/hal/nordic/nrfx/mdk/system_nrf52840.c.obj
[106/156] Building C object modules/nrf/drivers/hw_cc310/CMakeFiles/..__nrf__drivers__hw_cc310.dir/hw_cc310.c.obj
[107/156] Building C object zephyr/drivers/timer/CMakeFiles/drivers__timer.dir/nrf_rtc_timer.c.obj
[108/156] Building C object modules/hal_nordic/nrfx/CMakeFiles/modules__hal_nordic__nrfx.dir/nrfx_glue.c.obj
[109/156] Building C object modules/hal_nordic/nrfx/CMakeFiles/modules__hal_nordic__nrfx.dir/C_/Users/DESKTOP-DAIN-03/ncs/v1.9.1/modules/hal/nordic/nrfx/helpers/nrfx_flag32_allocator.c.obj
[110/156] Linking C static library modules\nrf\lib\fatal_error\lib..__nrf__lib__fatal_error.a
[111/156] Linking C static library zephyr\drivers\gpio\libdrivers__gpio.a
[112/156] Linking C static library modules\nrf\drivers\hw_cc310\lib..__nrf__drivers__hw_cc310.a
[113/156] Linking C static library zephyr\drivers\clock_control\libdrivers__clock_control.a
[114/156] Linking C static library zephyr\drivers\timer\libdrivers__timer.a
[115/156] Linking C static library zephyr\libzephyr.a
[116/156] Building C object zephyr/kernel/CMakeFiles/kernel.dir/condvar.c.obj
[117/156] Building C object zephyr/kernel/CMakeFiles/kernel.dir/system_work_q.c.obj
[118/156] Building C object modules/hal_nordic/nrfx/CMakeFiles/modules__hal_nordic__nrfx.dir/C_/Users/DESKTOP-DAIN-03/ncs/v1.9.1/modules/hal/nordic/nrfx/drivers/src/nrfx_clock.c.obj
[119/156] Building C object zephyr/kernel/CMakeFiles/kernel.dir/stack.c.obj
[120/156] Building C object modules/hal_nordic/nrfx/CMakeFiles/modules__hal_nordic__nrfx.dir/C_/Users/DESKTOP-DAIN-03/ncs/v1.9.1/modules/hal/nordic/nrfx/drivers/src/nrfx_gpiote.c.obj
[121/156] Building C object zephyr/kernel/CMakeFiles/kernel.dir/fatal.c.obj
[122/156] Building C object zephyr/kernel/CMakeFiles/kernel.dir/main_weak.c.obj
[123/156] Building C object zephyr/kernel/CMakeFiles/kernel.dir/sched.c.obj
[124/156] Building C object zephyr/kernel/CMakeFiles/kernel.dir/work.c.obj
[125/156] Building C object zephyr/kernel/CMakeFiles/kernel.dir/banner.c.obj
[126/156] Building C object zephyr/kernel/CMakeFiles/kernel.dir/kheap.c.obj
[127/156] Building C object zephyr/kernel/CMakeFiles/kernel.dir/device.c.obj
[128/156] Building C object zephyr/kernel/CMakeFiles/kernel.dir/init.c.obj
[129/156] Building C object zephyr/kernel/CMakeFiles/kernel.dir/version.c.obj
[130/156] Building C object zephyr/kernel/CMakeFiles/kernel.dir/errno.c.obj
[131/156] Building C object zephyr/kernel/CMakeFiles/kernel.dir/idle.c.obj
[132/156] Building C object zephyr/kernel/CMakeFiles/kernel.dir/mem_slab.c.obj
[133/156] Linking C static library modules\hal_nordic\nrfx\libmodules__hal_nordic__nrfx.a
[134/156] Building C object zephyr/kernel/CMakeFiles/kernel.dir/xip.c.obj
[135/156] Building C object zephyr/kernel/CMakeFiles/kernel.dir/msg_q.c.obj
[136/156] Building C object zephyr/kernel/CMakeFiles/kernel.dir/mailbox.c.obj
[137/156] Building C object zephyr/kernel/CMakeFiles/kernel.dir/sem.c.obj
[138/156] Building C object zephyr/kernel/CMakeFiles/kernel.dir/thread.c.obj
[139/156] Building C object zephyr/kernel/CMakeFiles/kernel.dir/queue.c.obj
[140/156] Building C object zephyr/kernel/CMakeFiles/kernel.dir/pipes.c.obj
[141/156] Building C object zephyr/kernel/CMakeFiles/kernel.dir/mutex.c.obj
[142/156] Building C object zephyr/kernel/CMakeFiles/kernel.dir/timer.c.obj
[143/156] Building C object zephyr/kernel/CMakeFiles/kernel.dir/mempool.c.obj
[144/156] Building C object zephyr/kernel/CMakeFiles/kernel.dir/timeout.c.obj
[145/156] Linking C static library zephyr\kernel\libkernel.a
[146/156] Linking C executable zephyr\zephyr_pre0.elf

[147/156] Generating dev_handles.c
[148/156] Building C object zephyr/CMakeFiles/zephyr_pre1.dir/misc/empty_file.c.obj
[149/156] Building C object zephyr/CMakeFiles/zephyr_pre1.dir/dev_handles.c.obj
[150/156] Linking C executable zephyr\zephyr_pre1.elf

[151/156] Generating linker.cmd
[152/156] Generating isr_tables.c, isrList.bin
[153/156] Building C object zephyr/CMakeFiles/zephyr_final.dir/misc/empty_file.c.obj
[154/156] Building C object zephyr/CMakeFiles/zephyr_final.dir/isr_tables.c.obj
[155/156] Building C object zephyr/CMakeFiles/zephyr_final.dir/dev_handles.c.obj
[156/156] Linking C executable zephyr\zephyr.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:       25288 B      1020 KB      2.42%
            SRAM:        6272 B       256 KB      2.39%
        IDT_LIST:          0 GB         2 KB      0.00%

Terminal will be reused by tasks, press any key to close it.

> Executing task: nRF Connect: Build: blinky_newest/build (active) <

Building blinky_newest
west build --build-dir c:\Users\DESKTOP-DAIN-03\Desktop\roobuck-scratch-repo\nordic_dev\blinky_newest\build c:\Users\DESKTOP-DAIN-03\Desktop\roobuck-scratch-repo\nordic_dev\blinky_newest

ninja: no work to do.

Terminal will be reused by tasks, press any key to close it.

> Executing task: nRF Connect: Flash: blinky_newest/build (active) <

Flashing build to undefined
west flash -d c:\Users\DESKTOP-DAIN-03\Desktop\roobuck-scratch-repo\nordic_dev\blinky_newest\build --skip-rebuild -r nrfjprog --dev-id 1050239339

-- west flash: using runner nrfjprog
-- runners.nrfjprog: Flashing file: c:\Users\DESKTOP-DAIN-03\Desktop\roobuck-scratch-repo\nordic_dev\blinky_newest\build\zephyr\zephyr.hex
ERROR: The operation attempted is unavailable due to readback protection in
ERROR: your device. Please use --recover to unlock the device.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
ERROR: runners.nrfjprog: Flashing failed because the target must be recovered.
  To fix, run "west flash --recover" instead.
  Note: this will recover and erase all flash memory prior to reflashing.
FATAL ERROR: command exited with status 16: nrfjprog --program 'c:\Users\DESKTOP-DAIN-03\Desktop\roobuck-scratch-repo\nordic_dev\blinky_newest\build\zephyr\zephyr.hex' --sectoranduicrerase -f NRF52 --snr 1050239339
The terminal process terminated with exit code: 16.

Terminal will be reused by tasks, press any key to close it.

> Executing task: nRF Connect: Flash: blinky_newest/build (active) <

Flashing build to undefined
west flash -d c:\Users\DESKTOP-DAIN-03\Desktop\roobuck-scratch-repo\nordic_dev\blinky_newest\build --skip-rebuild -r nrfjprog --dev-id 1050239339 --recover

-- west flash: using runner nrfjprog
-- runners.nrfjprog: Recovering and erasing all flash memory.
Recovering device. This operation might take 30s.
Writing image to disable ap protect.
Erasing user code and UICR flash areas.
-- runners.nrfjprog: Flashing file: c:\Users\DESKTOP-DAIN-03\Desktop\roobuck-scratch-repo\nordic_dev\blinky_newest\build\zephyr\zephyr.hex
Parsing image file.
WARNING: A programming operation has been performed without --verify.
WARNING: Programming can fail without error.
Enabling pin reset.
Applying pin reset.
-- runners.nrfjprog: Board with serial number 1050239339 flashed successfully.

Terminal will be reused by tasks, press any key to close it.

RE: Read debugs from nrf52840 dongle on nrf52840 DK

Simonr — Wed, 25 May 2022 10:33:56 GMT

No there, shouldn't be an issue with the debug out header unless it's been physically damaged.

RE: Read debugs from nrf52840 dongle on nrf52840 DK

Naing — Tue, 24 May 2022 11:56:06 GMT

That's great! I'll try out your suggestion once I received them. Any chance it might be the issue with the DK board's DEBUG OUT header? Cheers

RE: Read debugs from nrf52840 dongle on nrf52840 DK

Simonr — Tue, 24 May 2022 11:48:59 GMT

Hi again Naing

I just heard back from customer service that two nRF52840 Dongles have been shipped.

DHL Trackingnumber: 2952239356

Best regards,

Simon

RE: Read debugs from nrf52840 dongle on nrf52840 DK

Naing — Mon, 23 May 2022 23:47:58 GMT

Full Name: xxx

Address: xxx

Phone Number: xxx

Thanks.

RE: Read debugs from nrf52840 dongle on nrf52840 DK

Simonr — Mon, 23 May 2022 07:33:57 GMT

I've set the case to private mode now, so you can share your contact information. In order to send you anything, we'll need the following:

Full name
Address you want the device(s) shipped to
Phone number

Best regards,

Simon

RE: Read debugs from nrf52840 dongle on nrf52840 DK

Naing — Fri, 20 May 2022 07:00:23 GMT

3 of them doesn't turn on anymore but the remaining two happens as described. I've run out of new dongles to test, so it'd be great if I can have some to get at least one working dongle. Where should I mail you the address to send?

Cheers,

RE: Read debugs from nrf52840 dongle on nrf52840 DK

Simonr — Thu, 19 May 2022 13:22:31 GMT

The fried REG0 regulators would be on the Dongles. Do all the Dongles act the way you described in your last reply? If so I can try to get my hands on a couple to send you, so you can test only powering it from the DKs Debug OUT port with SB47 shorted as that should let you program and debug a Dongle As explained in the user guide you linked to. "The nRF52840 DK can supply power through the Debug out connector (P19). To enable this, short solder bridge SB47. While SB47 is shorted, it is not possible to program the onboard nRF52840 SoC even if the external board is unplugged."

https://infocenter.nordicsemi.com/index.jsp?topic=%2Fug_nrf52840_dk%2FUG%2Fdk%2Fhw_debug_out.html

Best regards,

Simon

RE: Read debugs from nrf52840 dongle on nrf52840 DK

Naing — Thu, 19 May 2022 06:08:03 GMT

Yes I have tried shorting the SB47 while DK is connected to the dongle. I just used a metal tip to do that so it's not permanent and I only tried that on one of the boards. Where is that REG0 regulator that has been fried? is it on the dongle or DK board?

RE: Read debugs from nrf52840 dongle on nrf52840 DK

Simonr — Thu, 19 May 2022 06:02:52 GMT

What seems to have happened is that the REG0 regulator (VDDH->VDD) has been fried, as its default output is 1.8V. If you have shorted SB47 on the DK so that the DK supplies power through the debug out connector while the Dongle is connected to power, this is likely to happen I'm afraid.

Best regards,

Simon

RE: Read debugs from nrf52840 dongle on nrf52840 DK

Naing — Tue, 17 May 2022 01:02:49 GMT

Hi,

I've tried supplying 3V through the VDD out pins on the dongle and cutting and soldering SB2/SB1 respectively. It behaves exactly same behavior as charging via USB. I actually have tested on 5 of such dongles. One of them seemed to work before (ie. can flash blinky from DK board onto the dongle) but with very dim blinky on green LED and after a while it didn't turn on anymore. Including that one, I have 3 bricked dongles now which are not turning on anymore even when I press the bootloader button. How can I fix this, if possible? I can safely say that they were working well out of the box. This happens only after soldering on the SWD header.

In the remaining two dongles, I noticed that after unplugging the dongle from USB while the SWD is connected to DK board, the red LED on dongle still flashes (faster than bootloader flash pattern). The dongle appears to be powered via the SWD.

Currently, none of them is working.

Regards,

RE: Read debugs from nrf52840 dongle on nrf52840 DK

Simonr — Wed, 11 May 2022 07:18:18 GMT

Okay, what it might be is that the Dongle isn't powered with 3.0V when you try programming it with the DK, as the DK supported for external debugging/programming is VDD voltage. This is normally 3V when running from USB, and the external board (Dongle) needs to match the VDD of the nRF52840 DK. It can't be powered by the 10 pin debug cable, but you can try powering it with an external source of some kind that provides 3.0V.

Best regards,

Simon

RE: Read debugs from nrf52840 dongle on nrf52840 DK

Naing — Tue, 10 May 2022 04:32:59 GMT

Hi,

This is the latest setup and the notches fit. I believe this is the right setup?

I found that when I burnt a bootloader using this setup in Arduino IDE, the bootloader is burnt on the SoC on the DK board instead of the dongle. So I think the DK board is not detecting the dongle. Is there any other ways to check this?

I also found this statement in the manual.

"If it is inconvenient to have a separate power supply on the external board, the nRF52840 DK can supply power through the Debug out connector (P19). To enable this, short solder bridge SB47. While SB47 is shorted, it is not possible to program the onboard nRF52840 SoC even if the external board is unplugged." -link

Would you recommend shorting SB47 and don't plug in the dongle USB anymore but instead supply power from DEBUG OUT SWD interface?

Regards,

RE: Read debugs from nrf52840 dongle on nrf52840 DK

Simonr — Fri, 06 May 2022 08:11:48 GMT

1. From your latest pictures it looks like the pin header is soldered on correctly, but does your 10pin cable not have this "notch" in it? It should fit into the "slot" on the pin header, to ensure it is mounted correctly.

If the Dongle is in Bootloader mode (pulsing red) it will still show up in the programmer app even when connected to the DK. And the DK will automatically choose the device connected to the debug out header if it's powered.

Best regards,

Simon

RE: Read debugs from nrf52840 dongle on nrf52840 DK

Naing — Fri, 06 May 2022 02:11:20 GMT

Hi, I've adjust a few things from your feedback.

1. I believe I soldered the pin header on dongle the opposite way. So, now I've reversed the connector cable as shown in the images. pic1, pic2 However, I'm still not able to read the debugs. The manual says if DEBUG OUT is connected to the dongle, the DK board will operate from the donlge's nRF SOC instead of its own SOC. Could you tell me how I can check this? Does it mean we should only see one device in the nRF programmer app because now I'm see both DK and dongle boards.

2. Yes it's the LED5 that's flashing

3. After doing No. 1, the Dongle doesn't go into bootloader mode automatically anymore. (solved)

4. I will update to v1.9.1, no problem.

Appreciate your help 🙂

RE: Read debugs from nrf52840 dongle on nrf52840 DK

Simonr — Wed, 04 May 2022 13:42:12 GMT

Hi again

Okay, thank you for clarifying, I see I misunderstood multiple things here. It should still work as far as I can see, but yes, the nRF Connect SDK should be able to get an RTT output from a Dongle connected like this in VS code. Are you sure the debug pin header is soldered on the correct way on the bottom of the Dongle? Can you show me a picture of that as well?

For the green LED I thought you said the led on the Dongle was blinking "really fast" so I thought something was wrong there, but I see now that this was likely LED5 on the DK, which indeed blinks to reflect activity on the debugger MCU.

For the Dongle going into bootloader mode, does this happen even if the Dongle isn't connected with the debugger cable when the DK is plugged into the PC, or if the DK is OFF when you plug it in?

I see you're using nRF Connect SDK v1.9.0. Is there a reason you're not using the latest version (v1.9.1) which has both features added and bugs/issues fixed?

Best regards,

Simon

RE: Read debugs from nrf52840 dongle on nrf52840 DK

Naing — Tue, 03 May 2022 13:28:45 GMT

Hi, I'm using the nRF connect SDK v1.9.0 which is installed using the nRF Connect for Desktop toolchain manager app.

As for the RTT, I thought it was just a normal debug monitor. I havn't put in any code specific to that. I'd appreciate if you can give me an example snippet of what it should look like. Or is it possible to debug normally without RTT?

The green LED flashing on the DK board seems constant now when I restarted. I didn't program anything on the DK board. Only the dongle is programmed with blinky. I believe green LED on DK board is turned on by default.

One more thing I noticed, the dongle gets into bootloader mode when the debugger(dk board) usb is plugged into PC. In order to run the blinky on the dongle, i have to unplug the dongle and plug it back in while debugger usb is still connected to PC.

RE: Read debugs from nrf52840 dongle on nrf52840 DK

Simonr — Tue, 03 May 2022 10:27:48 GMT

This seems like it should work, but I got a few ideas as to what could be going wrong.

First off, it might be that the RTT viewer in the nRF Terminal is not working as expected for some reason, but you could try out the J-Link RTT viewer instead, as that is a bit more stable. Also, can you show me how you've enabled the RTT logging in your application, and let me know what SDK and SDK version you're using for development?

As for the green LED flashing "very fast", I assume you mean faster than expected when it runs the normal Blinky application, but can you still see it physically blinking or does it appear to just be on?

Best regards,

Simon