Topic: Cairnsmore1 - Quad XC6SLX150 Board - page 14. (Read 286370 times)
Anyone know if the usual suspects, mokokam, is producing a +220MHs bitstream? I am all 220MHs with <0.5% error rates
Looks like I'll have to buy a jtag cable.
Does anyone have experience with this one:
http://www.amazon.com/SainSmart-Download-Programmer-Xilinx-Platform/dp/B0057OC5VQ/ref=pd_cp_pc_0
I can report that the SainSmart device works with Xilinx Impact.Does anyone have experience with this one:
http://www.amazon.com/SainSmart-Download-Programmer-Xilinx-Platform/dp/B0057OC5VQ/ref=pd_cp_pc_0
My problem board is now fully flashed and hashing again.
--
NOTE: Install stand-alone "LabTools" rather than the WebPack in order for Impact to be able to program/flash the Spartan 6 / 150 FPGAs. Otherwise you'll get a rather unhelpful message about a corrupt file when the problem is really that the free WebPack version isn't licensed to operate on the 'big' FPGA's.
I'm mining with a Raspberry Pi too, only 1 board though, but I guess it can handle a few more at least.
I wonder if anyone was able to set up CM1 board mining with Raspberry Pi already? If yes, how many boards is one RPi able to handle?
I'm running two with my Pi. No problems here. Can probably handle a lot more
Ebereon, quick question for you
How many CM1's do you have per instance of mpbm, per netbook? I seem to be getting some instability issues with cards or pairs of chips dropping if i run more than 15.
How many CM1's do you have per instance of mpbm, per netbook? I seem to be getting some instability issues with cards or pairs of chips dropping if i run more than 15.
I have no instability issues and I use USB-Hubs from EasyLine (2,99€; 4P), MS-TECH (16,99€; 7P) and LogiLink (14,99€; 10P).
But as I run Windows I can only connect 30 boards to one netbook (Atom N2600) and 20 Boards to the other (Atom 450). The system process uses up to 50% only for handling interupts. 40 boards running 1.5 controller (using up/down) with makomk bitstreams 200-220Mhz, 10 boards glasswalker combination. And here is my problem now, the 10 boards with glasswalkers bitstreams increases the cpu load by 10% (interupts), as glasswalkers controller need all 4 COMs from one board.
... I need to switch to linux now...
When a board/fpga droped out I trashed the damn "enterpoint USB cable" and used a new one. That way my boards running rock stable > 20 days. Every problem I had until today was faulty USB cables.
Eb
hrm. that may be my issue then. I was very surprised when I connected the new set and all of them were recognized with the enterpoint usb cables, though i noticed cards dropping randomly when I started mpbm. I will do more testing today and let you know what happens.
EDIT: I switched out the cables to the offending boards and all seems to be running smoothly.
Ebereon, quick question for you
How many CM1's do you have per instance of mpbm, per netbook? I seem to be getting some instability issues with cards or pairs of chips dropping if i run more than 15.
How many CM1's do you have per instance of mpbm, per netbook? I seem to be getting some instability issues with cards or pairs of chips dropping if i run more than 15.
I have no instability issues and I use USB-Hubs from EasyLine (2,99€; 4P), MS-TECH (16,99€; 7P) and LogiLink (14,99€; 10P).
But as I run Windows I can only connect 30 boards to one netbook (Atom N2600) and 20 Boards to the other (Atom 450). The system process uses up to 50% only for handling interupts. 40 boards running 1.5 controller (using up/down) with makomk bitstreams 200-220Mhz, 10 boards glasswalker combination. And here is my problem now, the 10 boards with glasswalkers bitstreams increases the cpu load by 10% (interupts), as glasswalkers controller need all 4 COMs from one board.
... I need to switch to linux now...
When a board/fpga droped out I trashed the damn "enterpoint USB cable" and used a new one. That way my boards running rock stable > 20 days. Every problem I had until today was faulty USB cables.
Eb
Ebereon, quick question for you
How many CM1's do you have per instance of mpbm, per netbook? I seem to be getting some instability issues with cards or pairs of chips dropping if i run more than 15.
How many CM1's do you have per instance of mpbm, per netbook? I seem to be getting some instability issues with cards or pairs of chips dropping if i run more than 15.
Glasswalker, in doing a review of the cairnsmoreworker.py with dynamic clocking support I have only one question.
-- edit --
Nevermind, I see that idea doesn't work. I'll just increase the required number of shares per speed step during warmup. As you've already provided.
--
Would it perhaps be more appropriate, or at least more conservative, to only reset the "recentinvalid" count upon a speed decrease rather than also on every speed increase? Might preclude a potential 'runaway' situation.
e.g., "if speedstep < 0:" in the below
Of course, please let me know if I overlooked something which moots this idea.
-- edit --
Nevermind, I see that idea doesn't work. I'll just increase the required number of shares per speed step during warmup. As you've already provided.
--
Would it perhaps be more appropriate, or at least more conservative, to only reset the "recentinvalid" count upon a speed decrease rather than also on every speed increase? Might preclude a potential 'runaway' situation.
e.g., "if speedstep < 0:" in the below
Of course, please let me know if I overlooked something which moots this idea.
Code:
if critical:
speedstep = -10
self.initialramp = False
elif warning:
speedstep = -1
self.initialramp = False
elif not self.recentinvalid and self.recentshares >= threshold:
speedstep = 1
else: speedstep = 0
if speedstep: self._set_speed(self.speed + speedstep)
if speedstep:
self.recentinvalid = 0
self.recentshares = 0
Nope, something low level went wrong with this board.
Got out the VOM and verified that the DIP switches are on/off working correctly.
I've ordered the jtag cable I referenced a few posts ago. (Dithered too long and I won't get it until Monday rather than tomorrow.)
If it can't be fixed with the jtag cable I'll have to start a conversation with yohan about an exchange. bummer
Got out the VOM and verified that the DIP switches are on/off working correctly.
I've ordered the jtag cable I referenced a few posts ago. (Dithered too long and I won't get it until Monday rather than tomorrow.)
If it can't be fixed with the jtag cable I'll have to start a conversation with yohan about an exchange. bummer
Lazyotto: To downgrade from glasswalker back to 1.5 try dip switch 3 and dip 6 both in the off position.
Yep, that's what I thought I was doing.I'll go back and retry, again, just in case one of the DIPs is acting a bit flakey.
BTW, I did bring it up in the current 'bad' condition and it successfully mines with dynamic clocking on two of the four COM ports. (Still booted in Windows atm.) The other two COM ports are not recognized by the MPBM Cairnsmore worker.
Lazyotto: To downgrade from glasswalker back to 1.5 try dip switch 3 and dip 6 both in the off position. once back on 1.5 then try to flash fpga 2+3 with glass's bitstream and then upgrade the controler back to glass's if you want to hash with it.
I've found on a couple of boards you get stubborn fpga's when flashing from makomk>glass if you have already upgraded the controler to glass's.
What i do now is flash all the fpga's first to glass's while still on 1.3/1.5 and then once all fpga's are flashed update the controler to glass's.
Let me know if this helps, if not hop on irc into #cm1 and i'll grab one of my boards and confirm the dip switchs for you.
I've found on a couple of boards you get stubborn fpga's when flashing from makomk>glass if you have already upgraded the controler to glass's.
What i do now is flash all the fpga's first to glass's while still on 1.3/1.5 and then once all fpga's are flashed update the controler to glass's.
Let me know if this helps, if not hop on irc into #cm1 and i'll grab one of my boards and confirm the dip switchs for you.
Glasswalker, do you have any thoughts about how your controller compares to the Enterpoint 1.5 and upcoming 1.6 versions in regard to the power consumption issues discussed by yohan in the post referenced above?
Hope that helps.Yes, thank you.
Latest HashVoodoo Release
Let me know your comments, and if you have any success.
Well, it appears that something went wrong during flashing on one of my two boards. (The other one is happily hashing now with dynamic clocking.)Let me know your comments, and if you have any success.
Cannot get p2 or p3 to successfully flash. (p0 and p1 do flash and successfully verify.)
When attempted to revert the controller firmware to Enterpoint's 1.5, spiprog states that "Device NOT XC3S50AN" and asks if I've set the correct DIP Switch.
Looks like I'll have to buy a jtag cable.
(Unless someone has magic advice to offer.)
Does anyone have experience with this one:
http://www.amazon.com/SainSmart-Download-Programmer-Xilinx-Platform/dp/B0057OC5VQ/ref=pd_cp_pc_0
--
Yes, I know I could find something cheaper via eBay, but this Amazon purchase could be delivered tomorrow.
Glasswalker, do you have any thoughts about how your controller compares to the Enterpoint 1.5 and upcoming 1.6 versions in regard to the power consumption issues discussed by yohan in the post referenced above?
Yes actually, talked to yohan about this a day or two ago.
So they disabled parts of the controller (most notably the dynamic clock generator chip) (not sure if this means they actively did something to "turn it off" to reduce power, or just "aren't using it").
The parts they disabled, I'm also not using in my controller bitstream right now. BUT I haven't done anything explicitly to reduce power consumption.
So... I'll need to clarify with them, to confirm if I have to add in some explicit code to disable the clockgen for example to reduce power usage. But ultimately that shouldn't be a problem (and possibly, we're already saving because I'm not using it, not sure, though I suspect I need to "turn it off").
As for the up/down chaining, we've discussed that. It's on the roadmap, but not there yet.
Hope that helps.
I've upgraded to Glasswalkers controler while testing it and downgraded back to 1.3, back up to glasswalker, then back to 1.5 before going back to Glass's. Did this to check it would be down gradable. Works fine on the 2-3 boards i tested that theory on.
2) Not tried reverting back to the enterpoint controller so I could use Makomk's bitstreams.
Stability has been really good since moving so not felt the need. Is there a reason to believe we can't revert back?
No.Stability has been really good since moving so not felt the need. Is there a reason to believe we can't revert back?
Just looking for solid confirmation.
Merely looking for warm fuzzies that no bridges are being burnt.
--
TY for your response, Lethos.
Latest HashVoodoo Release
Two questions:1) Does anyone have duration / stability data yet for this release? I.e., is it staying up continuously for days?
2) Has it been tested reverting the controller from the 'Glasswalker' flash/firmware back to the Enterpoint 1.x flavor?
1) I've been using it since it's release pretty much. Yes it's stable and is fine to be used continuous for days.
Invalids are always below 1% on my boards.
I have tried 2 programs to mine on it, both MPBM and I have been one of the testers for Luke-JR (BFGMiner), so that is the only stops I've made in mining.
MPBM is atm a little easier to tell invalids and rejects. Invalids are in the long term easily below 0.5% and it not unusual that some chips will report 0.1% or less invalids. I have experimented with all the way up to 220, it didn't create crazy amounts of invalids (still under 1% on average), it just sometimes for a short time went over 1%, to me that was unacceptable.
MPBM has pretty good set of rules, so it's speed increases are halted as soon as it steps over 0.1% invalids. I'd gotten use to essentially 0 invalids on his previous HV 175 bitstream, so I set the bar high on what I expect from it.
Still testing BFGMiner, so it's best if I don't comment on that at the moment.
2) Not tried reverting back to the enterpoint controller so I could use Makomk's bitstreams.
Stability has been really good since moving so not felt the need. Is there a reason to believe we can't revert back?
Latest HashVoodoo Release
Controller Rev 1.6 is coming.
Glasswalker, do you have any thoughts about how your controller compares to the Enterpoint 1.5 and upcoming 1.6 versions in regard to the power consumption issues discussed by yohan in the post referenced above?
Latest HashVoodoo Release
Two questions:1) Does anyone have duration / stability data yet for this release? I.e., is it staying up continuously for days?
2) Has it been tested reverting the controller from the 'Glasswalker' flash/firmware back to the Enterpoint 1.x flavor?
-- edit --
BTW, status report on my units' stability.
Seven days continuous operation so far with makomk's 200mhz version on two CM1's 'daisy-chained'. (Single USB cable to the two of them with in master/slave configuration.)
Ambient temperature about 80f / 27c.
Invalid rate of: 0.13 / 0.20 / 0.34 / 0.35 percent.
Not always easy for the testers either you know Luke and Kano. I love you work, but there are two sides to it.
Yeah 2 sides The free software and the profit from mining
Jump to: