EEVblog Electronics Community Forum
Electronics => Repair => Topic started by: autorepair78 on January 06, 2023, 12:48:52 pm
-
I have bought faulty 34461A with fired main procesor spear320. After replaced procesor power on and now I see black-white screen Agilent Techologies and nothing more. I have connected putty by rs232 in back of front panel pins connector and I see there is probobly firmware problem. Does anyone could help to repair it?
This is message from console
U-Boot 2010.03 (Oct 09 2012 - 12:48:30)Agilent P510
CPU: SPEAr320
DRAM: 128 MiB
Unknown id: 0xffffff. Using ST_M23P40
Flash: 64 KiB
NAND: INTERNAL ECC 128 MiB
In: serial
Out: serial
Err: serial
SerNum:MY99999999
Chip: AA Board Rev: 4
init RTC: 2001-01-01 00:40:34.33
Net: No ethernet found.
splash RTC: 2001-01-01 00:40:35.36
Press space to stop autoboot: 0
NAND read: device 0 offset 0x320000, size 0x10000
65536 bytes read: OK
## Booting kernel from Legacy Image at 00600000 ...
Image Name: PBOOT
Created: 2012-05-22 16:06:43 UTC
Image Type: ARM Linux Kernel Image (gzip compressed)
Data Size: 38780 Bytes = 37.9 KiB
Load Address: 00000000
Entry Point: 00000000
Uncompressing Kernel Image ... OK
Starting kernel ...
Debug serial initialized ........OK
No RTC on 320
Microsoft Windows CE Bootloader Common Library Version 1.4 Built May 22 2012 09:09:57
Microsoft Windows CE 6.0 Ethernet Bootloader for the Agilent P500 board
Adaptation performed by Agilent Technologies (c) 2008
Reading NAND configuration
fimage (3) is out of range. It must be a decimal integer between 0 and nimages (2)
PHY not found.
Press [ENTER] to launch image stored in flash or [SPACE] to cancel.
Initiating image launch in 0 seconds
System ready!
Preparing for download...
No RTC on 320
Loading image 1 from memory at 0xD0400000
BL_IMAGE_TYPE_UNKNOWN
Loading image 1 failed, trying next one
Loading image 2 from memory at 0xD2200000
BL_IMAGE_TYPE_UNKNOWN
Loading image 2 failed, trying next one
All images failed
Press r to reset
-
NAND read: device 0 offset 0x320000, size 0x10000
65536 bytes read: OK
## Booting kernel from Legacy Image at 00600000 ...
...
Uncompressing Kernel Image ... OK
...
Starting kernel ...
Reading NAND configuration
fimage (3) is out of range. It must be a decimal integer between 0 and nimages (2)
PHY not found.
Press [ENTER] to launch image stored in flash or [SPACE] to cancel.
Initiating image launch in 0 seconds
System ready!
Preparing for download...
No RTC on 320
Loading image 1 from memory at 0xD0400000
BL_IMAGE_TYPE_UNKNOWN
Loading image 1 failed, trying next one
Loading image 2 from memory at 0xD2200000
BL_IMAGE_TYPE_UNKNOWN
Loading image 2 failed, trying next one
All images failed
Press r to reset
Hi autorepair78,
disclaimer I'm no expert in repairing DMMs but based on the above error messages you can see that your DMM tries to boot, successfully loads the kernel and then fails multiple times with the error BL_IMAGE_TYPE_UNKNOWN. This error messages could result from Windows not being able to read the boot logo (the custom Keysight logo). "fimage (3) is out of range. It must be a decimal integer between 0 and nimages (2)" indicates that a wrong value is read and there could have been a single bit-flip in the image header. A possible cause could be that the old, faulty CPU wreaked havoc or maybe the DMM also suffers from faulty flash memory (this seems to be a problem with the 34465As, especially if they haven't been turned on for a while). To solve this, the easiest way is probably to flash the OS image. I'm not sure if this is easily possible with newer Keysight Hardware due to DRM, you will also likely need specialized hardware to flash the OS image. Maybe someone else here has experience with that. In case reflashing the OS image fails, the memory in your meter may be bad and needs replacement as well.