Softdevice asserts in release configuration flashed by SeS

[Mikl Scherbak]

I'm using Softdevice S132 V 7.0.2 with nrf52832 module. Project is in Segger Studio. Project runs in debug configuration as in debug or in non-debug mode. When changing to the release configuration and load it in debug mode it stops at 0xa64. Resetting the device makes it run normally.

[Jørgen Holmefjord]

Hi,

Have you debugged the application to see where the assert happens?

Which SDK version are you using?

Can you upload the project, for us to have a look at the differences between the build configurations?

Best regards,
Jørgen

[Jørgen Holmefjord]

Ok, lets start with the .emproject file and see what we can get from that.

After a reset, the device is able to pass the sd_softdevice_enable function call, even in release configuration?

[Mikl Scherbak]

Yes, after reset or flashed by j-flash light it works normally build in release configuration. I could not insert a file so here is a link to it .emproject

[Jørgen Holmefjord]

Your link say I need to request access. Can you send me the file in a PM here on DevZone, or provide a link with direct access?

I can also convert this ticket to private, in case you do not want to share the file in public forum.

[Mikl Scherbak]

emProject.zip

[Jørgen Holmefjord]

I'm not able to see any obvious things in the project file that should cause this, but there are some differences.

Is the issue related to unistop or unistop_boot project?

• I see that for the unistop_boot, log and RTT sources are excluded from build in release mode, but I assume this would have caused compile errors if this was an issue.
• The "Additional load file type[0] is set to ihex for release, while it is set to hex for debug.
• The optimization levels are different. Have you tried setting optimization to the same level for both debug and release to test if this makes any difference?

[Mikl Scherbak]

Issue is related to unistop. There are no build errors. I'v tried to change optimization levels but it did not help

[Jørgen Holmefjord]

I cannot see anything else in the project that should cause any asserts. Is there any additional information you can give us regarding the assert? It is not much more we can say about it without being able to reproduce the issue on our end.