All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Uncompression of image takes time.
Date: Wed, 28 Feb 2007 12:07:55 -0500	[thread overview]
Message-ID: <45E5B6EB.8090901@smiths-aerospace.com> (raw)
In-Reply-To: <loom.20070228T172807-968@post.gmane.org>

Adarsh Babu wrote:
> Hi,
> 
> I have an image which is 1.5MB in size after compression, thats is done for 
> MCF5271. When i try to load this on a MCF5271 eval board using u-boot 1.2.0 it 
> takes about 25 secs to just uncompress. I loaded a MCF5272 eval board with U-
> Boot 1.2.0 and then tried to start the same image(which was done for MCF5271). 
> It was very fast. The checksum verification finish off in a second and 
> uncompression in 10 seconds ! 
> 
> The clock configurations for both are provided below:
> M5272C3.h
> define CFG_HZ			1000
> #define CFG_CLK			66000000
> 
> M5271EVB.h:
> define CFG_HZ			1000000
> #define CFG_CLK			100000000
> 
> What should I do to get the image to uncompress faster in the MCF5271 EVB?
> 
> Regards,
> Adarsh.

1) Your CFG_HZ looks like a problem: it should be 1000 and your timer 
tick interrupt should be running 1000 times per second to match.  If you 
are indeed ticking 1,000,000 times per second, you are spending all of 
your processor time in your timer ISR.

2) Why is your image 1.5MB?  I suspect you have large unused areas of 
memory (typically due to ISR vectors, followed by a huge unused gap, 
followed by the code).  If you fix your image size (assuming it is 
broken), the checksum and uncompress will be much faster.

gvb

  reply	other threads:[~2007-02-28 17:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-28 16:39 [U-Boot-Users] Uncompression of image takes time Adarsh Babu
2007-02-28 17:07 ` Jerry Van Baren [this message]
2007-03-01  6:12   ` Adarsh Babu
2007-03-01 16:37     ` Adarsh Babu
2007-03-01 18:22     ` Jerry Van Baren
2007-03-02 12:11 Jerry Van Baren
2007-03-05 15:09 ` Adarsh Babu

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=45E5B6EB.8090901@smiths-aerospace.com \
    --to=gerald.vanbaren@smiths-aerospace.com \
    --cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.