Hi,
I saw another thread with same issue but unfortunately commented any
solution on that too.
[U-Boot] Unable to boot the new FIT image
https://lists.denx.de/pipermail/u-boot/2014-May/180688.html
Basically there are 2 issues that I am facing .
1. Compile u-boot 2018.3 with FIT_SIGNATURE and CONFIG
HI ,
I am using marvell armada 388 clearfog pro device.
I am using fitimage to upgrade my device. To make the device bootup secure
I want to sign the fitimage and verify the same in u-boot.
1. However I am observing that the mkimage is unable to assign sign value
to my fit image.
2. One more issue
On Tue, Jan 15, 2019 at 04:34:19PM +0100, Patrick Wildt wrote:
> The last parameter is expected to be the imagefile. Since -E is a
> flag having the output name before -p will make mkimage ignore the
> external offset option.
>
> Signed-off-by: Patrick Wildt
Applied to u-boot/master, thanks!
Hi,
Mark and I have been looking at a problem we've been experiencing on
our build system.
We're running a number of similarly configured makers and seemingly
randomly one will fail to build one of our kirkwood based targets
(specifically the SBx81LIFXCAT that was recently added) with a
segfault
On Fri, Jul 20, 2018 at 12:31:02PM +0200, Michal Simek wrote:
> There is no reason not to use macros which are already defined.
> It is also much easier for grepping.
>
> Signed-off-by: Michal Simek
> Reviewed-by: Simon Glass
Applied to u-boot/master, thanks!
--
Tom
signature.asc
Descripti
On Fri, Mar 30, 2018 at 10:28:19AM +0200, Guillaume GARDET wrote:
> Commit 253c60a breaks the exit value of 'mkimage -T rkimage'
> and print the following error:
> mkimage: Can't print header for Rockchip Boot Image support: Success
>
> It is not a failure to not print headers, so just display
Hi,
When trying to build a kernel uIimage for PowerPC, on a PoewrPC host,
mkimage generates a header that appears to be in Little-endian, rather
than Big-endian, resulting in an unbootable uImage.
From a correct build (NetBSD's mkubootimage):
: 2705 1956 ae84 7a0b 5a55 38e5 010e d6f8 '.
Dear Jeff,
In message <9CEC332718C5B346927BF91C9F4A66EAC03346@prgmbx01> you wrote:
>
> New to U-Boot. It came installed with the BSP on a vendor MPC board
> to boot vxWorks. I have a requirement to use a checksum when
> downloading the vxWorks ELF image. Our development environ is Windows
> 7, us
From: Bittner, Jeff
Sent: Thursday, July 13, 2017 10:19 AM
To: 'u-boot@lists.denx.de'
Subject: mkimage
New to U-Boot. It came installed with the BSP on a vendor MPC board to boot
vxWorks. I have a requirement to use a checksum when downloading the vxWorks
ELF image. Our development environ
New to U-Boot. It came installed with the BSP on a vendor MPC board to boot
vxWorks. I have a requirement to use a checksum when downloading the vxWorks
ELF image. Our development environ is Windows 7, using cross-compiler for
target MPC. I have the source for U-Boot and see that mkimage is
Hi Tom,
On Thu, Jun 29, 2017 at 10:00:55AM -0400, Tom Rini wrote:
> On Wed, Jun 28, 2017 at 09:19:43PM +0300, Baruch Siach wrote:
> > Since commit 5b9d44df2307f (mkimage: Display a better list of available
> > image
> > types) mkimage usage text suggest to "use -T to see a list of available
> >
On Wed, Jun 28, 2017 at 09:19:43PM +0300, Baruch Siach wrote:
> Since commit 5b9d44df2307f (mkimage: Display a better list of available image
> types) mkimage usage text suggest to "use -T to see a list of available image
> types". Unfortunately, commit 02221f29deb8 (mkimage: Convert to use getopt
On Fri, Jan 06, 2017 at 01:14:17PM -0600, George McCollister wrote:
> Add support for signing with the pkcs11 engine. This allows FIT images
> to be signed with keys securely stored on a smartcard, hardware security
> module, etc without exposing the keys.
>
> Support for other engines can be add
Hello,
I'm compiling vanilla 4.1.13 for ls1021a with gcc created with crosstool-ng
Upon kernel build completion I got the file: ls1021a-twr.dtb
Then I ran:
mkimage -A arm -O Linux -C none -T kernel -n 3.14.4 -d ls1021a-twr.dtb
uImage.dtb
using tftp I downloaded:
uImage -> 0x8300
uRamdisk ->
On Fri, Nov 04, 2016 at 02:22:15PM +0100, Tomeu Vizoso wrote:
> Adds -i option that allows specifying a ramdisk file to be added to the
> FIT image when we are using the automatic FIT mode (no ITS file).
>
> This makes adding Depthcharge support to LAVA much more convenient, as
> no additional co
On Mon, Jul 11, 2016 at 10:54:26PM -0700, Teddy Reed wrote:
> Signed-off-by: Teddy Reed
> Reported-by: Coverity (CID: 150277)
> Reviewed-by: Tom Rini
Applied to u-boot/master, thanks!
--
Tom
signature.asc
Description: Digital signature
___
U-Boot
Hello Jagan,
I just realize the uboot tool mkimage i have is "mkimage version
2013.10", which does not support "-K,-k" and other options. Thus the
command failed to run:
$ mkimage –D “${DTC_OPS}” –f rsa.its –K zynq-zed-pubkey.dtb –k mykeys
–r rsa_signed.img
How can I get the latest mkimage whic
Hi Tom,
On 30 June 2016 at 09:46, Simon Glass wrote:
>
> Hi Tom,
>
> On 27 June 2016 at 23:50, Tom Van Deun wrote:
> > Hello all
> >
> > I have been trying to create a FIT image using mkimage using the command:
> >
> > mkimage -D "-I dts -O dtb -p 2000" -f name.its name.fit
> >
> > The output is
Hi Tom,
On 27 June 2016 at 23:50, Tom Van Deun wrote:
> Hello all
>
> I have been trying to create a FIT image using mkimage using the command:
>
> mkimage -D "-I dts -O dtb -p 2000" -f name.its name.fit
>
> The output is:
>
> DTC: dts->dtb on file "name.its"
> mkimage: Can't read name.fit.tmp:
Hello all
I have been trying to create a FIT image using mkimage using the command:
mkimage -D "-I dts -O dtb -p 2000" -f name.its name.fit
The output is:
DTC: dts->dtb on file "name.its"
mkimage: Can't read name.fit.tmp: Invalid argument
mkimage Can't add hashes to FIT blob
No matter what I
The behavior of the global variable "pbl_cmd_initaddr" seems wrong,
and prevent to use some address depending on the size of the SPL.
This is maybe due to some alignment constraints but I didn't find any
documentation that would explain it.
The variable is initialized like this:
288
Hi Tom,
2016-05-03 1:32 GMT+02:00 Tom Rini :
> On Sun, May 01, 2016 at 03:01:27AM +0200, Andreas Bießmann wrote:
>
> > The getopt(3) optstring '-' is a GNU extension which is not available on
> BSD
> > systems like OS X.
> >
> > Remove this dependency by implementing argument parsing in another w
On Sun, May 01, 2016 at 03:01:27AM +0200, Andreas Bießmann wrote:
> The getopt(3) optstring '-' is a GNU extension which is not available on BSD
> systems like OS X.
>
> Remove this dependency by implementing argument parsing in another way. This
> will also change the lately introduced '-b' swit
Hi,
For adding public keys to uboot dtb the mkimage step is
mkimage -D "-I dts -O dtb -p 2000" -F -k keys -K u-boot.dtb -r fitImage
It resigns fitImage and adds public key to uboot dtb
but why do we need fitImage for adding public keys to uboot dtb ? can't
this be two different steps ? there is
On Fri, Dec 04, 2015 at 12:11:23AM +0200, Philippe De Swert wrote:
> Seems 92a655c3 broke creating multi and script type images.
> Since the file1:file2:file3 string does not get split up,
> it fails on trying to open an non-existing file.
>
> mkimage -A arm -O linux -T multi -C none -d zImage:s
On Wed, Sep 2, 2015 at 3:52 PM, Otavio Salvador
wrote:
> On Wed, Sep 2, 2015 at 4:48 PM, Robert Nelson wrote:
>> I've just finished bisecting a build error for the mx23_olinuxino platform.
>>
>> git bisect points to:
>>
>> http://git.denx.de/?p=u-boot.git;a=commit;h=92a655c326b22de58dcd5371ca1a62
On Wed, Sep 2, 2015 at 4:48 PM, Robert Nelson wrote:
> I've just finished bisecting a build error for the mx23_olinuxino platform.
>
> git bisect points to:
>
> http://git.denx.de/?p=u-boot.git;a=commit;h=92a655c326b22de58dcd5371ca1a62fdc57f8e04
I think it has been fixed and merged today in maste
Hi Simon,
I've just finished bisecting a build error for the mx23_olinuxino platform.
git bisect points to:
http://git.denx.de/?p=u-boot.git;a=commit;h=92a655c326b22de58dcd5371ca1a62fdc57f8e04
to build:
make ARCH=arm CROSS_COMPILE=${CC} distclean
make ARCH=arm CROSS_COMPILE=${CC} mx23_olinuxin
Hi,
On 4 November 2014 12:55, Wolfgang Denk wrote:
>
> Dear John,
>
> In message
> you
> wrote:
> >
> > At present, the load address and entry point are both "unsigned int". I'm
> > porting to aarch64, and will run the SPL at 0x803100. mkimage
> > truncates this to 0x3100. Are there
Dear John,
In message
you
wrote:
>
> At present, the load address and entry point are both "unsigned int". I'm
> porting to aarch64, and will run the SPL at 0x803100. mkimage
> truncates this to 0x3100. Are there any plans to support a load
> address and entry point larger than 32 b
At present, the load address and entry point are both "unsigned int". I'm
porting to aarch64, and will run the SPL at 0x803100. mkimage
truncates this to 0x3100. Are there any plans to support a load
address and entry point larger than 32 bits?
___
On Wed, Oct 29, 2014 at 12:34 PM, DaveKucharczyk
wrote:
> Fabio Estevam-2 wrote
>> This command is not correct. You missed the bs=512 part.
>>
>> It should be:
>>
>> dd if=u-boot.imx of=/dev/sdX bs=512 seek=2; sync
>
> Sorry, I forgot the block size in my original email. Yes, I do include
> bs=512
Hi Dave,
On 29/10/2014 14:52, DaveKucharczyk wrote:
> I was able to build using V=1 and noticed the entry point,
> CONFIG_SYS_TEXT_BASE, wasn't defined in include/configs/mx53_xxx.h file. We
> previously had it defined in /board/freescale/mx53_xxx/config.mk. Now
> everything builds without error.
Fabio Estevam-2 wrote
> This command is not correct. You missed the bs=512 part.
>
> It should be:
>
> dd if=u-boot.imx of=/dev/sdX bs=512 seek=2; sync
Sorry, I forgot the block size in my original email. Yes, I do include
bs=512. That is not the problem.
I'm going through all the README's aga
On Wed, Oct 29, 2014 at 11:52 AM, DaveKucharczyk
wrote:
> I’ve triple checked the pads and flash header. I dd the resulting,
> non-padded, u-boot.imx image to sd card by “dd if=u-boot.imx of=/dev/sdd
> seek=2 && sync”, but I get no life.
This command is not correct. You missed the bs=512 part.
Simon, thank you for your help.
Simon Glass-3 wrote
> BTW best not to have this in your sig when sending to a public mailing
> list.
I have no control of over my company's email signature so I switched my
subscription to use gmail.
Simon Glass-3 wrote
> There are only 3 places in mkimage.c which
Hi David,
On 27 October 2014 12:18, Kucharczyk, David wrote:
> Hi, I am in the middle of upgrading u-boot-2009.08 to u-boot-2014.07. Our
> resident u-boot expert is on vacation and I'm running into some issues. After
> working through a ton of compile errors I think I'm getting close.
>
> Our s
Hi, I am in the middle of upgrading u-boot-2009.08 to u-boot-2014.07. Our
resident u-boot expert is on vacation and I'm running into some issues. After
working through a ton of compile errors I think I'm getting close.
Our system is based on the Freescale iMX53.
I am able to build and run on a
On 26 May 2014 17:26, Simon Glass wrote:
[snip[
>> 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.
Sorry, I meant directory.
- Simon
Hi Yegor,
On 25 May 2014 23:41, Yegor Yefremov wrote:
> Hi Simon,
>
> On Sat, May 24, 2014 at 3:58 AM, Simon Glass wrote:
>> Hi Yegor,
>>
>> On 20 May 2014 20:59, Yegor Yefremov wrote:
>>> I have following folder structure:
>>>
>>> board/kernel_fdt.its
>>> output/images/zImage
>>>
>>> The kerne
Hi Simon,
On Sat, May 24, 2014 at 3:58 AM, Simon Glass wrote:
> Hi Yegor,
>
> On 20 May 2014 20:59, Yegor Yefremov 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
Hi Yegor,
On 20 May 2014 20:59, Yegor Yefremov 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
> "
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 outp
tion.
Regards,
Simon
>
> Best wishes,
>
> -邮件原件-
> 发件人: s...@google.com [mailto:s...@google.com] 代表 Simon Glass
> 发送时间: 2013年2月1日 22:25
> 收件人: Tiger Liu
> 抄送: u-boot@lists.denx.de
> 主题: Re: [U-Boot] [U-boot] mkimage -F parameter
>
> Hi Tiger,
>
> On Thu
表 Simon Glass
发送时间: 2013年2月1日 22:25
收件人: Tiger Liu
抄送: u-boot@lists.denx.de
主题: Re: [U-Boot] [U-boot] mkimage -F parameter
Hi Tiger,
On Thu, Jan 31, 2013 at 3:36 AM, wrote:
> Hi, experts:
>
> It seems mkimage has supported signing a image.
This code is not yet merged, as you have d
Hi Tiger,
On Thu, Jan 31, 2013 at 3:36 AM, wrote:
> Hi, experts:
>
> It seems mkimage has supported signing a image.
This code is not yet merged, as you have discovered.
>
> So, I have a question about signed linux kernel image:
>
> 1. if kernel image is signed by mkimage tool.
>
> Could
-boun...@lists.denx.de] 代表
Wolfgang Denk
发送时间: 2013年1月31日 21:55
收件人: Tiger Liu
抄送: u-boot@lists.denx.de
主题: Re: [U-Boot] [U-boot] mkimage -F parameter
Dear tiger...@viatech.com.cn,
In message you
wrote:
>
> It seems mkimage has supported signing a image.
Does it?
The mainline code does no
Dear tiger...@viatech.com.cn,
In message you
wrote:
>
> It seems mkimage has supported signing a image.
Does it?
The mainline code does not know any '-F' option...
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office
Hi, experts:
It seems mkimage has supported signing a image.
So, I have a question about signed linux kernel image:
1. if kernel image is signed by mkimage tool.
Could uboot verify this signed linux kernel image bf jumping to its
entry point function?
2. if uboot could verify the s
Hi,
I recently tried to get mkimage compiling on Cygwin and was successful with
a fresh git clone and with 'make tools' on the command line, except that I
had to modify config.mk to not include the -ansi flag for Cygwin (line 75
in my config.mk). I don't know why this line is included, since -ansi
Dear Fabio Giovagnini,
In message <201101191135.58566.fabio.giovagn...@aurion-tech.com> you wrote:
> Thanks
Depending on the actual system behaviour this may or may not be ok.
For example, nearly all PowerArchitecture systems use address1=0 and
address2=0.
Best regards,
Wolfgang Denk
--
DENX
Thanks
--
Ing. Fabio Giovagnini
Aurion s.r.l.
P.I e C.F.
00885711200
skype: aurion.giovagnini
Tel. +39.051.594.78.24
Fax. +39.051.082.14.49
Cell. +39.335.83.50.919
www.aurion-tech.com
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/ma
Re. XIP, we recently did some boot time optimizations and found that
if we loaded the uncompressed kernel-only uImage to RAM (diskboot)
with the load address in the uImage the same as the load address given
to diskboot and the execute addres at +64 then we shaved off 0.15
seconds by letting the ker
Dear Mike Frysinger,
In message <201001190415.22075.vap...@gentoo.org> you wrote:
>
...
> > not been much used on other platforms or even more recent kernels
> > than the 2.4.4 version we've been using by then (for details please
> > see http://www.denx.de/wiki/view/DULG/ConfigureLinuxForXIP)
>
>
On Tuesday 19 January 2010 03:55:15 Wolfgang Denk wrote:
> Mike Frysinger wrote:
> > the current mkimage requires XIP images to have their entry point set to
> > the load address + 64 bytes. my question is simply, why ? why cant the
> > entry point be an arbitrary location ? i cant seem to find
Dear Mike Frysinger,
In message <201001181955.55856.vap...@gentoo.org> you wrote:
>
> the current mkimage requires XIP images to have their entry point set to the
> load address + 64 bytes. my question is simply, why ? why cant the entry
> point be an arbitrary location ? i cant seem to find a
the current mkimage requires XIP images to have their entry point set to the
load address + 64 bytes. my question is simply, why ? why cant the entry
point be an arbitrary location ? i cant seem to find any technical reason for
this restriction.
the Blackfin kernel has long been using an ent
On Mon, Jun 08, 2009 at 10:48:58AM -0500, Hollis Blanchard wrote:
>Sorry, was on vacation. Copying a couple mailing lists...
>
>On Tue, 2009-06-02 at 12:34 +0300, Avi Kivity wrote:
>> I am now doing regular build tests on various platforms (kernel only for
>> now).
>
>That's great! Much appreciate
Hollis Blanchard wrote:
>> But ppc wants a mkimage and I don't have one to give it. Where
>> can I find it?
>>
>
> mkimage is a tool provided by u-boot
> (http://git.denx.de/cgi-bin/gitweb.cgi?p=u-boot.git;a=summary). IIRC
> people have discussed the need to include a copy in the kernel sour
Sorry, was on vacation. Copying a couple mailing lists...
On Tue, 2009-06-02 at 12:34 +0300, Avi Kivity wrote:
> I am now doing regular build tests on various platforms (kernel only for
> now).
That's great! Much appreciated.
> But ppc wants a mkimage and I don't have one to give it. Where
>
Dear Bartek,
in message <[EMAIL PROTECTED]> I wrote:
>
> compiling U-Boot in an old OS environment (RedHat-7.3 :-) gives the
> following warnigns from mkimage.[ch]:
>
> In file included from image.c:71:
> mkimage.h:41:23: warning: ISO C does not permit named variadic macros
> image.c:2422:54: wa
Dear Bartek,
compiling U-Boot in an old OS environment (RedHat-7.3 :-) gives the
following warnigns from mkimage.[ch]:
In file included from image.c:71:
mkimage.h:41:23: warning: ISO C does not permit named variadic macros
image.c:2422:54: warning: ISO C99 requires rest arguments to be used
image
On Fri, 8 Aug 2008, Kumar Gala wrote:
> does mkimage in the current 1.3.4-rc2 tree work for FIT w/o any
> patches? If not can we fix that since dtc 1.2.0 is out?
It doesn't. I was going to ask but you beat me :)
It would be very nice to have it fixed before 1.3.5.
=== Cut ===
TFTP side :
-
does mkimage in the current 1.3.4-rc2 tree work for FIT w/o any
patches? If not can we fix that since dtc 1.2.0 is out?
- k
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
64 matches
Mail list logo
