vs3 (OP)
|
|
May 11, 2014, 06:08:58 AM |
|
Ok, so now I have fully populated the board. And it is now detecting the bitfury chip also, yet another victory haha. with HID driver: https://i.imgur.com/CqBj6Oq.pngWith winusb driver: https://i.imgur.com/sLvg172.pngBut the hashrate is still 0. I will do some more testing, but I wanted to let you guys know I got a little further again. 2 things: 1) make sure you've ran the nf1init program - bfgminer will NOT recognize the device unless the product string says NanoFury 2) if you already did 1) then make sure that the WinUSB driver has been uninstalled when testing with HID - the two are incompatible (and it's somewhat tricky to uninstall the zadig stuff). Run the nf1init program and if it detects the device then bfgminer should detect it as well. If it doesn't - then you're using most likely the winusb driver (and not the HID one). Also - I'm presuming that you're trying with a fully populated board (not just barely the MCP2210 stuff).
|
|
|
|
Dexter770221
Legendary
Offline
Activity: 1029
Merit: 1000
|
|
May 11, 2014, 07:42:18 AM |
|
Anyone got luck with cgminer 4.3.3 and more chips than 6? With 6 chips I got ~10.5 GH, with more chips it's dropping.
|
Under development Modular UPGRADEABLE Miner (MUM). Looking for investors. Changing one PCB with screwdriver and you have brand new miner in hand... Plug&Play, scalable from one module to thousands.
|
|
|
mikerbiker6
|
|
May 11, 2014, 11:46:47 AM |
|
2 things: 1) make sure you've ran the nf1init program - bfgminer will NOT recognize the device unless the product string says NanoFury 2) if you already did 1) then make sure that the WinUSB driver has been uninstalled when testing with HID - the two are incompatible (and it's somewhat tricky to uninstall the zadig stuff). Run the nf1init program and if it detects the device then bfgminer should detect it as well. If it doesn't - then you're using most likely the winusb driver (and not the HID one). Yeah, I was already trying that but I thought, let you know I came this far. Sorry but I have no idea which file to run, since I don't know visual basic. I don't see an executable and the batch file just pops up and disappears. I downloaded visual studio, but there are 10 types of visual studios: express, studio express, basic, premium, ultimate, server, tool builder,..... I downloaded basic express and c++. Then ran nf1_init.vcxproj Readme tells me the cpp file is the source file, so open that. Then I press F5. but building fails. Probably I am just running the wrong file, but this is not explained in either github, nor the readme's.
|
Participate and Earn on the Letstalkbitcoin forum letstalkbitcoin.com
|
|
|
vs3 (OP)
|
|
May 11, 2014, 04:12:10 PM |
|
Then ran nf1_init.vcxproj
that's probably the reason - you need to open the "solution" file - NanoFury_Init\nf1_init.sln There is also a dependency with the HID library - there is a .bat file in the same folder that checks out that and puts it where it needs to go - just run it once before you open the solution file.
|
|
|
|
mikerbiker6
|
|
May 12, 2014, 09:45:20 AM |
|
Then ran nf1_init.vcxproj
that's probably the reason - you need to open the "solution" file - NanoFury_Init\nf1_init.sln There is also a dependency with the HID library - there is a .bat file in the same folder that checks out that and puts it where it needs to go - just run it once before you open the solution file. https://www.youtube.com/watch?v=eeBtCo1T4Jw&feature=youtu.beWhat I am doing is not what I think I should be doing.
|
Participate and Earn on the Letstalkbitcoin forum letstalkbitcoin.com
|
|
|
[gadget]
Newbie
Offline
Activity: 30
Merit: 0
|
|
May 12, 2014, 01:44:03 PM |
|
Hi guys, have leftover chips (Bitfury rev2) from a project - 22 in total. Offering them for sale at $6/chip. This is cheaper than buying from bitfurystrikesback, and I'm in the US, so save further on shipping. Pm me if interested. https://i.imgur.com/PtQOF1s.jpg
|
|
|
|
vs3 (OP)
|
|
May 12, 2014, 09:57:37 PM |
|
Then ran nf1_init.vcxproj
that's probably the reason - you need to open the "solution" file - NanoFury_Init\nf1_init.sln There is also a dependency with the HID library - there is a .bat file in the same folder that checks out that and puts it where it needs to go - just run it once before you open the solution file. https://www.youtube.com/watch?v=eeBtCo1T4Jw&feature=youtu.beWhat I am doing is not what I think I should be doing. There seems to be something not happening correctly with checking out the project or some dependency might be missing... I just tried this: C:\TMP\nf>git clone https://github.com/nanofury/NanoFury_Init.git Cloning into 'NanoFury_Init'... remote: Counting objects: 42, done. remote: Compressing objects: 100% (26/26), done. remote: Total 42 (delta 16), reused 42 (delta 16) Unpacking objects: 100% (42/42), done. Checking connectivity... done
C:\TMP\nf>dir Volume in drive C is DISK_C Volume Serial Number is AD41-1280
Directory of C:\TMP\nf
05/12/2014 14:44 <DIR> . 05/12/2014 14:44 <DIR> .. 05/12/2014 14:44 <DIR> NanoFury_Init 0 File(s) 0 bytes 3 Dir(s) 10,660,360,192 bytes free
C:\TMP\nf>cd NanoFury_Init
C:\TMP\nf\NanoFury_Init>git_clone_MCP2210-Library.bat
C:\TMP\nf\NanoFury_Init>cd nf1_init
C:\TMP\nf\NanoFury_Init\nf1_init>git clone https://github.com/nanofury/MCP2210-Library.git Cloning into 'MCP2210-Library'... remote: Reusing existing pack: 958, done. remote: Counting objects: 13, done. remote: Compressing objects: 100% (8/8), done. remote: Total 971 (delta 6), reused 6 (delta 5) Receiving objects: 100% (971/971), 421.01 KiB | 606.00 KiB/s, done. Resolving deltas: 100% (725/725), done. Checking connectivity... done
C:\TMP\nf\NanoFury_Init\nf1_init> C:\TMP\nf\NanoFury_Init\nf1_init>dir Volume in drive C is DISK_C Volume Serial Number is AD41-1280
Directory of C:\TMP\nf\NanoFury_Init\nf1_init
05/12/2014 14:44 <DIR> . 05/12/2014 14:44 <DIR> .. 05/12/2014 14:45 <DIR> MCP2210-Library 05/12/2014 14:44 3,431 nf1_init.cpp 05/12/2014 14:44 5,275 nf1_init.vcxproj 05/12/2014 14:44 2,600 nf1_init.vcxproj.filters 05/12/2014 14:44 15,387 nf_spidevc.cpp 05/12/2014 14:44 3,588 nf_spidevc.h 05/12/2014 14:44 21,583 nf_spitest.cpp 05/12/2014 14:44 1,685 nf_spitest.h 05/12/2014 14:44 1,722 ReadMe.txt 05/12/2014 14:44 295 stdafx.cpp 05/12/2014 14:44 535 stdafx.h 05/12/2014 14:44 314 targetver.h 05/12/2014 14:44 327,181 tvec.c 12 File(s) 383,596 bytes 3 Dir(s) 10,656,903,168 bytes free
C:\TMP\nf\NanoFury_Init\nf1_init>cd .. C:\TMP\nf\NanoFury_Init>start nf1_init.sln C:\TMP\nf\NanoFury_Init> then in Visual Studio I selected from the menu->build->clean, then build->Build Solution and got this output: 1>------ Build started: Project: nf1_init, Configuration: Debug Win32 ------ 1> stdafx.cpp 1> tvec.c 1> hid.c 1> Generating Code... 1> nf_spitest.cpp 1>c:\tmp\nf\nanofury_init\nf1_init\nf_spitest.cpp(274): warning C4101: 'i' : unreferenced local variable 1>c:\tmp\nf\nanofury_init\nf1_init\nf_spitest.cpp(273): warning C4101: 'st' : unreferenced local variable 1>c:\tmp\nf\nanofury_init\nf1_init\nf_spitest.cpp(395): warning C4996: 'localtime': This function or variable may be unsafe. Consider using localtime_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. 1> c:\program files\microsoft visual studio 10.0\vc\include\time.inl(112) : see declaration of 'localtime' 1> nf_spidevc.cpp 1>c:\tmp\nf\nanofury_init\nf1_init\nf_spidevc.cpp(238): warning C4996: 'wcscpy': This function or variable may be unsafe. Consider using wcscpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. 1> c:\program files\microsoft visual studio 10.0\vc\include\string.h(283) : see declaration of 'wcscpy' 1> nf1_init.cpp 1> mcp2210.cpp 1>c:\tmp\nf\nanofury_init\nf1_init\mcp2210-library\mcp2210.cpp(116): warning C4244: '=' : conversion from 'unsigned long' to 'byte', possible loss of data 1> Generating Code... 1> Creating library C:\TMP\nf\NanoFury_Init\Debug\nf1_init.lib and object C:\TMP\nf\NanoFury_Init\Debug\nf1_init.exp 1> Creating library C:\TMP\nf\NanoFury_Init\Debug\nf1_init.lib and object C:\TMP\nf\NanoFury_Init\Debug\nf1_init.exp 1> nf1_init.vcxproj -> C:\TMP\nf\NanoFury_Init\Debug\nf1_init.exe ========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
(and you can ignore the warnings - some of them come from butfury's code, some are from the MCP2210 library and some are leftovers from my tests - I may clean them up at some point but for the moment they're mostly harmless) Or if you have in your path "C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE" you can also build it from the command prompt: C:\TMP\nf\NanoFury_Init>devenv nf1_init.sln /rebuild Debug
Microsoft (R) Visual Studio Version 10.0.40219.1. Copyright (C) Microsoft Corp. All rights reserved. 1>------ Rebuild All started: Project: nf1_init, Configuration: Debug Win32 ------ 1> stdafx.cpp 1> tvec.c 1> hid.c 1> Generating Code... 1> nf_spitest.cpp 1>c:\tmp\nf\nanofury_init\nf1_init\nf_spitest.cpp(274): warning C4101: 'i' : unreferenced local variable 1>c:\tmp\nf\nanofury_init\nf1_init\nf_spitest.cpp(273): warning C4101: 'st' : unreferenced local variable 1>c:\tmp\nf\nanofury_init\nf1_init\nf_spitest.cpp(395): warning C4996: 'localtime': This function or variable may be unsafe. Consider using localtime_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. 1> c:\program files\microsoft visual studio 10.0\vc\include\time.inl(112) : see declaration of 'localtime' 1> nf_spidevc.cpp 1>c:\tmp\nf\nanofury_init\nf1_init\nf_spidevc.cpp(238): warning C4996: 'wcscpy': This function or variable may be unsafe. Consider using wcscpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details. 1> c:\program files\microsoft visual studio 10.0\vc\include\string.h(283) : see declaration of 'wcscpy' 1> nf1_init.cpp 1> mcp2210.cpp 1>c:\tmp\nf\nanofury_init\nf1_init\mcp2210-library\mcp2210.cpp(116): warning C4244: '=' : conversion from 'unsigned long' to 'byte', possible loss of data 1> Generating Code... 1> Creating library C:\TMP\nf\NanoFury_Init\Debug\nf1_init.lib and object C:\TMP\nf\NanoFury_Init\Debug\nf1_init.exp 1> Creating library C:\TMP\nf\NanoFury_Init\Debug\nf1_init.lib and object C:\TMP\nf\NanoFury_Init\Debug\nf1_init.exp 1> nf1_init.vcxproj -> C:\TMP\nf\NanoFury_Init\Debug\nf1_init.exe ========== Rebuild All: 1 succeeded, 0 failed, 0 skipped ==========
C:\TMP\nf\NanoFury_Init>
|
|
|
|
mikerbiker6
|
|
May 13, 2014, 05:51:35 PM |
|
Tried 10 different combinations of building but no luck. Is it possible to just send me the executable?
|
Participate and Earn on the Letstalkbitcoin forum letstalkbitcoin.com
|
|
|
vs3 (OP)
|
|
May 13, 2014, 07:49:55 PM |
|
Tried 10 different combinations of building but no luck. Is it possible to just send me the executable?
I've PMd you the link.
|
|
|
|
mikerbiker6
|
|
May 16, 2014, 06:25:56 PM |
|
Tried 10 different combinations of building but no luck. Is it possible to just send me the executable?
I've PMd you the link. Thanks, managed to get the init program to work on a different computer. (I have gathered some screenshots.) Then I ran bfgminer on my old computer with the serials: https://www.youtube.com/watch?v=tuLzgFW4XVY&feature=youtu.beIt thinks it is a klondike apparently. But on my other pc it is recognized as NFY . One step further! But then I get this: repeating units of "bitfury_init_oldbuf:giving up after 4 tries"
|
Participate and Earn on the Letstalkbitcoin forum letstalkbitcoin.com
|
|
|
Taugeran
|
|
May 16, 2014, 07:04:28 PM |
|
Tried 10 different combinations of building but no luck. Is it possible to just send me the executable?
I've PMd you the link. Thanks, managed to get the init program to work on a different computer. (I have gathered some screenshots.) Then I ran bfgminer on my old computer with the serials: https://www.youtube.com/watch?v=tuLzgFW4XVY&feature=youtu.beIt thinks it is a klondike apparently. But on my other pc it is recognized as NFY . One step further! But then I get this: repeating units of "bitfury_init_oldbuf:giving up after 4 tries" On the PC that runs the nF-init program, connect the NFY, and run the init with FixID This will give it the proper id to be picked up
|
Bitfury HW & Habañero : 1.625Th/s tips/Donations: 1NoS89H3Mr6U5CmP4VwWzU2318JEMxHL1 Come join Coinbase
|
|
|
vs3 (OP)
|
|
May 16, 2014, 09:54:59 PM |
|
repeating units of "bitfury_init_oldbuf:giving up after 4 tries"
This indicates that there is something wrong with the communication between MCP2210 and the bitfury chip. When bfgminer is running (or use nf1_init with the test parameter) check all voltages, check also all tracks for shorts. If you have oscilloscope check voltage levels and signal shape at the 3 pins (it is important that the "high" level is above the 0.86V which is used for reference - by design it should be in the 1.2-1.8V range) Check in this order: - shorts or missing components or bad solders on any tracks - 1.8V - 0.8V (should actually be around 0.86V unless you've picked different resistor values for the power converter chip) If all of those are good then as soon as you start the chip it should get hot. You can also start the chip with osc6 bits 5 or 10 and check oscillations on that pin (nf1_init configures the chip to send those out).
|
|
|
|
mikerbiker6
|
|
May 17, 2014, 09:41:20 AM |
|
On the PC that runs the nF-init program, connect the NFY, and run the init with FixID
This will give it the proper id to be picked up
What should I add in the command line to activate fixid? @Vs3, the voltage on pin 4 of the bitfury chip is 1.8V. I checked it. Did you mean that?
|
Participate and Earn on the Letstalkbitcoin forum letstalkbitcoin.com
|
|
|
Taugeran
|
|
May 17, 2014, 02:08:08 PM |
|
On the PC that runs the nF-init program, connect the NFY, and run the init with FixID
This will give it the proper id to be picked up
What should I add in the command line to activate fixid? @Vs3, the voltage on pin 4 of the bitfury chip is 1.8V. I checked it. Did you mean that? It's just nf1_init.exe fixID No hyphens
|
Bitfury HW & Habañero : 1.625Th/s tips/Donations: 1NoS89H3Mr6U5CmP4VwWzU2318JEMxHL1 Come join Coinbase
|
|
|
mikerbiker6
|
|
May 17, 2014, 04:28:15 PM Last edit: May 17, 2014, 05:11:19 PM by mikerbiker6 |
|
On the PC that runs the nF-init program, connect the NFY, and run the init with FixID
This will give it the proper id to be picked up
What should I add in the command line to activate fixid? @Vs3, the voltage on pin 4 of the bitfury chip is 1.8V. I checked it. Did you mean that? It's just nf1_init.exe fixID No hyphens Haha, that kinda makes sense. I used fixID and bfgminer now detects the miner directly,( with -S all at the end.) But it is not hashing, which I think must then be some kind of hardware problem.
|
Participate and Earn on the Letstalkbitcoin forum letstalkbitcoin.com
|
|
|
pauljbl
Newbie
Offline
Activity: 39
Merit: 0
|
|
May 17, 2014, 09:14:19 PM |
|
I've added support for NF2 and NF6 into cgminer git master branch. I'm not getting much love out of the NF6 just yet but they may well need so much power that even a regular USB3 port is not enough. The NF2s are behaving very nicely. This is at --nfu-bits 54: 14: NF2 00001099: | 4.670G / 4.655Gh/s WU: 65.2/m 23: NF2 00000753: | 4.447G / 4.509Gh/s WU: 63.6/m
Hi I see there is support for nf2 and nf6 could you add support for nanofurys devices that are chained together as I have 5 nanofurys chained. And also to set the bit speed of each individual bitfury chip. This is possible in bfgminer Thanks Paul
|
|
|
|
mikerbiker6
|
|
May 19, 2014, 08:50:03 PM |
|
Can someone please post the BOM for the NF1. Just to make sure I haven't got any wrong components.
|
Participate and Earn on the Letstalkbitcoin forum letstalkbitcoin.com
|
|
|
|
|
pinkfloyd11
Newbie
Offline
Activity: 56
Merit: 0
|
|
May 21, 2014, 02:22:33 PM |
|
|
|
|
|
|