Device HANG - Program counter stuck at __SEV() (Address 0x00078d58)

RE: Device HANG - Program counter stuck at __SEV() (Address 0x00078d58)

bjorn-spockeli — Wed, 24 Apr 2019 07:48:30 GMT

Ok, are you running the garbage collection, i.e. fds_gc, to reclaim the flash space? fds_record_delete only marks the record for deletion. Quote from the FDS API documentation.

Note that deleting a record does not free the space it occupies in flash memory. To reclaim flash space used by deleted records, call fds_gc to run garbage collection.

RE: Device HANG - Program counter stuck at __SEV() (Address 0x00078d58)

shreyab — Wed, 24 Apr 2019 06:59:33 GMT

[quote userid="7571" url="~/f/nordic-q-a/46024/device-hang---program-counter-stuck-at-__sev-address-0x00078d58/183123"]How are you erasing the pages prior to entering SystemOFF?[/quote]

yes, we are waiting for FDS_EVT_DEL_RECORD event before entering into System OFF.

[quote userid="7571" url="~/f/nordic-q-a/46024/device-hang---program-counter-stuck-at-__sev-address-0x00078d58/183123"]Are you using the NVMC directly to do the erase or are you using the fstorage or FDS APIs?[/quote]

We are using fds APIs for all flash related activities.

RE: Device HANG - Program counter stuck at __SEV() (Address 0x00078d58)

bjorn-spockeli — Tue, 23 Apr 2019 12:44:42 GMT

OK, if the bootlaoder is SD independent then it will call __SEV() as a part of the wait_for_event() function which is called in the infinite for loop. So for some reason you are not jumping from the bootloader to the application when waking up from SystemOFF.

[quote user="shreyab"]Further investigation reveals that, both data storage flash pages are full (probably corrupted) and in certain addresses there are random characters stored in ASCII sequence (the swap space is empty though and not at all corrupted).[/quote]

How are you erasing the pages prior to entering SystemOFF? Are you using the NVMC directly to do the erase or are you using the fstorage or FDS APIs?

RE: Device HANG - Program counter stuck at __SEV() (Address 0x00078d58)

shreyab — Mon, 15 Apr 2019 06:46:46 GMT

[quote userid="7571" url="~/f/nordic-q-a/46024/device-hang---program-counter-stuck-at-__sev-address-0x00078d58/181626"]Are you entering System OFF from the application or the bootloader? Have you configured the button to be a wakeup source in both the bootloader and the application?[/quote]

We are entering System OFF from the application, and we have configured the button to be a wakeup source in JUST the application.

[quote userid="7571" url="~/f/nordic-q-a/46024/device-hang---program-counter-stuck-at-__sev-address-0x00078d58/181626"] Are using the SoftDevice in your bootloader is it not dependent on the SD?[/quote]

Bootloader is not dependent on softdevice.

UPDATE -

Further investigation reveals that, both data storage flash pages are full (probably corrupted) and in certain addresses there are random characters stored in ASCII sequence (the swap space is empty though and not at all corrupted).

RE: Device HANG - Program counter stuck at __SEV() (Address 0x00078d58)

bjorn-spockeli — Thu, 11 Apr 2019 13:14:26 GMT

[quote user=""]We use System off mode and then use a button press to come out of it.[/quote]

Are you entering System OFF from the application or the bootloader? Have you configured the button to be a wakeup source in both the bootloader and the application?

[quote user=""]debugger also stuck at Address 0x00078d58 which is at __SEV()[/quote]

The address indicated that you're in the bootloader. Are using the SoftDevice in your bootloader is it not dependent on the SD? The __SEV() function is used in the wait_for_event() function, so the bootloader is simply waiting for an event.

Best regards

Bjørn