Avi Weiss created an issue:
https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5565
## Summary
calls to `tms570_irq_set_priority` protect against requesting a `priority < 2`,
but not against inputs with `vector < 2`.
for example calling `tms570_irq_set_priority(ESM_HIGH, 10)` will not only get
through the guard, it will attempt to write to `CHANCTRL0` (which gets blocked
by hardware), puts whatever was there (apparently hardcoded `INT-REQ0`) into
channel 10, and returns success.
So the channel 10 request dissappeared from the VIM channel map completely -
yet this call returns `RTEMS_SUCCESSFUL`
TRM (for both TMS570LS31x and TMS570LC43x) states:
_NOTE: `CHAN0` and `CHAN1` are hard wired to `INT_REQ0` and `INT_REQ1`, so they
cannot be remapped._
{width=900
height=537}
## Expected behaviour
should add protection for `vector < 2` as well, and make sure calls like this
don't falsly report success.
--
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5565
You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________
bugs mailing list
[email protected]
http://lists.rtems.org/mailman/listinfo/bugs
