CONFIG_APP_MSC_STORAGE_RAM VS FLASH_FATFS

RE: CONFIG_APP_MSC_STORAGE_RAM VS FLASH_FATFS

dejans — Tue, 18 Jul 2023 08:54:30 GMT

Hi,

Here is the pull request for disk access support.

Thank you for your patience.

Best regards,
Dejan

RE: CONFIG_APP_MSC_STORAGE_RAM VS FLASH_FATFS

dejans — Fri, 07 Jul 2023 12:26:54 GMT

Hi,

Due to vacation time and hence reduced staffing, we would need more time to look into your issue. This issue has been reported, but some delay in replying should be expected. I will get back to you when I get new information.

I am sorry for any inconvenience.

Thank you for your patience and understanding.

Best regards,
Dejan

RE: CONFIG_APP_MSC_STORAGE_RAM VS FLASH_FATFS

Sergnrf — Tue, 04 Jul 2023 10:06:12 GMT

devzone.nordicsemi.com/.../chatDK040723.rar
can fill the slot1 once, but writes Confirmed: FALSE, Active: FALSE, Permanent:FALSE

still looks like CONFIG_PM_EXTERNAL_FLASH_MCUBOOT_SECONDARY=y it doesn't work

large files does not react at all does not update in any way.

I apologize for the delay due to work switched to 2.4.0 NCS we hope to replace the FOTA to Mesh DFU

RE: CONFIG_APP_MSC_STORAGE_RAM VS FLASH_FATFS

Sergnrf — Tue, 04 Jul 2023 09:23:33 GMT

RE: CONFIG_APP_MSC_STORAGE_RAM VS FLASH_FATFS

dejans — Tue, 04 Jul 2023 08:56:00 GMT

Hi,

[quote user="dejans"]Could you please describe how you perform FOTA and provide all steps to reproduce your issue?[/quote]

We might need all necessary steps for reproducing your problem.

[quote user="Sergnrf"]the update most often does not start and freezes, or ends with the message connection time out.[/quote]

What happens when update freezes? Does it make any progress and then freezes?
Could you please show message connection time out?

Best regards,
Dejan

RE: CONFIG_APP_MSC_STORAGE_RAM VS FLASH_FATFS

Sergnrf — Mon, 03 Jul 2023 11:16:08 GMT

Hi,

There were no differences from the previous one, I added your recommendations, the mass storage worked, I don’t get rtt errors, the update most often does not start and freezes, or ends with the message connection time out.

Best regards,

Serhii

RE: CONFIG_APP_MSC_STORAGE_RAM VS FLASH_FATFS

dejans — Fri, 30 Jun 2023 15:48:41 GMT

Hi,

Could you please describe how you perform FOTA and provide all steps to reproduce your issue?

Could you provide your new project if there are differences with previously uploaded one?

Could you also provide log which would show us the error that you get when performing FOTA?

Due to vacations and potential limited staff availability, I cannot provide the expectation for problem resolution. However, I will look into your problem together with our developers and I will keep you updated with relevant new information. I have already reached out to our developers internally.

Thank you for your patience and understanding.

Best regards,
Dejan

RE: CONFIG_APP_MSC_STORAGE_RAM VS FLASH_FATFS

Sergnrf — Thu, 29 Jun 2023 13:54:58 GMT

Hi,
#CONFIG_BOOTLOADER_MCUBOOT=y
mass storage works, but FOTA update stopped working.
When can we expect a complete solution to the problem?

Best regards,
Serhii

RE: CONFIG_APP_MSC_STORAGE_RAM VS FLASH_FATFS

dejans — Tue, 27 Jun 2023 08:32:22 GMT

Hi,

I have replicated your issue using NCS v2.3.0. There are currently 2 options how you can fix the build error.

First option:

//in prj.conf, comment out configuration option CONFIG_BOOTLOADER_MCUBOOT
#CONFIG_BOOTLOADER_MCUBOOT=y

Second option:

//in prj.conf, make a following change to CONFIG_NVS
CONFIG_NVS=y

With either one of above-mentioned changes, you should be able to build your project successfully.

Best regards,
Dejan

RE: CONFIG_APP_MSC_STORAGE_RAM VS FLASH_FATFS

Sergnrf — Mon, 26 Jun 2023 10:56:02 GMT

#
# Copyright (c) 2020 Nordic Semiconductor ASA
#
# SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
#
CONFIG_NCS_SAMPLES_DEFAULTS=y

# Deffered logging helps improve LPN power consumption
# when friendship is established.
CONFIG_LOG_MODE_DEFERRED=y

# General configuration
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=2048
CONFIG_FLASH=y
CONFIG_FLASH_MAP=y
#CONFIG_NVS=y
CONFIG_SETTINGS=y
CONFIG_HWINFO=y
CONFIG_DK_LIBRARY=y
#CONFIG_PM_SINGLE_IMAGE=y
#CONFIG_PM_PARTITION_SIZE_SETTINGS_STORAGE=0x8000
#CONFIG_SOC_FLASH_NRF_PARTIAL_ERASE=y

# Bluetooth configuration
CONFIG_BT=y
CONFIG_BT_COMPANY_ID=0x0059
CONFIG_BT_DEVICE_NAME="Mesh Chat"
CONFIG_BT_L2CAP_TX_MTU=69
CONFIG_BT_L2CAP_TX_BUF_COUNT=8
CONFIG_BT_OBSERVER=y
CONFIG_BT_PERIPHERAL=y
#CONFIG_BT_SETTINGS=y
CONFIG_BT_RX_STACK_SIZE=2000

# Disable unused Bluetooth features
CONFIG_BT_CTLR_DUP_FILTER_LEN=0
CONFIG_BT_CTLR_LE_ENC=n
CONFIG_BT_DATA_LEN_UPDATE=n
CONFIG_BT_PHY_UPDATE=n
CONFIG_BT_CTLR_CHAN_SEL_2=n
CONFIG_BT_CTLR_MIN_USED_CHAN=n
CONFIG_BT_CTLR_PRIVACY=n

# Bluetooth Mesh configuration
CONFIG_BT_MESH=y
CONFIG_BT_MESH_RELAY=y
CONFIG_BT_MESH_FRIEND=y
CONFIG_BT_MESH_ADV_BUF_COUNT=13
CONFIG_BT_MESH_RX_SEG_MAX=10
CONFIG_BT_MESH_TX_SEG_MAX=10
CONFIG_BT_MESH_PB_GATT=y
CONFIG_BT_MESH_GATT_PROXY=y
CONFIG_BT_MESH_DK_PROV=y

# Enable Bluetooth mesh models debug logs
CONFIG_BT_DEBUG_LOG=y
CONFIG_BT_MESH_LOG_LEVEL_DBG=y

# Enable Shell module and use UART as a backend
CONFIG_SHELL=y
CONFIG_SHELL_BACKEND_SERIAL=y

CONFIG_USE_SEGGER_RTT=y

CONFIG_STDOUT_CONSOLE=y

#USB related configs
CONFIG_USB_DEVICE_STACK=y
CONFIG_USB_DEVICE_PRODUCT="Zephyr MSC sample"
CONFIG_USB_DEVICE_PID=0x0008
CONFIG_LOG=y
CONFIG_USB_DRIVER_LOG_LEVEL_ERR=y
CONFIG_USB_MASS_STORAGE=y
CONFIG_USB_DEVICE_LOG_LEVEL_ERR=y
CONFIG_USB_MASS_STORAGE_LOG_LEVEL_ERR=y
CONFIG_USB_DEVICE_INITIALIZE_AT_BOOT=n

