Custom FPGA Board for Sale!

[Dexter770221]

A quick guide how to synthesize a project in ISE WebPack 13.2 would also be very helpful. And for Altera users how to do it in Quartus...
I'm trying for 4 hours at least and nothing. Errors, errors... I've tried to synthesize LX150_makomk_Test. Becuse WebPack have limits I've change LOOP_LOG2 to 1. Any help?
TIA.

[fpgaminer]

A quick guide how to synthesize a project in ISE WebPack 13.2 would also be very helpful. And for Altera users how to do it in Quartus...
I'm trying for 4 hours at least and nothing. Errors, errors... I've tried to synthesize LX150_makomk_Test. Becuse WebPack have limits I've change LOOP_LOG2 to 1. Any help?
TIA.

For ISE you simply load the xise project file, make sure fpgaminer_top is selected in the Hierarchy in the upper-left, and then double click "Generate Programming File" in Processes in the lower-left.

For Quartus you can just load the project and press Ctrl+L. There should also be a menu options under Processing.

Let me know what errors you are getting or what the specific trouble is. Please note that the LX150_makomk_Test project won't compile on WebPack. You'd have to target a different device (LX75 or below).

[fpgaminer]

Fantastic work, molecular! I freed up a Linux machine last week for my lab, so I can certainly give your guide a try

[UrJtag ... ] maybe we can even program with this tool, I don't know. Anyone?

Okay, here's the deal with UrJTAG. I wanted to completely replace the ISE requirement on these X5000 boards by using UrJTAG which works on multiple platforms, at least Linux and Windows. Using UrJTAG would completely eliminate the need to use ISE for mining, because it can both program the FPGA and communicate with it to push and pull work.

Now, UrJTAG states explicitly in their documentation that support for Xilinx Platform Cables is experimental and slow. I figured I didn't have any other options, so I gave it a try anyway. Long story short, I can program an FPGA using UrJTAG and my Platform Cable, but it takes ten or more minutes to do so. I also have terrible trouble with the drivers, which need to be re-installed every time I boot my system.

I have not given up on using UrJTAG. I dug into its code for xpc_ext. It's fairly simple code, and it looks like the reason why it's so slow is because they're using a slow, GPIO bit-bang mode of the platform cable, whereas ISE would normally use special JTAG specific modes. So with some hard work it might be possible to fix UrJTAG's support of xpc_ext, and I have that on my TODO list. Don't expect it next or week or anything like that; I have a lot to clear off my plate and the work is non-trivial. But it would be kind of fun to get working

[Dexter770221]

Let me know what errors you are getting or what the specific trouble is. Please note that the LX150_makomk_Test project won't compile on WebPack. You'd have to target a different device (LX75 or below).

I'm synthesize it for LX75.
Errors:
HDLCompiler:1654 - "...\LX150_makomk_Test\hdl\sha256_transform.v" Line 290: Instantiating <e0_blk> from unknown module <e0>
HDLCompiler:1654 - "...\LX150_makomk_Test\hdl\sha256_transform.v" Line 266: Instantiating <s0_blk> from unknown module <s0>
... and 4 warnings about identifiers being never used...
TIA.

[molecular]

Fantastic work, molecular! I freed up a Linux machine last week for my lab, so I can certainly give your guide a try

[UrJtag ... ] maybe we can even program with this tool, I don't know. Anyone?

Okay, here's the deal with UrJTAG. I wanted to completely replace the ISE requirement on these X5000 boards by using UrJTAG which works on multiple platforms, at least Linux and Windows. Using UrJTAG would completely eliminate the need to use ISE for mining, because it can both program the FPGA and communicate with it to push and pull work.

Now, UrJTAG states explicitly in their documentation that support for Xilinx Platform Cables is experimental and slow. I figured I didn't have any other options, so I gave it a try anyway. Long story short, I can program an FPGA using UrJTAG and my Platform Cable, but it takes ten or more minutes to do so. I also have terrible trouble with the drivers, which need to be re-installed every time I boot my system.

I have not given up on using UrJTAG. I dug into its code for xpc_ext. It's fairly simple code, and it looks like the reason why it's so slow is because they're using a slow, GPIO bit-bang mode of the platform cable, whereas ISE would normally use special JTAG specific modes. So with some hard work it might be possible to fix UrJTAG's support of xpc_ext, and I have that on my TODO list. Don't expect it next or week or anything like that; I have a lot to clear off my plate and the work is non-trivial. But it would be kind of fun to get working

So many good and bad news in one post

Awesome that urJTAG can, in fact, be used for programming, I was really hoping that. Too bad it's using this bit-bang mode. 10 minutes is a tad too slow.

I also noticed another problem (not urJTAG-related): Once I plug in some other usb device (a hub in this case) on another port of the computer the miner is connected to (haven't verified if it's the same usb host), the "cable" gets "stuck" (for lack of other words). When starting the miner, it says "Cable locked, unlocking...." (or similar), but it does not succeed. The workaround is to use "Reset Cable" in Impact. Any ideas about that? Does it happen to you?

[molecular]

Holy shit, I thought I fried my x5000 for a minute there.

I fed it 12V. The tiny fan of the X5000 immediately gave me an audible clue (lawnmower-style) that I fed it more Voltage than it expected. Took me about 2 seconds to realize that and unplug it.

It survived!!!

Now I have a problem: I've got quite a weird setup for the PC I want to use the X5000 with:


large image: https://i.imgur.com/tDusj.jpg

Problem is: I'm using a pico-psu similar to this one: http://www.mini-box.com/s.nl/it.A/id.417/.f (you can see it at the top of the motherboard, plugged into the atx power connector) which is operating close to it's maximum capacity. Using one of the molex plugs coming out of it (this is not shown in the picture, which is older) for the X5000 (sharing it with the harddrive) causes the harddrive to behave erratically, so I'm guessing this is too much for the tiny thing and it's probably dropping Voltage.

So I thought I could connect the X5000 directly to the primary PSU delivering the 12V for the pico psu, assuming the red wire on molex was 12V instead of 5V for some reason (WRONG!)

Would've been quite elegant.

What are the input Voltage specs for the X5000? I assume it's not a good idea to operate it with 12V input voltage, right? (the fan could be adapted)

I'd hate to have to use yet another PSU for providing 5V to the X5000. Any ideas?

[fizzisist]

molecular, that's a sweet little setup. I think that's a smart idea to bypass the picoPSU, and I'm surprised it doesn't seem to be working. I didn't actually help design the X5000, but I'm 90% sure it's running on 12V. I believe it should accept between 6 and 20V. Are you sure that the primary PSU is outputting 12V? Maybe it's a bit higher? It could just be the fan that doesn't like the voltage. Are you sure you had the voltage going to the right pin?

It's a mystery, but hopefully li_gangyi can shed some light on it soon.

[molecular]

molecular, that's a sweet little setup. I think that's a smart idea to bypass the picoPSU, and I'm surprised it doesn't seem to be working. I didn't actually help design the X5000, but I'm 90% sure it's running on 12V. I believe it should accept between 6 and 20V. Are you sure that the primary PSU is outputting 12V? Maybe it's a bit higher? It could just be the fan that doesn't like the voltage. Are you sure you had the voltage going to the right pin?

It's a mystery, but hopefully li_gangyi can shed some light on it soon.

Why mystery? If what you're saying about the input voltage requirements is correct, it all makes perfect sense. Note that the fan is connected directly to the input plug. It's a 5V fan. Does not surprise me its going berserker when fed 12V.

It would be totally awesome if I could put 12V. I'm not sure the fan is really necessary, the cooling block does not seem to get even slightly warm (to my finger, that is, so it's subjective). I could always adjust the fan's voltage using a resistor.

li_gangyi will soon clear up the fog, I assume.

[li_gangyi]

Hi there,

Yeah it's 12V input to the board and 5v to the fan for the X5000. Anywhere between 6V and 19v should be fine.

Without the fan the heatsink does get quite warm, warm enough to warrant the fan.

[molecular]

Hi there,

Yeah it's 12V input to the board and 5v to the fan for the X5000. Anywhere between 6V and 19v should be fine.

Without the fan the heatsink does get quite warm, warm enough to warrant the fan.

Thanks, Li, for your answer. *whips out ohm-meter and soldering iron*

[thirdlight]

I'm pleased to report that my X5000 arrived today!

However... I've followed molecular's guide, I seem to get the board programmed, but when I try to ./mine.sh, I get:

Code:

