Progskeet 1.21: Difference between revisions
m (→Bitstreams) |
m (→Bitstreams) |
||
| Line 20: | Line 20: | ||
=== Bitstreams === | === Bitstreams === | ||
{{Bitstreams_1.2/1.21}} | {{Bitstreams_1.2/1.21}} | ||
== Injectus and Updating Bitstreams == | |||
{{Updating Bitstreams_1.2/1.21}} | |||
Revision as of 09:33, 21 May 2013
Progskeet Support
Anouncement
Dear Customers,
today back in stock new production of PROGSKEET v1.21. The new production introduce a review of the progskeet pcb layout to grant a better and fast production. No new features between v1.21 and v1.20.
Uber creator of PROGSKEET is working now to release a new version of winskeet... more infos soon
source: http://www.progskeet.com/forum/viewtopic.php?f=2&t=109404Note: It still has the Actel ProASIC3 A3P125 so they are not solving the 1.2 issue with the bitstream not fitting in the Actel (a problem of the 1.2 that still has not been fixed, even though the cause is obvious a design/implementation flaw).
Bitstreams
| This page has missing files. You can help PS3 Developer wiki by adding download/mirror links on it and listing hashes (MD5, SHA1 etc). |
121018_0031
http://forum.dayton360mods.com/downloads.php?do=file&id=25
<uf6668> hi everybody
<uf6668> quick announcement
<uf6668> here's the latest dat: http://www.sendspace.com/file/rwz8jx
<uf6668> this is ONLY for 1.2
<uf6668> if you want to use on 1.1 or 1.0, you will need to make modifications
<uf6668> it enables following:
<uf6668> 1) dual boot using a switch (led on = secondary nand/nor, led off = primary nand/nor)
<uf6668> 2) both solderless nand and nor together
<uf6668> the new structure is not ready yet because I've dev'd it on 250 and I have to fit it into 125
<uf6668> regarding opensource, the api will only be for the new architecture, so only after i fit it into 125
121101_1505
http://forum.dayton360mods.com/downloads.php?do=file&id=26
121101_1223
http://forum.dayton360mods.com/downloads.php?do=file&id=24
121106_2121
http://forum.dayton360mods.com/downloads.php?do=file&id=23
from Progskeet Website:
New release for 1.2, dumping and writing should be much faster now. http://www.progskeet.com/forum/viewtopic.php?f=9&t=4231
130330_1909
- Increased metastability of USB (should no longer disconnect)
- Restored Samsung Q compatibility that was caused by dualboot pin allocation
for anyone who has v1.2/v1.21: https://dl.dropbox.com/u/52587949/ProgSkeet_12_130330_1909.dat / http://www.sendspace.com/file/ua6u2o makes it work like a 1.1
130401_1824
- Added timeout for reads/writes (1ms), no more blocking
- Fixed bug where it would read gpio from data pins rather than from gpio pins
130401_2010
ProgSkeet_12_130401_2010.dat
- Reduced timeout from 1.3ms down to 320ns per word
<uf6667> https://dl.dropbox.com/u/52587949/ProgSkeet_12_130401_2010.dat <uf6667> I made this yesterday Mancer <uf6667> I introduced a timeout for the "rdy" pin <uf6667> so that in case rdy never goes high <uf6667> it will continue anyway
130415_2058
http://forum.dayton360mods.com/downloads.php?do=file&id=27
130402_1730
- Added metastability to the DQ ports to filter out noise and glitches
130415_2019 (NAND) & 130412_1647 (NOR)
130706_1928
130708_1211
- Added speed indicator
- HIGHLY improved single word flashing
- Added hardware data polling
- Both NAND and NOR are in one bitstream now (!!!)
- No more pullups needed
- Reverted to libusb-win32
- tooltips
130710_1058
130713_1838
- buffer write works, about 70 seconds for 16MB spansion (which used to require 15 minutes!)
- updated bitstream
130715_1749
- buffer write and single word improved, I write an entire 16MB nor, buffer write, in about 40 seconds (not including read and erase, duhhhhhhhhh), 3 seconds per sector for single word (spansion is very fast now too)
- AUTODETECT OF THE NOR!!!! just click "dump CFI"
130721_0313
- NAND works PERFECT now
- last bitstream before final release
- progskeet core was rewritten and command set reimplemented in qt (hence the lack of releases in almost a week)
- versioning added (it will check if you are using the appropriate bitstream, which is located in /bitstream)
- use of files to load presets (instead of using the box on the first page)… nand is still in the making, so I left the first box as-is for now
- CFI for NOR works however, presets include most popular NORs but you can also save them (click “Dump CFI” and then “yes” when you are asked to save. put them in /cfi/)
- handshakes implemented (goodbye timeouts! might, but doesn’t have to, make it slower though… on the other hand, this might enable calibration for specific computers/chipsets )
- usb core had a bug where it would just keep writing to fifo regardless of full or not, but this has been fixed
- SPI flashing added! (will only be available once I release it for every platform though)
Injectus and Updating Bitstreams
- 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
| 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. |