Pardon my necromancy, but:

The thing is based on a Xilinx FPGA and Lapis touted that they could update and modify the functionality of the card by issuing a bit of software to put on the computer' date=' which would be consistent with changing the configuration file for the FPGA. [/quote']
Does this not suggest they left a programming port accessible? Does that in turn suggest to anyone that it may be possible to retrieve the FPGA data?

Click to expand...

Xilinx FPGAs power up blank. They can be programmed externally, and they also have a mode where they'll output an incrementing address from some pins and receive the resulting data on other (or same?) pins. In other words a method to automatically load their programming from a storage chips such as a ROM of Flash.

I can't remember if the Lapis card has an EEPROM or similar on board, but it is entirely possible that the FPGA code was loaded by the computer through the interface to the expansion card, in which case the FPGA code would be a component of the Lapis Driver.

This would be consistent with Lapis's statement that the hardware functionality was updateable.

The computer boots up, the FPGA is blank, after the Lapis driver loads, the Lapis driver causes teh FPGA data to be driven on the bus to the Lapis card where it is addressed to the FPGA. After programming the FPGA the Lapis card begins functioning.

Alternatively, there may have been a memory chip on the Lapis card itself so that the Lapis card could operated before the Lapis driver loaded. I'd have to look at the card to be certain which way they did it.

Click to expand...