Original question:
Hello
As ESM group 3 is high severity error, when this happened; from the application what should be done?
Is it safe to run some piece of code and issue software reset? Any chance that it will recover?
Will the exception be triggered?
I saw that the halcogen generated code will stop with while(1) when esm 3 is detected, is this recommended way?
Deric
Hi Deric,
As ESM group 3 is high severity error, when this happened; from the application what should be done?
Will the exception be triggered?
ESM group 3 errors will generate aborts directly to the CPU.
These ESM group 3 errors will generate either data abort or prefetch abort.
Is it safe to run some piece of code and issue software reset? Any chance that it will recover?
Customers are responsible for writing their own abort handlers, as the response to an uncorrectable error depends on system-level safety constraints. HALCoGen does create an example data abort handler as it is used for some diagnostic checks. No example prefetch abort handler is provided though.
I saw that the halcogen generated code will stop with while(1) when esm 3 is detected, is this recommended way?
No, the code will get stuck in the dataEntry or prefetchEntry exceptions for ESM group 3 errors.
--
Thanks & regards,
Jagadish.
Hi Deric,
It is possible to recover from esm group 3 error? Like performing a software reset in the abort handler and restart back to main.
Even software reset wouldn't helpful to recover group 3 errors.
The group 3 ESM flags will not get clear by software reset.
And due to this your software will get stuck in the startup code
The only right way to eliminate the error is, first have to rectify the issue causing ESM group-3 error and then write the corresponding ESM flag with 1 in privileged mode. or else we should reprogram the code with rectifying the error that causing the ESM group-3 error.
--
Thanks & regards,
Jagadish.
