Antminer T9+ restarts every 3-7 min; Blank Miner status/Hardware ver/BMminer ver

[HobbyMinor]

Hello everyone,

I recently purchased a used (refurbished) Antminer T9+ to get my feet wet with mining BTC and have encountered the following issues.

• The miner restarts every 3-7 minutes. The fans turn on at max speed (starts sounding like a loud vacuum cleaner) and then turns off and restarts.
• On the webpage, my hardware version, bminer version, and miner status are all blank
• I am receiving the "bmminer not found, restart bmminer ..." message in the kernel logs

My PSU is an APW3++ connected to a 240V socket with a 240V 10A cable. I've used a multimeter to test the cable and see that it's yielding the given voltages +/-5%.

I've tried the following steps without any different results.

• Rebooted the machine from both the webpage and unplugged/replugged the cable countless times
• Replaced power cables to the PSU
• Upgraded to the latest T9+ firmware from the Antminer webpage
• Reset the firmware back to factory defaults via the webpage
• Used the ping diagnostics to ensure I was getting a successful response
• Copy and pasted the pool URLs and names from my Antpool account. My username is set to their specs: e.g., abc-t9.001 or abc-t9.10x32

Here are some more details from the webpage and kernel logs

Kernel Version           Linux 3.14.0-xilinx-g16220c3 #83 SMP PREEMPT Thu Jul 12 11:42:53 CST 2018
File System Version   Wed Jul 31 16:20:36 CST 2019
Logic Version            V3.57

