this fw seems to enable/disable cores with greater frequency... cool
If you use bertmod 98 then some fixes inside the new frimware will lost, because, the old bertmod 0.98 will change the /etc/init.d/cgminer.sh
for example !!!
New for me is the job of this file: /usr/bin/waas !
Can not parse JSON in config file %s: %d
asic_%d_voltagespi_frequency%dspi_voltage%fdie%d{
"asic_%d_voltage": {
"die%d": "%1.4f",
"die%d": "%1.4f"
"die%d": "",
"die%d": ""
},
"spi_frequency": "%d",
"spi_voltage": "%s"
}
/dev/i2c-%dError opening %s: %m
Error setting slave device address: %m
/sys/class/gpio/gpio76/directionCan not open /sys/class/gpio/gpio76/direction: %m
lowhighTPS65217 error: Bad ID 0x%02X
TPS65217 error: Bad status 0x%02X
TPS65217 OK. Modification %c, revision 1.%d
Wrong ENABLE value 0x%02X
Wrong SEQ4 value 0x%02X
Wrong SEQ1 value 0x%02X
Wrong SEQ3 value 0x%02X
Can not read ENABLE register
Can not read SEQ4 register
Can not read SEQ1 register
Can not read SEQ3 register
/sys/class/gpio/gpio49/directionCan not open /sys/class/gpio/gpio49/direction: %m
Wrong DEFDCDC1 value 0x%02X
Wrong DEFDCDC3 value 0x%02X
Wrong DEFSLEW value 0x%02X
Wrong DEFLDO1 value 0x%02X
Wrong DEFLDO2 value 0x%02X
Wrong DEFLDO3 value 0x%02X
Wrong DEFLDO4 value 0x%02X
Write failed to /sys/class/gpio/gpio49/direction
Waiting PGOOD for too long
/config/.wa3.3v.down0
?Can not open file %s:%m
Can not read file %s
Wrong value (%s) in file %s
Failed to connect to I2C bus %d
spi_transfer: ioctl error on SPI device: %m
FPGA I2C error: read data 0x%02X (expected 0x%02hhX) from reg %u:%u
spi_new: Out of memory!
/dev/spidev%d.%dCan not open SPI device %s: %m
spi_new: ioctl error on SPI device %s: %m
Can not write file %s
Write failed to %s
spitop_bitrev_pad.rbfCan not open RBF file spitop_bitrev_pad.rbf:%m
/sys/class/gpio/gpio67/value/sys/class/gpio/gpio66/valueCONF_DONE is HIGH when nCONFIG is LOW
/sys/class/gpio/gpio69/valuenSTATUS is HIGH when nCONFIG is LOW
CONF_DONE is HIGH when nCONFIG is HIGH
nSTATUS is LOW when nCONFIG is HIGH
SPI transfer failed after %d bytes
nSTATUS is LOW during the configuration
Can not read RBF file spitop_bitrev_pad.rbf:%m
CONF_DONE is LOW at the end of configuration
FPGA I2C error: Bad ID 0x%02X
SPI transfer failed
%02hhXCorrect SPI answer when expecting wrong one!
Wrong SPI answer:Wrong data from ASIC: num_cores = %hu, revision = 0x%04hX
/config/advanced.conf (here you can find it: cat /usr/bin/waas)
I think it is for the next fw release or the NEW: KNC-Tuner 1.0
Run this command to see some stats:
/usr/bin/waas -d (it is new inside monitordcdc)
here is my output: (I have an avg. 549 Gh/s) (now with my 4 RMA boards) 1. Coin on 14. november from september batch
{
"asic_1_voltage": {
"die1": "-0.1121",
"die2": "-0.1121",
"die3": "-0.1121",
"die4": "-0.1121"
},
"asic_2_voltage": {
"die1": "",
"die2": "",
"die3": "",
"die4": ""
},
"asic_3_voltage": {
"die1": "-0.1121",
"die2": "-0.1121",
"die3": "-0.1121",
"die4": "-0.1121"
},
"asic_4_voltage": {
"die1": "-0.1121",
"die2": "-0.1121",
"die3": "-0.1121",
"die4": "-0.1121"
},
"asic_5_voltage": {
"die1": "-0.1121",
"die2": "-0.1121",
"die3": "-0.1121",
"die4": "-0.1121"
},
"asic_6_voltage": {
"die1": "",
"die2": "",
"die3": "",
"die4": ""
},
"spi_frequency": "201442",
"spi_voltage": "1.95"
}
Can anyone send me an complete diff between 0.98 and 0.99 (i don´t know how) Thx a lot!!!
Not sure what horse to bet on next 
That's gotta be a good sign...
0.98 or 0.981 
