PLATFORM_FATAL_ERRORs are now caught even when they happen in the

initial JTAG scan that occours during platform_init.

Previously any fatal errors that occoured during this scan caused a
hardfault.
This commit is contained in:
Richard Eoin Meadows 2014-05-26 13:25:53 +01:00
parent 72ae78a185
commit 63bce97cbd
4 changed files with 20 additions and 0 deletions

View File

@ -92,6 +92,11 @@ int platform_init(void)
cdcacm_init();
// Set recovery point
if (setjmp(fatal_error_jmpbuf)) {
return 0; // Do nothing on failure
}
jtag_scan(NULL);
return 0;

View File

@ -140,6 +140,11 @@ int platform_init(void)
cdcacm_init();
usbuart_init();
// Set recovery point
if (setjmp(fatal_error_jmpbuf)) {
return 0; // Do nothing on failure
}
jtag_scan(NULL);
return 0;

View File

@ -121,6 +121,11 @@ int platform_init(void)
cdcacm_init();
// Set recovery point
if (setjmp(fatal_error_jmpbuf)) {
return 0; // Do nothing on failure
}
jtag_scan(NULL);
return 0;

View File

@ -99,6 +99,11 @@ int platform_init(void)
cdcacm_init();
// Set recovery point
if (setjmp(fatal_error_jmpbuf)) {
return 0; // Do nothing on failure
}
jtag_scan(NULL);
return 0;