From: Alexander Aring <alex.aring@gmail.com>
To: "Валерий Ныров" <nvg.dev@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: BeagleBoard-Xm: memtest return error
Date: Wed, 3 Jun 2015 21:42:05 +0200 [thread overview]
Message-ID: <20150603194202.GA4802@omega> (raw)
In-Reply-To: <CAKOK1G0iK=kZJPHGV6mtCbwdNpwdZOXEfnCTeozC+8Nkehxe1A@mail.gmail.com>
Hi,
On Wed, Jun 03, 2015 at 05:08:31PM +0300, Валерий Ныров wrote:
> Hello everyone! I am a newbie and trying to run the barebox on
> BeagleBoard-Xm rev.C with 512MB DDR on board.
>
> To support 512MB I did the following:
>
> 1) file: arm/boards/beagle/board.c, func: beagle_mem_init(), change line 85:
>
> beagle_mem_init(void)
> {
> //omap_add_ram0(SZ_128M);
> omap_add_ram0(SZ_512M);
> }
>
> 2) file: arm/boards/beagle/lowlevel.c, func: sdrc_init(), change line 127:
>
> //writel(0x02584099, OMAP3_SDRC_REG(MCFG_0));
> writel(0x02590099, OMAP3_SDRC_REG(MCFG_0)); // to add 512MB support on CS0
>
> Then launch barebox and send command - memtest, which return error:
> "FAILURE: Address bit stuck high @ 0x90000000: expected 0xaaaaaaaa,
> actual 0x7fffffff",
> but commands "memset" writes data to the address 0x90000000 correct,
> what I did not so?
>
if memtest failed then the caching will be enabled again. This means I
would not trust the memset and memory display command here.
Maybe you could add some memset argument for disable/enable the caching
on some page (which is memory address space) which you want to write and
read. Just for debugging cases.
Don't know if Sascha likes this idea.
- Alex
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2015-06-03 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 14:08 Валерий Ныров
2015-06-03 19:42 ` Alexander Aring [this message]
2015-06-05 6:11 ` Valeriy Nyrov
2015-06-05 11:28 ` Sascha Hauer
2015-06-05 11:28 ` 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=20150603194202.GA4802@omega \
--to=alex.aring@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=nvg.dev@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