Code:

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.14.0-xilinx-g16220c3 (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #83 SMP PREEMPT Thu Jul 12 11:42:53 CST 2018
[    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 16800000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 126976
[    0.000000] free_area_init_node: node 0, pgdat c074ac00, node_mem_map debd8000
[    0.000000]   Normal zone: 992 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 126976 pages, LIFO batch:31
[    0.000000] PERCPU: Embedded 8 pages/cpu @debc1000 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: 125984
[    0.000000] Kernel command line: noinitrd mem=496M console=ttyPS0,115200 root=ubi0:rootfs ubi.mtd=1 rootfstype=ubifs rw rootwait
[    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Memory: 364316K/507904K available (5057K kernel code, 284K rwdata, 1928K rodata, 204K init, 258K bss, 143588K reserved, 0K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xdf800000 - 0xff000000   ( 504 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xdf000000   ( 496 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc06da8ac   (6987 kB)
[    0.000000]       .init : 0xc06db000 - 0xc070e380   ( 205 kB)
[    0.000000]       .data : 0xc0710000 - 0xc0757138   ( 285 kB)
[    0.000000]        .bss : 0xc0757144 - 0xc0797bfc   ( 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 df802000
[    0.000000] zynq_clock_init: clkc starts at df802100
[    0.000000] Zynq clock init
[    0.000014] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 3298534883328ns
[    0.000291] ps7-ttc #0 at df804000, irq=43
[    0.000591] Console: colour dummy device 80x30
[    0.000621] Calibrating delay loop... 1325.46 BogoMIPS (lpj=6627328)
[    0.040196] pid_max: default: 32768 minimum: 301
[    0.040399] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.040418] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.042573] CPU: Testing write buffer coherency: ok
[    0.042882] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.042939] Setting up static identity map for 0x4cb118 - 0x4cb170
[    0.043159] L310 cache controller enabled
[    0.043179] l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x72760000, Cache size: 512 kB
[    0.120984] CPU1: Booted secondary processor
[    0.210218] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.210346] Brought up 2 CPUs
[    0.210365] SMP: Total of 2 processors activated.
[    0.210373] CPU: All CPU(s) started in SVC mode.
[    0.211028] devtmpfs: initialized
[    0.213457] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.214643] regulator-dummy: no parameters
[    0.221978] NET: Registered protocol family 16
[    0.224196] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.226464] cpuidle: using governor ladder
[    0.226478] cpuidle: using governor menu
[    0.233836] syscon f8000000.ps7-slcr: regmap [mem 0xf8000000-0xf8000fff] registered
[    0.235351] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.235365] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.235475] zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xdf880000
[    0.257246] bio: create slab <bio-0> at 0
[    0.258618] vgaarb: loaded
[    0.259312] SCSI subsystem initialized
[    0.260328] usbcore: registered new interface driver usbfs
[    0.260901] usbcore: registered new interface driver hub
[    0.261178] usbcore: registered new device driver usb
[    0.261694] media: Linux media interface: v0.10
[    0.261856] Linux video capture interface: v2.00
[    0.262092] pps_core: LinuxPPS API ver. 1 registered
[    0.262104] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.262224] PTP clock support registered
[    0.262588] EDAC MC: Ver: 3.0.0
[    0.263777] Advanced Linux Sound Architecture Driver Initialized.
[    0.266502] DMA-API: preallocated 4096 debug entries
[    0.266516] DMA-API: debugging enabled by kernel config
[    0.266584] Switched to clocksource arm_global_timer
[    0.286540] NET: Registered protocol family 2
[    0.287487] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[    0.287544] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
[    0.287629] TCP: Hash tables configured (established 4096 bind 4096)
[    0.287671] TCP: reno registered
[    0.287686] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.287717] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.287956] NET: Registered protocol family 1
[    0.288299] RPC: Registered named UNIX socket transport module.
[    0.288311] RPC: Registered udp transport module.
[    0.288319] RPC: Registered tcp transport module.
[    0.288327] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.288340] PCI: CLS 0 bytes, default 64
[    0.288764] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[    0.290754] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.292805] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.292994] msgmni has been set to 967
[    0.293747] io scheduler noop registered
[    0.293759] io scheduler deadline registered
[    0.293804] io scheduler cfq registered (default)
[    0.301794] dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-2364208
[    0.301814] dma-pl330 f8003000.ps7-dma: 	DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[    0.425245] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 82, base_baud = 3124999) is a xuartps
[    0.992134] console [ttyPS0] enabled
[    0.996381] xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to df866000
[    1.004007] [drm] Initialized drm 1.1.0 20060810
[    1.021051] brd: module loaded
[    1.030451] loop: module loaded
[    1.039841] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[    1.045587] e1000e: Copyright(c) 1999 - 2013 Intel Corporation.
[    1.053621] libphy: XEMACPS mii bus: probed
[    1.058024] ------------- phy_id = 0x3625e62
[    1.062738] xemacps e000b000.ps7-ethernet: pdev->id -1, baseaddr 0xe000b000, irq 54
[    1.071409] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.078157] ehci-pci: EHCI PCI platform driver
[    1.085360] zynq-dr e0002000.ps7-usb: Unable to init USB phy, missing?
[    1.092178] usbcore: registered new interface driver usb-storage
[    1.099052] mousedev: PS/2 mouse device common for all mice
[    1.105129] i2c /dev entries driver
[    1.112048] zynq-edac f8006000.ps7-ddrc: ecc not enabled
[    1.117648] cpufreq_cpu0: failed to get cpu0 regulator: -19
[    1.123516] Xilinx Zynq CpuIdle Driver started
[    1.128382] sdhci: Secure Digital Host Controller Interface driver
[    1.134478] sdhci: Copyright(c) Pierre Ossman
[    1.138886] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.145619] mmc0: no vqmmc regulator found
[    1.149655] mmc0: no vmmc regulator found
[    1.186605] mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
[    1.195279] usbcore: registered new interface driver usbhid
[    1.200788] usbhid: USB HID core driver
[    1.205492] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[    1.211784] nand: Micron MT29F2G08ABAEAWP
[    1.215752] nand: 256MiB, SLC, page size: 2048, OOB size: 64
[    1.221694] Bad block table found at page 131008, version 0x01
[    1.227919] Bad block table found at page 130944, version 0x01
[    1.233969] 3 ofpart partitions found on MTD device pl353-nand
[    1.239750] Creating 3 MTD partitions on "pl353-nand":
[    1.244847] 0x000000000000-0x000002000000 : "BOOT.bin-env-dts-kernel"
[    1.252896] 0x000002000000-0x00000b000000 : "angstram-rootfs"
[    1.260219] 0x00000b000000-0x000010000000 : "upgrade-rootfs"
[    1.270931] TCP: cubic registered
[    1.274169] NET: Registered protocol family 17
[    1.278860] Registering SWP/SWPB emulation handler
[    1.284736] regulator-dummy: disabling
[    1.289069] UBI: attaching mtd1 to ubi0
[    1.815738] UBI: scanning is finished
[    1.827349] UBI: attached mtd1 (name "angstram-rootfs", size 144 MiB) to ubi0
[    1.834402] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    1.841188] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    1.847874] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
[    1.854712] UBI: good PEBs: 1152, bad PEBs: 0, corrupted PEBs: 0
[    1.860722] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
[    1.867833] UBI: max/mean erase counter: 3/1, WL threshold: 4096, image sequence number: 1151692613
[    1.876863] UBI: available PEBs: 0, total reserved PEBs: 1152, PEBs reserved for bad PEB handling: 40
[    1.886060] UBI: background thread "ubi_bgt0d" started, PID 1084
[    1.886065] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    1.889994] ALSA device list:
[    1.889998]   No soundcards found.
[    1.906345] UBIFS: background thread "ubifs_bgt0_0" started, PID 1086
[    1.974517] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[    1.980469] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    1.989571] UBIFS: FS size: 128626688 bytes (122 MiB, 1013 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[    1.999461] UBIFS: reserved for root: 0 bytes (0 KiB)
[    2.004490] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 7CB6B46E-224A-4550-9A92-F6ED1D649181, small LPT model
[    2.016009] VFS: Mounted root (ubifs filesystem) on device 0:11.
[    2.023236] devtmpfs: mounted
[    2.026345] Freeing unused kernel memory: 204K (c06db000 - c070e000)
[    2.861195] random: dd urandom read with 1 bits of entropy available
[    3.246624] 
[    3.246624] bcm54xx_config_init
[    4.306624] 
[    4.306624] bcm54xx_config_init
[    8.307456] xemacps e000b000.ps7-ethernet: Set clk to 124999998 Hz
[    8.313559] xemacps e000b000.ps7-ethernet: link up (1000/FULL)
[   26.065607] In axi fpga driver!
[   26.068699] request_mem_region OK!
[   26.072064] AXI fpga dev virtual address is 0xdf9fe000
[   26.077195] *base_vir_addr = 0xc725
[   26.092392] In fpga mem driver!
[   26.095459] request_mem_region OK!
[   26.099050] fpga mem virtual address is 0xe2000000
[   26.896621] 
[   26.896621] bcm54xx_config_init
[   27.996626] 
[   27.996626] bcm54xx_config_init
[   31.997457] xemacps e000b000.ps7-ethernet: Set clk to 124999998 Hz
[   32.003564] xemacps e000b000.ps7-ethernet: link up (1000/FULL)
main.c:13992: log_level = 4
main.c:14019: This is XILINX board. Totalram:       507486208
main.c:14031: Detect 512MB control board of XILINX
driver-bitmain.c:1776: mmap axi_fpga_addr = 0xb6f70000
driver-bitmain.c:1781: axi_fpga_addr data = 0xc725
driver-bitmain.c:1797: mmap fpga_mem_addr = 0xb5d69000
driver-bitmain.c:994: forceFreq=-1 forceFlag=0
driver-bitmain.c:1696: min work minertest[0]:912


main.c:8570: DETECT HW version=8000c725
main.c:14064: miner ID : 80228d4675104814
main.c:14097: Miner Type = T9+
main.c:14101: AsicType = 1387
main.c:14104: real AsicNum = 18
main.c:14197: use critical mode to search freq...
driver-bitmain.c:1876: get PLUG ON=0x07003f0e
driver-bitmain.c:1907: Find hashboard on Chain[1]
driver-bitmain.c:1907: Find hashboard on Chain[2]
driver-bitmain.c:1907: Find hashboard on Chain[3]
driver-bitmain.c:1907: Find hashboard on Chain[8]
driver-bitmain.c:1907: Find hashboard on Chain[9]
driver-bitmain.c:1907: Find hashboard on Chain[10]
driver-bitmain.c:1907: Find hashboard on Chain[11]
driver-bitmain.c:1907: Find hashboard on Chain[12]
driver-bitmain.c:1907: Find hashboard on Chain[13]
main.c:2126: chain[1] PIC jump to app
main.c:2134: Check chain[1] PIC fw version=0x90
main.c:2126: chain[2] PIC jump to app
main.c:2134: Check chain[2] PIC fw version=0x90
main.c:2126: chain[3] PIC jump to app
main.c:2134: Check chain[3] PIC fw version=0x90
main.c:8651: 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 
main.c:8665: chain[1]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255]
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9022: chain[1] has freq in PIC and will jump over...
main.c:9026: Chain[1] has core num in PIC
main.c:8651: 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 
main.c:8665: chain[2]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255]
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9022: chain[2] has freq in PIC and will jump over...
main.c:9026: Chain[2] has core num in PIC
main.c:8651: 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 0x01 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 
main.c:8665: chain[3]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255]
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9022: chain[3] has freq in PIC and will jump over...
main.c:9026: Chain[3] has core num in PIC
main.c:9036: Chain[3] ASIC[3] has core num=1
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9022: chain[8] has freq in PIC and will jump over...
main.c:9026: Chain[8] has core num in PIC
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9022: chain[9] has freq in PIC and will jump over...
main.c:9026: Chain[9] has core num in PIC
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9022: chain[10] has freq in PIC and will jump over...
main.c:9026: Chain[10] has core num in PIC
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9022: chain[11] has freq in PIC and will jump over...
main.c:9026: Chain[11] has core num in PIC
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9022: chain[12] has freq in PIC and will jump over...
main.c:9026: Chain[12] has core num in PIC
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9022: chain[13] has freq in PIC and will jump over...
main.c:9026: Chain[13] has core num in PIC
main.c:9183: get PIC voltage=7 on chain[1], value=890
main.c:9183: get PIC voltage=7 on chain[2], value=890
main.c:9183: get PIC voltage=7 on chain[3], value=890
main.c:9183: get PIC voltage=7 on chain[8], value=890
main.c:9183: get PIC voltage=7 on chain[9], value=890
main.c:9183: get PIC voltage=7 on chain[10], value=890
main.c:9183: get PIC voltage=7 on chain[11], value=890
main.c:9183: get PIC voltage=7 on chain[12], value=890
main.c:9183: get PIC voltage=7 on chain[13], value=890
main.c:9349: chain[8] temp offset record: 1,3,0,0,0,0,33,28
main.c:9366: chain[8] temp chip I2C addr=0x98
main.c:9349: chain[10] temp offset record: 1,2,0,0,0,0,33,28
main.c:9366: chain[10] temp chip I2C addr=0x98
main.c:9349: chain[12] temp offset record: 1,2,0,0,0,0,33,28
main.c:9366: chain[12] temp chip I2C addr=0x98
main.c:13956: total_exist_chain_num = 9
main.c:9562: CRC error counter=0
main.c:9577: set command mode to VIL
main.c:9649: 
--- check asic number
main.c:9745: After Get ASIC NUM CRC error counter=0
main.c:9768: set_baud=0
main.c:10693: The min freq=700
main.c:10695: set real timeout 52, need sleep=379392
main.c:12825: After TEST CRC error counter=0
main.c:14236: search freq for 1 times, completed chain = 9, total chain num = 9 
main.c:14645: restart Miner chance num=2
main.c:14685: waiting for receive_func to exit!
main.c:14699: waiting for pic heart to exit!
main.c:13927: bmminer not found= 1874 root       0:00 grep bmminer

