From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [EXTERNAL] Re: Build uImage with ptxdist for a Toradex Apalis iMX-6q module
Date: Fri, 9 Feb 2018 15:25:34 +0100 [thread overview]
Message-ID: <20180209142534.qxe73vaxdxekjogp@pengutronix.de> (raw)
In-Reply-To: <aec96a8612964effa6781bf647d5ae21@lujp1svwi090222.corp.mooginc.com>
Hi,
On Fri, Feb 09, 2018 at 10:46:38AM +0000, Milluzzo, Massimo wrote:
> This is the result:
[...]
> + local src=/data/developer/user/nfs/project/External/Sources/Linux/bsp/src/u-boot-2016.11.tar.bz2
> + local md5=ca1f6e019d08aff8d0ca1beb2e66737d
> + local md5sum
> + '[' -z /data/developer/user/nfs/project/External/Sources/Linux/bsp/src/u-boot-2016.11.tar.bz2 ']'
> + case "${PTXCONF_SETUP_CHECK}" in
> + '[' ca1f6e019d08aff8d0ca1beb2e66737d = none ']'
> + for md5sum in '${md5}'
> + echo 'ca1f6e019d08aff8d0ca1beb2e66737d /data/developer/user/nfs/project/External/Sources/Linux/bsp/src/u-boot-2016.11.tar.bz2'
> + md5sum --check
> + return 1
> + '[' always = update ']'
> + '[' -z ca1f6e019d08aff8d0ca1beb2e66737d ']'
> + ptxd_bailout 'Wrong md5sum for '\''u-boot'\'' (/data/developer/user/nfs/project/External/Sources/Linux/bsp/src/u-boot-2016.11.tar.bz2)'
> + echo 'ptxdist: error: Wrong md5sum for '\''u-boot'\'' (/data/developer/user/nfs/project/External/Sources/Linux/bsp/src/u-boot-2016.11.tar.bz2)'
It's strange, that this doesn't show up in your output.
> + exit 1
> make: *** [/data/developer/user/nfs/project/External/Sources/Linux/bsp/platform-Toradex/state/u-boot.get] Error 1
>
> The error is really weird, in ptxdist configuration I use the result of the "md5sum" command (my configuration: https://ibb.co/c59egH ):
>
> $ md5sum /data/developer/user/nfs/project/External/Sources/Linux/bsp/src/u-boot-2016.11.tar.bz2
> 946cc788dea345987df565b834c4ae0f /data/developer/user/nfs/project/External/Sources/Linux/bsp/src/u-boot-2016.11.tar.bz2
>
> $ md5sum /data/developer/user/nfs/project/External/Sources/Linux/bsp/src/u-boot-2016.11.tar.bz2 | md5sum -c
> /data/developer/user/nfs/project/External/Sources/Linux/bsp/src/u-boot-2016.11.tar.bz2: OK
>
>
> I can't figure out where it takes the value " ca1f6e019d08aff8d0ca1beb2e66737d ".
From your platformconfig. You need to set the correct value:
$ ptxdist menuconfig platform
bootloaders --->
[*] U-Boot --->
(ca1f6e019d08aff8d0ca1beb2e66737d) U-Boot source md5
Regards,
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2018-02-09 14:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 15:53 [ptxdist] " Milluzzo, Massimo
2018-02-05 10:58 ` Roland Hieber
2018-02-05 15:27 ` [ptxdist] [EXTERNAL] " Milluzzo, Massimo
2018-02-08 9:21 ` [ptxdist] " Michael Olbrich
2018-02-08 12:55 ` [ptxdist] [EXTERNAL] " Milluzzo, Massimo
2018-02-08 14:53 ` Michael Olbrich
2018-02-09 7:44 ` Milluzzo, Massimo
2018-02-09 9:13 ` Michael Olbrich
2018-02-09 10:46 ` Milluzzo, Massimo
2018-02-09 14:25 ` Michael Olbrich [this message]
2018-02-09 14:56 ` Milluzzo, Massimo
2018-02-14 9:49 ` [ptxdist] FW: " Milluzzo, Massimo
2018-02-14 11:04 ` m.olbrich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180209142534.qxe73vaxdxekjogp@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox