Pages:
Author

Topic: [DIY] - Reward $100 | Antminer S1/S3 Blade on Raspberry Pi - page 24. (Read 82134 times)

full member
Activity: 238
Merit: 100
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-bmsc

ive 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:
legendary
Activity: 1358
Merit: 1002
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-bmsc

ive 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.


hmm interresting, since the timeout only says "ill wait x amount of time, for the device, which i changed from 999 ms to 2000 ms, that change works on linux, maybe its your libusb dll that is of older date? or does it get compiled with cgminer?

edit : i have reverted the repo to previous timeout
Totally understand.
The one edit that I did to mine was to add a sleep in the driver-bmsc.c file on line 1179, i.e cgsleep_ms(500);

have you tried with the drivers from silab?

http://www.silabs.com/products/mcu/pages/usbtouartbridgevcpdrivers.aspx


hmmm could you try setting --hotplug 0 and see if it helps with the error messages
hero member
Activity: 518
Merit: 500
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-bmsc

ive 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.


hmm interresting, since the timeout only says "ill wait x amount of time, for the device, which i changed from 999 ms to 2000 ms, that change works on linux, maybe its your libusb dll that is of older date? or does it get compiled with cgminer?

edit : i have reverted the repo to previous timeout
Totally understand.
The one edit that I did to mine was to add a sleep in the driver-bmsc.c file on line 1179, i.e cgsleep_ms(500);
legendary
Activity: 1358
Merit: 1002
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-bmsc

ive 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.


hmm interresting, since the timeout only says "ill wait x amount of time, for the device, which i changed from 999 ms to 2000 ms, that change works on linux, maybe its your libusb dll that is of older date? or does it get compiled with cgminer?

edit : i have reverted the repo to previous timeout
hero member
Activity: 518
Merit: 500
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-bmsc

ive 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.
legendary
Activity: 1358
Merit: 1002
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-bmsc

Just 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

I just run the executable with Run as Administrator and get the same error, so that does not seem to solve the issue.

ive changed the USB timeout on github, please try that
hero member
Activity: 518
Merit: 500
A bit of progress, but there are soooooo many timeout et al errors.
1. It takes a while to acknowledge the board connected amidst the timeout errors
2. With version 3.8.5 I do not get anywhere near the rejects I get here, infact, I at times run for a day without any reject!
3. HW errors are still high .... may be atiming issue (used --bmsc-options 115200:55)

hero member
Activity: 518
Merit: 500
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-bmsc

Just 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

I just run the executable with Run as Administrator and get the same error, so that does not seem to solve the issue.
full member
Activity: 238
Merit: 100
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-bmsc

Just 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
legendary
Activity: 1358
Merit: 1002
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-bmsc

Just 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.


if you get something that works, ill try it out on linux, and if it works there as well, i will update the repo
hero member
Activity: 518
Merit: 500
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-bmsc

Just 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.
full member
Activity: 238
Merit: 100
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-bmsc

great, good work
legendary
Activity: 1358
Merit: 1002
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-bmsc
full member
Activity: 238
Merit: 100
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.
full member
Activity: 238
Merit: 100
So far so good, I managed to get further than before. Stupidly, I was using the ckolivas repo instead of the bitmaintech one.

 Undecided

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://bitcointalksearch.org/topic/m.9399337
Another 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/
newbie
Activity: 22
Merit: 0
So far so good, I managed to get further than before. Stupidly, I was using the ckolivas repo instead of the bitmaintech one.

 Undecided

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.

newbie
Activity: 22
Merit: 0
Quote
Did anybody try FTDI chip and has any succes?

I'm interested too as I got a pile of PL2303's before we were set in stone about the CP2102s. I imagine I have to compile a cgminer/bfgminer with modified source on my linux machine for the different UART boards. I changed the "rules" files of each so that only the PID/VID of the PL2303s is used but haven't had any luck so far after compiling. I'll be reattempting later tonight/tomorrow just using --enable-bmsc.

Either way, I just purchased some CP2102s too and hopefully they can come in quick so I can get mining away on this.

Any thoughts?
full member
Activity: 238
Merit: 100
Did anybody try FTDI chip and has any succes?
legendary
Activity: 1358
Merit: 1002
impossible just happened... 104GHS/109W  Cool 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. Smiley

well i suddenly remembered that psus also have a loss, so i decided to pencil mod another blade, and now im running 2 blades, at 175 timing 63 at 92 GH / 102 Watt = 1.1 W/GH
full member
Activity: 238
Merit: 100
impossible just happened... 104GHS/109W  Cool 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. Smiley
Pages:
Jump to: