Programming QSPI with nrfjprog for nrf5340

RE: Programming QSPI with nrfjprog for nrf5340

edmcnicholas — Wed, 24 Jul 2024 01:15:51 GMT

No but hopfully there will be a simpler method then pm_static in the future.

RE: Programming QSPI with nrfjprog for nrf5340

Priyanka — Fri, 19 Jul 2024 09:24:52 GMT

Hi Edward,

Apologies for the delay as it's the summer holidays and we are understaffed.

Do you still have the issue?

-Priyanka

RE: Programming QSPI with nrfjprog for nrf5340

edmcnicholas — Thu, 18 Jul 2024 14:45:25 GMT

i had the external memory setup incorrectly in the pm_static

RE: Programming QSPI with nrfjprog for nrf5340

edmcnicholas — Thu, 18 Jul 2024 13:45:25 GMT

So I believe this is something to do with partition manager since my project uses bluetooth and the fs project does not. Below is my device tree and that works in fs but in my project i require a pm static.

&mx25l256 {
	partitions {
		compatible = "fixed-partitions";
		#address-cells = <1>;
		#size-cells = <1>;

		/* 128kiB external storage partition */
		external_partition: partition@f0000 {
			label = "disk";
			reg = <0x0000f0000 0x000800000>;
		};
	};
};

/ {
	msc_disk0 {
		status="okay";
		compatible = "zephyr,flash-disk";
		partition = <&external_partition>;
		disk-name = "SD";
		/* cache-size == page erase size */
		cache-size = <4096>;
	};
};

RE: Programming QSPI with nrfjprog for nrf5340

edmcnicholas — Thu, 18 Jul 2024 13:38:29 GMT

Ok so now I can read the files from the fs project so I need to figure out the difference between the 2 projects. I did have to add 32bit addressing to the device tree as well.

RE: Programming QSPI with nrfjprog for nrf5340

edmcnicholas — Thu, 18 Jul 2024 13:14:16 GMT

So i have gotten it to write by adding a 32bit addressing custom command, but i cant seem to find the file system now.

RE: Programming QSPI with nrfjprog for nrf5340

edmcnicholas — Thu, 18 Jul 2024 11:31:44 GMT

so the files seems to be overwriting itself every page. if i limit the file to the first page then it works but after that it seems to overwrite it. It cant seem to move past the first page. below is my init and i am using the MX25L25645GZNI

;----------------------------------------------
; Deprecated, use config.toml format instead
;----------------------------------------------

; nrfjprog QSPI 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 = 0x2000000

; 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 = PP4IO

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

; 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 = 0x80

; Define SPI interface timing. Valid options are in the range of 0 to 7.
; This argument is only used for devices where the dll function NRFJPROG_qspi_set_rx_delay() is supported.
RxDelay = 2

; 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

; Define the assigned pins for the QSPI peripheral. Valid options are those existing in your device
; For nRF53, QSPI pins are not configurable and these values are ignored.
CSNPin = 17
CSNPort = 0
SCKPin = 19
SCKPort = 0
DIO0Pin = 13
DIO0Port = 0
DIO1Pin = 14
DIO1Port = 0
DIO2Pin = 15
DIO2Port = 0
DIO3Pin = 16
DIO3Port = 0

; 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. Format is instruction code plus data to send in between optional brakets. 
; These instructions will be executed each time the qspi peripheral is initiated by nrfjprog. 
; To improve execution speed on consecutive interations with QSPI, you can run nrfjprog once with custom initialization, and then comment out the lines below.
; 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] 

; If retention is enabled, device RAM contents will be read and buffered during QSPI driver initialization.
; The buffered data will be written back to the device when unitializing the driver, restoring the original device RAM state.
; Enabled: RetainRAM = 1, Disabled: RetainRAM = 0
RetainRAM = 1

RE: Programming QSPI with nrfjprog for nrf5340

edmcnicholas — Thu, 18 Jul 2024 09:47:27 GMT

How would I be able to debug nrfjprog

RE: Programming QSPI with nrfjprog for nrf5340

edmcnicholas — Thu, 18 Jul 2024 09:46:30 GMT

Well since I am trying to load a file system it is a bit different but the Intel hex file I generated looks correct. I have also tried the base of qspi at 0x10000000 with the same results.

RE: Programming QSPI with nrfjprog for nrf5340

Priyanka — Thu, 18 Jul 2024 09:21:48 GMT

Hi Edward,

It does look puzzling. Please make sure our bin file is properly aligned, i.e. sometimes padding can help. Also, please verify that your memory layout does not overlap with any other critical regions. For further understanding, it would also be good to use a debugger t step through the initialization and programming process.

-Priyanka

RE: Programming QSPI with nrfjprog for nrf5340

edmcnicholas — Wed, 17 Jul 2024 16:56:11 GMT

D:\ZephyrWorkspace\ShockStream\Controller\fs>D:\Nordic\toolchains\cf2149caf2\opt\zephyr-sdk\arm-zephyr-eabi\bin\arm-zephyr-eabi-objcopy.exe  -v -I binary -O ihex --change-addresses 0x100f0000 nor2.bin nor2.hex
copy from `nor2.bin' [binary] to `nor2.hex' [ihex]

D:\ZephyrWorkspace\ShockStream\Controller\fs>nrfjprog  --log -f nRF53 --qspiini con_qspi.ini    --qspieraseall
WARNING: An operation that can take up to several minutes is being executed.
WARNING: Please remain patient.
Initializing the QSPI peripheral.
Erasing.
Uninitializing the QSPI peripheral.

D:\ZephyrWorkspace\ShockStream\Controller\fs>nrfjprog  --log -f nRF53 --qspiini con_qspi.ini --memrd 0x100F0000  --n 100

[ #################### ]   0.000s | Reading external memory, 0x0064 bytes @ 0x000F0000 - Done
0x100F0000: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF   |................|
0x100F0010: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF   |................|
0x100F0020: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF   |................|
0x100F0030: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF   |................|
0x100F0040: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF   |................|
0x100F0050: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF   |................|
0x100F0060: FFFFFFFF                              |....|

RE: Programming QSPI with nrfjprog for nrf5340

edmcnicholas — Wed, 17 Jul 2024 13:35:16 GMT

I already did that it is all 0xff. You can also see that the other bytes in the write read are 0xff

RE: Programming QSPI with nrfjprog for nrf5340

Priyanka — Wed, 17 Jul 2024 13:13:02 GMT

Hi Edward,

Could you check that the QSPI flash memory is properly erased before writing?

nrfjprog --log -f nRF53 --qspiini con_qspi.ini --qspieraseall

Regards,

Priyanka

RE: Programming QSPI with nrfjprog for nrf5340

edmcnicholas — Tue, 16 Jul 2024 22:39:17 GMT

I tried doing the same to my zephyr.hex from the project with the same results