MCUBoot RAM Loading with Embedded Artists IMXRT1062 OEM board

[EmanueleMarr]

Hi, I'm using NXP iMXRT1062 processor onEmbedded Artists OEM board rev. C1 and I'm using SDK v2.15.000.

I'm working with "eaimxrt1062_mcuboot_opensource" and "eaimxrt1062_ota_mcuboot_server_enet" examples to use the MCUBoot functionality.

I'm able to work in XIP mode as standard configuration from the SDK examples (the example are configured for XIP code execution from External flash via the FlexSPI bus).

I need to change the execution mode to full RAM execution avoiding the XIP.

I'm able to RUN the eaimxrt1062_mcuboot_opensource in ram booting from falsh at startup and executing the code in SDRAM. But I don't know how to modify the app side ("eaimxrt1062_ota_mcuboot_server_enet") and how to customize the MCUBoot side to perform the execution of OTA app from SDRAM too.

How I have to customize the linlker script for "eaimxrt1062_ota_mcuboot_server_enet" in order to obtain to be loaded in SDRAM by the MCUBoot? Please note that the OTA app should be stored in the external flash at 0x60040000 address.

My goal is obtain this:

• MCUBoot:
  • this should be programmed in External flash at 0x60000000 and executed in SDRAM (it still work)
  • the MCUBoot should jump at image stored at at 0x60040000; the image should be executed  in SDRAM

• OTA App:
  • this should be programmed in External flash at 0x60040000 and then should be executed in SDRAM 

Please note The OTA App will JUMP to a third application that will be executed in XIP mode and will be stored in external flash memory at 0x60200000.

My intention to execute the MCUBoot and the OTA app in SDRAM comes from my need to use the QUAD SPI flex SPI bus at a low clock rate to interface another external flash memory.  So I can't use standard XIP code execution because I noticed that XIP flex SPI bus clock rate should be not changed at runtime or the changes will no have effect, is it right?

I'm a bit confused due the lack of documentation for the MCUBoot applications.

Can anybody help me?

Thanks in advance,

Best Regards,

Emanuele

[stephanie_m]

Hello, 

Would you help us validate if you are seeing the same issue while using the latest version of the SDK available for the RT1062? 

Regards

[EmanueleMarr]

Dear stephanie_m,

Thank You for the reply.

My request ccame from a lack of information/documentation on how to manage the MCUBoot with both MCUBoot and OTA application running completely in SDRAM (not XIP). 

I don't know how and where to modify the "eaimxrt1062_mcuboot_opensource" and "eaimxrt1062_ota_mcuboot_server_enet" examples to obtain what I'm looking for to do.

Can you give me any guidelines or advice on how to proceed?

Please note I'm using the last updated version SDK available for the Embedded Artits iMX RT1062 OEM Board (see the attached image taken from the Embedded Artists website, at http://imx.embeddedartists.com/#imxrt1062). 

Are there newer SDK versions from NXP for imXRT1062? If yes I'm not sure they're re fully suitable for my board using Embedded Artits iMX RT1062 OEM Board.

Thanks in Advance,

Best Regards,

Emanuele

[Habib_MS]

Hello @EmanueleMarr,

I understand that your application will follow this flow, please correct me if I’m wrong:

    1. MCUboot_opensource will be loaded into SDRAM from FLASH. From there, it will receive a new application image, store it in FLASH, and also load it into SDRAM to execute it from SDRAM.
    2. Once the application image is running from SDRAM, that image will then jump to a second application located in FLASH and execute it using XIP.

If this understanding is correct, could you clarify the following points?

    1. Will MCUboot_opensource be responsible for receiving the second application image through some update           method, or is this second image assumed to always be present in FLASH?
    2. Will you boot the second image, or will you simply jump directly to the application?

On the other hand, the latest SDK designed for our EVKs is SDK version 25.12, available through the SDK Builder. You can use the MCUboot opensource examples as a reference. However, if you have specific questions related to Embedded Artists’ SDKs or the functionality of their boards, please contact Embedded Artists support directly.

BR
Habib

[EmanueleMarr]

Dear Habib,

thank you for yor reply.

Let's see here my answer to your questions

    1. Will MCUboot_opensource be responsible for receiving the second application image through some update           method, or is this second image assumed to always be present in FLASH?

The OTA application should manage the update using MCUBoot working mode and should

update the Third application by flash overwriting.

    2. Will you boot the second image, or will you simply jump directly to the application? 

The operation flow is the following:

a. MCUBoot is executed at power up (Boot from Flash, run in SDRAM)

b. MCUboot boots the OTA Application (Load from Flash, run in SDRAM)

c. OTA Application jumps to the third application (Run in flash, XIP mode)

Best Regards

Emanuele

[Habib_MS]

Hello @EmanueleMarr,

You can run MCUboot in SDRAM, but you must keep in mind that loading the OTA application into SDRAM and running MCUboot from it will cause problems, because you would be trying to read and write at the same time.

So, I can recommend two options:

• Run MCUboot somewhere else, either in the MCU's internal RAM or in flash. From there, you can transfer the OTA application to SDRAM. Where you run MCUboot will depend on your application.
• Another option is to use the Merge Tool from the Secure Provisioning Tool so that the ROM boot can move both parts to SDRAM from the start. In other words, you will have a single merged image, and thanks to this, the BootROM will copy both images directly into SDRAM. Also, please keep in mind that you will need to modify the MCUboot application to jump to the OTA application.

Keep in mind the initialization of the memories and ensure that your code does not attempt to configure the same peripheral that is already being used.

Finally, I can recommend this post, where they provide details on how to jump to an application that will perform XIP.”

BR
Habib