NR5340DK + spi_flash example: mx25r6435f@0: device not ready

[tcube]

Hello,

I'm having an error when running the spi_flash example on a nrf5340DK.

I added this to the .conf file to have more info:

CONFIG_FLASH_LOG_LEVEL_DBG=y
CONFIG_LOG=y
CONFIG_LOG_MODE_IMMEDIATE=y

Here are the console logs:

[00:00:00.253,509] <dbg> qspi_nor: qspi_nrfx_configure: RDSR 00 QE 0 need 1: updating
[00:00:00.261,871] <err> qspi_nor: JEDEC id [00 00 00] expect [c2 28 17]
*** Booting nRF Connect SDK v2.5.2 ***
mx25r6435f@0: device not ready.

I'm using ncs 2.5.2.

Am I missing something to run this example?

[Vidar Berg]

Hello,

Please try to run the example again after having erased the flash with nrfjprog:  nrf52840DK QSPI Flash memory . That, or try to power-cycle the DK.

$ nrfjprog --qspieraseall -f nrf53

 

Best regards,

Vidar

[Chasen]

Hello Vidar,

I am experiencing the same issue however it is on a custom board based n the nrf5340dk. The flash chip is the same as the one used on the dk. The only differrence is that I made a mistake in my schematic, and swapped CS and SCLK. I was able to swap them in the device tree and verified with a scope that the change registered properly.

Yellow - Clock input at chip

Blue - CS input at chip

Left - nF5340DK schematic

Right - Custom Board

When I attempt to run the spi_flash example code I receive the following.

And when I attempt to run the erase flash command referenced above, I get an error. However I get the error when I attempted it on my nRF5340dk as well.

attached is the log.log after I run the command.

Any suggestions would greatly be appreciated!

Thank you in advance!

7848.log.log

[Vidar Berg]

Hello,

The problem reported by the OP was likely caused by a QSPI NOR driver bug that was present in SDK v2.5.2. This bug was fixed in v2.5.3, which you are currently using.

Ref. https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/releases/release-notes-2.5.3.html 

Fix: https://github.com/zephyrproject-rtos/zephyr/pull/71373/commits/2ece3803177a6b4567f6d8465bacb3a613d9a1ab 

Are you able to probe the other two lines to check if the flash is responding at all? 

Edit: Forgot to add that nrfjprog is only able to interface with the external flash when the standard pinout is used.

[Chasen]

Hello Vidar,

Thanks for the quick response! Ill try and probe the additional signals and report back.

[Chasen]

I was able to capture a couple of traces this morning, but could only do 2 at a time

CLK(Blue) + SIO_0/SI(Red)

CLK(Blue) + SIO_0/SI(Red) -Zoomed

CLK(Blue) + SIO_1/SO(Red)

CLK(Blue) + SIO_1/SO(Red) - Zoomed

I tried slowing the clock down to see if it was a signal integrity issue, but does seems like 6MHz is the slowest I can go on the nRF53. If you have anything else I could try, let me know. In the mean time ill work on bringup of another board in hopes that it is a fault connection or chip.

Thanks again!