PRINTK over SWD

RE: PRINTK over SWD

Nyameaama — Fri, 14 Jun 2024 17:19:06 GMT

So I was able to fix my issue. For my design I had not set up an external LRFC oscillator so I added some things to my prj.conf file to enable to internal oscillator. I added these lines:

CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y

CONFIG_CLOCK_CONTROL_NRF_K32SRC_500PPM=y

CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC_CALIBRATION=y

CONFIG_CLOCK_CONTROL_NRF_CALIBRATION_LF_ALWAYS_ON=y

RE: PRINTK over SWD

Nyameaama — Fri, 14 Jun 2024 16:53:56 GMT

Would you be able to test my configuration on your side?

RE: PRINTK over SWD

Nyameaama — Fri, 14 Jun 2024 16:53:27 GMT

This is the output from the RTT Terminal:

SEGGER J-Link V7.88j - Real time terminal output
SEGGER J-Link (unknown) V1.0, SN=1050051574
Process: JLinkExe

RE: PRINTK over SWD

Sigurd Hellesvik — Fri, 14 Jun 2024 13:45:42 GMT

In that case, i think i would recommend that you use logs instead of print, and use CONFIG_LOG_BACKEND_RTT.

Or you can simply use that along with CONFIG_LOG_PRINTK to not even have to change your printks to logs.

See Logging in nRF Connect SDK

RE: PRINTK over SWD

Nyameaama — Fri, 14 Jun 2024 13:02:41 GMT

Okay so I would like to debug and print statements to the console using printk. I have a custom board featuring nRF5340 and a programming interface that I connect to the DK in order to program it, using SWDIO, SWDCLK and RESET. I would like to print via SWDIO using RTT. I tried to follow this solution:

Setting up console over SWD interface

However my configuration just does not work

RE: PRINTK over SWD

Sigurd Hellesvik — Fri, 14 Jun 2024 12:44:04 GMT

Can you specify what you mean by "printk over SWD"?

RE: PRINTK over SWD

Nyameaama — Fri, 14 Jun 2024 12:11:15 GMT

Hello, I’m sorry but a forgot to add my pinctrl file. Everything builds and works I am just not able to use printk over SWD

pinctrl.dtsi

&pinctrl {
i2c0_default: i2c0_default {
group1 {
psels = <NRF_PSEL(TWIM_SCL, 1, 12)>, <NRF_PSEL(TWIM_SDA, 1, 14)>;
};
};

i2c1_default: i2c1_default {
group1 {
psels = <NRF_PSEL(TWIM_SDA, 0, 5)>, <NRF_PSEL(TWIM_SCL, 1, 2)>;
};
};

spi4_default: spi4_default {
group1 {
psels = <NRF_PSEL(SPIM_MISO, 1, 9)>,
<NRF_PSEL(SPIM_MOSI, 1, 8)>,
<NRF_PSEL(SPIM_SCK, 1, 7)>;
};
};

uart2_default: uart2_default {
group1 {
psels = <NRF_PSEL(UART_RX, 0, 24)>, <NRF_PSEL(UART_TX, 0, 25)>;
};
};

uart3_default: uart3_default {
group1 {
psels = <NRF_PSEL(UART_RX, 0, 21)>, <NRF_PSEL(UART_TX, 0, 19)>;
};
};

qspi_default: qspi_default {
group1 {
psels = <NRF_PSEL(QSPI_CSN, 0, 18)>,
<NRF_PSEL(QSPI_IO0, 0, 13)>,
<NRF_PSEL(QSPI_IO1, 0, 14)>,
<NRF_PSEL(QSPI_IO2, 0, 15)>,
<NRF_PSEL(QSPI_IO3, 0, 16)>,
<NRF_PSEL(QSPI_SCK, 0, 17)>;
};
};
};

RE: PRINTK over SWD

Sigurd Hellesvik — Fri, 14 Jun 2024 09:03:33 GMT

Hi,

I recommend the Nordic Developer Academy as an excellent place to start learning the nRF Connect SDK.

For how to change pins for your board, you need pinctrl.

Here is what our AI says about pinctrl:

The pinctrl (pin control) is a feature used in Nordic Semiconductor's nRF Connect SDK to manage the pin configurations of various peripherals on the device. It allows you to assign different pins to the peripherals based on states. The two standard states are default and sleep.

In the pinctrl node, pin configurations are organized in groups within each sub-node. Each group specifies a list of pin function selections in the psels property. For example, a group could specify the pin configurations for UART_TX and UART_RTS. A group can also specify shared pin properties common to all specified pins.

Here's an example of how pin configurations are being applied in the TWIM driver:

&pinctrl {
 i2c0_default_alt: i2c0_default_alt {
 group1 {
 psels = <NRF_PSEL(TWIM_SDA, 1, 13)>,
 <NRF_PSEL(TWIM_SCL, 1, 15)>;
 };
 };
 i2c0_sleep_alt: i2c0_sleep_alt {
 group1 {
 psels = <NRF_PSEL(TWIM_SDA, 1, 13)>,
 <NRF_PSEL(TWIM_SCL, 1, 15)>;
 low-power-enable;
 };
 };
};

In this example, the i2c0_default_alt and i2c0_sleep_alt nodes define the pin configurations for the I2C peripheral in its default and sleep states, respectively. The psels property in each group specifies the function (SDA or SCL) and pin number for each pin.

For more information, you can refer to the Nordic Semiconductor's DevZone forum and Nordic Semiconductor's Academy Course.