RTT Viwer can't see log messages of nRF5340 NET core

[snowuyl]

Procedure to reproduce this issue is as follows.
1. cd D:\ncs\v2.3.0\nrf\samples\nrf5340\multiprotocol_rpmsg
2. west build -b nrf5340dk_nrf5340_cpuapp
3. west flash
4. Lauching RTT viwer and selecting NRF5340_XXAA_NET

5. RTT viwer shows "LOG: RTT Viewer connected" but can't see any log messags from nRF5340 NET core.

[snowuyl]

[snowuyl]

[snowuyl]

Thanks for your support!

[Priyanka]

Hi,

You can see from the sample description that it's meant to be built for netcore, but I am surprised how you get errors. Could you try deleting all previous builds and try building a fresh one? Please try for netcore this time again.

[snowuyl]

Thanks for your suggestion! I can build and flash after removed build folder. But I still can't see any debug messages on RTT Viewer. The following configuration is from  D:\ncs\v2.3.0\nrf\samples\nrf5340\multiprotocol_rpmsg\build\zephyr\.config.

# Logging
#
# CONFIG_LOG is not set
# CONFIG_LOG_OUTPUT is not set
# end of Logging

CONFIG_HAS_SEGGER_RTT=y

[snowuyl]

0552..config.zip

[Priyanka]

But when you did the fresh build, you did enable the follwowing in the prj.conf right? 

CONFIG_LOG=y
CONFIG_USE_SEGGER_RTT=y
CONFIG_LOG_BACKEND_RTT=y
CONFIG_PRINTK=y

[snowuyl]

I can't build successfully after I add the following configuration to prj.conf.

CONFIG_LOG=y
CONFIG_USE_SEGGER_RTT=y
CONFIG_LOG_BACKEND_RTT=y
CONFIG_PRINTK=y

Log messages of west build are as follows.

D:\ncs\v2.3.0\nrf\samples\nrf5340\multiprotocol_rpmsg>west build -b nrf5340dk_nrf5340_cpunet
-- west build: generating a build system

...

[286/296] Linking C executable zephyr\zephyr_pre0.elf
FAILED: zephyr/zephyr_pre0.elf zephyr/zephyr_pre0.map
cmd.exe /C "cd . && D:\ncs\toolchains\v2.3.0\opt\zephyr-sdk\arm-zephyr-eabi\bin\arm-zephyr-eabi-gcc.exe -gdwarf-4 @CMakeFiles\zephyr_pre0.rsp -o zephyr\zephyr_pre0.elf && cmd.exe /C "cd /D D:\ncs\v2.3.0\nrf\samples\nrf5340\multiprotocol_rpmsg\build\zephyr && D:\ncs\toolchains\v2.3.0\opt\bin\cmake.exe -E echo ""
d:/ncs/toolchains/v2.3.0/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.1.0/../../../../arm-zephyr-eabi/bin/ld.exe: zephyr\zephyr_pre0.elf section `rodata' will not fit in region `FLASH'
d:/ncs/toolchains/v2.3.0/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.1.0/../../../../arm-zephyr-eabi/bin/ld.exe: region `FLASH' overflowed by 4288 bytes
collect2.exe: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: 'D:\ncs\toolchains\v2.3.0\opt\bin\cmake.EXE' --build 'D:\ncs\v2.3.0\nrf\samples\nrf5340\multiprotocol_rpmsg\build'

D:\ncs\v2.3.0\nrf\samples\nrf5340\multiprotocol_rpmsg>

[Priyanka]

Does the FLASH overflow error occur only when you enable CONFIG_PRINTK ?

You might need to enable CONFIG_PRINTK, CONFIG_CONSOLE, and CONFIG_RTT_CONSOLE as well.

-Priyanka

[snowuyl]

CONFIG_LOG=y causes flash overflow error.

[Priyanka]

Hi,

I see that you have an ongoing conversation with a similar issue in this thread. So please continue the conversation there and feel free to close this ticket.

This will help future seekers and keep Devzone clean.

-Priyanka