Pages:
Author

Topic: High Efficiency FPGA & ASIC Bitcoin Mining Devices https://BTCFPGA.com - page 94. (Read 218469 times)

hero member
Activity: 896
Merit: 1000
Buy this account on March-2019. New Owner here!!
I am back in town now and back to my full working schedule

My first priority today is to get caught up on emails, anyone that is waiting for an email response will get one today

I will also start processing refunds for those who are eligible and who requested them

I need to talk to Luke-JR and see where we are at with everything and I will give an update later today

I will also make myself available on IRC on Freenode Network today in #BTCFPGA for anyone that wants live support

Glad to be back, time to roll up my sleeves and get back to work. Do not worry I will get to everyone and their issues today.

Thanks! Smiley

donator
Activity: 980
Merit: 1004
felonious vagrancy, personified
and which file(s) are that "relevant source code"?

There is a lovely file called README with the answer to your question.
legendary
Activity: 2576
Merit: 1186
It also looks like you're going to be forced to use some bloaty Java mining software provided by him if you want to use his bitstream
Completely incorrect FUD.
Hey, don't quote out of context! If it's incorrect, how about answering his reasoning too?
as he didn't release sufficient information to allow this to be ported to cgminer or MPBM.


The statement is simply incorrect, period.

The source code for all of the software is included in the jar file.  You can see every last line of code.  Everything you could possibly want to know is in there.

So, like I said, his statement is completely incorrect.
So what GPL-compatible license is the relevant source code available under, and which file(s) are that "relevant source code"?
full member
Activity: 134
Merit: 100
I request cancellation of one order
I requested a cancellation of my orders too.
No reply since 6/28. Guess they are working hard on correcting the problems. They are honest guys, so I'm not worried.
donator
Activity: 980
Merit: 1004
felonious vagrancy, personified
It also looks like you're going to be forced to use some bloaty Java mining software provided by him if you want to use his bitstream
Completely incorrect FUD.
Hey, don't quote out of context! If it's incorrect, how about answering his reasoning too?
as he didn't release sufficient information to allow this to be ported to cgminer or MPBM.


The statement is simply incorrect, period.

The source code for all of the software is included in the jar file.  You can see every last line of code.  Everything you could possibly want to know is in there.

So, like I said, his statement is completely incorrect.
legendary
Activity: 2576
Merit: 1186
It also looks like you're going to be forced to use some bloaty Java mining software provided by him if you want to use his bitstream
Completely incorrect FUD.
Hey, don't quote out of context! If it's incorrect, how about answering his reasoning too?
as he didn't release sufficient information to allow this to be ported to cgminer or MPBM.
donator
Activity: 980
Merit: 1004
felonious vagrancy, personified
How long until that new bitstream to take the boards to over 1GH/s@50W be ready?

That depends on E.T. and how soon he makes the bitstream available

I'm still waiting for your reply.
donator
Activity: 980
Merit: 1004
felonious vagrancy, personified
It also looks like you're going to be forced to use some bloaty Java mining software provided by him if you want to use his bitstream

Completely incorrect FUD.
donator
Activity: 980
Merit: 1004
felonious vagrancy, personified
legendary
Activity: 2576
Merit: 1186
Quick update from me... today I completed getting a basic firmware running complete with LED flashing and (very simple) command line interface. I also began writing the JTAG driver to talk to the FPGA(s): you can see my current draft of this here. The good news (or at least, interesting to me) is that this is looking like it might even be possible to chain multiple FPGAs (or even other devices) on each socket in the future, but I suppose that depends a lot on what hardware cablepair plans.

Also wanted to drop a note of thanks to TheSeven for helping me reverse engineer some of the pinouts last week. Anyone interested in keeping up with the latest on this free firmware in real time is welcome to join us on Freenode's #BTCFPGA channel.
hero member
Activity: 866
Merit: 1001
Any updates on fixes and when new boards are due out?

Phil
legendary
Activity: 1512
Merit: 1000
member
Activity: 112
Merit: 10
legendary
Activity: 1512
Merit: 1000
I cannot rule out a hardware issue with the backplane yet - hence cablepair's offer of replacement backplanes in case a MCU update can't solve it.

How fortunate that stcupp was innovative enough to design the modminer in a modular way.
The least expensive part of the hardware can easily be swapped out. Cudos for the for-though.

kind regards

FTFY
member
Activity: 112
Merit: 10
I cannot rule out a hardware issue with the backplane yet - hence cablepair's offer of replacement backplanes in case a MCU update can't solve it.

How fortunate that stcupp was innovative enough to design the modminer in a modular way.
The least expensive part of the hardware can easily be swapped out. Cudos for the for-though.

kind regards
legendary
Activity: 2576
Merit: 1186
TECHNICAL ISSUES:
Several people have reported that only 3 out of 4 of the cards are working, Luke-JR has done some testing and discovered there is a problem with the MCU that may be fixed with a firmware update.
Just to clarify, I cannot rule out a hardware issue with the backplane yet - hence cablepair's offer of replacement backplanes in case a MCU update can't solve it.
hero member
Activity: 896
Merit: 1000
Buy this account on March-2019. New Owner here!!
Notice To Customers 06/26/2012

First off I appreciate all of your kindness and patience, you gentlemen have been incredibly understanding as we try to work out these issues

I am sorry I have not been able to field many emails over the last couple of days, I had some family business to deal with out of town, I am currently up in the Adirondack mountains staying with family and there is no stable internet access and I need to go to the library for public wifi just to get online, but I will try to get online at least every other day to deal with customer issues until I return home on 07/01 - at that time my regular every day business / customer service activities will resume as usual.

