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

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

Priyanka — Fri, 14 Jul 2023 14:22:25 GMT

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

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

snowuyl — Thu, 13 Jul 2023 11:12:26 GMT

CONFIG_LOG=y causes flash overflow error.

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

Priyanka — Thu, 13 Jul 2023 11:09:23 GMT

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

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

snowuyl — Thu, 13 Jul 2023 01:32:46 GMT

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

...

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

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

Priyanka — Wed, 12 Jul 2023 09:49:18 GMT

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

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

snowuyl — Wed, 12 Jul 2023 06:56:24 GMT

devzone.nordicsemi.com/.../0552_2E00_.config.zip

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

snowuyl — Wed, 12 Jul 2023 06:55:54 GMT

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

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

Priyanka — Wed, 12 Jul 2023 05:50:30 GMT

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.

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

snowuyl — Wed, 12 Jul 2023 05:42:38 GMT

Thanks for your support!

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

Priyanka — Wed, 12 Jul 2023 05:41:28 GMT

Hi,

I will try discussing this internally with my colleagues and get back to you. Please expect a slight delay as we are short staffed at the moment owing to the summer holidays here in Norway.

Thank you for your patience and understanding.

-Priyanka

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

snowuyl — Tue, 11 Jul 2023 09:58:49 GMT

I try to build for net core. But west build failed with the following log messaging.

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 4252 bytes
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: modules/hal_nordic/nrf_802154/libnrf-802154-platform.a(nrf_802154_spinel_backend_ipc.c.obj): in function `spinel_packet_send_thread_fn':
D:/ncs/v2.3.0/zephyr/modules/hal_nordic/nrf_802154/serialization/platform/nrf_802154_spinel_backend_ipc.c:132: undefined reference to `nrf_802154_serialization_error'
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: modules/nrfxlib/nrf_802154/nrf_802154/serialization/libnrf-802154-serialization.a(nrf_802154_spinel.c.obj): in function `nrf_802154_serialization_init':
D:/ncs/v2.3.0/nrfxlib/nrf_802154/serialization/src/nrf_802154_spinel.c:87: undefined reference to `nrf_802154_serialization_error'
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: modules/nrfxlib/nrf_802154/nrf_802154/serialization/libnrf-802154-serialization.a(nrf_802154_spinel.c.obj): in function `nrf_802154_spinel_encoded_packet_received':
D:/ncs/v2.3.0/nrfxlib/nrf_802154/serialization/src/nrf_802154_spinel.c:128: undefined reference to `nrf_802154_serialization_error'
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: modules/nrfxlib/nrf_802154/nrf_802154/serialization/libnrf-802154-serialization.a(nrf_802154_spinel_net.c.obj): in function `local_transmitted_frame_ptr_free':
D:/ncs/v2.3.0/nrfxlib/nrf_802154/serialization/src/nrf_802154_spinel_net.c:79: undefined reference to `nrf_802154_serialization_error'
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: modules/nrfxlib/nrf_802154/nrf_802154/serialization/libnrf-802154-serialization.a(nrf_802154_spinel_net.c.obj): in function `nrf_802154_cca_done':
D:/ncs/v2.3.0/nrfxlib/nrf_802154/serialization/src/nrf_802154_spinel_net.c:101: undefined reference to `nrf_802154_serialization_error'
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: modules/nrfxlib/nrf_802154/nrf_802154/serialization/libnrf-802154-serialization.a(nrf_802154_spinel_net.c.obj):D:/ncs/v2.3.0/nrfxlib/nrf_802154/serialization/src/nrf_802154_spinel_net.c:123: more undefined references to `nrf_802154_serialization_error' follow
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'

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

Priyanka — Tue, 11 Jul 2023 09:26:19 GMT

Could you try building the same with cpunet instead of cpuapp and then check?

-Priyanka

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

snowuyl — Tue, 11 Jul 2023 08:50:05 GMT

Building is okay. Maybe you can provide me another sample that can show messages from net core.

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

Priyanka — Tue, 11 Jul 2023 08:48:25 GMT

[quote user=""]west build -b nrf5340dk_nrf5340_cpuapp[/quote]

Does this build successfully for you? Since you are building this for appcore, it might result in error. It will work when building for net core.

-Priyanka

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

snowuyl — Tue, 11 Jul 2023 08:38:59 GMT

devzone.nordicsemi.com/.../1803.prj.conf

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

snowuyl — Tue, 11 Jul 2023 08:37:07 GMT

Thanks for your reply! I have added the following configuration in prj.conf. But RTT Viewer still can't show any log messages.

# logging
CONFIG_LOG=y
CONFIG_USE_SEGGER_RTT=y
CONFIG_LOG_BACKEND_RTT=y
CONFIG_PRINTK=y

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

Priyanka — Tue, 11 Jul 2023 08:29:10 GMT

Hi,

Did you enable the log for the sample when you build it? Because it's disabled by default in the prj.conf file:

You can see the following in the Readme file within the project folder:

Please take a look at this ticket on how to view from RTT Logger.

-Priyanka

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

snowuyl — Tue, 11 Jul 2023 05:40:47 GMT

I have attached snapshot of RTT viewer. I don’t see any log file.

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

Priyanka — Tue, 11 Jul 2023 05:28:38 GMT

Hi,

You mentioned that the RTT Viewer shows that it's connected. Is it possible to attach the entire log that you see as of now in the RTT Viewer?

-Priyanka

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

snowuyl — Mon, 10 Jul 2023 11:02:10 GMT

No, I don’t get similar messages.

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

Priyanka — Mon, 10 Jul 2023 11:00:52 GMT

Do you get a message similar to the one mentioned in the ticket?

-Priyanka

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

snowuyl — Mon, 10 Jul 2023 09:29:59 GMT

Thanks for your reply! The ticket link you provided is related to nRF5340_xxAA_APP. Could you provide ticket link related nRF5340_xxAA_NET?

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

Priyanka — Mon, 10 Jul 2023 09:16:13 GMT

Hi,

Could you take a look at this ticket and see whether it helps?

-Priyanka

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

snowuyl — Mon, 10 Jul 2023 05:53:12 GMT

devzone.nordicsemi.com/.../_5B00_nRF5340_5D00_-MDBT53V_2D00_1M-_2600_-MDBT53V_2D00_P1M_5F00_Ver.C-spec.pdf

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

snowuyl — Mon, 10 Jul 2023 05:52:40 GMT

I am using Raytac MDBT53-DB board.