printf output is not displayed during debug

RE: printf output is not displayed during debug

Arie — Sun, 15 Jul 2018 15:06:06 GMT

After I haven’t found a solution in Google and didn’t receive an answer neither from the ARM nor from the Nordic support, I myself solved the problem, as follows:

In addition to known configuration, you must configure the TRACECONFIG register in your code:

		NRF_CLOCK->TRACECONFIG = (CLOCK_TRACECONFIG_TRACEMUX_Parallel << CLOCK_TRACECONFIG_TRACEMUX_Pos) |
		(CLOCK_TRACECONFIG_TRACEPORTSPEED_32MHz << CLOCK_TRACECONFIG_TRACEPORTSPEED_Pos);

🙂Enjoy!

RE: printf output is not displayed during debug

Arie — Wed, 04 Jul 2018 12:26:12 GMT

Agree. Thanks very much.

RE: printf output is not displayed during debug

Susheel Nuguru — Wed, 04 Jul 2018 12:09:09 GMT

native printf are never easy thing to support PC standard I/O for embedded solutions. They always remain tricky since embedded solutions does not have conventional IO capabilities. Neither do they have display. Hence all the prints needed to be rerouted from standard out to serial ports or debug ports.

RE: printf output is not displayed during debug

Arie — Wed, 04 Jul 2018 11:48:58 GMT

Thanks Aryan. I know this post and tried configuring the Trace before applying to support. This doesn’t work.

Surely, I can get output another way (and got it through the SEGGER J-Link RTT viewer), but I believe that such basic function as printf using native IDE should work (e.g. as in Code Composer Studio of TI).

RE: printf output is not displayed during debug

Susheel Nuguru — Wed, 04 Jul 2018 08:00:26 GMT

You need to configure, the Trace port to be able to do that, I think. You can follow this post if you want to try it.

I do not see why you cannot use retarget.c file and redirect the log to the uart com port. It really simple to do. It is really really small benefit of getting the logs to Keil Debug (printf) viewer.

RE: printf output is not displayed during debug

Arie — Tue, 03 Jul 2018 19:59:54 GMT

I use it in J-LINK/ J-Trace Cortex mode.

RE: printf output is not displayed during debug

Susheel Nuguru — Tue, 03 Jul 2018 19:53:39 GMT

Are you running this in simulator mode? if not, printf executing on nrf chip will not show you anything on the Keil console as far as i know.

RE: printf output is not displayed during debug

Arie — Tue, 03 Jul 2018 19:47:29 GMT

Thanks. I removed it, but this didn't help.

RE: printf output is not displayed during debug

Susheel Nuguru — Tue, 03 Jul 2018 19:28:37 GMT

if you have retarget.c file in your project, you need to remove it, as it is overwriting the functions that printf uses to redirect the logs from standard output to uart.

RE: printf output is not displayed during debug

Arie — Tue, 03 Jul 2018 19:17:12 GMT

Thanks,

I took the uart project as an example. I’m not interested specifically in uart or any other peripherals.

I just want my message, e.g. printf("Hello world!\r\n"); to be displayed in the Debug (printf) Viewer of the uVision.

RE: printf output is not displayed during debug

Susheel Nuguru — Tue, 03 Jul 2018 18:01:55 GMT

The UART pin mapping in the SDK are mapped to a particular DK as per the project. I am not how the mapping of UART pins are done from your Rigado BMD-300 module onto the custom board. Look into the code of UART initialization in your project and check that the UART pin number matches the UART pin on your board.