Attachments (1) Download All
Nordic Case Info
  • Case ID: 336138
Options

Failed to set MCUboot secondary to external flash. E: Failed to open flash area ID 2 (image 0 slot 1): -2, cannot continue

mmade

I have problem placing MCUboot secondary to external flash. I have been testing using nRF9160DK. Project compiles fine but device doesn't boot after flashing the firmware.

Here is the log from serial output of the board. I get error message E: Failed to open flash area ID 2 (image 0 slot 1): -2, cannot continue at the end.

Here is simple project which I have been trying to use.

app_eft.zip

Parents
  • 0

    Hello,

    I checked the ZIP file you shared, but I don't see a partition manager file defining the secondary slot in the external flash. Before integrating the external flash with MCUboot, please test whether you can write to and read from the external flash using a basic SPI/QSPI test sample provided by Zephyr (see the sample). I recommend referring to the MCUboot external flash test sample included in the SDK.

    Kind regards,
    Abhijith

  • 0 in reply to Menon

    Hello,

    I tried those samples and I managed to communicate with external flash using the samples. However that didn't help to solve my original problem.

    Here is the pm_static.yml file which is generated in build folder (copied partitions.yml from build folder and renamed to pm_static.yml). It shows that partition manager has allocated mcuboot_secondary to external flash.

Reply
  • 0 in reply to Menon

    Hello,

    I tried those samples and I managed to communicate with external flash using the samples. However that didn't help to solve my original problem.

    Here is the pm_static.yml file which is generated in build folder (copied partitions.yml from build folder and renamed to pm_static.yml). It shows that partition manager has allocated mcuboot_secondary to external flash.

Children
No Data
Terms of service