SDK_ERROR observed

RE: SDK_ERROR observed

Vidar Berg — Tue, 13 Jun 2023 10:15:20 GMT

Yes, the bootloader includes the DFU functionality. See 'DFU bootloader examples' for more details.

RE: SDK_ERROR observed

sa.qw — Mon, 12 Jun 2023 16:11:51 GMT

ok, then i need to debug the bootloader issue.

Also, is the bootloader pre-configured with DFU functionality in the nRF52810 chip (not the development kit) ?

RE: SDK_ERROR observed

Vidar Berg — Mon, 12 Jun 2023 14:54:37 GMT

Yes, this is the bootloader we include in this SDK.

RE: SDK_ERROR observed

sa.qw — Mon, 12 Jun 2023 14:33:43 GMT

Hi Vidar,

Can you please confirm it ?

Thank You

RE: SDK_ERROR observed

sa.qw — Mon, 05 Jun 2023 11:30:23 GMT

Hi Vidar,

Is the dfu/secure_bootloader is the one that i must use to support DFU?

RE: SDK_ERROR observed

Vidar Berg — Mon, 05 Jun 2023 11:26:07 GMT

Hi,

Yes, you need a bootloader to support DFU.

RE: SDK_ERROR observed

sa.qw — Mon, 05 Jun 2023 11:25:12 GMT

Hi Vidar,

Thank You for the information.

I would like to know is the dfu/secure_bootloader is mandatory to perform the DFU over BLE ?

From multiple forums I realized that its is required but i guess the DFU over BLE can work even without dfu/secure_bootloader.

RE: SDK_ERROR observed

Vidar Berg — Thu, 01 Jun 2023 14:19:13 GMT

Hi,

This is as expected. The example is configured to enter System OFF (deep sleep) after 3 minutes of inactivity, which is not possible to do when the chip is in debug interface mode. If you disconnect the debugger the chip will power down after 3 minutes.

RE: SDK_ERROR observed

sa.qw — Thu, 01 Jun 2023 14:00:32 GMT

Hi Vidar,

Ok, let me try.

In the mean time I encountered another issue with ble_app_uart application.

I didnt perform any change to the sdk or application, & flashed pca10040e project to nRF52832 ( I believe this is do-able ).

The application crashes after ~3mins. Below is the crash details.

RE: SDK_ERROR observed

Vidar Berg — Thu, 01 Jun 2023 13:20:38 GMT

Hi,

This project has the correct memory configuration to run on the nrf52810. Can you try to debug with the bootloader project and see if you can find out where it crashes?

RE: SDK_ERROR observed

sa.qw — Thu, 01 Jun 2023 13:16:31 GMT

Hi Vidar,

I'm using the project at location examples\dfu\secure_bootloader\pca10040e_s112_ble\ses.

And even the flag DEVELOP_IN_NRF52832 is defined in the project.

RE: SDK_ERROR observed

Vidar Berg — Thu, 01 Jun 2023 08:05:42 GMT

Hi,

Then the problem isn't with the application, but with the bootloader. Please double check that the bootloader project you selected is configured to run on the nRF52810 and not some other nRF52 variant.

RE: SDK_ERROR observed

sa.qw — Thu, 01 Jun 2023 05:14:37 GMT

Hi Vidar,

[quote userid="4240" url="~/f/nordic-q-a/99943/sdk_error-observed/428425"]Are you able to run the application if you only program the Softdevice and application without the bootloader?[/quote]

Yes.

[quote userid="4240" url="~/f/nordic-q-a/99943/sdk_error-observed/428425"]Because the stack pointer is well beyond the valid address range for RAM (which ranges from 0x20000000 to 0x20006000).[/quote]

[quote userid="4240" url="~/f/nordic-q-a/99943/sdk_error-observed/428425"]It's not reaching main(), but is it reaching the application's reset handler?[/quote]

Its not even reaching the application's reset handler, i tried by keeping a breakpoint in reset handler.

