mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Jose Luis Zabalza <jlz.3008@gmail.com>
To: barebox@lists.infradead.org
Subject: Re: Configure RAM size on iMX53 board
Date: Tue, 8 Nov 2016 21:51:36 +0100	[thread overview]
Message-ID: <CAKZffXG5CG9R8e4xoMdP6DFJq42ng5EQqwmhafikNn6HNzuedQ@mail.gmail.com> (raw)
In-Reply-To: <20161108075317.j4xkf7zpkdfyt5y3@pengutronix.de>

> So you have 512MiB on each chip select, so I assume that on the 512MiB
> board variants CS1 is not equipped.

Yes, it is.

>In that case you can in lowlevel.c
> test if you find SDRAM on CS1 and if not, disable the chip select
> completely in the SDRAM controller.

OK. But how ? I enable CS0 and CS1 on DCD table. Is there any way to
tell barebox not to use CS1 ?

> I am not sure how you can detect if there's SDRAM on CS1. I've seen
> situations in which the board just hangs if you access non existent RAM
> areas.

I have tried it, but I have not be able to implement a code for
autodetect. If the code write or read a value on a position without
physical  chip, the microcontroller hangs. ????

But it's not a problem. A solution is configure both CS and MMU. If
bootloader don't access to high positions, there is not problem. After
I set a environment variable with memory size and the mem kernel
parameter (or ATAG) does the rest.

So, I have to make sure Barebox don't reach CS1 memory positions. That is all.

Thanks for your help. See you later.


-- 

jlz.3008  a t  gmail.com
Linux Counter 172551
https://linuxcounter.net/cert/172551.png

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

  reply	other threads:[~2016-11-08 20:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-03 20:30 Jose Luis Zabalza
2016-11-03 22:42 ` Andrey Smirnov
2016-11-04  7:18 ` Sascha Hauer
2016-11-05  6:39   ` Jose Luis Zabalza
2016-11-07  7:43     ` Sascha Hauer
2016-11-08  5:09       ` Jose Luis Zabalza
2016-11-08  7:53         ` Sascha Hauer
2016-11-08 20:51           ` Jose Luis Zabalza [this message]
2016-11-08 21:24             ` Sascha Hauer
2016-11-09  4:23               ` Jose Luis Zabalza
2016-11-09  6:41                 ` Sascha Hauer

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=CAKZffXG5CG9R8e4xoMdP6DFJq42ng5EQqwmhafikNn6HNzuedQ@mail.gmail.com \
    --to=jlz.3008@gmail.com \
    --cc=barebox@lists.infradead.org \
    /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