New Official AMT Thread

[opieum2]

When I run the commands I am expecting to see some kind of error that states why that the card failed or something to that effect. I will look at the i2cset documentation directly and see if I can parse some info before I try anything further. Least knowing the safe ranges gives me a spot to work with and see if I can get the card back up. Assuming thats even possible.

[mrpark]

I guess I will try to plug my broken AMT miner in again just for fun. Sorry guys I been busy with working miners But I now have 7Th/s of hosted miner power with spondoolies, getting them for under 3k a piece now.

my affiliate link: https://spondoolies.refersion.com/c/c91a5

Then try:

special offer $300 off our in-stock SP10 Dawson use coupon TY7263NKAMIT, limited to 50 orders

I bought 3 more today, and got $900 off.

Shipping might also be free, not sure? Try it and see. They seem to have them in stock.

P.S. Full disclosure they are loud, 70db each, so might not work in a small place if you host yourself.

[opieum2]

Nice! I just ordered some more s2 antminers. For the price I am quite happy with them. They work well.

[mrpark]

Nice! I just ordered some more s2 antminers. For the price I am quite happy with them. They work well.

Yes! they are very good miners too! I guess if we took a pole here it might be 50/50. I just figured I would put it out there. I paid more for my first round then 2nd round. Finally I am getting somewhere with this mining stuff! I have to be aggressive since I lost so much time already!!! I may look at antminer when they come out with a 5-10Th/s to compare pricing.

[opieum2]

Well I am down to 2 working cards. The 3 I have had were running fine for a couple weeks just fine without any messing around.....then poof one dropped dead. Hoping this is just something to do with voltages.

[NotFuzzyWarm]

When I run the commands I am expecting to see some kind of error that states why that the card failed or something to that effect. I will look at the i2cset documentation directly and see if I can parse some info before I try anything further. Least knowing the safe ranges gives me a spot to work with and see if I can get the card back up. Assuming thats even possible.

Got a 'scope or better yet data analyzer so you can see if there is data moving around? Many scopes over that last few years can even specifically trigger on SPI & iC2 events to look at the data packets.

[NotFuzzyWarm]

Well I am down to 2 working cards. The 3 I have had were running fine for a couple weeks just fine without any messing around.....then poof one dropped dead. Hoping this is just something to do with voltages.

Still have the Vdd voltage present on the dead card? Check across any of the 4  yellowish chip caps in the corners of the chips to measure it.

If done right the regulator will have over current sensing (the Bitmine ref one does) and shut down if faulted. As to whether you need to cycle the power to reset it or if auto-recovery, or can use software to ack the fault and restart it unknown. If no Vdd then either a) something major failed resulting in a short or b) the regulator itself has not been told to run (ic2 com to it lost?).

If ya got Vdd then I'd guess coms are lost.

[NotFuzzyWarm]

Nice! I just ordered some more s2 antminers. For the price I am quite happy with them. They work well.

Yes! they are very good miners too! I guess if we took a pole here it might be 50/50. I just figured I would put it out there. I paid more for my first round then 2nd round. Finally I am getting somewhere with this mining stuff! I have to be aggressive since I lost so much time already!!! I may look at antminer when they come out with a 5-10Th/s to compare pricing.

Ordered my 1st s2 last night, BTC4.609 Just in time as it seems that the Luck factor has been heading South as of late. My pool has been chewing on a block for the past 1d 14:04:47. For once I picked the perfect time to switch pay from DGM to PPS

After a good run at normal it will be interesting to see what the s2 does when goosed faster. For a s1 the default s2 clock is super eco-mode. Will need a bigger psu of course...

[opieum2]

Some interesting stuff. Notice the FF FF in the second card. I plugged 4 of the 5 in on the broken miner. Something took here....not sure what this means. Looking up some info to get more details.

Code:

[2014-02-23 08:00:42] 1: no A1 chip-chain detected
 [2014-02-23 08:00:42] SPI '/dev/spidev0.0': mode=1, bits=8, speed=2000000
 [2014-02-23 08:00:42] checking board 2...
 [2014-02-23 08:00:42] written: 0x02, 0xfb
 [2014-02-23 08:00:42] 1176741124: A1 init chain
 [2014-02-23 08:00:42] TX: 6 bytes:01 00 00 00 00 00
 [2014-02-23 08:00:42] RX: 6 bytes:00 00 00 00 00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] RX: 2 bytes:FF FF
 [2014-02-23 08:00:42] 2: no A1 chip-chain detected
 [2014-02-23 08:00:42] SPI '/dev/spidev0.0': mode=1, bits=8, speed=2000000
 [2014-02-23 08:00:42] checking board 3...
 [2014-02-23 08:00:42] written: 0x02, 0xf7
 [2014-02-23 08:00:42] 0: A1 init chain
 [2014-02-23 08:00:42] TX: 6 bytes:01 00 00 00 00 00
 [2014-02-23 08:00:42] RX: 6 bytes:00 00 00 00 00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] 3: no A1 chip-chain detected
 [2014-02-23 08:00:42] SPI '/dev/spidev0.0': mode=1, bits=8, speed=2000000
 [2014-02-23 08:00:42] checking board 4...
 [2014-02-23 08:00:42] written: 0x02, 0xef
 [2014-02-23 08:00:42] 1176741124: A1 init chain
 [2014-02-23 08:00:42] TX: 6 bytes:01 00 00 00 00 00
 [2014-02-23 08:00:42] RX: 6 bytes:00 00 00 00 00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] RX: 2 bytes:00 00
 [2014-02-23 08:00:42] 4: no A1 chip-chain detected
 [2014-02-23 08:00:42] All devices disabled, cannot mine!

[ladi4ever]

We'll get back to the other technical questions a bit later today.

F** your technical garbage, refund my money that you stole from me..You are going to go to JAIL for a long time soon..

[NotFuzzyWarm]

I hope not obvious to ask, but what do working cards report?
Also, kicking around in the dusty corners of me mind is there being something in the A1 dev thread about the SPI link speed vs A1 clock. 2,400,000 sticks in ma head. Don't know if good or bad but your logs shows it trying 2,000,000

Along those lines, in the SPI/iC2 link you gave they mentioned that iC2 coms happen in-between the SPI start/stop bits. Is that auto-synced or 2 different clocks used? If so, are they synced so the 2 different coms don't step on each other?

Yes, reading the entire dev thread was the 1st thing I did once I um, got snagged, with my order... Is what clued me in to what was going on with the A1 rigs once chips were in the wild. 1st thing noted was the performance spec changes from what had been hoped.

As for the boards... I was really hoping that Bitmine had learned some things from doing the Avalon systems on how to run more than just a few chips per-blade much less a box full of them. Rather like BFL it seems not

[mrpark]

Opened my miner today again. Pi card was disconnected and stuck under the power supply,heh. Missing caps, heat sinks and a few boards had the PCI-E connector broken off. Also, where the small board connects across the cards, 2 of the card connectors were torn off.  I will post photos tomorrow. One of the chips didn't even have thermal compound on it. Very silly indeed...

[ISAWHIM]

Ok, latest update... xD

The boards with only one of the four caps/resistors around the A1, with the alternate other caps... are both non-responsive. (Both these originally came with heat-sinks.)

The four boards with copper heat-sinks, and all four caps/resistors, two are still running. One runs at 204GHs, one at 178GHs. Two do not function. Of the two which are not functioning, one is due to an A1 chip seemingly over-heating, due to improper mounting on the PCB. The other had no heat-sink, and had an "S" or a "5" written near the back-plane mount, in permanent marker. This card had no heat-sink originally, which was added from one of the failed cards. It seems to have a short, as it knocks the whole miner offline, stopping all cards from booting, as it seems to ground-out my single 12v rail.

There are two more cards I have yet to test, which have the blue-anodized aluminum heat-sinks on the A1's and no heat-sink on the back-side. I will attempt to place heat-sinks on those, from the other non-responding or malfunctioning cards.

The few fractions of a coin that I have earned, have just about equaled the additional money I had to spend, to attempt to get these working, and running.

I too, am down to only 2 working cards, of eight. However, those cards are working fine, with the exception of the one with obvious dead cores. There is nothing left I can do to resolve any issues myself. The only thing I could do, if the thermal-compound was the issue, would be to buy thermal-pads for the large heat-sink, and to slice the heat-sink in half, so it didn't expand as it heated. That, and add a pressure-clip to hold the front heat-sink to the back heat-sink, to sandwich the chips with some tension, for better thermal contact. However, the issue is not thermal, at the moment.

After testing these last two boards, I will contact AMT to have the non-functioning cards returned. Each will be clearly noted, as to the issues found. However, it seems that the issues are already known for the older boards.

