[U-Boot] mkimage: path behavior for FIT images

Simon Glass sjg at chromium.org
Tue May 27 05:26:17 CEST 2014


Hi Yegor,

On 25 May 2014 23:41, Yegor Yefremov <yegorslists at googlemail.com> wrote:
> Hi Simon,
>
> On Sat, May 24, 2014 at 3:58 AM, Simon Glass <sjg at chromium.org> wrote:
>> Hi Yegor,
>>
>> On 20 May 2014 20:59, Yegor Yefremov <yegorslists at googlemail.com> wrote:
>>> I have following folder structure:
>>>
>>> board/kernel_fdt.its
>>> output/images/zImage
>>>
>>> The kernel.its has following path for the zImage:
>>>
>>> data = /incbin/("output/images/zImage");
>>>
>>> When I invoke mkimage like this, it complains, that
>>> "output/images/zImage" doesn't exist:
>>>
>>> mkimage -f board/kernel_fdt.its output/images/kernel_fdt.itb
>>>
>>> in other words it seems to take zImage's relative path starting from
>>> "board", where kernel_fdt.its is located. Is it a desired behavior and
>>> how can I override it, so that root will be set to the mkimage
>>> invocation path?
>>
>> You could put ../output/... in there perhaps.
>
> Your workaround is working. Thanks.
>
> I just wanted to know, if it was a desired behavior. Can it be the dtc
> is invoked from "board/" and this is the cause of such behavior?

Yes, it uses the current directly as the base.

Regards,
Simon


More information about the U-Boot mailing list