Hard fault with enabling of softdevice

RE: Hard fault with enabling of softdevice

Sequoia — Tue, 25 Apr 2023 07:59:11 GMT

Hey Einar,

Sorry for the late reaction.

I messed around with some of the Preprocessor Definitions and the addation of NO_VTOR_CONFIG finaly did the trick. The code runs stable through the startup sections now and reaches the nain loop.

I tried adding NO_VTOR_CONFIG before when i was diiging in to the essentials needed for enabling the softdevice, but then it didnt work. So i wonder why it was the key stone this time.

The other preprocessor definitions i use are:

APP_TIMER_V2
APP_TIMER_V2_RTC1_ENABLED
CONFIG_GPIO_AS_PINRESET
CONFIG_NFCT_PINS_AS_GPIOS
ENABLE_SWO
FLOAT_ABI_HARD
NO_VTOR_CONFIG
NRF52
NRF52832_XXAB
NRF52_PAN_74
S132
NRF_SD_BLE_API_VERSION=7
SOFTDEVICE_PRESENT

I can sent the other files if you are stil interested in the problem, but it is working for me now, so my problem is solved.

RE: Hard fault with enabling of softdevice

Einar Thorsrud — Thu, 20 Apr 2023 13:55:27 GMT

That is interesting. I am also wondering about the other preprocessor defines and linker configuration. If it is difficult to find, perhaps you can upload your Keil and Segger projects here so that I can have a look? Not the code, just the project files (but please include all, as for instance with Segger, the linker configuration is in a separate xml file).

RE: Hard fault with enabling of softdevice

Sequoia — Thu, 20 Apr 2023 13:51:34 GMT

Hi Einar,

We use the nRF5 SDK files as a submodule in the Git repo of the project. We checked the file paths and the adds of the .c files in the project. There dont seem to be any differences there.
I load the softdevice out of the SDK folder in the Git repo.

When we ran through the differencves we had'nt thought off, indeed the precompiler definitions came to mind. In Segger these seem to be called Preproscessor Definitions.
In here we found some differences, those were the inclusion of difinitions:
CONFIG_NFCT_PINS_AS_GPIOS,
NRF_SD_BLE_API_VERSION=7,
S132,
__HEAP_SIZE=8192,
__STACK_SIZE=8192

I included these definitions under the Preprocessor Definitions in my Segger project and this seemed to make a difference.
For a moment a came pass the SVC #16 call and out of the function also pass the Critical Region part. Which seemed to point out that the Softdevice is working.
After that with a bit of debugging again i get a new fault:

Which stil seems to point to a problem with SVC adresses, but is i think an improvement over the hard fault.

RE: Hard fault with enabling of softdevice

Einar Thorsrud — Thu, 20 Apr 2023 12:09:55 GMT

Hi,

As you see this working when you build with Keil but not with Segger Embedded Studio I wonder what the difference is in the configuration between these two? Are there differences in the include path for instance? Differences in the processor defines? Or differences in the linker configuration / memory layout?

And as this happens when you enable the SoftDevice - are you building with the include files for the correct SoftDevice variant and version in your include path?