Topic: [ANN][BLC] Blakecoin Blake-256 for GPU/FPGA With Merged Mined Pools Stable Net - page 169. (Read 409569 times)

no good.

just in case flipped each switch back and forth to make sure all in correct positions (power off)

Doing reload again

flip switch 3 back while still on and connected to virtual box?

Cool, I just checked and its OK to run from the home directory

So flip the switch (3), confirm the red LEDs are flashing, init 0, replug the usb and give it a whirl 

Moving (and renaming ) file was going to be my next try but I was able to get good loads on 2nd try on p0 p1 and 1st trys on p2 p3

retried a few more times now have p0-p3 loaded no errors but lights are yellow red

You should (probably - see below) move the bitfile into the xc3sprog  directory
cd
mv CM1-hv-v04a-80MHz-ucf-75-fmax-78.bit xc3sprog
It helps to use tab for filename completion, also renaming the bit file to hv.bit makes typing a lot quicker

Bear with me a few minutes and I'll check out if it really matters which directory you run the commands from.

if I CD into xc3sprog it fails unble to find the bit file

if I co back up one level (where .bit file is then I get


xc3sprog -c cm1 -v -p0 CM1-hv-v04a-80MHz-ucf-75-fmax-78.bit

--snip--

p0 device failed to configure instruction capture is 0x3f
USB transactions: Write 2175 read 60 reties 2

thanks!

OK. You'll have to reprogram it (its only temporary unless you flash the MSC ROMs, which I don't recommend until we've got a good working version of the bitstream).

The way to tell the difference between my firmware and the bitcoin version is that the blue/green leds are swapped.

On bitcoin blue flashes as work is sent, and green flashes for a hash.
On blakecoin green flashes as work is sent, and blue flashes for a hash.

The difference is pretty obvious as the work is sent all together, while hashes occur randomly.

Anyway, to program ... power off the board, set the switches

x
x
x
x

x
    x  (three = program)
x      (two = fan override, switch this if not using the fans)
x

Wait for it to initialise, sequentially first blue, then red/yellow.

Start up your VirtualBox, login root/password
cd xc3sprog
xc3sprog -c cm1 -v -p0 CM1-hv-v04a-80MHz-ucf-75-fmax-78.bit
LEDs will go blue on one device
If all goes well, after 20 seconds you'll see red/yellow/green, and the green will fade
Repeat for p1 p2 p3
If instead it stays blue, just move on to the next one, once all four are blue, start from p0 again and it should work this time.
Now set the switches all in the ON position (assuming you've got the fan(s) connected, else switch 2 goes OFF)

x
x
x
x

x
x
x     (two = fan override, switch this if not using the fans)
x

The red LEDs should start flashing slowly (about once per second)
Type "init 0" (that's zero) to shutdown the VirtualBox, wait until closed
Disconnect and reconnect the USB
Now start the cgminer. You should get four blue flashes as they are detected (unfortunately the old bitcoin bitstream will also do this, but the blakecoin one will now give regular green flashes with occasional blue, while bitcoin gives regular blue ones with occasional green).

If it works, you can try the faster bitstreams, and eventually try flashing to ROM which will make them permanent via "xc3sprog -c cm1 -p0 -Ixc6lx150.bit CM1-hv-v04a-80MHz-ucf-75-fmax-78.bit"

altered switches
ok were blue at powerup then turned red/yellow

com 20-23 is my com ports also

got 3 test failed one failed to open (com22)

My configuration ...

x
x
x
x

x
x
  x
x

Switch 2 is the fan override since I'm not using the supplied fans. Switch 5 is the clock speed setting, needs to be in the opposite direction for the hashvoodo firmware.

this is my current config
holding board with 4 & 6 pin power pointing left (green phoniex on top)
switches as follow

x
x
x
  x

x
x
x
x

this is what CM1Quickstart calls Mining software configuration

Turn switch 3 back on, the red LEDs should start to blink. If you used the VirtualBox instance to program the devices, shut it down (init 0), unplug then replug the USB cable, then start cgminer (runblake.bat).

May not have loaded bitsteam correctly

all 4 have yellow and red solid led no blue 
slow red blinker center of board

progress

got icarus fails so tried -notest version


so it's sorta running

Yep, sorry its a bit rough at the moment. I wrote some quick notes here https://github.com/kramble/FPGA-Blakecoin-Miner/blob/master/cgminer/cgminer-3.1.1/README.txt

I did dry to get it working on cgminer 3.4.3 (the latest version that included ztex support), but no joy, its broken (works on ztex though) .

I'll make a start on BFGminer tomorrow, cgminer just doesn't seem to support the CM1 (kano didn't get his dev board, so no surprise there, its not easy to code blind without hardware to test on).

ok add these to your cgminer folder its the dependancies for kramble's mod should fix that issue
https://www.dropbox.com/s/xa01f9hhakpsexv/cgminer-3.1.1-blakefpga.zip

Now I get program cannot start because libsub-1.0.dll is missing

are you sure that is the right cgminer?

use the version kramble has modded as the newer versions of cgminer don't support the -S option any more
https://www.dropbox.com/s/m18kr3kgrl102w2/cgminer-311-2013-11-16-CM1.exe

EDit Wrong cgminer was using one for GPU. D/L correct one now. 

new hashvoodo loaded as controller
hashvoodoo_controller_25.bit

bitstream loaded on p0-p3
CM1-hv-v04a-80MHz-ucf-75-fmax-78.bit

Can't get cgminer to run WIn7

D:\Coin_Wallets\Miners\cgminer-blake256>D:\Coin_Wallets\Miners\cgminer-blake256\
cgminer -T --disable-gpu -S \\.\COM20 -S \\.\COM21 -S \\.\COM22 -S \\.\COM23 --u
rl localhost:8772 -u mogrith -p xxxx  2>log.txt
 [2013-11-17 12:28:43] cgminer: -S: unrecognized option

yes I see what you mean  

I have tested with a modified stratum proxy and the block candidate is still rejected but I have not yet tried with a modified block submission method and the modified stratum proxy at the same time this is the only way I can think of to avoid a calculation error like the one you are suggesting

only issue with that fix is the pool has a lot more duplicate shares that get submitted