Following a firmware update which showed no errors, my E1439C no longer shows up in the VXI resource manager.
?
Does anyone happen to have an image of the 28F800 flash chip, insight on how to extract the image from the firmware update file, or what I might find connecting to the RS-232 header?
?
If the module had previously been updated but not had a sticker applied to indicate it had been, is it possible I should have used the “C” instead of “B” firmware image, leading to an image being loaded for wrong FPGA or CPLD running versions?
?
Do CLIPs exist for these?
?
A Quick look at data sheets suggests there are two in system programmable CPLDs, and a half dozen or so “small” (by today’s standards) FPGAs. I suspect most of them are loaded by the coldfire processor from the flash, probably with two that are, or in theory could be programmed in circuit.
?
The .all firmware update file doesn’t break out the flash image. Its size is around 3/4 of a megabyte and the flash is a 1 megabyte chip. The firmware file sizes are different for different serial number ranges.
?
I’d guess that it must contain at least some compression unless they write parts of the image to blocks on the chip, and only contain what needs to be updated.
?
Does anyone have insight on how to recover these boards?
?
if case you’re going to ask, since I planned to have two channels and the documentation suggests they need ti have matching firmware, I thought it was reasonable to update them. Also, mention about needing a certain version for trigger to be enabled seemed like a good reason (again for multichannel).
?
Not that it should matter, but I have a Tek VXI mainframe with an E8491A FireWire interface and plenty of old PC hardware available running vista 32 bit, but could go older if needed.
?
if all else fails, are any of the ADC/analog board parts common to something else for which the parts might be useful as donor parts?
