Hello,
I was wondering to what extent the imx280 ROM bootloader needs the ELF file in a bootstream order to function and is
there any way around it?
We are using HABv4 (imx280) and for a single image it seems to require both the bin file and the elf file in the bd file.
I understand the necessity of the bin file in order to cover padding for the signing, but why is the elf file necessary
if we're specifying the load/call addresses ourselves in the bd file ?
It doesn't seem to work in a cold boot. It only works if we first load a 'proper' image and then load the elf-less bootstream
in USB recovery without removing power. Might be due to residual data in SRAM.
Thanks,
Filip Aben
Solved! Go to Solution.
Dear Filip Aben,
Hi, I believe you are referring to the sample code provided in the MX28 security app note where the BD file shows both BIN and ELF with load commands. If we are loading BIN then there should be no reason to load ELF. It was an oversight on my part when I was working on the app note. I went back, removed the load ELF part from the BD file and regenerated the u-boot.sb file and see no issue booting u-boot on i.MX28 EVK board.
Thanks
Fareed
Dear Filip Aben,
Hi, I believe you are referring to the sample code provided in the MX28 security app note where the BD file shows both BIN and ELF with load commands. If we are loading BIN then there should be no reason to load ELF. It was an oversight on my part when I was working on the app note. I went back, removed the load ELF part from the BD file and regenerated the u-boot.sb file and see no issue booting u-boot on i.MX28 EVK board.
Thanks
Fareed