STM32H5 does not have a DQS line for HYPERBUS

burakOnemli · ‎2024-09-21

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

SofLit · ‎2024-11-27

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.

View solution in original post

SofLit · ‎2024-09-21

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.

burakOnemli · ‎2024-09-21

Thanks for your reply @SofLit,

I will be waiting for your answer.

Best Regards,

Burak Önemli

Brian H · ‎2024-09-27

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.

burakOnemli · ‎2024-09-27

Hi @Brian H ,

I am happy to see that someone has been struggling the same problem as me. If Hyperbus can not be used in Stm32H563 devices why did they add it in the first place? I hope that the problem is STM32Cube ide based so that I don't have to change my PCB layout.

Brian H · ‎2024-09-27

Indeed. I'm already faced with a PCB change, but I chose the H563 for the whole combination of available peripherals...switching MCUs just to get external RAM would be a disaster....

burakOnemli · ‎2024-09-28

Hello @SofLit,

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

Thanks,

Burak Önemli

SofLit · ‎2024-09-30

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.

burakOnemli · ‎2024-09-30

Thanks for your reply @SofLit ,

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

SofLit · ‎2024-09-30

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.