Interfacing FAT file system into WinbondW25Q02 using SPI-nor driver

RE: Interfacing FAT file system into WinbondW25Q02 using SPI-nor driver

Barsa — Tue, 15 Oct 2024 18:42:20 GMT

Hi Ahaug,

No I still haven't figured out the solution.

Regards,

Barsha

RE: Interfacing FAT file system into WinbondW25Q02 using SPI-nor driver

AHaug — Mon, 14 Oct 2024 08:23:01 GMT

Hi,

[quote user="Barsa"] I am using JLink Edu V10.10[/quote]

I was referring to the Segger J-link installation from this step: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/installation/install_ncs.html#install_prerequisites

[quote user="Barsa"]it gives me built error.[/quote]

I've been out of office the past 3 weeks. Could you state if you've resolved this issue in the other cases you've opened since this reply?

Kind regards,
Andras

RE: Interfacing FAT file system into WinbondW25Q02 using SPI-nor driver

Barsa — Wed, 25 Sep 2024 21:45:07 GMT

hinAhaug,

I tried using different USB the problem still persists. I am using JLink Edu V10.10. Since the USB wasn't working, I tried using Bluetooth to read my stored data, but I realized that we use

CONFIG_DISK_DRIVER_FLASH=y to mount our storage and when I try to add CONFIG_BT=y in my prj.config, it gives me built error. I guess those two config doesn't go along with each other.

so I am kind off stuck here. I can't use USB, neither bluetooth.

your help would be highly appreciated.

RE: Interfacing FAT file system into WinbondW25Q02 using SPI-nor driver

AHaug — Mon, 16 Sep 2024 06:42:16 GMT

Hi,

[quote user="Barsa"]

About the size of my storage:

size = < 268435456 >;

this is 256Mega Byte (2 giga bit converted into bytes)

[/quote]

Perfect, I agree.

[quote user="Barsa"]. But I have been using the usb mass example which is using mx25r64 storage[/quote]

Ah, that explains why there's a NAND partition listed in the dts. I'll have a closer look into that sample myself.

[quote user="Barsa"]When I increase stack size: I do not get the stack overflow error but i still get this:[/quote]

Great, then we only have to see why it's not recognized. First we need to verify that it's not because of your other hardware or lacking software setup

J-link firmware version or USB cable:
1. Have you checked with different USB cables? Micro usb's are cheap and tend to break making them effectively only usable for charging and not data transfer which may lead to "USB device not recognized".
2. Your J-Link version may be incorrect. Which version of Segger-JLink are you
Do you see the same warning when testing other samples, or is it just the mas storage sample?
This discussion is not directly relevant, but posting it here since it's a good discussion regarding the sample you're using: https://devzone.nordicsemi.com/f/nordic-q-a/98797/mass-example-with-external-flash-not-working-with-config_bootloader_mcuboot-y

Kind regards,
Andreas

RE: Interfacing FAT file system into WinbondW25Q02 using SPI-nor driver

Barsa — Fri, 13 Sep 2024 13:35:24 GMT

Hi AHaug,

This is the storage that I am using:

About the size of my storage:

size = < 268435456 >;

this is 256Mega Byte (2 giga bit converted into bytes)

You mentioned error about flash disk: I know winbond is a NOR flash memory. But I have been using the usb mass example which is using mx25r64 storage: (which is also a serial NOR), so I took the same overlay that has been used on the sample code. Here is the overlay for mass sample:

/*
 * Copyright (c) 2020 Nordic Semiconductor ASA
 *
 * SPDX-License-Identifier: Apache-2.0
 */

/delete-node/ &storage_partition;

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

		storage_partition: partition@0 {
			label = "storage";
			reg = <0x00000000 0x00020000>;
		};
	};
};

/ {
	msc_disk0 {
		compatible = "zephyr,flash-disk";
		partition = <&storage_partition>;
		disk-name = "NAND";
		cache-size = <4096>;
	};
};

So I am a little confused here as they are using NAND as a label in their overlay. do I need to make any changes for serial NOR?

When I increase stack size: I do not get the stack overflow error but i still get this:

RE: Interfacing FAT file system into WinbondW25Q02 using SPI-nor driver

AHaug — Fri, 13 Sep 2024 08:13:32 GMT

[quote user="Barsa"]

However I used this

CONFIG_NFCT_PINS_AS_GPIOS=y

[/quote]

That's also a valid solution! :)

[quote user="Barsa"]Could you help me with this?[/quote]

I'll have a look. Could you verify if this is the device you're trying to set up? https://www.winbond.com/hq/product/code-storage-flash-memory/serial-nor-flash/?__locale=en&partNo=W25Q02NW_DTR

Discussing this out loud with you: The size parameter in your spi instance is given in bytes represented as int and the Winbounds size is 2 Gigabits. Have you validated that you've entered the correct size?

Moving on to fault: I see the error is on "flashdisk": Is this corresponding to the msc_disc0 nand disc-name that you've created in the partition? I'm curious to where the NAND-partition comes in on the SPI-nor type winbound device. Could you expand on this?

