Changing Flash parameters in overlay file

RE: Changing Flash parameters in overlay file

CktDesigner — Tue, 06 Sep 2022 02:34:18 GMT

OK, thanks... I didn't read the spec as carefully as I should have... My bad!

Thanks again...

RE: Changing Flash parameters in overlay file

Simonr — Mon, 05 Sep 2022 13:55:25 GMT

Hi again

I asked one of our FileSystem gurus, and this seems to be the cause for your issue:

- Hybrid sector size option - Physical set of thirty two 4kB sectors at top or bottom of address space with all remaining sectors of 64 KB, for compatibility with prior generation S25FL devices.

- Uniform sector option - always erase 256-KB blocks for software compatibility with higher density and future
devices.

The sector size is huge, it is not 4KB and is not uniform.

Best regards,

Simon

RE: Changing Flash parameters in overlay file

CktDesigner — Thu, 01 Sep 2022 13:54:38 GMT

As noted in the previous post... I didn't change the name for the memory entry, but did change some parameters (jedec-id, size, etc.). The name shouldn't matter. It only provides an identifier so it can be referenced from other places.

RE: Changing Flash parameters in overlay file

Simonr — Thu, 01 Sep 2022 11:04:14 GMT

From this .dts file it seems like the QSPI is defined as the MX25 flash chip that is onboard the nRF52840. You need to configure it for the S25FL that you're using. Make sure that the size and write/read permissions fits that board.

Best regards,

Simon

RE: Changing Flash parameters in overlay file

CktDesigner — Wed, 31 Aug 2022 15:52:14 GMT

Here is the file:

/*
 * Copyright (c) 2017 Linaro Limited
 *
 * SPDX-License-Identifier: Apache-2.0
 */

/dts-v1/;
#include <nordic/nrf52840_qiaa.dtsi>

/ {
	model = "Nordic nRF52840 ModelRocket";
	compatible = "nordic,nrf52840-dk-nrf52840";

	chosen {

#if 1
                zephyr,gps-uart = &uart0;
#endif
		zephyr,sram = &sram0;
		zephyr,flash = &flash0;
		zephyr,code-partition = &slot0_partition;
	};




	nrf_radio_fem: ble_pa {
	   compatible = "skyworks,sky66112-11", "generic-fem-two-ctrl-pins";
	   ctx-gpios = <&gpio1 2 GPIO_ACTIVE_HIGH>;
	   crx-gpios = <&gpio1 4 GPIO_ACTIVE_HIGH>;
    };

	fstab {
		compatible = "zephyr,fstab";
		lfs2: lfs2 {
			compatible = "zephyr,fstab,littlefs";
			mount-point = "/lfs2";
			partition = <&lfs2_part>;
/*
			automount;
*/
			read-size = <16>;
			prog-size = <16>;
			cache-size = <64>;
			lookahead-size = <32>;
			block-cycles = <512>;
		};
	};


};


&adc {
	status = "okay";
};

&gpiote {
	status = "okay";
};

&gpio0 {
	status = "okay";
};

&gpio1 {
	status = "okay";
};

&uart0 {
	compatible = "nordic,nrf-uarte";
	status = "okay";
	current-speed = <115200>;
	tx-pin = <12>;
	rx-pin = <41>;
        /delete-property/ rts-pin;
        /delete-property/ cts-pin;
};

&uart1 {
        compatible = "nordic,nrf-uarte";
	status = "disabled";
	current-speed = <115200>;
        /* Unused pins */
	rx-pin = <33>;
	tx-pin = <25>;
};

&i2c0 {
	compatible = "nordic,nrf-twim";
        /* Cannot be used together with spi0 */
	status = "okay";
	sda-pin = <26>;
	scl-pin = <27>;
};

&i2c1 {
	compatible = "nordic,nrf-twim";
	/* Cannot be used together with spi1. */
	status = "okay";
	sda-pin = <11>;
	scl-pin = <13>;
};

&pwm0 {
	status = "disabled";
	ch0-pin = <14>;
	ch0-inverted;
};

&spi0 {
	compatible = "nordic,nrf-spi";
	/* Cannot be used together with i2c0. */
	status = "disabled";
	sck-pin = <27>;
	mosi-pin = <26>;
	miso-pin = <29>;
};

&spi1 {
	compatible = "nordic,nrf-spi";
        /* Cannot be used together with i2c1 */
	status = "disabled";
	sck-pin = <31>;
	mosi-pin = <30>;
	miso-pin = <40>;
};

&spi2 {
	compatible = "nordic,nrf-spi";
	status = "disabled";
	sck-pin = <19>;
	mosi-pin = <20>;
	miso-pin = <21>;
};

