<<  >> (p.4)
    Author Topic: NanoFury Project - Open Source Design  (Read 75719 times)
    This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.

    • rgr_rgr
    Member
    **
    Offline Offline

    Activity: 115
    Merit: 10


    View Profile
    December 21, 2013, 10:10:23 PM
     #61
    I built a few ones for me. A friend of mine reorganised the layout. My fork: https://github.com/rgr-rgr/NanoFury. Pull request sent.

    By the way: I noticed a new version v0.7, not described in the Release_Notes ... ?

  • libertybuck
    Full Member
    ***
    Offline Offline

    Activity: 137
    Merit: 100


    View Profile
    December 22, 2013, 03:31:03 AM
     #62
    Sorry I have a silly question. Does the microchip PIC need NOT firmware ?  I could not find it from github.
    Driving safely with Android phone

  • Beastlymac
    Hero Member
    *****
    Offline Offline

    Activity: 630
    Merit: 501


    Miner Setup And Reviews. WASP Rep.


    View Profile
    December 22, 2013, 03:46:40 AM
     #63
    The device interacts directly with bfgminer so no it doesn't have any firmware.
    Message me if you have any problems

  • marto74
    Hero Member
    *****
    Offline Offline

    Activity: 728
    Merit: 500



    View Profile WWW
    December 22, 2013, 10:29:26 AM
     #64
    HI,
    here is our cgminer support

    technobit.eu/0_1_3.rar

    0.1.3 Milestone release - Nanfury support is added with native libusb api. No hid api's are required!
    * cgminer ./autegen.sh --enable-hexmineru to add Nanos' manufactured by TechnoBIT known as HEXu
    * cgminer --hexmineru-frequency command line to set chip frequency - range 1-62
    * cgminer Added to defaultetc/config/cgminer  Factory default or web Save+Apply is required for changes to be applied!
    * cgminer updated to 3.8.5 rev afe7710858e4ce28bb60f6ae6e167a18d687634f
    * cgminer patch to cgminer 3.8.5 rev afe7710858e4ce28bb60f6ae6e167a18d687634f.patch - various code cleanup and optimization needs to be done
    * hotplugd added hotplug support for HEXu inudev/rules.d/01-cgminer.rules. Factory default is required for changes to be applied!
    * openwrt updated to r39151
    http://technobit.eu
    tips : 12DNdacCtUZ99qcP74FwchaCPzeDL9Voff

  • vs3 (OP)
    Hero Member
    *****
    Offline Offline

    Activity: 622
    Merit: 500


    View Profile WWW
    December 22, 2013, 10:40:34 AM
     #65
    Quote from: marto74 on December 22, 2013, 10:29:26 AM
    HI,
    here is our cgminer support

    technobit.eu/0_1_3.rar

    0.1.3 Milestone release - Nanfury support is added with native libusb api. No hid api's are required!
    * cgminer ./autegen.sh --enable-hexmineru to add Nanos' manufactured by TechnoBIT known as HEXu
    * cgminer --hexmineru-frequency command line to set chip frequency - range 1-62
    * cgminer Added to defaultetc/config/cgminer  Factory default or web Save+Apply is required for changes to be applied!
    * cgminer updated to 3.8.5 rev afe7710858e4ce28bb60f6ae6e167a18d687634f
    * cgminer patch to cgminer 3.8.5 rev afe7710858e4ce28bb60f6ae6e167a18d687634f.patch - various code cleanup and optimization needs to be done
    * hotplugd added hotplug support for HEXu inudev/rules.d/01-cgminer.rules. Factory default is required for changes to be applied!
    * openwrt updated to r39151

    Marto - you guys rock! Smiley

    Thanks for the awesome news!
    NanoFury - Open Source Project | [GB] NanoFury NF1

  • bitly
    Newbie
    *
    Offline Offline

    Activity: 53
    Merit: 0



    View Profile WWW
    December 24, 2013, 06:44:49 PM
     #66
    Quote
    Unfortunately to this day there is no documentation for bifury's chip. I started digging trough the forums and collecting various bits from here and putting the pieces together. I've put all of those notes in a wiki article - which uses the "docuwiki" format, and github wants the "mediawiki" format, so on my to-do list is to start reworking that. If there are any volunteers to help with that or know how to easily convert it - please PM me.

    I'd like to help with the documentation. Please let me know what I could do.

  • vs3 (OP)
    Hero Member
    *****
    Offline Offline

    Activity: 622
    Merit: 500


    View Profile WWW
    December 24, 2013, 09:05:38 PM
     #67
    Quote from: bitly on December 24, 2013, 06:44:49 PM
    Quote
    Unfortunately to this day there is no documentation for bifury's chip. I started digging trough the forums and collecting various bits from here and putting the pieces together. I've put all of those notes in a wiki article - which uses the "docuwiki" format, and github wants the "mediawiki" format, so on my to-do list is to start reworking that. If there are any volunteers to help with that or know how to easily convert it - please PM me.

    I'd like to help with the documentation. Please let me know what I could do.

    Bitly - please PM me your email address and I'll set you up with access to that wiki page.
    NanoFury - Open Source Project | [GB] NanoFury NF1

  • vs3 (OP)
    Hero Member
    *****
    Offline Offline

    Activity: 622
    Merit: 500


    View Profile WWW
    December 24, 2013, 09:15:58 PM
     #68
    Quote from: rgr_rgr on December 21, 2013, 10:10:23 PM
    I built a few ones for me. A friend of mine reorganised the layout. My fork: https://github.com/rgr-rgr/NanoFury. Pull request sent.

    By the way: I noticed a new version v0.7, not described in the Release_Notes ... ?


    I saw your pull - very good job! (I also have a few minor questions - I sent you a PM)

    The v0.7 had a minor change mostly addressing shortages of the MCP2210 chip in I/SS footprint. In 0.7 both the I/SO and I/SS footprints are present, so you can use whichever chip you manage to find in stock.

    I think I pushed all files already - if you find any missing pieces let me know though and I'll make sure to add them.
    NanoFury - Open Source Project | [GB] NanoFury NF1

  • Luke-Jr
    Legendary
    *
    Offline Offline

    Activity: 2604
    Merit: 1194



    View Profile
    December 24, 2013, 10:09:50 PM
     #69
    I've seen documentation for the bitfury chip, bi*fury (not sure why it's mentioned here though..), and the mcp2210 chip in nanofury.
    Donate: (PM me)
    My projects: Bitcoin Knots, Bitcoin Core, BFGMiner, Eloipool (pool software), Tonal Bitcoin, and BitGit (Bitcoin code directory)

  • libertybuck
    Full Member
    ***
    Offline Offline

    Activity: 137
    Merit: 100


    View Profile
    December 25, 2013, 02:05:51 AM
     #70
    Quote from: Beastlymac on December 22, 2013, 03:46:40 AM
    The device interacts directly with bfgminer so no it doesn't have any firmware.

    Thanks. Good idea. Customers need not worry about firmware updating.
    Driving safely with Android phone

  • Beastlymac
    Hero Member
    *****
    Offline Offline

    Activity: 630
    Merit: 501


    Miner Setup And Reviews. WASP Rep.


    View Profile
    December 25, 2013, 03:05:00 AM
     #71
    Ckolivas
    DrHaribo
    MineForeMan
    Nwoolls

    Have all been sent devices so they can test and incorporate support for the NanoFury design.
    Message me if you have any problems

  • vs3 (OP)
    Hero Member
    *****
    Offline Offline

    Activity: 622
    Merit: 500


    View Profile WWW
    December 25, 2013, 10:40:33 AM
     #72
    Quote from: Luke-Jr on December 24, 2013, 10:09:50 PM
    I've seen documentation for the bitfury chip, bi*fury (not sure why it's mentioned here though..), and the mcp2210 chip in nanofury.

    Luke - the guys that made the bi*fury design are the same that have been working very closely with bitfury and making his boards since the very beginning. I won't be surprised if they actually do have some documentation. However I did not see any such thing published while I was designing the NanoFury (and I may have missed it if that happened in the last 2 months since I already know more than enough and I've just stopped looking for such documentation). If you do have a public link for such documentation - please share it Smiley

    As for the1 MCP2210 documentation - that's freely available from Microchip's web site and just in case I included a copy in the NanoFury github repository.
    NanoFury - Open Source Project | [GB] NanoFury NF1

  • rgr_rgr
    Member
    **
    Offline Offline

    Activity: 115
    Merit: 10


    View Profile
    December 26, 2013, 02:43:40 PM
     #73
    There is a test programm flying around called "nf1_init.exe". I want to run it on linux. Does anyone know the source for source?

  • Dexter770221
    Legendary
    *
    Offline Offline

    Activity: 1029
    Merit: 1000


    View Profile
    December 26, 2013, 03:43:12 PM
     #74
    Quote from: vs3 on December 25, 2013, 10:40:33 AM
    ....
     If you do have a public link for such documentation - please share it Smiley
    +1
    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.

  • vs3 (OP)
    Hero Member
    *****
    Offline Offline

    Activity: 622
    Merit: 500


    View Profile WWW
    December 26, 2013, 06:55:03 PM
     #75
    Quote from: rgr_rgr on December 26, 2013, 02:43:40 PM
    There is a test programm flying around called "nf1_init.exe". I want to run it on linux. Does anyone know the source for source?

    Is this what you're looking for:
    https://github.com/nanofury/NanoFury_Init
    NanoFury - Open Source Project | [GB] NanoFury NF1

  • rgr_rgr
    Member
    **
    Offline Offline

    Activity: 115
    Merit: 10


    View Profile
    December 26, 2013, 08:07:26 PM
     #76
    Yes, thanks for the wake up :-)
    I knew I have seen somewhere the source - but did not see it in front of me :-)

    Well it is written Visual C for Windows - I would need a linux port. Has somebody done it?

    Basically I just need to set the product string:
    Quote
    can also fix the "Product String" which is a required change so that ''bfgminer'' can recognize all devices automatically

  • Taugeran
    Hero Member
    *****
    Offline Offline

    Activity: 658
    Merit: 500


    CCNA: There i fixed the internet.


    View Profile
    December 26, 2013, 09:44:44 PM
     #77
    Quote from: rgr_rgr on December 26, 2013, 08:07:26 PM
    Yes, thanks for the wake up :-)
    I knew I have seen somewhere the source - but did not see it in front of me :-)

    Well it is written Visual C for Windows - I would need a linux port. Has somebody done it?

    Basically I just need to set the product string:
    Quote
    can also fix the "Product String" which is a required change so that ''bfgminer'' can recognize all devices automatically

    You can always use a windows VM and patch the rgrfury into the vm
    Bitfury HW & Habañero : 1.625Th/s
    tips/Donations: 1NoS89H3Mr6U5CmP4VwWzU2318JEMxHL1
    Come join Coinbase

  • Taugeran
    Hero Member
    *****
    Offline Offline

    Activity: 658
    Merit: 500


    CCNA: There i fixed the internet.


    View Profile
    December 26, 2013, 10:01:29 PM
     #78
    Quote from: Taugeran on December 26, 2013, 09:44:44 PM
    Quote from: rgr_rgr on December 26, 2013, 08:07:26 PM
    Yes, thanks for the wake up :-)
    I knew I have seen somewhere the source - but did not see it in front of me :-)

    Well it is written Visual C for Windows - I would need a linux port. Has somebody done it?

    Basically I just need to set the product string:
    Quote
    can also fix the "Product String" which is a required change so that ''bfgminer'' can recognize all devices automatically

    You can always use a windows VM and patch the rgrfury into the vm

    Upon review of the source for nf1_init. It should only be a matter of changing some windows specific functions to Linux counterparts and compiling
    Bitfury HW & Habañero : 1.625Th/s
    tips/Donations: 1NoS89H3Mr6U5CmP4VwWzU2318JEMxHL1
    Come join Coinbase

  • razorfishsl
    Sr. Member
    ****
    Offline Offline

    Activity: 398
    Merit: 250


    View Profile WWW
    December 28, 2013, 01:21:46 AM
     #79
    I'm Working on a few ideas on increasing the hashing speed.

    But I note on the IOREFF for Ver.7 that it is shown as 0V8(fine!!), but that it appears to be derived from the BUCK convertor (301F) rather than via a voltage divider & cap.
    'Bitfury' seems to have stated that the IOREFF pin should be tied to 0V8, but if people start playing about with R2/R3 and the 'stupid' pencil mod, will this not impact the voltage that IOREFF sees potentially making it as high as 0v95?

    Also I notice that VUSB does not appear to be decoupled correctly (0uf22/0uf47)?


    Next question…
    Prior to the nano 50 miners meant 50  embedded SOC's

    Since all the function of the SOC has now been offloaded to the miner software, how does that impact the % processor power required to support multiple miners?
    I.E can a PI or other SOC (A10/A20)still carry the utilization 'load'?

    RF
    High Quality USB Hubs for Bitcoin miners
    https://bt.irlbtc.com/view/560003

  • Taugeran
    Hero Member
    *****
    Offline Offline

    Activity: 658
    Merit: 500


    CCNA: There i fixed the internet.


    View Profile
    December 28, 2013, 02:44:58 AM
     #80
    Quote from: rgr_rgr on December 21, 2013, 10:10:23 PM
    I built a few ones for me. A friend of mine reorganised the layout. My fork: https://github.com/rgr-rgr/NanoFury. Pull request sent.

    By the way: I noticed a new version v0.7, not described in the Release_Notes ... ?


    they all use a 2 layer pcb correct? none use a 4 layer?
    Bitfury HW & Habañero : 1.625Th/s
    tips/Donations: 1NoS89H3Mr6U5CmP4VwWzU2318JEMxHL1
    Come join Coinbase
    Pages: « 1 2 3 [4] 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 »  All
      Print  
Page 3
Viewing Page: 4

IRLBTC™ © 2025 IRLBTC.com