nrf52 DK is On but Not Advertising

RE: nrf52 DK is On but Not Advertising

Karl Ylvisaker — Fri, 29 Jan 2021 07:55:38 GMT

NRF_LOG_BACKEND_RTT_ENABLED should be defined to 1 in the sdk_config if you intend to use the debug terminal ( which uses RTT ), please revert this change.

Could you answer the other questions in my previous comment as well?

Looking forward to resolving this issue together,

Best regards,
Karl

RE: nrf52 DK is On but Not Advertising

jasonterance — Fri, 29 Jan 2021 04:32:27 GMT

I tried changing

NRF_LOG_BACKEND_RTT_ENABLED

to 0 but nothing changes. There's still nothing in the debug terminal.

RE: nrf52 DK is On but Not Advertising

Karl Ylvisaker — Thu, 28 Jan 2021 07:47:04 GMT

Hello Jason,

[quote user="jasonterance"]I defined DEBUG in the preprocessor defines, but there is still no output in the logger.[/quote]

Just to confirm, are you not seeing any output to your logger backend? Not even 'Template example started.'?
Could you go ahead and add a NRF_LOG_INFO line with some text right after your call to the log_init function, to see if this is displayed in the logger output?

[quote user="jasonterance"].Just to make sure, where should I see NRF_LOG_INFO("") ; functions? Do they output to the debug terminal?[/quote]

This depends on which logger backend you have enabled for the nrf_log module. The module may output its logs to either UART, RTT, CLI, or FLASH - the default behavior of the example repository you linked in your initial ticket uses the RTT backend, which means that you should be able to see the loggers output either in the debug terminal or using the RTT Viewer application by Segger. Have you changed from the default backend, or do you still have it configured to use the RTT backend in your sdk_config file?

[quote user="jasonterance"]Also, I tried to toggle LED 4 with nrf_gpio_pin_toggle(LED_4); at the end of main but nothing happens, so it seems unresponsive or stuck.[/quote]

Yes, this likely means that the application encounters an error during its initialization or startup, and thus never gets to the toggling, since the default error handling is to reset the application.
If we can manage to get your logger module up an running we will immediately be told which function it is that returns the error, so I think we should focus on getting that up and running first.

Best regards,
Karl

RE: nrf52 DK is On but Not Advertising

jasonterance — Wed, 27 Jan 2021 19:27:35 GMT

Hey Karl, I defined DEBUG in the preprocessor defines, but there is still no output in the logger.Just to make sure, where should I see NRF_LOG_INFO("") ; functions? Do they output to the debug terminal? Also, I tried to toggle LED 4 with nrf_gpio_pin_toggle(LED_4); at the end of main but nothing happens, so it seems unresponsive or stuck.

Thank you,

Jason

RE: nrf52 DK is On but Not Advertising

Karl Ylvisaker — Tue, 26 Jan 2021 08:13:55 GMT

Hello jasonterance,

[quote user=""]Thank you for all the examples, by the way. They're very helpful. Thanks in advance![/quote]

No problem at all, I am happy to hear that you have found the examples very helpful!

[quote user=""]However, when I build and run everything, nothing is advertised.[/quote]

Could you elaborate on this a bit further? Are you seeing anything output to your logger backend when you run the program?
Does the device reset at any point, or does it seem unresponsive / stuck when you run your program?
Could you also verify for me that you have defined DEBUG in your preprocessor defines, like shown in the included image?

This will produce a detailed error message to the logger output in the case that an error code != NRF_SUCCESS is passed to an APP_ERROR_CHECK, instead of just resetting the device right away(which is the default error handling).

I suspect that something might have gone wrong during your services declaration, and that the device thus never gets passed that part in your code. If this is the case you should see an output to your logger backend when this occurs.

[quote user=""]I have already flashed the S132 SoftDevice (At least, I'm pretty sure)[/quote]

The SDK examples for SES are all configured to flash the SoftDevice as well, so I too would think that this is covered since you are using the BLE template example as your foundation.

Looking forward to resolving this issue together!

Best regards,
Karl