Products > Test Equipment
E4406A -- failed firmware update
(1/4) > >>
n8ur:
Hi --

I was attempting to update my E4406A from an earlier firmware version and the process failed.  I think it was due to the firewall on the Windows XP virtual machine I was using.  After the update, the system goes through the entire boot process and brings up the X windows background then stops with:

Exec: load error: 8.  Process killed.
/users/arcturus/.xinitrc: 68 killed
Hostname is VSA
Firmware Exit, cycle power

The OS seems to be OK because it gets as far as the arcturus login before exiting.

I got my hands on an actual, physical WinXP machine and tried the manual update process per the instructions using a hub between the two devices.  I can't complete that because the SEA command returns only:

Path Number              Device Path
P0                             FLASH

So there is no LAN path to boot to.

The "boot information" screen shows primary boot path as "255.0" and alternate boot path as "SESCSI .6.0".  The IO information screen shows the LAN device is present.  The machine address info shows what seems to be a valid MAC address, which is what I used for the manual update attempt.  The memory command shows 4 64MB units, total 256MB.  The Warnings screen shows no errors other than that fastboot is enabled.

In the BOOT INFORMATION screen the top 3 options (Autoboot, Autosearch, Autostart) are all turned off.  Could the "Autosearch" setting be related to finding a network boot host?

Is there something I need to do to get the firmware updater and the E4406A to talk to each other?  Or is it possible to get to a shell that would allow me to configure the network via ifconfig or /etc/network?

I'm stumped; any help would be appreciated.

Thanks,
John
nexus:
I've done a lot of firmware updates on E444X PSA analyzers, which I believe run the same HP UNIX os. I also remember that when I first started, I had a hell of a time getting a LAN boot path to show up.

This is all due to firewalls and blocked ports. You will have to experiment with adding exceptions to ports and disabling TCP/UDP blocking in windows firewall until you can get the instrument to boot from LAN.

First, I would try using a crossover cable between the PC running the update and the instrument. Some switches can block layers of the traffic needed to allow the instrument to boot from LAN.

The next thing to do is to make sure your host PC is disconnected from the internet. Then go ahead and disable windows firewall on all networks (private, public, etc).

In windows firewall exceptions, add the IP address of your instrument to the exceptions.
Also, in the Agilent update program install folder (in your "Program Files") folder, there is an application called "bootpdnt". Add exceptions to this application in windows firewall as well. The run the update program again, restart the instrument and see if it recognizes your PC as a boot device while the update program is running and at the appropriate step.
n8ur:
Thanks for that info, nexus!  I'll try a direct crossover cable (I've been using a switch that's isolated from the house network).  I'll also check the firewall rules.

But... I wonder if the E4406A even has the IP address still configured after the broken update?  So I'm not sure firewall rules at the IP level are doing anything.  However, if the bootpdnt program is being blocked from listening/talking, that could certainly explain it.

Thanks!
nexus:
No problem. I believe there is a way to see or set the IP when the OS is unbootable.

I've attached 2 documents I saved which were for the PSA series analyzers but will probably also apply to the VSA as it runs a similar CPU/OS. These have instructions on firmware recovery and update procedures.

Hopefully you are able to reinstall the fw and get it up and running again!
nexus:

--- Quote from: n8ur on September 11, 2022, 06:17:00 pm ---bootpdnt program is being blocked from listening/talking, that could certainly explain it

--- End quote ---

Also, make sure you set bootpdnt to run as administrator. there is also another application in the same folder called "tftpdnt" which i also set to run with administrator as well.
Navigation
Message Index
Next page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod