Skip to main content
Visitor II
February 25, 2025
Solved

STM32H735IGT6 with Infineon HyperRAM S70KL1283 with xSPI (Octal) interface

  • February 25, 2025
  • 2 replies
  • 594 views

Hi there,

I have a new custom PCB with STM32H735IGT6 with Infineon HyperRAM S70KL1283 connected to OCTOSPI2.

This RAM device does not use HYPERBUS but xSPI (Octal) interface. It seems to be using a combination of HYPERBUS and regular command SPI mode as protocol.
As far as I understand the supported frame formats in the STM32H735 our RAM device is not supported by the OCTOSPI interface.
Is that correct?

As a solution we have to take the HYPERBUS variant (S70KL1282) of the RAM device.

Can anybody confirm my thoughts?

Many thanks!

 

    This topic has been closed for replies.
    Best answer by KDJEM.1

    Hello @PK-Sabik and welcome to the community,

     

    The command format and order shared in the device datasheet must be aligned with the command format and order mentioned in the STM32 reference.

     

    I noted in S70KL1283 memory datasheet that:

    - Each transaction has a 16-bit command which selects the type of device operation to perform. The 16-bit command is based on two 8-bit opcodes. The same 8-bit opcode is sent on both edges of the clock.

    KDJEM1_1-1740479794351.png

    But the format supported by the OCTOSPI interface with the HyperBus protocol, as mentioned in the reference manual, is 

    KDJEM1_2-1740480194715.png

    KDJEM1_3-1740480219225.png

    For that, the user must verify if these interfaces are supported by the device. I recommend you to look this FAQ may help you to start with the OCTOSPI interface.

    KDJEM1_4-1740480738211.png

     

    Thank you.

    Kaouthar

     

    2 replies

    KDJEM.1Answer
    Technical Moderator
    February 25, 2025

    Hello @PK-Sabik and welcome to the community,

     

    The command format and order shared in the device datasheet must be aligned with the command format and order mentioned in the STM32 reference.

     

    I noted in S70KL1283 memory datasheet that:

    - Each transaction has a 16-bit command which selects the type of device operation to perform. The 16-bit command is based on two 8-bit opcodes. The same 8-bit opcode is sent on both edges of the clock.

    KDJEM1_1-1740479794351.png

    But the format supported by the OCTOSPI interface with the HyperBus protocol, as mentioned in the reference manual, is 

    KDJEM1_2-1740480194715.png

    KDJEM1_3-1740480219225.png

    For that, the user must verify if these interfaces are supported by the device. I recommend you to look this FAQ may help you to start with the OCTOSPI interface.

    KDJEM1_4-1740480738211.png

     

    Thank you.

    Kaouthar

     

    PK-SabikAuthor
    Visitor II
    February 25, 2025

    Hello Kaouthar,

    thank you for your answer.

    As I understood, you have the same conclusion as me that our current RAM device is not compatible with the STM32H7 OCTOSPI.

    We will replace the RAM devices on our existing PCBs with a device that is supporting HYPERBUS. Then it should work as expected.

    Regards,
    Peter.