[quote user="Barsa"]I am not able to see my storage as a USB device in my PC after i plug it in, I get this error and it reboots[/quote]

You'll get the stack overflow errors whenever your stack sizes are too small (which I assume you also find obvious, but stating it nonetheless), but finding out which stack that's too small might vary from fault to fault. In this case I believe it is your main stack that might bee too small, which you set to 2k in your prj.conf i.e CONFIG_MAIN_STACK_SIZE=2048. Try to set it to 4k or 8k and see if this removes the stack overflow issue,

Kind regards,
Andreas

RE: Interfacing FAT file system into WinbondW25Q02 using SPI-nor driver

Barsa — Fri, 13 Sep 2024 00:55:52 GMT

Hi AHaug,

That was helpful thank you very much. However I used this

CONFIG_NFCT_PINS_AS_GPIOS=y

in my prj config and now I am able to mount file system using same pin configurations since I have already given my PCB for printing using those pins.

Also, although I am able to mount the file system when I use partition size below 30 mB, it mounts but once I try to go beyond that it shows mount error. Could you help me with this?

Here is my overlay

/*
 * Copyright (c) 2020 Nordic Semiconductor ASA
 *
 * SPDX-License-Identifier: Apache-2.0
 */
// / {
// 	aliases {
// 		spi-flash0 = &winbond;
// 	};
// };
/* Disable conflicting buttons and UART */
&button2 {
	status = "disabled";
};

&button3 {
	status = "disabled";
};

&gpio_fwd {
	status = "disabled";
};

&pinctrl {
		spi_master_default: spi_master_default {
				group1 {
						psels = <NRF_PSEL(SPIM_SCK, 0, 2)>,
										<NRF_PSEL(SPIM_MOSI, 0, 9)>,
										<NRF_PSEL(SPIM_MISO, 0, 3)>;
				};
		};

		spi_master_sleep: spi_master_sleep {
				group1 {
						psels = <NRF_PSEL(SPIM_SCK, 0, 2)>,
										<NRF_PSEL(SPIM_MOSI, 0, 9)>,
										<NRF_PSEL(SPIM_MISO, 0, 3)>;
						low-power-enable;
				};
		};
};

&spi4 {
		compatible = "nordic,nrf-spim";
		pinctrl-0 = <&spi_master_default>;
		pinctrl-1 = <&spi_master_sleep>;
		pinctrl-names = "default", "sleep";
		cs-gpios = <&gpio0 11 GPIO_ACTIVE_LOW>;	
		status = "okay";
		winbond:winbondw25q02@0 {
			compatible = "jedec,spi-nor";
			reg = <0>;
	//      irq-gpios = <&gpio0 21 0>;
			spi-max-frequency = <32000000>;
			//label = "WINBOND";
			jedec-id = [ ef 70 22 ];
			size = < 268435456 >;
			has-dpd;
			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
		 	];
			 t-enter-dpd = <10000>;
			 t-exit-dpd = <35000>;
			 
		};
};

/delete-node/ &storage_partition;

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

		storage_partition: partition@0 {
			label = "storage";
			reg = <0x00000000 0x08000000>;  // 128 MB
		};
	};
};

/ {
	msc_disk0 {
		compatible = "zephyr,flash-disk";
		partition = <&storage_partition>;
		disk-name = "NAND";
		cache-size = <4096>;
	};
};

Here is the error I am getting

[00:00:00.273,406] <err> usb_msc: Storage init ERROR !!!! - Aborting USB init
Area 0 at 0x0 on winbondw25q02@0 for 134217728 bytes
[00:00:00.273,498] <inf> flashdisk: Initialize device NAND
[00:00:00.273,529] <inf> flashdisk: offset 0, sector size 512, page size 4096, volume size 134217728
[00:00:00.286,987] <err> flashdisk: Error -22 getting page info at offset 2000000
[00:00:00.286,987] <err> fs: fs mount error (-5)
[00:00:00.287,017] <err> main: Failed to mount filesystem
[00:00:00.287,078] <inf> main: The device is put in USB mass storage mode.

I tried partition size of 128mega byte here.

Also,

I am not able to see my storage as a USB device in my PC after i plug it in, I get this error and it reboots

