Error while testing spi_flash sample on nrf53 and nrf52840 DK

[Vivek]

 Hi Team,

I am facing an issue while testing spi_flash sample while testing it on nrf5340 as well as nrf52840 DK. Attaching the code with the ticket. The sample throws below error.

sample_spi_flash_1.zip

Please have a look and let me know what's the issue with this sample as it's unable to detect the flash here.

Thanks

[Vidar Berg]

Hi,

I built and ran your project on a nRF52840 DK, but was unable to reproduce the problem.

Please try to program the hex file below which is from my build and see if you can get the same result on your nRF52840 DK. 

HEX file

6318.merged.hex

nrfjprog --program merged.hex --chiperase --verify --reset

If this does not work either, try to erase the external flash with nrfjprog:

nrfjprog -f nrf52 --qspieraseall
nrfjrog -r

Best regards,

Vidar

[Vivek]

Hi

Vidar Berg said:

6318.merged.hex

we tried flashing this hex file as well as tried the two commands as mentioned but still the problem is not resolved.

Vidar Berg said:

If this does not work either, try to erase the external flash with nrfjprog:

The error still persists. We are currently using NCS 2.8.0 so is there any issue with that?

Awaiting for the response.

Thanks.

[Vidar Berg]

It is surprising that my pre-compiled hex file works on my DK but fails on yours when you can erase the Macronix flash using nrfjprog without issues. This suggests that the connections and power to the flash are ok.

Are you also able to write and read from the external flash using nrfjprog?

nrfjprog -f nrf52 --qspieraseall
# Write test word to Macronix flash
nrfjprog -f nrf52 --memwr 0x12000000 --val 0x123456
# Read back value to confirm it was stored correctly
nrfjprog -f nrf52 --memrd 0x12000000

[Vivek]

Hi, 
No, we are not able to do that. The memory (device) is not ready, it says.
Did you run your program using nrf SDK v2.8.0. We are using v2.8.0
Is there any issue here?

[Vidar Berg]

I'm using SDK v2.8.0 as you can see from the log I posted in my first answer. Also, if we are testing with the same hex file there is not really any reason to suspect the problem is with the configuration or build setup.