S32K328 HyperRAM read write errors at low temperatures Hello NXP Community, we are using an NXP S32K328 with an Infineon S27KL0642DPBHB023 64-Mbit HyperRAM connected through the QuadSPI interface. The interface operates with the following basic configuration: HyperRAM voltage = 3.3 V QuadSPI clock = 120 MHz Interface mode = Octal DDR Clock mode = Single-ended CK Read-data strobe = External RWDS Latency mode = Fixed latency Normal memory access = Memory-mapped AHB At room temperature, the HyperRAM interface appears to work correctly. At low temperatures, down to −40 °C, we observe read/write comparison errors. The problem appears to be related mainly to the temperature of the S32K328. Cooling the S32K328 can reproduce the errors, while cooling the HyperRAM alone has a much smaller effect. The relevant S32K328 QuadSPI settings are: DDR_EN = 1 DQS_EN = 1 External DQS/RWDS = selected DQS_OUT_EN = 1 VAR_LAT_EN = 0 FLSHCR.TCSS = 4 FLSHCR.TCSH = 7 FLSHCR.TDH = 1 The current DLL configuration is: SLV_DLL_BYPASS = 0 SLAVE_AUTO_UPDT = 1 SLV_EN = 1 SLV_DLY_COARSE = 0 FREQEN = 1 DLL_CDL8 = 0 DLLRES = 8 DLL_REFCNTR = 2 SMPR.FSPHS = 0 SMPR.FSDLY = 0 SMPR.DLLFSMPFA = 0 We tested all available combinations of: SLV_DLY_OFFSET = 0 to 7 SLV_FINE_OFFSET = 0 to 15 At low temperatures, failures occur across all tested DLL configurations. The sweep shows differences between the configurations, but it does not provide a completely error-free operating range or a clearly optimal DLL parameter set. Therefore, we are currently not sure whether the problem is caused by the DLL configuration itself or by another temperature-dependent part of the S32K328 QuadSPI interface. Could you please help us with the following questions? Is the S32K328 QuadSPI configuration shown above suitable for HyperRAM operation at 120 MHz? Are the selected DLL parameters correct for this frequency and the full temperature range? Which values should be used for FREQEN, DLL_CDL8, DLLRES and DLL_REFCNTR at 120 MHz? Which DLL status flags should be monitored to verify correct operation? Should both DLLA_LOCK and SLVA_LOCK be checked before accessing the HyperRAM? How should DLLA_RANGE_ERR or FINE_UNDERFLOW be handled? Could the QuadSPI DLL or external-DQS path operate outside its valid range at low temperatures? Does the DLL configuration affect only read-data sampling, or can it also affect write timing? Are FLSHCR.TCSS = 4, FLSHCR.TCSH = 7 and FLSHCR.TDH = 1 suitable for 120 MHz HyperRAM operation? Which pad settings are recommended for CK, CS#, DQ[7:0] and RWDS at 120 MHz Octal DDR? Are there any known S32K328 errata or RTD issues related to QuadSPI, external DQS or operation at low temperatures? Is there a validated S32K328 HyperRAM initialization example or register configuration for 120 MHz operation? Any guidance on additional S32K328 registers or status information that should be checked would be very helpful. Thank you. Re: S32K328 HyperRAM read write errors at low temperatures 1) The operating mode is supported, but the current configuration does not fully match the required 120 MHz DDR external-DQS settings in Table 66. FREQEN should be 0, SMPR.DLLFSMPFA should be 4, FLSHCR.TCSS should be 2, FLSHCR.TCSH should be 5, and both delay offsets should initially be 0. The remaining listed settings match Table 66. The configuration should be corrected before further low-temperature testing.
2) The operating mode is supported, but the current configuration does not fully match the required 120 MHz DDR external-DQS settings in Table 66. FREQEN should be 0, SMPR.DLLFSMPFA should be 4, FLSHCR.TCSS should be 2, FLSHCR.TCSH should be 5, and both delay offsets should initially be 0. The remaining listed settings match Table 66. The configuration should be corrected before further low-temperature testing.
3) According to Table 66:
FREQEN = 0 DLL_CDL8 = 0 DLLRES = 8 DLL_REFCNTR = 2
The DLL programming sequence described in the “DLL and delay chain usage” chapter must also be followed.
4) Monitor these DLLSR flags:
DLLA_LOCK = 1: DLL reference chain is locked. SLVA_LOCK = 1: Slave delay chain is locked. DLLA_RANGE_ERR = 0: DLL master delay chain is within its valid range. DLLA_FINE_UNDERFLOW = 0: No fine-delay-chain underflow occurred.
5) Yes. When the DLL and slave delay line are enabled, both DLLA_LOCK and SLVA_LOCK should indicate lock before starting HyperRAM accesses.
6) These flags indicate that the configured delay cannot be generated correctly. HyperRAM operation should not be considered reliable while either error is present. Recheck the Table 66 configuration and the required DLL initialization sequence. If the error remains, reduce the QuadSPI frequency for further testing.
7) Please retest with the documented settings first.
😎 The external DQS and slave-DLL settings primarily control read-data sampling. Write timing is mainly determined by CK, CS#, data-output timing, pad configuration and the FLSHCR timing fields. Separate read-only and write/read-back tests can help identify which path is failing.
9) They do not match Table 66. For the characterized 120 MHz DDR configuration, use:
FLSHCR.TCSS = 2 FLSHCR.TCSH = 5 FLSHCR.TDH = 1
10) The data-sheet characteristics use DSE = 1 and SRE = 0. They assume a maximum output load of 25 pF, an input transition time of 1 ns and QuadSPI traces no longer than 2 inches. These conditions and the actual CK/RWDS signal quality should be verified on the board.
11) I have not identified a published S32K328 erratum specifically describing external-DQS failures at low temperature. The applicable errata and the release notes for the exact RTD version should nevertheless be checked.
12) No validated HyperRAM initialization example is currently available. Please use the configuration specified in Table 66 of the S32K3xx Data Sheet as the reference for the QuadSPI settings.
Re: S32K328 HyperRAM read write errors at low temperatures Hello NXP Community, we are continuing our investigation of temperature-dependent HyperRAM errors on an S32K328 connected to an Infineon S27KL0642DPBHB023, 8 MiB, 3.3 V. The interface operates at 120 MHz in Octal DDR mode using external edge-aligned RWDS/DQS. Normal memory access uses the QuadSPI AHB memory-mapped window: 0x68000000 to 0x687FFFFF Current relevant configuration ------------------------------ QuadSPI SCK = 120 MHz DDR_EN = 1 DQS_EN = 1 DQS_FA_SEL = 3 DQS_OUT_EN = 1 FLSHCR.TCSS = 2 FLSHCR.TCSH = 5 FLSHCR.TDH = 1 SMPR.DLLFSMPFA = 4 SMPR.FSDLY = 0 SMPR.FSPHS = 0 DLL FREQEN = 0 DLL_CDL8 = 0 DLL_REFCNTR = 2 DLLRES = 8 SLV_DLY_OFFSET = 0 SLV_FINE_OFFSET = 8 SLAVE_AUTO_UPDT = 1 SLV_EN = 1 SLV_DLL_BYPASS = 0 The fine offset of 8 was selected empirically from temperature tests. It is not taken from the zero-offset reference configuration in Data Sheet Rev. 14. Our current initialization contains this sequence: Configure QuadSPI and LUT Configure DLL using auto-update Perform one dummy AHB read Perform QuadSPI software reset Configure DLL again Read HyperRAM registers using IP commands Start normal AHB accesses The dummy read currently performs a volatile 32-bit read first and invalidates the corresponding Cortex-M7 cache line afterwards. Difference from Data Sheet Rev. 14 ---------------------------------- In S32K3xx Data Sheet Rev. 14, Table 66 appears to specify the following for the S32K328 120 MHz DDR, External DQS, Edge Aligned configuration: FLSHCR.TCSS = 3 FLSHCR.TCSH = 3 FREQEN = 0 DLL_REFCNTR = 2 DLLRES = 8 SLV_DLY_OFFSET = 0 SLV_FINE_OFFSET = 0 SLAVE_AUTO_UPDT = 0 SLV_UPD = 1, according to the RM programming sequence DLLFSMPFA = 4 FSDLY = 0 This differs from our current TCSS/TCSH = 2/5, fine offset 8 and auto-update mode. Failure signature ----------------- Temperature testing still shows occasional memory-test failures even with settings near the center of the measured sampling window. The reported failures have a repeatable signature: - A complete 32-byte block is affected. - When reading address A, the returned block appears to match the expected pattern for address A + 0xFFE0. - The same signature was reported with several DLL offset/fine settings. The initialization-time DLL status indicated: DLLA_LOCK = 1 SLVA_LOCK = 1 DLLA_RANGE_ERR = 0 FINE_UNDERFLOW = 0 We have not yet confirmed that these status values remain unchanged at the exact instant of every memory failure. The 0xFFE0 displacement is notable because it equals 0x10000 - 0x20, but we do not assume that this proves a 64-KiB wrap or AHB addressing issue. Questions --------- 1. For the S32K328 at 120 MHz DDR with external edge-aligned DQS, should we use the complete configuration from Data Sheet Rev. 14 Table 66, including: TCSS/TCSH = 3/3 SLAVE_AUTO_UPDT = 0 SLV_DLY_OFFSET = 0 SLV_FINE_OFFSET = 0 2. Could you confirm the correct FLSHCR.TDH value for this exact Table 66 column? 3. If SLAVE_AUTO_UPDT = 0 is required, what is the exact sequence for: SLV_EN SLV_UPD DLLEN DLLA_LOCK SLVA_LOCK SLV_UPD clear 4. Is the following initialization sequence valid? DLL configuration dummy AHB read QuadSPI software reset second DLL configuration first IP access first AHB memory-mapped access Or should software reset occur before the only DLL initialization? 5. After clearing SLV_UPD, which DLL lock indications remain valid and should be checked before the first HyperRAM access? 6. Which QuadSPI AHB buffers, FIFOs and sequence pointers must be cleared after software reset, DLL reconfiguration or IP-command access? 7. For the dummy AHB read, should the CPU cache line be invalidated and a DSB executed before the volatile read? 8. Is there any known S32K328 QuadSPI behavior that could return a complete 32-byte block associated with another address, particularly with an apparent displacement of 0xFFE0? 9. Which measurements or register traces would NXP recommend to distinguish between: read-address generation error write-address error stale AHB buffer data CPU cache coherency HyperBus address wrapping external-DQS sampling error We can provide the complete LUT contents, initialization source and register dumps as attachments. Thank you.
View full article