|
User ID is 2167
Order ID is 2456
|
|
|
|
Got another board setup (I really need better heatsinks...), but I've come to the conclusion that the PL2303s simply won't work, period. cgminer sees the uarts, and sends the nonce tests. However, that fails (Bmsc recv golden nonce timeout). Even if I comment out/skip past the checks in driver-bmsc.c, it fails out even further down. So I suspect it really won't work, at least not with the little time I can invest at this point.
Has anyone had the PL2303 work?
I do have some CP2102s which should be in the mailbox any day now so I can get in on the party. I might try underclocking so I can avoid/minimize the heatsinking.
What is Your PL2303 Vendor and Device ID? edit: if it is 067b:2303 it should work as an Icarus, so You would try to recompile cgminer with --enable-icarus (both should work --enable-bmsc or --enable-icarus) |
|
|
|
Well, ran out of cp2102 usbs  edit: now stable at 252 GHs 315 Watt / 252 GHs = 1.25 W/GH wow edit: I suppose it is without any cooler i have a fan, and that helped, but im adding an extra just in case edit: picture:   Still have 15 boards left... Temperature 32°F it is reality? |
|
|
|
Well, ran out of cp2102 usbs edit: now stable at 252 GHs 315 Watt / 252 GHs = 1.25 W/GH wow edit: I suppose it is without any cooler |
|
|
|
it is first time I see it  but it has one UART so it should serve at least one blade in that case it is quite expensive solution better to make (buy) usb hub with 2 or more cp2102 and put it into Rapsberry, it should work |
|
|
|
well, im currently looking into connecting 2 boards to 1 cp2102, i get to set freq on all 64 chips, but currently timing out on golden nonce test...
What mods have you made to the driver? I tried that with 3.8.5 and both boards were hashing the same nonce ..... thus single board speed. im working directly off my github version, so far i have had no luck, ive even tried to disable the detection routine, and pretended everything "was fine" The detection routine? Is that in reference to the CP2012 ? I am still unsure where the bmsc code determines the number of chips since it at times initializes less than the 32 on a board, and by initializing I mean setting the frequency if you have that in the command-line, otherwise, I can not see where it does that! Anyway back to your thingy-bob, where in code do you disable the detection routine that you refer to? its the area where it tests the golden nonce, in driver-bmsc.c just trying to bypas this area to see if i can get it to start hashing OK. Since you have managed to get all 64 chips detected, then I suppose you can try to find out why it is not going past the golden_nonce test: After this: applog(LOG_ERR, "Bmsc recv golden nonce timeout");Add this: applog(LOG_ERR, "Bmsc recv golden nonce timeout received: %s", ret);My C++ is useless, but that should tell us what the return is (or does it fail on the next if ... else ... ?) EDIT: I have actually just seen the REAL initialization routine in driver-bmsc.c aka static void bmsc_initialise(struct cgpu_info *bmsc, int baud){
...
}----------------start nonce------------------ [2014-11-08 18:08:26] Bmsc send golden nonce [2014-11-08 18:08:27] Bmsc recv golden nonce timeout code 2 recieved: 0000000000 - should have recieved: 000187a2 [2014-11-08 18:08:27] -----------------start freq------------------- [2014-11-08 18:08:27] Send frequency 82078106 [2014-11-08 18:08:28] Send freq getstatus 8 Seems like the REAL initialise routine just fiddles about with the usb, nothing to do with the board .... unless there is something hidden in the usb_ident structure. [2014-11-08 18:08:27] Bmsc recv golden nonce timeout code 2 recieved: 0000000000 - should have recieved: 000187a2That does not offer any insight, to me at least, but suffice to say, I have seen that zero number printed out in the error messages before, though I have tried to replicate it to no avail. it sends a known nonce to the asics, and expects to recieve the 000187a2 but the error code it recieves is a communication timeout, and does not recieve any data. Better to order one more cp2102 I think. But good luck its called curiousity :-p well we have the software side running as it should, now we just need the prototype, or order 15 more cp2102 :-/ I have only 4 blades and 2 cp2102 (I have bought them per $8 per piece) just now but already purchased 2 more (about $2,6 per piece). What is much more important I think is to solve how to get proper information about how chips are running, about their status "x" or "o" and temperature. Have You any idea how to do it? In original S1 unit there is kernel module which very probably does it, send that info into some virtual device where cgi-bin script is reading it. But depends on if those informations are there where we are connected now or if there is need to attach another pin of the blabe. |
|
|
|
well, im currently looking into connecting 2 boards to 1 cp2102, i get to set freq on all 64 chips, but currently timing out on golden nonce test...
What mods have you made to the driver? I tried that with 3.8.5 and both boards were hashing the same nonce ..... thus single board speed. im working directly off my github version, so far i have had no luck, ive even tried to disable the detection routine, and pretended everything "was fine" The detection routine? Is that in reference to the CP2012 ? I am still unsure where the bmsc code determines the number of chips since it at times initializes less than the 32 on a board, and by initializing I mean setting the frequency if you have that in the command-line, otherwise, I can not see where it does that! Anyway back to your thingy-bob, where in code do you disable the detection routine that you refer to? its the area where it tests the golden nonce, in driver-bmsc.c just trying to bypas this area to see if i can get it to start hashing OK. Since you have managed to get all 64 chips detected, then I suppose you can try to find out why it is not going past the golden_nonce test: After this: applog(LOG_ERR, "Bmsc recv golden nonce timeout");Add this: applog(LOG_ERR, "Bmsc recv golden nonce timeout received: %s", ret);My C++ is useless, but that should tell us what the return is (or does it fail on the next if ... else ... ?) EDIT: I have actually just seen the REAL initialization routine in driver-bmsc.c aka static void bmsc_initialise(struct cgpu_info *bmsc, int baud){
...
}----------------start nonce------------------ [2014-11-08 18:08:26] Bmsc send golden nonce [2014-11-08 18:08:27] Bmsc recv golden nonce timeout code 2 recieved: 0000000000 - should have recieved: 000187a2 [2014-11-08 18:08:27] -----------------start freq------------------- [2014-11-08 18:08:27] Send frequency 82078106 [2014-11-08 18:08:28] Send freq getstatus 8 Seems like the REAL initialise routine just fiddles about with the usb, nothing to do with the board .... unless there is something hidden in the usb_ident structure. [2014-11-08 18:08:27] Bmsc recv golden nonce timeout code 2 recieved: 0000000000 - should have recieved: 000187a2That does not offer any insight, to me at least, but suffice to say, I have seen that zero number printed out in the error messages before, though I have tried to replicate it to no avail. it sends a known nonce to the asics, and expects to recieve the 000187a2 but the error code it recieves is a communication timeout, and does not recieve any data. Better to order one more cp2102 I think. But good luck |
|
|
|
repo with changes from idonthave and changed timing settings to set the timings you now can just type the timing in ms instead of the 0.55, so --bmsc-options 115200:55 working on more changes https://github.com/FireWalkerX/cgminer-bmscive changed the USB timeout on github, please try that Just recompiled that and same result, only this time the board does not get recognised at all. PS. I assumed you only changed the usbutils.c file, so I just replaced that rather than re-download the entire repo. ensure Yourself if wires are fixed properly. I use such workaround to fix them:  |
|
|
|
repo with changes from idonthave and changed timing settings to set the timings you now can just type the timing in ms instead of the 0.55, so --bmsc-options 115200:55 working on more changes https://github.com/FireWalkerX/cgminer-bmscJust compiled for windows in MinGW and run with the above options but still have the error UUGGHHHHHHhhhhh.....! On a positive note, it detects all chips first time around unlike 3.8.5 which initially detects, normally, 12!  Well, well, keep up the effort .... I am working on something too and will update the thread as soon as I have something of substance to report on. does cgminer have access to usb device? with ubuntu I have to run cgminer as superuser if did not install |
|
|
|
repo with changes from idonthave and changed timing settings to set the timings you now can just type the timing in ms instead of the 0.55, so --bmsc-options 115200:55 working on more changes https://github.com/FireWalkerX/cgminer-bmscgreat, good work |
|
|
|
|
Effectivity of the cp2102 solution
If You have blade, psu and pc (so I suppose $0 investition for blade, $0 for psu and $0 for pc), the only investition You have to do is usb to uart controller. If You are lucky, You get one for $2.65. You can pensil mod Your blade, lose few days with compiling of bitmain sources and reach finaly 50GHs per 55W. In that case You get with nowadays difficulty $6.65 per month and pay electridity (if lucky and have $0.1 per W) $3.96 so net is $2.69 per month. If You invested only $2.65 for controller You can get it back in one month. Conclusion is the solution is effective only if You know everything written above and get it cheaper hardware.
|
|
|
|
So far so good, I managed to get further than before. Stupidly, I was using the ckolivas repo instead of the bitmaintech one.  For someone in my footsteps: So, install the bitmaintech one and compile. With my PL2303s, I didn't have to make any changes except to the rules file which I will be reverting back as it wasn't necessary. It may be the cause of my problems anyways. The UART is seen by cgminer where it attempts to mine. However, I'm hitting the: [2014-11-08 00:07:48] Bmsc send golden nonce [2014-11-08 00:07:48] Bmsc recv golden nonce timeout issue which can't be fixed by the timing of which I plug in the device. Still diagnosing this. I suspect it may have to do with the shitty connections I have as the jumper leads to the blade header aren't so good or the rules file. If not, I will also try another blade, small chance this one isn't working. Compile bitmaintech sources, read this: https://bitcointalk.org/index.php?topic=671128.msg9399337#msg9399337Another chance could be maybe to try change vid/pid when load module into kernel but not sure if modprobe can do that. edit: what about this: http://www.ha19.no/usb/ |
|
|
|
|
Did anybody try FTDI chip and has any succes?
|
|
|
|
impossible just happened... 104GHS/109W  0.44 0781 edit: pool rej. 1% Epic ! timing is critical my undervolt isnt the best, im getting 1.34 (53 GHs 74 Watt) 1 blade at 200 MHz and timing 60 do not be afraid to go below 2.8kOhm... if You would see my multimeter which I used You would laugh... as that guy says, it is not rocket engineering ive been thinking of trying 2.56 (4.47 + 12 + 12 kohm :-p ) prommising results with 0.27 0781 - 103/108 ... more tommorow redid my pensil mod, all just slight below 2 kohm - measured 0.75, 0.75, 0.76, 0.79 volts 200 MHz timing 60 53 GHs 62 Watts i dont think i can push it any further with the pencil mod now. right now im running 51 GHs vs 59 Watt Agree, we need more stable solution then just a pensil. But 51/59 is quite good, I have 102/109 at the moment. Let me know if You decide to solder and share pic to encourage me do the same. |
|
|
|
I thought I'd missed something you put out earlier! Thanks for the pointer. I managed to compile having made the changes to driver-bmsc.c, aka replace memcpy((char *)&nonce, nonce_bin, sizeof(nonce_bin)); with memcpy((char *)&nonce, nonce_bin, sizeof(nonce));Then issued: ./autogen.sh --enable-bmsc CFLAGS="-02 -Wall -W -march=i686" --host=i686-pc-mingw32 make I did NOT include driver-icarus as has been suggested somewhere else, and the device was detected albeit with some issues. Below are the two screen shots i grabbed: EDIT: I run the executable with the options: --bmsc-options 115200:0.6 --bmsc-freq 0F81   Exactly the same result without zadig) if zadig is installed -no USB device detected try --bmsc-options 115200:0.27 --bmsc-freq 0781 |
|
|
|
impossible just happened... 104GHS/109W 0.44 0781 edit: pool rej. 1% Epic ! timing is critical my undervolt isnt the best, im getting 1.34 (53 GHs 74 Watt) 1 blade at 200 MHz and timing 60 do not be afraid to go below 2.8kOhm... if You would see my multimeter which I used You would laugh... as that guy says, it is not rocket engineering ive been thinking of trying 2.56 (4.47 + 12 + 12 kohm :-p ) prommising results with 0.27 0781 - 103/108 ... more tommorow |
|
|
|
impossible just happened... 104GHS/109W 0.44 0781 edit: pool rej. 1% Epic ! timing is critical my undervolt isnt the best, im getting 1.34 (53 GHs 74 Watt) 1 blade at 200 MHz and timing 60 do not be afraid to go below 2.8kOhm... if You would see my multimeter which I used You would laugh... as that guy says, it is not rocket engineering |
|
|
|
we need to read the chips fast enough for when the chips have anything to deliver, but not too fast to waiste time, and chip speed, so its a tradeoff.. the timings are the same as those found in the antminers config file versus speed.
edit:
on my test board with 200MHz and timing 100 vs timing 55 = aprox 5 GH lost if read to slow
even better with 0.44 - 93-4GHs/106-7W seems like we need to make a speed vs timing list sure, but as I have noticed, we use different blades, I have undervolted... edit: it means I will have probably a litle bit different table... and at the moment, for me it is just fun, I have only 4 blades mine is also undervolted with a pen, but im waiting for my solder paste to add a resistor in parallel to the other ones (i have 20 blades :-p ) i havnt done a decent job on my test board (74 watts / 52 GHs) yep, I was also thinking about to solder it... would You share then how You did it? If I will be able to make cheap and easy box I will buy some blades and build unit, but only if get consumption low enough edit: but it would be very difficult to get better then 1.17W/GHs... so... |
|
|
|
we need to read the chips fast enough for when the chips have anything to deliver, but not too fast to waiste time, and chip speed, so its a tradeoff.. the timings are the same as those found in the antminers config file versus speed.
edit:
on my test board with 200MHz and timing 100 vs timing 55 = aprox 5 GH lost if read to slow
even better with 0.44 - 93-4GHs/106-7W seems like we need to make a speed vs timing list sure, but as I have noticed, we use different blades, I have undervolted... edit: it means I will have probably a litle bit different table... and at the moment, for me it is just fun, I have only 4 blades |
|
|
|
|
Show Posts
