From: Iwo Mergler <iwo@call-direct.com.au>
To: venki kaps <venkiece2005@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: kernel crashing with jffs2 (32MB NAND Flash and 32MB SDRAM )
Date: Wed, 08 Jul 2009 09:34:22 +1000 [thread overview]
Message-ID: <4A53DB7E.2010205@call-direct.com.au> (raw)
In-Reply-To: <6d53329e0907070447o763f214dy2e1b179674cd26f5@mail.gmail.com>
venki kaps wrote:
> Thanks for the reply.
> It's a new hardware i.e, ATMEL AT91SAM9G20 Board
> and at the same first time we are using.
>
> Did *this* board ever work correctly?
> No.
>
> But At mem=8M and mem=16M the Linux is coming up
> but after the kernel prompt it is crashing in between.
>
> At mem=32M the Linux is not coming up over board.
> Before kernel prompt it’s crashing.
>
> If SDRAM is problem, Linux itself is not coming up over board.
> am i right?
>
> is it u-boot problem?
> i.e number of column & row address bits and the number of banks is
> set correctly to match the installed SDRAM
>
> is it required to change u-boot or SDRAM or 2.6.27 kernel?
>
> Could you suggest something?
>
> Thanks & Regards,
> Venkappa
>
Looks like you have faulty hardware. The SDRAM controller is set up
by the bootstrap code, before U-Boot. Since you have probably not
modified that code or the board, those settings are likely to be
correct.
I can't remember what the Atmel U-Boot defaults are, but typically
U-Boot gets loaded just under the 8 or 16MB offset in SDRAM. It
then loads the compressed kernel at about 4MB offset. The kernel
then decompresses itself into the first 2MB or so.
By the time you get a console prompt, a lot of the kernel code
has already run successfully. However, it is possible to get to
this point with partially broken SDRAM.
Have a close look on the board for solder bridges between the
SDRAM pins.
You could try to use SamBA to check the SDRAM memory range
for errors.
Also, you can try to reflash the board with the original Atmel
images, just in case there are transient bit errors in your flash.
Otherwise, contact Atmel.
Best regards,
Iwo
prev parent reply other threads:[~2009-07-07 23:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 11:13 kernel crashing with jffs2 (32MB NAND Flash and 32MB SDRAM ) venki kaps
2009-07-07 3:51 ` Iwo Mergler
2009-07-07 11:47 ` venki kaps
2009-07-07 23:34 ` Iwo Mergler [this message]
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=4A53DB7E.2010205@call-direct.com.au \
--to=iwo@call-direct.com.au \
--cc=linux-mtd@lists.infradead.org \
--cc=venkiece2005@gmail.com \
/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.