mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Juergen Beisert <jbe@pengutronix.de>
To: "Zoltán Kócsi" <zoltan@bendor.com.au>
Cc: barebox@lists.infradead.org
Subject: Re: More Mini2440 questions...
Date: Mon, 4 Apr 2011 14:26:24 +0200	[thread overview]
Message-ID: <201104041426.24763.jbe@pengutronix.de> (raw)
In-Reply-To: <20110404221321.0452b0b9@manocska.bendor.com.au>

Hi Zoltán,

Zoltán Kócsi wrote:
> On Mon, 4 Apr 2011 13:13:31 +0200
>
> Juergen Beisert <jbe@pengutronix.de> wrote:
> > Hi Zoltán,
> >
> > Zoltán Kócsi wrote:
> > > Thanks for all the answers for my previous questions!
> > >
> > > The 'next' branch indeed boots from the NAND FLASH like a charm.
> >
> > \o/
> >
> > Just for my list of tested min2440 variants: What type of SDRAMs and
> > NAND is your system using?
>
> The SDRAM is Micron 48LC16M16A2-75, the NAND is Samsung K9F1G08U0B.
>
> Actually, taking a look at the RAM datasheet of the reveals that with a
> 3 clock RAS->CAS latency the chip can can merrily work with a 133MHz
> bus clock, so the S3C's FCLK could be boosted up to 532MHz. A
> 30% speed increase is not something to sneeze on...

You can try. But when I read the datasheet, most of the time they only talk 
about 400 MHz max. CPU clock, and never about 533 MHz any more.

BTW: The average data throughput of a SDRAM running at 133 MHz @ CL3 is lower 
than of a SDRAM running at 100 MHz @ CL2. The CL3 hurts more than you will 
win with the increased clock.
 
> >[...]
> >
> > "/env/config" for parameterization. Maybe these file will help you to
> > understand how it works.
>
> I'll try my bestto grok them :-)
>
> > So, the changes in your environment are lost after reboot?
>
> Yes.
>
> > Do you see any kind of error message (like CRC sum errors)? when
> > barebox comes up after reset and tries to load the saved environment?
>
> No. Here's what goes on, with unimportant stuff deleted:
>
> mini2440:/ printenv
> locals:
> machine=mini2440
> [...]
> nfsroot=:/path/to/nfs/root
> [...]
> globals:
> PATH=/env/bin
>
> mini2440:/ nfsroot=/some/other/root
> mini2440:/ PATH=$PATH:/some/location
> mini2440:/ printenv
> locals:
> [...]
> nfsroot=/some/other/root
> [...]
> globals:
> PATH=/env/bin:/some/location
>
> mini2440:/ saveenv
> saving environment

Ahh, no I see the problem: You did not change anything in the environment. You 
are using barebox, not u-boot!

Try to edit the /env/config file at your mini2440 instead:

mini2440:/ edit /env/config
mini2440:/ saveenv

Think in scripts now, not in environment variables any more.

Regards,
Juergen

-- 
Pengutronix e.K.                              | Juergen Beisert             |
Linux Solutions for Science and Industry      | Phone: +49-8766-939 228     |
Vertretung Sued/Muenchen, Germany             | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686              | http://www.pengutronix.de/  |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2011-04-04 12:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04 11:02 Zoltán Kócsi
2011-04-04 11:13 ` Juergen Beisert
2011-04-04 12:13   ` Zoltán Kócsi
2011-04-04 12:26     ` Juergen Beisert [this message]
2011-04-04 12:52       ` Marc Kleine-Budde
2011-04-05  3:09         ` Zoltán Kócsi
2011-04-05  3:07       ` Zoltán Kócsi

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=201104041426.24763.jbe@pengutronix.de \
    --to=jbe@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=zoltan@bendor.com.au \
    /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