 Show Posts
|
|
Pages: [1] 2 3 4 5 6 »
|
|
Could you send a fresh discord invitation? The last one is expired.
|
|
|
|
Regarding the question about bitstream compatibility, the answer is no, a bitstream built for VCU1525 will not work on the XUPP3R. The clock & USB UART are on different pins, so I must 'build' two versions of the bitstream, one for each card. Although the change in the code is tiny, it still takes the tools 5+ hours to re-run place & route, with multiple runs needed to get a success.
Can you inplement a double set of interfaces to support both boards by the single firmware? BUFGMUX_CTRL can be used to select the clock signal, if clocking assignment is different. It is probably possible to build one firmware for both board. I get the general idea but I still have a hard time seeing how to do that with the USB-UART pins. If the alternative serial pins are mutually unused on the other board then: - you can transmit on both TX pins. - enable the pull up for RX pins, because in idle state the serial lines are in high state. Then you can make a common RX signal: RX_COMMON=1'b1^RX_A^RX_B. |
|
|
|
Turn on the overtemperature shutdown in the bitstream, and control the temperature in the mining software. It is easy.
“Turn on overtemp shutdown in the bitstream” AFAIK there’s no such magic button. If you want temp monitoring and thermal limits with an FPGA you have to include them in your design logic. False. The better fpgas(like virtex 5/6, complete series 7 and newer xilinx) has pin terminals to an separated internal die temperature sensor transistor. A properly designed board should use it for temperature measurement and shutdown. It works even when FPGA isn't configured. An alternative is using jtag to read XADC (7 series and newer). I actually went ahead and RTFM'd the "UltraScale Architecture SYStem MONitor User's Guide". It looks like it is very close to being a "magic button", it takes only one line of code: set_property BITSTREAM.CONFIG.OVERTEMPSHUTDOWN ENABLE On the other hand the whole guide to the SYSMON block has 113 pages, so it must be also relatively easy to accidentally mis-configure it. You are going too far to look up some useful information, but it is on the top. Read the "VCU1525 Acceleration Platform User Guide", on page 47. It says fan controller IC has a die temperature sensor connected to FPGA-s DXP/DXN pin, and has an TCRIT#output which connected to the supervisory IC and it will shut down the FPGA, when overheated. It is independent from the FPGA and FPGA's SYSMON. It looks like the Xilinx's card is a properly designed FPGA board  |
|
|
|
From my practice there are simple measures to avoid failures.
Do not place these boards in the closed case, setup the fan to cool the bottom layer of PCB.
Do not allow the local overheat of any component like DC/DC or external power connector.
Turn on the overtemperature shutdown in the bitstream, and control the temperature in the mining software. It is easy.
Then the FPGA board will work for years.
“Turn on overtemp shutdown in the bitstream” AFAIK there’s no such magic button. If you want temp monitoring and thermal limits with an FPGA you have to include them in your design logic. Same as an ASIC. Otherwise you very much can exceed junction temps and damage the hardware if you have enough power going into the board to begin with. This is also possible on some GPUs with poor drivers. A few of my old Titan Blacks from HPC work had power stages for memory that would overheat if the memory was trashed too much for too long, and the mosfet would slip down on the boards till they caused a short. Actually caught a entire server on fire that way once... False. The better fpgas(like virtex 5/6, complete series 7 and newer xilinx) has pin terminals to an separated internal die temperature sensor transistor. A properly designed board should use it for temperature measurement and shutdown. It works even when FPGA isn't configured. An alternative is using jtag to read XADC (7 series and newer). |
|
|
|
Note that we do have onboard monitoring for temperature, voltage, and current, with thresholds set to shut down the board if it appears to be entering a situation that would cause damage. We provide a utility (console and GUI versions) that you can use to talk to this onboard controller via the USB and see what is going on with all the sensors. Unlike GPUs and CPUs, FPGAs have no inherent thermal throttling, unless the FPGA developer builds that into their logic, which is very rarely done. FPGAs also burn more power as they get hotter, so from a power efficiency point of view, it is better to keep them cool.
@BittWareFPGATech The OP stated that you will be mining with your own boards. Can you vouch for these hash rates presented by the OP? We have not yet done any mining, and for the record, have no big plans for this. We have joked internally that perhaps we should use mining as the factory burn in test for our boards. The OP has offered to get us the code once released, and we may play around a little to understand the thermals, etc. Well, there aren't any special. Use xilinx power estimator with 100% toggle rate and 2.6 average fanout. The calculated result has 5% accuracy. |
|
|
|
I want to buy the ztex modules. Hello,
Want to sell:
2xZTEX USB-FPGA Modules 1.15y
2xCairnsmore 1 FPGA modules
3xIcarus FPGA modules
+ cables and ...
Consider your offer
Im in EU
|
|
|
|
u can get flagged like a pool just send a PM to fairglu with ur mining address
Thanks, but I like the anonymity. |
|
|
|
miners listen up please! we need danbi pool below 20% of new blocks (this would be around 40% of POW blocks) please who mine at danbi switch to http://dmdeu.miningfield.com/ who mine at danbi and is from USA switch to http://dmd.donkeypool.com:808/thx for ur support to create a more healthy mining hashrate distribution  solominers ignore this u are the true heroes regarding decentralized mining! stay solomining  Great. It seems my hashrate in last 1000 blocks is 7.5%, and 8% in last 100 blocks   |
|
|
|
But, what is the point? It is easier to provide random benefits to active wallets...
Nothing. If you'd mine for a long time, then it will be equal to increased reward. Statistics is a fun player:) |
|
|
|
Dave says new admin fee coding in operation on donkeypool, congrats to those who mined for 0% fee during the past day or so . Donkeypool gobbled up a lot of DMD during the Danbi fork period Now another subject: Are u f'in kidding 120 diff for 0.2 DMD reward  Here is the solution: please quit mining:) |
|
|
|
thx
but i know you dont understand what i am saying
not sync wallet so i cant a anything my wallet i cant transfer cryptsy so i cant sell my dmd so my all dmd in wallet worth of nothing i mining 10 month and all dmd cant sell
i dont understand why release half working wallet
bye
OMG. We understand that you misunderstood how wallet works. DMD wallet has a blockchain and a wallet.dat. The former contains information about transactions, the latter contains private keys for your addresses. Syncing means downloading the blockchain from network. If wallet unable to sync it doesn't affect you private keys. Your earnings are in safe because you still have wallet.dat therefore you can initialize and sign transactions and other members has the correct blockchain which contains the information about your balance. Therefore you have to backup your wallet and delete the blockchain to resync and gain access to your coins. |
|
|
|
And i´m lose my DMD 172 coins in stake  what's happening You will not lose any coin. Stake requires mature coins, not mature wallet uptime. |
|
|
|
|
Hm. I'm giving 66% of network hashrate on the main chain. Will it cause forking or is it ok? My wallet configured to connect to 6 main node and listen=0.
|
|
|
|
if we after reduction are able to hold like 1-2 ghash miningrate im happy
its clear lot people will leave and must leave or everyone mining would mine at a big loss
2 ghash is still a nice hashrate only very big farms can deliver that
its like 80x amd 290 gpu
so some troublemaker alone wont have easy access to that
and our coin isnt vulnerable to 51% (special after 1000000 total coins when pos is on same blocktime with pow)
what we did experienced last few days isnt a 51% issue its a network overload issue with injection of bad blocks
which all got rejected but still created lot of work
BUT close at trigger and until pools confirmed to work after trigger
we ask everyone who can to switch to solo mining
thx for support
I think 2gh is not enough. I'm able to increase my 0.8GH/s to 8.3GH/s. Actually I never planned to attack DMD and I will never do, but you have to know, not I'm the only one with huge hidden hashpower. DMD has a relatively high price therefore it is an ideal target. nice after we reached new specs with faster pos and slower pow it would be good u try if u could attack a friendly security check im pretty sure u cant do anything more than increase pow diff u use fpga? ór sitting on a warehouse full GPU? It is a GPU farm, but currently not used due to high electricity bills. |
|
|
|
if we after reduction are able to hold like 1-2 ghash miningrate im happy
its clear lot people will leave and must leave or everyone mining would mine at a big loss
2 ghash is still a nice hashrate only very big farms can deliver that
its like 80x amd 290 gpu
so some troublemaker alone wont have easy access to that
and our coin isnt vulnerable to 51% (special after 1000000 total coins when pos is on same blocktime with pow)
what we did experienced last few days isnt a 51% issue its a network overload issue with injection of bad blocks
which all got rejected but still created lot of work
BUT close at trigger and until pools confirmed to work after trigger
we ask everyone who can to switch to solo mining
thx for support
I think 2gh is not enough. I'm able to increase my 0.8GH/s to 8.3GH/s. Actually I never planned to attack DMD and I will never do, but you have to know, not I'm the only one with huge hidden hashpower. DMD has a relatively high price therefore it is an ideal target. |
|
|
|
even Danbi's is on lower diff fork occasionally ... shut it down and let the chain heal itself ... I am about ready to quit solo mining too, 1/4 blocks mined orphaned ... Good to see you back here. This looks FUBR. I tried solo and was mining more orphans than DMDs so I quit. donkeypool is getting hosed with orphans too. There are other coins that are as profitable as DMD right now. Here is the solution: I've resynced a wallet with maxconnections=7, and 4x connect=<rootnode>, therefore it will stay at right chain and I moved my 800 MH/s from danbi's pool. |
|
|
|
I think i fond the problem
danbis pool is ( involutary i belive ) performing a sucessfully a 51% atack
i'm monitoring the block exlorer everithing goes fine, until a bunch of blocks from danbis pool arrive making every block orphan
I have confirmed blocks , and next minute they are orphan
I'm force to stop mining until this is fixed
its very sad whats hapening
If it is true then it proves why master node is a bad idea. |
|
|
|
|
Hi cryptonite!
I've downloaded the new wallet and deleted the blockchain but it not synchronizes. In debug log it reports misbehaving for all root nodes:
connected 193.68.21.19
send version message: version 60012, blocks=0, us=0.0.0.0:0, them=193.68.21.19:17771, peer=193.68.21.19:17771
Flushed 0 addresses to peers.dat 2ms
socket closed
disconnecting node 54.191.208.14
Misbehaving: 193.68.21.19:17771 (0 -> 1)
ProcessMessage(checkpoint, 109 bytes) FAILED
|
|
|
|
if reactor in the form its designed split community that much
we freeze project and research possibilities to launch it decentralized
or even cancel it at all
...
I accept it is hard decision for you. I don't support the reactor, but I will support you anyway, even if you choose to start the reactor. I'm glad we have flexible devs. |
|
|
|
|
