On Wed, Jun 03, 2015 at 09:42:05PM +0200, Alexander Aring wrote:
> 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.
How about a command to flush caches instead?
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@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/barebox
