Segger Embedded Studio 6.30 causes crash if optimised

user102074 over 4 years ago

I'm developing for nRF52832, SDK 17.0.2 and softdevice S312 7.0.1.

After I upgraded from Segger Embedded Studio 6.22a to 6.30 I found that turning on any compiler optimisation causes a runtime error during initialisation of the softdevice. The reported error is NRF_ERROR_INVALID_PARAM.

The error seems to be related to ble_gap.h and calls to softdevice GAP initialisation functions. Perhaps something to do with the compiler's optimisation of the SVCALL macros.

I can switch between the two versions of SES, and I can confirm that the problem only occurs on SES version 6.30 and only when compiler optimisation is set to level 1 or higher.

Is this a Segger problem or is it a Nordic problem?

Thanks,
Barry

Top Replies

user102074 over 4 years ago +1

Thanks Kenneth. For anyone else reading this, another relevant discussion that I found is this one: https://devzone.nordicsemi.com/f/nordic-q-a/87736/segger-embedded-studio-latest-incompatible-with-nrf5…

0 user79167 over 4 years ago

Hello,

I just observed a similar problem with SES 6.30. A release version of the FW got stuck somewhere, not answering. The first problem when building the release version was a throwing a warning that was not seen before and not giving any sense. After some investigation I switched to SES 6.22a and the release version works ok, no warning in building.
There must be something wrong with SES 6.30 or some setting is missing. Based on the warning I got it looks like missing some nRF related definitions.

A debug version works ok.

Any advises, please?

Best regards,

peter
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 user102074 over 4 years ago in reply to user79167

Peter, if this is the same problem that I encountered then you can build a release version with SES 6.30 by turning off all compiler optimisation. Set compiler optimisation for the "Release "version to "None".

Regards, Barry.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 user2111 over 4 years ago

I know there are some issues with recent SES releases and the nRF5 SDK, e.g.:
https://devzone.nordicsemi.com/f/nordic-q-a/88123/build-environment-problem/368739#368739

We recommend to use the toolchain listed in the release notes for a specific nRF5 SDK, e.g.:

nRF5 SDK v17.1.0
------------------------
Release Date: August, 2021

...

The following toolchains/devices have been used for testing and verification:

- ARM: MDK-ARM version 5.25
- GCC: GCC ARM Embedded 9.2020-q2.major
- IAR: IAR Workbench 7.80.4
- SES: SES 5.42a
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 user79167 over 4 years ago

Hi Barry,

thanx for the suggestion. Setting the compiler optimization to none helped. Also the warning disappeared.

Best regards,

peter
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 user102074 over 4 years ago

Thanks Kenneth. For anyone else reading this, another relevant discussion that I found is this one:

https://devzone.nordicsemi.com/f/nordic-q-a/87736/segger-embedded-studio-latest-incompatible-with-nrf5-sdk/

Despite the statement that SDK v17.1.0 has not been tested with SES versions later than 5.42a, I have had no noticeable problems with my SDK 17 applications as I upgraded SES over the past 10 months all the way through to 6.22a. Seems like a number of people have had similar experiences. It looks like SES 6.30 introduced changes that were a step too far for SDK 17, so I'll stick at SES 6.22a.

Regards,
Barry
Cancel
Vote Up +1 Vote Down

Sign in to reply

Verify Answer

Cancel