main.c:14758: bmminer not found, restart bmminer ...
driver-btm-c5.c:12243:bitmain_c5_init: This is user mode for mining
driver-btm-c5.c:12292:bitmain_c5_init: Detect 512MB control board of XILINX
driver-btm-c5.c:12321:bitmain_c5_init: Miner Type = T9+
driver-btm-c5.c:12324:bitmain_c5_init: Miner compile time: Wed Jul 31 16:20:36 CST 2019 type: Antminer T9+
driver-btm-c5.c:12414:bitmain_c5_init: miner ID : 80228d4675104814
driver-btm-c5.c:12571:bitmain_c5_init: Checking fans...
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[4] speed=5880
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[5] speed=5640
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[4] speed=5880
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[5] speed=5640
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[4] speed=5880
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[5] speed=5640
driver-btm-c5.c:1680:jump_to_app_CheckAndRestorePIC_T9_18: chain[1] PIC jump to app
driver-btm-c5.c:1685:jump_to_app_CheckAndRestorePIC_T9_18: Check chain[1] PIC fw version=0x90
driver-btm-c5.c:12624:bitmain_c5_init: 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 
driver-btm-c5.c:12639:bitmain_c5_init: chain[1]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255]
driver-btm-c5.c:12784:bitmain_c5_init: Chain[J2] has backup chain_voltage=870
driver-btm-c5.c:12794:bitmain_c5_init: Detect: use voltage limit rules on single board!
driver-btm-c5.c:12800:bitmain_c5_init: Detect: T9+ use voltage level=1
driver-btm-c5.c:12808:bitmain_c5_init: Chain[J2] test patten OK temp=-1
driver-btm-c5.c:1680:jump_to_app_CheckAndRestorePIC_T9_18: chain[2] PIC jump to app
driver-btm-c5.c:1685:jump_to_app_CheckAndRestorePIC_T9_18: Check chain[2] PIC fw version=0x90
driver-btm-c5.c:12624:bitmain_c5_init: 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 
driver-btm-c5.c:12639:bitmain_c5_init: chain[2]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255]
driver-btm-c5.c:12784:bitmain_c5_init: Chain[J3] has backup chain_voltage=870
driver-btm-c5.c:12794:bitmain_c5_init: Detect: use voltage limit rules on single board!
driver-btm-c5.c:12800:bitmain_c5_init: Detect: T9+ use voltage level=1
driver-btm-c5.c:12808:bitmain_c5_init: Chain[J3] test patten OK temp=-1
driver-btm-c5.c:1680:jump_to_app_CheckAndRestorePIC_T9_18: chain[3] PIC jump to app
driver-btm-c5.c:1685:jump_to_app_CheckAndRestorePIC_T9_18: Check chain[3] PIC fw version=0x90
driver-btm-c5.c:12624:bitmain_c5_init: 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 0x01 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 
driver-btm-c5.c:12639:bitmain_c5_init: chain[3]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255]
driver-btm-c5.c:12784:bitmain_c5_init: Chain[J4] has backup chain_voltage=870
driver-btm-c5.c:12794:bitmain_c5_init: Detect: use voltage limit rules on single board!
driver-btm-c5.c:12800:bitmain_c5_init: Detect: T9+ use voltage level=1
driver-btm-c5.c:12808:bitmain_c5_init: Chain[J4] test patten OK temp=-1
driver-btm-c5.c:12784:bitmain_c5_init: Chain[J9] has backup chain_voltage=870
driver-btm-c5.c:12794:bitmain_c5_init: Detect: use voltage limit rules on single board!
driver-btm-c5.c:12800:bitmain_c5_init: Detect: T9+ use voltage level=1
driver-btm-c5.c:12808:bitmain_c5_init: Chain[J9] test patten OK temp=-1
driver-btm-c5.c:12784:bitmain_c5_init: Chain[J10] has backup chain_voltage=870
driver-btm-c5.c:12794:bitmain_c5_init: Detect: use voltage limit rules on single board!
driver-btm-c5.c:12800:bitmain_c5_init: Detect: T9+ use voltage level=1
driver-btm-c5.c:12808:bitmain_c5_init: Chain[J10] test patten OK temp=-1
driver-btm-c5.c:12784:bitmain_c5_init: Chain[J11] has backup chain_voltage=870
driver-btm-c5.c:12794:bitmain_c5_init: Detect: use voltage limit rules on single board!
driver-btm-c5.c:12800:bitmain_c5_init: Detect: T9+ use voltage level=1
driver-btm-c5.c:12808:bitmain_c5_init: Chain[J11] test patten OK temp=-1
driver-btm-c5.c:12784:bitmain_c5_init: Chain[J12] has backup chain_voltage=870
driver-btm-c5.c:12794:bitmain_c5_init: Detect: use voltage limit rules on single board!
driver-btm-c5.c:12800:bitmain_c5_init: Detect: T9+ use voltage level=1
driver-btm-c5.c:12808:bitmain_c5_init: Chain[J12] test patten OK temp=-1
driver-btm-c5.c:12784:bitmain_c5_init: Chain[J13] has backup chain_voltage=870
driver-btm-c5.c:12794:bitmain_c5_init: Detect: use voltage limit rules on single board!
driver-btm-c5.c:12800:bitmain_c5_init: Detect: T9+ use voltage level=1
driver-btm-c5.c:12808:bitmain_c5_init: Chain[J13] test patten OK temp=-1
driver-btm-c5.c:12784:bitmain_c5_init: Chain[J14] has backup chain_voltage=870
driver-btm-c5.c:12794:bitmain_c5_init: Detect: use voltage limit rules on single board!
driver-btm-c5.c:12800:bitmain_c5_init: Detect: T9+ use voltage level=1
driver-btm-c5.c:12808:bitmain_c5_init: Chain[J14] test patten OK temp=-1
driver-btm-c5.c:12195:init_exist_chain_table: total_exist_chain_num = 9
driver-btm-c5.c:13239:bitmain_c5_init: Chain[J2] will use voltage=890 [7] to open core
driver-btm-c5.c:2168:set_Voltage_S9_plus_plus_BM1387_54: set voltage 7 seccessful
driver-btm-c5.c:13239:bitmain_c5_init: Chain[J3] will use voltage=890 [7] to open core
driver-btm-c5.c:2168:set_Voltage_S9_plus_plus_BM1387_54: set voltage 7 seccessful
driver-btm-c5.c:13239:bitmain_c5_init: Chain[J4] will use voltage=890 [7] to open core
driver-btm-c5.c:2168:set_Voltage_S9_plus_plus_BM1387_54: set voltage 7 seccessful
driver-btm-c5.c:13239:bitmain_c5_init: Chain[J9] will use voltage=890 [7] to open core
driver-btm-c5.c:13239:bitmain_c5_init: Chain[J10] will use voltage=890 [7] to open core
driver-btm-c5.c:13239:bitmain_c5_init: Chain[J11] will use voltage=890 [7] to open core
driver-btm-c5.c:13239:bitmain_c5_init: Chain[J12] will use voltage=890 [7] to open core
driver-btm-c5.c:13239:bitmain_c5_init: Chain[J13] will use voltage=890 [7] to open core
driver-btm-c5.c:13239:bitmain_c5_init: Chain[J14] will use voltage=890 [7] to open core
driver-btm-c5.c:13303:bitmain_c5_init: Chain[J2] orignal chain_voltage_pic=7 value=890
driver-btm-c5.c:13320:bitmain_c5_init: Chain[J2] will use backup chain_voltage_pic=870 [11]
driver-btm-c5.c:13330:bitmain_c5_init: Chain[J2] get working chain_voltage_pic=11
driver-btm-c5.c:13303:bitmain_c5_init: Chain[J3] orignal chain_voltage_pic=7 value=890
driver-btm-c5.c:13320:bitmain_c5_init: Chain[J3] will use backup chain_voltage_pic=870 [11]
driver-btm-c5.c:13330:bitmain_c5_init: Chain[J3] get working chain_voltage_pic=11
driver-btm-c5.c:13303:bitmain_c5_init: Chain[J4] orignal chain_voltage_pic=7 value=890
driver-btm-c5.c:13320:bitmain_c5_init: Chain[J4] will use backup chain_voltage_pic=870 [11]
driver-btm-c5.c:13330:bitmain_c5_init: Chain[J4] get working chain_voltage_pic=11
driver-btm-c5.c:13303:bitmain_c5_init: Chain[J9] orignal chain_voltage_pic=7 value=890
driver-btm-c5.c:13320:bitmain_c5_init: Chain[J9] will use backup chain_voltage_pic=870 [11]
driver-btm-c5.c:13330:bitmain_c5_init: Chain[J9] get working chain_voltage_pic=11
driver-btm-c5.c:13303:bitmain_c5_init: Chain[J10] orignal chain_voltage_pic=7 value=890
driver-btm-c5.c:13320:bitmain_c5_init: Chain[J10] will use backup chain_voltage_pic=870 [11]
driver-btm-c5.c:13330:bitmain_c5_init: Chain[J10] get working chain_voltage_pic=11
driver-btm-c5.c:13303:bitmain_c5_init: Chain[J11] orignal chain_voltage_pic=7 value=890
driver-btm-c5.c:13320:bitmain_c5_init: Chain[J11] will use backup chain_voltage_pic=870 [11]
driver-btm-c5.c:13330:bitmain_c5_init: Chain[J11] get working chain_voltage_pic=11
driver-btm-c5.c:13303:bitmain_c5_init: Chain[J12] orignal chain_voltage_pic=7 value=890
driver-btm-c5.c:13320:bitmain_c5_init: Chain[J12] will use backup chain_voltage_pic=870 [11]
driver-btm-c5.c:13330:bitmain_c5_init: Chain[J12] get working chain_voltage_pic=11
driver-btm-c5.c:13303:bitmain_c5_init: Chain[J13] orignal chain_voltage_pic=7 value=890
driver-btm-c5.c:13320:bitmain_c5_init: Chain[J13] will use backup chain_voltage_pic=870 [11]
driver-btm-c5.c:13330:bitmain_c5_init: Chain[J13] get working chain_voltage_pic=11
driver-btm-c5.c:13303:bitmain_c5_init: Chain[J14] orignal chain_voltage_pic=7 value=890
driver-btm-c5.c:13320:bitmain_c5_init: Chain[J14] will use backup chain_voltage_pic=870 [11]
driver-btm-c5.c:13330:bitmain_c5_init: Chain[J14] get working chain_voltage_pic=11

Thank you for the assistance, all.

[BitMaxz]

How about the temp on the miner's status on the WebGUI? Can you make a screenshot? And post it here.

Or try to flash it through SD card flashing. You can make an SD card program recovery by following the guide below.

- T9-Control-Board-Program-Recovery

Don't forget to switch the JP4 before you put the SD card.

[mikeywith]

There might be an issue with how you use the pool/worker details, Antpool is the worst pool to test a miner with, I usually test cksolo as you can't make any mistakes as long as you use a valid BTC address, so please try the following:

URL:

Code:

stratum+tcp://solo.ckpool.org:3333

Worker:

Code:

1PKN98VN2z5gwSGZvGKS2bj8aADZBkyhkZ

Password:

Code:

x

Allow up to 15 mins before you reboot the miner, if it starts mining then you know your issue was Antpool, if the problem remains, then I would like to see a screenshot of the miner status page and the system view (main page).

[NotFuzzyWarm]

When using copy/paste you have to be careful and make sure there are no whitespaces that got copied as well as the text, they are usually at the end of the text you pasted. Most miners and pools do not like a whitespace and treat it as an invalid character so will not connect.

[HobbyMinor]

There might be an issue with how you use the pool/worker details, Antpool is the worst pool to test a miner with, I usually test cksolo as you can't make any mistakes as long as you use a valid BTC address, so please try the following...

Thanks for the test data. I'll try this suggestion out before I start flashing with the firmware. By the way, your post on the Internet Connection Sharing was ingenious; I ran out of long enough RJ-45 cables.

Yeah, I was very paranoid about having no extra spaces.


I've tried the suggestion of switching over to the other pool with the same results. Interestingly, the kernel logs are showing something about a PIC failure now.

Code:

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.14.0-xilinx-g16220c3 (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #83 SMP PREEMPT Thu Jul 12 11:42:53 CST 2018
[    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 16800000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 126976
[    0.000000] free_area_init_node: node 0, pgdat c074ac00, node_mem_map debd8000
[    0.000000]   Normal zone: 992 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 126976 pages, LIFO batch:31
[    0.000000] PERCPU: Embedded 8 pages/cpu @debc1000 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: 125984
[    0.000000] Kernel command line: noinitrd mem=496M console=ttyPS0,115200 root=ubi0:rootfs ubi.mtd=1 rootfstype=ubifs rw rootwait
[    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Memory: 364316K/507904K available (5057K kernel code, 284K rwdata, 1928K rodata, 204K init, 258K bss, 143588K reserved, 0K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xdf800000 - 0xff000000   ( 504 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xdf000000   ( 496 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc06da8ac   (6987 kB)
[    0.000000]       .init : 0xc06db000 - 0xc070e380   ( 205 kB)
[    0.000000]       .data : 0xc0710000 - 0xc0757138   ( 285 kB)
[    0.000000]        .bss : 0xc0757144 - 0xc0797bfc   ( 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 df802000
[    0.000000] zynq_clock_init: clkc starts at df802100
[    0.000000] Zynq clock init
[    0.000014] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 3298534883328ns
[    0.000290] ps7-ttc #0 at df804000, irq=43
[    0.000588] Console: colour dummy device 80x30
[    0.000618] Calibrating delay loop... 1332.01 BogoMIPS (lpj=6660096)
[    0.090240] pid_max: default: 32768 minimum: 301
[    0.090446] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.090467] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.092619] CPU: Testing write buffer coherency: ok
[    0.092929] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.092985] Setting up static identity map for 0x4cb118 - 0x4cb170
[    0.093206] L310 cache controller enabled
[    0.093226] l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x72760000, Cache size: 512 kB
[    0.170984] CPU1: Booted secondary processor
[    0.260218] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.260346] Brought up 2 CPUs
[    0.260365] SMP: Total of 2 processors activated.
[    0.260373] CPU: All CPU(s) started in SVC mode.
[    0.261030] devtmpfs: initialized
[    0.263460] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.264644] regulator-dummy: no parameters
[    0.271507] NET: Registered protocol family 16
[    0.273773] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.276036] cpuidle: using governor ladder
[    0.276050] cpuidle: using governor menu
[    0.283421] syscon f8000000.ps7-slcr: regmap [mem 0xf8000000-0xf8000fff] registered
[    0.284932] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.284946] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.285054] zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xdf880000
[    0.306693] bio: create slab <bio-0> at 0
[    0.308083] vgaarb: loaded
[    0.308796] SCSI subsystem initialized
[    0.309663] usbcore: registered new interface driver usbfs
[    0.309850] usbcore: registered new interface driver hub
[    0.310075] usbcore: registered new device driver usb
[    0.310729] media: Linux media interface: v0.10
[    0.310886] Linux video capture interface: v2.00
[    0.311423] pps_core: LinuxPPS API ver. 1 registered
[    0.311436] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.311578] PTP clock support registered
[    0.311933] EDAC MC: Ver: 3.0.0
[    0.313136] Advanced Linux Sound Architecture Driver Initialized.
[    0.315854] DMA-API: preallocated 4096 debug entries
[    0.315867] DMA-API: debugging enabled by kernel config
[    0.315936] Switched to clocksource arm_global_timer
[    0.336511] NET: Registered protocol family 2
[    0.337169] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[    0.337225] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
[    0.337310] TCP: Hash tables configured (established 4096 bind 4096)
[    0.337356] TCP: reno registered
[    0.337373] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.337405] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.337631] NET: Registered protocol family 1
[    0.337957] RPC: Registered named UNIX socket transport module.
[    0.337970] RPC: Registered udp transport module.
[    0.337979] RPC: Registered tcp transport module.
[    0.337987] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.337999] PCI: CLS 0 bytes, default 64
[    0.338415] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[    0.340393] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.342458] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.342662] msgmni has been set to 967
[    0.343419] io scheduler noop registered
[    0.343432] io scheduler deadline registered
[    0.343472] io scheduler cfq registered (default)
[    0.356625] dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-2364208
[    0.356645] dma-pl330 f8003000.ps7-dma: 	DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[    0.479321] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 82, base_baud = 3124999) is a xuartps
[    1.046635] console [ttyPS0] enabled
[    1.050874] xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to df866000
[    1.058504] [drm] Initialized drm 1.1.0 20060810
[    1.075422] brd: module loaded
[    1.084804] loop: module loaded
[    1.094234] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[    1.100209] e1000e: Copyright(c) 1999 - 2013 Intel Corporation.
[    1.107942] libphy: XEMACPS mii bus: probed
[    1.112309] ------------- phy_id = 0x3625e62
[    1.117250] xemacps e000b000.ps7-ethernet: pdev->id -1, baseaddr 0xe000b000, irq 54
[    1.125858] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.132504] ehci-pci: EHCI PCI platform driver
[    1.139745] zynq-dr e0002000.ps7-usb: Unable to init USB phy, missing?
[    1.146559] usbcore: registered new interface driver usb-storage
[    1.153385] mousedev: PS/2 mouse device common for all mice
[    1.159562] i2c /dev entries driver
[    1.166482] zynq-edac f8006000.ps7-ddrc: ecc not enabled
[    1.171957] cpufreq_cpu0: failed to get cpu0 regulator: -19
[    1.177860] Xilinx Zynq CpuIdle Driver started
[    1.182702] sdhci: Secure Digital Host Controller Interface driver
[    1.188883] sdhci: Copyright(c) Pierre Ossman
[    1.193154] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.199974] mmc0: no vqmmc regulator found
[    1.203990] mmc0: no vmmc regulator found
[    1.245955] mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
[    1.254644] usbcore: registered new interface driver usbhid
[    1.260151] usbhid: USB HID core driver
[    1.264848] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[    1.271149] nand: Micron MT29F2G08ABAEAWP
[    1.275114] nand: 256MiB, SLC, page size: 2048, OOB size: 64
[    1.281056] Bad block table found at page 131008, version 0x01
[    1.287283] Bad block table found at page 130944, version 0x01
[    1.293330] 3 ofpart partitions found on MTD device pl353-nand
[    1.299114] Creating 3 MTD partitions on "pl353-nand":
[    1.304204] 0x000000000000-0x000002000000 : "BOOT.bin-env-dts-kernel"
[    1.312265] 0x000002000000-0x00000b000000 : "angstram-rootfs"
[    1.319583] 0x00000b000000-0x000010000000 : "upgrade-rootfs"
[    1.330294] TCP: cubic registered
[    1.333530] NET: Registered protocol family 17
[    1.338224] Registering SWP/SWPB emulation handler
[    1.344089] regulator-dummy: disabling
[    1.348394] UBI: attaching mtd1 to ubi0
[    1.874935] UBI: scanning is finished
[    1.886564] UBI: attached mtd1 (name "angstram-rootfs", size 144 MiB) to ubi0
[    1.893615] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    1.900403] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    1.907087] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
[    1.913926] UBI: good PEBs: 1152, bad PEBs: 0, corrupted PEBs: 0
[    1.919936] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
[    1.927047] UBI: max/mean erase counter: 3/1, WL threshold: 4096, image sequence number: 1151692613
[    1.936077] UBI: available PEBs: 0, total reserved PEBs: 1152, PEBs reserved for bad PEB handling: 40
[    1.945273] UBI: background thread "ubi_bgt0d" started, PID 1084
[    1.945278] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    1.949214] ALSA device list:
[    1.949217]   No soundcards found.
[    1.965566] UBIFS: background thread "ubifs_bgt0_0" started, PID 1086
[    2.019287] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[    2.025216] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    2.034365] UBIFS: FS size: 128626688 bytes (122 MiB, 1013 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[    2.044241] UBIFS: reserved for root: 0 bytes (0 KiB)
[    2.049351] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 7CB6B46E-224A-4550-9A92-F6ED1D649181, small LPT model
[    2.060824] VFS: Mounted root (ubifs filesystem) on device 0:11.
[    2.068017] devtmpfs: mounted
[    2.071125] Freeing unused kernel memory: 204K (c06db000 - c070e000)
[    2.908882] random: dd urandom read with 1 bits of entropy available
[    3.295979] 
[    3.295979] bcm54xx_config_init
[    4.365984] 
[    4.365984] bcm54xx_config_init
[    9.366811] xemacps e000b000.ps7-ethernet: Set clk to 124999998 Hz
[    9.372915] xemacps e000b000.ps7-ethernet: link up (1000/FULL)
[   31.376755] xemacps e000b000.ps7-ethernet: link down
[   34.376763] xemacps e000b000.ps7-ethernet: link up (1000/FULL)
[   36.376768] xemacps e000b000.ps7-ethernet: link down
[   39.376769] xemacps e000b000.ps7-ethernet: link up (1000/FULL)
[   41.262585] In axi fpga driver!
[   41.265657] request_mem_region OK!
[   41.269068] AXI fpga dev virtual address is 0xdf9fe000
[   41.274155] *base_vir_addr = 0xc725
[   41.288863] In fpga mem driver!
[   41.292095] request_mem_region OK!
[   41.295651] fpga mem virtual address is 0xe2000000
[   41.376798] xemacps e000b000.ps7-ethernet: link down
[   46.376795] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz
[   46.382880] xemacps e000b000.ps7-ethernet: link up (100/FULL)
[   47.125965] 
[   47.125965] bcm54xx_config_init
[   48.215947] 
[   48.215947] bcm54xx_config_init
[   60.216791] xemacps e000b000.ps7-ethernet: Set clk to 124999998 Hz
[   60.222930] xemacps e000b000.ps7-ethernet: link up (1000/FULL)
[   62.226756] xemacps e000b000.ps7-ethernet: link down
[   64.226789] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz
[   64.232862] xemacps e000b000.ps7-ethernet: link up (100/FULL)
main.c:13992: log_level = 4
main.c:14019: This is XILINX board. Totalram:       507486208
main.c:14031: Detect 512MB control board of XILINX
driver-bitmain.c:1776: mmap axi_fpga_addr = 0xb6f29000
driver-bitmain.c:1781: axi_fpga_addr data = 0xc725
driver-bitmain.c:1797: mmap fpga_mem_addr = 0xb5d22000
driver-bitmain.c:994: forceFreq=-1 forceFlag=0
driver-bitmain.c:1696: min work minertest[0]:912


main.c:8570: DETECT HW version=8000c725
main.c:14064: miner ID : 80228d4675104814
main.c:14097: Miner Type = T9+
main.c:14101: AsicType = 1387
main.c:14104: real AsicNum = 18
main.c:14197: use critical mode to search freq...
driver-bitmain.c:1876: get PLUG ON=0x07003f0e
driver-bitmain.c:1907: Find hashboard on Chain[1]
driver-bitmain.c:1907: Find hashboard on Chain[2]
driver-bitmain.c:1907: Find hashboard on Chain[3]
driver-bitmain.c:1907: Find hashboard on Chain[8]
driver-bitmain.c:1907: Find hashboard on Chain[9]
driver-bitmain.c:1907: Find hashboard on Chain[10]
driver-bitmain.c:1907: Find hashboard on Chain[11]
driver-bitmain.c:1907: Find hashboard on Chain[12]
driver-bitmain.c:1907: Find hashboard on Chain[13]
main.c:2126: chain[1] PIC jump to app
main.c:2134: Check chain[1] PIC fw version=0x90
main.c:2126: chain[2] PIC jump to app
main.c:2134: Check chain[2] PIC fw version=0x90
main.c:2126: chain[3] PIC jump to app
main.c:2134: Check chain[3] PIC fw version=0x90
main.c:8651: 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 
main.c:8665: chain[1]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255]
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9022: chain[1] has freq in PIC and will jump over...
main.c:9026: Chain[1] has core num in PIC
main.c:8651: 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 
main.c:8665: chain[2]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255]
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9022: chain[2] has freq in PIC and will jump over...
main.c:9026: Chain[2] has core num in PIC
main.c:8651: 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 0x01 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 
main.c:8665: chain[3]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255]
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9022: chain[3] has freq in PIC and will jump over...
main.c:9026: Chain[3] has core num in PIC
main.c:9036: Chain[3] ASIC[3] has core num=1
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9022: chain[8] has freq in PIC and will jump over...
main.c:9026: Chain[8] has core num in PIC
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9022: chain[9] has freq in PIC and will jump over...
main.c:9026: Chain[9] has core num in PIC
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9022: chain[10] has freq in PIC and will jump over...
main.c:9026: Chain[10] has core num in PIC
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9022: chain[11] has freq in PIC and will jump over...
main.c:9026: Chain[11] has core num in PIC
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9022: chain[12] has freq in PIC and will jump over...
main.c:9026: Chain[12] has core num in PIC
main.c:9003: has freq in PIC, will disable freq setting.
main.c:9022: chain[13] has freq in PIC and will jump over...
main.c:9026: Chain[13] has core num in PIC
main.c:9183: get PIC voltage=7 on chain[1], value=890
main.c:9183: get PIC voltage=7 on chain[2], value=890
main.c:9183: get PIC voltage=7 on chain[3], value=890
main.c:9183: get PIC voltage=7 on chain[8], value=890
main.c:9183: get PIC voltage=7 on chain[9], value=890
main.c:9183: get PIC voltage=7 on chain[10], value=890
main.c:9183: get PIC voltage=7 on chain[11], value=890
main.c:9183: get PIC voltage=7 on chain[12], value=890
main.c:9183: get PIC voltage=7 on chain[13], value=890
main.c:9349: chain[8] temp offset record: 1,3,0,0,0,0,33,28
main.c:9366: chain[8] temp chip I2C addr=0x98
main.c:9349: chain[10] temp offset record: 1,2,0,0,0,0,33,28
main.c:9366: chain[10] temp chip I2C addr=0x98
main.c:9349: chain[12] temp offset record: 1,2,0,0,0,0,33,28
main.c:9366: chain[12] temp chip I2C addr=0x98
main.c:13956: total_exist_chain_num = 9
main.c:9562: CRC error counter=0
main.c:9577: set command mode to VIL
main.c:9649: 
--- check asic number
main.c:9745: After Get ASIC NUM CRC error counter=0
main.c:9768: set_baud=0
main.c:10693: The min freq=700
main.c:10695: set real timeout 52, need sleep=379392
main.c:12825: After TEST CRC error counter=0
main.c:14236: search freq for 1 times, completed chain = 9, total chain num = 9 
main.c:14645: restart Miner chance num=2
main.c:14685: waiting for receive_func to exit!
main.c:14699: waiting for pic heart to exit!
main.c:13927: bmminer not found= 1982 root       0:00 grep bmminer

