I'll check my firmware stash once I get some time, but I do remember that newer sensor board DSP firmwares are not compatible with older main firmware. It might be worth trying to boot the unit without the sensor board installed.
I have downloaded firmware updates from the keysight website. I don't know if there is a bootloader or something that the download wouldn't contain which you would need.
Next weekend, I can try to pull the flash. I remember that one of the JLCC package adapter which comes with the TL866 leaves some pins floating, Vdd IIRC. I had to add a few bodge wires when reading a power supply ROM.
I'd say to replace the sram.
....I have downloaded firmware updates from the keysight website. I don't know if there is a bootloader or something that the download wouldn't contain which you would need....
TiN on xdevs has small snake script to split binary, you have to know address where to split.
I'll check my firmware stash once I get some time, but I do remember that newer sensor board DSP firmwares are not compatible with older main firmware. It might be worth trying to boot the unit without the sensor board installed.
if you could pull the flash or have the binary at hand, it would be AWESOME. I really appreciate your help.
....
At this point if you think it is the flash then why not desolder the two in your unit, read them and post the files.
Keysight has a full archive of the various versions so we can take a look and see what/if it matches a downloaded version. Splitting/combining the files shouldn't be a problem with TiN's python script. Maybe we'll find some corrupted bytes or an entire erased sector. It looks like the cal data is also in the flash chips, so it would be ideal to read yours no matter what.
Upon checking the CPU/memory side, there is activity with fairly good looking signal shapes around the CPU and all memory chips and the PAL. CPU is NOT in reset or halt or freeze either. It seems to me that the CPU is stuck at the very beginning of boot sequence (reading from FLASH into its own small on-chip RAM and perhaps performing basic tasks) before reading the whole firmware into the SRAM and running it. It's a hunch and i have no concrete proof for this
So my guess is that the FLASH memories are bad or corrupted (perhaps during a firmware upgrade though GPIB?!)
Before taking out the flash chips did you check if they are addressed at all (CE,OE)? It could be 'just' an address decoder gone bad.
Did you ask on the yahoo HP-Agilent group? Someone there might have a copy of the firmware (I went and took a quick look but didn't see anything more than what is on the Keysight website).
TonyG
yes, I have posted the problem on yahoo HP group. No help...those guys are busy with moving to groups.io and lots of complaining about receiving too many messages, etc...nothing much is going on there right now...
Between vacation, work and my wife's mother passing away I just haven't had time to get to the bench - We have all that behind us now so I'm hoping to get Part 2 of the drive repair done soon.
I see that there was a response this morning with more detail on debugging the issue. For those interested the thread is:
https://groups.yahoo.com/neo/groups/hp_agilent_equipment/conversations/topics/90969