NXP MCU Boot Utility - Error - Cannot recognise/convert the format of image file

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

NXP MCU Boot Utility - Error - Cannot recognise/convert the format of image file

644 Views
timmek
Contributor II

Hello,

I would like to use NXP MCU Boot Utility v5.2.1.

When I pressed 'Generate Unsigned Bootable Image' button error message appears:
'Cannot recognise/convert the format of image file.'
'You should first specify a source image file (.elf, .axf/ .srec/ .hex/ .bin)!'

In log window I can see:
'Generate Bootable Image' button is clicked
Original image file is a bootable image file
Original image file is a bootable image file'

What is wrong with this HEX file? Did you encounter similar issues?

 

Labels (1)
Tags (1)
0 Kudos
Reply
1 Reply

581 Views
diego_charles
NXP TechSupport
NXP TechSupport

Hi @timmek 

I hope that you are doing well!

I checked your attached hex file. I saw that your application starts at 0x6000_0000 and already containts some boot structures. I am not sure if this is the reason why it is not valid. 

diego_charles_0-1706646938691.png

Below my steps to generate a bootable image. 

First, you need to add an offset to your image. Make your image start at other address for example 0x6000_2000. This is because the tool will generate a bootable image that will containt the FDCDC, IVT and boot data. The IVT needs to be placed at 0x6000_1000, for XIP images. 

diego_charles_0-1706650354682.png

Then , you need to set XIP_BOOT_HEADER_ENABLE=0

diego_charles_1-1706650421665.png

Then generate the hex file, this will be raw image, that can not be booted. I am attaching mine as reference. 

After that, use the same offset you added to the image. This will be the image base address. 


As shown below, this raw image can be used by the MCU Boot Utility to generate a bootable image.

diego_charles_2-1706650480010.png

 

Additiionally, the MCU boot utility come with raw image examples with an offset that you can try out. 

diego_charles_1-1706647892146.png

I hope this could help you! 

Diego

 

 

0 Kudos
Reply