main.c:14758: bmminer not found, restart bmminer ...
driver-btm-c5.c:12243:bitmain_c5_init: This is user mode for mining
driver-btm-c5.c:12292:bitmain_c5_init: Detect 512MB control board of XILINX
driver-btm-c5.c:12321:bitmain_c5_init: Miner Type = T9+
driver-btm-c5.c:12324:bitmain_c5_init: Miner compile time: Wed Jul 31 16:20:36 CST 2019 type: Antminer T9+
driver-btm-c5.c:12414:bitmain_c5_init: miner ID : 80228d4675104814
driver-btm-c5.c:12571:bitmain_c5_init: Checking fans...
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[4] speed=5880
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[5] speed=5640
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[4] speed=5880
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[5] speed=5640
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[4] speed=5880
driver-btm-c5.c:3006:check_fan_beforeInit: get fan[5] speed=5640
driver-btm-c5.c:1680:jump_to_app_CheckAndRestorePIC_T9_18: chain[1] PIC jump to app
driver-btm-c5.c:1685:jump_to_app_CheckAndRestorePIC_T9_18: Check chain[1] PIC fw version=0x90
driver-btm-c5.c:12624:bitmain_c5_init: 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 
driver-btm-c5.c:12639:bitmain_c5_init: chain[1]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255]
driver-btm-c5.c:12784:bitmain_c5_init: Chain[J2] has backup chain_voltage=870
driver-btm-c5.c:12794:bitmain_c5_init: Detect: use voltage limit rules on single board!
driver-btm-c5.c:12800:bitmain_c5_init: Detect: T9+ use voltage level=1
driver-btm-c5.c:12808:bitmain_c5_init: Chain[J2] test patten OK temp=-1
driver-btm-c5.c:1680:jump_to_app_CheckAndRestorePIC_T9_18: chain[2] PIC jump to app
driver-btm-c5.c:1685:jump_to_app_CheckAndRestorePIC_T9_18: Check chain[2] PIC fw version=0x90
driver-btm-c5.c:12624:bitmain_c5_init: 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 
driver-btm-c5.c:12639:bitmain_c5_init: chain[2]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255]
driver-btm-c5.c:12784:bitmain_c5_init: Chain[J3] has backup chain_voltage=870
driver-btm-c5.c:12794:bitmain_c5_init: Detect: use voltage limit rules on single board!
driver-btm-c5.c:12800:bitmain_c5_init: Detect: T9+ use voltage level=1
driver-btm-c5.c:12808:bitmain_c5_init: Chain[J3] test patten OK temp=-1
driver-btm-c5.c:1680:jump_to_app_CheckAndRestorePIC_T9_18: chain[3] PIC jump to app
driver-btm-c5.c:1685:jump_to_app_CheckAndRestorePIC_T9_18: Check chain[3] PIC fw version=0x90
driver-btm-c5.c:12624:bitmain_c5_init: 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 0x01 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 
driver-btm-c5.c:12639:bitmain_c5_init: chain[3]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255]
driver-btm-c5.c:12784:bitmain_c5_init: Chain[J4] has backup chain_voltage=870
driver-btm-c5.c:12794:bitmain_c5_init: Detect: use voltage limit rules on single board!
driver-btm-c5.c:12800:bitmain_c5_init: Detect: T9+ use voltage level=1
driver-btm-c5.c:12808:bitmain_c5_init: Chain[J4] test patten OK temp=-1
driver-btm-c5.c:12784:bitmain_c5_init: Chain[J9] has backup chain_voltage=870
driver-btm-c5.c:12794:bitmain_c5_init: Detect: use voltage limit rules on single board!
driver-btm-c5.c:12800:bitmain_c5_init: Detect: T9+ use voltage level=1
driver-btm-c5.c:12808:bitmain_c5_init: Chain[J9] test patten OK temp=-1
driver-btm-c5.c:12784:bitmain_c5_init: Chain[J10] has backup chain_voltage=870
driver-btm-c5.c:12794:bitmain_c5_init: Detect: use voltage limit rules on single board!
driver-btm-c5.c:12800:bitmain_c5_init: Detect: T9+ use voltage level=1
driver-btm-c5.c:12808:bitmain_c5_init: Chain[J10] test patten OK temp=-1
driver-btm-c5.c:12784:bitmain_c5_init: Chain[J11] has backup chain_voltage=870
driver-btm-c5.c:12794:bitmain_c5_init: Detect: use voltage limit rules on single board!
driver-btm-c5.c:12800:bitmain_c5_init: Detect: T9+ use voltage level=1
driver-btm-c5.c:12808:bitmain_c5_init: Chain[J11] test patten OK temp=-1
driver-btm-c5.c:12784:bitmain_c5_init: Chain[J12] has backup chain_voltage=870
driver-btm-c5.c:12794:bitmain_c5_init: Detect: use voltage limit rules on single board!
driver-btm-c5.c:12800:bitmain_c5_init: Detect: T9+ use voltage level=1
driver-btm-c5.c:12808:bitmain_c5_init: Chain[J12] test patten OK temp=-1
driver-btm-c5.c:12784:bitmain_c5_init: Chain[J13] has backup chain_voltage=870
driver-btm-c5.c:12794:bitmain_c5_init: Detect: use voltage limit rules on single board!
driver-btm-c5.c:12800:bitmain_c5_init: Detect: T9+ use voltage level=1
driver-btm-c5.c:12808:bitmain_c5_init: Chain[J13] test patten OK temp=-1
driver-btm-c5.c:12784:bitmain_c5_init: Chain[J14] has backup chain_voltage=870
driver-btm-c5.c:12794:bitmain_c5_init: Detect: use voltage limit rules on single board!
driver-btm-c5.c:12800:bitmain_c5_init: Detect: T9+ use voltage level=1
driver-btm-c5.c:12808:bitmain_c5_init: Chain[J14] test patten OK temp=-1
driver-btm-c5.c:12195:init_exist_chain_table: total_exist_chain_num = 9
driver-btm-c5.c:13239:bitmain_c5_init: Chain[J2] will use voltage=890 [7] to open core
driver-btm-c5.c:2168:set_Voltage_S9_plus_plus_BM1387_54: set voltage 7 seccessful
driver-btm-c5.c:13239:bitmain_c5_init: Chain[J3] will use voltage=890 [7] to open core
driver-btm-c5.c:2168:set_Voltage_S9_plus_plus_BM1387_54: set voltage 7 seccessful
driver-btm-c5.c:13239:bitmain_c5_init: Chain[J4] will use voltage=890 [7] to open core
driver-btm-c5.c:2168:set_Voltage_S9_plus_plus_BM1387_54: set voltage 7 seccessful
driver-btm-c5.c:13239:bitmain_c5_init: Chain[J9] will use voltage=890 [7] to open core
driver-btm-c5.c:13239:bitmain_c5_init: Chain[J10] will use voltage=890 [7] to open core
driver-btm-c5.c:13239:bitmain_c5_init: Chain[J11] will use voltage=890 [7] to open core
driver-btm-c5.c:13239:bitmain_c5_init: Chain[J12] will use voltage=890 [7] to open core
driver-btm-c5.c:13239:bitmain_c5_init: Chain[J13] will use voltage=890 [7] to open core
driver-btm-c5.c:13239:bitmain_c5_init: Chain[J14] will use voltage=890 [7] to open core
driver-btm-c5.c:13303:bitmain_c5_init: Chain[J2] orignal chain_voltage_pic=7 value=890
driver-btm-c5.c:13320:bitmain_c5_init: Chain[J2] will use backup chain_voltage_pic=870 [11]
driver-btm-c5.c:13330:bitmain_c5_init: Chain[J2] get working chain_voltage_pic=11
driver-btm-c5.c:13303:bitmain_c5_init: Chain[J3] orignal chain_voltage_pic=7 value=890
driver-btm-c5.c:13320:bitmain_c5_init: Chain[J3] will use backup chain_voltage_pic=870 [11]
driver-btm-c5.c:13330:bitmain_c5_init: Chain[J3] get working chain_voltage_pic=11
driver-btm-c5.c:13303:bitmain_c5_init: Chain[J4] orignal chain_voltage_pic=7 value=890
driver-btm-c5.c:13320:bitmain_c5_init: Chain[J4] will use backup chain_voltage_pic=870 [11]
driver-btm-c5.c:13330:bitmain_c5_init: Chain[J4] get working chain_voltage_pic=11
driver-btm-c5.c:13303:bitmain_c5_init: Chain[J9] orignal chain_voltage_pic=7 value=890
driver-btm-c5.c:13320:bitmain_c5_init: Chain[J9] will use backup chain_voltage_pic=870 [11]
driver-btm-c5.c:13330:bitmain_c5_init: Chain[J9] get working chain_voltage_pic=11
driver-btm-c5.c:13303:bitmain_c5_init: Chain[J10] orignal chain_voltage_pic=7 value=890
driver-btm-c5.c:13320:bitmain_c5_init: Chain[J10] will use backup chain_voltage_pic=870 [11]
driver-btm-c5.c:13330:bitmain_c5_init: Chain[J10] get working chain_voltage_pic=11
driver-btm-c5.c:13303:bitmain_c5_init: Chain[J11] orignal chain_voltage_pic=7 value=890
driver-btm-c5.c:13320:bitmain_c5_init: Chain[J11] will use backup chain_voltage_pic=870 [11]
driver-btm-c5.c:13330:bitmain_c5_init: Chain[J11] get working chain_voltage_pic=11
driver-btm-c5.c:13303:bitmain_c5_init: Chain[J12] orignal chain_voltage_pic=7 value=890
driver-btm-c5.c:13320:bitmain_c5_init: Chain[J12] will use backup chain_voltage_pic=870 [11]
driver-btm-c5.c:13330:bitmain_c5_init: Chain[J12] get working chain_voltage_pic=11
driver-btm-c5.c:13303:bitmain_c5_init: Chain[J13] orignal chain_voltage_pic=7 value=890
driver-btm-c5.c:13320:bitmain_c5_init: Chain[J13] will use backup chain_voltage_pic=870 [11]
driver-btm-c5.c:13330:bitmain_c5_init: Chain[J13] get working chain_voltage_pic=11
driver-btm-c5.c:13303:bitmain_c5_init: Chain[J14] orignal chain_voltage_pic=7 value=890
driver-btm-c5.c:13320:bitmain_c5_init: Chain[J14] will use backup chain_voltage_pic=870 [11]
driver-btm-c5.c:13330:bitmain_c5_init: Chain[J14] get working chain_voltage_pic=11
driver-btm-c5.c:11821:T9_18_getASICnum: T9+ try get asic num for the 1 time
driver-btm-c5.c:9775:pic_heart_beat_func: chain[3] heart beat fail 1 times.
driver-btm-c5.c:11832:T9_18_getASICnum: Chain[J2] has 18 asic
driver-btm-c5.c:11832:T9_18_getASICnum: Chain[J3] has 18 asic
driver-btm-c5.c:11832:T9_18_getASICnum: Chain[J4] has 0 asic
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]!
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]!
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]!
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]!
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]!
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]!
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]!
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]!
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]!
driver-btm-c5.c:9775:pic_heart_beat_func: chain[3] heart beat fail 2 times.
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]!
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]!
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]!
driver-btm-c5.c:11821:T9_18_getASICnum: T9+ try get asic num for the 2 time
driver-btm-c5.c:9775:pic_heart_beat_func: chain[3] heart beat fail 3 times.
driver-btm-c5.c:11832:T9_18_getASICnum: Chain[J2] has 18 asic
driver-btm-c5.c:11832:T9_18_getASICnum: Chain[J3] has 18 asic
driver-btm-c5.c:11832:T9_18_getASICnum: Chain[J4] has 0 asic
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]!
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]!
dsPIC33EP16GS202.c:214:dsPIC33EP16GS202_enable_pic_dc_dc: dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]!

Screenshots are in this link: https://imgur.com/a/qzYZZTj

I ran the network diagnostics as usual.

[mikeywith]

The results are pretty different, which means you were likely using an invalid worker/URL, however, you now have a bigger problem than just a trailing space or bad pool connection.

Code:

driver-btm-c5.c:11832:T9_18_getASICnum: Chain[J2] has 18 asic
driver-btm-c5.c:11832:T9_18_getASICnum: Chain[J3] has 18 asic
driver-btm-c5.c:11832:T9_18_getASICnum: Chain[J4] has 0 asic

If I recall correctly the T9+ has 54 Asic on each dashboard, the exact number doesn't matter as I am 100% sure it's way more than 18, which means you have 3 faulty hash boards, and fixing them would cost more than what miner is actually worth.

Having said that, this could be a PSU related issue, try to unplug 2 hash boards and keep only 1, perform this test 3 times on each chain, I would also Sdcard the miner and install a custom firmware like Braiins or Vnish, sometimes a custom firmware that uses a different frequency and voltage can get the hash boards to work.

[HobbyMinor]

If I recall correctly the T9+ has 54 Asic on each dashboard, the exact number doesn't matter as I am 100% sure it's way more than 18, which means you have 3 faulty hash boards, and fixing them would cost more than what miner is actually worth.

Having said that, this could be a PSU related issue, try to unplug 2 hash boards and keep only 1, perform this test 3 times on each chain, I would also Sdcard the miner and install a custom firmware like Braiins or Vnish, sometimes a custom firmware that uses a different frequency and voltage can get the hash boards to work.

Thanks mikeywith, I was afraid that would be the issue. You are correct in that each chipboard should have 54 ASICs each.

I have a meeting with the seller's technician so I'll report back here the results for the benefit of the rest of the forum. This is the last time I buy a used miner, haha. On the other hand, how did you'll get so proficient at debugging these embedded devices? The level of detail and amount of information to parse through in the debug logs is quite mindboggling. I'm a software engineer by trade and it's already complex enough, so I can't imagine how non-technical folks begin to fix these sort of issues.

[mikeywith]

I have a meeting with the seller's technician so I'll report back here the results for the benefit of the rest of the forum.

I can go into detail on what needs fixing and how to troubleshoot the chips even further, but I have done that so many times in the past and it's all available on the forum, also this gear is so old that it isn't really worth fixing IMO, but it would be a great start for you to get things going.

This is the last time I buy a used miner...

I had a lot of brand new gears that arrived DOA, they didn't work out of the box, this isn't used vs new, it simply is Bitmain.

On the other hand, how did you'll get so proficient at debugging these embedded devices?

I wouldn't call myself a professional and I can't speak for others, but I have personally had a truckload of bad miners that needed fixing and troubleshooting, sending the gears back to Bitmain was not an option so every gear I bought (either to mine with or resell) I had to fix it or send it to the garbage, so the need for learning was very strong.

Also I would say at least 80% of the content related to mining gears comes from this very forum, we have a good number of great contributors whom I learned a lot from, I am also very active across all different mining groups from FB to Telegram and have many friends who own a lot of mining gears, mining is LIFE for me.

With that being said, rest assured that troubleshooting mining gears require no skills, you just need to go through a ton of issue and these issues kind of repeat themselves every step of the way, one last thing worth mentioning is that Bitmain gears are "crazy", you might turn on the miner tomorrow and it hashes at full speed showing all asics as if there was never a problem.  

Good luck and please keep us updated.

[HobbyMinor]

Hey all,

Sorry to disappoint anyone looking for a conclusion, but I've decided to just return it to them for a refund. I'm rather reluctant to go out and buy some microSD cards just to flash around the firmware or debug deeper due to time constraints.

The meeting with their technician never occurred since they kept on rescheduling to a point it was beyond the refund date of the miner. Interestingly, the seller indicates that the item is refurbished and was "fully tested as working" before shipping out. I'm going to hazard a guess that something was damaged during shipping, although there doesn't appear to be anything loose when I shake the machines.

Thanks for the help, everyone.

[mikeywith]

It's very unlikely that one of the chips or heatsinks will lose contact to the hash board just from shipping, if you don't see obvious physical damage caused by mishandling of the package then the seller has probably sent you a broken unit, it might have not been done intentionally because testing refurbished gears isn't simple, you can solder the chip, glue the heatsink, test it for a few minutes and it works perfectly, send it do the client and it longer works as it should, obviously if they ran the miner much longer before sending it out it would have had the same issue you have now.

With that being said, T9+ is a very old gear, despite coming from the S9 era it isn't as robust and it gets way too hot, it's overclocked by default and most importantly it isn't a gear you want to own today.

[HobbyMinor]

Hi mikeywith,

I really appreciate the responses from you as your posts have been very informative into this debugging process.

I've actually decided against returning the equipment and chose to take this up as a challenge to either fix it or at least figure out what's wrong. While it is likely I won't be mining BTC in the future due to the costs involved, I'll use this as an opportunity to learn more about electronics and embedded systems. I'll start tinkering around by following your suggestion by testing each hashboard individually first, and then I'll update back on this post.

Regards