[NXP][MIMXRT1189] MCUBoot RAM Load for CM33 app [Hyperram/DTCM] #98573
Replies: 5 comments 1 reply
-
|
Hi @DerekSnell + dt_chosen(chosen_flash PROPERTY "zephyr,flash")
+ dt_reg_addr(chosen_flash_address PATH ${chosen_flash})
- set(imgtool_args --align 1 --load-addr ${chosen_ram_address} ${imgtool_args})
+ set(imgtool_args --align 1 --load-addr ${chosen_flash_address} ${imgtool_args})I have also modified the application to use chosen {
zephyr,flash = &itcm;
zephyr,sram = &hyperram1;
};
// HyperRAM region for CM33 data
hyperram1: memory@38100000 {
/* Infineon S80KS2562 256 Mb */
device_type = "memory";
reg = <0x38100000 DT_SIZE_M(1)>;
zephyr,memory-attr = <DT_MEM_ARM(ATTR_MPU_RAM)>;
};
In this case, the MCUboot can copy the cm33 image to itcm and jump to it, but the image itself has problem to run: *** Booting MCUboot v2.2.0-141-gd5b0dcb9aaee ***
*** Using Zephyr OS build 16f4d6c23e40 ***
I: Starting bootloader
I: Primary slot: version=0.0.0+0
I: Image 0 Secondary slot: Image not found
I: Image 0 RAM loading to 0x1ffe0000 is succeeded.
D: boot_validate_slot: slot 0, expected_swap_type 0
D: bootutil_img_validate: flash area 0x14014b34
D: bootutil_img_hash
D: bootutil_tlv_iter_begin: type 65535, prot == 0
D: bootutil_img_validate: TLV off 23672, end 24004
D: bootutil_tlv_iter_next: searching for 65535 (65535 is any) starting at 23672 ending at 24004
D: bootutil_tlv_iter_next: TLV 16 found at 23676 (size 32)
D: bootutil_img_validate: EXPECTED_HASH_TLV == 16
D: bootutil_tlv_iter_next: searching for 65535 (65535 is any) starting at 23708 ending at 24004
D: bootutil_tlv_iter_next: TLV 1 found at 23712 (size 32)
D: bootutil_img_validate: EXPECTED_KEY_TLV == 1
D: bootutil_find_key
D: bootutil_tlv_iter_next: searching for 65535 (65535 is any) starting at 23744 ending at 24004
D: bootutil_tlv_iter_next: TLV 32 found at 23748 (size 256)
D: bootutil_img_validate: EXPECTED_SIG_TLV == 32
D: bootutil_verify_sig: RSA key_id 0
D: bootutil_tlv_iter_next: searching for 65535 (65535 is any) starting at 24004 ending at 24004
D: bootutil_tlv_iter_next: TLV 65535 not found
I: Image 0 loaded from the primary slot
D: Left boot_go with success == 1
I: Bootloader chainload address offset: 0x1ffe0000
I: Image version: v0.0.0
I: Jumping to the first image slot
When I debug CM33 app with the |
Beta Was this translation helpful? Give feedback.
-
|
Hi @javad123javad , If you want to use the MCUboot RAM Load feature with |
Beta Was this translation helpful? Give feedback.
-
|
Hi @javad123javad ,
Use these commands to build and flash the EVK board: Some details about this patch and the changes made:
Console output: Let me know how this works for you, or if you have any questions. Best regards |
Beta Was this translation helpful? Give feedback.
-
Hi @DerekSnell, I have performed exactly the same settings for our custom board in which the Hyperram and FLASH are connected in reverse order in comparsion to the 1180-EVK. *** Using Zephyr OS build v4.3.0-rc3-3-gdf8b43d330ed ***
I: Starting bootloader
I: Primary slot: version=0.0.0+0
I: Image 0 Secondary slot: Image not found
I: Image 0 RAM loading to 0x38000000 is succeeded.
D: boot_validate_slot: slot 0, expected_swap_type 0
D: bootutil_img_validate: flash area 0x14014d10
D: bootutil_img_hash
D: bootutil_tlv_iter_begin: type 65535, prot == 0
D: bootutil_img_validate: TLV iteration failed -1
D: boot_scramble_region: 0x14014d10 0 1048576 0
D: boot_erase_region: flash_area 0x14014d10, offset 0, size 1048576, backwards == 0
D: boot_erase_region: device with erase
E: Image in the primary slot is not valid!
I: Removing image 0 from SRAM at address 0x38000000
I: No slot to load for image 0
D: Left boot_go with success == 0
E: Unable to find bootable image
Here is which I did on Zephyr repo (please notice that I used flexspi2 to calculate absolute address): diff --git a/cmake/mcuboot.cmake b/cmake/mcuboot.cmake
index 43d265c419d..9ffb525613b 100644
--- a/cmake/mcuboot.cmake
+++ b/cmake/mcuboot.cmake
@@ -134,10 +134,14 @@ function(zephyr_mcuboot_tasks)
set(imgtool_args --overwrite-only --align 1 ${imgtool_args})
elseif(CONFIG_MCUBOOT_BOOTLOADER_MODE_RAM_LOAD OR CONFIG_MCUBOOT_BOOTLOADER_MODE_RAM_LOAD_WITH_REVERT)
# RAM load requires setting the location of where to load the image to
- dt_chosen(chosen_ram PROPERTY "zephyr,sram")
+ dt_chosen(chosen_ram PROPERTY "zephyr,flash")
dt_reg_addr(chosen_ram_address PATH ${chosen_ram})
dt_nodelabel(slot0_partition NODELABEL "slot0_partition" REQUIRED)
- dt_reg_addr(slot0_partition_address PATH ${slot0_partition})
+ dt_reg_addr(slot0_offset PATH ${slot0_partition})
+ dt_nodelabel(flexspi2 NODELABEL "flexspi2" REQUIRED)
+ dt_reg_addr(flexspi2_base PATH ${flexspi2} INDEX 1)
+ math(EXPR slot0_addr "${flexspi2_base} + ${slot0_offset}")
+
dt_nodelabel(slot1_partition NODELABEL "slot1_partition" REQUIRED)
dt_reg_addr(slot1_partition_address PATH ${slot1_partition})
@@ -148,7 +152,7 @@ function(zephyr_mcuboot_tasks)
set(imgtool_args --align ${write_block_size} --load-addr ${chosen_ram_address} ${imgtool_args})
endif()
set(imgtool_args_alt_slot ${imgtool_args} --hex-addr ${slot1_partition_address})
- set(imgtool_args ${imgtool_args} --hex-addr ${slot0_partition_address})
+ set(imgtool_args ${imgtool_args} --hex-addr ${slot0_addr})
elseif(CONFIG_MCUBOOT_BOOTLOADER_MODE_SINGLE_APP_RAM_LOAD)
dt_chosen(ram_load_dev PROPERTY "mcuboot,ram-load-dev")
if(DEFINED ram_load_dev)
diff --git a/share/sysbuild/image_configurations/MAIN_image_default.cmake b/share/sysbuild/image_configurations/MAIN_image_default.cmake
index 8e569b228e2..b7cc1dc78ed 100644
--- a/share/sysbuild/image_configurations/MAIN_image_default.cmake
+++ b/share/sysbuild/image_configurations/MAIN_image_default.cmake
@@ -37,8 +37,8 @@ if(SB_CONFIG_BOOTLOADER_MCUBOOT)
elseif(SB_CONFIG_MCUBOOT_MODE_RAM_LOAD)
# RAM load mode requires XIP be disabled and flash size be set to 0
set_config_bool(${ZCMAKE_APPLICATION} CONFIG_MCUBOOT_BOOTLOADER_MODE_RAM_LOAD y)
- set_config_bool(${ZCMAKE_APPLICATION} CONFIG_XIP n)
- set_config_int(${ZCMAKE_APPLICATION} CONFIG_FLASH_SIZE 0)
+ #set_config_bool(${ZCMAKE_APPLICATION} CONFIG_XIP n)
+ #set_config_int(${ZCMAKE_APPLICATION} CONFIG_FLASH_SIZE 0)
elseif(SB_CONFIG_MCUBOOT_MODE_RAM_LOAD_WITH_REVERT)
# RAM load mode requires XIP be disabled and flash size be set to 0
set_config_bool(${ZCMAKE_APPLICATION} CONFIG_MCUBOOT_BOOTLOADER_MODE_RAM_LOAD_WITH_REVERT y)
Hyperram is also configured as follows, as we are running both CM33 and CM7 from Hyperram: When I build the application with I have attached the blinky, if you want to check. blinky.tar.gz |
Beta Was this translation helpful? Give feedback.
-
|
Hi @javad123javad , You need to put more effort in troubleshooting your custom board. You can use the debugger with the MCUboot app to confirm if the RAM load is using the correct addresses, the source address in flash and the destination address in HyperRAM. And if so, you can confirm if the image copied to HyperRAM is read correctly, or if the image validation is failing for other reasons. Like in the debugger, after the image is loaded to HyperRAM, dump that image and compare with the expected image in flash. Or step through the MCUboot code to see why the validation fails. You also have the working example on the EVK I shared, so you can compare the RAM load feature between them to see what is different.
Yes, the patch I provided does the same. This is warning comes from the mcuboot.overlay that removes the Let us know what you find |
Beta Was this translation helpful? Give feedback.
-
|
Hi @javad123javad , What are the first two lines in the generated file blinky/zephyr/zephyr.signed.hex ? The file from my example shows that the blinky image will be programmed at 0x38020000, which is the In the generated file blinky/zephyr/zephyr.map , what is the Have you compared your generated blinky/zephyr/.config with the same file from my example, to see how they compare? Or can you share yours? Some Kconfigs to confirm are:
Thanks |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
We are trying to use MCUboot RAM load feature on MIXRT1189 SOC on our custom board to load the application into Hyperram (folowing your article in MCUboot RAM Loading with Zephyr ).
We tried loading the CM33 application into HyperRAM. It appears that the image is successfully copied and the MCUboot header is correctly decoded; however, it fails to parse the TLV tags.
Are there any specific considerations we should take into account for this SoC? On our custom board, the HyperRAM is connected to FlexSPI1 and the Flash is connected to FlexSPI2 (in the reverse configuration compared to the MIMXRT1180_EVK).
The project configuration is as follows:
sysbuild/mcuboot.conf:sysbuild/mcuboot.overlay:blinky/prj.conf:board overlay:
I also found another problem in
zephyr.map:We expect thart
__text_region_startbe mapped to0x0000000038000XXXwhile it is mapped to0x00000000388007fcwhich has overlap withzephyr,sramregion for.dataand.bssBeta Was this translation helpful? Give feedback.
All reactions