CONFIG_MAIN_STACK_SIZE=1536
CONFIG_APP_MSC_STORAGE_FLASH_FATFS=y
#CONFIG_APP_MSC_STORAGE_RAM=y

# FOTA FOTA FOTA
CONFIG_IMG_MANAGER=y
CONFIG_MCUBOOT_IMG_MANAGER=y
# Enable point to point DFU over SMP
CONFIG_BOOTLOADER_MCUBOOT=y
CONFIG_MCUMGR=y
CONFIG_MCUMGR_CMD_OS_MGMT=y
CONFIG_MCUMGR_CMD_IMG_MGMT=y
# Enable the Bluetooth (unauthenticated) and shell mcumgr transports.
CONFIG_MCUMGR_SMP_BT=y
CONFIG_MCUMGR_SMP_BT_AUTHEN=n

CONFIG_BT_L2CAP_TX_MTU=252
#CONFIG_BT_L2CAP_RX_MTU=252
#CONFIG_BT_RX_BUF_LEN=260
CONFIG_BT_BUF_ACL_RX_SIZE=256
CONFIG_BT_DATA_LEN_UPDATE=y
CONFIG_BT_AUTO_DATA_LEN_UPDATE=y

# Some command handlers require a large stack.
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=4096

# Enable Extended Advertiser to advertise BT SMP service
CONFIG_BT_EXT_ADV=y
CONFIG_BT_EXT_ADV_MAX_ADV_SET=4

# One extra connection for mesh GATT/proxy and one for SMP BT.
CONFIG_BT_MAX_CONN=3

# One extra identity for SMP service
CONFIG_BT_ID_MAX=2
# end FOTA FOTA FOTA end

# FOTA External flash
CONFIG_PM_EXTERNAL_FLASH_MCUBOOT_SECONDARY=y

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

RE: CONFIG_APP_MSC_STORAGE_RAM VS FLASH_FATFS

dejans — Mon, 26 Jun 2023 10:44:11 GMT

Hi,

Could you share your changed prj.conf file?

Best regards,
Dejan

RE: CONFIG_APP_MSC_STORAGE_RAM VS FLASH_FATFS

Sergnrf — Mon, 26 Jun 2023 09:25:26 GMT

fixed it but the error is still the same

RE: CONFIG_APP_MSC_STORAGE_RAM VS FLASH_FATFS

dejans — Mon, 26 Jun 2023 09:20:55 GMT

Hi,

I have tested your sample and found 2 pairs of conflicting lines in your prj.conf.

CONFIG_NVS=y
and
CONFIG_NVS=n
as well as 
CONFIG_PM_SINGLE_IMAGE=y
and
CONFIG_PM_SINGLE_IMAGE=n

You should have assigned the value for each configuration option once.

CONFIG_NVS=n
CONFIG_PM_SINGLE_IMAGE=n

Best regards,
Dejan

RE: CONFIG_APP_MSC_STORAGE_RAM VS FLASH_FATFS

Sergnrf — Thu, 22 Jun 2023 20:07:30 GMT

Hi,
sure
devzone.nordicsemi.com/.../chatDK.zip

Best regards,
Serhii

RE: CONFIG_APP_MSC_STORAGE_RAM VS FLASH_FATFS

dejans — Thu, 22 Jun 2023 08:17:36 GMT

Hi,

There might be a problem with coexistence of storage partition with external flash partition. It would be useful if I could reproduce this issue. Could you make a minimal sample which I could use for this purpose?

Best regards,
Dejan

RE: CONFIG_APP_MSC_STORAGE_RAM VS FLASH_FATFS

Sergnrf — Fri, 16 Jun 2023 16:40:27 GMT

In version with FOTA and CONFIG_PM_EXTERNAL_FLASH_MCUBOOT_SECONDARY=y

when I add to prj.conf your changes

when I set CONFIG_NVS=n I have error

