This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM5718: Error while booting using verified u-boot in AM5718 processor

Part Number: AM5718

Hi,

We are working on a custom board based on AM5718 processor using ti-processor-sdk-linux-am57xx-evm-05.03.00.07.   For the verification of  kernel and other images while booting  we are trying to implement verified u-boot feaure in our board.  kernel.itb image  was built  from  kernel.its source file(having kernel and DTB images ) using mkimage tool. Then the kernel.itb image was loaded through tftp and tried booting the board. However the booting halted showing the below error:

ERROR: new format image overwritten - must RESET the board to recover
resetting ...

Please see the full log below:

=> setenv serverip 10.176.17.30
=> dhcp
link up on port 0, speed 100, full duplex
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
DHCP client bound to address 10.176.17.224 (1652 ms)
Using ethernet@48484000 device
TFTP from server 10.176.17.30; our IP address is 10.176.17.224
Filename 'zImage'.
Load address: 0x82000000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
###############
1.6 MiB/s
done
Bytes transferred = 4022784 (3d6200 hex)
=> tftp 0x82000000 kernel.itb
link up on port 0, speed 100, full duplex
Using ethernet@48484000 device
TFTP from server 10.176.17.30; our IP address is 10.176.17.224
Filename 'kernel.itb'.
Load address: 0x82000000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
###################################
1.6 MiB/s
done
Bytes transferred = 8146232 (7c4d38 hex)
=> bootm 0x82000000#config@1
## Loading kernel from FIT Image at 82000000 ...
Using 'config@1' configuration
Trying 'kernel@1' kernel subimage
Description: My default kernel
Type: Kernel Image
Compression: uncompressed
Data Start: 0x820000c4
Data Size: 4022784 Bytes = 3.8 MiB
Architecture: ARM
OS: Linux
Load Address: 0x82000000
Entry Point: 0x82000000
Hash algo: md5
Hash value: 55981089d3e5663647198dc418960f9a
Verifying Hash Integrity ... md5+ OK
## Loading fdt from FIT Image at 82000000 ...
Using 'config@1' configuration
Trying 'fdt@1' fdt subimage
Description: FDT for my cool board
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x827ac688
Data Size: 98603 Bytes = 96.3 KiB
Architecture: ARM
Hash algo: crc32
Hash value: c24dd685
Verifying Hash Integrity ... crc32+ OK
Booting using the fdt blob at 0x827ac688
Loading Kernel Image ... OK
ERROR: new format image overwritten - must RESET the board to recover
resetting ...

U-Boot SPL 2018.01-00569-gfd38f5afef-dirty (Apr 07 2021 - 10:37:59)
DRA722-GP ES2.0
Trying to boot from SPI
no pinctrl state for default mode
no pinctrl state for default mode


Is there any other configurations to be done in u-boot before booting using kernel.itb image.?

Kindly help us in booting  the board using verified u-boot feature.

Regards,

Sharanya

  • Hi Sharanya,

    We do not have support for verified boot & i believe you have added that. Can you confirm if the default zImage & dtb load/boot
    works fine?

    Looking at your logs:


     bootm 0x82000000#config@1
    ## Loading kernel from FIT Image at 82000000 ...
    Using 'config@1' configuration
    Trying 'kernel@1' kernel subimage
    Description: My default kernel
    Type: Kernel Image
    Compression: uncompressed
    Data Start: 0x820000c4
    Data Size: 4022784 Bytes = 3.8 MiB
    Architecture: ARM
    OS: Linux
    Load Address: 0x82000000
    Entry Point: 0x82000000
    Hash algo: md5
    Hash value: 55981089d3e5663647198dc418960f9a
    Verifying Hash Integrity ... md5+ OK
    ## Loading fdt from FIT Image at 82000000 ...
    Using 'config@1' configuration
    Trying 'fdt@1' fdt subimage
    Description: FDT for my cool board
    Type: Flat Device Tree
    Compression: uncompressed 

    FDT is overwriting kernel image at 82000000 & hence you are unable to boot.

    Can you confirm if the non-verified default boot with zImage & DTB works well?

    We have never supported verified boot on AM57 so i can only comment from the logs you have provided.
    When  you create the FIT image kernel.itb can you put fdt at a different address other than 82000000? If that
    can be pushed to different address we can prevent overwriting of kernel by dtb.

    - Keerthy