CONFIG_APP_MSC_STORAGE_RAM VS FLASH_FATFS

[Sergnrf]

Hi Team,
NCS v2.3.0
nrf52840

my project works as expected with CONFIG_APP_MSC_STORAGE_RAM=y

but I need storage FLASH_FATFS

I set CONFIG_APP_MSC_STORAGE_FLASH_FATFS=y
and the disk does not open in Windows, it gives an error window when connecting nrf USB.

Thank you.

4034.chatDK_update.7z

[dejans]

Hi,

Could you please show the error that you get?

Best regards,
Dejan

[Sergnrf]

windows error looks the same as in devzone.nordicsemi.com/.../nrf52833dk_nrf52833-usb-mass-storage-issue

[dejans]

Hi,

Is your project based on the mass storage sample?

Best regards,
Dejan

[Sergnrf]

Yes, example Mass

[dejans]

Hi,

As you based your project on the mass sample, you could start adding the changes one-by-one to the mass sample in order to find which one of the introduced changes breaks the storage.

Best regards,
Dejan

[Sergnrf]

I use CHAT + MASS when I add I come to the example that I posted here for you

[dejans]

Hi,

Sergnrf said:

I use CHAT + MASS when I add I come to the example that I posted here for you

Thank you for providing this information.

You could start with mass sample and then add the functionalities that you need to it. In this way, you could narrow down the problem to a specific change which introduces the problem.

Best regards,
Dejan

[dejans]

Hi,

CONFIG_APP_MSC_STORAGE_FLASH_FATFS is Kconfig option in the scope of zephyr/samples/subsys/usb/mass sample.

Best regards,
Dejan

[dejans]

Hi,

I have made an internal inquiry. I will get back to you when I get more information.

Best regards,
Dejan

[dejans]

Hi,

The issue might not be with any of the samples (mass and chat) independently, but with the way how they are used together. We have looked into it, and it might potentially be configuration/devicetree/partition problem.

Could you provide information on how this issue is connected with your other issue? 

You could also have a look at this discussion for some further hints.

Did you have any progress related to this issue yourself? Could you provide status update from your side?

Best regards,
Dejan

[Sergnrf]

Hi,
so far nothing has helped.

Best regards,
Serhii

[dejans]

Hi,

This may or may not be related to your issue, but due to some blocking behavior when working with USB, all shell_print statements in model_handler.c should ideally be either removed or replaced by either printk or LOG.

Regarding the persistent USB storage, I have tested successfully with a following configuration changes applied to your project:

prj.conf

CONFIG_NVS=n 							
CONFIG_SETTINGS=n 	
CONFIG_PM_SINGLE_IMAGE=n 					
# CONFIG_PM_PARTITION_SIZE_SETTINGS_STORAGE=0x8000		
CONFIG_SOC_FLASH_NRF_PARTIAL_ERASE=n 				
CONFIG_BT_SETTINGS=n
CONFIG_APP_MSC_STORAGE_FLASH_FATFS=y
#CONFIG_APP_MSC_STORAGE_RAM=y

nrf52840dk_nrf52840.overlay

storage_partition: partition@0 {
			label = "storage";
			#reg = <0x00000000 DT_SIZE_K(8000)>;
			reg = <0x00000000 0x00020000>;
		};

With above-mentioned changes I could see USB disk with persistent storage after the reset.

Best regards,
Dejan