Dollemizer Firmware ASICBOOST Comming! [custom s9, s9i, t9 Firmware upgrade] - page 3.

minefarmbuy

full member

Activity: 1022

Merit: 221

We are not retail.

Quote from: fanatic26_ on August 07, 2018, 04:58:33 PM

Its been common knowledge for YEARS not to mess with bitmains firmware yet you people are bricking your units left and right for no good reason at all. Pushing these machines past the rated hash rate decreases efficiency and eats away at any extra profits you think you are squeezing out of the machine.

Just plug your miner in and run it the way it was built to run. Stop being stupid and letting greed take you down a wrong path.

It's weird. Sometimes the hard way is the best way to learn. Asics aren't gpu's their CPU's that will burn your house down. Enjoy.

Always love me a fanatic post though. Need people like you around. Balance in the force and what not.

fanatic26_

full member

Activity: 294

Merit: 129

Its been common knowledge for YEARS not to mess with bitmains firmware yet you people are bricking your units left and right for no good reason at all. Pushing these machines past the rated hash rate decreases efficiency and eats away at any extra profits you think you are squeezing out of the machine.

Just plug your miner in and run it the way it was built to run. Stop being stupid and letting greed take you down a wrong path.

nokapol

newbie

Activity: 2

Merit: 0

Low hashrate and not temperature monitoring.
http://dl4.joxi.net/drive/2018/08/03/0013/1525/910837/37/231f0acad1.png

taserz

sr. member

Activity: 800

Merit: 294

Created AutoTune to saved the planet! ~USA

Quote from: bitsolutions on August 01, 2018, 11:55:15 PM

I've never heard of a GPLv3 requirement to run it(if there is one please point me to the specific line in the GPLv3 license), GPLv3 requirements are based on distribution of the software(ie downloading it) not running it. You can contact me via PM.
Here's proof I downloaded it:

Code:

$ shasum -a 256 Dollemizer875-USA.gz
ee4386b018901799c205788bf0fb15db21b1599e4c4bf3a0d2e6abdd1d618d7e Dollemizer875-USA.gz

This is true GPL requirements are based off distribution NOT usage. Requesting source code or thread being closed.

bitsolutions

sr. member

Activity: 261

Merit: 257

Quote from: DolleTeam on July 18, 2018, 04:02:18 AM

The GPLv3 states that you need to show us that you run our software and then we can send you the source code. We do not have to make the source code public.
If you would like the source code, send us that you are running our software and share your contact details.

I've never heard of a GPLv3 requirement to run it(if there is one please point me to the specific line in the GPLv3 license), GPLv3 requirements are based on distribution of the software(ie downloading it) not running it. You can contact me via PM.
Here's proof I downloaded it:

Code:

$ shasum -a 256 Dollemizer875-USA.gz
ee4386b018901799c205788bf0fb15db21b1599e4c4bf3a0d2e6abdd1d618d7e Dollemizer875-USA.gz

numnutz2009

sr. member

Activity: 387

Merit: 254

Quote from: taserz on August 01, 2018, 11:11:28 AM

That won't fix a hashboard pic programmed for a different miner from a malicious firmware update aka this firmware here.

hes sayin he cant revert to the original firmware. that can mean 2 things...either the board firmware or the controller firmware. if he is havin issues flashin the controller i provided a way around that. alot of miners wont let u go back from a modded version unless you force it and since he kinda left it open to assumption i thought i would pass that info along. he can also try flashin it to see if it also forces flashin of the board firmware too. its not like he has ne thing to lose but as it sits they dont work.

what i find confusin is 2 boards dont work for him...if the firmware did in fact kill his boards all of them would be dead not just some of them.

taserz

sr. member

Activity: 800

Merit: 294

Created AutoTune to saved the planet! ~USA

Quote from: numnutz2009 on August 01, 2018, 08:08:11 AM

to be fair ur post is misleading. the share count isnt the number u should look at. u can if the diff of each share is the same between both pools but some have a much higher diff so u cant compare one to the other.

either way i wouldnt use this firmware. folks should have known the same firmware used on s9's shouldnt be used with the t9 versions. i dont really consider this part their fault even if they said it might work with the t9 model. its well known that the models are completely different and have different power requirements and firmware configs. it sucks that it happened but take this as a chance to learn and be sure to read up on the machines ur plannin on moddin via software and hardware.

if u want to force the old firmware back onto the machine use the antminer manager app that bitmain has on their site. it seems to get around the wrong firmware error when flashing custom firmware images. just download the app and the official firmware for ur model miner and connect to it using the app. u have to import the firmware u downloaded to the apps repo but u can figure that stuff out. i have used this to force flash miners that wouldnt accept the official update so i know it works but i havent used this threads custom firmware but it should have the same result.

That won't fix a hashboard pic programmed for a different miner from a malicious firmware update aka this firmware here.

numnutz2009

sr. member

Activity: 387

Merit: 254

Quote from: coinhicken on July 23, 2018, 11:33:59 AM

So the fee is totally out of balance on this firmware. I have been running for 21 hours and these are my results.

748 shares mined to my pools.

1394 shares mined to dev fee pools.

That's more like a 150% fee...

I mean I can manually remove the dev fee pool using the cgminer api and it works fine. But I don't mind the dev fee if its as advertised.

Are there fixes coming for this?

to be fair ur post is misleading. the share count isnt the number u should look at. u can if the diff of each share is the same between both pools but some have a much higher diff so u cant compare one to the other.

either way i wouldnt use this firmware. folks should have known the same firmware used on s9's shouldnt be used with the t9 versions. i dont really consider this part their fault even if they said it might work with the t9 model. its well known that the models are completely different and have different power requirements and firmware configs. it sucks that it happened but take this as a chance to learn and be sure to read up on the machines ur plannin on moddin via software and hardware.

if u want to force the old firmware back onto the machine use the antminer manager app that bitmain has on their site. it seems to get around the wrong firmware error when flashing custom firmware images. just download the app and the official firmware for ur model miner and connect to it using the app. u have to import the firmware u downloaded to the apps repo but u can figure that stuff out. i have used this to force flash miners that wouldnt accept the official update so i know it works but i havent used this threads custom firmware but it should have the same result.

x3aklili

newbie

Activity: 103

Merit: 0

your dollemizer burn my T9+ and not release the pach to recover it. my PICs FW now get error.
i was reset it many time but it won't revert back to original bitmain Firmware.
God Damn your guys

thecryptoprick

newbie

Activity: 21

Merit: 0

This software comes with a small built-in fee of 1,9%.

Quote from: DolleTeam on July 03, 2018, 04:30:23 PM

the Miner will mine in the first 4 Minutes for our fee. Then it will mine for 200 Minutes on your pools and will continue from there.

This is equivalent of ~ 1.96 % of the Mining time. (4/204)

Um, yeah no thanks...

taserz

sr. member

Activity: 800

Merit: 294

Created AutoTune to saved the planet! ~USA

Yeah a bunch of us are trying to undo what dollemizer firmware did to this guy. They label their firmwar as working on a T9+ but state the have never tested it. Amongst reviewing some of the code with darval you can't have the firmware flash for the s9 and t9 they use a different number of chips amongst other things. So far we made a bmminer if you have an unflashed dollemizer t9 that should work but really darval is this guys real hope to flash the pic.

tim-bc

full member

Activity: 538

Merit: 175

Quote from: DolleTeam on February 06, 2018, 07:22:35 AM

@DarkPoe, I do not think it will work on the T9.

Quote from: vonRau on July 01, 2018, 11:54:11 AM

Incorrect firmware!!!

Quote from: RadekG2 on July 02, 2018, 10:17:27 AM

I still do not understand why we should pay fee, when another FW with the same functionality is available for free?! Your FW can set only voltage and frequency, for the cost of fee, so where is the advance?

Quote from: piscess16 on July 03, 2018, 04:10:29 PM

and the FW can support T9+ or not ?

Quote from: DolleTeam on July 03, 2018, 04:30:23 PM

For the T9+, we haven't done testing on a T9+

Quote from: piscess16 on July 03, 2018, 10:33:37 PM

Hi i have testing update the T9+ FW, but have the error cant to running

Quote from: elliott123 on July 06, 2018, 07:23:06 AM

How to you revert back to stock. I have reinstalled the bitmain firmware but the index page has still got the dollemizer logo on it.

Quote from: Dodgymon on July 09, 2018, 08:42:41 AM

I tried this on an Antminer T9+ and it is not hashing.
I am getting this error "Logic Version T9+-nopreheat"

I have flashed back to factory firmware and reset to defaults and still no luck.
Also restored from a backup and still nothing.

Quote from: taserz on July 10, 2018, 04:45:34 PM

Quote from: ?? on ??

I tried it with T9+, and it is not hashing. Eventough I reset it and installed Bitmain firmware.

Sounds like his firmware cooked you t9+

Quote from: rperus on July 10, 2018, 05:54:11 PM

I installed Dollemizer in a T9+. Unfurtenately, it did not work my hashrate is zero. I tried to uninstalled an reinstall Bitmain´s firmware, but the hashrate is still zero, it is not possible to uninstall the software. What can I do the Antminer is new, and I lost the warranty.

Quote from: bitsolutions on July 15, 2018, 05:42:16 PM

The cgminer source code (cgminer/bmminer) is GPLv3 licensed which requires you provide the source code upon request.

Quote from: Dodgymon on July 15, 2018, 09:07:29 PM

Quote from: Dodgymon on July 11, 2018, 10:48:18 AM

You can just buy a new control board from Bitmain. I am 99% sure you can reload the software from an SD card just like you can if you brick an L3+
I personally just ordered a new control board $60 USD + postage

I just tried a different control board and still the same error
"T9+_fixed450_noPreHeat_test"

Quote from: DolleTeam on July 18, 2018, 03:43:40 AM

Our software is not compatible with T9+.

Quote from: rperus on July 18, 2018, 09:03:36 AM

There are 3 different ways to reset it the Ip report button, the reset hole and within the software. I did those 3 methods several times, Bitmain does not support reset it from the SD card anymore.

I also tried to install Bitmain's Las firmware and my backup, but Dollemizer software is still there.

Iclear the cache of the browser, but dollemizer is still there.

Quote from: elliott123 on July 18, 2018, 09:57:58 AM

I also cannot get back to stock. Cant even SSH into my miner after I reinstalled the Bitmain Firmware. The standard credentials are root as user and admin as the password. Im getting Access Denied using those credentials.

Quote from: taserz on July 23, 2018, 08:04:54 PM

Quote from: coinhicken on July 23, 2018, 11:33:59 AM

So the fee is totally out of balance on this firmware. I have been running for 21 hours and these are my results.

748 shares mined to my pools.

1394 shares mined to dev fee pools.

That's more like a 150% fee...

I mean I can manually remove the dev fee pool using the cgminer api and it works fine. But I don't mind the dev fee if its as advertised.

Are there fixes coming for this?

Did you not read the thread. They take most of your hashing power and they changed your ssh password.

Quote from: x3aklili on July 26, 2018, 11:16:20 AM

my T9+ is dead because of your wrong firmware also i revert back to original bitmain firmware but fails . no any reset method work.

Quote from: x3aklili on July 26, 2018, 04:32:57 PM

your FW has been compleated killed my 2 boards! i just bought my T9+ 3 days ago.

now i don't know how i can kill you Dollemizer as you killed my machine.

...

after i reverted back to original t9+ bitmain firmware. it seems you put something on firmware like hardware lock to prevent made change on your fucking scam Firmware. and by now my machine have only 3.5Th/s

and it seems my 2 boards was burned because of your missed up !
all 4 ways reset has been fails

warranty has been void and who will be responsible?

xxcsu

hero member

Activity: 1498

Merit: 597

You should read the whole topic before installing some junk firmware on your miner !

Quote from: x3aklili on July 26, 2018, 04:32:57 PM

warranty has been void and who will be responsible?

I know its not helping you at all, but :
The answer to your question is : ONLY YOU !

x3aklili

newbie

Activity: 103

Merit: 0

your FW has been compleated killed my 2 boards! i just bought my T9+ 3 days ago.

now i don't know how i can kill you Dollemizer as you killed my machine.

Code:

[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 3.14.0-xilinx-gb190cb0-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #57 SMP PREEMPT Fri Dec 9 14:49:22 CST 2016
[ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine model: Xilinx Zynq
[ 0.000000] cma: CMA: reserved 128 MiB at 27800000
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] On node 0 totalpages: 258048
[ 0.000000] free_area_init_node: node 0, pgdat c0740a40, node_mem_map e6fd8000
[ 0.000000] Normal zone: 1520 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 194560 pages, LIFO batch:31
[ 0.000000] HighMem zone: 496 pages used for memmap
[ 0.000000] HighMem zone: 63488 pages, LIFO batch:15
[ 0.000000] PERCPU: Embedded 8 pages/cpu @e6fc0000 s9088 r8192 d15488 u32768
[ 0.000000] pcpu-alloc: s9088 r8192 d15488 u32768 alloc=8*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 256528
[ 0.000000] Kernel command line: noinitrd mem=1008M console=ttyPS0,115200 root=ubi0:rootfs ubi.mtd=1 rootfstype=ubifs rw rootwait
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Memory: 884148K/1032192K available (5032K kernel code, 283K rwdata, 1916K rodata, 204K init, 258K bss, 148044K reserved, 253952K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
[ 0.000000] vmalloc : 0xf0000000 - 0xff000000 ( 240 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xef800000 ( 760 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
[ 0.000000] .text : 0xc0008000 - 0xc06d1374 (6949 kB)
[ 0.000000] .init : 0xc06d2000 - 0xc0705380 ( 205 kB)
[ 0.000000] .data : 0xc0706000 - 0xc074cf78 ( 284 kB)
[ 0.000000] .bss : 0xc074cf84 - 0xc078d9fc ( 259 kB)
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] Dump stacks of tasks blocking RCU-preempt GP.
[ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] ps7-slcr mapped to f0004000
[ 0.000000] zynq_clock_init: clkc starts at f0004100
[ 0.000000] Zynq clock init
[ 0.000015] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 3298534883328ns
[ 0.000303] ps7-ttc #0 at f0006000, irq=43
[ 0.000614] Console: colour dummy device 80x30
[ 0.000651] Calibrating delay loop... 1332.01 BogoMIPS (lpj=6660096)
[ 0.090248] pid_max: default: 32768 minimum: 301
[ 0.090472] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.090494] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.092634] CPU: Testing write buffer coherency: ok
[ 0.092981] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.093040] Setting up static identity map for 0x4c4af8 - 0x4c4b50
[ 0.093266] L310 cache controller enabled
[ 0.093286] l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x72760000, Cache size: 512 kB
[ 0.171030] CPU1: Booted secondary processor
[ 0.260224] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.260357] Brought up 2 CPUs
[ 0.260377] SMP: Total of 2 processors activated.
[ 0.260385] CPU: All CPU(s) started in SVC mode.
[ 0.261034] devtmpfs: initialized
[ 0.263442] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[ 0.264647] regulator-dummy: no parameters
[ 0.271918] NET: Registered protocol family 16
[ 0.274179] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.276445] cpuidle: using governor ladder
[ 0.276458] cpuidle: using governor menu
[ 0.283839] syscon f8000000.ps7-slcr: regmap [mem 0xf8000000-0xf8000fff] registered
[ 0.285351] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[ 0.285365] hw-breakpoint: maximum watchpoint size is 4 bytes.
[ 0.285480] zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xf0080000
[ 0.307462] bio: create slab at 0
[ 0.308864] vgaarb: loaded
[ 0.309560] SCSI subsystem initialized
[ 0.310762] usbcore: registered new interface driver usbfs
[ 0.310935] usbcore: registered new interface driver hub
[ 0.311200] usbcore: registered new device driver usb
[ 0.312005] media: Linux media interface: v0.10
[ 0.312159] Linux video capture interface: v2.00
[ 0.312395] pps_core: LinuxPPS API ver. 1 registered
[ 0.312406] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti
[ 0.312527] PTP clock support registered
[ 0.312890] EDAC MC: Ver: 3.0.0
[ 0.313912] Advanced Linux Sound Architecture Driver Initialized.
[ 0.316740] DMA-API: preallocated 4096 debug entries
[ 0.316754] DMA-API: debugging enabled by kernel config
[ 0.316840] Switched to clocksource arm_global_timer
[ 0.336826] NET: Registered protocol family 2
[ 0.337796] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.337891] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.338050] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.338110] TCP: reno registered
[ 0.338129] UDP hash table entries: 512 (order: 2, 16384 bytes)
[ 0.338181] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[ 0.338453] NET: Registered protocol family 1
[ 0.338818] RPC: Registered named UNIX socket transport module.
[ 0.338831] RPC: Registered udp transport module.
[ 0.338839] RPC: Registered tcp transport module.
[ 0.338848] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.338861] PCI: CLS 0 bytes, default 64
[ 0.339302] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[ 0.341323] futex hash table entries: 512 (order: 3, 32768 bytes)
[ 0.342719] bounce pool size: 64 pages
[ 0.343629] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[ 0.343839] msgmni has been set to 1486
[ 0.344616] io scheduler noop registered
[ 0.344629] io scheduler deadline registered
[ 0.344667] io scheduler cfq registered (default)
[ 0.356803] dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-2364208
[ 0.356823] dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[ 0.480746] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 82, base_baud = 3124999) is a xuartps
[ 1.053349] console [ttyPS0] enabled
[ 1.057627] xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to f0068000
[ 1.065237] [drm] Initialized drm 1.1.0 20060810
[ 1.082158] brd: module loaded
[ 1.091508] loop: module loaded
[ 1.100928] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[ 1.106680] e1000e: Copyright(c) 1999 - 2013 Intel Corporation.
[ 1.114592] libphy: XEMACPS mii bus: probed
[ 1.119146] ------------- phy_id = 0x3625e62
[ 1.123882] xemacps e000b000.ps7-ethernet: pdev->id -1, baseaddr 0xe000b000, irq 54
[ 1.132633] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.139296] ehci-pci: EHCI PCI platform driver
[ 1.146508] zynq-dr e0002000.ps7-usb: Unable to init USB phy, missing?
[ 1.153338] usbcore: registered new interface driver usb-storage
[ 1.160201] mousedev: PS/2 mouse device common for all mice
[ 1.166292] i2c /dev entries driver
[ 1.173241] zynq-edac f8006000.ps7-ddrc: ecc not enabled
[ 1.178782] cpufreq_cpu0: failed to get cpu0 regulator: -19
[ 1.184654] Xilinx Zynq CpuIdle Driver started
[ 1.189555] sdhci: Secure Digital Host Controller Interface driver
[ 1.195649] sdhci: Copyright(c) Pierre Ossman
[ 1.200016] sdhci-pltfm: SDHCI platform and OF driver helper
[ 1.206796] mmc0: no vqmmc regulator found
[ 1.210885] mmc0: no vmmc regulator found
[ 1.246857] mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
[ 1.255551] usbcore: registered new interface driver usbhid
[ 1.261059] usbhid: USB HID core driver
[ 1.265766] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[ 1.272065] nand: Micron MT29F2G08ABAEAWP
[ 1.276029] nand: 256MiB, SLC, page size: 2048, OOB size: 64
[ 1.281981] Bad block table found at page 131008, version 0x01
[ 1.288209] Bad block table found at page 130944, version 0x01
[ 1.294258] 3 ofpart partitions found on MTD device pl353-nand
[ 1.300044] Creating 3 MTD partitions on "pl353-nand":
[ 1.305129] 0x000000000000-0x000002000000 : "BOOT.bin-env-dts-kernel"
[ 1.313173] 0x000002000000-0x00000b000000 : "angstram-rootfs"
[ 1.320491] 0x00000b000000-0x000010000000 : "upgrade-rootfs"
[ 1.329416] TCP: cubic registered
[ 1.332650] NET: Registered protocol family 17
[ 1.337362] Registering SWP/SWPB emulation handler
[ 1.343301] regulator-dummy: disabling
[ 1.347663] UBI: attaching mtd1 to ubi0
[ 1.734313] UBI: scanning is finished
[ 1.746150] UBI: attached mtd1 (name "angstram-rootfs", size 144 MiB) to ubi0
[ 1.753230] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 1.759993] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 1.766656] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
[ 1.773535] UBI: good PEBs: 1152, bad PEBs: 0, corrupted PEBs: 0
[ 1.779515] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
[ 1.786622] UBI: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 862493722
[ 1.795578] UBI: available PEBs: 0, total reserved PEBs: 1152, PEBs reserved for bad PEB handling: 40
[ 1.804796] UBI: background thread "ubi_bgt0d" started, PID 1080
[ 1.804801] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 1.808779] ALSA device list:
[ 1.808782] No soundcards found.
[ 1.825634] UBIFS: background thread "ubifs_bgt0_0" started, PID 1082
[ 1.957626] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[ 1.963558] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 1.972689] UBIFS: FS size: 128626688 bytes (122 MiB, 1013 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[ 1.982574] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 1.987613] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 2A24A8E1-2021-4A54-8A4E-D8E294AE00E5, small LPT model
[ 2.027697] VFS: Mounted root (ubifs filesystem) on device 0:11.
[ 2.079822] devtmpfs: mounted
[ 2.082930] Freeing unused kernel memory: 204K (c06d2000 - c0705000)
[ 3.229537] random: dd urandom read with 0 bits of entropy available
[ 3.856877]
[ 3.856877] bcm54xx_config_init
[ 4.466873]
[ 4.466873] bcm54xx_config_init
[ 8.467697] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz
[ 8.473784] xemacps e000b000.ps7-ethernet: link up (100/FULL)
[ 23.648077] In axi fpga driver!
[ 23.651144] request_mem_region OK!
[ 23.654536] AXI fpga dev virtual address is 0xf01fe000
[ 23.659675] *base_vir_addr = 0xc510
[ 23.674414] In fpga mem driver!
[ 23.677707] request_mem_region OK!
[ 23.681220] fpga mem virtual address is 0xf3000000
[ 24.456883]
[ 24.456883] bcm54xx_config_init
[ 25.086884]
[ 25.086884] bcm54xx_config_init
[ 29.087735] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz
[ 29.093750] xemacps e000b000.ps7-ethernet: link up (100/FULL)
[ 1070.665169] random: nonblocking pool is initialized
This is XILINX board. Totalram: 1039794176
Detect 1GB control board of XILINX
DETECT HW version=8000c510
miner ID : 815255ce2c008814
Miner Type = T9+
AsicType = 1387
real AsicNum = 18
use critical mode to search freq...
get PLUG ON=0x07003f0e
Find hashboard on Chain[1]
Find hashboard on Chain[2]
Find hashboard on Chain[3]
Find hashboard on Chain[8]
Find hashboard on Chain[9]
Find hashboard on Chain[10]
Find hashboard on Chain[11]
Find hashboard on Chain[12]
Find hashboard on Chain[13]
set_reset_allhashboard = 0x0000ffff
chain[1] PIC jump to app
dsPIC33EP16GS202_get_pic_sw_version failed on Chain[1]!
dsPIC33EP16GS202_get_pic_sw_version failed on Chain[1]!
dsPIC33EP16GS202_get_pic_sw_version failed on Chain[1]!
Check chain[1] PIC fw version=0xff
chain[2] PIC jump to app
dsPIC33EP16GS202_get_pic_sw_version failed on Chain[2]!
dsPIC33EP16GS202_get_pic_sw_version failed on Chain[2]!
dsPIC33EP16GS202_get_pic_sw_version failed on Chain[2]!
Check chain[2] PIC fw version=0xff
chain[3] PIC jump to app
Check chain[3] PIC fw version=0x90
Chain[1] read_freq_badcores : 0x7d 0x33 0x33 0x33 0x11 0x33 0x33 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff
chain[1]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255]
has freq in PIC, will disable freq setting.
chain[1] has freq in PIC and will jump over...
Chain[1] has core num in PIC
Chain[2] read_freq_badcores : 0x7d 0x33 0x33 0x33 0x11 0x33 0x33 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff
chain[2]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255]
has freq in PIC, will disable freq setting.
chain[2] has freq in PIC and will jump over...
Chain[2] has core num in PIC
Chain[3] read_freq_badcores : 0x7d 0x33 0x33 0x33 0x11 0x33 0x33 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff
chain[3]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255]
has freq in PIC, will disable freq setting.
chain[3] has freq in PIC and will jump over...
Chain[3] has core num in PIC
has freq in PIC, will disable freq setting.
chain[8] has freq in PIC and will jump over...
Chain[8] has core num in PIC
has freq in PIC, will disable freq setting.
chain[9] has freq in PIC and will jump over...
Chain[9] has core num in PIC
has freq in PIC, will disable freq setting.
chain[10] has freq in PIC and will jump over...
Chain[10] has core num in PIC
has freq in PIC, will disable freq setting.
chain[11] has freq in PIC and will jump over...
Chain[11] has core num in PIC
has freq in PIC, will disable freq setting.
chain[12] has freq in PIC and will jump over...
Chain[12] has core num in PIC
has freq in PIC, will disable freq setting.
chain[13] has freq in PIC and will jump over...
Chain[13] has core num in PIC
get PIC voltage=11 on chain[1], value=870
get PIC voltage=11 on chain[2], value=870
get PIC voltage=11 on chain[3], value=870
get PIC voltage=11 on chain[8], value=870
get PIC voltage=11 on chain[9], value=870
get PIC voltage=11 on chain[10], value=870
get PIC voltage=11 on chain[11], value=870
get PIC voltage=11 on chain[12], value=870
get PIC voltage=11 on chain[13], value=870
dsPIC33EP16GS202_pic_heart_beat failed on Chain[1]!
dsPIC33EP16GS202_pic_heart_beat failed on Chain[1]!
dsPIC33EP16GS202_pic_heart_beat failed on Chain[1]!
dsPIC33EP16GS202_pic_heart_beat failed on Chain[2]!
dsPIC33EP16GS202_pic_heart_beat failed on Chain[2]!
dsPIC33EP16GS202_pic_heart_beat failed on Chain[2]!
set_reset_allhashboard = 0x00000000
chain[8] temp offset record: 1,0,0,0,0,0,37,28
chain[8] temp chip I2C addr=0x98
chain[8] has no middle temp, use special fix mode.
chain[10] temp offset record: 1,0,0,0,0,0,37,28
chain[10] temp chip I2C addr=0x98
chain[10] has no middle temp, use special fix mode.
chain[12] temp offset record: 1,0,0,0,0,0,37,28
chain[12] temp chip I2C addr=0x98
chain[12] has no middle temp, use special fix mode.
dsPIC33EP16GS202_pic_heart_beat failed on Chain[1]!
dsPIC33EP16GS202_pic_heart_beat failed on Chain[1]!
dsPIC33EP16GS202_pic_heart_beat failed on Chain[1]!
dsPIC33EP16GS202_pic_heart_beat failed on Chain[2]!
dsPIC33EP16GS202_pic_heart_beat failed on Chain[2]!
dsPIC33EP16GS202_pic_heart_beat failed on Chain[2]!
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
CRC error counter=0
set command mode to VIL

--- check asic number
After Get ASIC NUM CRC error counter=0
set_baud=0
The min freq=700
set real timeout 52, need sleep=379392
After TEST CRC error counter=0
search freq for 1 times, completed chain = 9, total chain num = 9
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
restart Miner chance num=2
waiting for receive_func to exit!
waiting for pic heart to exit!
bmminer not found= 1723 root 0:00 grep bmminer

bmminer not found, restart bmminer ...
This is user mode for mining
Detect 1GB control board of XILINX
Miner Type = T9+
Miner compile time: Fri Nov 24 23:19:16 EST 2017 type: Antminer T9+set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
set_reset_allhashboard = 0x0000ffff
miner ID : 815255ce2c008814
set_reset_allhashboard = 0x0000ffff
Checking fans!get fan[5] speed=6120
get fan[2] speed=4440
get fan[5] speed=6120
get fan[2] speed=4440
get fan[5] speed=6120
chain[1] PIC jump to app
dsPIC33EP16GS202_get_pic_sw_version failed on Chain[1]!
dsPIC33EP16GS202_get_pic_sw_version failed on Chain[1]!
dsPIC33EP16GS202_get_pic_sw_version failed on Chain[1]!
Check chain[1] PIC fw version=0xff
Chain[1] read_freq_badcores : 0x7d 0x33 0x33 0x33 0x11 0x33 0x33 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff
chain[1]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255]
Chain[J2] has backup chain_voltage=870
Detect: use voltage limit rules on single board!
Detect: T9+ use voltage level=1
Chain[J2] test patten OK temp=-1
chain[2] PIC jump to app
dsPIC33EP16GS202_get_pic_sw_version failed on Chain[2]!
dsPIC33EP16GS202_get_pic_sw_version failed on Chain[2]!
dsPIC33EP16GS202_get_pic_sw_version failed on Chain[2]!
Check chain[2] PIC fw version=0xff
Chain[2] read_freq_badcores : 0x7d 0x33 0x33 0x33 0x11 0x33 0x33 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff
chain[2]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255]
Chain[J3] has backup chain_voltage=870
Detect: use voltage limit rules on single board!
Detect: T9+ use voltage level=1
Chain[J3] test patten OK temp=-1
chain[3] PIC jump to app
Check chain[3] PIC fw version=0x90
Chain[3] read_freq_badcores : 0x7d 0x33 0x33 0x33 0x11 0x33 0x33 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff
chain[3]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255]
Chain[J4] has backup chain_voltage=870
Detect: use voltage limit rules on single board!
Detect: T9+ use voltage level=1
Chain[J4] test patten OK temp=-1
Chain[J9] has backup chain_voltage=870
Detect: use voltage limit rules on single board!
Detect: T9+ use voltage level=1
Chain[J9] test patten OK temp=-1
Chain[J10] has backup chain_voltage=870
Detect: use voltage limit rules on single board!
Detect: T9+ use voltage level=1
Chain[J10] test patten OK temp=-1
Chain[J11] has backup chain_voltage=870
Detect: use voltage limit rules on single board!
Detect: T9+ use voltage level=1
Chain[J11] test patten OK temp=-1
Chain[J12] has backup chain_voltage=870
Detect: use voltage limit rules on single board!
Detect: T9+ use voltage level=1
Chain[J12] test patten OK temp=-1
Chain[J13] has backup chain_voltage=870
Detect: use voltage limit rules on single board!
Detect: T9+ use voltage level=1
Chain[J13] test patten OK temp=-1
Chain[J14] has backup chain_voltage=870
Detect: use voltage limit rules on single board!
Detect: T9+ use voltage level=1
Chain[J14] test patten OK temp=-1
Chain[J2] will use voltage=930 [1] to open core
set_Voltage_S9_plus_plus_BM1387_54 failed on Chain[1]!

