Hi,
We currently have the S32K3x8EVB-Q289 board and we are trying to make the QSPI work with the onboard S26KL512SDABHV030 flash.
After extensive debugging, we have hit a wall and we couldn't figure out what was going on until we found something that we want to clear up.
In the EVB user guide and schematics, it indicates that the S26KL512SDABHV030 is soldered on the board. By inspecting the part, we also confirmed that the markings are:
6KL512SDAHV03 which is the 03 variant (DCARS variant).
After reading the S26K512S datasheet, it states that the DCARS uses the PSC signal to generate the RWDS (needed for reading). However, in the schematics of the EVB, the PSC is not routed anywhere (except to test pad TPAD21). PSC# is RFU on the 3V variant so we don't need it.
Looking at the logic analyzer, we never see the RWDS toggling after the latency period (when we should observe the returned data) and the transfer eventually times out.
We have not been able to get the flash working and we are wondering whether the EVB is shipped with the wrong flash variant.
Thanks for your help.
Michal
Here is another update:
After connecting PSC to SCK, we now have have a RWDS signal.
This confirms the following:
- The 03 (DCARS) variant does need a PSC signal to be able to indicate when data is available. This is currently not connected on the Rev C EVB.
- The 02 (non-DCARS) variant is the IC that should have been installed
Since the PSC signal is not delayed, the RWDS toggle is very close to the data change edges giving us inconsistent readings (we are testing with the device ID reads for now).
Using the internal DQS of the S32K358 also does not provide a reliable method of reading the data as it may not be aligned correctly with data changes.
Please advise
Michal
We have a Rev C board.
So that erratum does not apply to our case, and furthermore, that would still leave the PSC pin disconnected (even if the schematics had them swapped since only the SCK pin is connected).
Reading the S26KL5152S datasheet, it says that we can connect the SCK pin to PSC and the memory would then behave like a 02 (non-DCARS) variant. We will re-work the board to add this connection and see if that fixes the issue.
If you have another solution, please let us know.
Michal
Could you specify used board revision? In the board user manual following erratum is specified:
