Agilent 34461A corrupted flash

[voltsandjolts]

This probably isn't the fault you are seeing but...the P89LPC932A1FDH is an 8051 microcontroller which needs firmware to operate. Knowing Keysight, it's probably locked, making it impossible to read the firmware from a working device. Oh, wait...didn't glitching the reset line on nxp mcu's allow full debug access, maybe that was arm mcu's...hmm maybe 

Note also, the NAND must have a version of firmware that matches the mainboard logic, IIUC. There was something about not being able to upgrade from 1.x to 3.x, you had to go to 2.17 first - maybe it upgrades the mainboard firmware or something? Ah, here it is;

https://www.keysight.com/gb/en/lib/software-detail/instrument-firmware-software/34460a34461a34465a34470a-firmware-2367633.html

NOTICE: Upgrading the 34460A and 34461A with firmware revision 1.xx to revision 3.0 or greater
34460A and 34461A DMMs with firmware revision 1.08, 1.09, or 1.10 currently installed must first be upgraded to revision 2.17 (see the ‘Previous Versions’ tab), and then upgraded to revision 3.0 or greater. Upgrades to 3.0 or greater (from 1.xx) cannot be done directly. If attempted, the DMM can be recovered by updating the firmware (to 2.17) from the front panel USB port. Select ‘Front Panel’ on the Firmware Update Utility to create the appropriate folder on a USB thumb drive.

Also;
https://docs.keysight.com/kkbopen/follow-support-instructions-to-restore-the-firmware-displayed-on-the-34461a-dmm-after-firmware-update-what-to-do-580260380.html

I'm unsure why matching versions matters - can someone confirm?

[imett]

Here is the pinout on the connector labeled J102.

Code: [Select]

         0        0 GND
   3.3V  0        0 GND
   TMS   0        0 GND
   TCK   0        0 GND
   TDO   0        0 3.3V
   TDI   0        0 TRST
   3.3V  0        0 GND

Great! Thanks. I only have a Segger J-Link. Not sure if it is compatible with Spear320. I doubt that but I will certainly check

How could a memory dump help?

Please could you confirm the J102 pinout? in my board (34460-26502) the TRST is connectect directly to 3v3 (from the DC/DC buck converter) and the 3V3 in the pinout have in series a resistance..
Other things in the second row from the top (in the proposed J102 pinout is 3v3--- GND) in the pcb there is  a label "FUSB" what does it means?
regards matteo

[voltsandjolts]

in the pcb there is  a label "FUSB" what does it means?

This is a total guess:
The SPEAr mcu has several boot modes selected by pin states, one of them is boot from USB. FUSB could be connected to boot state pins B1 and B2 and mean "Force USB", as-in force USB boot. If this is the case, FUSB pin would likely be pulled high through a 1K or so. If pulled low, with the rear panel USB is connected to a host computer, you should see a USB device "0483:3801 STMicroelectronics". See RM0082 section 38 for details on USB boot.

[lzcubchgg]

My 34461A is broken, showing that it cannot measure any values, including current, voltage, and resistance. The automatic detection has passed. I want to try repairing it. Where should I check? I really need help.

[testpoint1]

This probably isn't the fault you are seeing but...the P89LPC932A1FDH is an 8051 microcontroller which needs firmware to operate. Knowing Keysight, it's probably locked, making it impossible to read the firmware from a working device. Oh, wait...didn't glitching the reset line on nxp mcu's allow full debug access, maybe that was arm mcu's...hmm maybe 

Note also, the NAND must have a version of firmware that matches the mainboard logic, IIUC. There was something about not being able to upgrade from 1.x to 3.x, you had to go to 2.17 first - maybe it upgrades the mainboard firmware or something? Ah, here it is;

https://www.keysight.com/gb/en/lib/software-detail/instrument-firmware-software/34460a34461a34465a34470a-firmware-2367633.html

NOTICE: Upgrading the 34460A and 34461A with firmware revision 1.xx to revision 3.0 or greater
34460A and 34461A DMMs with firmware revision 1.08, 1.09, or 1.10 currently installed must first be upgraded to revision 2.17 (see the ‘Previous Versions’ tab), and then upgraded to revision 3.0 or greater. Upgrades to 3.0 or greater (from 1.xx) cannot be done directly. If attempted, the DMM can be recovered by updating the firmware (to 2.17) from the front panel USB port. Select ‘Front Panel’ on the Firmware Update Utility to create the appropriate folder on a USB thumb drive.

Also;
https://docs.keysight.com/kkbopen/follow-support-instructions-to-restore-the-firmware-displayed-on-the-34461a-dmm-after-firmware-update-what-to-do-580260380.html

I'm unsure why matching versions matters - can someone confirm?

I also think the chip "P89LPC932A1FDH" need to be programmed, but when I replaced it, the board can boot, just boot to that screen, then I try to replace the NAND and ARM, same phenomenon, give up; then I bought a white screen spare part board, replace the ARM CPU, easy to fix it.

[lzcubchgg]

white screen spare board from eBay?
URL? thank...