Products > Test Equipment

Agilent DSOX3054A not booting possible NAND corruption HELP! (RESOLVED)

(1/11) > >>

analogRF:
after a couple of years (!) of searching and not being able to buy a 3000A/T model I finally got hold of a defective DSOX3054A which is stuck at boot. After a quick flash of several LEDs, only the REF and MATH LEDs remain on and nothing else.

Attached is what I got on the serial console and it looks to me to have a NAND flash corruption but I am not sure, I hope someone can confirm
I also ran a couple of informational commands after stopping the U-Boot which you can see in the attached file and below

--- Code: ---U-Boot 2010.03 (Jan 26 2011 - 12:37:34)Agilent P500

CPU:   SPEAr600
DRAM:  128 MiB
Flash: 512 KiB
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
SerNum:serial number not programmed
Chip:  BD Board Rev: 4
Net:   smsc
Press space to stop autoboot:  0
## Booting kernel from Legacy Image at f8050000 ...
   Image Name:   PBOOT
   Created:      2011-01-27  11:38:14 UTC
   Image Type:   ARM Linux Kernel Image (gzip compressed)
   Data Size:    36703 Bytes = 35.8 KiB
   Load Address: 00000000
   Entry Point:  00000000
   Uncompressing Kernel Image ... OK

Starting kernel ...


Debug serial initialized ........OK

Microsoft Windows CE Bootloader Common Library Version 1.4 Built Jan 27 2011 02:04:15
Microsoft Windows CE 6.0 Ethernet Bootloader for the Agilent P500 board
Adaptation performed by Agilent Technologies (c) 2008


System ready!
Preparing for download...
 Loading image 1 from memory at 0xD0600000
O
BL_IMAGE_TYPE_BIN

X
XXXXOOOOXOOOOOOOOXOXXOOOOOOOOXOOXOXOOOOXXXOOOOOOOOOXOOOOXOXXOXXOXOOOXOXXXXXXOOXXOOOOOOXOOXXOXXOOOERROR: Checksum failure (expected=0x1217115 

computed=0x1217126)
****** Checksum failure on record 36, ABORT!!! ******

Completed file(s):
-------------------------------------------------------------------------------
[0]: Address=0x80361000  Length=0x12F9870  Name="" Target=RAM
 Loading image 1 failed, trying next one
 Loading image 2 from memory at 0xD1600000

BL_IMAGE_TYPE_UNKNOWN

 Loading image 2 failed, trying next one
 All images failed

Press r to reset




================================================================================================

p500> imls
Legacy Image at F8000000:
   Image Name:   XLOADER
   Created:      2010-09-24  21:30:18 UTC
   Image Type:   ARM Linux Firmware (uncompressed)
   Data Size:    5370 Bytes = 5.2 KiB
   Load Address: d2800b00
   Entry Point:  d2800b00
   Verifying Checksum ... OK
Legacy Image at F8010000:
   Image Name:   UBOOT
   Created:      2011-01-26  19:52:00 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    194572 Bytes = 190 KiB
   Load Address: 03f00000
   Entry Point:  03f00000
   Verifying Checksum ... OK
Legacy Image at F8050000:
   Image Name:   PBOOT
   Created:      2011-01-27  11:38:14 UTC
   Image Type:   ARM Linux Kernel Image (gzip compressed)
   Data Size:    36703 Bytes = 35.8 KiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
p500> nand
nand - NAND sub-system

Usage:
nand info - show available NAND devices
nand device [dev] - show or set current device
nand read - addr off|partition size
nand write - addr off|partition size
    read/write 'size' bytes starting at offset 'off'
    to/from memory address 'addr', skipping bad blocks.
nand erase [clean] [off size] - erase 'size' bytes from
    offset 'off' (entire device if not specified)
nand bad - show bad blocks
nand dump[.oob] off - dump page
nand scrub - really clean NAND erasing bad blocks (UNSAFE)
nand markbad off [...] - mark bad block(s) at offset (UNSAFE)
nand biterr off - make a bit error at offset (UNSAFE)
p500> nand info

Device 0: NAND 128MiB 3,3V 8-bit, sector size 128 KiB
p500> nand bad

Device 0 bad blocks:
p500>

--- End code ---

I measured most or all of the voltages marked on board and they seem to be OK except one VP23V which is always 0V (see attached picture)
Other voltages are OK but some are less close than I thought they should be

The front USB has no power at all unless I stop the U-Boot then it gets 5.54V which seems a bit high!? (see the picture)

that's as far I have been able to go.

I have been/am reading the very very long thread on 2000/3000 and it is really next to impossible to find clear answer in 106 pages  |O

if someone can give me a direction it is highly appreciated.

TheSteve:
Appears to be classic NAND corruption.

nctnico:
How about sending it to Keysight for a free repair?

analogRF:

--- Quote from: nctnico on February 05, 2021, 04:42:39 pm ---How about sending it to Keysight for a free repair?

--- End quote ---

are they still doing that free replacement thing? this is quite an old scope, Agilent branded S/N MY5316xxx

analogRF:

--- Quote from: nctnico on February 05, 2021, 04:42:39 pm ---How about sending it to Keysight for a free repair?

--- End quote ---

I would also like to repair it myself as a good experience.
I dont have a lan card (yet) but is it possible to boot it by uploading the image through the YMODEM method (serial  console)?

is there any way to know what version of FW it has had?

Navigation

[0] Message Index

[#] Next page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod