Logging ASM330LHH IMU Data to W25Q64JV External Flash Using S32K344

[sharathkumar2026]

HI team

I am working on an implementation where the ASM330LHH IMU sensor is interfaced with the S32K344 MCU, and the acquired sensor data (for example, accelerometer and gyroscope measurements) must be stored in a W25Q64JVSSIQ external QSPI Flash memory using S32 Design Studio (S32DS) 3.6.8.

Currently, I am facing challenges in integrating the IMU data acquisition with the external Flash storage mechanism.

I would appreciate guidance on the following topics:

1. External Flash (W25Q64JV) Enablement Through QSPI

• What are the recommended steps to configure the QuadSPI (QSPI) peripheral in S32K344 for interfacing with the W25Q64JV external Flash?
• I have already QSPI RTD drivers and configuration modules should be used in S32DS 3.6.8
• How can the QSPI communication be validated after initialization?
• What is the recommended procedure to read the JEDEC ID and verify that the external Flash is detected correctly?

---

2. Integration of ASM330LHH Sensor Data with External Flash Storage

• What is the recommended software architecture for integrating the ASM330LHH sensor driver with the W25Q64JV Flash driver?
• What sequence should be followed to:
  1. Initialize the IMU sensor.
  2. Acquire accelerometer/gyroscope data.
  3. Buffer the sensor samples in RAM.
  4. Program the buffered data into external Flash memory.
• Are there any best practices for implementing page-aligned Flash writes, sector erase management, and circular logging mechanisms?
• How should timestamps and sensor records be organized to support efficient data retrieval?

---

3. Verification and Validation of Stored Data

• What is the recommended approach to verify that the IMU data stored in external Flash matches the originally acquired sensor data?
• Should read-back verification be performed after every page program operation?
• What validation methods are commonly used to ensure data integrity, such as:
  • Flash read/write verification
  • Checksum or CRC validation
  • Memory dump analysis
  • UART/CAN diagnostic logging
• How can the stored accelerometer and gyroscope data be compared against real-time sensor readings to confirm correctness?

---

1.  

[Julián_AragónM]

Hello @sharathkumar2026,

1. There is an already existing example for communicating with the on-board W25Q64 Winbond memory for the FRDM-A-S32K344 board in our Application Code Hub: QSPI Flash Memory Read/Write demo for FRDM-A-S32K344. 

The example performs a device identification via JEDEC ID and status register readout, a continuous sector erase, page write, read-back, and data integrity verification, with RGB LED feedback via GPIO to indicate operation progress and pass/fail status.

You can import it directly through S32DS: 

2. The ASM330LHH is a third-party device, so you must look for its datasheet, or user manual in order to know which commands to send and how to read the data.

I can recommend going over the Motion Sensing using FreeMASTER example. It reads 3-axis acceleration data from an FXLS8964AF accelerometer over LPI2C: It is based on S32K312, and uses FreeMASTER, however, it may prove useful to use it as reference.

3. This depends on the level of robustness your application needs. Read-back verification is usually not needed, simply check returned status after every operation and validate each record with CRC.

Best regards,
Julián