[DIY] - Reward $100 | Antminer S1/S3 Blade on Raspberry Pi

[pekatete]

ok, official legend status goes to J4bberwock

It took me almost 1 hour 

YOU are the man. I think it is safe to say the bounty goes to you, and you deserve it.
For RPi I think the same solution works out of the box, simply install the cgminer version and you are off.
TOP MAN!

[J4bberwock]

ok, official legend status goes to J4bberwock

It took me almost 1 hour 

I had a feeling it was going to be easy, but you actually went ahead and got it done.  This should also work for the S3 as the chip is basically the same as the S1.  This has opened a new branch of S1/S3 modding.

The control board is the same on both S1 and S3, and I suspect that even the PCB for the hashing boards is the same, meaning I could buy bare chips from bitmaintech and replace the 1st gen ones, with the new ones.
At least, that's what I would have done if I had to produce miners, using the exact same pinout on each chips generation to be able to reuse the "old" boards I have in stock.
would also cost less, since ou don't have to design a new board.

[powersup]

Check this guide out, it should give you the commands for setting the frequency.

https://coinreport.net/overclock-antminer-u1-guide/

just a note, the S1 uses different hex values to the U1, so make sure you use the S1 hex values

Man, I wish I wasn't half a world away from my miner right now  

[J4bberwock]

ok, official legend status goes to J4bberwock

It took me almost 1 hour 

YOU are the man. I think it is safe to say the bounty goes to you, and you deserve it.
For RPi I think the same solution works out of the box, simply install the cgminer version and you are off.
TOP MAN!

yes, it's easier to use a simple uart to usb board, maybe with a usb hub chip.
It will allow to plug it on any controler, PC, mac, RPI, openwrt platform...

[pekatete]

The control board is the same on both S1 and S3, and I suspect that even the PCB for the hashing boards is the same, meaning I could buy bare chips from bitmaintech and replace the 1st gen ones, with the new ones.
At least, that's what I would have done if I had to produce miners, using the exact same pinout on each chips generation to be able to reuse the "old" boards I have in stock.
would also cost less, since ou don't have to design a new board.

Control board IS the same, however the PCB boards are definitely different. The S1 has 32 chips on each PCB whereas the S3 has only 16 chips. However, if the chip footprints and connections are the same, then you can swap these out from the S1, but you'll need more power to run the hungrier S3 chips (now that you'll have 32) AND you'll also have to swap out the voltage regulators AND hope that the power traces on the PCB can handle the extra power.

All in all, I think there's still a bit to hack on this S1, both hardware wise and driver / software wise. Also the miner. There are still LOTS of efficiencies that I believe can be squeezed out of the old lady.

[J4bberwock]

The control board is the same on both S1 and S3, and I suspect that even the PCB for the hashing boards is the same, meaning I could buy bare chips from bitmaintech and replace the 1st gen ones, with the new ones.
At least, that's what I would have done if I had to produce miners, using the exact same pinout on each chips generation to be able to reuse the "old" boards I have in stock.
would also cost less, since ou don't have to design a new board.

Control board IS the same, however the PCB boards are definitely different. The S1 has 32 chips on each PCB whereas the S3 has only 16 chips. However, if the chip footprints and connections are the same, then you can swap these out from the S1, but you'll need more power to run the hungrier S3 chips (now that you'll have 32) AND you'll also have to swap out the voltage regulators AND hope that the power traces on the PCB can handle the extra power.

All in all, I think there's still a bit to hack on this S1, both hardware wise and driver / software wise. Also the miner. There are still LOTS of efficiencies that I believe can be squeezed out of the old lady.

Ok, then, just populate 4 to 6 chips in each row, wire the 2 in/out pins from the missing chips to bypass them, and/or run the S3 chips undervolted.

[powersup]

ok, official legend status goes to J4bberwock

It took me almost 1 hour 

YOU are the man. I think it is safe to say the bounty goes to you, and you deserve it.
For RPi I think the same solution works out of the box, simply install the cgminer version and you are off.
TOP MAN!

I couldn't agree more. J4bberwock deserves the bounty. I have sent 0.025 BTC to the address in your signature. Tx id = e13405cc62b73c17b4290c24fd59b0f99d9a14523f98e678716cc37320c40953.

[pekatete]

The control board is the same on both S1 and S3, and I suspect that even the PCB for the hashing boards is the same, meaning I could buy bare chips from bitmaintech and replace the 1st gen ones, with the new ones.
At least, that's what I would have done if I had to produce miners, using the exact same pinout on each chips generation to be able to reuse the "old" boards I have in stock.
would also cost less, since ou don't have to design a new board.

Control board IS the same, however the PCB boards are definitely different. The S1 has 32 chips on each PCB whereas the S3 has only 16 chips. However, if the chip footprints and connections are the same, then you can swap these out from the S1, but you'll need more power to run the hungrier S3 chips (now that you'll have 32) AND you'll also have to swap out the voltage regulators AND hope that the power traces on the PCB can handle the extra power.

All in all, I think there's still a bit to hack on this S1, both hardware wise and driver / software wise. Also the miner. There are still LOTS of efficiencies that I believe can be squeezed out of the old lady.

Ok, then, just populate 4 to 6 chips in each row, wire the 2 in/out pins from the missing chips to bypass them, and/or run the S3 chips undervolted.

Yep, lots of permutations, like I said, the old lady still has some juice left in her!
Did you use one of these?

[bluecityste]

So, does this mean (in theory) that this system can be used to control multiple S3 blades from the S1 upgrade kits?

Well done J4bberwock (i think! Unfortunately most of this thread is way aver my head).

Stephen

[smit1237]

Damn i can't get it to work Looks like i have some bad wiring

[J4bberwock]

So, does this mean (in theory) that this system can be used to control multiple S3 blades from the S1 upgrade kits?

Well done J4bberwock (i think! Unfortunately most of this thread is way aver my head).

Stephen

Yes, but the cgminer part still needs to be fixed correctly, I'm not a coder, but I can have a look, it will be slower than if someone actually knowing what to do is looking at it.

I'm currently having high HW errors because I can't choose the frequency and the timeout, and maybe another parameter.
In the december build, it looks like the values are hardcoded, and the newer version gives me even worst results for now.

[J4bberwock]

Damn i can't get it to work Looks like i have some bad wiring

pin3 is Rx, pin5 is tx
Pin 1 in the closest to the fan connector.
Doesn't work for me with the newest bfgminer.
Cgminer from december in bitmain's github works ok without any parameter except the pool settings

[powersup]

So, does this mean (in theory) that this system can be used to control multiple S3 blades from the S1 upgrade kits?

Well done J4bberwock (i think! Unfortunately most of this thread is way aver my head).

Stephen

In theory yes, but it would require some heavy mod work.  The problem is the blades are manufactured identically.  Each chip on the blade is assigned an address on the UART bus.  The problem with multiple blades on the same bus is there will be address conflicts.  The MCU on the S1 and S3 controller uses 2 UART ports, one for each blade.

Why is say in theory it can be done is because you can change the address of the chips by bridging pins, so, in theory you could change the chip addresses on the second and third blade and have them all run off the same UART bus.

[J4bberwock]

Yep, lots of permutations, like I said, the old lady still has some juice left in her!
Did you use one of these?

Yes, a simple one like this.
Costs 3$ or so, but it will be cleaner to have a nice board with integrated usb hub so you can plug a few hashing boards on it.
I'll work on it this weekend.

[J4bberwock]

Here is the test setup.
Getting 45 Gh from a board, but many HW errors

[pekatete]

Here is the test setup.
Getting 45 Gh from a board, but many HW errors

Brilliant!
1. The errors I think will have to do with the driver in cgminer. Look at setting these values in the initialisation string of cgminer, I got this from the Kernel Log of a running miner:

Code:

 --bitmain-options 115200:32:8:15:262.5:0a02 -o stratum+tcp://my.pool.io:3333 -O username:password -o stratum+tcp://my.backup:3333 -O username:password -o stratum+tcp://my.otherbackup.com:9332 -O username:password --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --queue 10 --scan-time 1 --expiry 1

EDIT: I think this bit --bitmain-options 115200:32:8:15:262.5:0a02  could be helpful.
EDIT2: That sets the frequency to 262.5 and HEX value to 0a02 - replace accordingly.
EDIT3: HANGON! Those values I got from my S3, heres one from the S1 --bitmain-options 115200:32:8:35:400:4f81

2. Do all the chips feel warm to the touch? I have a feeling you are not interfacing with all the chips.

[J4bberwock]

Here is the test setup.
Getting 45 Gh from a board, but many HW errors

Brilliant!
1. The errors I think will have to do with the driver in cgminer. Look at setting these values in the initialisation string of cgminer, I got this from the Kernel Log of a running miner:

Code:

 --bitmain-options 115200:32:8:15:262.5:0a02 -o stratum+tcp://my.pool.io:3333 -O username:password -o stratum+tcp://my.backup:3333 -O username:password -o stratum+tcp://my.otherbackup.com:9332 -O username:password --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --queue 10 --scan-time 1 --expiry 1

EDIT: I think this bit --bitmain-options 115200:32:8:15:262.5:0a02  could be helpful.
EDIT2: That sets the frequency to 262.5 and HEX value to 0a02 - replace accordingly.

2. Do all the chips feel warm to the touch? I have a feeling you are not interfacing with all the chips.

yes, they are all hot/warm, but the default frequency for the U2 is lower than the one on S1.
I'll test your settings and report back

[pekatete]

Here is the test setup.
Getting 45 Gh from a board, but many HW errors

Brilliant!
1. The errors I think will have to do with the driver in cgminer. Look at setting these values in the initialisation string of cgminer, I got this from the Kernel Log of a running miner:

Code:

 --bitmain-options 115200:32:8:15:262.5:0a02 -o stratum+tcp://my.pool.io:3333 -O username:password -o stratum+tcp://my.backup:3333 -O username:password -o stratum+tcp://my.otherbackup.com:9332 -O username:password --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --queue 10 --scan-time 1 --expiry 1

EDIT: I think this bit --bitmain-options 115200:32:8:15:262.5:0a02  could be helpful.
EDIT2: That sets the frequency to 262.5 and HEX value to 0a02 - replace accordingly.

2. Do all the chips feel warm to the touch? I have a feeling you are not interfacing with all the chips.

yes, they are all hot/warm, but the default frequency for the U2 is lower than the one on S1.
I'll test your settings and report back

I added a third edit - those values were for an S3 here's the one from an S1 --bitmain-options 115200:32:8:35:400:4f81 and they are from the System Log NOT the Kernel Log

[smit1237]

omg still no luck. Blade blinks but nothing happen

[chadwickx16]

Where do you get the UART to USB Converters from? Never mind, I forgot the Google is my friend sometimes.    Great work J4bberwock!!!!!

Will this one will work??

What is the male to male jumper called between the cable coming from the USB and into the Ant's cable?  Sorry UberN00b here, never really attempted anything like this before.