sd_flash_page_erase cause hardfault

[sean]

hi,

    We are currently having some problems erasing flash，The problem recurrence rate was 1%，the recurrence rate of specify chip problems is 100%，Here are some scenarios as flow.Windows/KEIL/SDK17.0.2

---------scenarios 1--------------

sd_softdevice_enable()      return NRF_SUCCESS
sd_flash_page_erase()     return NRF_SUCCESS

wating sd_flash_page_erase()  event    --> cause hardfault
sd_ble_cfg_set()
sd_ble_enable() 

advertising_init()

->Problems occur, specify chip  100% recurrence rate

-----------scenarios 2----------------------

sd_softdevice_enable()         return NRF_SUCCESS

nrf_delay_ms(100)
sd_flash_page_erase()        return NRF_SUCCESS

wating sd_flash_page_erase()  event
sd_ble_cfg_set()
sd_ble_enable() 

advertising_init()

-> specify chip Problems disappear

-----------scenarios 3----------------------

sd_softdevice_enable()       return NRF_SUCCESS

sd_ble_cfg_set()
sd_ble_enable() 

sd_flash_page_erase()       return NRF_SUCCESS

wating sd_flash_page_erase()  event

advertising_init()

-> specify chip Problems disappear

[Vidar Berg]

Hello,

Does the program enter the HardFault_Handler() function, or does it go into the user specified fault handler that is registered when you call sd_softdevice_enable()? Could you include a screenshot showing the call stack and cpu registers after you have entered one of these fault handlers?

Thanks,

Vidar

[sean]

hi，

   it go into the user specified fault handler，As shown below.

 

call stack and cpu registers

If  need any more information let me know.

[Vidar Berg]

Hi,

Thanks for confirming. What you are seeing is a Softdevice assertion (Error handling). I will look into what may causing this assert, but first I need to know what nRF52 and Softdevice variant you are using.

[sean]

hi，

 nRF52833.    Softdevice:   s140_nrf52_7.0.1_softdevice

[Vidar Berg]

Hi,

Are you using the internal RC oscillator or the crystal oscillator as the low frequency clock source?

Thanks,

Vidar