code build issue with mcuboot and mass storage

RE: code build issue with mcuboot and mass storage

Marte Myrvold — Mon, 07 Aug 2023 14:15:10 GMT

Hi,

Are you able to figure out which thread it is failing in? You can try to set CONFIG_THREAD_NAME=y in prj.conf to see if you get the name of the thread in the assert, or you can debug the application and enable breakpoints on Zephyr fatal errors to see which thread is running when it asserts.

Best regards,
Marte

RE: code build issue with mcuboot and mass storage

Mithilesh Yadav — Fri, 04 Aug 2023 13:59:02 GMT

Thank you for sharing valuable knowledge.

When I am running combined project then getting following error without manifest:

Despite increasing the stack size, heap size and thread stack size, the error persists.

Please help me.

RE: code build issue with mcuboot and mass storage

Marte Myrvold — Fri, 04 Aug 2023 13:41:37 GMT

Hi,

The advantage of using a manifest repo is that you can easily configure the version of nRF Connect SDK, and other repositories, associated with your driver directly in the west.yml manifest file. So it can be more organized in that regard. It is perfectly fine to not use a manifest repo as well, but then you need to make sure that the installed SDK is the correct version associated with your driver.

Best regards,
Marte

RE: code build issue with mcuboot and mass storage

Mithilesh Yadav — Thu, 03 Aug 2023 13:44:47 GMT

Yes, I ran the west update as well as pull the fresh SDK but got the same error.

I successfully tested a sensor using an out-of-tree driver by following the sample you provided, and its working fine.

Could you please explain the pros and cons of developing an application with oot driver using manifest and without manifest repo?

RE: code build issue with mcuboot and mass storage

Marte Myrvold — Thu, 03 Aug 2023 07:53:39 GMT

Hi,

Did you run west update after updating the revision of the nRF Connect SDK in your repository?

Using the application as the manifest repository is the recommended method for out-of-tree drivers, but it is possible to install nRF Connect SDK with Toolchain Manager and create an oot driver without west manifest.

As an example, I have made an oot driver without west manifest. I copied the BME680 sensor driver and simply renamed it to BME681. To use it in an application, I added it with ZEPHYR_EXTRA_MODULES in the application's CMakeLists.txt, for example:

set(ZEPHYR_EXTRA_MODULES ${CMAKE_CURRENT_SOURCE_DIR}/../out_of_tree_driver_bme681)

This code is not thoroughly tested or qualified and should be considered provided “as-is”. Please test it with your application and let me know if you find any issues.

devzone.nordicsemi.com/.../out_5F00_of_5F00_tree_5F00_driver_5F00_bme681.zip

Best regards,
Marte

RE: code build issue with mcuboot and mass storage

Mithilesh Yadav — Thu, 03 Aug 2023 05:00:00 GMT

Hi,

Code build successfully When I installed the SDK by nRF Connect desktop toolchain manager application.

But I need to develop project for OOT driver.

Is there any way I can develop my project with OOT tree driver using NCS(Installed by toolchain manager).

RE: code build issue with mcuboot and mass storage

Mithilesh Yadav — Wed, 02 Aug 2023 14:59:33 GMT

Yes, sample path is correct. Let me install the NCS by Toolchain manager and check with it.

Actually I need to develop out of tree driver, so I installed the NCS using the below link:

https://github.com/nrfconnect/ncs-example-application

RE: code build issue with mcuboot and mass storage

Marte Myrvold — Wed, 02 Aug 2023 13:48:07 GMT

Hi,

I got some warnings about the external_flash partition, but still not the errors you are seeing. To verify, it is the SMP server sample located in zephyr/samples/subsys/mgmt/mcumgr/smp_svr you are testing? Have you made any other changes to the sample or the SDK itself?

Best regards,
Marte

RE: code build issue with mcuboot and mass storage

Mithilesh Yadav — Wed, 02 Aug 2023 12:44:02 GMT

Hi,

Did you try this with ncs v2.4.0.

I can not upload any project due company policy restriction, smp_svr sample's complete configuration is given below:

prj.conf:

# Enable MCUmgr and dependencies.
CONFIG_NET_BUF=y
CONFIG_ZCBOR=y
CONFIG_CRC=y
CONFIG_MCUMGR=y
CONFIG_STREAM_FLASH=y
CONFIG_FLASH_MAP=y

# Some command handlers require a large stack.
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=2304
CONFIG_MAIN_STACK_SIZE=8192

# Ensure an MCUboot-compatible binary is generated.
CONFIG_BOOTLOADER_MCUBOOT=y

# Enable flash operations.
CONFIG_FLASH=y

# Required by the `taskstat` command.
CONFIG_THREAD_MONITOR=y

# Support for taskstat command
CONFIG_MCUMGR_GRP_OS_TASKSTAT=y

# Enable statistics and statistic names.
CONFIG_STATS=y
CONFIG_STATS_NAMES=y

# Enable most core commands.
CONFIG_FLASH=y
CONFIG_IMG_MANAGER=y
CONFIG_MCUMGR_GRP_IMG=y
CONFIG_MCUMGR_GRP_OS=y
CONFIG_MCUMGR_GRP_STAT=y

# Enable logging
CONFIG_LOG=y
CONFIG_MCUBOOT_UTIL_LOG_LEVEL_WRN=y

# Disable debug logging
CONFIG_LOG_MAX_LEVEL=3

CONFIG_MCUBOOT_IMAGE_VERSION="1.1.1"

#qspi
CONFIG_NORDIC_QSPI_NOR=y
CONFIG_NORDIC_QSPI_NOR_FLASH_LAYOUT_PAGE_SIZE=4096
CONFIG_NORDIC_QSPI_NOR_STACK_WRITE_BUFFER_SIZE=16
CONFIG_PM_EXTERNAL_FLASH_MCUBOOT_SECONDARY=y

#USB related configs
CONFIG_USB_DEVICE_STACK=y
CONFIG_USB_DEVICE_PRODUCT="Zephyr MSC sample"
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_APP_MSC_STORAGE_FLASH_LITTLEFS=y

nrf52840dk_nrf52840.overlay:

/delete-node/ &boot_partition;
/delete-node/ &slot0_partition;
/delete-node/ &slot1_partition;


&flash0 {
	partitions {
		boot_partition: partition@0 {
			label = "mcuboot";
			reg = <0x000000000 0x00010000>;
		};
		slot0_partition: partition@10000 {
			label = "image-0";
			reg = <0x000010000 0x0000e8000>;
		};
	};
};

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

		slot1_partition: partition@0 {
			label = "image-1";
			reg = <0x000000000 0x0000e8000>;
		};
		external_flash: partition@e8000 {
			label = "external flash";
			reg = <0x0000e8000 0x000718000>;
		};
	};
};

/ {
	chosen {
		nordic,pm-ext-flash = &mx25r64;
	};
	msc_disk0 {
		compatible = "zephyr,flash-disk";
		partition = <&external_flash>;
		disk-name = "NAND";
		cache-size = <4096>;
	};
};

child_image/mcuboot/prj.conf:

CONFIG_MAIN_STACK_SIZE=10240

CONFIG_SIZE_OPTIMIZATIONS=y
CONFIG_NORDIC_QSPI_NOR=y
CONFIG_NORDIC_QSPI_NOR_FLASH_LAYOUT_PAGE_SIZE=4096
CONFIG_NORDIC_QSPI_NOR_STACK_WRITE_BUFFER_SIZE=16

# Enable flash operations
CONFIG_FLASH=y

CONFIG_MULTITHREADING=y
CONFIG_BOOT_MAX_IMG_SECTORS=256

CONFIG_MCUBOOT_INDICATION_LED=y

CONFIG_PM_PARTITION_SIZE_MCUBOOT=0x10000

CONFIG_CONSOLE=y
CONFIG_UART_CONSOLE=y

CONFIG_LOG=y
CONFIG_LOG_MODE_IMMEDIATE=y
CONFIG_LOG_BACKEND_UART=y
CONFIG_PM_EXTERNAL_FLASH_MCUBOOT_SECONDARY=y 
CONFIG_MCUBOOT_SERIAL_DIRECT_IMAGE_UPLOAD=y

CONFIG_FW_INFO_FIRMWARE_VERSION=1

child_image/mcuboot/boards/nrf52840dk_nrf52840.overlay:

/ {
	chosen {
		nordic,pm-ext-flash = &mx25r64;
	};
};

RE: code build issue with mcuboot and mass storage

Marte Myrvold — Wed, 02 Aug 2023 12:16:50 GMT

Hi,

I am not able to reproduce the error by adding the configurations you mention in smp_svr sample. Can you upload a project where this can easily be reproduced?

Best regards,
Marte