Avi Weiss created an issue:
https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5585
## Summary
In `bsps/arm/tms570/start/bspstarthooks-hwinit.c`:
```c
/*
* Chip specific list of peripherals which should be tested
* for functional RAM parity reporting
*/
const tms570_selftest_par_desc_t *const
tms570_selftest_par_list[] = {
&tms570_selftest_par_het1_desc,
&tms570_selftest_par_htu1_desc,
&tms570_selftest_par_het2_desc,
&tms570_selftest_par_htu2_desc,
&tms570_selftest_par_adc1_desc,
&tms570_selftest_par_adc2_desc,
&tms570_selftest_par_can1_desc,
&tms570_selftest_par_can2_desc,
&tms570_selftest_par_can3_desc,
&tms570_selftest_par_vim_desc,
&tms570_selftest_par_dma_desc,
&tms570_selftest_par_spi1_desc,
&tms570_selftest_par_spi3_desc,
&tms570_selftest_par_spi5_desc,
};
```
which is fine for the 3137, but for 4357, some of these modules use ECC
protection:
{width=661
height=530}
So I'm not sure what these self-tests actually do when run as-is on the 4357
variant, but it's definitely not what is intended.
## Expected behaviour
Exclude these on 4357 for now, future work should add ECC self-tests for those
modules.
--
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5585
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