set_Voltage_S9_plus_plus_BM1387_54 failed on Chain[1]!

set_Voltage_S9_plus_plus_BM1387_54 failed on Chain[1]!

Chain[J3] will use voltage=930 [1] to open core
set_Voltage_S9_plus_plus_BM1387_54 failed on Chain[2]!

set_Voltage_S9_plus_plus_BM1387_54 failed on Chain[2]!

set_Voltage_S9_plus_plus_BM1387_54 failed on Chain[2]!

Chain[J4] will use voltage=930 [1] to open core
Chain[J9] will use voltage=930 [1] to open core
Chain[J10] will use voltage=930 [1] to open core
Chain[J11] will use voltage=930 [1] to open core
Chain[J12] will use voltage=930 [1] to open core
Chain[J13] will use voltage=930 [1] to open core
Chain[J14] will use voltage=930 [1] to open core
Chain[J2] orignal chain_voltage_pic=11 value=870
Chain[J3] orignal chain_voltage_pic=11 value=870
Chain[J4] orignal chain_voltage_pic=11 value=870
Chain[J9] orignal chain_voltage_pic=11 value=870
Chain[J10] orignal chain_voltage_pic=11 value=870
Chain[J11] orignal chain_voltage_pic=11 value=870
Chain[J12] orignal chain_voltage_pic=11 value=870
Chain[J13] orignal chain_voltage_pic=1 value=930
Chain[J13] will use backup chain_voltage_pic=870 [11]
Chain[J13] get working chain_voltage_pic=11
Chain[J14] orignal chain_voltage_pic=1 value=930
Chain[J14] will use backup chain_voltage_pic=870 [11]
Chain[J14] get working chain_voltage_pic=11
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
T9+ try get asic num for the 1 time
Chain[J2] has 0 asic
set_reset_allhashboard = 0x0000ffff
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
set_reset_allhashboard = 0x00000000
T9+ try get asic num for the 2 time
Chain[J2] has 0 asic
set_reset_allhashboard = 0x0000ffff
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
set_reset_allhashboard = 0x00000000
T9+ try get asic num for the 3 time
Chain[J2] has 0 asic
set_reset_allhashboard = 0x0000ffff
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
set_reset_allhashboard = 0x00000000
T9+ try get asic num for the 4 time
Chain[J2] has 0 asic
set_reset_allhashboard = 0x0000ffff
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
set_reset_allhashboard = 0x00000000
T9+ try get asic num for the 5 time
Chain[J2] has 0 asic
set_reset_allhashboard = 0x0000ffff
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]!
set_reset_allhashboard = 0x00000000
T9+ try get asic num for the 6 time
Chain[J2] has 0 asic
Chain[J4] has core num in PIC
Chain[J13] has core num in PIC
Chain[J14] has core num in PIC
miner total rate=3539GH/s fixed rate=3500GH/s
read PIC voltage=930 on chain[3]
Chain:3 chipnum=18
Chain[J4] voltage added=0.0V
Chain:3 base freq=575
Asic[ 0]:575
Asic[ 1]:575 Asic[ 2]:575 Asic[ 3]:575 Asic[ 4]:575 Asic[ 5]:575 Asic[ 6]:575 Asic[ 7]:575 Asic[ 8]:575
Asic[ 9]:575 Asic[10]:575 Asic[11]:575 Asic[12]:575 Asic[13]:575 Asic[14]:575 Asic[15]:575 Asic[16]:575
Asic[17]:575
Chain:3 max freq=575
Chain:3 min freq=575

