mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: Jose Luis Zabalza <jlz.3008@gmail.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: Configure RAM size on iMX53 board
Date: Thu, 3 Nov 2016 15:42:13 -0700	[thread overview]
Message-ID: <CAHQ1cqFuQdm8EykmLh7b589Y6VLw8Vr69_goSw5-oo5mBikJsw@mail.gmail.com> (raw)
In-Reply-To: <CAKZffXFSfTJJiwj2ZOB7nT-DWZ7_AqyysZkavNM++c4LSp6tZg@mail.gmail.com>

On Thu, Nov 3, 2016 at 1:30 PM, Jose Luis Zabalza <jlz.3008@gmail.com> wrote:
> Hello everybody
>
> I have two iMX53 custom boards. They are the same board but 512MB vs
> 1GB RAM version.  Both boards are working with the same Uboot binary
> but I would like use Barebox.
>
> I have to be able to run Barebox on 1GB version but the same Barebox
> binary don't work on 512MB version.
>
> I use imx-usb-loader to put Barebox on the board. On 1GB version
> Barebox are working OK and load Linux kernel successfully. On 512MB
> Barebox are loaded successfully but don't work. lsusb tell me the
> board is working on Serial Download mode yet. No message is printed on
> the console.
>
> Do I have to set Barebox for work with different RAM size?
>

One of the first things Barebox does when it start is placing itself
at the end of RAM as well as reserving adjacent areas for stack and
heap. So while you don't strictly have to configure it for different
RAM sizes it _does_ need to know actual RAM size to be able to
calculate various addresses correctly.

To the best of my knowledge there are two ways that knowledge is passed along:

     1) Hardcore that knowledge in entry point code as a part of PBL
     2) Implement additional memory size detection logic

AFAIK all i.MX variants in latest master should fall under second
category, so different RAM sizes should be accounted for.

You might gain some additional insight into the problem if you enable
CONFIG_DEBUG_LL (and route it to appropriate port) in "Debugging" menu
of menuconfig.

Hope this helps.

Regards,
Andrey Smirnov

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

  reply	other threads:[~2016-11-03 22:42 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 [this message]
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
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=CAHQ1cqFuQdm8EykmLh7b589Y6VLw8Vr69_goSw5-oo5mBikJsw@mail.gmail.com \
    --to=andrew.smirnov@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=jlz.3008@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox