Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
Using SEMPER NOR Flash with HyperBus Interface in Legacy SPI Mode - KBA233015
Question: Infineon has the latest 45-nm SEMPER NOR flash with HyperBus interface (S26HL-T and S26HS-T series), which can support legacy SPI (x1) mode and HyperBus (x8) mode. Can I use it like a normal SPI (x1) NOR flash?
Answer: SEMPER NOR flash with HyperBus interface (S26HL-T and S26HS-T series) has some ordering part numbers (OPN) that work in legacy SPI (x1) mode by factory default.
When SEMPER NOR flash with HyperBus interface works in legacy SPI (x1) mode, the Read Device ID (RDIDN_0_0, 9Fh) command will output the 8-bit byte stream from flash. Since the Device ID is aligned in 16-bit length (“word” type), the Device ID byte value is in the lower 8-bit; the upper 8-bit is padded with the “00h” value.
For example, if we read Device ID from S26HL512T in legacy SPI (x1) mode, the output byte stream will be: 0x34 – 0x00 – 0xA6 – 0x00 – 0x1A – 0x00 – 0xA2 – 0x00 …
Therefore, when using the code to read and pair the Device ID developed for SPI/QSPI flash, consider the Device ID pattern in byte mode and handle the “00h” padding correctly for every 16-bit width.
More information is available in the “Device ID Address Space” section in the datasheet:
Figure 1. S26HL-T/S26HS-T Device ID Datasheet Table