[quote userid="4240" url="~/f/nordic-q-a/99943/sdk_error-observed/428425"]The bootloader will not be able to boot the application unless you also program a valid bootloader settings page along with it[/quote]

Thanks for the information but i was expecting the project dfu\secure_bootloader will have the valid bootloader settings and while flashing the nordic device via JLink, it also writes the bootloader settings as well. If this is not the case, then

can bootloader setting be written via JLink ?
Is DFU Secure Bootloader MANDATORY to perform DFU via BLE ?
1. As, i was trying to add bootloader to enable the DFU via BLE

I guess the issue is with the bootloader setting, as i erased the complete flash via JLink and only flashed the Application + Soft Device via JLink, and i have it working.

RE: SDK_ERROR observed

Vidar Berg — Wed, 31 May 2023 11:20:39 GMT

Hi,

[quote user="sa.qw"]Can you help me with some pointer on how to debug it or how you will debug it.[/quote]

Are you able to run the application if you only program the Softdevice and application without the bootloader?

[quote user="sa.qw"]Also how you got to know that its a corrupted/invalid stack pointer, as I least expect it because i have a simple application and the execution never comes the Application, it crashes even before it.[/quote]

Because the stack pointer is well beyond the valid address range for RAM (which ranges from 0x20000000 to 0x20006000).

[quote user="sa.qw"]I have reasons to say that its not occurring in or due Application as execution never reaches there.[/quote]

It's not reaching main(), but is it reaching the application's reset handler?

[quote user="sa.qw"]I first use the project dfu\secure_bootloader to write the bootloader (+soft device), then use my project to write the application + soft device. I hope its not an issue.[/quote]

The bootloader will not be able to boot the application unless you also program a valid bootloader settings page along with it. See Combine application, bootloader and softdevice image - Bootloader setting.

RE: SDK_ERROR observed

sa.qw — Tue, 30 May 2023 14:48:23 GMT

Hi Vidar,

Sorry to say but I couldn't upload the complete code base.

Can you help me with some pointer on how to debug it or how you will debug it.

Also how you got to know that its a corrupted/invalid stack pointer, as I least expect it because i have a simple application and the execution never comes the Application, it crashes even before it.

I have reasons to say that its not occurring in or due Application as execution never reaches there.

Also, yes I have also added the bootloader.

And FYI, am uploading the binaries (bootloader / soft device / application) though JLINK !

I first use the project dfu\secure_bootloader to write the bootloader (+soft device), then use my project to write the application + soft device. I hope its not an issue.

RE: SDK_ERROR observed

Vidar Berg — Tue, 30 May 2023 14:44:40 GMT

Do you have a bootloader present when you're debugging this? In other words, are you sure the crash is occuring in the application and not in the bootloader?

RE: SDK_ERROR observed

Vidar Berg — Tue, 30 May 2023 14:40:01 GMT

Sorry, I'm not seeing any errors in your project file or in flash_placement.xml. Are you able to upload the whole project so I can try to debug it here?

RE: SDK_ERROR observed

sa.qw — Tue, 30 May 2023 14:29:28 GMT

Hi Vidar,

Uploading by project file.

devzone.nordicsemi.com/.../5153.ble_5F00_app_5F00_uart_5F00_pca10040e_5F00_s112.zip

*Zipping it as it doesn't allow me to upload .emProject file

RE: SDK_ERROR observed

Vidar Berg — Tue, 30 May 2023 09:38:56 GMT

Hello,

Please upload your project file too (*.emProject). From the images you posted I see that you have a corrupted/invalid stack pointer.

RE: SDK_ERROR observed

sa.qw — Fri, 26 May 2023 15:47:04 GMT

Hi Vidar,

Below are the details with SES v5.42a :-

If I continue execution, it go to the address 0x781b330a and on every continue be there.

Also, in the release notes, SES v4.50 is mentioned. Hence, I even tried with v4.50 and below are the details on crash:-

And continuing the execution, below are register values (same as that of SES v5.42a

Also, using the project saadc_pca10040e, works fine (on all SES versions).

The above logs are for project ble_app_uart_pca10040e_s112.

I even tried to place a breakpoint at the first instruction in Reset_Handler() at instruction "b nRFInitialize", even then the execution didnt stop at this first instruction and instead directly shows the instruction at address 0xA60.

From few posts it looks like it could be related to the Flash Placement (note - I didn't change it), hence attaching the flash_placement.xml.

devzone.nordicsemi.com/.../2844.flash_5F00_placement.xml

RE: SDK_ERROR observed

Vidar Berg — Fri, 26 May 2023 11:05:21 GMT

No problem. The disassembly view shows that the program hangs in the MBR's hardfault handler. If you make the debugger continue execution, you should see that the program execution ends up in the hardfault handler declared in the application.

Can you post a screenshot of the CPU registers when the CPU is halted at 0xa60? It may give us a clue as to why the exception was raised.

[quote user="sa.qw"]I'm using the Segger Embedded Studio v7.22, nRF5 SDK v17.0.2 and application ble_app_uart[/quote]

I recommend you use an older version to avoid issues with our example projects. The SDK 17.x was tested with Embedded studio version v5.42a (mentioned in the release notes), and there were some breaking changes introduced after v6.20

RE: SDK_ERROR observed

sa.qw — Fri, 26 May 2023 04:37:29 GMT

Thanks Vidar.

That helps.

Also, recently i ran into a new problem.

I changed the Optimization Level from "Level 2 for size" to "Level 0", the build failed due to size.

Then i changed back the Optimization Level to "Level 2 for size".

But after that when I start the debugging, the execution never halts at main().

Instead it Halts at 0xa60 location

I guess it has crashed as the output log mentions about the HardFault:-

Preparing target for download
Executing Reset script TargetInterface.resetAndStop()
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.
Downloading ‘s112_nrf52_7.2.0_softdevice.hex’ to J-Link
Programming 2.7 KB of addresses 00000000 — 00000aff
Programming 95.9 KB of addresses 00001000 — 00018feb
J-Link: Flash download: Bank 0 @ 0x00000000: 1 range affected (32768 bytes)
J-Link: Flash download: Total: 1.209s (Prepare: 0.079s, Compare: 0.083s, Erase: 0.670s, Program & Verify: 0.352s, Restore: 0.022s)
J-Link: Flash download: Program & Verify speed: 91 KB/s
Download successful
Downloading ‘ble_app_uart_pca10040e_s112.elf’ to J-Link
Programming 27.3 KB of addresses 00019000 — 0001fd44
Programming 0.1 KB of addresses 0001fd48 — 0001fdbb
J-Link: Flash download: Bank 0 @ 0x00000000: Skipped. Contents already match
Download successful
Stopped by vector catch HardFault FORCED IACCVIOL BusFault STKERR

I'm using the Segger Embedded Studio v7.22, nRF5 SDK v17.0.2 and application ble_app_uart

Can you please help here as am stuck on this one for quick long.

RE: SDK_ERROR observed

Vidar Berg — Wed, 24 May 2023 08:54:59 GMT

No problem.

I'm not aware of any project settings that will make SES output a dissambly file, but you can view it by right clicking on the executable (or source file) and select "view disassembly".

RE: SDK_ERROR observed

sa.qw — Wed, 24 May 2023 03:06:27 GMT

Thank You Vidar.

I was able to see it by checking the memory address, but this approach is even better.

Also, Vidar can you help me to generate disassembly file (*.dis) in Segger Embedded Studio which will help to to debug & view the complete code in disassembly.

I know that the --disassemble, can be used to generate the disassembly but i didnt get the option/place to add this and i guess the Segger Embedded Studio must already have the feature to generate it.

RE: SDK_ERROR observed

Vidar Berg — Mon, 22 May 2023 11:32:50 GMT

Hello,

Please right click on the 'p_file_name' variable highlighted below and select 'string'. The value field will then display the file path to the file where the code assert was raised. The error occurred at line 1213 (0x4bd) in this file, and the error code was 0x11 (NRF_ERROR_BUSY).

Best regards,

Vidar