Slok, your units are more interesting now. If you can run the ZCX command and tell us how many and what speed the cortexes are, we can compare them to mine. Maybe your units run all of them slow. Maybe you have B grade chips and whole bunches are not running. If they are all running slow, we might be able to boost.
C
ok, but how, can't find that chiliflash app.
Current Firmware:
https://www.dropbox.com/s/zoewijezzhfl3bs/Chili14e.hexFlash Utility:
https://www.dropbox.com/s/xpccbhfkbpinov8/ChiliFlash.exeUtility Source:
https://www.dropbox.com/s/zn8gkojly2f87wx/ChiliFlash.rarAlternate FW:
Voltage limited to 1.1V, can prevent overcurrent conditions on cards with almost all cores enabled.
https://www.dropbox.com/s/rfa4kuigov99sg8/Chili14e1v1.hex1V limited, to bring power use down to ~4J/GH
https://www.dropbox.com/s/b9f9ne7ilwl3ap8/Chili14e1v0.hexPrevious FW
https://www.dropbox.com/s/8qhhoqmvtk6i6jj/Chili14d.hexFlashing instructions:
Open the exe file in Windows (or inspect the source of the VS project and compile yourself), and select the comm port for the card from the drop down list. Note that you need the default FTDI/VCP drivers (ie, the ones you'd use for bfgminer) installed to see a comm port, you can't have the WinUSB drivers at this point.
Open the port, and you should see a bunch of information including the current FW version, the number of cores on each chip and their frequency.
Click browse and navigate to the hex file you want to flash, and then click program. The progress bar will increment and the LEDs on the unit will binary count as it programs, and when it's done the program will prompt you to power cycle the unit, and the inner and outer 4 LEDs on the board will alternatingly flash until you do.
Should you need to program the FTDI chip, you can use the following links
FTDI Programming Template:
https://www.dropbox.com/s/gkbcih32atez8qb/BFL%20FTDI.xmlFT_PROG utility:
http://www.ftdichip.com/Support/Utilities/FT_Prog_v2.8.2.0.zip