How to fix UART behavior in segger?

[puff]

Still playing with my app. Since RTT (or whatever it was, when printf was printing info to segger debug console) was ruining the debug process, I just switched off RTT and disabled uart module. But now I need some way to print out some debug info. So, I connected an rx pin of my usb-serial interface to pin9 of 51822. However, printf still prints out to segger debug console, not to my usb-uart, and probably still causing crashes when run not in debug mode. Is there a way to check what could be wrong?

[puff]

I am playing with custom characteristic example from github, based on 10028 board, s130 softdevice. I had to import it to segger first. mdfind NRF_LOG_BACKEND_SERIAL_USES_RTT shows just email notifications from this site, so I am pretty much sure that there is no such a line in any file on my computer. I tried playing with project file several times, each time leadin to a hardfault. (I was editing it in segger text editing window and then I normally clicke reload button when building).

[puff]

what's strange: I can see app_uart_fifo.o among the object files, but I can't see app_uart.o - why is it so?

[Hung Bui]

I would suggest to use our SDK example in SDK v12. Then you can use this tutorial to convert a Keil project into SES.