README.ASIC 6.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184
  1. SUPPORTED DEVICES
  2. Currently supported ASIC devices include Avalon, Bitfountain's Block Erupter
  3. series (both USB and blades), a large variety of Bitfury-based miners,
  4. Butterfly Labs' SC range of devices, Klondike modules, and KnCMiner's Mercury,
  5. Jupiter and Saturn.
  6. AVALON
  7. ------
  8. Currently, Avalon boards are supported only by connecting them directly (or via
  9. a hub) to a regular PC running BFGMiner. It is also possible to install the
  10. OpenWrt packages of BFGMiner to the Avalon's embedded controller, but this is
  11. not a simple task due to its lack of available flash space.
  12. To use the Avalon from a regular PC, you will need to specify two options:
  13. First, add the -S option specifying the avalon driver specifically. For example,
  14. -S avalon:\\.\COM9
  15. Next, use the --avalon-options copying the command as used by the internal
  16. router used by the Avalon. eg:
  17. --avalon-options 115200:24:10:45:282
  18. The values are baud : miners : asic count : timeout : frequency.
  19. Baud:
  20. The device is essentially hard coded to emulate 115200 baud so you shouldn't
  21. change this.
  22. Miners:
  23. Most Avalons are 3 module devices, which come to 24 miners. 4 module devices
  24. would use 32 here.
  25. Asic count:
  26. Virtually all have 10, so don't change this.
  27. Timeout:
  28. This defines how long the device will work on a work item before accepting new
  29. work to replace it. It should be changed according to the frequency (last
  30. setting).
  31. It is possible to set this a little lower if you are trying to tune for short
  32. block mining (eg p2pool) but much lower and the device will start creating
  33. duplicate shares.
  34. Sample settings for valid different frequencies (last 2 values):
  35. 34:375
  36. 36:350
  37. 39:325
  38. 43:300
  39. 45:282
  40. 47:270
  41. 50:256
  42. Frequency:
  43. This is the clock speed of the devices. Only specific values work, 256, 270,
  44. 282 (default), 300, 325, 350 and 375.
  45. If you use the full curses based interface with Avalons you will get this
  46. information:
  47. AVA 0: 22/ 46C 60%/2400R
  48. The values are:
  49. ambient temp / highest device temp set fan % / lowest detected fan RPM.
  50. Check the API for more detailed information.
  51. BFSB, MEGABIGPOWER, AND METABANK BITFURY BOARDS
  52. -----------------------------------------------
  53. Both BFSB and MegaBigPower (V2 only at this time) boards are supported with the
  54. "bfsb" driver. Metabank boards are supported with the "metabank" driver. These
  55. drivers are not enabled by default, since they must be run on a Raspberry Pi in
  56. a specific hardware configuration with the boards. To enable them, you must
  57. build with --enable-bfsb or --enable-metabank. Do not try to use these drivers
  58. without the manufacturer-supported hardware configuration! Also note that these
  59. drivers do not properly support thermal shutdown at this time, and without
  60. sufficient cooling you may destroy your board or chips!
  61. To start BFGMiner, ensure your Raspberry Pi's SPI is enabled (you can run the
  62. raspi-config utility for this). For Metabank boards, you must also load the I2C
  63. drivers (do not try to modprobe both with a single command; it won't work):
  64. modprobe i2c-bcm2708
  65. modprobe i2c-dev
  66. Then you must run BFGMiner as root, with the proper driver selected.
  67. For example:
  68. sudo bfgminer -S bfsb:auto
  69. BIG PICTURE MINING BITFURY USB
  70. ------------------------------
  71. These miners are sensitive to unexpected data. Usually you can re-plug them to
  72. reset to a known-good initialisation state. To ensure they are properly detected
  73. and used with BFGMiner, you must specify -S bigpic:all (or equivalent) options
  74. prior to any other -S options (which might probe the device and confuse it).
  75. BLOCK ERUPTER BLADE
  76. -------------------
  77. Blades communicate over Ethernet using the old but simple getwork mining
  78. protocol. If you build BFGMiner with libmicrohttpd, you can have it work with
  79. one or more blades. First, start BFGMiner with the --http-port option. For
  80. example:
  81. bfgminer --http-port 8330
  82. Then configure your blade to connect to your BFGMiner instance on the same port,
  83. with a unique username per blade. It will then show up as a SGW device and
  84. should work more or less like any other miner.
  85. BLOCK ERUPTER USB
  86. -----------------
  87. These will autodetect if supported by the device; otherwise, you need to use
  88. the '--scan-serial erupter:<device>' option to tell BFGMiner what device to
  89. probe; if you know you have no other serial devices, or only ones that can
  90. tolerate garbage, you can use '--scan-serial erupter:all' to probe all serial
  91. ports. They communicate with the Icarus protocol, which has some additional
  92. options in README.FPGA
  93. KLONDIKE
  94. --------
  95. --klondike-options <arg> Set klondike options clock:temptarget
  96. KNCMINER
  97. --------
  98. KnCMiner rigs use a BeagleBone Black (BBB) as the host; this is pluged into a
  99. "cape" with a FPGA and connections for 4-6 ASIC modules (depending on the cape
  100. version). Note that in addition to the usual dependencies, this driver also
  101. requires i2c-tools (aka libi2c-dev on some systems). The BBB comes with the
  102. Ångström Distribution by default. The following is a step by step install for
  103. BFGMiner on this system;
  104. -----------------Start------------
  105. cat >/etc/opkg/feeds.conf <<\EOF
  106. src/gz noarch http://feeds.angstrom-distribution.org/feeds/v2013.06/ipk/eglibc/all/
  107. src/gz base http://feeds.angstrom-distribution.org/feeds/v2013.06/ipk/eglibc/cortexa8hf-vfp-neon/base/
  108. src/gz beaglebone http://feeds.angstrom-distribution.org/feeds/v2013.06/ipk/eglibc/cortexa8hf-vfp-neon/machine/beaglebone/
  109. EOF
  110. opkg update
  111. opkg install angstrom-feed-configs
  112. rm /etc/opkg/feeds.conf
  113. opkg update
  114. opkg install update-alternatives
  115. opkg install automake autoconf make gcc cpp binutils git less pkgconfig-dev ncurses-dev libtool nano bash i2c-tools-dev
  116. while ! opkg install libcurl-dev; do true; done
  117. ln -s aclocal-1.12 /usr/share/aclocal
  118. curl http://www.digip.org/jansson/releases/jansson-2.0.1.tar.bz2 | tar -xjvp
  119. cd jansson-2.0.1
  120. ./configure --prefix=/usr CC=arm-angstrom-linux-gnueabi-gcc --disable-static NM=arm-angstrom-linux-gnueabi-nm
  121. make install && ldconfig
  122. cd ..
  123. git clone git://github.com/luke-jr/bfgminer
  124. cd bfgminer
  125. ./autogen.sh
  126. git clone git://github.com/troydhanson/uthash
  127. ./configure --host=arm-angstrom-linux-gnueabi --enable-knc CFLAGS="-I$PWD/uthash/src -O0 -ggdb"
  128. make AR=arm-angstrom-linux-gnueabi-ar
  129. /etc/init.d/cgminer.sh stop
  130. ./bfgminer -S knc:auto -c /config/cgminer.conf
  131. ---------------END-------------
  132. ---
  133. This code is provided entirely free of charge by the programmer in his spare
  134. time so donations would be greatly appreciated. Please consider donating to the
  135. address below.
  136. Luke-Jr <luke-jr+bfgminer@utopios.org>
  137. 1QATWksNFGeUJCWBrN4g6hGM178Lovm7Wh