I'm in the project in which we are trying to implement logging to file functionality to NRF5340 chip.
Following lines were added to config.proj file:
I'm in the project in which we are trying to implement logging to file functionality to NRF5340 chip.
Following lines were added to config.proj file:
Hello,
Do you have a project you can share (that I can run on an nRF5340-DK)? What ncs version are you using?
Are you able to get more debug information by:
# Add asserts
CONFIG_ASSERT=y
CONFIG_ASSERT_VERBOSE=y
CONFIG_ASSERT_NO_COND_INFO=n
CONFIG_ASSERT_NO_MSG_INFO=n
CONFIG_RESET_ON_FATAL_ERROR=n
CONFIG_THREAD_NAME=y
Kenneth
Hi, thank you for your answer. Unfortunately at the current stage I'm unable to share full project as it is a proprietary code.
But during debugging, I was able to made it to work only when RTT is disabled (CONFIG_SHELL_BACKEND_RTT).
So, maybe you know how can RTT and Logging to file be enabled at the same time?
Not in specific, but googling for CONFIG_SHELL_BACKEND_RTT and logging I could find some issues that could be related. Those do however look to be fixed in zephyr, so I guess it may depend a bit on what nRF Connect SDK release you are working on whether they have made it into the release for NCS. But good to hear you have found a workaround.
Kenneth
This is just a temporary walkaround, as the cause of the problem is still unknown
I'm using nRF Connect SDK 1.9.1
This is just a temporary walkaround, as the cause of the problem is still unknown
I'm using nRF Connect SDK 1.9.1
Some related thread I can find are:
Log and shell through RTT backend don't play nicely
https://github.com/zephyrproject-rtos/zephyr/issues/36909
If you are able to provide a project I can run on an nRF5340 that show the symptoms by for instance simply commenting out CONFIG_SHELL_BACKEND_RTT then I can run in by the developers to see if I can get their feedback.
If possible trying this on a newer ncs release can also be something to try. The current latest is v2.1.0.
Kenneth