STM32H743: QUADSPI internal timing criticality errata
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-06-10 4:38 AM - last edited on ‎2025-06-10 6:19 AM by mƎALLEm
Hi all,
I am working on a QSPI driver for W25Q512 flash memory (extloader for stm32cubeprogrammer and main firmware driver).
I had a look at the errata ES0392 - Rev 13 and I have a question about paragraph 2.8.4:
2.8.4 - QUADSPI internal timing criticality
---------------
Description
The timing of some internal signals of the QUADSPI peripheral is critical.
At certain conditions, this can lead to a general failure of the peripheral.
As these conditions cannot be exactly determined, it is recommended to systematically apply the workaround as described.
...
[omissis]
I have applied the suggested patch on the "external loader" driver and there is no particular problem in applying it, but I have also the "very similar" driver on the main application firmware in processor.
Up to now I had no errors in the main firmware qspi driver : read and write are ok also without the patch.
Applying the patch on the "main firmware" needs testing and I have to schedule this testing.
Is it possible to have some more details on this "certain conditions" to better evaluate the situation and get less worried about this... ?
Does it mean clock, temperature, ...?
Thanks,
best regards
Lucio
Solved! Go to Solution.
- Labels:
-
QSPI
-
STM32H7 Series
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-06-24 4:28 AM - edited ‎2025-06-24 4:29 AM
Hello,
According to our expert, unfortunately we don't have the exact condition when the issue could happen. It could be the clock, temperature, voltage ... It's linked to a synchronization issue between two clock domains that could be influenced by temperature, clocks, voltage ..
So in any case you need to apply the workaround.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-06-10 6:25 AM
Hello,
I will check internally and get back to you as soon as I have an answer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-06-24 4:28 AM - edited ‎2025-06-24 4:29 AM
Hello,
According to our expert, unfortunately we don't have the exact condition when the issue could happen. It could be the clock, temperature, voltage ... It's linked to a synchronization issue between two clock domains that could be influenced by temperature, clocks, voltage ..
So in any case you need to apply the workaround.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-07-11 3:15 AM
Hi,
sorry for my late reply.
I applied the suggested workaround ; thanks a lot for your answer .
Best regards,
Lucio