I just want to remind anyone who has just walked-in to this post... This is NOT a reflection of a "finished AMT miner". This was one of the alternative options. I am simply being thorough in my posting, as to the specific issues, so that the information can be used to help with any possible resolution to the specific units I was sent. I was aware that the boards may have issues, as they were of various production versions.

Just had to add those last few lines. I didn't want people thinking that this was what THEY were going to be delivered.

[Syke]

We'll get back to the other technical questions a bit later today.

[AMT_miners]

Ok, latest update... xD

The boards with only one of the four caps/resistors around the A1, with the alternate other caps... are both non-responsive. (Both these originally came with heat-sinks.)

The four boards with copper heat-sinks, and all four caps/resistors, two are still running. One runs at 204GHs, one at 178GHs. Two do not function. Of the two which are not functioning, one is due to an A1 chip seemingly over-heating, due to improper mounting on the PCB. The other had no heat-sink, and had an "S" or a "5" written near the back-plane mount, in permanent marker. This card had no heat-sink originally, which was added from one of the failed cards. It seems to have a short, as it knocks the whole miner offline, stopping all cards from booting, as it seems to ground-out my single 12v rail.

There are two more cards I have yet to test, which have the blue-anodized aluminum heat-sinks on the A1's and no heat-sink on the back-side. I will attempt to place heat-sinks on those, from the other non-responding or malfunctioning cards.

The few fractions of a coin that I have earned, have just about equaled the additional money I had to spend, to attempt to get these working, and running.

I too, am down to only 2 working cards, of eight. However, those cards are working fine, with the exception of the one with obvious dead cores. There is nothing left I can do to resolve any issues myself. The only thing I could do, if the thermal-compound was the issue, would be to buy thermal-pads for the large heat-sink, and to slice the heat-sink in half, so it didn't expand as it heated. That, and add a pressure-clip to hold the front heat-sink to the back heat-sink, to sandwich the chips with some tension, for better thermal contact. However, the issue is not thermal, at the moment.

After testing these last two boards, I will contact AMT to have the non-functioning cards returned. Each will be clearly noted, as to the issues found. However, it seems that the issues are already known for the older boards.

I just want to remind anyone who has just walked-in to this post... This is NOT a reflection of a "finished AMT miner". This was one of the alternative options. I am simply being thorough in my posting, as to the specific issues, so that the information can be used to help with any possible resolution to the specific units I was sent. I was aware that the boards may have issues, as they were of various production versions.

Just had to add those last few lines. I didn't want people thinking that this was what THEY were going to be delivered.

ISAWHIM,

We appreciate your diagnostic efforts thus far, they have been well documented and thorough. Send back to the two non working boards and we'll you send you another 2 working boards plus an additional 2 non working with issues. The "S" did stand for short. With about 7% right off the line from this production run we had encountered that problem of a short which caused the entire miner to fail, more over caused the power supply to short itself out. This was easily noted when watching the fan of the psu try to start after the 20-30 second warm up, spin once and then stop. Although power is still routed the entire miner, none of the cards would hash due to the board which caused the power supply short.

Hold on to that one and try to figure out why that happens. In some cases is was a poorly soldered component, a resister out of place or one that had a tombstone effect, diagnose that board and see if you can view any physical complications first. Second, using the DVM check the voltages of the three main sections of the board.

1.  Chip area, on or around each chip each cap should result in a voltage and not 0.03. This is the first way to know that the chip is not the problem causing a short but a problem in either the power supply on the board.

2. Compare against working boards the voltages in the trimpot area.  The trimpot area has its own supply, so if the the chip supply went down, the trimpot section would/could still work.

3. SPI/bridge backplane area. Scope around the backplane area and the 6 com lines originating from the backplane connector.

Obviously this is confusing and frustrating without a clear understanding of what you should be looking for. We'll send you and NotFuzzyWarm an NDA and up returned receipt we'll provide you two with partials boms/gerbers. Not enough to reproduce, but more than enough to see what you're looking at. Take a break until you get those, your a big help thus far and we dont want you getting frustrating and saying "ahh I quit" just yet.

Although we believe the problem lies in the copper/quality in/of the PCB boards themselves, missed component values and other issues as well, its still worth trying to see if we can bring any of these back to life.

[AMT_miners]

