|
yes;) it's already what I did:
Before i connection only hashboard for test
1 - remove original Bmminer
2 - copy Bmminer-T9 +
3 - rename to bmminer
3 - Attribution of the right attribute
4 - replace minerConfiguration.cgi
5 - delete from minerConfiguration2.cgi (if in doubt)
6 - in page configuration, modified the value and apply
and after you know more ...
|
|
|
|
|
it's more than 3 months that my T9 + turn at about 12.5Ths without problem, I had tweak this minor since long time: p
so I prayed the Bmminer T9 + that I copy on my minor, I also gave him the right to know rwxr-xr-x ...
I do not see where the mistake is ... anyway it is absolutely necessary to execute your deployer? Did I miss something ?
I must recognize that the possibility of changing the tension of your bmminer greatly interests me: p
|
|
|
|
Thank you I know lol I'm not at my test shot on the minor, I'm also in hardware!  on your tweak, i did not run the "bmminer-deploy.exe" but i just copy the "bmminer-t9 +" and "minerconfiguration" on my minor, i got the config page, i take 700mhz and 870mv ... But that did not work, I took care not to use the bmminer-S9 but beautiful and well the T9 + bmminer;) |
|
|
|
I tested this for T9+!!! but ... i'm sorry, big problem, PIC SW error see : Miner Type = T9+
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x0000ffff
chain[2] PIC jump to app
Check chain[2] PIC fw version=0x03
chain[2] PIC need restore ...
dsPIC33EP16GS202_get_pic_sw_version failed on Chain[2]!
dsPIC33EP16GS202_get_pic_sw_version failed on Chain[2]!
dsPIC33EP16GS202_get_pic_sw_version failed on Chain[2]!
After restore: chain[2] PIC fw version=0xff
chain[2] PIC need restore ...
dsPIC33EP16GS202_get_pic_sw_version failed on Chain[2]!
dsPIC33EP16GS202_get_pic_sw_version failed on Chain[2]!
dsPIC33EP16GS202_get_pic_sw_version failed on Chain[2]!
After restore: chain[2] PIC fw version=0xff
Chain[J3] will use voltage=930 [1] to open core
set_Voltage_S9_plus_plus_BM1387_54 failed on Chain[2]!
set_Voltage_S9_plus_plus_BM1387_54 failed on Chain[2]!
set_Voltage_S9_plus_plus_BM1387_54 failed on Chain[2]!
Chain[J11] will use voltage=930 [1] to open core
Chain[J12] will use voltage=930 [1] to open core
Fix freq=675 custom_voltage_value=870 custom_voltage_enabled=1 disable_fan_check=0 fixed_frequency=1
Fix freq=675 Chain[2] voltage_pic=11 value=870
voltage_config=7792282
Fix freq=675 Chain[10] voltage_pic=11 value=870
voltage_config=7792282
Fix freq=675 Chain[11] voltage_pic=11 value=870
voltage_config=7792282
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
Chain[J3] has 0 asic
Chain[J11] has 0 asic
Chain[J12] has 0 asic
miner total rate=0GH/s fixed rate=0GH/s
i restored my board with my PicKit3 |
|
|
|
|
Great! so, if I understand correctly, can not change the voltage via this BMMINER for T9 + but only the ratio "voltage / freq" has been changed?
in addition, your BMMINER for T9 + thus brings the freq control, and the deactivation of the fan check?
I'm just going to take the BMMINER and the configuration page and test all that to see how it's done;)
|
|
|
|
What conssomation? my T9 + test indicates Fix freq = 643 Chain [1] voltage_pic = 28 value = 820
Fix freq = 643 Chain [2] voltage_pic = 28 value = 820
Fix freq = 643 Chain [8] voltage_pic = 28 value = 820
perfectly stable at 7.9Ths and 0.0003% hw (only 2 hashboard) and 920W |
|
|
|
T9+ is annoying to overclock and honestly not worth it. Don't do it also this one won't work.
if I can allow myself, Original T9 + = 10.5Ths ==> 1450W at wall 220v My T9 + = 12.5Ths ==> 1400W at wall 220V Its worth it 2Th free! ? Regards: p But I agree 100% not to mount Bmminer S9 that VERY strongly risk giving the error "PIC Error" and brick one or more hash board ... |
|
|
|
Hi, that makes me look nice! I nevertheless "find" a problem, in the "set-miner-config" ... cp /www/pages/cgi-bin/minerConfiguration2.cgi /www/pages/cgi-bin/minerConfiguration.cgi -f
This will just erase the new configuration page once "apply" ... a simple oversight? As far as I'm concerned, I'm looking forward to the Bmminer for T9 + because it's actually exactly what I'm working on now, because of the decreasing voltage variant with freq, I'm limited to 12.5Ths stable in overclock (1400W at wall). |
|
|
|
Of course ! Plug this on the all on your hash board ! And see my tuto. Your picture is ok to connect this ! |
|
|
|
|
No , if you take freq "700" , it run at 700mhz and 870Mv chip ... (i read the code source)
|
|
|
|
|
Easy , on "echo "\"bitmain-freq\" : \"1\"," " replace the "1" number for your desire freq,
for you, take - echo "\"bitmain-freq\" : \"700\"," -
|
|
|
|
|
Thank you;) so at worst, a PicKit 3 does not cost anything, I got mine for 20USD new
this solution works very well, and will only cost you 20usd and it's easy to do, I explain everything;) if you really have no choice ...
I pence that may have integrated my HEX file in a firmware, it must necessarily be able to do it in a software way (it already does with bad firmware) ...
I'm going to hang on this question but currently I'm working on other small projects so I do not have much time ...
friendly;)
|
|
|
|
|
Thank you ! your comments are a pleasure to hear!
You see now that I am not a scamer or even a naughty perssonne: p
I noticed that some perssonne have the same problem with their S9, I do not have S9 on hand but if I had one, then it would be just as easy to do the same tutorial! (if you have an S9 down I'm interested)
I remain at disposal to give help;)
|
|
|
|
it's exactly the same problem as with my T9 +, see my subject;) In your case, I am 99.9% sure that with the PicKit3 you bring back to life your card! 1: extract the HEX file from a functioning card 2: the reinjected into the card that does not work (FW 0X00) Ps : the PicKit3, the cost is ~_ 25USD |
|
|
|
be careful, my "tutor" only fixes the problem of the lost pic, in the log of the kernel there must be this after having checked the fan: chain [1] PIC jump to app
Check chain [1] PIC fw version = 0x03 (or other)
but if you have: chain [1] PIC jump to app
Check chain [1] PIC fw version = 0x00 or 0xff
so my tutorial will be useful! Also beware, my HEX file is ONLY for the T9+ ! it is equipped with a PIC32 while all other antminer are equipped with PIC16 !!!
We have tested this with some users before, but it does not seem to work for everyone. I'm glad it worked for you  You said that it did not work for many others, which model? what process? have you program the pic? Thank you |
|
|
|
Great! Glad to see that his help !!! I think that now that I extracted the program HEX pic32, it should not be difficult to inject it into an update, to reprogram via software;) ps: you already had a Pickit3 on hand ? |
|
|
|
Hi,
i have 3 S9 13,5Th, work fine your soft, actually summer mode 830mV/512MHz.
Good work,
but i have T9+ , and of course i temporarily kill him the machine.
[...]
Please temporarily originally silence bitmain soft for T9+,
maybe 550MHz...
Thanks!
best regards
Imre
from Hungary
Please see my post |
|
|
|
Hi all! I know some people have had a problem with their T9 + who lost 2 hash board, especially after flashing the firmware Dollemizer! or build own bmminer by source code What happens, the bad firmware erases the board DSPIC32 to reprogram them, but as it does not have the HEX file, it reprograms nothing, and therefore the chain is definitely lost! I also had the problem after trying a BMMINER custom that had exactly the same effect! so I got hooked on the question ... and HERE IS THE SOLUTION! pre-requisite: - a PICKIT 3 case - MPLAB X IPE - Bitmain HEX original file (pic32) After : 1 - connect to the board, pin1 in front of the PICKIT arrow  2 - Connect on MPLAB  3 - Enter in advanced mode and take "power target circuit from tool"  4 - ERASE the pic (use if you sure that the hash board is hs) Erasing...
Erase successful
2018-09-19 22:17:36 +0200 - Programming...
5 - Put in Hex File my Hex file extracted from good board (download here http://www.k-upload.fr/afficher-fichier-2018-09-19-103561fd6dspic33ep16g.hex.html ) or ( http://www.mediafire.com/file/mk8ivrax849ztxp/DSPIC33EP16GS202-ORIGINAL-T9%252B.hex/file ) Connecting to MPLAB PICkit 3...
Currently loaded firmware on PICkit 3
Firmware Suite Version.....01.54.00
Firmware type..............dsPIC33E/24E
Programmer to target power is enabled - VDD = 3,250000 volts.
Target device dsPIC33EP16GS202 found.
Device ID Revision = 4003
DEVSN0 = 00000000
DEVSN1 = 00000000
2018-09-19 22:16:21 +0200 - Hex file loaded successfully.
Loading code from C:\Users\xxx\Desktop\Firmware antminer D3 et L3+\pump firmware T9+\Prog PIC\DSPIC33EP16GS202.hex...
6 - "Program" and wait ! Programming...
The following memory area(s) will be programmed:
program memory: start address = 0x0, end address = 0x1dff
Programming/Verify complete
2018-09-19 22:18:13 +0200 - Programming complete
once the cards flash with PicKit, do not forget to reflash the minor with official firmware bitmain before reboot the minor ... to do this, do it before you flash the card, or just connect the controller card (without the hashboard) and flash the official firmware, power off the miner, reconnect the hashboard and turn on again. Essenciel is that the first start after flashing the board is done with an official firmware on the minor (with hashboard connected) otherwise the problem will come back immediately.. Now your board is reprogramed ! and working !!! For any advice or request do not hesitate! If you like it;) BTC: 1FWpeHCs7rB7LgWUiU2j2GgwuZpEYtfGm2 LTC: LShLPeXRMgRg3K2DP1ZMmWXbfS3Fh4ATNQ EDIT : FREE GIFT ! for no error / brick your miner after compile your own code for bmminer Modifi this "define" to "undefine" on the bitmain code on "driver-btm-c5.H" (the effect : no flash pic) 241 #define ENABLE_RESTORE_PIC_APP // if enabled, will restore PIC APP when the version is not correct!!!
|
|
|
|
Sorry, they talk about a good time to troubleshoot a persian scammed by a firmware ... and I have recovered for my own tests! at my risk and perils |
|
|
|
|
Show Posts
