STL Library flash test error configuration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-07 7:18 AM
Hi, my current issue is that after implement Self test library for a stm32h5 the basic things like STL_SCH_Init() works fine but when i try to run the flash test the STL_SCH_ConfigureFlash fails, the status says STL_ERROR.
How i run the test:
- I define STL_MemConfig_t FlashRangesVar (with the right memory ranges inside a STL_MemSubset_t struct).
- STL_SCH_Init() ->works fine.
- STL_SCH_InitFlash(&StatusVar) -> works fine an statusVar is STL_NOT_TESTED.
- STL_SCH_ConfigureFlash(&statusVar,&FlashRangesVar) -> this works but statusVar says STL_ERROR and not STL_NOT_TESTED like the documentation says.
I also use the CRC tool that is required for the test with the full flash range.
So my question is why the configureFlash fails?, because even if i define small ranges for the test it still fails the configuration and i check and re-check the ranges.
Thanks for reading.
- Labels:
-
Functional Safety
-
STM32H5 Series
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-13 8:13 AM
Thanks for your reply, it was a flash offset that misaligned the flash memory.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-13 8:54 AM
Sorry I delete by mistake my original reply. Yes, the tested area has to be set carefully. It has to start at 1KB boundary and end at binary end aligned at word boundary. Binary has to be continuous without any gaps in between code sections. Valid CRC value must be stored for each tested 1KB tested memory section at CRC-area else test execution fails. Note ST Cube Programmer computes CRCs for memory sections occupied by code exclusively. For more details pls study the STL user guide.