Many of you have not received your orders, or have received incomplete orders.  Many of you who have received ModMiner Quads but they are not operating the way they are supposed to. Many of you have asked questions and need more information hopefully this notice gives you the information you need, if not please feel free to email me at [email protected] with any more specific questions / information

TECHNICAL ISSUES:
Several people have reported that only 3 out of 4 of the cards are working, Luke-JR has done some testing and discovered there is a problem with the MCU that may be fixed with a firmware update. This will allow all ModMiner Quads that you currently have and ModMiner Quads we will ship in the future to operate at the full capacity of 840 mhash as promised and work with CGMINER as promised.

I have hired Luke-JR as a private contractor to develop open source firmware for the ModMiner Quad to fix this issue. This is something he is currently working on and we hope to have good news some time this week.


REFUNDS / REPLACEMENTS:

For ANY current customer that has a ModMiner Quad and is not able to get it working to full capacity with the above mentioned firmware update we will ship replacement ModMiner Quad back planes to you free of charge.

For customers who are still waiting for their shipments please accept my apologies. Stcupp stopped production of the units due to this discovered bug and it has been suspended until the bug has been fixed.

There is a very small amount of customers that received a tracking number via email (From me) but the tracking never updated because the unit was not shipped. This is because of production slowing down / stopping in between me releasing your order from NY to ship from the production site in WV.

For those customers (who received tracking numbers but the shipments never actually went out) I will give you a 9% refund immediately if you have not already received it. I will also offer a complete refund and cancellation of the orders for these customers who request it.

For customers who are in their fifth week since they placed their order and have not already received their 9% refund please email me at [email protected] and include a Bitcoin address. I will get the refund to you immediately.

TECHNICAL SUPPORT:
Please feel free to post technical questions about the ModMiner Quad here in this thread. Stcupp will answer them when he is available and also Luke-JR is being paid an hourly wage as a sub-contractor and I will be happy to pay him to answer any technical questions that are posted.

PRODUCTION:
As I have mentioned before we are moving production to a professional manufacturing facility, this is ready to begin as soon as this MCU bug is fixed. As soon as this bug is fixed we will begin mass production and customers will enjoy very fast shipment and small lead times.

Thank you for bearing with us through this ordeal, I am sorry these problems happened however please know - we are doing everything we can to correct them and get your ModMiner Quads shipped and working at full capacity.





legendary
Activity: 960
Merit: 1028
Spurn wild goose chases. Seek that which endures.
Good news: kernel recognizes the card and the "cdc_acm" driver creates a USB serial device file (/dev/ttyACM0).
Bad news: MPBM doesn't see the card. Neither does BFGMiner.

What worker module should I be using? Do I need to download any FPGA firmware?

Edit: Again, thanks to Luke I was able to sort it out. Now to see if it'll program properly.
legendary
Activity: 960
Merit: 1028
Spurn wild goose chases. Seek that which endures.
http://fs07n5.sendspace.com/dl/56045c81d8dc87863633a93d98caa90a/4fe0dd5d18e34a41/0ixpqy/MMQ.zip

Reset button is on the left
ISP button is on the right

To do the update:

Hold BOTH the Reset and ISP buttons
Release the Reset button while still holding the ISP button
Release the ISP button
Unplug USB and plug it back in, the board will now show up as a mass storage device
Open the MSD and you should see one file named firmware.bin
Delete firmware.bin and copy the new firmware file to the device
If running linux make sure you sync/unmount the drive first
Unplug USB, hit the Reset button, and plug USB back in
The firmware is now updated.
For Linux, it isn't quite that simple. Apparently the MCU has a buggy implementation of USB Mass Storage and/or VFAT, and goes crazy with Linux's vfat driver. But it's still possible to do, using GNU Mtools (package "mtools" under Debian,Ubuntu,Gentoo):
Code:
mdel -i /dev/disk/by-id/usb-NXP_LPC134X_IFLASH_ISP000000000-0:0 ::/firmware.bin
mcopy -i /dev/disk/by-id/usb-NXP_LPC134X_IFLASH_ISP000000000-0:0 MCU.bin ::/
Hooboy. This... might explain the issues I've been having. Gonna try it.
legendary
Activity: 2576
Merit: 1186
http://fs07n5.sendspace.com/dl/56045c81d8dc87863633a93d98caa90a/4fe0dd5d18e34a41/0ixpqy/MMQ.zip

Reset button is on the left
ISP button is on the right

To do the update:

Hold BOTH the Reset and ISP buttons
Release the Reset button while still holding the ISP button
Release the ISP button
Unplug USB and plug it back in, the board will now show up as a mass storage device
Open the MSD and you should see one file named firmware.bin
Delete firmware.bin and copy the new firmware file to the device
If running linux make sure you sync/unmount the drive first
Unplug USB, hit the Reset button, and plug USB back in
The firmware is now updated.
For Linux, it isn't quite that simple. Apparently the MCU has a buggy implementation of USB Mass Storage and/or VFAT, and goes crazy with Linux's vfat driver. But it's still possible to do, using GNU Mtools (package "mtools" under Debian,Ubuntu,Gentoo):
Code:
mdel -i /dev/disk/by-id/usb-NXP_LPC134X_IFLASH_ISP000000000-0:0 ::/firmware.bin
mcopy -i /dev/disk/by-id/usb-NXP_LPC134X_IFLASH_ISP000000000-0:0 MCU.bin ::/
Pages:
Jump to: