mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: 'Sascha Hauer' <s.hauer@pengutronix.de>
To: duhuanpeng <548708880@qq.com>
Cc: barebox@lists.infradead.org
Subject: Re: 答复: freescale-mx28-evk run from ram
Date: Fri, 2 Mar 2018 11:15:05 +0100	[thread overview]
Message-ID: <20180302101505.iawtfiddffoswajt@pengutronix.de> (raw)
In-Reply-To: <000001d3b205$12bea160$383be420$@qq.com>

On Fri, Mar 02, 2018 at 05:01:37PM +0800, duhuanpeng wrote:
> > I assume you use freescale-mx28-evk_defconfig, right?
> Yes.
> 
> Which image do you start? It seems you are trying to start barebox.bin.
> > barebox.bin and barebox-freescale-mx28evk-2nd.img
> It should be images/barebox-freescale-mx28evk-2nd.img instead.
> 
> The image should be linked to 0x0, that is right. The code is position
> independent though and the full barebox relocates itself to the end of the
> available SDRAM automatically. TEXT_BASE is not relevant here.
> The start symbol is still 0x00000000 even I change TEXT_BASE in menuconfig.
> my board have 64MiB ram. Modified board. 
> Very cheap one, just 33?. :D
> EasyARM-i.MX283A

You are running on a board which actually is no mx28-evk, so it's no
wonder it doesn't work. Please mention that next time, because that
changes the question from "What is broken with the mx28-evk" to "What is
different on your board". This is a very important detail to answer
questions.

Anyway, you say your board only has 64MiB of RAM, so you must at least
change:

ENTRY_FUNCTION(start_barebox_freescale_mx28evk, r0, r1, r2)
{
        barebox_arm_entry(IMX_MEMORY_BASE, SZ_128M, NULL);
}

to SZ_64M. Other differences might include the pinmux and the UART port
number which is used for console output.

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

  parent reply	other threads:[~2018-03-02 10:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-01 16:30 duhuanpeng
2018-03-02  7:36 ` Sascha Hauer
2018-03-02  9:53   ` 答复: " duhuanpeng
     [not found]   ` <000001d3b205$12bea160$383be420$@qq.com>
2018-03-02 10:15     ` 'Sascha Hauer' [this message]
2018-03-02 10:55       ` 答复: " duhuanpeng
2018-03-02 10:56       ` duhuanpeng

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=20180302101505.iawtfiddffoswajt@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=548708880@qq.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