Correcting Jagannadh's email id.
thanks Ram
On Tue, Sep 15, 2015 at 6:14 PM, Ramakrishnan Meenakshi Sundaram < ramki982@gmail.com> wrote:
Hi Jagannadh,
I'm Ram from Symantec. I've been working on using u-boot secure booting with RSA.
As part of that - I was observing that once we define CONFIG_FIT_SIGNATURE
- it disables the CONFIG_IMAGE_FORMAT_LEGACY.
As a result - when the system detects a boot.scr in my sd card - it rejects that with
Wrong image format for "source" command SCRIPT FAILED: continuing...
After this, when it comes to the u-boot prompt - I'm able to successfully boot my kernel. So i wanted to explore ways to automatically boot a FIT image. Is there any recommended way of automatically booting fit images ?
Some additional notes (based on code walkthrough) :
I'm seeing this is due to the code sequence in cmd_source.c & image.c. On further analysis - I did find that when mkimage is converting the boot.cmd to boot.scr, it uses the default legacy header. As a result when CONFIG_IMAGE_FORMAT_LEGACY is disabled - the boot.scr fails to execute.
thanks Ram