J8013e Firmware Update

[Jkobe Peoples]

Ihave applied current firmware to older cards in the past without issue. Not sure if any were that old though but I would use the HP Download Manager which automates updates to JetDirect cards and test one. I can see if I happen to have an older one as I have an extensive repository of old firmware. I will check and post back.

Thank you for your reply! Download Manager attempts the update, but fails repeatedly. After some (tedious) digging on the HP forums, I found a post that mentioned the FW updates are specific to certain versions in some (unexplained) cases, and pointed to the info I provided in my OP. It says you can go to the latest FW only from those listed versions.

Regardless of why, I have tried tree printers using DLM, and all have failed. The one printer I tried to update at the Web GUI failed and is now bricked, so at least DLM uses a recoverable method, but not a successful one.

For example, you mentioned HP JetDirect 610n EIO print server (J4169A), firmware L.21.11. It could be that this particular JetDirect 610n variant is not possible to update due to hardware limitations. Hardware components used in a model can differ across its variants. Some variants used flashable memory some not.

Older versions of the firmware only support upgrading using the Trival File Transfer Protocol, but documentation regarding this seems to have been removed from the HP website (This also seems to be the method that HP Download Manager used).

You need to set up a TFTP server on your computer on the default port (69) that will be accessible to the printer. You can for example use this software available for all popular OS's, or this python script written by yours truly.

For HP Jetdirect devices with firmware versions x.22.xx or later, FTP can be used to upgrade the firmware.If the HP Jetdirect device has firmware version x.24.xx or greater, Embedded Web Server (EWS) can also be used to upgrade the firmware.

The EWS manual says to use ftp, which (along with telnet) has been removed from MacOS 'for security', of course, but I was able to copy over the binaries from an earlier OS version. Unfortunately, that too caused the printer to 'print' the firmware file.

HP Webjet Admin will not even recognise that the printer is on the network and connecting to it shows that it is a "Generic Network Card". Went to _firmware, but no information is available. Please help!

Thank you very much! I did not expect the update to do both JetDirect card and the the printer Firmware at the same time. I was looking for and update that would do just the JetDirect card. Thanks again.

This article describes how to update a removable or in-chassis device's firmware using the Windows Update (WU) service. For information about updating system firmware, see Windows UEFI firmware update platform.

To do this, you'll provide a device driver that includes the firmware payload. If you provide a function driver for your device, you can add the firmware update logic and payload to the existing driver, or you can provide a separate firmware update driver package. If your device uses a Microsoft-supplied driver, you must provide a separate firmware update driver package. In both cases, the firmware update driver package must be Universal.

Alternatively, if you want to update the function driver and the firmware update driver separately, create a second device node, on which you'll install the firmware update driver. The following diagram shows how one device can have two separate device nodes:

There are a couple ways to create a second device node. Certain device types have the ability to expose a second device node on one physical device, such as USB. You can use this functionality to create a device node targetable by WU, and install a firmware update driver on it. Many device types, however, don't allow a single physical device to enumerate more than one device node.

In this case, use an extension INF that specifies the AddComponent directive to create a device node that can be targeted by Windows Update and install the firmware update driver on it. The following snippet from an INF file shows how you can do this:

In the above INF sample, ComponentIDs = ComponentDeviceId indicates that the child device will have a hardware ID of SWC\ComponentDeviceId. When installed, this INF creates the following device hierarchy:

To locate another device node, the firmware driver should walk the device tree relative to itself, not by enumerating all device nodes for a match. A user may have plugged in multiple instances of the device, and the firmware driver should only update the device with which it's associated. Typically, the device node to be located is the parent or sibling of the device node on which the firmware driver is installed. For example, in the diagram above with two device nodes, the firmware update driver can look for a sibling device to find the function driver. In the diagram immediately above, the firmware driver can look for the parent device to find the primary device with which it needs to communicate.

The driver should be robust to multiple instances of the device being on the system, possibly with multiple different firmware versions. For example, there may be one instance of the device that has been connected and updated several times; a brand new device may then be plugged in which is several firmware versions old. This means that state (such as current version) must be stored against the device, and not in a global location.

3a8082e126