[NXP][MIMXRT1189] MCUBoot RAM Load for CM33 app [Hyperram/DTCM]

[javad123javad]

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.

*** 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 0x38000000 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 iteration failed -1 D: boot_scramble_region: 0x14014b34 0 8388608 0 D: boot_erase_region: flash_area 0x14014b34, offset 0, size 8388608, 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 

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:

CONFIG_BOOT_IMAGE_EXECUTABLE_RAM_START=0x38000000 CONFIG_BOOT_IMAGE_EXECUTABLE_RAM_SIZE=131072 # CONFIG_BOOT_VALIDATE_SLOT0=n # CONFIG_BOOT_MAX_IMG_SECTORS=512 # CONFIG_BOOT_MAX_IMG_SECTORS_AUTO=n CONFIG_MCUBOOT_LOG_LEVEL_DBG=y CONFIG_LOG=y CONFIG_BOOT_BANNER=y # Enable signature verification CONFIG_BOOT_SIGNATURE_TYPE_RSA=y CONFIG_BOOT_SIGNATURE_KEY_FILE="root-rsa-2048.pem" 

sysbuild/mcuboot.overlay:

/ { chosen { zephyr,sram = &dtcm; zephyr,code-partition = &boot_partition; }; }; 

blinky/prj.conf:

CONFIG_FLASH_BASE_ADDRESS=0x14020000 # Enable Zephyr application to be booted by MCUboot CONFIG_BOOTLOADER_MCUBOOT=y # Use the default MCUBoot PEM key file (BOOT_SIGNATURE_KEY_FILE) CONFIG_MCUBOOT_SIGNATURE_KEY_FILE="bootloader/mcuboot/root-rsa-2048.pem" 

board overlay:

/ { chosen { zephyr,flash = &hyperram1; zephyr,sram = &hyperram0; }; // HyperRAM connected to FlexSPI1 hyperram0: memory@38800000 { /* Infineon S80KS2562 256 Mb */ device_type = "memory"; reg = <0x38800000 DT_SIZE_M(16)>; zephyr,memory-attr = <DT_MEM_ARM(ATTR_MPU_RAM)>; }; hyperram1: memory@38000000 { /* Infineon S80KS2562 256 Mb */ device_type = "memory"; reg = <0x38000000 DT_SIZE_M(8)>; zephyr,memory-attr = <DT_MEM_ARM(ATTR_MPU_FLASH)>; }; 

I also found another problem in zephyr.map:
We expect thart __text_region_start be mapped to 0x0000000038000XXX while it is mapped to 0x00000000388007fc which has overlap with zephyr,sram region for .data and .bss

[javad123javad]

Hi @DerekSnell
As a step further, I have modified the cmake/mcuboot.cmake to use zephyr,flash addr for --load-addr register address:

+ 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 itcm (only for test, it should be Hyperram) for zephyr,flash :

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 west debug, it also crashes. But, when I set zephyr,sram=&dtcm, the debugger doesn't crash (but the app still doesn't run via Mcuboot)