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

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...

>[...]
>
> "/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

mini2440:/ reset


barebox 2011.03.0-00081-g6402171 (Apr  3 2011 - 11:12:11)

Board: Mini 2440
registered netconsole as cs1
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB
3,3V 8-bit) 
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
dm9000 i/o: 0x20000300, id: 0x90000a46 
eth@eth0: got MAC address from EEPROM: 00:00:00:00:00:00
refclk:    12000 kHz
mpll:     405000 kHz
upll:      48000 kHz
fclk:     405000 kHz
hclk:     101250 kHz
pclk:      50625 kHz
SDRAM1:   CL2@101MHz
Malloc space: 0x33a00000 -> 0x33e00000 (size  4 MB)
Stack space : 0x339f8000 -> 0x33a00000 (size 32 kB)
running /env/bin/init...

Hit any key to stop autoboot:  3

type update_kernel [<imagename>] to update kernel into flash
type update_root [<imagename>] to update rootfs into flash

mini2440:/ printenv
locals:
[...]
nfsroot=:/path/to/nfs/root
[...]
globals:
PATH=/env/bin
mini2440:/ 

No error message, nothing. 

Zoltan

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

  reply	other threads:[~2011-04-04 12:13 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 [this message]
2011-04-04 12:26     ` Juergen Beisert
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=20110404221321.0452b0b9@manocska.bendor.com.au \
    --to=zoltan@bendor.com.au \
    --cc=barebox@lists.infradead.org \
    --cc=jbe@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