2 years, 6 months ago.

Mbed OS 2 release 165 causes hard fault on K64F

Since the 165 release, it has not been possible to get code to run on a K64F using Mbed OS 2 (on both K64F's with latest DAPlink firmware and also brand-new K64F's fresh out of the box).

Even a simple GPIO blinky example fails the run and the following fault message appears in the terminal:

-- MbedOS Fault Handler --

++ MbedOS Error Info ++
Error Status: 0x80FF013D Code: 317 Module: 255
Error Message: Fault exception
Location: 0x493F
Error Value: 0xE7E
For more info, visit: https://armmbed.github.io/mbedos-error/?error=0x80FF013D
-- MbedOS Error Info --

= System will be rebooted due to a fatal error =
= Reboot count(=35) reached maximum, system will halt after rebooting 
++ MbedOS Fault Handler ++

FaultType: HardFault

Context:
R0   : 00006A74
R1   : 00000000
R2   : 00007A74
R3   : 200000E4
R4   : 00007A74
R5   : 00006A74
R6   : 00006A84
R7   : 20000548
R8   : 00000000
R9   : 00000000
R10  : 0000685C
R11  : 0000685C
R12  : 00000000
SP   : 2002FFD0
LR   : 00000E67
PC   : 00000E7E
xPSR : 41000000
PSP  : 00000000
MSP  : 2002FF68
CPUID: 410FC241
HFSR : 40000000
MMFSR: 00000000
BFSR : 00000086
UFSR : 00000000
DFSR : 00000008
AFSR : 00000000
BFAR : 00006A74
Mode : Thread
Priv : Privileged
Stack: MSP

Switching back to version 164 fixes the issue.

1 Answer

2 years, 6 months ago.

Hi Craig,

Thank you for reporting this problem. We've just confirmed that a program never reaches main() so we suspect there is a problem with changes made to the scatterfile. This only impacts Mbed OS2 so we created an internal tracking JIRA. We'll update you as soon as a fix is available. Please continue using version 164.

Our apologies for the inconvenience.

Regards,

Ralph, Team Mbed

Accepted Answer

No progress so far?

posted by Diego Contreras 23 Apr 2019