Skip to main content
Associate III
Nov 20, 2026 1:43 AM UTC
Question

HyperRAM Hold time failing issue with STM32N657

Hello Team,

We are using STM32N657 and HyperRAM S80KS5122GABHI023 in our design. We are facing issue related to minimum 0.5ns hold time requirement of HyperRAM. We are getting hold time 0.34ns for RWDS. Same thing is also happening with Data 0-7 lines also.

We are operating HyperRAM at 200MHz.

Could you please suggest us how can we manually add delay in RWDS and Data lines to meet hold time requirement?

 

Thanks

2 replies

KDJEM.1
ST Technical Moderator
Nov 20, 2026 9:21 AM UTC

Hello ​@kadam ;

 

I recommend you to look at DS14791 precisely Table93. and respect the minimum timing supported by STM32N657.I 

Thank you.

Kaouthar

To give better visibility on the answered topics, please click on "Best answer" on the reply which solved your issue or answered your question.
kadamAuthor
Associate III
Nov 21, 2026 3:56 AM UTC

Hello Kaouthar,

Thank you for your reply.

As per table, for 200MHz clock frequency, when we calculate data output hold time (min) value is 0.75ns. In our case we are getting ~0.34ns. I believe this case suffice RAM side hold time requirement.

When we have captured waveform for both Clock and RWDS with Data write operation, we are seeing that Clock and RWDS both have same edge of toggling with 180 degree shift. Due this we have lower hold time. 

So, We have also performed auto calibration. Along with this we have also try to provide manual delay in RWDS and Data lines by writing value inside XSPI DLL slave output calibration configuration (XSPI_CALSOR) register.

XSPI_CALSOR value Clock to RWDS hold time
0x0006000A 429ps
0x000A000A 314ps
0x0007000F 400ps
0x0002000A 366.133ps
0x000F000A 400ps

 

 

 

 

Also, full RAM write and read test is failing. We are getting CRC mismatch.

Suggest us if we have missed any sequence in defining auto calibration and manual delay.

Could you please guide us to resolve this issue? 

Thanks