Enabled crash reporting for DISCO_F407VG target

[masoudr]

Description

Enabled Crash-Reporting feature for STM32 DISCO F4 board (DISCO_F407VG target) based on this issue.
I've tested with mbed-os-example-crash-reporting with mbed-os-5.12.2 and here is the result:

Mbed-OS crash reporting test: main()

Forcing exception

++ MbedOS Fault Handler ++

FaultType: HardFault

Context:
R0   : 0000000A
R1   : 0000000A
R2   : E000ED00
R3   : 0000AAA3
R4   : 00000000
R5   : 00000000
R6   : 00000000
R7   : 00000000
R8   : 00000000
R9   : 00000000
R10  : 00000000
R11  : 00000000
R12  : FFFFFFFF
SP   : 200027C0
LR   : 08009BE7
PC   : 08009CE4
xPSR : 010F0000
PSP  : 200027A0
MSP  : 2001FFB0
CPUID: 410FC241
HFSR : 40000000
MMFSR: 00000000
BFSR : 00000000
UFSR : 00000100
DFSR : 00000000
AFSR : 00000000
Mode : Thread
Priv : Privileged
Stack: PSP

-- MbedOS Fault Handler --



++ MbedOS Error Info ++
Error Status: 0x80FF013D Code: 317 Module: 255
Error Message: Fault exception
Location: 0x8001F5B
Error Value: 0x8009CE4
Current Thread: main  Id: 0x20001100 Entry: 0x800411B StackSize: 0xE00 StackMem: 0x200019F0 SP: 0x2001FF0C 
For more info, visit: https://mbed.com/s/error?error=0x80FF013D&tgt=DISCO_F407VG
-- MbedOS Error Info --

= System will be rebooted due to a fatal error =
= Reboot count(=1) reached maximum, system will halt after rebooting ⸮
mbed_error_reboot_callback: System rebooting, reboot error callback received

Mbed-OS crash reporting test: main()

Successfully read reboot info ==> 

  error status: 0x80FF013D
  error value: 0x08009CE4
  error address: 0x08001F5B
  error reboot count: 0x00000001
  error crc: 0x3334F2BE

Crash Report data captured:
[0]: 0x0000000A
[1]: 0x0000000A
[2]: 0xE000ED00
[3]: 0x0000AAA3
[4]: 0x00000000
[5]: 0x00000000
[6]: 0x00000000
[7]: 0x00000000
[8]: 0x00000000
[9]: 0x00000000
[10]: 0x00000000
[11]: 0x00000000
[12]: 0xFFFFFFFF
[13]: 0x200027C0
[14]: 0x08009BE7
[15]: 0x08009CE4

Mbed-OS crash reporting test completed

Pull request type

[ ] Fix
[ ] Refactor
[x] Target update
[ ] Functionality change
[ ] Docs update
[ ] Test update
[ ] Breaking change

Reviewers

Release Notes

[jeromecoutant]

No problem to enable CRASH report for DISCO_F407VG,
but you need to enable it for all the tool chains

[masoudr]

Thanks, I didn't know that, I can fix the other toolchains, do I need to create new PR for them? Or should close this and create another PR?

[jeromecoutant]

You can push other commits within this PR

[ciarmcom]

@masoudr, thank you for your changes.
@ARMmbed/mbed-os-core @ARMmbed/mbed-os-maintainers please review.

[jeromecoutant]

ST CI OK:

Target	Toolchain	TestSuite	TestCase
DISCO_F407VG	ARM	tests-mbed_platform-crash_reporting	tests-mbed_platform-crash_reporting	OK
DISCO_F407VG	GCC_ARM	tests-mbed_platform-crash_reporting	tests-mbed_platform-crash_reporting	OK
DISCO_F407VG	IAR	tests-mbed_platform-crash_reporting	tests-mbed_platform-crash_reporting	OK

[0xc0170]

CI started

[mbed-ci]

Test run: SUCCESS

Summary: 11 of 11 test jobs passed
Build number : 2
Build artifacts