• State Verified Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 64 subscribers
  • Views 1745 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 279228
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Zephyr RTT log output stops with SHELL is enabled

Allen

Hello,

I had RTT configured as the logging backend and it was working fine. When I enabled the SHELL on RTT, the log output stopped. Maybe more specifically, printk() output stopped.

It looks like this should be the default operation but it isn't work for me.  nRF Connect SDK 1.7.0 on 52832 processor.

Thanks

  • 0

    Ok, here is some more info.

    CONFIG_SHELL_LOG_BACKEND=y

    This option can only be enabled if CONFIG_LOG_MINIMAL=n

    CONFIG_LOG_MINIMAL can not be set to 'n' when CONFIG_NCS_SAMPLES_DEFAULTS=y

    However setting CONFIG_NCS_SAMPLES_DEFAULTS=n sees to have its own set of problems.

    I am still unable to get printk() output when the CONFIG_SHELL=y

  • 0 in reply to Allen

    Put these options in "prj.conf" to enable Shell and Log output via RTT. This will also enable printk() RTT output.

    CONFIG_NCS_SAMPLES_DEFAULTS=n
    CONFIG_SHELL=y
    CONFIG_SHELL_STACK_SIZE=1024
    CONFIG_SHELL_BACKEND_SERIAL=n
    CONFIG_SHELL_BACKEND_RTT=y

    CONFIG_LOG=y
    CONFIG_LOG_PRINTK=y
    CONFIG_LOG_BACKEND_UART=n
    CONFIG_SHELL_LOG_BACKEND=y
Related