problem with 0x8C8 line

RE: problem with 0x8C8 line

bjorn-spockeli — Mon, 20 Apr 2020 08:51:16 GMT

[quote user="gercer"]Should I erase the flash memory often to avoid writing outside the mapped flash?[/quote]

No, its usually incorrect or corrupted values that cause the CPU is instructed to write to a protected flash region or branch to an address outside the mapped flash.

So I would recommend using the HardFault handling library in SDK v15.2.0 to debug the issue.

Best regards

Bjørn

RE: problem with 0x8C8 line

gercer — Fri, 17 Apr 2020 17:34:39 GMT

Thank you for the answer
Im using SDK 15.2.

Should I erase the flash memory often to avoid writing outside the mapped flash?

RE: problem with 0x8C8 line

bjorn-spockeli — Fri, 17 Apr 2020 08:50:13 GMT

Hi Gerardo,

Which SDK version are you using? There is a known issue in SDK v15.3.0 for ble_nus_data_send, see https://devzone.nordicsemi.com/f/nordic-q-a/51621/hardfault-ble_nus_send_data.

As stated in the question you linked to, address 0x8C8 is the HardFault handler of the MBR. HardFaults typically occur when the CPU is instructed to write to a protected flash region or branch to an address outside the mapped flash . In the known issue with ble_nus_data_send the issue was that the p_nus->data_handler was a null pointer.

The issue in the case you referred to was that some preprocessor definitions were missing, which caused the incorrect SD APIs being used and this caused a Hardfault. The map file for your application adn the blinky application can be found in the Output\Release\Exe or Debug folder after compiling the SES project.

Best regards

Bjørn