mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Alexander Shiyan <shc_work@mail.ru>
Cc: barebox@lists.infradead.org
Subject: Re: Boot from SD fail after 2013.02
Date: Thu, 18 Apr 2013 20:23:17 +0200	[thread overview]
Message-ID: <20130418182317.GJ1906@pengutronix.de> (raw)
In-Reply-To: <1366304572.52315039@f26.mail.ru>

On Thu, Apr 18, 2013 at 09:02:52PM +0400, Alexander Shiyan wrote:
> > On Thu, Apr 18, 2013 at 03:06:26PM +0400, Alexander Shiyan wrote:
> > > 
> > > So. OK, I temporary patch my board and it working now.
> > > Please forget about correct memory size, it is not true.
> > > Size is incorrect. Both banks are enabled and size detected as 512M.
> > > I think this size is programmed by flash_header:
> > >   { .ptr_type = 4, .addr = 0x83fd9000, .val = 0xb2a20000, },
> > >   { .ptr_type = 4, .addr = 0x83fd9008, .val = 0xb2a20000, },
> > > 
> > > After program NAND and start from NAND, size is still wrong...
> > > So, what we can do it this case for proper operation? Disable second bank?
> > 
> > When writing the autodetection code I assumed that all boards correctly
> > setup the SDRAM controller. Appearently I was wrong.
> > 
> > I suggest disabling the second chip select since it's not used on your
> > board. However, I begin doubting that it was the right decision to
> > depend on ram size detection.
> 
> Yes, disabling second bank is helps.
> So, I repair my second board (same as first, but with real 512M of SDRAM).
> Works, but of course memory is fixed at 256M. Tomorrow I will test current
> 2013.04 on this board since probably problem appears only on 256M-version.
> Currently I think about return fixed table of memory in the board file or get
> memory size by testing memory. In both cases we need to disable ESDCTL
> module and now I do not know how make it better rather than simple remove
> this module from Makefile.

I wonder if it's possible to detect whether there actually is memory on
the seconf bank. I remember trying it (probably on some other i.MX), but
all I got was a locked up system when I tried to access non present
SDRAM.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

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

  reply	other threads:[~2013-04-18 18:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1366188021.710900767@f16.mail.ru>
2013-04-17 10:01 ` Sascha Hauer
2013-04-17 11:40   ` Re[2]: " Alexander Shiyan
2013-04-17 12:02     ` Sascha Hauer
2013-04-17 12:19       ` Re[2]: " Alexander Shiyan
2013-04-17 12:22         ` Sascha Hauer
2013-04-18 11:06           ` Re[2]: " Alexander Shiyan
2013-04-18 11:59             ` Sascha Hauer
2013-04-18 17:02               ` Re[2]: " Alexander Shiyan
2013-04-18 18:23                 ` Sascha Hauer [this message]
2013-04-19  8:10                   ` Alexander Shiyan

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=20130418182317.GJ1906@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=shc_work@mail.ru \
    /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