nrF5340 network processor RTT and debug UART nrf Connect SDK v1.5.0

[Alex Rawstorne]

Hi,

I was using the  die temperature measure example you gave running on the network core. I am using SDK 1.5.0 and 1.4.0 and can't seem to get any debug out from the UART or via RTT. My proj.conf file has :

CONFIG_GPIO=y
CONFIG_SERIAL=y
CONFIG_SENSOR=y
CONFIG_TEMP_NRF5=y

CONFIG_PRINTK=y
CONFIG_CONSOLE=y
CONFIG_LOG=y
CONFIG_STDOUT_CONSOLE=y
CONFIG_RTT_CONSOLE=y
CONFIG_USE_SEGGER_RTT=y

Can't get anything working on the RTT or uart via printk or printf.  I was able to get the temperatures by watching val but not sure why printk isn't working. The debugging sort of works as I can step through code and I did program the dummy app to enable the network core. I'm using the standard DTS file for the network processor on the PDK. Also tried the log module with LOG_INF and this comes up with a compile error that the __log_level is undeclared. I tried the same project but on a nrf52833 kit and it works fine. I then tried the rpmsg sample you provide and lo and behold couldn't get the UART or RTT working either ( I tried it last year and it did seem to work then). I also looked at the levels on P0.25 and P0.26 with a scope and they are low with no activity.  Any ideas where I'm going wrong?

[Alex Rawstorne]

Hi Amanda, 

It is 0.8.0. I have connected the wires for the UART P0.24, P0.25  to P0.20 and P0.22. I also shorted P0.20 and P0.22 beforehand to ensure I was getting output on the terminal to make sure I had the right COM port. I sort of got it working now with Jlink RTT viewer by selecting the NETWORK processor. Still no UART output though. I think that the problem is in Segger that by default it connects the JLink to the app processor and not the NW processor.

Regards

Alex

[Amanda Hsieh]

Hi Alex, 

Could you try P0.25 and P0.26 as the doc suggested? Also, see this post. 

-Amanda H.

[Alex Rawstorne]

Hi Amanda,

Sorry, my mistake Pins P0.25 and P0.26. I checked with a scope and neither P0.25 and P0.26 were high as per above. How do you tell Segger ES to set the debugger to the network core ?

Regards 

Alex

[Amanda Hsieh]

Hi Alex,

Alex Rawstorne said:

How do you tell Segger ES to set the debugger to the network core ?

See this https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_nrf5340.html#programming-the-network-sample-from-ses

-Amanda H. 

[Alex Rawstorne]

Hi Amanda,

Thanks. From what i understand this is how you merge an app project and nw project. I want to debug my nw project using SES. I have programmed the blank app application to enable the nw processor. I then load my nw application (in this case Temperature) and then run the debugger, which runs. I can watch the appropriate variables but I don't see debug output in the UART window or the debug window. If I stop the debugger and run Jlink RTT viewer with the NW core I am able to see the RTT output. So in a nutshell when I'm debugging in SES I can't see this debug output even when the debugger is running.

Alex 

[Amanda Hsieh]

Hi Alex, 

You might need to add CONFIG_UART_CONSOLE=n. If you still have the issue, are you able to get the RTT in SES with radio test? I add the following configs into the prj.conf of radio_test to test on the nw core and load empty_app_core to the app core, and I can see the SES RTT. 

###########
CONFIG_USE_SEGGER_RTT=y
CONFIG_RTT_CONSOLE=y
CONFIG_UART_CONSOLE=n

###########

-Amanda H.