Bitcoin Forum
December 10, 2016, 03:12:05 PM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 [93] 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 »
  Print  
Author Topic: Cairnsmore1 - Quad XC6SLX150 Board  (Read 251420 times)
Isokivi
Hero Member
*****
Offline Offline

Activity: 924


Items flashing here available at btctrinkets.com


View Profile WWW
August 07, 2012, 01:26:53 PM
 #1841

I am very pleased to report that the bitminter-mining client would now seem to support and work with carinsmore1's solong as they have an icarus compatible bitstream in them.
I can report hashing, valid shares and the mining speed being about what it should be with makomk's 200 and 180mhs shortfin icarus bitstreams.

This is a java-based, extremeley easy to use miner that is tied to a specific pool (bitminter). I mine at this pool and consider it the best one out there. Infact the only non-awesome thing about the client is that it is not open sourced, for obvious reasons.
You can find the beta-client that supports icarus at:

 http://bitminter.com/beta/beta.jnlp

The pools website is:

https://bitminter.com/
It's a mid-sized rapidly growing pool. That is hop-proof, pays tx-fees, merged mining.

To try it out you'll need to:
1. register an account.
2. dl and run the client.
3. select devices->probe all ports for fgpas.
4. wait for ~20sec per fgpa for the client to figure out timings (yes automatic!)
5. feel your ass grow as the coins roll in.

See you on the leaderboards.

[edit]
Looks like there might be some issues to work out, but I cant submit 100% accurate reports for drharibo (pool op and developer of the client) because I dont have a 100% working hub/cable setup (hub#3, cable #13 in try now).
If someone with a rock-solid setup tests this, please drop drharibo a line or two. He can be found here on the forums and on irc at freenode.

Bitcoin trinkets now on my online store: btc trinkets.com <- Bitcoin Tiepins, cufflinks, lapel pins, keychains, card holders and challenge coins.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481382725
Hero Member
*
Offline Offline

Posts: 1481382725

View Profile Personal Message (Offline)

Ignore
1481382725
Reply with quote  #2

1481382725
Report to moderator
1481382725
Hero Member
*
Offline Offline

Posts: 1481382725

View Profile Personal Message (Offline)

Ignore
1481382725
Reply with quote  #2

1481382725
Report to moderator
1481382725
Hero Member
*
Offline Offline

Posts: 1481382725

View Profile Personal Message (Offline)

Ignore
1481382725
Reply with quote  #2

1481382725
Report to moderator
steamboat
Hero Member
*****
Offline Offline

Activity: 648


View Profile
August 07, 2012, 05:31:53 PM
 #1842

ebereon,

how many boards do you have running per instance of cgminer?

EDIT: I've gotten 8 boards running fine in 2 instances of cgminer (any more than 4 per instance crashes it for some reason???) but I can't seem to get my 9th to get detected.

as per Ebereons instructions, I've identified the boards usb's. I've uninstalled w/ and w/out deleting the drivers, and w/ and w/out uninstalling the com's ports associated w/ the board. Each time, the board re-installs to the same coms, which gives me

[2012-08-04 21:39:32] Started cgminer 2.6.2a
 [2012-08-04 21:39:32] Icarus Detect: Test failed at \\.\COM20: get 00000000, should: 000187a2
 [2012-08-04 21:39:32] Icarus Detect: Test failed at \\.\COM21: get 00000000, should: 000187a2

every time. No clue where to begin figuring out this issue, any help would be greatly appreciated.

Thanks,

Steamboat

I don't use cgminer yet, just tested it after mpbm was working without problems. Make sure all boards accept the 190Mh bitstream, best joice is mpbm and check 1 day the invalids. If you have invalids >3% on some pair, use a slower bitstream. If now all works in mpbm with <3% invalids, then i'm sure all boards will be working with cgminer too.

eb

I have no idea where to begin w/ configuring MPBM. haven't been able to find any documentation

ASIC miners available for purchase

Those who serve best, profit most.
hm
Member
**
Offline Offline

Activity: 106


View Profile
August 07, 2012, 05:42:32 PM
 #1843

I succeeded to revert controller firmware from glasswalker to v1.3 after numerous tries. Strangely, it never worked with switch3=off & switch6=off. So I turned switch3=off and switch6=on, and voilà .. immediate success. I must have misunderstood the dip switch settings tables.

Then I flashed latest makomk 140 bitstream, but my board #62-0017 has still low or unstable hash rates.
The best bitstream for me was still twin_test, it hashed at its full speed at least for some hours per day, but in the rest of the day it showed very unstable hash rates.

I hope my board can be fixed soon, I already wrote to support on sunday night/monday morning.
LazyOtto
Sr. Member
****
Offline Offline

Activity: 476


View Profile
August 07, 2012, 06:52:02 PM
 #1844

I have no idea where to begin w/ configuring MPBM. haven't been able to find any documentation
Info can be dug out of this thread:
https://bitcointalk.org/index.php?topic=62823.0

But mind you the thread starts out talking about setting it up with an editable config file but the current version *must* be configured by the web interface found at http://<host address where mpbm is running>:8832/

Somewhere along the thread it switches over but I don't recall where. Probably around June 2012.

First, set up some "Work sources". There is an example 'work source group' with a few 'work sources' created on first run. (Or, you can leave these be until you have a proven "Worker" setup and you'll just donate a few shares to the author. This would probably be best - start with a 'known working' configuration for the sources until you know your hardware is configured / working.)

Second, create a "Worker" for each 'hash producer' / unit of hardware. E.g., one for a BFL, one for an icarus, apparently two for a CM1.

Explore the menu items and drop down lists.

Easiest to use under Linux, probably (isn't everything Smiley); I have it running on OS X 10.7 where I had to patch two lines for the BFL worker to function under Python 3.
steamboat
Hero Member
*****
Offline Offline

Activity: 648


View Profile
August 07, 2012, 07:43:29 PM
 #1845

This is a make-shift guide for windows users for faster, permanent flashing. I have not yet tested it, but apparrentley Slipbye has had succes with it. It also gets us out of the virtual machine (for good ?)

21:13] <TheSeven> http://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.6.0/libusb-win32-devel-filter-1.2.6.0.exe/download
[21:14] <TheSeven> install that, make sure the board to be flashed is plugged, start the libusb filter wizard
[21:14] <TheSeven> select the USB composite device which shows an ID of 0403 8350
[21:14] <TheSeven> install the filter driver for that
[21:14] <TheSeven> download this: https://xc3sprog.svn.sourceforge.net/svnroot/xc3sprog/trunk/xc3sprog.exe
[21:14] <TheSeven> create a new file called cablelist.txt in the same directory
[21:15] <TheSeven> put this line inside that file:
[21:15] <TheSeven> cm1 ftdi 20000000 0x0403:0x8350:
[21:15] <TheSeven> open a command prompt in the directory where the files are and run these commands:
[21:15] <TheSeven> set CABLEDB=cablelist.txt
[21:15] <TheSeven> xc3sprog -c cm1
[21:15] <TheSeven> it should detect the fpgas
a this point you want to copy the .bit files you'll be using to the same folder as xc3sprog is in.
[21:16] <TheSeven> if that worked, you can go ahead with flashing like usual
[21:16] <TheSeven> xc3sprog -c cm1 -p 0 -Ixc6lx150.bit file_to_be_flashed.bit

Enjoy your 1-3hours of spare time per day Smiley

1. Do I need to do this w/ one board plugged in at a time?
2. If I don't, do all boards need to be idle?

I'm getting this error w/ 8 boards mining, 1 board idle.

Could not open FTDI device (using libftdi): unable to claim usb device. Make sur
e the default FTDI driver is not in use
FTD2XX/WIN: Can't set VID/PID to 0403:8350. Expect failure
Using FTD2XX,
JTAG loc.: 0    IDCODE: 0x3401d093      Desc:       XC6SLX150   Rev: C  IR lengt
h: 6
JTAG loc.: 1    IDCODE: 0x3401d093      Desc:       XC6SLX150   Rev: C  IR lengt
h: 6
JTAG loc.: 2    IDCODE: 0x3401d093      Desc:       XC6SLX150   Rev: C  IR lengt
h: 6
JTAG loc.: 3    IDCODE: 0x3401d093      Desc:       XC6SLX150   Rev: C  IR lengt
h: 6

ASIC miners available for purchase

Those who serve best, profit most.
steamboat
Hero Member
*****
Offline Offline

Activity: 648


View Profile
August 07, 2012, 07:45:39 PM
 #1846

I have no idea where to begin w/ configuring MPBM. haven't been able to find any documentation
Info can be dug out of this thread:
https://bitcointalk.org/index.php?topic=62823.0

But mind you the thread starts out talking about setting it up with an editable config file but the current version *must* be configured by the web interface found at http://<host address where mpbm is running>:8832/

Somewhere along the thread it switches over but I don't recall where. Probably around June 2012.

First, set up some "Work sources". There is an example 'work source group' with a few 'work sources' created on first run. (Or, you can leave these be until you have a proven "Worker" setup and you'll just donate a few shares to the author. This would probably be best - start with a 'known working' configuration for the sources until you know your hardware is configured / working.)

Second, create a "Worker" for each 'hash producer' / unit of hardware. E.g., one for a BFL, one for an icarus, apparently two for a CM1.

Explore the menu items and drop down lists.

Easiest to use under Linux, probably (isn't everything Smiley); I have it running on OS X 10.7 where I had to patch two lines for the BFL worker to function under Python 3.

awesome, thanks for the lead

ASIC miners available for purchase

Those who serve best, profit most.
testconpastas2
Full Member
***
Offline Offline

Activity: 199



View Profile
August 08, 2012, 06:36:12 AM
 #1847


1. Do I need to do this w/ one board plugged in at a time?
2. If I don't, do all boards need to be idle?

I'm getting this error w/ 8 boards mining, 1 board idle.

Could not open FTDI device (using libftdi): unable to claim usb device. Make sur
e the default FTDI driver is not in use
FTD2XX/WIN: Can't set VID/PID to 0403:8350. Expect failure
Using FTD2XX,
JTAG loc.: 0    IDCODE: 0x3401d093      Desc:       XC6SLX150   Rev: C  IR lengt
h: 6
JTAG loc.: 1    IDCODE: 0x3401d093      Desc:       XC6SLX150   Rev: C  IR lengt
h: 6
JTAG loc.: 2    IDCODE: 0x3401d093      Desc:       XC6SLX150   Rev: C  IR lengt
h: 6
JTAG loc.: 3    IDCODE: 0x3401d093      Desc:       XC6SLX150   Rev: C  IR lengt
h: 6

what i do is plug only one of the cm1 (which i want to program) in a laptop .uninstall all usb filters ( in the laptop )and install it again for the new board. then that error dissapear

Bitmessage: BM-2DAetLWJBKWHZoPbNCgg5z8jwaPpDYWwd4
gpg key id:C6EF5CE3
makomk
Hero Member
*****
Offline Offline

Activity: 686


View Profile
August 08, 2012, 11:39:41 AM
 #1848

Minor bitstream revision: http://www.makomk.com/~aidan/shortfin-dcmwd-20120808.zip

If you're already running the previous one, there's probably no point upgrading. The only difference is that with this one you should be able to disable the array clock with switch 3, temp-upload a bitstream, and re-enable the array clock without having to mess around with flashing and power cycling the whole board. Once you've got a bitstream flashed and running it shouldn't make much difference.

Quad XC6SLX150 Board: 860 MHash/s or so.
SIGS ABOUT BUTTERFLY LABS ARE PAID ADS
spiccioli
Legendary
*
Offline Offline

Activity: 1376

nec sine labore


View Profile
August 08, 2012, 01:51:06 PM
 #1849

It is the second time that I see an unusual high number of HW: problems

Code:
cgminer version 2.6.1 - Started: [2012-08-07 21:17:00]
--------------------------------------------------------------------------------
 (5s):6845.8 (avg):7432.2 Mh/s | Q:27929  A:111001  R:127  HW:0  E:397%  U:100.1/m
 TQ: 21  ST: 22  SS: 0  DW: 2780  NB: 120  LW: 189336  GF: 17  RF: 0
 Connected to http://eu.ozco.in with LP as user ....
 Block: 000001ed239005bf46732ab08477af4d...  Started: [15:44:09]
--------------------------------------------------------------------------------
 [P]ool management [S]ettings [D]isplay options [Q]uit
 ICA  0:                | 351.4/357.9Mh/s | A:4882 R: 2 HW:  17 U: 4.40/m
 ICA  1:                | 372.5/358.0Mh/s | A:4968 R: 7 HW:7004 U: 4.48/m
 ICA  2:                | 311.4/364.7Mh/s | A:5381 R: 6 HW: 405 U: 4.85/m
 ICA  3:                | 379.5/377.4Mh/s | A:5773 R: 9 HW:3232 U: 5.21/m
 ICA  4:                | 365.8/364.6Mh/s | A:5245 R: 6 HW:   7 U: 4.73/m
 ICA  5:                | 358.8/365.0Mh/s | A:5192 R: 7 HW:   5 U: 4.68/m
 ICA  6:                | 379.6/379.6Mh/s | A:5724 R: 6 HW:   7 U: 5.16/m
 ICA  7:                | 379.5/378.1Mh/s | A:5987 R: 4 HW:  58 U: 5.40/m
 ICA  8:                | 379.7/379.3Mh/s | A:5832 R:10 HW:  14 U: 5.26/m
 ICA  9:                | 379.7/373.4Mh/s | A:5716 R: 7 HW: 263 U: 5.15/m
 ICA 10:                | 379.7/378.8Mh/s | A:5718 R: 7 HW:  34 U: 5.16/m
 ICA 11:                | 379.8/379.8Mh/s | A:5895 R: 5 HW:   5 U: 5.32/m
 ICA 12:                | 344.9/357.8Mh/s | A:5069 R: 2 HW:   7 U: 4.57/m
 ICA 13:                | 353.9/358.1Mh/s | A:5028 R: 6 HW:   1 U: 4.53/m
 ICA 14:                | 379.8/379.1Mh/s | A:5807 R: 3 HW: 940 U: 5.24/m
 ICA 15:                | 379.7/379.3Mh/s | A:5879 R: 6 HW:7012 U: 5.30/m
 ICA 16:                | 378.2/364.2Mh/s | A:5481 R: 7 HW: 416 U: 4.94/m
 ICA 17:                | 379.7/379.4Mh/s | A:5785 R:16 HW:6170 U: 5.22/m
 ICA 18:                | 379.8/378.9Mh/s | A:5725 R: 6 HW:  27 U: 5.16/m
 ICA 19:                | 379.6/379.4Mh/s | A:5919 R: 5 HW:  14 U: 5.34/m
--------------------------------------------------------------------------------

 [2012-08-08 15:45:48] Accepted 0abab2ce.894d460e ICA 5 pool 0
 [2012-08-08 15:45:48] Accepted 6e2644f1.38b5ddd0 ICA 8 pool 0
 [2012-08-08 15:45:49] Accepted 95fe325d.d3a35568 ICA 8 pool 0
 [2012-08-08 15:45:49] Accepted be904261.547a05bb ICA 7 pool 0
 [2012-08-08 15:45:49] Accepted ded736b7.4a9579ab ICA 8 pool 0
 [2012-08-08 15:45:49] Accepted a7b9c5c6.c2379ef4 ICA 0 pool 0
 [2012-08-08 15:45:50] Accepted f25f84ec.c96549cf ICA 9 pool 0
 [2012-08-08 15:45:50] Accepted d76c4fb3.395aa784 ICA 15 pool 0
 [2012-08-08 15:45:52] Accepted b1806040.3c4f3497 ICA 17 pool 0
 [2012-08-08 15:45:52] Accepted c6752272.c4cb99e6 ICA 6 pool 0
 [2012-08-08 15:45:53] Accepted ed9a9ad2.f41377c9 ICA 14 pool 0
 [2012-08-08 15:45:54] Accepted cf152c4e.ca339738 ICA 14 pool 0
 [2012-08-08 15:45:55] Accepted c23deda9.ae9fd167 ICA 14 pool 0
 [2012-08-08 15:45:56] Accepted 1d203a55.33002845 ICA 13 pool 0
 [2012-08-08 15:45:56] Accepted fa14b15b.57442b0a ICA 19 pool 0
 [2012-08-08 15:45:56] Accepted e22bd3f1.c609b40f ICA 17 pool 0
 [2012-08-08 15:45:57] Accepted c66a3ebb.80e9d0fe ICA 11 pool 0
 [2012-08-08 15:45:58] Accepted 07a80eb6.3a611af5 ICA 6 pool 0

ICA 1/3/15/17 have a HW: value which is wrong.

All of these boards are running makomk 190 MH/s bitstream (the older one, without watch dog) but ICA0/1 which are running makomk's dcmwd2 160MH/s one.

What can it be that happens here?

spiccioli
steamboat
Hero Member
*****
Offline Offline

Activity: 648


View Profile
August 08, 2012, 02:31:53 PM
 #1850


1. Do I need to do this w/ one board plugged in at a time?
2. If I don't, do all boards need to be idle?


what i do is plug only one of the cm1 (which i want to program) in a laptop .uninstall all usb filters ( in the laptop )and install it again for the new board. then that error dissapear

I'm using the same laptop to run them as I do to flash them, so I'm trying to not unplug all the boards to flash, guess i'm going to have to Sad


Minor bitstream revision: http://www.makomk.com/~aidan/shortfin-dcmwd-20120808.zip

If you're already running the previous one, there's probably no point upgrading. The only difference is that with this one you should be able to disable the array clock with switch 3, temp-upload a bitstream, and re-enable the array clock without having to mess around with flashing and power cycling the whole board. Once you've got a bitstream flashed and running it shouldn't make much difference.

Can you do this and permanently flash the bitstream?

It is the second time that I see an unusual high number of HW: problems

ICA 1/3/15/17 have a HW: value which is wrong.

All of these boards are running makomk 190 MH/s bitstream (the older one, without watch dog) but ICA0/1 which are running makomk's dcmwd2 160MH/s one.

What can it be that happens here?

spiccioli

what s/n boards do you have? I have 45, 72-80 and i haven't seen ANY HW errors. maybe I don't have cgminer configured correctly to show me them?

ASIC miners available for purchase

Those who serve best, profit most.
spiccioli
Legendary
*
Offline Offline

Activity: 1376

nec sine labore


View Profile
August 08, 2012, 02:37:00 PM
 #1851


It is the second time that I see an unusual high number of HW: problems

ICA 1/3/15/17 have a HW: value which is wrong.

All of these boards are running makomk 190 MH/s bitstream (the older one, without watch dog) but ICA0/1 which are running makomk's dcmwd2 160MH/s one.

What can it be that happens here?

spiccioli

what s/n boards do you have? I have 45, 72-80 and i haven't seen ANY HW errors. maybe I don't have cgminer configured correctly to show me them?

You need to apply a patch to cgminer to see HW: or use the latest version released a couple of days ago, I think it is 2.6.3

spiccioli
toxicocean
Newbie
*
Offline Offline

Activity: 24


View Profile
August 08, 2012, 04:19:28 PM
 #1852

I'm currently running the dcmwd2_200 bitstream on my #0005 board (controller v1.3), and it has been running smooth for a good 42 hours now.
Only thing I noticed is that it seems to be a bit slower than the previous shortfin_190 bitstream (dcmwd2_200 runs at around 722 MH/s, shortfin_190 at about 752 MH/s - as reported by a mining pool. Cgminer reports 775 MH/s for the dcmwd2_200 bitstream and 739 MH/s for the shortfin_190)

makomk
Hero Member
*****
Offline Offline

Activity: 686


View Profile
August 08, 2012, 04:42:13 PM
 #1853

I'm currently running the dcmwd2_200 bitstream on my #0005 board (controller v1.3), and it has been running smooth for a good 42 hours now.
Only thing I noticed is that it seems to be a bit slower than the previous shortfin_190 bitstream (dcmwd2_200 runs at around 722 MH/s, shortfin_190 at about 752 MH/s - as reported by a mining pool. Cgminer reports 775 MH/s for the dcmwd2_200 bitstream and 739 MH/s for the shortfin_190)
Yeah, that can happen, and I can't imagine that the 200 MHz version would run terribly well on a low serial number board. Actually measuring the real effective hash rate is a bit of a pain. Unfortunately not all pools report hash rates as accurately as they perhaps could either.

Quad XC6SLX150 Board: 860 MHash/s or so.
SIGS ABOUT BUTTERFLY LABS ARE PAID ADS
hm
Member
**
Offline Offline

Activity: 106


View Profile
August 08, 2012, 04:53:09 PM
 #1854

is it normal that my board #62-0017 makes a high frequency sound when hashing with glasswalker or makomk bitstreams?

none of the bitstreams I tested is working stable, the best one was still twin_test, though also having instable hash rates, but it had the longest periods of stability per day, i.e. hashing at it's full possible hash rates between zero and 12h per day.

I wonder what I can do to get the good results like e.g. toxicocean. Any tips? I already tried countless combinations of usb cables and hubs without success... A friends board (sn>300) is hashing OK on my setup, but I don't have access to another pre#50 board to compare it to mine, still I don't believe in my USB setup being the cause of my problems.

I appreciate any helpful hints while waiting for RMA. I would even go so far as using my soldering iron to apply the still unknown capacitor fix myself if this doesn't void the warranty.

ps. shortfin_dcmwd2_test_140.bit has between zero and one "Accepted" per "new block", this evening I'll flash the twin_test.
steamboat
Hero Member
*****
Offline Offline

Activity: 648


View Profile
August 08, 2012, 05:08:54 PM
 #1855

is it normal that my board #62-0017 makes a high frequency sound when hashing with glasswalker or makomk bitstreams?

none of the bitstreams I tested is working stable, the best one was still twin_test, though also having instable hash rates, but it had the longest periods of stability per day, i.e. hashing at it's full possible hash rates between zero and 12h per day.

I wonder what I can do to get the good results like e.g. toxicocean. Any tips? I already tried countless combinations of usb cables and hubs without success... A friends board (sn>300) is hashing OK on my setup, but I don't have access to another pre#50 board to compare it to mine, still I don't believe in my USB setup being the cause of my problems.

I appreciate any helpful hints while waiting for RMA. I would even go so far as using my soldering iron to apply the still unknown capacitor fix myself if this doesn't void the warranty.

ps. shortfin_dcmwd2_test_140.bit has between zero and one "Accepted" per "new block", this evening I'll flash the twin_test.

I noticed that one of mine does this as well, and i'm pretty sure it's one of the ones that's getting a low U value in cgminer. I'm going to update the boards to the dcm200 bitstream today or tomorrow and i'll let you know what i find out.

ASIC miners available for purchase

Those who serve best, profit most.
toxicocean
Newbie
*
Offline Offline

Activity: 24


View Profile
August 08, 2012, 08:32:03 PM
 #1856

is it normal that my board #62-0017 makes a high frequency sound when hashing with glasswalker or makomk bitstreams?

I wonder what I can do to get the good results like e.g. toxicocean. Any tips?

I have the high frequency sound also (but not always, or at least I don't always notice it)

hm, if it helps here's a rundown how I program and run mine (#0005) - I assume the controller version is already v1.3, and the drivers are already installed on your programming/mining pc:

- start the enterpoint virtualbox on my pc (I use Windows 7, 64bit)
- set the correct switches on the cairnsmore for programming (at this point the cm is completely off: not powered, and not connected through USB)
  (switches depending on your bitstream, but for the Makomk bitstreams: SW1: 3 off, others on; SW6: 1 off, others on; SW2/SW5: all on; SW3/SW4: 2 off, others on)
- login to the enterpoint virtualbox (root/password)
- power on the cm1 (power only), and wait for about 3 minutes
- connect the cm1 with usb cable to pc
- verify xc3sprog can connect to the cm: xc3sprog -c cm1 -j
- if ok, continue, otherwise start over again from beginning (better to disconnect the cm and reboot the pc at that point to be absolutly sure)
- program the bitstream:
xc3sprog -c cm1 -p0 -Ixc6lx150.bit shortfin_icarus_cm1_test_190_overclock.bit
xc3sprog -c cm1 -p1 -Ixc6lx150.bit shortfin_icarus_cm1_test_190_overclock.bit
xc3sprog -c cm1 -p2 -Ixc6lx150.bit shortfin_icarus_cm1_test_190_overclock.bit
xc3sprog -c cm1 -p3 -Ixc6lx150.bit shortfin_icarus_cm1_test_190_overclock.bit

each command will take some time, haven't checked but I guess around 10 minutes
- if all commands went ok ("Verify: Success!"), power off the cm1, and disconnect USB cable
- set the switches for mining: SW1: 3 on (others stay as they are)
- boot your mining pc/pi/whatever (if you use the programming pc also for mining, reboot it first!)
- power on the cm1 (power only), and wait for about 3 minutes (leds will be blue at the start, and will all turn to orange after some time)
- connect the cm1 with usb cable to pc
- start cgminer (any new version)
Linux: cgminer --quiet --disable-gpu -S /dev/ttyUSB0 -S /dev/ttyUSB1 -S /dev/ttyUSB2 -S /dev/ttyUSB3 -o http://<url>:<port> -O <username>:<pw>
Windows: cgminer --disable-gpu -S \\.\COM21 -S \\.\COM23 -o http://<url>:<port> -O <username>:<pw>
(Starting it like that on Linux will give a warning message that 2 of the devices couldn't be opened, but it will start on the other 2,
on Windows you can also specify \\.\COM20 and \\.\COM22 if the 21 and 23 don't work)
- cm1 should now be mining (leds shouldn't be constantly orange anymore) - let it mine for 48 hours to have stable statistics (MH and U values)

some additional info: I don't use any USB hubs, I just connect straight to my pc; except for mining on my Raspberry Pi, for which I use an unpowered USB hub. To make it work I need to boot the Pi first, enable the ftdi driver (execute with root: modprobe ftdi_sio product=0x8350 vendor=0x0403), connect the unpowered hub first, then connect the c1m to the hub, and then mine.

dunno if this helps...
Entropy-uc
Hero Member
*****
Offline Offline

Activity: 560


View Profile
August 08, 2012, 10:16:03 PM
 #1857

boards which i had thought it was buggy  after a power cycle and plug out plug in usb cycle ( and plugin first "buggy" boards)  it started to work again .  
I ordered new hub switches and new fans but they dont be received till wed/thu , so i will have to wait to test new things.

I'm using w7 64bits and the admin privileges issue ahows up randomly no matter if I'was or not in admin mode , and when it appears allways the board is in "my frozen mode"  COM's OK ,orange led...

you get the same error if you try to run a second instance of cgminer over a running board but in "my" case  it show up slowly as it was checking something on the board.


Edit: not the same in "my case" before the admin privileges line it shows up the lines  
[2012-08-04 21:39:32] Icarus Detect: Test failed at \\.\COM20: get 00000000, should: 000187a2
[2012-08-04 21:39:32] Icarus Detect: Test failed at \\.\COM21: get 00000000, should: 000187a2



what do you mean a second instance of cgminer over a board?

My windows boxes always mine from the last 2 COM ports of any board, and the first board starts with COM20.

So I have always (6 different win7 boxes here) started with -S "\\.\COM22" -S "\\.\COM23"
hm
Member
**
Offline Offline

Activity: 106


View Profile
August 08, 2012, 11:25:13 PM
 #1858

Thank you steamboat, and thank you toxicocean for the detailed description of the flashing process.
I already got twin_test.bit flashed and running (too short to give stats), but tomorrow I'll probably test another one of makomk's bitstreams, following your guide, which differs from my procedure in that I set the DIP switches when the board is already powered up and I connect the USB cable before starting the VM.

I just moved my board some meters away from it's original position, perhaps there's a different level of EM noise from laptop, network switch, external usb/sata hdd, and power cables, which could influence the cm1? I'll see tomorrow after work...

Let's hope that future bitstreams will solve the issues of pre#50 owners.
kano
Legendary
*
Offline Offline

Activity: 1932


Linux since 1997 RedHat 4


View Profile
August 09, 2012, 02:30:23 AM
 #1859


It is the second time that I see an unusual high number of HW: problems

ICA 1/3/15/17 have a HW: value which is wrong.

All of these boards are running makomk 190 MH/s bitstream (the older one, without watch dog) but ICA0/1 which are running makomk's dcmwd2 160MH/s one.

What can it be that happens here?

spiccioli

what s/n boards do you have? I have 45, 72-80 and i haven't seen ANY HW errors. maybe I don't have cgminer configured correctly to show me them?

You need to apply a patch to cgminer to see HW: or use the latest version released a couple of days ago, I think it is 2.6.3

spiccioli

2.6.4a doesn't seem to be counting HW errors.

Kano - is there a plan to get this into the main build?
https://bitcointalk.org/index.php?topic=28402.msg1081302#msg1081302

Pool: https://kano.is BTC: 1KanoiBupPiZfkwqB7rfLXAzPnoTshAVmb
CKPool and CGMiner developer, IRC FreeNode #ckpool and #cgminer kanoi
Help keep Bitcoin secure by mining on pools with Stratum, the best protocol to mine Bitcoins with ASIC hardware
spiccioli
Legendary
*
Offline Offline

Activity: 1376

nec sine labore


View Profile
August 09, 2012, 06:27:53 AM
 #1860


It is the second time that I see an unusual high number of HW: problems

ICA 1/3/15/17 have a HW: value which is wrong.

All of these boards are running makomk 190 MH/s bitstream (the older one, without watch dog) but ICA0/1 which are running makomk's dcmwd2 160MH/s one.

What can it be that happens here?

spiccioli

what s/n boards do you have? I have 45, 72-80 and i haven't seen ANY HW errors. maybe I don't have cgminer configured correctly to show me them?

You need to apply a patch to cgminer to see HW: or use the latest version released a couple of days ago, I think it is 2.6.3

spiccioli

2.6.4a doesn't seem to be counting HW errors.

Kano - is there a plan to get this into the main build?

Sorry,

I was wrong, there is an entry in the Changelog about hardware errors, but it is for modminer, I thought it was for every hashing device.

spiccioli

Pages: « 1 ... 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 [93] 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!