Electronics > Repair
Agilent 34461A corrupted flash
dc101:
I have a Agilent 34461a that's well out of warranty and no longer boots. Thanks to previous threads on this forum I was able to determine it's a result of corrupt/dead flash, although I can't 100% rule out a more serious issue. I suspect this may have resulted from leaving it unplugged for some amount of time. I emailed Keysight and asked them for a copy of the pboot.bin image and nk.bin, but I'm not very optimistic they will send me the files.
Does anyone here have a copy of pboot.bin and nk.bin? Or is anyone who has a 34461a willing to try and dump these files? My 34461a is running U-Boot 2010.03 (Oct 09 2012 - 12:48:30)Agilent P510. I was able to flash nk.bin that I grabbed off the USB thumbdrive for a front panel update, but without pboot.bin there is no kernel to boot nk.bin, and I'm not 100% the nk.bin I flashed is in the correct format.
Boot log:
--- Code: ---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: 2021-03-22 21:08:23.75
Net: No ethernet found.
splash RTC: 2021-03-22 21:08:24.78
Press space to stop autoboot: 0
NAND read: device 0 offset 0x320000, size 0x10000
65536 bytes read: OK
Wrong Image Format for bootm command
ERROR: can't get kernel image!
p510>
--- End code ---
Sure enough if I list the flash images, pboot is definitely gone:
--- Code: ---********************* NOR Flash Images *********************
********************* NAND Flash Images *********************
Image at offset 00000000:
Image Name: XLOADER
Created: 2012-05-16 23:33:58 UTC
Image Type: ARM Linux Firmware (uncompressed)
Data Size: 5370 Bytes = 5.2 KiB
Load Address: d2800b00
Entry Point: d2800b00
Verifying Checksum ... OK
Image at offset 00020000:
Image Name: XLOADER
Created: 2012-05-16 23:33:58 UTC
Image Type: ARM Linux Firmware (uncompressed)
Data Size: 5370 Bytes = 5.2 KiB
Load Address: d2800b00
Entry Point: d2800b00
Verifying Checksum ... OK
Image at offset 00040000:
Image Name: XLOADER
Created: 2012-05-16 23:33:58 UTC
Image Type: ARM Linux Firmware (uncompressed)
Data Size: 5370 Bytes = 5.2 KiB
Load Address: d2800b00
Entry Point: d2800b00
Verifying Checksum ... OK
Image at offset 00060000:
Image Name: XLOADER
Created: 2012-05-16 23:33:58 UTC
Image Type: ARM Linux Firmware (uncompressed)
Data Size: 5370 Bytes = 5.2 KiB
Load Address: d2800b00
Entry Point: d2800b00
Verifying Checksum ... OK
Image at offset 00100000:
Image Name: UBOOT
Created: 2012-10-09 18:59:15 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 237084 Bytes = 231.5 KiB
Load Address: 03f00000
Entry Point: 03f00000
Verifying Checksum ... OK
p510>
--- End code ---
Cheers
-Tim
dc101:
On a whim I grabbed pboot from my 53220a, but unfortunately the units are not as similar as I thought. I was hoping it would at least boot, but it stops shortly after loading.
Keysight has already informed me that I need to send the unit in for repair because there are "no user repair actions available."
--- Code: ---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: 2021-03-22 23:06:53.27
Net: No ethernet found.
splash RTC: 2021-03-22 23:06:54.31
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: 2009-10-22 11:56:02 UTC
Image Type: ARM Linux Kernel Image (gzip compressed)
Data Size: 37189 Bytes = 36.3 KiB
Load Address: 00000000
Entry Point: 00000000
Uncompressing Kernel Image ... OK
Starting kernel ...
Debug serial initialized ........OK
--- End code ---
perieanuo:
Unknown id: 0xffffff. Using ST_M23P40
imho tah means the memory chip is not responding at all
haven't yes seen chips with good memory space and not responding to ID interogation, but who knows, maybe others have seen this
corrupted or defective flash for me means remove memory/test in external programmer/replace or reprogram
i'd guess, the flash is not 'corrupted', is not responding at all
if you cand find the .hex, remove and replace with new programmed flash chip, or maybe your agilent have some sort of firmware update procedure if the flash is empty, i don't know that agilent model
dc101:
I've been wondering this exact thing, is the flash corrupt, did the flash die, is the DDR bad?
I have a BGA63 socket in the mail that I ordered for a different project, so I could buy a new flash chip and reprogram it, but like you said I need to find the hex files to program it with. I believe I can use the nk.bin file from the firmware update, but pboot.bin is proving impossible to find. I may have to eat the cost of buying a new front panel, I believe it's around $US 250.00.
perieanuo:
sometimes a good empty flash can do it, have you tried just replacing that flash? at least, you will see the message changing and maybe update proposed.
(I suspect from "Using ST_M23P40" you can try this type of flash or somethin,g with same size or bigger and same reading/writing algo, if you got one in your spare parts)
plus, it's a simple so8
case, so changing it it's really simple even with some soldering station
Navigation
[0] Message Index
[#] Next page
Go to full version