rtems_error(RTEMS_ERROR_PANIC, (...)) and rtems_error(RTEMS_ERROR_ABORT, (...)) both reset?

Sebastian Huber sebastian.huber at embedded-brains.de
Mon Aug 5 07:49:44 UTC 2013


Hello,

On 2013-08-05 08:11, Nick Withers wrote:
> Hi there!
>
> It seems that rtems_error(RTEMS_ERROR_PANIC, (...)) and
> rtems_error(RTEMS_ERROR_ABORT, (...)) both cause resets on the MVME3100
> board I'm using with RTEMS Git HEAD (updated today).
>
> I believe this differs from 4.10 but have run into some troubles on my
> side trying to verify this.
>
> Is the behaviour I'm seeing intentional? I was under the impression
> (e.g., from
> http://www.rtems.org/onlinedocs/doxygen/cpukit/html/error_8h.html#details ) that the RTEMS_ERROR_PANIC case should leave the system up but halted...?
>

yes, the system termination handling changed from RTEMS 4.10.  Now every 
terminating execution path (unexpected exception, exit(), etc.) should end up 
in _Internal_error_Occurred() which invokes the fatal error extensions.

http://www.rtems.org/wiki/index.php/4.11_Release_Notes

http://www.rtems.org/onlinedocs/doxygen/cpukit/html/group__ScoreIntErr.html

The application can provide an initial extension to do application specific 
termination handling.

The default provided by the BSP is to call bsp_reset().

-- 
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax     : +49 89 189 47 41-09
E-Mail  : sebastian.huber at embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.



More information about the users mailing list