Skip to main content
L
lucky65
Explorer
June 10, 2025
Solved

STM32H743: QUADSPI internal timing criticality errata

  • June 10, 2025
  • 2 replies
  • 458 views

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

 

 

    This topic has been closed for replies.
    Best answer by mƎALLEm

    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.

    2 replies

    M
    mƎALLEm
    Technical Moderator
    June 10, 2025

    Hello,

    I will check internally and get back to you as soon as I have an answer.

     

      M
      mƎALLEmAnswer
      Technical Moderator
      June 24, 2025

      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.

      L
      lucky65Author
      Explorer
      July 11, 2025

      Hi,

      sorry for my late reply.

      I applied the suggested workaround ; thanks a lot for your answer .

       

      Best regards,

      Lucio

       

      Terms & ConditionsAccessibility statement