ERROR: ld.so: object '~/x5000/usb-driver-HEAD-913cbbf/libusb-driver.so' from LD_PRELOAD cannot be preloaded: ignored.
Sourcing from XIL_CSE_TCL: /opt/Xilinx/13.2/ISE_DS/ISE/cse/tcl ...
Found /opt/Xilinx/13.2/ISE_DS/ISE/cse/tcl/../../lib/lin/libCseJtagTcl.so...
Loading CseJtag Global Variables...
Found /opt/Xilinx/13.2/ISE_DS/ISE/cse/tcl/../../lib/lin/libCseFpgaTcl.so...
Loading CseFpga Global Variables...
Found /opt/Xilinx/13.2/ISE_DS/ISE/cse/tcl/../../lib/lin/libCseCoreTcl.so...
Loading CseCore Global Variables...
Found /opt/Xilinx/13.2/ISE_DS/ISE/cse/tcl/../../lib/lin/libCseVIOTcl.so...
Loading CseVIO Global Variables...
Info: OS platform = i686.
Info:Connecting to cable (Usb Port - USB21).
Info:Checking cable driver.
Info:File version of /opt/Xilinx/13.2/ISE_DS/ISE/cse/tcl/../../bin/lin/xusbdfwu.hex = 1030.
Info:File version of /usr/share/xusbdfwu.hex = 1030.
Info: Using libusb.
Info: Kernel release = 2.6.35-30-generic.
Info: Max current requested during enumeration is 280 mA.
ERROR set configuration. strerr=Device or resource busy.
Info:write cmdbuffer failed 20000020.
ERROR claiming interface.
ERROR setting interface.
control tranfer failed.
Info:write cmdbuffer failed 20000020.
control tranfer failed.
Info:Loopback test failed. Sent character = 00, Received character = 00.
Info:Cable connection failed.
Status returned CSE_FAILURE
    while executing
"csejtag_target open $handle  $CABLE_NAME  0  $CABLE_ARGS"
    (procedure "initChipScopeVIO" line 15)
    invoked from within
"initChipScopeVIO $handle"
    (procedure "main" line 10)
    invoked from within
"main $argc $argv"
    (file "mine.tcl" line 351)

Any suggestions?

[molecular]

I'm pleased to report that my X5000 arrived today!

However... I've followed molecular's guide, I seem to get the board programmed, but when I try to ./mine.sh, I get:

Code:

ERROR: ld.so: object '~/x5000/usb-driver-HEAD-913cbbf/libusb-driver.so' from LD_PRELOAD cannot be preloaded: ignored.
Sourcing from XIL_CSE_TCL: /opt/Xilinx/13.2/ISE_DS/ISE/cse/tcl ...
Found /opt/Xilinx/13.2/ISE_DS/ISE/cse/tcl/../../lib/lin/libCseJtagTcl.so...
Loading CseJtag Global Variables...
Found /opt/Xilinx/13.2/ISE_DS/ISE/cse/tcl/../../lib/lin/libCseFpgaTcl.so...
Loading CseFpga Global Variables...
Found /opt/Xilinx/13.2/ISE_DS/ISE/cse/tcl/../../lib/lin/libCseCoreTcl.so...
Loading CseCore Global Variables...
Found /opt/Xilinx/13.2/ISE_DS/ISE/cse/tcl/../../lib/lin/libCseVIOTcl.so...
Loading CseVIO Global Variables...
Info: OS platform = i686.
Info:Connecting to cable (Usb Port - USB21).
Info:Checking cable driver.
Info:File version of /opt/Xilinx/13.2/ISE_DS/ISE/cse/tcl/../../bin/lin/xusbdfwu.hex = 1030.
Info:File version of /usr/share/xusbdfwu.hex = 1030.
Info: Using libusb.
Info: Kernel release = 2.6.35-30-generic.
Info: Max current requested during enumeration is 280 mA.
ERROR set configuration. strerr=Device or resource busy.
Info:write cmdbuffer failed 20000020.
ERROR claiming interface.
ERROR setting interface.
control tranfer failed.
Info:write cmdbuffer failed 20000020.
control tranfer failed.
Info:Loopback test failed. Sent character = 00, Received character = 00.
Info:Cable connection failed.
Status returned CSE_FAILURE
    while executing
"csejtag_target open $handle  $CABLE_NAME  0  $CABLE_ARGS"
    (procedure "initChipScopeVIO" line 15)
    invoked from within
"initChipScopeVIO $handle"
    (procedure "main" line 10)
    invoked from within
"main $argc $argv"
    (file "mine.tcl" line 351)

Any suggestions?

I think I never saw this in my test.

Two suggestions:

• try the urJTAG tool. try to load the cable driver and detect the chain (whatever all that means)
• try keeping impact open after programming, then before starting mine.sh, use "Reset Cable" in the menu

[thirdlight]

Thanks. molecular, for the fast reply!

I changed

Code:

export LD_PRELOAD=~/x5000/usb-driver-HEAD-913cbbf/libusb-driver.so

to

Code:

export LD_PRELOAD=/home/myusername/x5000/usb-driver-HEAD-913cbbf/libusb-driver.so

in miner.sh, and now have 4 shares accepted at bitcoins.lc!

Getting quite a few

Code:

Info: Cable is LOCKED. Retrying...

Is that a problem?

Thanks

[molecular]

Thanks. molecular, for the fast reply!

I changed

Code:

export LD_PRELOAD=~/x5000/usb-driver-HEAD-913cbbf/libusb-driver.so

to

Code:

export LD_PRELOAD=/home/myusername/x5000/usb-driver-HEAD-913cbbf/libusb-driver.so

in miner.sh, and now have 4 shares accepted at bitcoins.lc!

Getting quite a few

Awesome!

Code:

Info: Cable is LOCKED. Retrying...

Is that a problem?

Only if it persists. I sometimes see this on startup, too. Sometimes it can't "unlock the cable", I then use impact "Reset Cable", then it usually works again. If all fails, I replug the USB cable.

If you gain any knowledge about this, let me know.

[molecular]

ok, finally got the x5000 powered by the main PSU (220V->12V) and got around to posting to "Pictures of you mining rigs" thread: https://bitcointalk.org/index.php?topic=7216.820

I'm now feeding only the 12V (black/yellow) of the molex connector and using a (I think 100 Ohm) resistor that I soldered to the molex connector on board to supply (whatever Voltage that boils down to) to the 5V fan. Seems to work... any thoughts?

[thirdlight]

I sometimes see this on startup, too.

It did settle down, but still see it occasionally.

I'm not too worried, as the pool is reporting > 100MH/s (114 at the moment, 30 minute average) and Flexible Mining Proxy reports between 93 & 97 MH/s (60 minute average).

I'll test against some other pools later, but for now I'm happy to just sit back & watch the bitcents trickle in!

[molecular]

I sometimes see this on startup, too.

It did settle down, but still see it occasionally.

I'm not too worried, as the pool is reporting > 100MH/s (114 at the moment, 30 minute average) and Flexible Mining Proxy reports between 93 & 97 MH/s (60 minute average).

I'll test against some other pools later, but for now I'm happy to just sit back & watch the bitcents trickle in!

On another note, this happens to me at times.
I think it's triggered by usb action of other devices (when I plug in/out other stuff). I'm not sure how this comes about. Have to restart mine.sh, then it works again.

Code:

Info:write cmdbuffer failed FFFFFFED.
ERROR! Waiting to try again ...
usb_transfer: -19 (error sending control message: No such device)
Info:write cmdbuffer failed FFFFFFED.
ERROR! Waiting to try again ...
usb_transfer: -19 (error sending control message: No such device)
Info:write cmdbuffer failed FFFFFFED.
ERROR! Waiting to try again ...
usb_transfer: -19 (error sending control message: No such device)
Info:write cmdbuffer failed FFFFFFED.
ERROR! Waiting to try again ...

[fizzisist]

Hi there,

Yeah it's 12V input to the board and 5v to the fan for the X5000. Anywhere between 6V and 19v should be fine.

Without the fan the heatsink does get quite warm, warm enough to warrant the fan.

Ah, the mystery to me was that the photo in the first post showed the fan connected to 12V, so I couldn't understand why the fan was going nuts. Nevermind!

I'm now feeding only the 12V (black/yellow) of the molex connector and using a (I think 100 Ohm) resistor that I soldered to the molex connector on board to supply (whatever Voltage that boils down to) to the 5V fan. Seems to work... any thoughts?

That resistor could be dissipating a lot a power if you do that, probably almost a watt. Unless it's rated for that, it might suddenly or gradually die on you. A better option might be to take the 5V from the picoPSU, if you have a way to do it.

[molecular]

Ah, the mystery to me was that the photo in the first post showed the fan connected to 12V, so I couldn't understand why the fan was going nuts. Nevermind!

Not quite right either. It was a total fuckup by me. I put 12V on the 5V part of the molex. That's why it might make the impression that the fan is connected to 12V part of molex if you assume I connected the molex right, which I didn't. So the fan was connected to 12V via the 5V pins of the connector. That's why it went berserker.

I'm now feeding only the 12V (black/yellow) of the molex connector and using a (I think 100 Ohm) resistor that I soldered to the molex connector on board to supply (whatever Voltage that boils down to) to the 5V fan. Seems to work... any thoughts?

That resistor could be dissipating a lot a power if you do that, probably almost a watt. Unless it's rated for that, it might suddenly or gradually die on you. A better option might be to take the 5V from the picoPSU, if you have a way to do it.

I = 12V / 100 Ohm = 0.12A
0.12A * 7V = 0.82 VA

Did I calculate that right?

What happens when the resistor dies? Does it shorcut or does it break the connection?

Taking the 5V from the picu psu would be possible by investing more cable and soldering.

[molecular]

Is there any chance to get more than the 100 MHash/s out of a x5000? Can the changes to the "software" you made for x6*00 be "backported"?