FW upgrade err in 33522a - possible 5.03 FW released corrupted

[Zucca]

Tried from 1.12 to 1.14, to 2.09 and to (current 5.03).... same effing error



Kindly ask here for help since KS drop the support to home labs.

[IanB]

Not that it helps, but that error message seems like it might come from .NET. That's a typical .NET message, similar to trying to dereference a null pointer in native code.

It is typically indicative of a bug in the application, since if the program logic is correct it should never happen.

How does the update process work? Do you plug the device into a Windows PC and then run the update utility on the PC? Or does the update run directly on the Agilent device?

Either way, I would look for a log file that may contain more detailed diagnostic information. Such a file is very likely to get created by the update utility. What about the Help menu? Does it give you any clues where to look?

[Someone]

Although Keysight push the update utility there is still the option to put an archive file on a USB and let the instrument do the update locally, less crap to go wrong/be incompatible.

[Zucca]

With this stone age SW



I was able to bring it to 5.02 (hopping from one FW to the next one... it took hours...)

The 5.03 (current) was not recognized anymore by the above SW... IT WAS SAYING FW CORRUPTED!

So I use the current KeysightFirmwareUpdateUtility.exe

- Per LAN from 5.02 to 5.03 I got the first post message again
- Per USB now it is showing "Upgrading frimware. Please do not power down." since 1 hour and the USB LED is not blinking anymore,
Of course the device is not responsive.. it seems stuck.
I leave like this over night...

NO HOPE IT WILL WORK.

What a royal pain in the ass... 

WORST CASE KS RELEASED A CORRUPTED FW?
This is the bad guy, 5.03!
https://www.keysight.com/us/en/lib/software-detail/instrument-firmware-software/33500-series-firmware-1974550.html

[Zucca]

Morning update: still stuck in FW upgrade.

Do I risk to power cycle it?

[Zucca]

Although Keysight push the update utility there is still the option to put an archive file on a USB and let the instrument do the update locally, less crap to go wrong/be incompatible.

Funny enough USB upgrade method was the one who got me stuck in FW upgrade endless loop.

[Zucca]

Not that it helps, but that error message seems like it might come from .NET. That's a typical .NET message, similar to trying to dereference a null pointer in native code.

This is my reaction when I hear .NET



unfortunately they got me this time...

[Zucca]

Title changed.

Do not risk to upgrade a 33500a to 5.03 until I dig further.

WORST CASE KS RELEASED A CORRUPTED FW?
This is the bad guy, 5.03!
https://www.keysight.com/us/en/lib/software-detail/instrument-firmware-software/33500-series-firmware-1974550.html

[nfmax]

My 33522B has been running 5.03-1.19-2.00-58-00 without issue for months. Though I haven’t been using it much

[Zucca]

My 33522B has been running 5.03-1.19-2.00-58-00 without issue for months. Though I haven’t been using it much

Which makes my theory 5.03 is messing with 33522A even stronger.

[Zucca]

Called customer support US:

1)
They did not ask for company credential

2)

You can try to power cycle the device, if it does not boot up anymore you need to ship it to us for repair

 

[Hexley]

Another "B" data point: After seeing your post, I tried an update of my 33521B from 5.02 to 5.03, using version 1.0.31.0 of the Firmware Update Utility (over LAN). Worked fine.

Sorry this does not help you, but might be of interest to "B" owners who see this thread.

Good luck.

[TheSteve]

I have a B model running 5.03 as well, no issues.

I'd power cycle the 33522A - it probably never even started the update. The on screen message is generated by a firmware update command before any updating actually happens.

[Zucca]

TheSteve gets a cold beer, he was right the unit recovered after a power cycle.

Current FW
5.02-1.19-2.00-58-00

Upgrade error via LAN with KS FW update utility:


With the old FW update utility (which worked until the 5.03FW, the above was always failing with the above error)


I get:


back to square one.

Keep you posted.

[Zucca]

Official statement from KS customer support, I told them I will not try with a second PC.

That's a good idea try with a difference pc, but unfortunately if that doesn't work , there is no other fix. You would have to send instrument in for repair to get it updated.

So KS officially does not know what the error "Object reference not set to an instance of an object" means.

 

[IanB]

I take it you have not found a log file?

Also, there are different versions of .NET. If you are not running an up to date version of Windows, there might possibly be a version compatibility issue. But then it seems the update utility should fail to install or run at all.

If you happen, by chance, to be running an older version of Windows like Windows 7, then issues are more likely.

[Zucca]

Thanks IanB.

No no log.

I looked in %temp%, in the .exe directories and in local data.

I found a user.config file in

c:\Users\USER\AppData\Local\Keysight_Technologies\Keysight_Firmware_Update__Url_ebga2x3amjpzllod1hfqzjc4lb1i1d2t\1.0.31.0\user.config

Code: [Select]

<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <configSections>
        <sectionGroup name="userSettings" type="System.Configuration.UserSettingsGroup, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" >
            <section name="FWUpdateUI.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" allowExeDefinition="MachineToLocalUser" requirePermission="false" />
        </sectionGroup>
    </configSections>
    <userSettings>
        <FWUpdateUI.Properties.Settings>
            <setting name="LastFirmwareFilePath" serializeAs="String">
                <value>E:\SHARED\Wood\Z\04_HW\Electronics\Equipment\Agilent_33522A\FW</value>
            </setting>
        </FWUpdateUI.Properties.Settings>
    </userSettings>
</configuration>
I found and tried the console .exe, same errror.

Code: [Select]

Microsoft Windows [Version 10.0.19045.4780]
(c) Microsoft Corporation. All rights reserved.

C:\Program Files (x86)\Keysight\Firmware Update Utility>"Keysight Firmware Update Utility Console.exe"
Invalid arguments.

USAGE:
FWUpdateConsole ["fileLocation"] [connectionAddr] [connectionType] [password]

Parameters:
  "fileLocation"     Location of update file surrounded by quotation marks.
  connectionAddr     IP-address/hostname(SOCKETS) or VISA string/alias.
  connectionType     Type of connection (LAN, USB, or GPIB)
  password           Password for unlocking instrument's cal security for update (optional).


C:\Program Files (x86)\Keysight\Firmware Update Utility>"Keysight Firmware Update Utility Console.exe" "c:\Users\Zuk\Desktop\temp\Agt335xx_rev_05_03.upd" 192.168.10.20 LAN

Keysight Firmware Update Utility
Version 1.0.31
Copyright Keysight Technologies, Inc 2016

Loading the firmware file Agt335xx_rev_05_03.upd
Firmware file loaded successfully

Connecting to the device 192.168.10.20
Successfully connected to instrument: Agilent Technologies 33522A (MY50002971)


The update failed: Update failed: Error while copying files:
Object reference not set to an instance of an object.