&spi3 {
	compatible = "nordic,nrf-spi";
	status = "disabled";
	sck-pin = <47>;
	mosi-pin = <46>;
	miso-pin = <45>;
};

&qspi {
	status = "okay";
	sck-pin = <19>;
	io-pins = <20>, <21>, <22>, <23>;
	csn-pins = <17>;
	mx25r64: mx25r6435f@0 {
		compatible = "nordic,qspi-nor";
		reg = <0>;
		/* MX25R64 supports only pp and pp4io */
		writeoc = "pp4io";
		/* MX25R64 supports all readoc options */
		readoc = "read4io";
		sck-frequency = <8000000>;
		label = "MX25R64";

		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
		];

		has-dpd;
		t-enter-dpd = <10000>;
		t-exit-dpd = <35000>;

#if 0
		jedec-id = [c2 28 17];
		size = <67108864>;
#endif
		jedec-id = [01 20 18];
        size = <134217728>;
		partitions {
			compatible = "fixed-partitions";
			#address-cells = <1>;
			#size-cells = <1>;

			lfs2_part: partition@0 {
				label = "main_storage";
				reg = <0x00000000 0x02000000>;
			};
			
		};
		/* End from overlay */
	};
};

&flash0 {

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

		boot_partition: partition@0 {
			label = "mcuboot";
			reg = <0x000000000 0x0000C000>;
		};
		slot0_partition: partition@c000 {
			label = "image-0";
			reg = <0x0000C000 0x00067000>;
		};
		slot1_partition: partition@73000 {
			label = "image-1";
			reg = <0x00073000 0x00067000>;
		};
		scratch_partition: partition@da000 {
			label = "image-scratch";
			reg = <0x000da000 0x0001e000>;
		};

		/*
		 * The flash starting at 0x000f8000 and ending at
		 * 0x000fffff is reserved for use by the application.
		 */

		/*
		 * Storage partition will be used by FCB/LittleFS/NVS
		 * if enabled.
		 */
		storage_partition: partition@f8000 {
			label = "storage";
			reg = <0x000f8000 0x00008000>;
		};
	};
};

zephyr_udc0: &usbd {
	compatible = "nordic,nrf-usbd";
	status = "okay";
};

Note that I started with the nRF52840-DK file and edited it to reflect my board. Also, I have two file systems. "/lfs1" mounts the on-chip storage partition, while "/lfs2" is for the external flash device attached to the QSPI bus. Also note that I didn't change the "name" of the flash device, but rather changed the important parameters.

Thanks!

RE: Changing Flash parameters in overlay file

Simonr — Tue, 30 Aug 2022 10:46:53 GMT

Can you upload the overlay (.dts) file where your QSPI (pins, size, etc.) are set up of how it looks now so we can take a look? I'm afraid I'm not familiar with an error in this line in lfs.c, but it seems like the dir pair is corrupted at some point when trying to fetch a matching dir...

Best regards,

Simon

RE: Changing Flash parameters in overlay file

CktDesigner — Mon, 29 Aug 2022 15:44:50 GMT

Hi Simon,

Yes...

Still using nRF52840 and S25FL external flash connected via QSPI, so it is not an SD card (your referenced case deals with SD cards).

I've also moved to NCS 2.0.2 (the latest released version of NCS).

I've had trouble finding any detailed documentation on the structure/internals of littleFS. But I've traced through the code and the error appears to occur when the CRCs are being checked during the formatting process. I saw one post that implied that the config statement "CONFIG_APP_WIPE_STORAGE=y" should be included in prj.conf, but if I do so, the build process fails, indicating that this configuration variable was not found.

I assume the physical interface to the chip works since it reads the jedec-id (I had to change the listed on in the .dts file to expect the one in the S25FL device.). As I mentioned earlier, I had the software running on the -DK board, but am struggling to get it working on my custom board with a different (larger) QSPI device.

Thanks...

RE: Changing Flash parameters in overlay file

Simonr — Mon, 29 Aug 2022 11:59:18 GMT

It's been a while, so just to make sure we're on the same page. You're still using an nRF52840, the S25FL external flash, and you're still having error -5 (I/O error) when trying to mount the external board. Is that correct?

This could be due to the mount process already being in progress when this is called somehow. You can try waiting for the SD card to be detected before starting the mount process. You can also check out this case where my colleague Torbjørn provided a possible fix to a mount error like this.

Best regards,

Simon

RE: Changing Flash parameters in overlay file

CktDesigner — Sat, 27 Aug 2022 17:29:10 GMT

Hi Simon,

I moved on to other issues (and other projects), but am now back to trying to solve this issue.

I'm now using NCS 2.0.0 but having the same issues. I'm actually using two LFS volumes. One uses an on-chip storage partition (and works well), and the other attempts to mount the qspi-nor device (for larger data files) and is still having issues mounting...

Any thoughts?

Thanks!

RE: Changing Flash parameters in overlay file

Simonr — Fri, 01 Oct 2021 06:24:11 GMT

I have asked our development team to take a look at this, but I'm still waiting for a reply there. Hopefully I'll hear back either today or just over the weekend. Thank you for your patience.

Best regards,

Simon

RE: Changing Flash parameters in overlay file

CktDesigner — Tue, 28 Sep 2021 23:07:38 GMT

OK, thanks.

I updated the overlay to reflect the 128 Mbit size of the Cypress part, but it didn't make any difference. Still fails during format with error code of -5.

Thanks again...

RE: Changing Flash parameters in overlay file

Simonr — Mon, 27 Sep 2021 10:54:57 GMT

Hi again

Yes, you seem to be right indeed.

I have looked at the Macronix and Cypress write procedures, and they seem very similar, so I've not been able to track down what exact changes are necessary to be done yet, but I have a few suggestions, and I'm also awaiting a reply from our FS/QSPI experts (I hoped they got back to me by today, but they have not). I will update you as soon as I hear from them.

You can try setting the size in your overlay file to match the size of your Cypress chip. Since you're able to read the JEDEC ID correctly for instance, the flash chip seems to be set up correctly, but the file system procedure is what's not working as intended.

Best regards,

Simon

RE: Changing Flash parameters in overlay file

CktDesigner — Thu, 23 Sep 2021 14:11:37 GMT

Yes, I'm using the project you referenced.

But in main.c at lines 20 through 32 it defines "PARTITION_MODE" which references /lfs1 which is defined in the overlay file. There, the partition /lfs1_part is referenced which is defined in the &mx25r64, which is the Flash device connected via the qspi bus.

So by default, the example uses the external flash. I think to use the SOC flash you have to comment out the definition of PARTITION_MODE on main.c line 20...

I needed to add the jedec-id line to redefine the device id to the one I'm using on my custom board. When it still didn't work I thought that some other parameter must need to be adjusted but didn't see any concise definitions for these parameters.

RE: Changing Flash parameters in overlay file

Simonr — Thu, 23 Sep 2021 07:51:00 GMT

Just to clarify, the project you're using is the littleFS File System Sample application in Zephyr, correct? I assume you have noticed that on an nRF52840 DK, the file system will be placed in the SoC flash by default. Have you not made any changes to make it use the external flash device except adding the jedec-id in your overlay file?

Best regards,

Simon

RE: Changing Flash parameters in overlay file

CktDesigner — Tue, 21 Sep 2021 18:25:19 GMT

Hi Simon,

Thanks for your assistance!

The only change I made to the example project was to add a line in the .overlay file for nrf52840kd_nrf52840 to change the jedec-id for the device I'm using.

So the line: jedec-id = [01 20 18]; was added as line 27 of that file.

I know the size parameters will need to be changed, but figured that could be done after the basic operation was verified since the new part is larger than the one on the nRF52840-DK.

The device I'm using is a Cypress S25FL128SAGNFI001 (https://www.digikey.com/en/products/detail/cypress-semiconductor-corp/S25FL128SAGNFI001/13167436)

The datasheet is: https://www.cypress.com/file/448601/download

Thanks!

RE: Changing Flash parameters in overlay file

Simonr — Tue, 21 Sep 2021 09:27:16 GMT

Hi again

Okay, so it seems like the error you're seeing is that the device tries to mount with the settings/parameters you're using, but is not able to because the settings aren't stored correctly. CONFIG_APP_WIPE_STORAGE does not seem to be the way to go, seeing as the littleFS device hasn't been written to at all before. It should be sufficient to set up the device, let it fail to mount as LittleFS will have to format the device, and then reset it when the device is formatted correctly. If you then try to mount (automount should be fine as well), the device should be able to mount.

If you're still running into errors, can you tell me in detail what changes you've made to the example project and maybe provide a link to the datasheet of the Flash device you're trying to format for?

Best regards,

Simon

RE: Changing Flash parameters in overlay file

CktDesigner — Sat, 18 Sep 2021 19:09:25 GMT

I stepped back and used the littlefs sample project to just test the Flash/LittleFS interface of my new board. Since the board is new, the flash has never been written, so when booting, the mount fails (as expected with an error at lfs.c line 997 (Corrupted dir pair at (0x0, 0x1))) and it appears LittleFS attempts to format the device. It looks like it prepares a superblock, then attempts to write it. A failure occurs during formatting (returning -28). Looking this up in lfs.h shows that -28 indicates LFS_ERR_NOSPC (no space left on device). Stepping through, it looks like the error is being thrown at line 1692 of lfs.c due to the comparison at line 1689. I'm not sure why this is happening yet. The device is new, so is there some other (erase?) procedure that needs to be performed before running this test? I would think that formatting would prepare/initialize any information about the device needed for the file system?

I removed the comment from the CONFIG_APP_WIPE_STORAGE=y line in prj.conf thinking that perhaps it might erase the device during the formatting process, but got the same error (-28).

Note that CONFIG_APP_WIPE_STORAGE=y works here, but if I put it in my prj.conf running Cmake fails! Both are using NCS 1.6.1 Running without the APP_WIPE config statement causes an error -5 (LFS_ERR_IO - Error during device operation). As mentioned earlier, the device on the new board is very similar to the one on nRF52840DK, except larger.

Thanks!

RE: Changing Flash parameters in overlay file

CktDesigner — Fri, 17 Sep 2021 12:56:07 GMT

Hi Simon,

If "CONFIG_APP_WIPE_STORAGE=y" is included in prj.conf I get an error when Cmake executes.

I then checked: http://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/kconfig/index-all.html

and didn't see it listed as a legal CONFIG option, so I assumed it had been removed.

The call returns -5 (0xfffffffb)

Sorry, line 1051 should be 1851...

Thanks!

RE: Changing Flash parameters in overlay file

Simonr — Fri, 17 Sep 2021 10:47:35 GMT

Where do you see that the CONFIG_APP_WIPE_STORAGE config is not supported in NCS v1.6.1? It seems to be included as an optional configuration in the littlefs sample project for instance. lfs_dir_compact is not in line 1051 of lfs.c on my end. Can you show me the exact error and return code you're getting?

Best regards,

Simon

RE: Changing Flash parameters in overlay file

CktDesigner — Thu, 16 Sep 2021 05:35:41 GMT

Hi Simon,

Thanks... I commented out the "automount", so the messages shown in the screen capture simply move from before boot to after boot (when I then have to manually mount the file system).

In reading through the code (and looking through lots of posts), it appears that the problem occurs because the Flash is new (hasn't been written). It seems that the LittleFS attempts to format the Flash but fails. I saw a post that recommended using "CONFIG_APP_WIPE_STORAGE=y" in the prj.conf file, but that doesn't seem to be supported in the version I'm using (NCS 1.6.1). More tracing seems to show that a call to "lfs_dir_compact" (during format? on line 1051 of lfs.c) returns -5 (fffffffb). Haven't figured out why yet...

RE: Changing Flash parameters in overlay file

Simonr — Fri, 10 Sep 2021 10:17:38 GMT

This could to relate to an issue with the automount flag in the .overlay file of NCS. Can you try commenting out the automount flag in the .overlay file to see if the mount error resolves. This is an issue internally that we're currently looking at and the fix will likely be added to a future release of NCS.

Best regards,

Simon

RE: Changing Flash parameters in overlay file

CktDesigner — Thu, 09 Sep 2021 03:21:11 GMT

Hi Simon,

Thanks for your reply.

To be truthful, I'm not sure right now what parameter(s) I need to change. I'm transitioning from using the nRF52840-DK for development/evaluation to my custom board for production and trying to get the file system to function using a slightly different Flash device. The attached image shows the errors I'm seeing (minus the mismatch JEDEC-ID which was easy to fix). Since the errors occur prior to the call to "main()", I assumed that some parameter set in the device-tree must be the culprit, but then couldn't find documentation/definitions for the variables set there. The call you referenced would be executed in main (at the earliest), after the error occurs (without editing code that probably shouldn't be changed). Zephyr must be attempting to initialize the file system and failing. The Flash interface must be "basically" working since it reads the JEDEC-ID (and the error is not thrown once the correct value was put into the overlay file). So I'm looking for documentation so I can try to figure out what is happening (without having to read through a lot of Zephyr boot code). Any pointers would be appreciated!!

Thanks!

RE: Changing Flash parameters in overlay file

Simonr — Tue, 07 Sep 2021 06:52:55 GMT

What flash parameters specifically are you looking to modify? The block size and erase value are set in the qspi_flash_parameters() function in nrf_qspi_nor.c for instance, and all flash parameters can be found in flash.h in \zephyr\include\drivers\flash.h

Best regards,

Simon