[00:00:00.256,744] <dbg> spi_nrfx_spim: spi_context_buffers_setup: tx_bufs 0x200053f8 - rx_bufs 0x20005400 - 1
[00:00:00.256,805] <dbg> spi_nrfx_spim: spi_context_update_rx: rx buf/len 0x2000543f/1
--- 2 messages dropped ---
[00:00:00.256,835] <dbg> spi_nrfx_spim: spi_context_update_tx: tx buf/len (nil)/0
[00:00:00.256,835] <dbg> spi_nrfx_spim: spi_context_update_rx: rx buf/len (nil)/0
[00:00:00.256,866] <dbg> spi_nrfx_spim: finish_transaction: Transaction finished with status 0
[00:00:00.256,866] <dbg> spi_nrfx_spim: spi_context_buffers_setup: tx_bufs 0x200053f8 - rx_bufs 0x20005400 - 1
--- 15 messages dropped ---
[00:00:00.274,444] <dbg> spi_nrfx_spim: spi_context_update_rx: rx buf/len 0x20000ca4/512
[00:00:00.274,719] <dbg> spi_nrfx_spim: spi_context_update_tx: tx buf/len (nil)/0
[00:00:00.274,749] <dbg> spi_nrfx_spim: spi_context_update_rx: rx buf/len (nil)/0
[00:00:00.274,780] <dbg> spi_nrfx_spim: finish_transaction: Transaction finished with status 0
Mount /NAND:: 0
[00:00:00.324,951] <dbg> spi_nrfx_spim: spi_context_buffers_setup: tx_bufs 0x20005220 - rx_bufs 0x20005228 - 1
[00:00:00.324,981] <dbg> spi_nrfx_spim: spi_context_buffers_setup: current_tx 0x20005230 (2), current_rx 0x20005230 (2), tx buf/len 0x20005218/4, rx buf/len 0x20005218/4
[00:00:00.325,012] <dbg> spi_nrfx_spim: spi_context_update_tx: tx buf/len 0x20000ca4/512
[00:00:00.325,012] <dbg> spi_nrfx_spim: spi_context_update_rx: rx buf/len 0x20000ca4/512
[00:00:00.325,317] <dbg> spi_nrfx_spim: spi_context_update_tx: tx buf/len (nil)/0
[00:00:00.325,317] <dbg> spi_nrfx_spim: spi_context_update_rx: rx buf/len (nil)/0
[00:00:00.325,347] <dbg> spi_nrfx_spim: finish_transaction: Transaction finished with status 0
/NAND:: bsize = 512 ; frsize = 512 ; blocks = 216 ; bfree = 216
/NAND: opendir: 0
[00:00:00.325,897] <dbg> spi_nrfx_spim: spi_context_buffers_setup: tx_bufs 0x20005138 - rx_bufs 0x20005140 - 1
[00:00:00.325,927] <dbg> spi_nrfx_spim: spi_context_buffers_setup: current_tx 0x20005148 (2), current_rx 0x20005148 (2), tx buf/len 0x20005130/4, rx buf/len 0x20005130/4
[00:00:00.325,958] <dbg> spi_nrfx_spim: spi_context_update_tx: tx buf/len 0x20000ca4/512
[00:00:00.325,958] <dbg> spi_nrfx_spim: spi_context_update_rx: rx buf/len 0x20000ca4/512
[00:00:00.326,263] <dbg> spi_nrfx_spim: spi_context_update_tx: tx buf/len (nil)/0
[00:00:00.326,263] <dbg> spi_nrfx_spim: spi_context_update_rx: rx buf/len (nil)/0
[00:00:00.326,293] <dbg> spi_nrfx_spim: finish_transaction: Transaction finished with status 0
End of files
[00:00:00.326,416] <inf> main: The device is put in USB mass storage mode.

[00:01:45.822,265] <err> os: ***** USAGE FAULT *****
[00:01:45.822,296] <err> os:   Stack overflow (context area not valid)
[00:01:45.822,326] <err> os: r0/a1:  0x20003e20  r1/a2:  0x00000018  r2/a3:  0x00000000
[00:01:45.822,326] <err> os: r3/a4:  0x20003ddc r12/ip:  0x00000000 r14/lr:  0x00001f09
[00:01:45.822,326] <err> os:  xpsr:  0x61000200
[00:01:45.822,357] <err> os: Faulting instruction address (r15/pc): 0x00000974
[00:01:45.822,387] <err> os: >>> ZEPHYR FATAL ERROR 2: Stack overflow on CPU 0
[00:01:45.822,418] <err> os: Current thread: 0x20000960 (unknown)

RE: Interfacing FAT file system into WinbondW25Q02 using SPI-nor driver

AHaug — Tue, 10 Sep 2024 11:54:49 GMT

Hi Barsha,

The suggestion still stands. The 5340SoC uses P0.02 and P0.03 for the NFC pins.

Let me know if you see the same thing when changing the GPIO's and we'll continue from there :)

Kind regards,
Andreas

RE: Interfacing FAT file system into WinbondW25Q02 using SPI-nor driver

Barsa — Tue, 10 Sep 2024 11:49:14 GMT

Hi,

Actually I am using Fanstel BT 40F which has nrf 5340 soc. I have tested that those two pins works fine as a GPIO. Like I mentioned above, I have done basic reading, writing and erasing using spi communication with this storage on those pins. It is the file system inplementation that I am not able to do.

Regards,

Barsha

RE: Interfacing FAT file system into WinbondW25Q02 using SPI-nor driver

AHaug — Tue, 10 Sep 2024 11:37:25 GMT

Hi,

The pins you've selected (P0.02 and P0.03) are among the few GPIOs are reserved for NFC. If you consult with the pin assignment in the product specification you can see which pins you can use for general purpose input that you can select yourself and which are reserved for others: https://docs.nordicsemi.com/bundle/ps_nrf5340/page/chapters/pin.html

Try with for instance P0.07 and P0.08 instead (or any other available that you want to use)

Kind regards,
Andreas