unable to print debug logs in my custom board

RE: unable to print debug logs in my custom board

sakib — Mon, 22 Jun 2020 09:37:02 GMT

sorry for that will create a new one

RE: unable to print debug logs in my custom board

awneil — Mon, 22 Jun 2020 09:35:16 GMT

What does this have to do with the rest of this thread?

RE: unable to print debug logs in my custom board

sakib — Sun, 21 Jun 2020 16:41:22 GMT

Hi,
we required an NFC tap to pair the Bluetooth feature in our product. our aim/application is, when a user taps his/her smartphone onto the antenna present on the product/device, it should start pairing, and as soon as the BT gets paired a window should appear onto the smartphone asking the user to enter a password/authentication key. if the entered password doesn't match the preset password, the paired board/device should get disconnected.

we have integrated the "ble_nfc_pairing_reference" example from the SDK into our application code and it seems to satisfy most of our application requirement except one.

the path where the example is present in the SDK
\nRF5_SDK_15.3.0_59ac345\examples\ble_peripheral\experimental\ble_nfc_pairing_reference

problem:- the example doesn't seem to ask for an authentication key when the BT is getting paired.

in addition, we are developing a customized Bluetooth application for this feature.

in short, our aim is to provide better security of the product so that a user would not be able to enter into the device just by doing tap to pair.

please guide us with the best possible option to achieve our requirements.

thanks
sakib

RE: unable to print debug logs in my custom board

awneil — Tue, 21 Apr 2020 09:32:53 GMT

[quote userid="89683" url="~/f/nordic-q-a/60390/unable-to-print-debug-logs-in-my-custom-board/245775"]do I have to use these functions[/quote]

Of course, you don't have to - you can write it all from scratch if you really want to.

[quote userid="89683" url="~/f/nordic-q-a/60390/unable-to-print-debug-logs-in-my-custom-board/245775"]won't these RTT debugs have an effect on other time constraint applications[/quote]

RTT has far less impact that doing it over the UART!

With RTT, all your code does is write to a RAM buffer. The J-Link then reads the RAM directly - so there's no CPU resource consumed.

https://www.segger.com/products/debug-probes/j-link/technology/about-real-time-transfer/

RE: unable to print debug logs in my custom board

sakib — Tue, 21 Apr 2020 09:17:42 GMT

hi,

thanks for the clarification awneil, just for confirmation sake, do I have to use these functions for debugging as per my setup and design? or are there any better ways to debug my application with the same design and setup.

my concern is won't these RTT debugs have an effect on other time constraint applications of the product like BLE, NFC, etc?

thanks

sakib

RE: unable to print debug logs in my custom board

awneil — Tue, 21 Apr 2020 08:15:29 GMT

[quote userid="89683" url="~/f/nordic-q-a/60390/unable-to-print-debug-logs-in-my-custom-board/245753"]functions like SEGGER_RTT_WriteString(),SEGGER_RTT_printf()[/quote]

Those are just the low-level functions - NRF_DEBUG_LOG() sits above them.

NRF_DEBUG_LOG() is agnostic to the underlying transport used.

RE: unable to print debug logs in my custom board

sakib — Tue, 21 Apr 2020 08:07:34 GMT

Hello, Simon

I am able to print the logs using the j-link RTT viewer.I'd follow the below-linked blog

https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/debugging-with-real-time-terminal

I think the RTT requires/follows different sets of functions like SEGGER_RTT_WriteString(),SEGGER_RTT_printf() etc to print the logs.

My question is, is it not possible to print the logs using NRF_DEBUG_LOG() through RTT viewer?

thanks

sakib

RE: unable to print debug logs in my custom board

awneil — Tue, 21 Apr 2020 08:04:53 GMT

Of course, there are other techniques which use the SWD pins in a "generic" way.

And there's also SWO ...

RE: unable to print debug logs in my custom board

Simonr — Tue, 21 Apr 2020 07:59:23 GMT

Thank you for pointing that out Andrew, I have edited my reply to specify J-Link 🙂

RE: unable to print debug logs in my custom board

awneil — Tue, 21 Apr 2020 07:26:33 GMT

[quote userid="75734" url="~/f/nordic-q-a/60390/unable-to-print-debug-logs-in-my-custom-board/245689"]The RTT logger only requires the programmer pins (SWDIO/SWDCLK) [/quote]

It also requires a J-Link - it is a proprietary Segger think, not available with other debug probes.

[quote userid="75734" url="~/f/nordic-q-a/60390/unable-to-print-debug-logs-in-my-custom-board/245689"]P0.09 and P0.10 are configured as NFC pins by default. You'll need to configure these as GPIOs[/quote]

Good point!

RE: unable to print debug logs in my custom board

Simonr — Tue, 21 Apr 2020 05:50:37 GMT

I suggest you use the RTT logger for debug logging instead. The RTT logger only requires the programmer pins (SWDIO/SWDCLK) connected to the J-Link debugger. In order to enable the RTT instead of the UART, you can set NRF_LOG_BACKEND_RTT_ENABLED to 1 and NRF_LOG_BACKEND_UART_ENABLED to 0 in sdk_config.h.

I took a look at your design and I can't see anything in particular that poses a problem. One thing though. P0.09 and P0.10 are configured as NFC pins by default. You'll need to configure these as GPIOs to use them as such in your project settings.

Best regards,

Simon

RE: unable to print debug logs in my custom board

sakib — Mon, 20 Apr 2020 10:17:04 GMT

hello, Simon,

correction:- I verified the usage of UART with the design engineer, it's used for sending data to another module(refer U2 in the schematic design)

so probably it can't be used to send/receive debugs.

can you please go through the design and let me know what are the other options I have for viewing NRF_DEBUG_LOG() outputs.

the custom board is connected through USB(refer to J9 in the design pdf that I attached in the first query) and another header with jlink is connected at j6.

thanks

sakib

RE: unable to print debug logs in my custom board

Simonr — Mon, 20 Apr 2020 08:50:17 GMT

How is the custom board connected to the computer? And specifically, how is the UART pins connected to the DK/J-Link/computer?

I see that the UART RX pin in your design is set to P0.07 instead of the "default" P0.08. Have you edited the pin settings in your project as well?

Best regards,

Simon

RE: unable to print debug logs in my custom board

sakib — Sun, 19 Apr 2020 05:30:20 GMT

hello awneil,

[quote userid="6462" url="~/f/nordic-q-a/60390/unable-to-print-debug-logs-in-my-custom-board/245354"]Before going to the custom board, did you have it working on a Dev Board?[/quote]

yes, everything is working fine in the case of Dev board.

my aim is to print log through UART.

the NRF_LOG_INIT() and NRF_LOG_DEFAULT_BACKENDS_INIT() functions are called at the start of the main.NRF_LOG_PROCESS() is present inside the infinite while loop.below are the macros enabled relating to UART.

NRF_LOG_BACKEND_UART_ENABLED, NRF_LOG_ENABLED, NRF_LOG_DEFERRED, NRF_FPRINTF_ENABLED are all set to 1

NRF_LOG_BACKEND_UART_TX_PIN(set as 6), NRF_LOG_BACKEND_UART_BAUDRATE(set as 115200).

thanks

sakib

RE: unable to print debug logs in my custom board

awneil — Sat, 18 Apr 2020 21:35:13 GMT

Before going to the custom board, did you have it working on a Dev Board?

Are you sending the NRF_LOG_INFO output via UART or RTT ?

[quote userid="89683" url="~/f/nordic-q-a/60390/unable-to-print-debug-logs-in-my-custom-board"].Processor always call NRF_LOG_PROCESS[/quote]

Where, exactly, is it called?

https://devzone.nordicsemi.com/f/nordic-q-a/34666/nrf5-sdk-v15-0-0-bug-report-incorrect-use-of-nrf_log_process-in-ble_app_uart-peripheral-example-among-others