ltib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ltib] Freescale iMX25 (or other BSP) / Bad MD5 values


From: Franz Trierweiler
Subject: Re: [Ltib] Freescale iMX25 (or other BSP) / Bad MD5 values
Date: Mon, 19 Oct 2009 13:35:22 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4pre) Gecko/20091014 Fedora/3.0-2.8.b4.fc11 Thunderbird/3.0b4

Le 19/10/2009 10:20, Stuart Hughes a écrit :
Hi Franz,

In fact given your problem with the mux_server patch, it may be the case that the .md5 files are correct and the files corrupt.

I've attached a list of MD5SUMS I just generated, which should be correct.  After de-compression put it where your files are and then run:

$ md5sum -c MD5SUMS

This will verify the files on the GPP.  However, the files you don't have will generate warnings (I think) and the files not on the GPP in the ISO will not be verified.

You really need to take this up with Freescale.

Regards, Stuart

Franz Trierweiler wrote:
Good Evening,

I just wanted to let you know that on the iMX25 CD/ROM provided by Freescale (the ISO image is available at http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX25PDK&fpsp=1&tab=Design_Tools_Tab - the image to pick-up is L2.6.26_MX25TO1_AV_ER3_source.tar.gz ), many MD5 files have a wrong content in /opt/freescale/pkgs (in fact, the first time I ran ./ltib I got a MD5 error and rpm-fs.patch was renamed into rpm-fs.patch.bad). The only way to fix this is to recompute all MD5 values either in the /opt/freescale/pkgs (just after ./install) or in the directory where you have copied the CD/ROM content.

Yo can run this fast and dirty script (sorry, comments are in french):

# Liste les fichiers du répertoire et
# calcule le md5 correspondant qu'il stocke
# dans un fichier du même nom avec extension md5

# Efface les MD5
rm *.md5
for i in $(ls); do
    file=$i;
    echo $file;
    md5sum $file > ${file}.md5;
done;

I submitted the issue to Freescale technical support and they told me they were aware of the presence of bad MD5 files. They send me back a set of modified files but many of them still had wrong MD5 checksums (that's why I recompute them). Of course, recomputing all MD5 values is a bit stupid since we loose the benefit of checking what Freescale provided us with.

The iMX25 evalboard and dev kit are quite new, so there are still minor issues. Nevertheless, there I am interested in knowing whether other iMX users (27/35) faced the same issue.

Regards,
Franz


------------------------------------------------------------------------

_______________________________________________
LTIB home page: http://ltib.org

Ltib mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/ltib
Hi Stuart,

Thanks for the MD5 list. I checked and indeed, my mux_server.c checksum was wrong despite the fact that the two files (Freescale's one and the file available from bitshrine gpp) seemed to be identical. Eventually since it is no use of trying to find out why this file is corrupted, I took mux_server.c from gpp and stuck it into pkgs.

I restarted ./lib and this works fine. The first zImage and rootfs is being built.

I am going to send back this mux_server.c issue to Freescale tech support so that they fix at least this in the CD/ROM and ISO image.

Regards,
Franz

reply via email to

[Prev in Thread] Current Thread [Next in Thread]