Trying to do DFU on nRF5340 development kit with external flash MX66L1G

RE: Trying to do DFU on nRF5340 development kit with external flash MX66L1G

Menon — Mon, 12 Aug 2024 13:07:15 GMT

Hello Radhika,

The error message (-19, "No such device") and the log referencing JEDEC ID 0, which suggests that the QSPI device may not be connected or powered correctly. Could you please provide details on how the device is powered and specify the exact pins being used for QSPI? Although the overlay references default and qspi_sleep, it would be helpful to confirm the exact pins in use. Additionally, if you have access to a logic analyzer, probing the SPI pins might offer further insights into the issue.

Kind Regards,

Abhijith

RE: Trying to do DFU on nRF5340 development kit with external flash MX66L1G

Radhika-eaton — Wed, 07 Aug 2024 11:33:11 GMT

Hi Abhijith,

I have checked the physical connections with the help of logic analyzer they are correct as per my understanding. And now I have also verified the sfdp-bfp values. But now before the boot when the kernel does the entry level device initialization it is getting failed for this serial flash.

I am getting an error [00:00:00.253,173] <err> qspi_nor: JEDEC id [00 00 00] expect [c2 20 1b]

These are the logs:

init clock@5000: 0
init gpio@842500: 0
init gpio@842800: 0
init uart@8000: 0
z_device_is_ready: uart@8000
z_device_is_ready: initialized=1, init_res=0
init mbox@2a000: 0
Initializing QSPI NOR flash
dev: 0xa084
Sending RDID command
res: 195887104
Received JEDEC ID: [00 00 00]
[00:00:00.252,929] <err> qspi_nor: JEDEC id [00 00 00] expect [c2 20 1b]
qspi_init: -19
init mx66l1g45g@0: 19
init flash-controller@39000: 0
z_device_is_ready: gpio@842800
z_device_is_ready: initialized=1, init_res=0
init spi@a000: 0
*** Booting nRF Connect SDK 3758bcbfa5cd ***
z_device_is_ready: mx66l1g45g@0
z_device_is_ready: initialized=1, init_res=19
mx66l1g45g@0: device not ready.

Thanks
Radhika

RE: Trying to do DFU on nRF5340 development kit with external flash MX66L1G

Radhika-eaton — Mon, 05 Aug 2024 16:19:46 GMT

Hi Abhijith,

I will check the physical connections with the help of logic analyzer. The JEDEC ID in the overlay file are correct confirmed from the datasheet.

I am unable to cross-check the sfdp-bfp values inside the overlay file from the datasheet, can you please guide me in this on how to create and identify these values from the flash parameter table.

devzone.nordicsemi.com/.../MX66L1G45G.PDF

Thank you so much.

Regards,
Radhika

RE: Trying to do DFU on nRF5340 development kit with external flash MX66L1G

Menon — Mon, 05 Aug 2024 12:54:44 GMT

Hello Radhi,

Thank you confirming the details.

[quote user="Radhika-eaton"]Device initialization failed: No such device
MX66L1G: device not ready.[/quote]

Double-check the physical connections to ensure the QSPI lines (CLK, CS, DQ0, DQ1, DQ2, DQ3) are correctly connected between the nRF5340 and the MX66L1G. The JEDEC ID in the overlay file should match the actual JEDEC ID of the MX66L1G flash chip. The JEDEC ID provided is [c2 20 1b]. Ensure that this is correct. You might need to refer to the MX66L1G datasheet to verify the JEDEC ID.

I am not sure, but have you cross-checked the sfdp-bfp values inside the overlay with the data sheet of MX66L1G?

Kind Regards,

Abhijith

RE: Trying to do DFU on nRF5340 development kit with external flash MX66L1G

Radhika-eaton — Mon, 05 Aug 2024 09:48:39 GMT

I am trying to achieve the DFU over serial recovery mode where the secondary slot is in external flash. Though I am ok with either method. Now when I tried the sample example of spi flash on the latest ncs version ncs\v2.3.0\zephyr\samples\drivers\spi_flash it says

*** Booting Zephyr OS build v3.2.99-ncs2 ***
flash_dev->name: MX66L1G
flash_dev->config: 0x73e8
flash_dev->driver_api: 0x7438
flash_dev->status: 536871396
flash_dev->data: 0x20000090
device_is_ready: MX66L1G
device_is_ready: initialized=1, init_res=19
Device initialization failed: No such device
MX66L1G: device not ready.

nRF Connect is giving me the signed image using key based signing MCUBoot bootloader key file: C:/ncs/v2.3.0/bootloader/mcuboot/root-rsa-2048.pem

Note: MX25R64 external flash is working but the other custom external flash MX66L1G is not working with the same configuration.

Please help me resolve the situation.

devzone.nordicsemi.com/.../spi_5F00_flash.7z

RE: Trying to do DFU on nRF5340 development kit with external flash MX66L1G

Menon — Thu, 01 Aug 2024 17:11:51 GMT

Hello,

Sorry for the late response. It's the summer vacation period here in Norway, and the increased workload has caused the delay

While reviewing the prj.config, I noticed that you have enabled serial recovery in the MCUboot configuration. However, from your thread, it seems you are only looking for serial DFU, correct? Please confirm this. The guide I pointed you to works with the newer version of the nRF Connect SDK, but your version is a bit older, which might cause some configuration differences. If possible, I recommend updating your application to the latest version.

The "bootable status false" message indicates that the device will not boot from this image, and "unavailable hash" suggests that the hash of the image in slot 0 is not available. This could be due to an issue with how the image was created, signed, or uploaded. I suspect this issue might be due to improper signing of the image. Are you properly using the image signing with Imgtool? Please refer to the section on Image Signing for guidance.

Also, check the mcumgr configurations you have enabled in the prj.config. I recommend comparing your application with this sample, as it is more relatable to your SDK version. Additionally, check the repository for some bootloader samples with external flash.

[quote user="Radhika-eaton"]could you please prioritize this ticket? [/quote]

I won’t be able to prioritize the ticket, but I will try to respond as soon as possible.

Kind regards,

Abhijith

RE: Trying to do DFU on nRF5340 development kit with external flash MX66L1G

Radhika-eaton — Wed, 31 Jul 2024 11:19:19 GMT

Hi, could you please prioritize this ticket? It’s crucial for my project. If you have any questions, don’t hesitate to ask.

RE: Trying to do DFU on nRF5340 development kit with external flash MX66L1G

Radhika-eaton — Thu, 25 Jul 2024 10:59:20 GMT

Hi,

I am configuring the image version with a config in the prj.conf

CONFIG_MCUBOOT_EXTRA_IMGTOOL_ARGS="--version=1.0.0"

It seems like there is an issue with the mcumgr commands compatibility with ncs 2.3.0, because now if I am trying to upload the secondary image in the external flash, image upload is not taking place.

PS C:\ncs\v2.3.0\nrf\tests\modules\mcuboot\external_flash> mcumgr image list --conntype serial --connstring "COM13,baud=115200"
Images:
 image=0 slot=0
    version: 2.0.0
    bootable: true
    flags: active confirmed
    hash: 2dfa0f4e6324f9dc8682cc81fc97bf013ca5396574c26e1669350daad8543ca6
Split status: N/A (0)
PS C:\ncs\v2.3.0\nrf\tests\modules\mcuboot\external_flash> mcumgr -c testDK image upload build_2/zephyr/app_update.bin
 0 B / 63.76 KiB [------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------]   0.00%

I also verified the working of external flash with the nrf sample sdk-nrf/tests/modules/mcuboot/external_flash at main · nrfconnect/sdk-nrf (github.com)

The results were successful

*** Booting Zephyr OS build fcaa60a99fa9 ***
Running TESTSUITE test_mcuboot_external_flash
===================================================================
START - test_external_flash
 PASS - test_external_flash in 0.001 seconds
===================================================================
TESTSUITE test_mcuboot_external_flash succeeded
===================================================================
PROJECT EXECUTION SUCCESSFUL

RE: Trying to do DFU on nRF5340 development kit with external flash MX66L1G

Menon — Wed, 24 Jul 2024 14:46:04 GMT

Hello,

It seems there might be an issue with image versioning. Could you please let me know how you are configuring the image version in both the application and the bootloader?

Kind regards,

Abhijith

RE: Trying to do DFU on nRF5340 development kit with external flash MX66L1G

Radhika-eaton — Wed, 24 Jul 2024 10:25:43 GMT

I am struggling with mcumgr now, why is there an issue with mcumgr and how can we resolve it?

PS C:\ncs\v2.3.0\zephyr\samples\subsys\mgmt\mcumgr\smp_svr> mcumgr -c testDK image list
Images:
 image=0 slot=0
    version: 2.0.0.0
    bootable: false
    flags:
    hash: Unavailable
Split status: N/A (0)
PS C:\ncs\v2.3.0\zephyr\samples\subsys\mgmt\mcumgr\smp_svr> mcumgr -c testDK image upload build/zephyr/app_update.bin  
 72.02 KiB / 72.02 KiB [===================================================================================================================================================================================================] 100.00% 1.92 KiB/s 37s
Done
PS C:\ncs\v2.3.0\zephyr\samples\subsys\mgmt\mcumgr\smp_svr> mcumgr -c testDK image list
Images:
 image=0 slot=0
    version: 1.0.0.0
    bootable: false
    flags: 
    hash: Unavailable
Split status: N/A (0)
PS C:\ncs\v2.3.0\zephyr\samples\subsys\mgmt\mcumgr\smp_svr>

RE: Trying to do DFU on nRF5340 development kit with external flash MX66L1G

Radhika-eaton — Wed, 24 Jul 2024 10:20:47 GMT

Yes, I have added the board.overlay in app and mcuboot.

&qspi {
   status = "okay";
   pinctrl-0 = <&qspi_default>;
   pinctrl-1 = <&qspi_sleep>;
   pinctrl-names = "default", "sleep";
   mx66l1g: mx66l1g45g@0 {
      compatible = "nordic,qspi-nor";
      reg = <0>;
      /* MX66L1G supports only pp and pp4io */
      writeoc = "pp4io";
      /* MX66L1G supports all readoc options */
      readoc = "read4io";
      sck-frequency = <8000000>;
      label = "MX66L1G";
      jedec-id = [c2 20 1b];
      sfdp-bfp = [
            e5 20 fb ff  ff ff ff 3f  44 eb 08 6b  08 3b 04 bb
            fe ff ff ff  ff ff 00 ff  ff ff 44 eb  0c 20 0f 52
            10 d8 00 ff  d6 49 c5 00  82 df 04 e3  44 03 67 38
            30 b0 30 b0  f7 bd d5 5c  4a 9e 29 ff  f0 50 f9 85
		];
      size = <1073741824>;
      status = "okay";
   };
   mx25r6435f@0 {
      status = "disabled";
   };
};

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

I tried the sample which you have mentioned, with that I am facing mcumgr issues. Like, if I run this command "mcumgr -c testDK image list" I am seeing these prints

mages:
 image=0 slot=0
    version: 2.0.0.0
    bootable: false
    flags:
    hash: Unavailable
Split status: N/A (0)

There is no display for flags: and hash: is unavailable. After this if I still go with image upload then the second image is written on the primary slot.

mcuboot.conf

#
# Copyright (c) 2022 Nordic Semiconductor
#
# SPDX-License-Identifier: Apache-2.0
#

# STEP 2.3 - Enable logging for MCUboot
CONFIG_LOG=y
CONFIG_MCUBOOT_LOG_LEVEL_INF=y

#STEP 3.1 - Enable Serial Recovery over UART
CONFIG_MCUBOOT_SERIAL=y
CONFIG_BOOT_SERIAL_UART=y

# STEP 3.2 - Disable console UART, since Serial Recovery uses UART
CONFIG_UART_CONSOLE=n

# STEP 3.3 - Configure boolader to use only one slot. 
# STEP 5.1 - Go back to two slots, as we need two for DFU from the app
CONFIG_SINGLE_APPLICATION_SLOT=n

# STEP 3.4 - Turn on a LED so we can see when Serial Recovery mode is active
CONFIG_MCUBOOT_INDICATION_LED=y

#Boot image sectors warning
CONFIG_BOOT_MAX_IMG_SECTORS=512

#Place mcuboot secondary in external flash
#CONFIG_PM_EXTERNAL_FLASH_MCUBOOT_SECONDARY=y

RE: Trying to do DFU on nRF5340 development kit with external flash MX66L1G

Menon — Tue, 23 Jul 2024 12:22:00 GMT

Hello Radhika,

Have you set the external flash in both `app.overlay` and `mcuboot.overlay` as mentioned here? See this sample for reference. Could you share the entire log and overlay files? Please use the insert tab to share the log and files, as it is a bit hard to go through the screenshots.

Kind regards,

Abhijith