C:\ncs\v2.3.0\nrf\include\flash_map_pm.h:41:22: error: 'PM_storage_partition_ID' undeclared (first use in this function)
   41 | #define PM_ID(label) PM_##label##_ID
      |                      ^~~
C:\ncs\v2.3.0\nrf\include\flash_map_pm.h:46:35: note: in expansion of macro 'PM_ID'
   46 | #define FIXED_PARTITION_ID(label) PM_ID(label)
      |                                   ^~~~~
c:\da\ncs\chat\src\mass.c:23:41: note: in expansion of macro 'FIXED_PARTITION_ID'
   23 | #define STORAGE_PARTITION_ID            FIXED_PARTITION_ID(STORAGE_PARTITION)
      |                                         ^~~~~~~~~~~~~~~~~~
c:\da\ncs\chat\src\mass.c:34:36: note: in expansion of macro 'STORAGE_PARTITION_ID'
   34 |         mnt->storage_dev = (void *)STORAGE_PARTITION_ID;
      |                                    ^~~~~~~~~~~~~~~~~~~~
C:\ncs\v2.3.0\nrf\include\flash_map_pm.h:41:22: note: each undeclared identifier is reported only once for each function it appears in
   41 | #define PM_ID(label) PM_##label##_ID
      |                      ^~~
C:\ncs\v2.3.0\nrf\include\flash_map_pm.h:46:35: note: in expansion of macro 'PM_ID'
   46 | #define FIXED_PARTITION_ID(label) PM_ID(label)
      |                                   ^~~~~
c:\da\ncs\chat\src\mass.c:23:41: note: in expansion of macro 'FIXED_PARTITION_ID'
   23 | #define STORAGE_PARTITION_ID            FIXED_PARTITION_ID(STORAGE_PARTITION)
      |                                         ^~~~~~~~~~~~~~~~~~
c:\da\ncs\chat\src\mass.c:34:36: note: in expansion of macro 'STORAGE_PARTITION_ID'
   34 |         mnt->storage_dev = (void *)STORAGE_PARTITION_ID;

RE: CONFIG_APP_MSC_STORAGE_RAM VS FLASH_FATFS

Sergnrf — Fri, 16 Jun 2023 15:56:22 GMT

Thank you Dejan, I will be satisfied with this option if I can replace shell_print to some kind of uart_tx?

To give out an msg array to the uart.

RE: CONFIG_APP_MSC_STORAGE_RAM VS FLASH_FATFS

dejans — Fri, 16 Jun 2023 09:45:42 GMT

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

RE: CONFIG_APP_MSC_STORAGE_RAM VS FLASH_FATFS

Sergnrf — Wed, 14 Jun 2023 11:56:12 GMT

Hi,
so far nothing has helped.

Best regards,
Serhii

RE: CONFIG_APP_MSC_STORAGE_RAM VS FLASH_FATFS

dejans — Wed, 14 Jun 2023 08:34:55 GMT

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

RE: CONFIG_APP_MSC_STORAGE_RAM VS FLASH_FATFS

dejans — Tue, 06 Jun 2023 17:26:49 GMT

Hi,

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

Best regards,
Dejan

RE: CONFIG_APP_MSC_STORAGE_RAM VS FLASH_FATFS

dejans — Tue, 06 Jun 2023 17:26:07 GMT

Hi,

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

Best regards,
Dejan

RE: CONFIG_APP_MSC_STORAGE_RAM VS FLASH_FATFS

dejans — Mon, 05 Jun 2023 07:56:57 GMT

Hi,

[quote user="Sergnrf"]I use CHAT + MASS when I add I come to the example that I posted here for you[/quote]

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

RE: CONFIG_APP_MSC_STORAGE_RAM VS FLASH_FATFS

Sergnrf — Fri, 02 Jun 2023 09:30:03 GMT

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

RE: CONFIG_APP_MSC_STORAGE_RAM VS FLASH_FATFS

dejans — Fri, 02 Jun 2023 08:10:21 GMT

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