Skip to main content
Associate
September 21, 2024
Solved

STM32H5 does not have a DQS line for HYPERBUS

  • September 21, 2024
  • 4 replies
  • 2971 views

Hello everyone,

I was trying to design a Hyperbus RAM based PCB for one of my projects but I realized that when I configure Hyperbus under the OCTOSPI1 settings I do not get the DQS(RWDS) line. Here are the configuration pictures. 

 

Thanks,

Burak Önemli

Screenshot 2024-09-21 at 15.58.34.png

Screenshot 2024-09-21 at 15.59.41.png

Screenshot 2024-09-21 at 16.01.07.png

Best answer by mƎALLEm

Fixed in CubeMX 6.13.0

4 replies

mƎALLEm
Technical Moderator
September 21, 2024

Hello @burakOnemli and welcome to the community,

I will check internally this point and get back to you as soon as I have a feedback (internal ticket 191726 for follow-up).

 

"To give better visibility on the answered topics, please click on ""Accept as Solution"" on the reply which solved your issue or answered your question."
Associate
September 21, 2024

Thanks for your reply @mƎALLEm,

 

I will be waiting for your answer.

 

Best Regards,

Burak Önemli

Brian H
Senior
September 27, 2024

I'm in the same situation with STM32H563IIK6. A connection for RWDS isn't available in HyperBus configuration, only the somewhat-similar DQS is available for Octo-SPI With Data Strobe, which does not offer nCLK option.

 

Aside: The device I am using (Infineon S27KS0643) does not require differential clock, but does not seem to function correctly with the peripheral in DQS mode.  However, the use of RDWS is necessary as the PSRAM uses it to indicate latency requirement for read commands.  Here is the Infineon datasheet.  

In my case, I have not yet ruled out my PCB layout as a cause of problems, but the need for RDWS in STM's peripheral remains.

Associate
September 29, 2024

Hello @mƎALLEm,

Are there any news about the topic or are we still waiting for an answer. 

Thanks,

Burak Önemli

mƎALLEm
Technical Moderator
September 30, 2024

Hello @burakOnemli ,

The limitation is confirmed. 

Sorry for any inconvenience. 

 

"To give better visibility on the answered topics, please click on ""Accept as Solution"" on the reply which solved your issue or answered your question."
Associate
September 30, 2024

Thanks for your reply @mƎALLEm ,

Hope that the configuration will be fixed in STM32Cubeide so that it does not cause any further confusions for other people that is working with STM32H563. 

Best Regards,

Burak Önemli

mƎALLEm
Technical Moderator
September 30, 2024

Unmarked the solution, until it ill be fixed.

"To give better visibility on the answered topics, please click on ""Accept as Solution"" on the reply which solved your issue or answered your question."
mƎALLEm
mƎALLEmBest answer
Technical Moderator
November 27, 2024

Fixed in CubeMX 6.13.0

"To give better visibility on the answered topics, please click on ""Accept as Solution"" on the reply which solved your issue or answered your question."
Brian H
Senior
November 27, 2024

This is good news, as it implies that there is not a limitation in the h5 silicon.

When should we expect this version to be published through the in-app update channels?  Right now, the latest update package I'm being shown only includes MX 6.12.1.202409122256:

BrianH_1-1732717597997.png

[...]

BrianH_0-1732717573465.png

Granted it's only been about three hours since your post... :)

mƎALLEm
Technical Moderator
November 27, 2024

I don't know but you can download V6.13.0 directly from this link.

"To give better visibility on the answered topics, please click on ""Accept as Solution"" on the reply which solved your issue or answered your question."