Products > Test Equipment
HP / Agilent 34401A hidden menu
<< < (10/36) > >>
giacomo:

--- Quote from: syzygy on April 30, 2021, 02:25:42 am ---excuse my ignorance - is there a logfile or equivalent that describes the features, or even dates, of the revisions?
my 34401A is Rev 08-05-02 - I don't see that f/w listed anywhere?

--- End quote ---

Take a look at the redme.txt file ;)

https://xdevs.com/doc/HP_Agilent_Keysight/34401A/fw/

I believe they have summarized the information available from the various manuals

"The EEPROM structure looks the same from 07-05-02 to 11-05-02, so no calibration seems to be necessary when upgrading FW from 07-05-02 to 11-05-02."

You can upgrade if you want
syzygy:
Thanks - I just read the txt file - but although it says I can upgrade, I don't see any info on what an 'upgrade' changes?  The list at the top focuses on the physical things - color of buttons, banana jacks, board S/N, etc. - None of that can be changed by 'upgrading' to 10-05-02, or 11-05-02, etc.?

I'm lost as to how the f/w revs differ, and also my rev (08-05-02) never seems to be listed?

Thanks
coromonadalix:
the upgrade problem is ;  the mcu is under the vfd display,  you have to put a new ic there ???

I could be wrong  since i always mistake the display  fw and the main fw  version
Hydron:
Thought I'd update this somewhat dormant thread with a little more info.

Background is that I recently got a 34401a in decent condition/calibration (factory cal from 2007, but a few spot checks still look good), and the hidden menu looked like a nice thing to have, plus I wanted a backup of my EEPROM anyway, so I had a play:

- On boot the meter reads the first 211 16-bit words (up to word address 0xD2) of the EEPROM in order (looks like the rest is just blank and never used, so can be ignored)
- This is a nice and easy way to get a backup using a scope or LA without any EEPROM flash tools. Was a lot easier than the last time I did this with a 16-bit parallel EEPROM in a Keithley 236!
- Needs a bit of care with bus decode setup - it's not normal SPI, though my scope (RTB2k) was happy when I set it up as a 27-bit (!!) SPI bus and the correct polarity of chip select, clock (appears to be opposite for data in vs out) etc. Only the last 2 bytes of data output on each read will be valid (and the first ~10 bits will depend on the 100k pullup and your probe impedance and threshold, as it's Hi-Z for that period)

Once I had my backup, I had a bit of play with POKE commands, as per my rough notes (attached). Note that addresses listed in them are word addresses in hex, I was too lazy to append 0x most of the time.
Unfortunately I didn't have much luck finding anything useful, other than if you hate someone you should send DIAG:POKE 0,0,0 to their meter.

I then needed to restore my original backup, so I first had a crack programming the 34401a-save-state-menu.BIN previously posted into my EEPROM. Sadly my meter (on 11-05-02) didn't like this at all, throwing a number of 74x errors on boot, and no new menus appeared.

My original EEPROM dump works fine when programmed back into my meter, so I'm not sure what is the issue is with dimmog's .BIN given the previously reported success swapping the EEPROM (and activated hidden menu) into a 10-05-02 meter. Not a lot more that I think I can do now, though I'm open to suggestions while my meter is still opened up on the bench :(
tv84:
Interesting theme...  ::)

I will have a peek to see if I can add something to this quest.

@Hydron, can you share your original dump? Your checksums offsets should be dump-dependent.


Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod