hatdfault BLE application on srf52833 with s140 softdevice

RE: hatdfault BLE application on srf52833 with s140 softdevice

Davide Renzetti — Thu, 31 Jul 2025 12:28:04 GMT

Hi Susheel,

yes I included all SDH libraries. I've gone forward with developing and now, I discoverd that the MWU generate an event.

this the main code:

int main(void)
{

disable_nfc_pins();
checkSystemReset();
ble_stack_init();
BoardInit();
FwAndIDTypeRecognition();

////// SETUP RTOOS ///////
AppConfigInit();
EventManagerInit();
board_interface_init();

....

}

When the debug reach "BoardInit()" the MWU generate an event reagarding subregion PREGION[0].SUBSTATWA->SR0.

If I cancel "BoardInit()" from main and restart the debug, when the debug reach "AppConfigInit()", the MWU generate an event reagarding subregion PREGION[0].SUBSTATWA->SR30.

The debug stop on:

void app_error_fault_handler(uint32_t id, uint32_t pc, uint32_t info), with id=0x00001001, pc=0x38A5C, info=0x40000000

RE: hatdfault BLE application on srf52833 with s140 softdevice

Susheel Nuguru — Thu, 12 Jun 2025 10:54:08 GMT

Hi Davide,

If this is not the FreeRTOS port from us and you are using some other SDK aswell, then there could be conflicts of resources with the other modules and softdevice. Softdevice owns certains resources and expects them to be untouched/unconfigured while initializing the softdevice.

Are you sure you are including all our SDH libraries (components/libraries/softdevice/common and our port of Freertos files and not just from opensource.

If you can help me reproduce this on the nRF52DK, then it will be helpful for me to understand the underlying issue. Please note that we do not have the capacity to debug any other SDK solutions other than what is released by us (NordicSemi)

RE: hatdfault BLE application on srf52833 with s140 softdevice

Davide Renzetti — Thu, 05 Jun 2025 14:55:52 GMT

I Turbo J,

actually putting in debug, I notice in the Disassembly pane, that the application starts from the 'address 0x26100 instead of 0x000000 where is located the softdevvice. How can do to start the appplication from 0x000000 address? I tried putting in Project options->Debug->Loader->Additional file[0]:s140_nrf52_7.2.0_softdevice.hex, and Additional File Address[0[]=0x000000, but the application alway start from 0x26100.

Thank you for support,

Davide

RE: hatdfault BLE application on srf52833 with s140 softdevice

Turbo J — Thu, 05 Jun 2025 13:54:36 GMT

Check that the debugger is set up correctly.

We had another case some weeks ago where the debugger was set up to run the processor from the application reset vector - which ignores the required softdevice setup that must be run before the application start.

Hard faulting in the first SD call sounds a lot like such a problem.

I strongly recommend switching to NRF connect SDK.

RE: hatdfault BLE application on srf52833 with s140 softdevice

Davide Renzetti — Thu, 05 Jun 2025 13:25:06 GMT

Hello Hieu,

yes I'm integrate the ble_app_blinky features into UWB with RTOS project. I confirm I'm using nRF5 SDK v17.1.0.

I started my project with "DWM3001CDK-DW3_QM33_SDK_CLI-FreeRTOS.emProject" example project by Qorvo (UWB with RTOS). Then I added my application and all works fine. Now, I want to add BLE functionalities. So, my steps were as follow:

1) I modified the linker as shown above.

2) I installed the s140_nrf52_7.2.0_softdevice.hex as shown above.

3) I setup following parameters in sdh_config.h:

NRF_SDH_BLE_ENABLED 1

NRF_SDH_BLE_ENABLED 1
NRF_SDH_BLE_VS_UUID_COUNT 1
NRF_SDH_BLE_SERVICE_CHANGED 1

4) I add following parametrs in Project Options->Preprocessor->Preprocessor Definitions:

SOFTDEVICE_PRESENT

S140

NRF_SD_BLE_API_VERSION=7

5) I compiled the application (WITHOUT add BLE functionalities) and everything continues to work well.

6) Then, in main.c, after board initialization, I added BLE call as follow:

int main(void) {

disable_nfc_pins();
BoardInit();
APP_ERROR_CHECK(nrf_sdh_enable_request());

......

}

In debug mode, when I go into APP_ERROR_CHECK(nrf_sdh_enable_request(), the debug jump to SVCALL(SD_SOFTDEVICE_ENABLE, uint32_t, sd_softdevice_enable(nrf_clock_lf_cfg_t const * p_clock_lf_cfg, and right after click "Step Into", the debug stop at void vPortSVCHandler( void ) and the register values are like there:

Go forward 1 step and the debug goes to hardfault handler, and the register values are there:

I hope I have been clear, and you can help me.

Best regards,

Davide

RE: hatdfault BLE application on srf52833 with s140 softdevice

Hieu — Thu, 05 Jun 2025 11:53:40 GMT

Hello Davide,

I am a little confused now. Are you having the hardfault with the unmodified ble_app_blinky example, or are you trying to integrate the ble_app_blinky features into your UWB with RTOS project?

If you are working on an unmodified example, then please check your SEGGER Embedded Studio version. nRF5 SDK v17.1.0 was tested and released with SES v5.42a. That is the version you should use.

If you are working on integrating BLE into your UWB project, then please give some more information about your project. It might be outside of my expertise then, but Susheel will return next week and resume helping you in this case.

Best regards,

Hieu

RE: hatdfault BLE application on srf52833 with s140 softdevice

Davide Renzetti — Thu, 05 Jun 2025 07:56:06 GMT

Another test:

just the debug call:

SVCALL(SD_SOFTDEVICE_ENABLE, uint32_t, sd_softdevice_enable(nrf_clock_lf_cfg_t const * p_clock_lf_cfg, nrf_fault_handler_t fault_handler));

the debug stop at void vPortSVCHandler( void ) and the register values are there:

Go forward by 1 step and the debug goes to hardfault handler, and the register values are there:

I hope it is usefull to solve the issue.

RE: hatdfault BLE application on srf52833 with s140 softdevice

Davide Renzetti — Wed, 04 Jun 2025 14:15:42 GMT

Hi Hieu,

isn't a new project. It's an old project in Segger embedded studio with Qorvo DWM3001C (nrf52833). In this project I use UWB ranging and Rtos. Now, I must add BLE functions, but it doen't work! I think it's very hard convert the segger eproject into nRf Connect SDK!

I hope you can help me.

Best regards,

Davide

RE: hatdfault BLE application on srf52833 with s140 softdevice

Hieu — Wed, 04 Jun 2025 13:20:04 GMT

Hi Davide,

Before we dive further into this, are you starting a new project? If you are, then we strongly recommend you use the nRF Connect SDK instead. There are free online courses on our Developer Academy page to help you getting started with it.

Hieu

RE: hatdfault BLE application on srf52833 with s140 softdevice

Davide Renzetti — Wed, 04 Jun 2025 07:31:44 GMT

I made another test. I wrote following this simple main.c:

disable_nfc_pins();
BoardInit();
APP_ERROR_CHECK(nrf_sdh_enable_request());

When execute APP_ERROR_CHECK(nrf_sdh_enable_request()), the appplication goes in hardfault and the message by hardfault handler are as followos:

Cause: The processor has attempted to execute an undefined instruction.
HARD FAULT at 0x4DB59EF4 R0: 0x00000000 R1: 0x00000000 R2: 0x00000000 R3: 0x200108A0
R12: 0x00000000 LR: 0x4DB59EF5 PSR: 0x6100000B
Cause: The processor has attempted to execute an undefined instruction.

RE: hatdfault BLE application on srf52833 with s140 softdevice

Davide Renzetti — Tue, 03 Jun 2025 13:23:14 GMT

Hi Susheel,

I thought it was a stack or heap size problem, so I enlarged a lot their size, but I always have hardfaut. I enabled the hardfault handler. These are the results:

HARD FAULT at 0x00000000 R0: 0x00000000 R1: 0x00000000 R2: 0x20002C00 R3: 0x200108A0
R12: 0x00000000 LR: 0x00000000 PSR: 0x2000000B
Cause: The processor has attempted to execute an instruction that makes illegal use of the EPSR.

RE: hatdfault BLE application on srf52833 with s140 softdevice

Susheel Nuguru — Fri, 30 May 2025 20:29:42 GMT

Hi Davide,

Can you please enable the serial logs and give us some details of the hardfault on your serial logs. Also make sure you enable

HARDFAULT_HANDLER_ENABLED to 1 in your sdk_config.h

There also an external blog you can use to try to attempt to debug the hardfault to get the context of where the hardfault happens.