read PIC voltage=930 on chain[12]
Chain:12 chipnum=18
Chain[J13] voltage added=0.0V
Chain:12 base freq=575
Asic[ 0]:575
Asic[ 1]:575 Asic[ 2]:575 Asic[ 3]:575 Asic[ 4]:575 Asic[ 5]:575 Asic[ 6]:575 Asic[ 7]:575 Asic[ 8]:575
Asic[ 9]:575 Asic[10]:575 Asic[11]:575 Asic[12]:575 Asic[13]:575 Asic[14]:575 Asic[15]:575 Asic[16]:575
Asic[17]:575
Chain:12 max freq=575
Chain:12 min freq=575

read PIC voltage=930 on chain[13]
Chain:13 chipnum=18
Chain[J14] voltage added=0.0V
Chain:13 base freq=575
Asic[ 0]:575
Asic[ 1]:575 Asic[ 2]:575 Asic[ 3]:575 Asic[ 4]:575 Asic[ 5]:575 Asic[ 6]:575 Asic[ 7]:575 Asic[ 8]:575
Asic[ 9]:575 Asic[10]:575 Asic[11]:575 Asic[12]:575 Asic[13]:575 Asic[14]:575 Asic[15]:575 Asic[16]:575
Asic[17]:575
Chain:13 max freq=575
Chain:13 min freq=575

Miner fix freq ...
read PIC voltage=930 on chain[3]
Chain:3 chipnum=18
Chain[J4] voltage added=0.0V
Chain:3 base freq=575
Asic[ 0]:575
Asic[ 1]:575 Asic[ 2]:575 Asic[ 3]:575 Asic[ 4]:575 Asic[ 5]:575 Asic[ 6]:575 Asic[ 7]:575 Asic[ 8]:575
Asic[ 9]:575 Asic[10]:575 Asic[11]:575 Asic[12]:575 Asic[13]:575 Asic[14]:575 Asic[15]:575 Asic[16]:575
Asic[17]:575
Chain:3 max freq=575
Chain:3 min freq=575

read PIC voltage=930 on chain[12]
Chain:12 chipnum=18
Chain[J13] voltage added=0.0V
Chain:12 base freq=575
Asic[ 0]:575
Asic[ 1]:575 Asic[ 2]:575 Asic[ 3]:575 Asic[ 4]:575 Asic[ 5]:575 Asic[ 6]:575 Asic[ 7]:575 Asic[ 8]:575
Asic[ 9]:575 Asic[10]:575 Asic[11]:575 Asic[12]:575 Asic[13]:575 Asic[14]:575 Asic[15]:575 Asic[16]:575
Asic[17]:575
Chain:12 max freq=575
Chain:12 min freq=575

read PIC voltage=930 on chain[13]
Chain:13 chipnum=18
Chain[J14] voltage added=0.0V
Chain:13 base freq=575
Asic[ 0]:575
Asic[ 1]:575 Asic[ 2]:575 Asic[ 3]:575 Asic[ 4]:575 Asic[ 5]:575 Asic[ 6]:575 Asic[ 7]:575 Asic[ 8]:575
Asic[ 9]:575 Asic[10]:575 Asic[11]:575 Asic[12]:575 Asic[13]:575 Asic[14]:575 Asic[15]:575 Asic[16]:575
Asic[17]:575
Chain:13 max freq=575
Chain:13 min freq=575

max freq = 575
set baud=1
Chain[J13] PIC temp offset=1,0,0,0,0,0,37,28
chain[12] temp chip I2C addr=0x98
chain[12] has no middle temp, use special fix mode.
Chain[J13] chip[0] use PIC middle temp offset=0 typeID=55
New offset Chain[12] chip[0] local:30 remote:34 offset:26
Chain[J13] chip[0] get middle temp offset=26 typeID=55
open core on chain[3] [12] [13]...
set voltage=870 on chain[3], the real voltage=870
Chain[J4] set working voltage=870 [11]
setStartTimePoint total_tv_start_sys=322 total_tv_end_sys=323
restartNum = 2 , auto-reinit enabled...
do read_temp_func once...
do check_asic_reg 0x08

get RT hashrate from Chain[3]: (asic index start from 1-18)
Asic[01]=61.0690 Asic[02]=66.2360 Asic[03]=67.0240 Asic[04]=61.4040 Asic[05]=65.1960 Asic[06]=66.6890 Asic[07]=64.3400 Asic[08]=62.3440
Asic[09]=62.7300 Asic[10]=65.0110 Asic[11]=65.3300 Asic[12]=64.4410 Asic[13]=66.4880 Asic[14]=62.2930 Asic[15]=64.9610 Asic[16]=66.9570
Asic[17]=71.0850 Asic[18]=69.2560

get RT hashrate from Chain[12]: (asic index start from 1-18)
Asic[01]=70.2620 Asic[02]=68.5680 Asic[03]=70.3460 Asic[04]=63.3000 Asic[05]=63.7860 Asic[06]=67.6450 Asic[07]=66.7060 Asic[08]=65.3970
Asic[09]=69.8770 Asic[10]=59.9110 Asic[11]=69.7420 Asic[12]=67.3260 Asic[13]=59.8440 Asic[14]=62.6460 Asic[15]=68.0980 Asic[16]=67.0920
Asic[17]=65.2800 Asic[18]=64.3070

get RT hashrate from Chain[13]: (asic index start from 1-18)
Asic[01]=64.3570 Asic[02]=66.5710 Asic[03]=69.9770 Asic[04]=66.9910 Asic[05]=70.0280 Asic[06]=66.1520 Asic[07]=67.5450 Asic[08]=61.0520
Asic[09]=63.3670 Asic[10]=68.5850 Asic[11]=62.8640 Asic[12]=69.1220 Asic[13]=60.5990 Asic[14]=63.4510 Asic[15]=63.5010 Asic[16]=67.4440
Asic[17]=63.7530 Asic[18]=67.3600
Check Chain[J4] ASIC RT error: (asic index start from 1-18)
Check Chain[J13] ASIC RT error: (asic index start from 1-18)
Check Chain[J14] ASIC RT error: (asic index start from 1-18)
Done check_asic_reg
do read temp on Chain[12]
Chain[12] Chip[1] TempTypeID=55 middle offset=26
Chain[12] Chip[1] local Temp=69
Chain[12] Chip[1] middle Temp=83
Special fix Chain[12] Chip[1] middle Temp = 84
Done read temp on Chain[12]
set FAN speed according to: temp_highest=69 temp_top1[PWM_T]=69 temp_top1[TEMP_POS_LOCAL]=69 temp_change=1 fix_fan_steps=0
FAN PWM: 86
read_temp_func Done!
CRC error counter=24078

here half of my miner is S9 plus

and half of it is t9+

after i reverted back to original t9+ bitmain firmware. it seems you put something on firmware like hardware lock to prevent made change on your fucking scam Firmware. and by now my machine have only 3.5Th/s

and it seems my 2 boards was burned because of your missed up !
all 4 ways reset has been fails

warranty has been void and who will be responsible?

tim-bc

full member

Activity: 538

Merit: 175

Quote from: x3aklili on July 26, 2018, 11:16:20 AM

my T9+ is dead because of your wrong firmware also i revert back to original bitmain firmware but fails .

no any reset method work.

now what should i do ?

If you are still covered by the Bitmain warranty you might be able to get a new one

x3aklili

newbie

Activity: 103

Merit: 0

my T9+ is dead because of your wrong firmware also i revert back to original bitmain firmware but fails .

no any reset method work.

now what should i do ?

taserz

sr. member

Activity: 800

Merit: 294

Created AutoTune to saved the planet! ~USA

Quote from: coinhicken on July 24, 2018, 09:57:03 AM

I probably should. But yours is not a true firmware unless I missed something. It's simply a miner replacement. I will have to write my own management script to modify my little 7 machine farm. It's not a huge deal I just don't have tons of time to work on it at the moment.

It will take you less than 10 minutes to do it to 7 machines. I am working on making it flashable but I rather make it better before making it flashable. Currently mine does everything this one does and more with no dev fee. Hell if there was to be a feed it would be so much smaller than this dude hijacking everyone's machines.

Also this guys firmware is only a modification of bmminer and your ssh password I took a look Wink

coinhicken

newbie

Activity: 20

Merit: 0

Quote from: zacocity on July 25, 2018, 10:29:02 AM

@coinhicken
What things do you need in the firmware?

Good question. Mostly I would like to lower my power usage and heat a little bit. And the auto balance stuff is nice for that. Yes, I can do that all manually but Its a lot of work to do manually. And If I'm going to do that I might as well compile my own firmware from the bitmain source.

Also, anything that locks down the ssh account is a big no. Since I have a remote management system that I wrote that uses ssh to change config and check stats.

zacocity

newbie

Activity: 15

Merit: 0

@coinhicken
What things do you need in the firmware?

coinhicken

newbie

Activity: 20

Merit: 0

Quote from: taserz on July 24, 2018, 01:32:21 AM

Just use my firmware no dev fee and it does the exact same thing.

I probably should. But yours is not a true firmware unless I missed something. It's simply a miner replacement. I will have to write my own management script to modify my little 7 machine farm. It's not a huge deal I just don't have tons of time to work on it at the moment.

Topic: Dollemizer Firmware ASICBOOST Comming! [custom s9, s9i, t9 Firmware upgrade] - page 3. (Read 33180 times)