nrf5340dk qspi_nor flash driver - fastread no longer working

[DevanMallory]

We are trying to build an qspi external flash application with the nrf5340dk. However, I noticed, that when going from ncs v2.4.2 to v2.5.2, the qspi_nor flash driver no longer works when configuring the readoc to use fastread instead of read4io, on a default nrf5340 development kit with the built in MXR25R64 flash. I've managed to replicate this in the mass storage sample, the spi flash sample, and in our own project that utilizes the qspi nor driver. The specific error that comes up is that the jdec ID on the flash somehow reads as all zeros, instead of the actual jdec id on the flash. Do you know if you could help resolve this in a future version of ncs? So far, I have tried replacing the code for the driver itself (nrf_qspi_nor.c) in 2.5.2 with the code from 2.4.2, but that has not resolved the issue.

Thanks,

Devan Mallory

[DevanMallory]

Dear Hung Bui,

Yes, sorry about that, you are correct, on version ncs 2.5.0 fastread actually works so the issue is in v2.5.1. the mass storage sample I used is located in ncs\v2.5.1\zephyr\samples\subsys\usb\mass, and I used the nrf5340dk_nrf5340_cpuapp.overlay file located in the boards folder. In my overlay I also copied the &qspi node from the nrf340 cpuapp dtsi file, and then edited the read and write operations as shown in the first picture that I sent. The overlay was working with pp4io and read4io, but failing when I put pp and fastread instead.

[Hung Bui]

Hi Devan, 
Good to know that v2.5.0 works. Could you please provide the nrf5340dk_nrf5340_cpuapp.overlay you used or the one that can reproduce the issue ?I just want to make sure we use the same file. 

[DevanMallory]

nrf5340dk_nrf5340_cpuapp (2).overlaysure, here it is

[Hung Bui]

Hi Devan, 
I'm sorry for late reply. But I tried here on all 3 SDK v2.5.0 , v2.5.1 and v2.5.2 and they all seems to work fine. 

I can format the flash drive and copy a file to it. 
Could you try with the attached hex, it's compiled with your overlay and in SDK v2.5.2 

5460.zephyr.hex

2063.mass.zip

[DevanMallory]

Oh sorry, I forgot to mention that in the mass example it is failing specifically when there is a pre-existing file system configured. To enable this in the kconfig, I added the line:

CONFIG_APP_MSC_STORAGE_FLASH_LITTLEFS=y

 to the project as mentioned in the README.rst and Kconfig definition file.

[Hung Bui]

Hi Mallory, 
When I use the config you provided I can see the size of the drive changed to 128kB, but I still can copy a file into it. 
To avoid a lot of back and forth, please provide us a .zip file of your mass project. 
Also please tell what exactly expected and what exactly doesn't work as expected, extra log and assert please. 
I'm not very familiar with the mass/USB sample so you will need to be very specific :) 

[DevanMallory]

Sorry for not replying for a long time, got busy with some other projects but I just would like to clarify that the issue we were experiencing was related to this:  spi_flash is not running on nRF5340DK out of box  It looks like they are going to hopefully fix it.

[ovrebekk]

Hi 

The issue should be fixed in the v2.6.1 and v2.5.3 releases of the SDK. 

Best regards
Torbjørn