Search content
Sort by
Showing 9 of 9 results by danielyap
Hi guys, so I just restarted my computer and sometimes it works, sometimes it don't. I'm not entirely sure why this happens. 
In any case, does any one know why do I need to flash my board with the Hex provided by @thierry4wd in order for a custom bmminer to work? Is there any way to do this without flashing the board. Right now, I have to take out each board and flash them 1 by 1 with the pickit 3 in order for the custom bmminer to work...
Here's a snippet of the kernel log when I paste the bmminer in before flashing the boards with the hex
Thanks for the help so far guys! Really appreciate it!
In any case, does any one know why do I need to flash my board with the Hex provided by @thierry4wd in order for a custom bmminer to work? Is there any way to do this without flashing the board. Right now, I have to take out each board and flash them 1 by 1 with the pickit 3 in order for the custom bmminer to work...
Here's a snippet of the kernel log when I paste the bmminer in before flashing the boards with the hex
Code:
[ 23.956220] bcm54xx_config_init
[ 26.956770] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz
[ 26.962790] xemacps e000b000.ps7-ethernet: link up (100/FULL)
[ 100.487087] random: nonblocking pool is initialized
Detect 512MB control board of XILINX
Miner Type = T9+
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x0000ffff
chain[1] PIC jump to app
Check chain[1] PIC fw version=0x90
chain[1] PIC need restore ...
[ 26.956770] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz
[ 26.962790] xemacps e000b000.ps7-ethernet: link up (100/FULL)
[ 100.487087] random: nonblocking pool is initialized
Detect 512MB control board of XILINX
Miner Type = T9+
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x0000ffff
chain[1] PIC jump to app
Check chain[1] PIC fw version=0x90
chain[1] PIC need restore ...
Thanks for the help so far guys! Really appreciate it!
for the error:
"Boot, Secure and General Segments" "You are trying to change your boot.
simply follow the instructions: D then activate "advanced setting", then go to "setting" then in the "secure segment" tab choose "Boot, Secure and General Segments"
For the problem: Too much current has been drawn on VDD. Please disconnect your circuit and check the CLK and DATA lines for shorts and then reconnect. I also had the problem, maybe a procedural error, try to disconnect and reconnect ... it worked for me.
"Boot, Secure and General Segments" "You are trying to change your boot.
simply follow the instructions: D then activate "advanced setting", then go to "setting" then in the "secure segment" tab choose "Boot, Secure and General Segments"
For the problem: Too much current has been drawn on VDD. Please disconnect your circuit and check the CLK and DATA lines for shorts and then reconnect. I also had the problem, maybe a procedural error, try to disconnect and reconnect ... it worked for me.
Thanks! will try that out.. how about the hex problem? Your HEX works but the stock HEX will cause this error all the time...instead of opening each miner to program the HEX, how do I program via the PIC? (if possible)
Hmm. I've been successful for some boards but sometimes when I try to connect the board, this is what I get...
Any idea why this happens?
Also, I find that when I try to upload a custom bmminer, I get this same error all the time,
Which I'll then have to flash your working HEX in order for that bmminer to work. Any idea why that happens as well? Thanks!
Code:
*****************************************************
Connecting to MPLAB PICkit 3...
Currently loaded firmware on PICkit 3
Firmware Suite Version.....01.54.00
Firmware type..............dsPIC33E/24E
Target device was not found (could not detect target voltage VDD). You must connect to a target device to use PICkit 3.
*****************************************************
Connecting to MPLAB PICkit 3...
Currently loaded firmware on PICkit 3
Firmware Suite Version.....01.54.00
Firmware type..............dsPIC33E/24E
Programmer to target power is enabled - VDD = 3.250000 volts.
Target device dsPIC33EP16GS202 found.
Device ID Revision = 4003
DEVSN0 = 00000000
DEVSN1 = 00000000
Erasing...
Erase successful
2018-10-04 21:51:39 +0800 - Hex file loaded successfully.
Loading code from \\Mac\Home\Downloads\k-upload-file_2018-09-19-103561fd6dspic33ep16g.hex...
2018-10-04 21:51:41 +0800 - Programming...
You are trying to change protected boot memory. In order to do this you must select the "Boot, Secure and General Segments" option on the debug tool Secure Segment properties page.
Failed to program device
Too much current has been drawn on VDD. Please disconnect your circuit, check the CLK and DATA lines for shorts and then reconnect.
Connecting to MPLAB PICkit 3...
Currently loaded firmware on PICkit 3
Firmware Suite Version.....01.54.00
Firmware type..............dsPIC33E/24E
Target device was not found (could not detect target voltage VDD). You must connect to a target device to use PICkit 3.
*****************************************************
Connecting to MPLAB PICkit 3...
Currently loaded firmware on PICkit 3
Firmware Suite Version.....01.54.00
Firmware type..............dsPIC33E/24E
Programmer to target power is enabled - VDD = 3.250000 volts.
Target device dsPIC33EP16GS202 found.
Device ID Revision = 4003
DEVSN0 = 00000000
DEVSN1 = 00000000
Erasing...
Erase successful
2018-10-04 21:51:39 +0800 - Hex file loaded successfully.
Loading code from \\Mac\Home\Downloads\k-upload-file_2018-09-19-103561fd6dspic33ep16g.hex...
2018-10-04 21:51:41 +0800 - Programming...
You are trying to change protected boot memory. In order to do this you must select the "Boot, Secure and General Segments" option on the debug tool Secure Segment properties page.
Failed to program device
Too much current has been drawn on VDD. Please disconnect your circuit, check the CLK and DATA lines for shorts and then reconnect.
Any idea why this happens?
Also, I find that when I try to upload a custom bmminer, I get this same error all the time,
Code:
dsPIC33EP16GS202_get_pic_sw_version failed on Chain[1]!
Which I'll then have to flash your working HEX in order for that bmminer to work. Any idea why that happens as well? Thanks!
I'm getting this error T9+ August Batch
Does this mean my PIC is PIC33 not PIC32?
Also, how do I connect the PicKit 3 to my board? there's no slot for me to put it in...
https://imgur.com/a/DxJdSzH
Please help me! Thank you so much!
Code:
dsPIC33EP16GS202_get_pic_sw_version failed on Chain[1]!
Does this mean my PIC is PIC33 not PIC32?
Also, how do I connect the PicKit 3 to my board? there's no slot for me to put it in...
https://imgur.com/a/DxJdSzH
Please help me! Thank you so much!
Re: Dollemizer Firmware ASICBOOST Comming! [custom s9, s9i, t9 Firmware upgrade]
That has a 7% dev fee...
How do we detect if there's a Dev fee or not?
Re: KryptMiner - 20th/s @ 800w (a new magical miner / scam?)
Good try bro...seriously fuck all the weird haters in this thread...You clearly mentioned you're gonna go ahead and try this out, not promoting it. As far as I'm concerned you did us all a favour by going in head on. We have an outcome which really saved all of us the hassle. You did well, cheers!
Re: Ebit e9 miner with 6.8Th/s from Ebang company a new rival for existing producers
Would it make sense to leave a pc running in the farm connected to the network just so I can use teamviewer to access the web interface? What do you plan to do with the SSH interface anyways? Sorry I'm new to this so id appreciate any input I can get. Thanks!
Hello,
I have the same error, but I cannot figure out why.
I had 2 Sapphire RX580 8Gb cards running since September.
They ran without any problems (Claymore settings 1260/2230/910)
PSU : EVGA 1600 T2
Since I added a 3rd card I have approx every 3-4 hours the message :
WATCHDOG: GPU 1 hangs in OpenCL call
Sometimes it's GPU 3, sometimes GPU 2...
I put specific values for GPU 3 (115/2170/910) and always the same problem.
I changed the Rizer, reinstalled the drivers but nothing seems to work. Maybe a Win10 issue ?
Thx
I have the same error, but I cannot figure out why.
I had 2 Sapphire RX580 8Gb cards running since September.
They ran without any problems (Claymore settings 1260/2230/910)
PSU : EVGA 1600 T2
Since I added a 3rd card I have approx every 3-4 hours the message :
WATCHDOG: GPU 1 hangs in OpenCL call
Sometimes it's GPU 3, sometimes GPU 2...
I put specific values for GPU 3 (115/2170/910) and always the same problem.
I changed the Rizer, reinstalled the drivers but nothing seems to work. Maybe a Win10 issue ?
Thx
Try a clean uninstall of drivers using DDU
http://www.guru3d.com/files-details/display-driver-uninstaller-download.html
then install blockchain drivers for windows 10
If this doesn't work, I suggest updating to Win10 Fall Creator's Update and to AMD's 17.10.3.
It could very well be a windows update sneaked on you and wrecked your GPU drivers.
I'm running on RX580 Sapphire Nitro+. Was running on Win10-64Bit-Crimson-ReLive-Beta-Blockchain-Workloads-Aug23 getting 30mhs. Kept getting the OpenCL GPU Hang errors. I did the AMD 17.10.3 update and tried to run again but my hashrate greatly reduced to 23mhs. Any idea how to run on the new driver and get 30mhs?