Pages:
Author

Topic: Cairnsmore1 - Quad XC6SLX150 Board - page 47. (Read 286370 times)

legendary
Activity: 1379
Merit: 1003
nec sine labore
July 30, 2012, 01:28:57 PM
makomk 160.bit on board #62-0008 gives a U: of 0.5 - 0.8 after an hour of hashing using cgminer 2.4.3 on linux.

I'm trying now to flash the 140 MH/s one to see if it is better.

spiccioli

You have the wrong one, the one you want (trust me) is:
shortfin_icarus_cm1_test_160.bit

Isokivi,

sorry, I was not clear enough shorting the bitstream name from  shortfin_icarus_cm1_test_160.bit to 160.bit, but I'm using the correct one Smiley

Anyway, with the 140.bit I always fail cgminer test, even after a few complete power-off/on of the board, so I think I'm gonna flash the old twin_test.bit for now. Sad

spiccioli
sr. member
Activity: 327
Merit: 250
July 30, 2012, 01:27:42 PM
How do I actually flash the shortfin_* bitstreams?
Using the VirtualBox and "xc3sprog -c cm1 -p 0 shortfin_*.bit" gives me

Ignoring unknown field '
'
Unknown error

Sad

Did you copy the files to the VBOX? do an ls *.bit and make sure your files are there.The command should be xc3sprog -c cm1 -p0 shortfin_icarus_cm1_test_160.bit no space between -p0. Then you would just change -p0 to -p1, p2, and p3, as each one completes to do all 4 fpga's.

sr. member
Activity: 397
Merit: 500
July 30, 2012, 01:22:39 PM
How do I actually flash the shortfin_* bitstreams?
Using the VirtualBox and "xc3sprog -c cm1 -p 0 shortfin_*.bit" gives me

Ignoring unknown field '
'
Unknown error

Sad

flash it like the twin_test.bit.

without flashing to SPI:
Code:
xc3sprog -c cm1 -p0 shortfin_icarus_cm1_test_160.bit
With flashing to SPI:
Code:
xc3sprog -c cm1 -p0 -Ixc6lx150.bit shortfin_icarus_cm1_test_160.bit

Make sure when flashing:
SW1 #3 off
SW6 #1 off

SW2 all on
SW5 all on
SW3 #2 off
SW4 #2 off

When mining:
SW1 #3 on
Others same as approve

eb
donator
Activity: 543
Merit: 500
July 30, 2012, 01:20:38 PM
How do I actually flash the shortfin_* bitstreams?
Using the VirtualBox and "xc3sprog -c cm1 -p 0 shortfin_*.bit" gives me

Ignoring unknown field '
'
Unknown error

Sad
hero member
Activity: 910
Merit: 1000
Items flashing here available at btctrinkets.com
July 30, 2012, 01:07:39 PM
makomk 160.bit on board #62-0008 gives a U: of 0.5 - 0.8 after an hour of hashing using cgminer 2.4.3 on linux.

I'm trying now to flash the 140 MH/s one to see if it is better.

spiccioli

You have the wrong one, the one you want (trust me) is:
shortfin_icarus_cm1_test_160.bit
legendary
Activity: 1379
Merit: 1003
nec sine labore
July 30, 2012, 12:58:01 PM
makomk 160.bit on board #62-0008 gives a U: of 0.5 - 0.8 after an hour of hashing using cgminer 2.4.3 on linux.

I'm trying now to flash the 140 MH/s one to see if it is better.

spiccioli
hero member
Activity: 910
Merit: 1000
Items flashing here available at btctrinkets.com
July 30, 2012, 12:55:11 PM
Looks like I can report succes on makomk's 160 bitstream, with cgminer 2.61 in windows 7 64-bit.
newbie
Activity: 33
Merit: 0
July 30, 2012, 12:26:27 PM
How many bitstreams are currently in development?

