• State Suggested Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 25 subscribers
  • Views 143 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 289747
Options

Zephyr buletooth sample hci_pwr_ctrl don't have debug print in nrf52840dk.

user112412

When I try to debug hci_pwr_ctrl in Zephyr/buletooth/sample using segger embedded studio, debug terminal don't have output of printk function, which based on nrf52840dk.

Only have the following message, and code always keep running.

So, I should how to solve it.

Thanks for help.

Parents
  • 0

    Hi,

    When you use UART for HCI you cannot use the same UART for logging. So I suggest you use RTT instead by adding somethin like this to prj.conf:

    # Segger RTT
CONFIG_USE_SEGGER_RTT=y
CONFIG_RTT_CONSOLE=y
CONFIG_UART_CONSOLE=n
CONFIG_LOG_BACKEND_RTT=y
CONFIG_LOG_BACKEND_UART=n

    You could also use a second UART either for HCI or logging, but note that the onboard debugger only do USB-UART bridging for a single UART.

Reply
  • 0

    Hi,

    When you use UART for HCI you cannot use the same UART for logging. So I suggest you use RTT instead by adding somethin like this to prj.conf:

    # Segger RTT
CONFIG_USE_SEGGER_RTT=y
CONFIG_RTT_CONSOLE=y
CONFIG_UART_CONSOLE=n
CONFIG_LOG_BACKEND_RTT=y
CONFIG_LOG_BACKEND_UART=n

    You could also use a second UART either for HCI or logging, but note that the onboard debugger only do USB-UART bridging for a single UART.

Children
Related
Terms of service