XIP problems with a custom board running nrf5340

RE: XIP problems with a custom board running nrf5340

Pelle — Fri, 09 Sep 2022 09:34:15 GMT

PROBLEM SOLVED

Added a custom QSPI settings file with these properties and used it with the command:

nrfjprog --qspiini ../app/QspiSettings.ini --coprocessor CP_APPLICATION --sectorerase --qspisectorerase --program zephyr.hex --verify

The added part above is "--qspiini ../app/QspiSettings.ini" which adds a custom settings file for the correct flash device.

And this is how the file looks like:
(I changed the following parameters to correspond to W25Q64 flash memory):

MemSize = 8000000 (instead of 800000)
WriteMode = PP4O (instead of PP4IO which is not supported by W25Q64)
SckDelay = 0xA (instead of 0x80)

And changed all pins to correct values.

All of those parameters above was found in the data sheet of W25Q64 flash.

; nrfjprog.exe configuration file.

[DEFAULT_CONFIGURATION]
; Define the capacity of the flash memory device in bytes. Set to 0 if no external memory device is present in your board.
MemSize = 8000000

; Define the desired ReadMode. Valid options are FASTREAD, READ2O, READ2IO, READ4O and READ4IO
ReadMode = READ4IO

; Define the desired WriteMode. Valid options are PP, PP2O, PP4O and PP4IO
WriteMode = PP4O

; Define the desired AddressMode. Valid options are BIT24 and BIT32
AddressMode = BIT24

; Define the desired Frequency. Valid options are M2, M4, M8, M16 and M32
Frequency = M16

; Define the desired SPI mode. Valid options are MODE0 and MODE3
SpiMode = MODE0

; Define the desired SckDelay. Valid options are in the range 0 to 255
SckDelay = 0xA

; Define the desired IO level for DIO2 and DIO3 during a custom instruction. Valid options are LEVEL_HIGH and LEVEL_LOW
CustomInstructionIO2Level = LEVEL_LOW
CustomInstructionIO3Level = LEVEL_HIGH

CSNPin = 18
CSNPort = 0
SCKPin = 17
SCKPort = 0
DIO0Pin = 13
DIO0Port = 0
DIO1Pin = 14
DIO1Port = 0
DIO2Pin = 15
DIO2Port = 0
DIO3Pin = 16
DIO3Port = 0


; Define the assigned pins for the QSPI peripheral. Valid options are those existing in your device

; Define the Index of the Write In Progress (WIP) bit in the status register. Valid options are in the range of 0 to 7.
WIPIndex = 0

; Define page size for commands. Valid sizes are PAGE256 and PAGE512.
PPSize = PAGE256

; Custom instructions to send to the external memory after initialization. Only used if --qspicustominit option is given in the call to nrfjprog. Format is 
; instruction code plus data to send in between optional brakets. Numbers can be given in decimal, hex (starting with either 0x or 0X) and binary (starting 
; with either 0b or 0B) formats. The custom instructions will be executed in the order found. 
; This example includes two commands, first a WREN (WRite ENable) and then a WRSR (WRite Satus Register) enabling the Quad Operation and the High Performance
; mode for the MX25R6435F memory present in the nRF52840 DK.
InitializationCustomInstruction =  0x06
InitializationCustomInstruction =  0x01, [0x40, 0, 0x2]

RE: XIP problems with a custom board running nrf5340

Pelle — Fri, 09 Sep 2022 08:01:27 GMT

I've changed jedec-id and didn't help, also updated some other properties. Still doesn't work when trying to flash the external memory.

I'm still wondering how the flash procedure for the external flash works. It must be the nordic bootloader in ROM that handles it right? Then it shouldn't matter at flash-time how the QSPI peripheral is setup by the user in dts files?
I read something about an init file for qspi for flashing, using:

--qspiini <file>

I've been using this so far and probably this is for the devkit (mx25r64 flash):

--qspicustominit

How to write this QSPI settings file, any examples?

Thanks

RE: XIP problems with a custom board running nrf5340

Jørgen Holmefjord — Thu, 08 Sep 2022 15:01:37 GMT

The Devicetree properties are described in the documentation. You definitely need to change the jedec-id to the ID described in the datasheet of your flash device.

RE: XIP problems with a custom board running nrf5340

Pelle — Thu, 08 Sep 2022 13:34:13 GMT

Hi, I have modified the dts file for the qspi node..

But not sure exactly what everything means in that node, very confusing. This is how the qspi node looks like now in the .dts file:

&qspi {
	status = "okay";
	pinctrl-0 = <&qspi_default>;
	pinctrl-1 = <&qspi_sleep>;
	pinctrl-names = "default", "sleep";
	w25q64: w25q64jw@0 {
		compatible = "nordic,qspi-nor";
		reg = <0>;
		/* MX25R64 supports only pp and pp4io */
		writeoc = "pp4o";
		/* MX25R64 supports all readoc options */
		readoc = "read4io";
		sck-frequency = <8000000>;
		label = "W25Q64";
		jedec-id = [c2 28 17];
		sfdp-bfp = [
			e5 20 f1 ff  ff ff ff 03  44 eb 08 6b  08 3b 04 bb
			ee ff ff ff  ff ff 00 ff  ff ff 00 ff  0c 20 0f 52
			10 d8 00 ff  23 72 f5 00  82 ed 04 cc  44 83 68 44
			30 b0 30 b0  f7 c4 d5 5c  00 be 29 ff  f0 d0 ff ff
		];
		size = <67108864>;
		has-dpd;
		t-enter-dpd = <10000>;
		t-exit-dpd = <35000>;
	};
};

But still, wondering what happens during the Flash procedure? Is this .dts config used when flashing the external memory?

RE: XIP problems with a custom board running nrf5340

Jørgen Holmefjord — Thu, 08 Sep 2022 13:31:11 GMT

Hi,

Have you added an overlay to define the correct flash chip? The MX25R64 is defined in the nRF5340 DK devicetree. If you are using a different flash chip you need to add an overlay with the correct config for that chip. You may reference part of this post for a similar flash chip, but that is for SPI and not QSPI.

Best regards,
Jørgen