mail archive of the barebox mailing list
 help / color / mirror / Atom feed
* BeagleBoard-Xm: memtest return error
@ 2015-06-03 14:08 Валерий Ныров
  2015-06-03 19:42 ` Alexander Aring
  0 siblings, 1 reply; 5+ messages in thread
From: Валерий Ныров @ 2015-06-03 14:08 UTC (permalink / raw)
  To: barebox

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?

Best Regards,
Valeriy Nyrov.

Here is the log:

Board: Texas Instruments beagle
netconsole: registered as netconsole-1
i2c-omap i2c-omap30: bus 0 rev4.4 at 100 kHz
ehci ehci0: USB EHCI 1.00
nand: No NAND device found
gpmc_nand gpmc_nand0: probe failed: No such device or address
omap-hsmmc omap3-hsmmc0: registered as omap3-hsmmc0
mci0: detected SD card version 2.0
mci0: registered disk0
malloc space: 0x85e00000 -> 0x87dfffff (size 32 MiB)
environment load /boot/barebox.env: No such file or directory
Maybe you have to create the partition.
running /env/bin/init...
set parameter: No such device
Failed to add partitions
128k(nand0.xload),256k(nand0.barebox)ro,128k(nand0.bareboxenv),128k(nand0.oftree),4M(nand0.kernel),1200

Hit any key to stop autoboot:  1
barebox@Texas Instruments beagle:/ memtest
Start iteration 1 of 1.
Do memtest with caching enabled.
Testing memory space: 0x80000000 -> 0x85dfffff:
Starting data line test.
Check for address bits stuck high.
Check for address bits stuck low or shorted.
Starting integrity check of physicaly ram.
Filling ram with patterns...
        [#################################################################]
Compare written patterns...
        [#################################################################]
Filling ram with inverted pattern and compare it...
        [#################################################################]
done.

Testing memory space: 0x87e48000 -> 0x87ff3fff:
Starting data line test.
Check for address bits stuck high.
Check for address bits stuck low or shorted.
Starting integrity check of physicaly ram.
Filling ram with patterns...
        [#################################################################]
Compare written patterns...
        [#################################################################]
Filling ram with inverted pattern and compare it...
        [#################################################################]
done.

Testing memory space: 0x88000000 -> 0x9fffffff:
Starting data line test.
Check for address bits stuck high.
FAILURE: Address bit stuck high @ 0x90000000: expected 0xaaaaaaaa,
actual 0x7fffffff.
Memtest failed. Error: -5

barebox@Texas Instruments beagle:/ memset -b 0x90000000 0xaa 4
barebox@Texas Instruments beagle:/ md -b 0x90000000
90000000: aa aa aa aa aa aa aa aa aa aa aa aa 00 00 00 00    ................
90000010: aa aa aa aa 00 00 00 00 00 00 00 00 00 00 00 00

barebox@Texas Instruments beagle:/ memset -b 0x90000000 0x55 4
barebox@Texas Instruments beagle:/ md -b 0x90000000
90000000: 55 55 55 55 aa aa aa aa aa aa aa aa 00 00 00 00    UUUU............
90000010: aa aa aa aa 00 00 00 00 00 00 00 00 00 00 00 00    ................

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: BeagleBoard-Xm: memtest return error
  2015-06-03 14:08 BeagleBoard-Xm: memtest return error Валерий Ныров
@ 2015-06-03 19:42 ` Alexander Aring
  2015-06-05  6:11   ` Valeriy Nyrov
  2015-06-05 11:28   ` Sascha Hauer
  0 siblings, 2 replies; 5+ messages in thread
From: Alexander Aring @ 2015-06-03 19:42 UTC (permalink / raw)
  To: Валерий
	Ныров
  Cc: barebox

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: BeagleBoard-Xm: memtest return error
  2015-06-03 19:42 ` Alexander Aring
@ 2015-06-05  6:11   ` Valeriy Nyrov
  2015-06-05 11:28     ` Sascha Hauer
  2015-06-05 11:28   ` Sascha Hauer
  1 sibling, 1 reply; 5+ messages in thread
From: Valeriy Nyrov @ 2015-06-05  6:11 UTC (permalink / raw)
  To: barebox

Hi Alex,
that is, memset command can not be used?
I have understood correctly - to the test was successful it is necessary to
disable the data cache?

Best Regards,
Valeriy



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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: BeagleBoard-Xm: memtest return error
  2015-06-05  6:11   ` Valeriy Nyrov
@ 2015-06-05 11:28     ` Sascha Hauer
  0 siblings, 0 replies; 5+ messages in thread
From: Sascha Hauer @ 2015-06-05 11:28 UTC (permalink / raw)
  To: Valeriy Nyrov; +Cc: barebox

On Fri, Jun 05, 2015 at 06:11:46AM +0000, Valeriy Nyrov wrote:
> Hi Alex,
> that is, memset command can not be used?
> I have understood correctly - to the test was successful it is necessary to
> disable the data cache?

For testing purposes it should be enough to do some memcpy to fill the
cache with something else.

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: BeagleBoard-Xm: memtest return error
  2015-06-03 19:42 ` Alexander Aring
  2015-06-05  6:11   ` Valeriy Nyrov
@ 2015-06-05 11:28   ` Sascha Hauer
  1 sibling, 0 replies; 5+ messages in thread
From: Sascha Hauer @ 2015-06-05 11:28 UTC (permalink / raw)
  To: Alexander Aring
  Cc: barebox,
	Валерий
	Ныров

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@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2015-06-05 11:32 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-06-03 14:08 BeagleBoard-Xm: memtest return error Валерий Ныров
2015-06-03 19:42 ` Alexander Aring
2015-06-05  6:11   ` Valeriy Nyrov
2015-06-05 11:28     ` Sascha Hauer
2015-06-05 11:28   ` Sascha Hauer

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox