* memtest failed for rk3588
@ 2024-12-06 13:10 Alexander Shiyan
2024-12-06 14:25 ` Sascha Hauer
0 siblings, 1 reply; 6+ messages in thread
From: Alexander Shiyan @ 2024-12-06 13:10 UTC (permalink / raw)
To: Barebox List
Hello all!
When testing a board with a RK3588 CPU, I get a stable crash on memtest.
This is the first sample of the board on this CPU and of course it is possible
that something is really not soldered correctly, but should the
bootloader crash in this case?
barebox 2024.12.0-00352-g41ed6686c3d4-dirty #69 Fri Dec 6 15:45:18 MSK 2024
Board: Diasom DS-RK3588-BTB-EVB
deep-probe: supported due to diasom,ds-rk3588-btb
rockchip-dmc memory-controller.of: Detected memory size: 0x400000000
netconsole: registered as netconsole-1
arm-scmi firmware:scmi.of: SCMI Protocol v2.0 'rockchip:' Firmware version 0x0
psci psci.of: detected version 1.1
fan53555-regulator rk86020: FAN53555 Option[10] Rev[1] Detected!
fan53555-regulator rk86030: FAN53555 Option[10] Rev[1] Detected!
dw_mmc fe2c0000.mmc@fe2c0000.of: registered as mmc1
mmc1: detected SD card version 2.0
mmc1: registered mmc1
rk3568-dwcmshc-sdhci fe2e0000.mmc@fe2e0000.of: registered as mmc0
mmc0: detected MMC card version 5.1
mmc0: registered mmc0.boot0
mmc0: registered mmc0.boot1
mmc0: registered mmc0
fan53555-regulator rk86021: FAN53555 Option[10] Rev[1] Detected!
malloc space: 0xafd00000 -> 0xefcfffff (size 1 GiB)
environment load /dev/env0: No such file or directory
Maybe you have to create the partition.
Hit any to stop autoboot: 3
barebox@Diasom DS-RK3588-BTB-EVB:/ memtest
Start iteration 1 of 1.
Testing memory space: 0x0000000100000000 -> 0x00000003ffffffff:
Starting data line test.
Check for address bits stuck high.
Check for address bits stuck low or shorted.
Starting moving inversions test of RAM:
Fill with address, compare, fill with inverted address, compare again
[##########################################DABT (current EL)
exception (ESR 0x96000010) at 0x00000003fc000200
elr: 00000000efd07064 lr : 00000000efd07058
x0 : 00000002fc000200 x1 : 0000000000000001
x2 : 000000005fffffff x3 : 0000000000000002
x4 : 0000000000000002 x5 : 0000000000000020
x6 : 00000000ffffffd8 x7 : 00000000efff76ae
x8 : 00000000efff79c8 x9 : 0000000000000078
x10: 0000000000000001 x11: 0000000000000011
x12: 0000000000000010 x13: 00000000efdaf076
x14: 0000000000000000 x15: 0000000000000003
x16: 00000000efff73f8 x17: 0000000000000003
x18: 00000000efff7b20 x19: 0000000100000000
x20: 0000000000000001 x21: 0000000000000001
x22: fffffffffffffffe x23: 0000000000000000
x24: 0000000000000001 x25: 0000000000000000
x26: 00000000efd9e5de x27: 00000000efd9e5f1
x28: 0000000000000000 x29: 00000000efff7a60
Call trace:
[<efd07064>] (mem_test_moving_inversions+0xfc/0x244) from [<efd6375c>]
(do_test_one_area+0x74/0x98)
[<efd6375c>] (do_test_one_area+0x74/0x98) from [<efd63808>]
(do_memtest_biggest+0x28/0x3c)
[<efd63808>] (do_memtest_biggest+0x28/0x3c) from [<efd63a18>]
(do_memtest+0x1fc/0x218)
[<efd63a18>] (do_memtest+0x1fc/0x218) from [<efd073cc>]
(execute_command+0x44/0x8c)
[<efd073cc>] (execute_command+0x44/0x8c) from [<efd042c0>]
(execute_binfmt+0x68/0xa0)
[<efd042c0>] (execute_binfmt+0x68/0xa0) from [<efd11430>]
(run_list_real+0x8cc/0x978)
[<efd11430>] (run_list_real+0x8cc/0x978) from [<efd109b8>]
(parse_stream_outer+0x140/0x1ec)
[<efd109b8>] (parse_stream_outer+0x140/0x1ec) from [<efd11734>]
(run_shell+0x64/0xac)
[<efd11734>] (run_shell+0x64/0xac) from [<efd019f4>] (run_init+0x114/0x258)
[<efd019f4>] (run_init+0x114/0x258) from [<efd01b88>] (start_barebox+0x50/0x8c)
[<efd01b88>] (start_barebox+0x50/0x8c) from [<efd8a6b8>]
(psci_driver_register+0x0/0x1c)
[<efd8a6b8>] (psci_driver_register+0x0/0x1c) from [<efd0000c>]
(__bare_init_start+0x0/0x14)
[<efd0000c>] (__bare_init_start+0x0/0x14) from [<00b01bc8>] (0xb01bc8)
[<00b01bc8>] (0xb01bc8) from [<00b013ac>] (0xb013ac)
panic: unhandled exception
### ERROR ### Please RESET the board ###
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: memtest failed for rk3588 2024-12-06 13:10 memtest failed for rk3588 Alexander Shiyan @ 2024-12-06 14:25 ` Sascha Hauer 2024-12-10 11:29 ` Alexander Shiyan 0 siblings, 1 reply; 6+ messages in thread From: Sascha Hauer @ 2024-12-06 14:25 UTC (permalink / raw) To: Alexander Shiyan; +Cc: Barebox List Hi Alexander, On Fri, Dec 06, 2024 at 04:10:42PM +0300, Alexander Shiyan wrote: > Hello all! > > When testing a board with a RK3588 CPU, I get a stable crash on memtest. > This is the first sample of the board on this CPU and of course it is possible > that something is really not soldered correctly, but should the > bootloader crash in this case? > > > Testing memory space: 0x0000000100000000 -> 0x00000003ffffffff: > Starting data line test. > Check for address bits stuck high. > Check for address bits stuck low or shorted. > Starting moving inversions test of RAM: > Fill with address, compare, fill with inverted address, compare again > [##########################################DABT (current EL) > exception (ESR 0x96000010) at 0x00000003fc000200 Can you access 0x3fc000200 using md/mw? Sascha -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: memtest failed for rk3588 2024-12-06 14:25 ` Sascha Hauer @ 2024-12-10 11:29 ` Alexander Shiyan 2024-12-10 11:47 ` Sascha Hauer 0 siblings, 1 reply; 6+ messages in thread From: Alexander Shiyan @ 2024-12-10 11:29 UTC (permalink / raw) To: Sascha Hauer; +Cc: Barebox List Hello. The dump does not cause a crash, but the output is very strange: barebox@Diasom DS-RK3588-BTB-EVB:/ md 0x3fc000100 3fc000100: 940033fd b0000060 39477ea1 91274c00 .3..`....~G9.L'. 3fc000110: 17ffffe2 91404001 b9428020 37f80180 .....@@. .B....7 3fc000120: b9428020 32010000 b9028020 52800020 .B....2 ... ..R 3fc000130: b9420822 32000042 b9020822 b9420822 ".B.B..2"...".B. 3fc000140: 521c0042 b9020822 d65f03c0 52800000 B..R"....._....R 3fc000150: 17fffff8 91404000 34000081 b9428001 .....@@....4..B. 3fc000160: 12007821 b9028001 b9420801 121f7821 !x........B.!x.. 3fc000170: b9020801 b9420801 521c0021 b9020801 ......B.!..R.... 3fc000180: d65f03c0 d37b7c21 71000c5f 8b010000 .._.!|{._..q.... 3fc000190: 528aaaa1 72bdddc1 f9400400 b900ac01 ...R...r..@..... 3fc0001a0: 529dddc1 72aaaaa1 b90a7c01 b94a2401 ...R...r.|...$J. 3fc0001b0: 321c0021 b90a2401 b94a2403 12147463 !..2.$...$J.ct.. 3fc0001c0: 54000300 52808001 1ac22022 2a030042 ...T...R" ..B..* 3fc0001d0: b90a2402 b94a2401 32000021 b90a2401 .$...$J.!..2.$.. 3fc0001e0: b94a2401 360fffe1 b94a2401 121f7821 .$J....6.$J.!x.. 3fc0001f0: b90a2401 b94a2401 12147421 b90a2401 .$...$J.!t...$.. barebox@Diasom DS-RK3588-BTB-EVB:/ md 0x3fc000200 3fc000200: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ 3fc000210: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ 3fc000220: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ 3fc000230: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ 3fc000240: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ 3fc000250: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ 3fc000260: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ 3fc000270: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ 3fc000280: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ 3fc000290: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ 3fc0002a0: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ 3fc0002b0: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ 3fc0002c0: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ 3fc0002d0: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ 3fc0002e0: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ 3fc0002f0: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ barebox@Diasom DS-RK3588-BTB-EVB:/ пт, 6 дек. 2024 г. в 17:25, Sascha Hauer <s.hauer@pengutronix.de>: > > Hi Alexander, > > On Fri, Dec 06, 2024 at 04:10:42PM +0300, Alexander Shiyan wrote: > > Hello all! > > > > When testing a board with a RK3588 CPU, I get a stable crash on memtest. > > This is the first sample of the board on this CPU and of course it is possible > > that something is really not soldered correctly, but should the > > bootloader crash in this case? > > > > > > Testing memory space: 0x0000000100000000 -> 0x00000003ffffffff: > > Starting data line test. > > Check for address bits stuck high. > > Check for address bits stuck low or shorted. > > Starting moving inversions test of RAM: > > Fill with address, compare, fill with inverted address, compare again > > [##########################################DABT (current EL) > > exception (ESR 0x96000010) at 0x00000003fc000200 > > Can you access 0x3fc000200 using md/mw? > > Sascha > > -- > Pengutronix e.K. | | > Steuerwalder Str. 21 | http://www.pengutronix.de/ | > 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | > Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: memtest failed for rk3588 2024-12-10 11:29 ` Alexander Shiyan @ 2024-12-10 11:47 ` Sascha Hauer 2024-12-11 15:52 ` Alexander Shiyan 0 siblings, 1 reply; 6+ messages in thread From: Sascha Hauer @ 2024-12-10 11:47 UTC (permalink / raw) To: Alexander Shiyan; +Cc: Barebox List On Tue, Dec 10, 2024 at 02:29:59PM +0300, Alexander Shiyan wrote: > Hello. > > The dump does not cause a crash, but the output is very strange: > > barebox@Diasom DS-RK3588-BTB-EVB:/ md 0x3fc000100 > 3fc000100: 940033fd b0000060 39477ea1 91274c00 .3..`....~G9.L'. > 3fc000110: 17ffffe2 91404001 b9428020 37f80180 .....@@. .B....7 > 3fc000120: b9428020 32010000 b9028020 52800020 .B....2 ... ..R > 3fc000130: b9420822 32000042 b9020822 b9420822 ".B.B..2"...".B. > 3fc000140: 521c0042 b9020822 d65f03c0 52800000 B..R"....._....R > 3fc000150: 17fffff8 91404000 34000081 b9428001 .....@@....4..B. > 3fc000160: 12007821 b9028001 b9420801 121f7821 !x........B.!x.. > 3fc000170: b9020801 b9420801 521c0021 b9020801 ......B.!..R.... > 3fc000180: d65f03c0 d37b7c21 71000c5f 8b010000 .._.!|{._..q.... > 3fc000190: 528aaaa1 72bdddc1 f9400400 b900ac01 ...R...r..@..... > 3fc0001a0: 529dddc1 72aaaaa1 b90a7c01 b94a2401 ...R...r.|...$J. > 3fc0001b0: 321c0021 b90a2401 b94a2403 12147463 !..2.$...$J.ct.. > 3fc0001c0: 54000300 52808001 1ac22022 2a030042 ...T...R" ..B..* > 3fc0001d0: b90a2402 b94a2401 32000021 b90a2401 .$...$J.!..2.$.. > 3fc0001e0: b94a2401 360fffe1 b94a2401 121f7821 .$J....6.$J.!x.. > 3fc0001f0: b90a2401 b94a2401 12147421 b90a2401 .$...$J.!t...$.. > barebox@Diasom DS-RK3588-BTB-EVB:/ md 0x3fc000200 > 3fc000200: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > 3fc000210: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > 3fc000220: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > 3fc000230: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > 3fc000240: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > 3fc000250: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > 3fc000260: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > 3fc000270: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > 3fc000280: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > 3fc000290: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > 3fc0002a0: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > 3fc0002b0: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > 3fc0002c0: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > 3fc0002d0: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > 3fc0002e0: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > 3fc0002f0: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ See: | commit d8a6e1c2662aad2f5d9b4050a276b8e6b9fbb3b1 | Author: Jan Luebbe <jlu@pengutronix.de> | Date: Sun Aug 3 17:51:38 2014 +0200 | | ARM/mem: handle data aborts gracefully for md | | Sometimes memory ranges contain inaccessible registers which trigger a | data abort when accessed. To handle this gracefully, we extend the data | abort exception handler to ignore the exception when configured to do | so. | | This allows detecting inaccessible memory from the md command. It will | show XX for unreadable bytes instead. I don't know why you get a data abort here. The answer is probably somewhere in the DMC section of the RK3588 reference manual. Sascha -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: memtest failed for rk3588 2024-12-10 11:47 ` Sascha Hauer @ 2024-12-11 15:52 ` Alexander Shiyan 2024-12-13 12:15 ` Alexander Shiyan 0 siblings, 1 reply; 6+ messages in thread From: Alexander Shiyan @ 2024-12-11 15:52 UTC (permalink / raw) To: Sascha Hauer; +Cc: Barebox List So far I have isolated several memory pages using reserved-memory: <0x3 0xfc000000 0x0 0x500000> and <0x3 0xfff00000 0x0 0x100000> So it looks like there is a memory chip bug. barebox@Diasom DS-RK3588-BTB-EVB:/ memtest -t Start iteration 1 of 1. Testing memory space: 0x0000000000a00000 -> 0x00000000afcfffff: Starting data line test. Check for address bits stuck high. Check for address bits stuck low or shorted. Starting moving inversions test of RAM: Fill with address, compare, fill with inverted address, compare again [################################################################] done. Testing memory space: 0x0000000100000000 -> 0x00000003fbffffff: Starting data line test. Check for address bits stuck high. Check for address bits stuck low or shorted. Starting moving inversions test of RAM: Fill with address, compare, fill with inverted address, compare again [################################################################] done. Testing memory space: 0x00000003fc500000 -> 0x00000003ffefffff: Starting data line test. Check for address bits stuck high. Check for address bits stuck low or shorted. Starting moving inversions test of RAM: Fill with address, compare, fill with inverted address, compare again [################################################################] done. Memtest successful. вт, 10 дек. 2024 г. в 14:47, Sascha Hauer <s.hauer@pengutronix.de>: > > On Tue, Dec 10, 2024 at 02:29:59PM +0300, Alexander Shiyan wrote: > > Hello. > > > > The dump does not cause a crash, but the output is very strange: > > > > barebox@Diasom DS-RK3588-BTB-EVB:/ md 0x3fc000100 > > 3fc000100: 940033fd b0000060 39477ea1 91274c00 .3..`....~G9.L'. > > 3fc000110: 17ffffe2 91404001 b9428020 37f80180 .....@@. .B....7 > > 3fc000120: b9428020 32010000 b9028020 52800020 .B....2 ... ..R > > 3fc000130: b9420822 32000042 b9020822 b9420822 ".B.B..2"...".B. > > 3fc000140: 521c0042 b9020822 d65f03c0 52800000 B..R"....._....R > > 3fc000150: 17fffff8 91404000 34000081 b9428001 .....@@....4..B. > > 3fc000160: 12007821 b9028001 b9420801 121f7821 !x........B.!x.. > > 3fc000170: b9020801 b9420801 521c0021 b9020801 ......B.!..R.... > > 3fc000180: d65f03c0 d37b7c21 71000c5f 8b010000 .._.!|{._..q.... > > 3fc000190: 528aaaa1 72bdddc1 f9400400 b900ac01 ...R...r..@..... > > 3fc0001a0: 529dddc1 72aaaaa1 b90a7c01 b94a2401 ...R...r.|...$J. > > 3fc0001b0: 321c0021 b90a2401 b94a2403 12147463 !..2.$...$J.ct.. > > 3fc0001c0: 54000300 52808001 1ac22022 2a030042 ...T...R" ..B..* > > 3fc0001d0: b90a2402 b94a2401 32000021 b90a2401 .$...$J.!..2.$.. > > 3fc0001e0: b94a2401 360fffe1 b94a2401 121f7821 .$J....6.$J.!x.. > > 3fc0001f0: b90a2401 b94a2401 12147421 b90a2401 .$...$J.!t...$.. > > barebox@Diasom DS-RK3588-BTB-EVB:/ md 0x3fc000200 > > 3fc000200: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > > 3fc000210: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > > 3fc000220: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > > 3fc000230: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > > 3fc000240: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > > 3fc000250: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > > 3fc000260: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > > 3fc000270: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > > 3fc000280: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > > 3fc000290: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > > 3fc0002a0: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > > 3fc0002b0: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > > 3fc0002c0: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > > 3fc0002d0: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > > 3fc0002e0: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > > 3fc0002f0: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > > See: > > | commit d8a6e1c2662aad2f5d9b4050a276b8e6b9fbb3b1 > | Author: Jan Luebbe <jlu@pengutronix.de> > | Date: Sun Aug 3 17:51:38 2014 +0200 > | > | ARM/mem: handle data aborts gracefully for md > | > | Sometimes memory ranges contain inaccessible registers which trigger a > | data abort when accessed. To handle this gracefully, we extend the data > | abort exception handler to ignore the exception when configured to do > | so. > | > | This allows detecting inaccessible memory from the md command. It will > | show XX for unreadable bytes instead. > > I don't know why you get a data abort here. The answer is probably > somewhere in the DMC section of the RK3588 reference manual. > > Sascha > > -- > Pengutronix e.K. | | > Steuerwalder Str. 21 | http://www.pengutronix.de/ | > 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | > Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: memtest failed for rk3588 2024-12-11 15:52 ` Alexander Shiyan @ 2024-12-13 12:15 ` Alexander Shiyan 0 siblings, 0 replies; 6+ messages in thread From: Alexander Shiyan @ 2024-12-13 12:15 UTC (permalink / raw) To: Sascha Hauer; +Cc: Barebox List Hello All! Update: I have start the second board and got similar errors. Analysis of the code (at the 0x3fc000000), before the memory area that is not available (at 0x3fc000200) is very similar to the code from sdram-init.bin. Maybe we are missing a description of some necessary memory area? Thanks! ср, 11 дек. 2024 г. в 18:52, Alexander Shiyan <eagle.alexander923@gmail.com>: > > So far I have isolated several memory pages using reserved-memory: > <0x3 0xfc000000 0x0 0x500000> > and > <0x3 0xfff00000 0x0 0x100000> > So it looks like there is a memory chip bug. > > barebox@Diasom DS-RK3588-BTB-EVB:/ memtest -t > Start iteration 1 of 1. > Testing memory space: 0x0000000000a00000 -> 0x00000000afcfffff: > Starting data line test. > Check for address bits stuck high. > Check for address bits stuck low or shorted. > Starting moving inversions test of RAM: > Fill with address, compare, fill with inverted address, compare again > [################################################################] > done. > > Testing memory space: 0x0000000100000000 -> 0x00000003fbffffff: > Starting data line test. > Check for address bits stuck high. > Check for address bits stuck low or shorted. > Starting moving inversions test of RAM: > Fill with address, compare, fill with inverted address, compare again > [################################################################] > done. > > Testing memory space: 0x00000003fc500000 -> 0x00000003ffefffff: > Starting data line test. > Check for address bits stuck high. > Check for address bits stuck low or shorted. > Starting moving inversions test of RAM: > Fill with address, compare, fill with inverted address, compare again > [################################################################] > done. > > Memtest successful. > > вт, 10 дек. 2024 г. в 14:47, Sascha Hauer <s.hauer@pengutronix.de>: > > > > On Tue, Dec 10, 2024 at 02:29:59PM +0300, Alexander Shiyan wrote: > > > Hello. > > > > > > The dump does not cause a crash, but the output is very strange: > > > > > > barebox@Diasom DS-RK3588-BTB-EVB:/ md 0x3fc000100 > > > 3fc000100: 940033fd b0000060 39477ea1 91274c00 .3..`....~G9.L'. > > > 3fc000110: 17ffffe2 91404001 b9428020 37f80180 .....@@. .B....7 > > > 3fc000120: b9428020 32010000 b9028020 52800020 .B....2 ... ..R > > > 3fc000130: b9420822 32000042 b9020822 b9420822 ".B.B..2"...".B. > > > 3fc000140: 521c0042 b9020822 d65f03c0 52800000 B..R"....._....R > > > 3fc000150: 17fffff8 91404000 34000081 b9428001 .....@@....4..B. > > > 3fc000160: 12007821 b9028001 b9420801 121f7821 !x........B.!x.. > > > 3fc000170: b9020801 b9420801 521c0021 b9020801 ......B.!..R.... > > > 3fc000180: d65f03c0 d37b7c21 71000c5f 8b010000 .._.!|{._..q.... > > > 3fc000190: 528aaaa1 72bdddc1 f9400400 b900ac01 ...R...r..@..... > > > 3fc0001a0: 529dddc1 72aaaaa1 b90a7c01 b94a2401 ...R...r.|...$J. > > > 3fc0001b0: 321c0021 b90a2401 b94a2403 12147463 !..2.$...$J.ct.. > > > 3fc0001c0: 54000300 52808001 1ac22022 2a030042 ...T...R" ..B..* > > > 3fc0001d0: b90a2402 b94a2401 32000021 b90a2401 .$...$J.!..2.$.. > > > 3fc0001e0: b94a2401 360fffe1 b94a2401 121f7821 .$J....6.$J.!x.. > > > 3fc0001f0: b90a2401 b94a2401 12147421 b90a2401 .$...$J.!t...$.. > > > barebox@Diasom DS-RK3588-BTB-EVB:/ md 0x3fc000200 > > > 3fc000200: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > > > 3fc000210: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > > > 3fc000220: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > > > 3fc000230: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > > > 3fc000240: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > > > 3fc000250: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > > > 3fc000260: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > > > 3fc000270: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > > > 3fc000280: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > > > 3fc000290: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > > > 3fc0002a0: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > > > 3fc0002b0: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > > > 3fc0002c0: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > > > 3fc0002d0: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > > > 3fc0002e0: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > > > 3fc0002f0: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx ................ > > > > See: > > > > | commit d8a6e1c2662aad2f5d9b4050a276b8e6b9fbb3b1 > > | Author: Jan Luebbe <jlu@pengutronix.de> > > | Date: Sun Aug 3 17:51:38 2014 +0200 > > | > > | ARM/mem: handle data aborts gracefully for md > > | > > | Sometimes memory ranges contain inaccessible registers which trigger a > > | data abort when accessed. To handle this gracefully, we extend the data > > | abort exception handler to ignore the exception when configured to do > > | so. > > | > > | This allows detecting inaccessible memory from the md command. It will > > | show XX for unreadable bytes instead. > > > > I don't know why you get a data abort here. The answer is probably > > somewhere in the DMC section of the RK3588 reference manual. > > > > Sascha > > > > -- > > Pengutronix e.K. | | > > Steuerwalder Str. 21 | http://www.pengutronix.de/ | > > 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | > > Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2024-12-13 12:16 UTC | newest] Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2024-12-06 13:10 memtest failed for rk3588 Alexander Shiyan 2024-12-06 14:25 ` Sascha Hauer 2024-12-10 11:29 ` Alexander Shiyan 2024-12-10 11:47 ` Sascha Hauer 2024-12-11 15:52 ` Alexander Shiyan 2024-12-13 12:15 ` Alexander Shiyan
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox