Template:Updating Bitstreams 1.2/1.21
- Install the Infectus driver for Injectus --> connect only the Injectus via usb to PC
- Disconnect the Injectus and connect it via 15 pin cable to the Progskeet 1.2, then connect it to the PC.
Load the Bitstream with the Infectus Programmer. - When it´s done disconnect it from the PC and connect the Slaveboard instead of the Injectus. Then connect it to the PC.
Install the driver manually.
If it´s done, it will look like this:
Progskeet 1.2 - Injectus - 01
Progskeet 1.2 - Injectus - 02
Progskeet 1.2 - Injectus - 03
Error Codes[edit source]
| Error 3 | Cannot reset hardware. The software cannot establish communication with the programmer. Power/communications issue. |
| Error 5 | Hardware timeout. The software issues this error message when it is waiting on a response from the programmer while executing a command and the programmer does not respond within the expected amount of time. This error can result from several causes, see also Error 3 and Error 10 |
| Error 6 | Wrong model number see also Error 3 for possible causes |
| Error 8 | Malfunctioning port. The port that is selected with the Configure command does not exist on your computer, is not functional, or has a bad cable connected to it. |
| Error 9 | Programmer execution error. The programmer failed an internal consistency check, see Error 3 and Error 5 for possible causes |
| Error 10 | Error in programming algorithm. Please call technical support. The software has detected an internal error. |
| Error 11 | There is no data in the buffer, You must load a file or read a chip. A command tried to read data from the buffer to program or verify a chip, but nothing has been loaded into the buffer yet or the buffer was recently cleared. |
| Error 14 | There is no chip in the programmer. Be certain that you inserted your chip correctly. If it was inserted correctly, remove it and run the hardware self-test to make sure your programmer is functioning correctly. |
| Error 15 | The chip is not inserted in the programmer. The continuity test determined that the chip in the programmer site does not have continuity on all the proper pins. You should examine these pins carefully. |
| Error 16 | The chip is inserted backwards. The chip has passed the continuity tests, but appears to have the GND and Vcc pins improperly placed in the socket. If LCC, PLCC, or QFP is not accidentally rotated, then the device is probably defective. Try a known good device. |
| Error 17 | Out of base memory. You should have at least 200K free. |
| Error 18 | Temporary file error. The software's virtual memory manager is trying to store data that is currently not needed in RAM to the disk. The program was unable to create a temporary file, or the disk is full. Make sure you have plenty of disk space (the larger the data files, the larger the requirement for temporary disk space). |
| Error 21 | Cannot program. Not able to program the device in the programmer. |
| Error 22 | Cannot erase. Not able to erase the device in the programmer. |
| Error 23 | Invalid electronic signature in chip (device ID)
|
| Error 24 | Invalid electronic signature in chip (algorithm ID). The chip may be damaged or the programming algorithm may have changed. |
| Error 26 | Device is not blank. The Device/Blank command was executed or the Blank check before programming option was enabled in the Device/Options dialog box, and the device in the programmer site is determined to have programmed data. You may have used the wrong algorithm, or the device may have been programmed previously. |
| Error 27 | Device is not secured. An attempt to secure a device was made, but it failed. |
| Error 31 | Database file is invalid, The EXE file is corrupt. The .EXE file you are executing has been corrupted. You should uninstall and then reinstall the software to fix the executable. |
| Error 32 | Sorry, algorithm not found. Please call technical support. The .EXE file you are executing has been corrupted. You should get a new copy. |
| Error 33 | You must reselect the chip you want to program. The device was selected before establishing communication with the programmer; this may have been done prior to turning on the programmer or before switching to a different programmer. Reselect the chip and the error should not recur. |
| Error 36 | You must properly install the correct socket module |
| Error 39 | Device already secured. The device cannot be legitimately programmed, read, etc., because it is secured. If it is a PLD, it may still be functionally tested with the Test command under the Test tab. |
| Error 44 | Internal error. Please call technical support. The software detected an internal inconsistency. This may be caused by the computer not performing correctly. Contact technical support |
| Error 46 | AFS software required to execute this function. This is a function that is available to users who have purchased the Advanced Feature Software only. In order to use the chosen function you must purchase the AFS upgrade. |
| Error 47 | Self-test failed. This unit may need service. Please call technical support. The self-test has detected a hardware problem. The unit may need to be returned for repair. Note the exact error message and contact Technical Support. |
| Error 57 | You must purchase support for this device. The device that you selected is not supported in the default device set for this programmer. |
| Error 70 | The buffer data cannot be used to program. You loaded a file type that is not a valid option for the currently selected device. Re-select the device and load the buffer again. If the error persists, call technical support. |