Warning: Stack pointer is setup to incorrect alignment. Stack addr = 0xFFFFFFFF

[adam30504]

Hi.

I'm useing SDK 15.3 for testing DFU in nRF52832.
I've already porting DFU to project ble_app_uart_c.
now, I want to run BOOT project,and I'm useing project secure_bootloader.
in this project I choose secure_bootloader_ble_s132_pca10040 as my project.
after I run compiler sucess,I'm trying to load this BOOT to my bord.
But debug log shows "Warning: Stack pointer is setup to incorrect alignment. Stack addr = 0xFFFFFFFF"
and the loading seems fail.

I've tried some situation but it shows same problem.

1. load soft_device via nRFgo studio and load this BOOT via IAR
-> shows "Warning: Stack pointer is setup to incorrect alignment. Stack addr = 0xFFFFFFFF"

2. load soft_device via nRFgo studio and load my application via IAR
-> shows NRF_LOG_ERROR("No bootloader was found"); and then I load this BOOT
->show same message "Warning: Stack pointer is setup to incorrect alignment. Stack addr = 0xFFFFFFFF"

3. load soft_device via nRFgo studio and load BOOT hex via nRFgo studio
-> shoes error programing failed: This hex file has data in SoftDevice region.Try progeaming using "Program SoftDevice",or erease all before programing.

I don't know why I can't load this BOOT to my bord.
Is there's flash protect? how should I do?

[Øyvind]

Hello, 

Have you tried following the "Getting started with Nordic's Secure DFU bootloader" guide?

Kind regards,
Øyvind

[adam30504]

Yes, I'm on the Step D.

I've got zip file, trying loading BOOT to my bord.

[Øyvind]

First of all, have you tried flashing the Secure Bootloader using Segger Embedded Studio? Have a look at this answer from my colleague.

Secondly, you must merge the SoftDevice .hex with the secure bootloader .hex, then flash this using the Programmer app in nRF Connect for Desktop.

Let me know how this works for you.

Kind regards,
Øyvind

[adam30504]

Thanks your kindly help!

now, I'm use nRF Connect erase flash, load softdevice and bootloader

(the bootloader merged bootloader_setting.hex, it's from my application)

after this I try to use debugger with BOOT in IAR.

the warning message is still showing, and I still can't entry debugger.

like this post you've post.

by the way, If I merge bootloader+softdevice+application and use nrfjprog to load to my bord, it works fine.

If I use IAR and entry debugger with application, it works fine.

the problem seems on the BOOT loader.

[Øyvind]

Could you please tell what IAR version you are running? Please read the release notes of SDK v15.3.

Have you ensured that all settings are correct in IAR? e.g. this thread and this thread.

Going through the DFU tutorial, did you get any errors prior to Step D?

[Øyvind]

Hello again, 

A small update on your case. we've been able to reproduce your issue here. The issue seems to be related to a change we have done in SDK 15.3 on how it handles MBR. Have a look at my colleague Bjørn's answer.

The quick workaround for this is:

1. Use Segger Embedded Studio, which seemingly works as intended.
2. In IAR, Project options --> Debugger --> Setup --> Supress Download.
   1. You will need to load the project externally i.e. nrfjprog, then you'll be able to debug.

[adam30504]

Hi

as I followed your step

"In IAR, Project options --> Debugger --> Setup --> Supress Download.

1. You will need to load the project externally i.e. nrfjprog, then you'll be able to debug."

the problem seems solved!

now, my BOOT project can be entry debugger via IAR.

Thank you, again!

By the way, my IAR version is

IAR Embedded Workbench for ARM 8.11.2.13606

IAR Embedded Workbench shared components 8.0.8.4892