Using printk on custom board nRF Connect SDK

RE: Using printk on custom board nRF Connect SDK

Hung Bui — Thu, 23 Feb 2023 14:27:06 GMT

Hi Dario,

Could you elaborate what you meant by "print via the dev-kit that I connect to" . How do you connect your board to the devkit ? Via GPIO or via SWD interface ?
You can use the DK UART by connecting the UART pins of the custom board to the UART pin of the nRF5340 on the DK. If you don't flash anything on the nRF5340 DK you can overwrite the nRF5340 on the DK and transmit your UART data via the interface chip on the DK.

If you simply want printk to be routed to RTT. You can try the example I attached here. It works on the DK configuration, so I'm don't know if it work with your board dts configuration or not.

devzone.nordicsemi.com/.../button_5F00_RTT.zip

If you want to output to the onboard USB interface, you may want to look at the thingy53 samples that it output the log via USB. Check the peripheral_uart sample. It has both RTT and USB (UART) log.

RE: Using printk on custom board nRF Connect SDK

dario.sortino — Thu, 23 Feb 2023 14:15:46 GMT

I solved by using the following config

CONFIG_UART_CONSOLE=n

CONFIG_CONSOLE=y

CONFIG_USE_SEGGER_RTT=y

CONFIG_RTT_CONSOLE=y

And it works just fine with the printk function

RE: Using printk on custom board nRF Connect SDK

dario.sortino — Wed, 22 Feb 2023 15:13:44 GMT

The build is failing and it fails until i comment out the CONFIG_LOG =y line

FAILED: zephyr/zephyr_pre0.elf zephyr/zephyr_pre0.map
cmd.exe /C "cd . && C:\ncs\toolchains\v2.2.0\opt\zephyr-sdk\arm-zephyr-eabi\bin\arm-zephyr-eabi-gcc.exe -gdwarf-4 zephyr/CMakeFiles/zephyr_pre0.dir/misc/empty_file.c.obj -o zephyr\zephyr_pre0.elf -Wl,-T zephyr/linker_zephyr_pre0.cmd -Wl,-Map=C:/Users/dsortino/Desktop/GitHubProj/component_ifeel/element_firmware/iFeel_ConnectSDK/iFeel-WiredReceiver/build/zephyr/zephyr_pre0.map -Wl,--whole-archive app/libapp.a zephyr/libzephyr.a zephyr/arch/common/libarch__common.a zephyr/arch/arch/arm/core/aarch32/libarch__arm__core__aarch32.a zephyr/arch/arch/arm/core/aarch32/cortex_m/libarch__arm__core__aarch32__cortex_m.a zephyr/arch/arch/arm/core/aarch32/cortex_m/cmse/libarch__arm__core__aarch32__cortex_m__cmse.a zephyr/arch/arch/arm/core/aarch32/mpu/libarch__arm__core__aarch32__mpu.a zephyr/lib/libc/minimal/liblib__libc__minimal.a zephyr/soc/arm/common/cortex_m/libsoc__arm__common__cortex_m.a zephyr/subsys/fs/libsubsys__fs.a zephyr/drivers/usb/device/libdrivers__usb__device.a zephyr/drivers/clock_control/libdrivers__clock_control.a zephyr/drivers/console/libdrivers__console.a zephyr/drivers/gpio/libdrivers__gpio.a zephyr/drivers/i2c/libdrivers__i2c.a zephyr/drivers/spi/libdrivers__spi.a zephyr/drivers/hwinfo/libdrivers__hwinfo.a zephyr/drivers/serial/libdrivers__serial.a zephyr/drivers/timer/libdrivers__timer.a modules/nrf/lib/fatal_error/lib..__nrf__lib__fatal_error.a modules/nrf/drivers/hw_cc310/lib..__nrf__drivers__hw_cc310.a modules/fatfs/lib..__modules__fs__fatfs.a modules/hal_nordic/nrfx/libmodules__hal_nordic__nrfx.a modules/segger/libmodules__segger.a -Wl,--no-whole-archive zephyr/kernel/libkernel.a zephyr/CMakeFiles/offsets.dir/./arch/arm/core/offsets/offsets.c.obj -L"c:/ncs/toolchains/v2.2.0/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.1.0/thumb/v8-m.main/nofp" -LC:/Users/dsortino/Desktop/GitHubProj/component_ifeel/element_firmware/iFeel_ConnectSDK/iFeel-WiredReceiver/build/zephyr -lgcc zephyr/arch/common/libisr_tables.a -no-pie -mcpu=cortex-m33 -mthumb -mabi=aapcs -mfp16-format=ieee -Wl,--gc-sections -Wl,--build-id=none -Wl,--sort-common=descending -Wl,--sort-section=alignment -Wl,-u,_OffsetAbsSyms -Wl,-u,_ConfigAbsSyms -nostdlib -static -Wl,-X -Wl,-N -Wl,--orphan-handling=warn C:/ncs/v2.2.0/nrfxlib/crypto/nrf_cc312_platform/lib/cortex-m33/soft-float/no-interrupts/libnrf_cc312_platform_0.9.16.a && cmd.exe /C "cd /D C:\Users\dsortino\Desktop\GitHubProj\component_ifeel\element_firmware\iFeel_ConnectSDK\iFeel-WiredReceiver\build\zephyr && C:\ncs\toolchains\v2.2.0\opt\bin\cmake.exe -E echo ""
c:/ncs/toolchains/v2.2.0/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.1.0/../../../../arm-zephyr-eabi/bin/ld.exe: zephyr/libzephyr.a(sync_rtc.c.obj): in function `sync_rtc_setup':
C:\ncs\v2.2.0\zephyr\soc\arm\nordic_nrf\nrf53\sync_rtc.c:240: undefined reference to `__device_dts_ord_21'
collect2.exe: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.

RE: Using printk on custom board nRF Connect SDK

MaximSh — Wed, 22 Feb 2023 15:11:01 GMT

What failed?
Did you opened a J-Link RTT Viewer?
It should work with this configs

RE: Using printk on custom board nRF Connect SDK

dario.sortino — Wed, 22 Feb 2023 15:06:50 GMT

Still doesnt work. Maybe its a matter of dts

RE: Using printk on custom board nRF Connect SDK

MaximSh — Wed, 22 Feb 2023 15:01:59 GMT

#include <logging/log.h>

RE: Using printk on custom board nRF Connect SDK

dario.sortino — Wed, 22 Feb 2023 15:00:01 GMT

I fail to build with this setup.

Any include to add?

RE: Using printk on custom board nRF Connect SDK

MaximSh — Wed, 22 Feb 2023 14:51:41 GMT

If you want to print via SWDIO you can use RTT

Configs

CONFIG_LOG=y

CONFIG_UART_CONSOLE=n

CONFIG_CONSOLE=y

CONFIG_USE_SEGGER_RTT=y

CONFIG_RTT_CONSOLE=y

Code

1. Define

#define LOG_LEVEL LOG_LEVEL_INF

#define MODULE BLE

LOG_MODULE_REGISTER(MODULE);

2. Use

LOG_DBG("Test: %d\n", data);
LOG_INF(...)
LOG_WRN(...)
LOG_ERR(...)