Guess while we are on the design end of things, good guide from PCB Universe to choosing cladding thickness and how that affects trace layout. http://www.pcbuniverse.com/pcbu-tech-tips.php?a=4 They also have a good faq on via designs.

For general trace width data this calculator is very handy http://circuitcalculator.com/wordpress/?p=25/
From same folks but for Vias http://circuitcalculator.com/wordpress/2006/03/12/pcb-via-calculator/

+1
Very helpful post.

[AMT_miners]

I don't get it,  why is the program called I2Cset when the chipset doesn't use I2C but rather SPI?

I believe there is an i2c to SPI bridge, which would explain the need for both and why they are both detected.
I am still understanding those aspects a bit more as I am finding I need the information to make potentially bring the boards back to life.

http://www.i2cchip.com/mix_spi_i2c.html is one resource (of many I found)

The good news is that it might be possible to bring the cards back provided I can find the right command to bring them back. The AMT-setup dpot command (in my previous post) do not appear to work at all as they are coming up with an invalid value. That just means it doesn't work. I am reading through the AMT script to understand the issue.

As you can see in the above I get [OK] Error: Data value invalid! is a sign that the code might not be correct. OR something else is wrong. Hopefully AMT can clear this particular piece up.
The card on the chain is found so that's positive. BUT the command to set it is invalid (bad). I know at this point I have 7 cards that are potentially zombiefiable (new word to add to webster dictionary), I have 3 working cards (not messing with that) and 1 totally dead card that will prevent any sort of power up (need to check it for shorts)

On the hardware side I tried something based on ISAWHIM's mention of the potential board short from the PCB touching the metal cage. I taped up the edges where the cards contact the metal I had hoped on a long shot that might actually bring up a card or two, but no dice

That said least now that is a potential issue that is mitigated. I think the boards COULD be brought back with software. Maybe not all but some of them. The fact that the i2cset commands was not actually taking because the value was invalid would be a good reason why this happened. I am currently testing now with AMT's default firmware before I move on to the porting process (which I have partially done). I figure it might be best doing it with what is already available before reinventing the wheel. If I get the cards back up then I will proceed with the next steps of porting over to the new firmware.

I think there is progress tho seeing as the cards are detected but nonfucntional at this point. Hopefully not beyond the point of recovery.

EDIT: To add I am working on the i2cset commands to do all this manually if I have to (not something I recommend to anyone not experienced in this sort of thing), and seeing how the script interacts with that. If I can manually do this bypassing the script I will modify the existing scripts to issue the correct commands and add comments in the scripts for proper use. Its fairly trivial to add the usage part.  That might actually get the hardware working. While the progress is slow (in my opinion) its progress that's happening. My time is limited so I really only put in a couple hours a day on this at most.

Opieum,

The AMT script is design to run with the UI only. So basically if you log in directly and using the:

killall cgminer

amt-setup

(what ever else)

and you run from the command line - you'll be using default bitmine values. The script itself starts with the automatically when the miner first starts, killing it or logging in directly via the pi null and void this script. You can refun this, but the best way to see if its working/having any change is to hook up the second monitor to the pi and also have your computer handing, work on the pi itself, use "reboot" to reboot the miner itself, then do not login to the pi but to the admin panel on the browser and run the miner that way. You can always check the activity in the settings section of the UI as well.

We can ask Zefir to help us with this one. He is a nice man who we know face to face, he's a bit down/sad about the industry. Although he is from the squad of optimists turned pessimist, he may still be willing to help. Zefir is we looked up to since before we knew zefir, and when meeting him in person for the first time in swiss, it was kind of like a celebrity shock type of thing. He's someone that really wanted to bitcoin to work as intended rather than how it exists today. We'll see if he'd be willing to come over to our thread and assist thus far.

Here is a thought that we've had for sometime but could never verify it because as brilliant as our software guys are, they are just arrogant. And although they've confirmed this isn't a problem on several occasions, we still feel that it might be a good place to look. Our software guys like to create rather than verify someone's else work.

The A1 disables itself and the entire chain if it reaches the point of overheating (or when it thinks it's overheating), we've always had a gut feeling that chip parameters later set are somehow remembered physically and are not being told to "reactivate later" hence getting the "no a1 chip chain detected".

[chlangyue0168]

how about my 690# and 691#

[ladi4ever]

Opened my miner today again. Pi card was disconnected and stuck under the power supply,heh. Missing caps, heat sinks and a few boards had the PCI-E connector broken off. Also, where the small board connects across the cards, 2 of the card connectors were torn off.  I will post photos tomorrow. One of the chips didn't even have thermal compound on it. Very silly indeed...

Same here bro, he sells garbage, un-approved Equipment and fire hazard. Guy is a looser..

[opieum2]

I don't get it,  why is the program called I2Cset when the chipset doesn't use I2C but rather SPI?

I believe there is an i2c to SPI bridge, which would explain the need for both and why they are both detected.
I am still understanding those aspects a bit more as I am finding I need the information to make potentially bring the boards back to life.

http://www.i2cchip.com/mix_spi_i2c.html is one resource (of many I found)

The good news is that it might be possible to bring the cards back provided I can find the right command to bring them back. The AMT-setup dpot command (in my previous post) do not appear to work at all as they are coming up with an invalid value. That just means it doesn't work. I am reading through the AMT script to understand the issue.

As you can see in the above I get [OK] Error: Data value invalid! is a sign that the code might not be correct. OR something else is wrong. Hopefully AMT can clear this particular piece up.
The card on the chain is found so that's positive. BUT the command to set it is invalid (bad). I know at this point I have 7 cards that are potentially zombiefiable (new word to add to webster dictionary), I have 3 working cards (not messing with that) and 1 totally dead card that will prevent any sort of power up (need to check it for shorts)

On the hardware side I tried something based on ISAWHIM's mention of the potential board short from the PCB touching the metal cage. I taped up the edges where the cards contact the metal I had hoped on a long shot that might actually bring up a card or two, but no dice

That said least now that is a potential issue that is mitigated. I think the boards COULD be brought back with software. Maybe not all but some of them. The fact that the i2cset commands was not actually taking because the value was invalid would be a good reason why this happened. I am currently testing now with AMT's default firmware before I move on to the porting process (which I have partially done). I figure it might be best doing it with what is already available before reinventing the wheel. If I get the cards back up then I will proceed with the next steps of porting over to the new firmware.

I think there is progress tho seeing as the cards are detected but nonfucntional at this point. Hopefully not beyond the point of recovery.

EDIT: To add I am working on the i2cset commands to do all this manually if I have to (not something I recommend to anyone not experienced in this sort of thing), and seeing how the script interacts with that. If I can manually do this bypassing the script I will modify the existing scripts to issue the correct commands and add comments in the scripts for proper use. Its fairly trivial to add the usage part.  That might actually get the hardware working. While the progress is slow (in my opinion) its progress that's happening. My time is limited so I really only put in a couple hours a day on this at most.

Opieum,

The AMT script is design to run with the UI only. So basically if you log in directly and using the:

killall cgminer

amt-setup

(what ever else)

and you run from the command line - you'll be using default bitmine values. The script itself starts with the automatically when the miner first starts, killing it or logging in directly via the pi null and void this script. You can refun this, but the best way to see if its working/having any change is to hook up the second monitor to the pi and also have your computer handing, work on the pi itself, use "reboot" to reboot the miner itself, then do not login to the pi but to the admin panel on the browser and run the miner that way. You can always check the activity in the settings section of the UI as well.

We can ask Zefir to help us with this one. He is a nice man who we know face to face, he's a bit down/sad about the industry. Although he is from the squad of optimists turned pessimist, he may still be willing to help. Zefir is we looked up to since before we knew zefir, and when meeting him in person for the first time in swiss, it was kind of like a celebrity shock type of thing. He's someone that really wanted to bitcoin to work as intended rather than how it exists today. We'll see if he'd be willing to come over to our thread and assist thus far.

Here is a thought that we've had for sometime but could never verify it because as brilliant as our software guys are, they are just arrogant. And although they've confirmed this isn't a problem on several occasions, we still feel that it might be a good place to look. Our software guys like to create rather than verify someone's else work.

The A1 disables itself and the entire chain if it reaches the point of overheating (or when it thinks it's overheating), we've always had a gut feeling that chip parameters later set are somehow remembered physically and are not being told to "reactivate later" hence getting the "no a1 chip chain detected".

Thanks. Yea it seems possible to reactivate these. I reached out to zefir for some info. He was helpful in pointing me to a few things, but I think I need to get alot more details. I do agree it would be better if you reached out to him on this. I will post the info I have and what I have found that might help get this off the ground. My driver development experience is very limited BUT I do have some. At any rate hopefully some issues can be addressed via software.