nrf52832 and S112

RE: nrf52832 and S112

Susheel Nuguru — Mon, 05 Dec 2022 08:49:22 GMT

Matjaz,

We do not have the resources to debug optimization/compiler specific related issues. Without the optimization if this works, and with optimizations it doesn't then it is something specific to your application and not the solution. There are some hints in the external sites on best practices for writing code to be optimization friendly.

RE: nrf52832 and S112

Matjaz1118 — Fri, 02 Dec 2022 14:25:38 GMT

Hi,

the project I sent has a compiler optimization turned off. If you change the optimization to optimize for size, the error should occur again.

RE: nrf52832 and S112

Susheel Nuguru — Fri, 02 Dec 2022 14:12:40 GMT

Hi, I j ust ran your project on nRF52832 DK with your project in PCA10040e directory and it worked just fine. No faults or errors.

RE: nrf52832 and S112

Matjaz1118 — Thu, 01 Dec 2022 10:10:45 GMT

Hi,

I am attaching the project.

devzone.nordicsemi.com/.../3312.Application.zip

RE: nrf52832 and S112

Jared — Wed, 30 Nov 2022 13:17:47 GMT

Hi,

Could you share your entire project so I could try to reproduce the issue?

Also, In the meantime, could you try doing the opposite by starting with a PCA10040 example and then modify it to use the S112 by changing the memory config, change include folder and load settings in project settings Segger?

regards

Jared

RE: nrf52832 and S112

Matjaz1118 — Tue, 29 Nov 2022 20:44:16 GMT

Hi,

So I checked the call stack and it seems that the function that causes the crash is sd_ble_gap_device_name_set (main c, line178). As I was having a hard time figuring out witch error code is reported, I turned off compiler optimization (before it was set to optimize for size). When I run debug session again, the before-mentioned function returned 0 and the blinky demo is now running!

But it would be nice if size optimization would work, as we only have 256 kB of flash available.

RE: nrf52832 and S112

Matjaz1118 — Tue, 29 Nov 2022 13:47:37 GMT

Thanks, Jared I will do this in the evening when I will have access to the dev board. I will report back the error code.

RE: nrf52832 and S112

Jared — Tue, 29 Nov 2022 13:40:43 GMT

Hi,

The error handler in app_error_weak.c is usually called when you call APP_ERROR_CHECK(err_code) and passing a non-zero err_code as parameter. So somewhere in your code, APP_ERROR_CHECK() is called with a non-zero return value which cause the program to go into the error handler. It would be nice if you could use breakpoints, the debugger and figure exactly what function that returns this non-zero return value.

regards

Jared

RE: nrf52832 and S112

Matjaz1118 — Tue, 29 Nov 2022 12:28:22 GMT

Hi Jared,

my program stops in error handler (app_error_weak.c) on line 100 (NRF_BREAKPOINT_COND;). I will post the call stack in the evening, as currently, I don't have the hardware with me.

I am aware, that nRF Connect SDK is currently the preferred SDK, but we already have some experience using nRF5SDK, so that is why this SDK has been chosen.

RE: nrf52832 and S112

Jared — Tue, 29 Nov 2022 12:05:02 GMT

Hi there,

You're preprocessor definitions looks ok.

What exactly do you mean by crash? Does it go into an error handler or does it hardfault? Can you share the call stack and use breakpoints and specify how far the program reach before it crashes?

Also, if you're starting a new project then I would recommend using nRF Connect SDK instead of nRF5SDK, as the former is our primary SDK with active development vs the nRF5SDK is only in maintenance mode.

regards

Jared