- Glasswalker is re-writing the Icarus-bitstream, main problem is JTAG noise and meeting the timing?!
- Which bitstream is makomk working on? According to the filename, also some kind of Icarus-rewrite?
- Is EP still working on a (from-scratch) bitstream or are they now waiting for Glasswalker to finish his work?
- Is anyone working on making the TML-bitstream fully compatible with CM1?

I'm working on adding native support to the TML-bitstream with the included FTDI chip.  I've had to rewrite the jtag interface so it's been some time, but i'm progressing nicely.

How does that work exactly chrisp, can you still use a miner like cgminer, or do you need a miner provided by Et? I have yet to even look at making anything work with the Et bitstream.

I am using the ET miner.  Using cgminer would require porting over his interface to the encryption servers and the like, doable, but more work.  So it's the same java app that's distributed on his website.
sr. member
Activity: 327
Merit: 250
July 30, 2012, 12:24:51 PM
How many bitstreams are currently in development?

- Glasswalker is re-writing the Icarus-bitstream, main problem is JTAG noise and meeting the timing?!
- Which bitstream is makomk working on? According to the filename, also some kind of Icarus-rewrite?
- Is EP still working on a (from-scratch) bitstream or are they now waiting for Glasswalker to finish his work?
- Is anyone working on making the TML-bitstream fully compatible with CM1?

I'm working on adding native support to the TML-bitstream with the included FTDI chip.  I've had to rewrite the jtag interface so it's been some time, but i'm progressing nicely.

How does that work exactly chrisp, can you still use a miner like cgminer, or do you need a miner provided by Et? I have yet to even look at making anything work with the Et bitstream.
newbie
Activity: 33
Merit: 0
July 30, 2012, 12:12:58 PM
How many bitstreams are currently in development?

- Glasswalker is re-writing the Icarus-bitstream, main problem is JTAG noise and meeting the timing?!
- Which bitstream is makomk working on? According to the filename, also some kind of Icarus-rewrite?
- Is EP still working on a (from-scratch) bitstream or are they now waiting for Glasswalker to finish his work?
- Is anyone working on making the TML-bitstream fully compatible with CM1?

I'm working on adding native support to the TML-bitstream with the included FTDI chip.  I've had to rewrite the jtag interface so it's been some time, but i'm progressing nicely.
legendary
Activity: 1379
Merit: 1003
nec sine labore
July 30, 2012, 11:52:43 AM
New Results with makomk 160.bit running smooth so far in cgminer 2.6.0.

Its getting there!

ICA 0:                | 357.4/358.3Mh/s | A:194 R:0 HW:0 U:  4.50/m
ICA 1:                | 361.1/355.3Mh/s | A:205 R:0 HW:0 U:  4.75/m
Nice! Out of interest, did you have trouble getting the board to pass cgminer's validation? I'm hoping I found the cause of that problem and fixed it, but...

makomk,

I've just flashed 5 of my boards with controller rev. 1.3, one of them, serial nr 62-0104 keeps failing cgminer validation, the other four are working nicely.

spiccioli.

EDIT: a full reset (removing power), it seems SW1 switch 1 OFF is not the same, seems to have solved my issue, now all 5 boards are hashing.
 
sr. member
Activity: 327
Merit: 250
July 30, 2012, 11:21:22 AM
New Results with makomk 160.bit running smooth so far in cgminer 2.6.0.

Its getting there!

ICA 0:                | 357.4/358.3Mh/s | A:194 R:0 HW:0 U:  4.50/m
ICA 1:                | 361.1/355.3Mh/s | A:205 R:0 HW:0 U:  4.75/m
Nice! Out of interest, did you have trouble getting the board to pass cgminer's validation? I'm hoping I found the cause of that problem and fixed it, but...

Ive never had that error before and cgminer started right up, that's also running with 2 Actual Icarus units. I stopped and started it about 5 times as I moved it from the laptop I program them on to where they actually sit and they started up great each time. I havent written these to flash yet so they are still working with the temporary flash.

One thing I added to make these work better was a powered USB from Zefir's Advice, before the powered USB I was unable to get the 140 bitstream to work.
sr. member
Activity: 462
Merit: 251
July 30, 2012, 11:04:15 AM
Ok I have just added what is our official Glasswalker2 release to zip that you download from http://www.enterpoint.co.uk/cairnsmore/cairnsmore1_support_materials.html for the Glasswalker Controller. With serial nos 0051 and onwards boards we would expect 3 FPGA positions to run with this build at 175MHz. You probably only get 2 to run on a pre-0051 at the moment with this particular build.

We do have other taylored versions of this build running at 200 MHz, in 2 FPGAs, on a couple of pre 0051 test boards that we have for testing. We are looking at a pile of options and seeing what we can achieve on these earlier boards and this will take some time to complete. We are looking to get this up to 3 or 4 FPGAs if it is possible and we are investigating the possible issues that are currently restricting us going to 3 or 4 FPGAs.

In a similar vein we are also looking to get 4 FPGAs on the post 0050 boards. We are running a large sample with the 175MHz build on 3 FPGAs as an extended production test now and those appear stable in this setup.

I am struggling to find time to be on this forum currently so I may well be out of date or not aware of things happening here currently due to many commitments including helping the team to make this all work. So I am not answering things here it's because  I am otherwise engaged.
hero member
Activity: 686
Merit: 564
July 30, 2012, 11:01:19 AM
New Results with makomk 160.bit running smooth so far in cgminer 2.6.0.

Its getting there!

ICA 0:                | 357.4/358.3Mh/s | A:194 R:0 HW:0 U:  4.50/m
ICA 1:                | 361.1/355.3Mh/s | A:205 R:0 HW:0 U:  4.75/m
Nice! Out of interest, did you have trouble getting the board to pass cgminer's validation? I'm hoping I found the cause of that problem and fixed it, but...
sr. member
Activity: 327
Merit: 250
July 30, 2012, 10:38:29 AM
New Results with makomk 160.bit running smooth so far in cgminer 2.6.0.

Its getting there!

ICA 0:                | 357.4/358.3Mh/s | A:194 R:0 HW:0 U:  4.50/m
ICA 1:                | 361.1/355.3Mh/s | A:205 R:0 HW:0 U:  4.75/m

Doff
member
Activity: 108
Merit: 10
July 30, 2012, 10:01:11 AM
Strange, with 2 COMS I have 1 FPGA working each instead of 2 per COM.  It only reports 140/140 not 280/280.  Board # 171. Controller version 1.3.

what worker are you using? If you use mine, please use the icarus now. My worker was only for the twin_test.bit.

I'm using MBPM with the icarus worker.
member
Activity: 108
Merit: 10
July 30, 2012, 10:00:33 AM
Strange, with 2 COMS I have 1 FPGA working each instead of 2 per COM.  It only reports 140/140 not 280/280.  Board # 171. Controller version 1.3.

misternoodle,

do you have SW3/SW4 switches correctly set?

They have to be ON-OFF-ON-ON

spiccioli.

I will check when I get home tonight. They might be all on, but not 100% sure. 

Thanks.
sr. member
Activity: 397
Merit: 500
July 30, 2012, 09:55:20 AM
Strange, with 2 COMS I have 1 FPGA working each instead of 2 per COM.  It only reports 140/140 not 280/280.  Board # 171. Controller version 1.3.

what worker are you using? If you use mine, please use the icarus now. My worker was only for the twin_test.bit.
legendary
Activity: 1379
Merit: 1003
nec sine labore
July 30, 2012, 09:50:49 AM
Strange, with 2 COMS I have 1 FPGA working each instead of 2 per COM.  It only reports 140/140 not 280/280.  Board # 171. Controller version 1.3.

misternoodle,

do you have SW3/SW4 switches correctly set?

They have to be ON-OFF-ON-ON

spiccioli.
member
Activity: 108
Merit: 10
July 30, 2012, 09:32:55 AM
Strange, with 2 COMS I have 1 FPGA working each instead of 2 per COM.  It only reports 140/140 not 280/280.  Board # 171. Controller version 1.3.
Pages:
Jump to: