RTEMS | bsp/arm/tms570: hw_init does not explicitly handle some serious eFuse errors (#5590)

Tue May 26 08:03:50 UTC 2026

Avi Weiss created an issue: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5590

## Summary
In `tms570_system_hw_init`, only 2 of the 4 return statuses from `tms570_efc_check` are explicitly dealt with.

Statuses `1` and `3` currently just get reported to an empty hook in the stock BSP (via `bsp_selftest_fail_notification`) and then fall-through in `tms570_system_hw_init` with start-up continuing.

## Expected behaviour
Deal with status returns `1` and `3` from `tms570_efc_check` in `tms570_system_hw_init` and probably stop initialisation as these are specifically referenced in the TRMs for safety critical systems as serious errors.

(see TRM s38.3.2 _Checking for eFuse Errors After Power Up_)

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5590
You're receiving this email because of your account on gitlab.rtems.org.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20260526/089eb158/attachment-0001.htm>