Bitmain S17+ Problem

[keksik]

Hello,

i have Bitmain Antminer S17+ and I am having problem with the hashboard now. it find some chips, then disable the chain and only chain 2 is working (using hiveon asic fw)
Would be someone kind and advice me what to do, before i must check physical chips on hashboard (as I dont have technical equipment for that, heat pistol, volt meter, etc)
here is log

Code:

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 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: Reserved 16 MiB at 0x0e000000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 61440
[    0.000000] free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
[    0.000000]   Normal zone: 480 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 61440 pages, LIFO batch:15
[    0.000000] percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
[    0.000000] pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 60960
[    0.000000] Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
[    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Memory: 193872K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 35504K reserved, 16384K cma-reserved, 0K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xcf800000 - 0xff800000   ( 768 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xcf000000   ( 240 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc090c424   (9234 kB)
[    0.000000]       .init : 0xc0a00000 - 0xc0b00000   (1024 kB)
[    0.000000]       .data : 0xc0b00000 - 0xc0b39fe0   ( 232 kB)
[    0.000000]        .bss : 0xc0b39fe0 - 0xc0b71c28   ( 224 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] 	Build-time adjustment of leaf fanout to 32.
[    0.000000] 	RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] efuse mapped to cf800000
[    0.000000] ps7-slcr mapped to cf802000
[    0.000000] L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
[    0.000000] L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
[    0.000000] L2C-310 erratum 769419 enabled
[    0.000000] L2C-310 enabling early BRESP for Cortex-A9
[    0.000000] L2C-310 full line of zeros enabled for Cortex-A9
[    0.000000] L2C-310 ID prefetch enabled, offset 1 lines
[    0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled
[    0.000000] L2C-310 cache controller enabled, 8 ways, 512 kB
[    0.000000] L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
[    0.000000] zynq_clock_init: clkc starts at cf802100
[    0.000000] Zynq clock init
[    0.000011] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
[    0.000030] clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
[    0.000054] Switching to timer-based delay loop, resolution 3ns
[    0.000293] clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
[    0.000319] ps7-ttc #0 at cf80a000, irq=18
[    0.000554] Console: colour dummy device 80x30
[    0.000570] Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
[    0.000584] pid_max: default: 32768 minimum: 301
[    0.000712] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.000722] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.001328] CPU: Testing write buffer coherency: ok
[    0.001530] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.001583] Setting up static identity map for 0x100000 - 0x100058
[    0.100279] CPU1: failed to boot: -1
[    0.100309] Brought up 1 CPUs
[    0.100318] SMP: Total of 1 processors activated (666.66 BogoMIPS).
[    0.100324] CPU: All CPU(s) started in SVC mode.
[    0.101115] devtmpfs: initialized
[    0.103197] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.103631] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.104580] pinctrl core: initialized pinctrl subsystem
[    0.105689] NET: Registered protocol family 16
[    0.107444] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.150232] cpuidle: using governor menu
[    0.159126] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.159136] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.159283] zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
[    0.220810] vgaarb: loaded
[    0.221160] SCSI subsystem initialized
[    0.221440] usbcore: registered new interface driver usbfs
[    0.221509] usbcore: registered new interface driver hub
[    0.221943] usbcore: registered new device driver usb
[    0.222487] media: Linux media interface: v0.10
[    0.222601] Linux video capture interface: v2.00
[    0.222759] pps_core: LinuxPPS API ver. 1 registered
[    0.222767] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.222850] PTP clock support registered
[    0.223029] EDAC MC: Ver: 3.0.0
[    0.230624] Advanced Linux Sound Architecture Driver Initialized.
[    0.241223] clocksource: Switched to clocksource arm_global_timer
[    0.259551] NET: Registered protocol family 2
[    0.260553] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[    0.260589] TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
[    0.260634] TCP: Hash tables configured (established 2048 bind 2048)
[    0.260683] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.260710] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.260916] NET: Registered protocol family 1
[    0.271594] RPC: Registered named UNIX socket transport module.
[    0.271602] RPC: Registered udp transport module.
[    0.271608] RPC: Registered tcp transport module.
[    0.271613] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.271636] PCI: CLS 0 bytes, default 64
[    0.271857] Trying to unpack rootfs image as initramfs...
[    0.272448] rootfs image is not initramfs (no cpio magic); looks like an initrd
[    0.368042] Freeing initrd memory: 22464K (cc511000 - cdb01000)
[    0.368388] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[    0.370189] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.381981] workingset: timestamp_bits=28 max_order=16 bucket_order=0
[    0.392825] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    0.393953] io scheduler noop registered
[    0.393970] io scheduler deadline registered
[    0.393999] io scheduler cfq registered (default)
[    0.395675] dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
[    0.395689] dma-pl330 f8003000.ps7-dma: 	DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[    0.396856] e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
[    0.900915] console [ttyPS0] enabled
[    0.903809] xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[    0.909981] [drm] Initialized drm 1.1.0 20060810
[    1.087612] brd: module loaded
[    1.176549] loop: module loaded
[    1.180498] CAN device driver interface
[    1.186407] gpiod_set_value: invalid GPIO
[    1.190186] libphy: MACB_mii_bus: probed
[    1.271289] macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
[    1.279733] Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
[    1.290031] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[    1.294574] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[    1.300452] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.306069] ehci-pci: EHCI PCI platform driver
[    1.309377] usbcore: registered new interface driver usb-storage
[    1.315929] mousedev: PS/2 mouse device common for all mice
[    1.331304] i2c /dev entries driver
[    1.336386] Xilinx Zynq CpuIdle Driver started
[    1.340727] sdhci: Secure Digital Host Controller Interface driver
[    1.345629] sdhci: Copyright(c) Pierre Ossman
[    1.348606] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.392360] mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
[    1.399267] ledtrig-cpu: registered to indicate activity on CPUs
[    1.404546] usbcore: registered new interface driver usbhid
[    1.408726] usbhid: USB HID core driver
[    1.412620] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[    1.417581] nand: Micron MT29F2G08ABAGAWP
[    1.420275] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
[    1.426914] nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
[    1.437072] Bad block table found at page 131008, version 0x01
[    1.442029] Bad block table found at page 130944, version 0x01
[    1.446800] 6 ofpart partitions found on MTD device pl35x-nand
[    1.451319] Creating 6 MTD partitions on "pl35x-nand":
[    1.455068] 0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
[    1.471774] 0x000002800000-0x000004800000 : "ramfs"
[    1.486774] 0x000004800000-0x000005000000 : "configs"
[    1.501864] 0x000005000000-0x000006000000 : "reserve"
[    1.516970] 0x000006000000-0x000008000000 : "ramfs-bak"
[    1.532384] 0x000008000000-0x000010000000 : "reserve1"
[    1.551389] NET: Registered protocol family 10
[    1.565997] sit: IPv6 over IPv4 tunneling driver
[    1.570216] NET: Registered protocol family 17
[    1.573521] can: controller area network core (rev 20120528 abi 9)
[    1.578359] NET: Registered protocol family 29
[    1.581495] can: raw protocol (rev 20120528)
[    1.584395] can: broadcast manager protocol (rev 20120528 t)
[    1.588742] can: netlink gateway (rev 20130117) max_hops=1
[    1.593210] zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
[    1.599036] zynq_pm_late_init: Unable to map DDRC IO memory.
[    1.603600] Registering SWP/SWPB emulation handler
[    1.608925] hctosys: unable to open rtc device (rtc0)
[    1.613182] ALSA device list:
[    1.614755]   No soundcards found.
[    1.617214] RAMDISK: gzip image found at block 0
[    4.183281] EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
[    4.200756] EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
[    4.206617] VFS: Mounted root (ext4 filesystem) on device 1:0.
[    4.211226] devtmpfs: mounted
[    4.214000] Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
[    4.398523] EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
[    4.425390] random: dd urandom read with 0 bits of entropy available
[    4.473709] ubi0: attaching mtd2
[    4.506219] ubi0: scanning is finished
[    4.515229] ubi0: attached mtd2 (name "configs", size 8 MiB)
[    4.519506] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    4.525255] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    4.530650] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
[    4.536407] ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
[    4.540936] ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
[    4.546878] ubi0: max/mean erase counter: 17/7, WL threshold: 4096, image sequence number: 237714726
[    4.554690] ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
[    4.562520] ubi0: background thread "ubi_bgt0d" started, PID 709
[    4.580339] UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 712
[    4.613332] UBIFS (ubi0:0): recovery needed
[    4.695242] UBIFS (ubi0:0): recovery completed
[    4.698298] UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
[    4.704507] UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    4.713073] UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
[    4.721745] UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
[    4.726683] UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID FF09433B-E002-4C29-97EC-6220DDC4BB36, small LPT model
[    4.759758] ubi1: attaching mtd5
[    5.248389] ubi1: scanning is finished
[    5.258690] ubi1: attached mtd5 (name "reserve1", size 128 MiB)
[    5.263392] ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    5.268875] ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    5.274405] ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
[    5.279985] ubi1: good PEBs: 1020, bad PEBs: 4, corrupted PEBs: 0
[    5.284797] ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
[    5.290664] ubi1: max/mean erase counter: 3723/736, WL threshold: 4096, image sequence number: 3265111179
[    5.298943] ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
[    5.306938] ubi1: background thread "ubi_bgt1d" started, PID 721
[    5.321227] UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 724
[    5.357973] UBIFS (ubi1:0): recovery needed
[    5.475411] UBIFS (ubi1:0): recovery completed
[    5.478474] UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
[    5.484746] UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    5.493333] UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
[    5.502614] UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
[    5.507901] UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 1AF6F1E1-61F0-462C-AE44-C7D9596CF7E2, small LPT model
[    6.239438] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    6.268417] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    6.273123] macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
[    6.273134] macb e000b000.ethernet eth0: link up (100/Full)
[    6.284419] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   19.738347] In axi fpga driver!
[   19.747888] request_mem_region OK!
[   19.757112] AXI fpga dev virtual address is 0xcfb38000
[   19.768053] *base_vir_addr = 0xb023
[   19.810912] In fpga mem driver!
[   19.816717] request_mem_region OK!
[   19.820239] fpga mem virtual address is 0xd2000000
[  243.450382] random: nonblocking pool is initialized
2022-05-14 14:31:12 Read tune config: tune_profile=4, tune_status=1, tune_frequency=500, tune_voltage=1880, tune_freq_step=5, tune_volt_step=20, tune_max_frequency=525, tune_power=2650, tune_bad_domains_threshold=1, tune_max_voltage=1900, tune_freq_yellow_step=10, tune_max_restarts=10, tune_restarts=2, voltage_increase=20, voltage_pre_heat_delay=30, tune_decrease_voltage_mode=1, tune_uptime=240, tune_chain_statuses=4, tune_bad_freq_step=25
2022-05-14 14:31:12 driver/driver-btm-api.c:278:init_freq_mode: This is scan-user version
2022-05-14 14:31:12 driver/driver-btm-api.c:1990:bitmain_soc_init: opt_multi_version     = 1
2022-05-14 14:31:12 driver/driver-btm-api.c:1991:bitmain_soc_init: opt_bitmain_ab        = 1
2022-05-14 14:31:12 driver/driver-btm-api.c:1992:bitmain_soc_init: opt_bitmain_work_mode = 0
2022-05-14 14:31:12 driver/driver-btm-api.c:1993:bitmain_soc_init: Miner compile time: Fri Apr 3 15:30:33 UTC 2020 type: Antminer S17+ Hiveon
2022-05-14 14:31:12 driver/driver-btm-api.c:1995:bitmain_soc_init: commit version: 3f36039 2020-04-01 16:04:28, build by: user 2020-04-01 19:37:05
2022-05-14 14:31:12 driver/driver-btm-api.c:1628:show_sn: 803c25064e10481c Zv
2022-05-14 14:31:12 driver/driver-btm-api.c:1636:show_sn: no SN got, please write SN to /nvdata/sn
2022-05-14 14:31:12 driver/fan.c:211:front_fan_power_on: Note: front fan is power on!
2022-05-14 14:31:12 driver/fan.c:217:rear_fan_power_on: Note: rear fan is power on!
2022-05-14 14:31:12 driver/driver-btm-api.c:1690:miner_device_init: Detect 256MB control board of XILINX
2022-05-14 14:31:12 driver/driver-btm-api.c:1664:init_fan_parameter: fan_eft : 0  fan_pwm : 100
2022-05-14 14:31:18 driver/driver-btm-api.c:1315:init_miner_version: miner ID : 803c25064e10481c
2022-05-14 14:31:18 driver/driver-btm-api.c:1320:init_miner_version: FPGA Version = 0xB023
2022-05-14 14:31:23 driver/thread.c:1671:create_read_nonce_reg_thread: create thread
2022-05-14 14:31:23 driver/driver-btm-api.c:1371:bitmain_board_init: product_id[0] = 0
2022-05-14 14:31:23 driver/driver-btm-api.c:1371:bitmain_board_init: product_id[1] = 0
2022-05-14 14:31:23 driver/driver-btm-api.c:1371:bitmain_board_init: product_id[2] = 0
2022-05-14 14:31:23 driver/driver-btm-api.c:1392:bitmain_board_init: project:0
2022-05-14 14:31:23 driver/driver-btm-api.c:1450:bitmain_board_init: Project type: Antminer S17+
2022-05-14 14:31:23 driver/driver-btm-api.c:1017:dump_pcb_bom_version: Chain [0] PCB Version: 0x0100
2022-05-14 14:31:23 driver/driver-btm-api.c:1018:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2022-05-14 14:31:23 driver/driver-btm-api.c:1017:dump_pcb_bom_version: Chain [1] PCB Version: 0x0100
2022-05-14 14:31:23 driver/driver-btm-api.c:1018:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2022-05-14 14:31:23 driver/driver-btm-api.c:1017:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2022-05-14 14:31:23 driver/driver-btm-api.c:1018:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2022-05-14 14:31:25 driver/driver-btm-api.c:1489:bitmain_board_init: Fan check passed.
2022-05-14 14:31:26 driver/board.c:31:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2022-05-14 14:31:30 driver/board.c:34:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2022-05-14 14:31:31 driver/board.c:31:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2022-05-14 14:31:35 driver/board.c:34:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2022-05-14 14:31:35 driver/board.c:31:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2022-05-14 14:31:40 driver/board.c:34:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2022-05-14 14:31:40 driver/thread.c:1666:create_pic_heart_beat_thread: create thread
2022-05-14 14:31:40 driver/power_api.c:191:power_init: power init ... 
2022-05-14 14:31:40 driver/power_api.c:265:power_init: highest_voltage    = 21.000000
2022-05-14 14:31:40 driver/power_api.c:266:power_init: working_voltage    = 19.500000
2022-05-14 14:31:40 driver/power_api.c:267:power_init: higher_voltage     = 20.400000
2022-05-14 14:31:40 driver/driver-btm-api.c:1500:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2022-05-14 14:31:40 driver/power_api.c:177:power_off: init gpio907
2022-05-14 14:32:12 driver/power_api.c:448:set_to_highest_voltage: setting to voltage: 21.00 ...
2022-05-14 14:32:14 driver/power_api.c:571:check_voltage_multi: retry time: 0
2022-05-14 14:32:15 driver/power_api.c:539:_get_avg_voltage: average voltage = 21.105755 
2022-05-14 14:32:15 driver/power_api.c:557:check_voltage: target_vol = 21.00, actural_vol = 21.11, check voltage passed.
2022-05-14 14:32:15 driver/uart.c:49:set_baud: set UART baud to 115200
2022-05-14 14:32:21 driver/driver-btm-api.c:1173:check_asic_number_with_power_on: Chain[0]: find 20 asic, times 0
2022-05-14 14:32:27 driver/driver-btm-api.c:1173:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 1
2022-05-14 14:32:32 driver/driver-btm-api.c:1173:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 2
2022-05-14 14:32:32 driver/driver-btm-api.c:1187:check_asic_number_with_power_on: Chain 0 only find 0 asic, will power off hash board 0
2022-05-14 14:32:38 driver/driver-btm-api.c:1173:check_asic_number_with_power_on: Chain[1]: find 28 asic, times 0
2022-05-14 14:32:44 driver/driver-btm-api.c:1173:check_asic_number_with_power_on: Chain[1]: find 28 asic, times 1
2022-05-14 14:32:49 driver/driver-btm-api.c:1173:check_asic_number_with_power_on: Chain[1]: find 28 asic, times 2
2022-05-14 14:32:49 driver/driver-btm-api.c:1187:check_asic_number_with_power_on: Chain 1 only find 28 asic, will power off hash board 1
2022-05-14 14:32:55 driver/driver-btm-api.c:1173:check_asic_number_with_power_on: Chain[2]: find 65 asic, times 0
2022-05-14 14:32:58 driver/driver-hash-chip.c:100:set_uart_relay: set uart relay to 0x330003
2022-05-14 14:32:58 driver/driver-btm-api.c:1000:set_order_clock: chain[2]: set order clock, stragegy 3
2022-05-14 14:32:58 driver/driver-hash-chip.c:292:set_clock_delay_control: core_data = 0x34
2022-05-14 14:32:58 voltage[2] = 1900
2022-05-14 14:32:58 Highest voltage is 21.00
2022-05-14 14:32:58 driver/power_api.c:279:set_working_voltage: working_voltage = 19.200000
2022-05-14 14:33:00 driver/temperature.c:321:calibrate_temp_sensor_all_chains: chain 2 temp sensor NCT218, offset -8
2022-05-14 14:33:00 driver/uart.c:49:set_baud: set UART baud to 12000000
2022-05-14 14:33:00 driver/driver-btm-api.c:662:check_bringup_temp: Bring up temperature is 23
2022-05-14 14:33:00 driver/thread.c:1686:create_check_miner_status_thread: create thread
2022-05-14 14:33:00 driver/thread.c:1676:create_set_miner_status_thread: create thread
2022-05-14 14:33:00 driver/thread.c:1701:create_auto_tune_thread: create thread
2022-05-14 14:33:00 driver/thread.c:1706:create_read_real_voltage_thread: create thread
2022-05-14 14:33:00 driver/frequency.c:759:inc_freq_with_fixed_vco: chain = 255, freq = 475, is_higher_voltage = true
2022-05-14 14:33:17 driver/driver-btm-api.c:983:set_timeout: freq = 475, percent = 90, hcn = 44236, timeout = 93
2022-05-14 14:33:17 driver/power_api.c:773:set_to_working_voltage_by_steps: Set to voltage 19.20, step by step.
2022-05-14 14:33:21 driver/power_api.c:571:check_voltage_multi: retry time: 0
2022-05-14 14:33:21 driver/power_api.c:539:_get_avg_voltage: average voltage = 19.291560 
2022-05-14 14:33:21 driver/power_api.c:557:check_voltage: target_vol = 19.20, actural_vol = 19.29, check voltage passed.
2022-05-14 14:33:22 driver/power_api.c:497:get_average_voltage: average_voltage = 19.267263
2022-05-14 14:33:22 driver/thread.c:1661:create_temperature_monitor_thread: create thread
2022-05-14 14:33:22 driver/thread.c:1681:create_check_system_status_thread: create thread
2022-05-14 14:33:22 driver/thread.c:1693:create_read_hash_rate_thread: create thread
2022-05-14 14:33:23 driver/driver-btm-api.c:2219:bitmain_soc_init: Init done!
2022-05-14 14:33:23 driver/driver-btm-api.c:204:set_miner_status: STATUS_INIT
2022-05-14 14:33:23 driver/driver-btm-api.c:204:set_miner_status: STATUS_OKAY
2022-05-14 14:33:28 driver/driver-btm-api.c:2461:dhash_chip_send_job: Version num

[BitMaxz]

How about multimeter? Because without tools you can't able to know if that chip near ASIC #20 is shorted or dead.

Check this troubleshooting guide from Zeusbtc below

- https://www.zeusbtc.com/articles/information/182-antminer-s17-manual-download
- https://www.zeusbtc.com/manuals/Antminer-S17-plus-Hash-Board-Repair-Guide.asp

Why not check that hashboard physically and maybe one of the heatsinks is loose.

[keksik]

How about multimeter? Because without tools you can't able to know if that chip near ASIC #20 is shorted or dead.

Check this troubleshooting guide from Zeusbtc below

- https://www.zeusbtc.com/articles/information/182-antminer-s17-manual-download
- https://www.zeusbtc.com/manuals/Antminer-S17-plus-Hash-Board-Repair-Guide.asp

Why not check that hashboard physically and maybe one of the heatsinks is loose.

Hello,

Unfortunately indont have multimeter but can look around for one. If it find 28asics for example it means around chip 28 could be bad chip? yes i inspected hashboards physically and cleaned everting, was not dirty much but better than nothing. also one of the heatsing fall off. so how to put it back? may i use Arctic Silver 7g Premium Silver Thermal Cooling Adhesive Set (ASTA-7G) (which i used a year ago for S9) or only heatgun and basic solder?
second question, can u help me identify the chains physical position? I have J1-4J(using only J1,2,3) data cables connected to hasboard, but in system chain 0,1,2 are how related to J?
J1 is chain0, J2 is Chain1, J3 is chain2?

Is ok, if I pull only data cable from hashboard and let it still be connected to psu? ill just remove the data cable to test it with one chain at the time.

Is better to use for testing purpose original FW instead of hiveon FW i am currently running(underclock settings) so it will provide more V to the hashbaord for better stability?

thank you in advance, appreciate


EDIT: I cleaned hashbaord and also tested data cables. switched the good one hashboard in different position and it worked in every position, so data cables are ok and seems PSU as well, correct?
so are the two remaining hashbaord dead? i can only try switching to oficial FW to test it with stock settings(more power for hashboards) if it will work, but if not, hashbaords are dead, correct?

Per bitmain official site, repairing faulty hashboard should cost 100USD + shipping, see this page:
https://support.bitmain.com/hc/en-us/articles/360014534694-How-much-does-a-repair-cost-

[BitMaxz]

Yes if it detects only 28 ASICs then there is a big possibility that the chip is broken or near parts like shorted capacitors.
Regarding thermal adhesive for a loose heatsink, Artic silver is fine.

Chain [ 0] and [1] are broken based on your kernel logs running them one by one if it only detects a few Asic chips then it's a hardware issue.

I have already given you a guide above there are 13 voltage domains and each line has 5 ASIC chips if one chip is broken of any of these domain samples like in 8 one of the chips under that is broken and the rest 9, 10, 11, 12, and 13 won't be able to detect then the hashboard will automatically shut down because it didn't detect the required amount of ASIC. You need to replace it in order to fix the issue sometimes capacitors near that ASIC are shorted removing it is fine.

About the PSU if you already test them one by one but the result is the same then it's not the PSU the two hashboard is totally broken and it needs to repair.

Even if you change it to official firmware I believe the result will be the same. Unless there is some modified firmware out there that can able to ignore missing chips and only the remaining chips will run. Old units like Antminer s9 can able to ignore those bad ASIC chips and run like normal with lesser hashrate.

[keksik]

I have glued the heatsink which fell off, lets see if it will work.

also meantime tested one s17+ with
Chain0 65asics
Chain1 28asics - disabled hashbaord
Chain2 0asics - disabled hashbaord

then original FW throw this:

Code:

2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:09 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:09 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:09 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:09 chain = 0, mode = 1, load_done = true.
2022-05-16 18:44:09 Voltage read fail. Will exit.
2022-05-16 18:44:09 driver-btm-api.c:222:set_miner_status: ERROR_SOC_INIT
2022-05-16 18:44:09 driver-btm-api.c:156:stop_mining: stop mining: soc init failed!
2022-05-16 18:44:09 thread.c:1403:cancel_read_nonce_reg_thread: cancel thread
2022-05-16 18:44:09 driver-btm-api.c:141:killall_hashboard: ****power off hashboard****

and u were correct,results is same...i will send it to bitmain repair center. also do you know what i need to repair it at home?

P.S. really appreciate your effort here, i have seen you responded to many threads man, thank you for all ppl here.

[BitMaxz]

Did you buy this unit directly from Bitmain?

It seems few of your hashboard have EEPROM issues that causes "ERROR_SOC_INIT"
If you bought this unit 2nd those 2 hashboard are replacements and they only flash it with modified firmware to bypass that issue. Usually, you need a code editor to be able to fix this issue.

However, since detected chips on two of your hashboard are abnormal you must hire a technician that could repair ASIC machines. Bitmain repair center is nice but I suggest you check this https://www.zeusbtc.com/ASIC-Miner-Repair/

Look for a repair center near your area because sending it back to Bitmain will cost you more than hiring ASIC tech near your location.

[keksik]

Did you buy this unit directly from Bitmain?

It seems few of your hashboard have EEPROM issues that causes "ERROR_SOC_INIT"
If you bought this unit 2nd those 2 hashboard are replacements and they only flash it with modified firmware to bypass that issue. Usually, you need a code editor to be able to fix this issue.

However, since detected chips on two of your hashboard are abnormal you must hire a technician that could repair ASIC machines. Bitmain repair center is nice but I suggest you check this https://www.zeusbtc.com/ASIC-Miner-Repair/

Look for a repair center near your area because sending it back to Bitmain will cost you more than hiring ASIC tech near your location.

thank you for your reply again, much appreciate your expert opinion. Yes i bought them from second hand...So it means, when i swaped hashbaords between two machines it caused they dont work now and shows 0 asics?
I have reviewed the repair centers from Zeusbtc in Europe (as I am ehre) and repair cost range from 200-500EUR per one, so I decided I would like to repair them on my own. can you let me know what tools i would need? to repair 5 hashbaord it will cost 1000-1500Eur so i can do it(I repaired my S9 in the past with PICkit and some heatsink replacement, no chip replacement yet, but like to learn) on my own, save, learn something and have tools/knowledge for next repair.

Also i have one additional important question. Today I turn on T17E, showin 3 chains working ok with 51TH with stock FW, i decided to change fw to hiveon via sd card, it is a minute. after update one chain disapeared, so i reverted back to stock via sd card again and now i dont see two chains. same happen to me with those S17+ i am talking above... do you think there could be other problem and not hashbaords? what are your thoughts.

Code:

Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
  Normal zone: 480 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1 
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 195704K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 33672K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xcf800000 - 0xff800000   ( 768 MB)
    lowmem  : 0xc0000000 - 0xcf000000   ( 240 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .text : 0xc0008000 - 0xc090c424   (9234 kB)
      .init : 0xc0a00000 - 0xc0b00000   (1024 kB)
      .data : 0xc0b00000 - 0xc0b39fe0   ( 232 kB)
       .bss : 0xc0b39fe0 - 0xc0b71c28   ( 224 kB)
Preemptible hierarchical RCU implementation.
	Build-time adjustment of leaf fanout to 32.
	RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 20632K (cc6db000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: 	DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAGAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
  No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
random: dd urandom read with 0 bits of entropy available
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 24/8, WL threshold: 4096, image sequence number: 3745532542
ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
ubi0: background thread "ubi_bgt0d" started, PID 708
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 711
UBIFS (ubi0:0): recovery needed
UBIFS (ubi0:0): recovery completed
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID 3E2BC2EA-ECA1-4E91-BF05-322AFDAF11A7, small LPT model
ubi1: attaching mtd5
ubi1: scanning is finished
ubi1: attached mtd5 (name "reserve1", size 128 MiB)
ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi1: good PEBs: 1020, bad PEBs: 4, corrupted PEBs: 0
ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi1: max/mean erase counter: 18741/16682, WL threshold: 4096, image sequence number: 614900815
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): recovery needed
UBIFS (ubi1:0): recovery completed
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 91DF6B3D-1A99-4241-87C7-EB25097110C1, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfb54000
*base_vir_addr = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2022-05-17 13:12:10:thread.c:1555:create_bitmain_soc_init_thread: create thread
2022-05-17 13:12:10:driver-btm-api.c:682:init_freq_mode: This is scan-user version
2022-05-17 13:12:10:driver-btm-api.c:2518:bitmain_soc_init: Miner compile time: Fri Jan  8 22:35:06 CST 2021 type: Antminer T17e
2022-05-17 13:12:10:driver-btm-api.c:2519:bitmain_soc_init: commit version: 37668c9 2021-01-08 18:20:11, build by: jenkins 2021-01-08 22:39:58
2022-05-17 13:12:10:driver-btm-api.c:2520:bitmain_soc_init: opt_multi_version     = 1
2022-05-17 13:12:10:driver-btm-api.c:2521:bitmain_soc_init: opt_bitmain_ab        = 1
2022-05-17 13:12:10:driver-btm-api.c:2522:bitmain_soc_init: mid_auto_gen          = 0
2022-05-17 13:12:10:driver-btm-api.c:2523:bitmain_soc_init: work_mode             = 0
2022-05-17 13:12:10:driver-btm-api.c:2524:bitmain_soc_init: power_feedback_en     = true
2022-05-17 13:12:10:driver-btm-api.c:2067:show_sn: no SN got, please write SN to /config/sn
2022-05-17 13:12:10:driver-btm-api.c:1384:miner_device_init: Detect 256MB control board of XILINX
2022-05-17 13:12:10:driver-btm-api.c:1325:init_fan_parameter: fan_eft : 0  fan_pwm : 0
2022-05-17 13:12:16:driver-btm-api.c:1309:init_miner_version: miner ID : 80546d842b104814
2022-05-17 13:12:16:driver-btm-api.c:1315:init_miner_version: FPGA Version = 0xB023
2022-05-17 13:12:21:auto_adapt.c:100:_get_board_info: chain[0] board bin: 1, chip bin: 1, chip ft: A4V41, chip version: AB
2022-05-17 13:12:21:auto_adapt.c:100:_get_board_info: chain[1] board bin: 1, chip bin: 1, chip ft: A4V41, chip version: AB
2022-05-17 13:12:21:auto_adapt.c:100:_get_board_info: chain[2] board bin: 1, chip bin: 1, chip ft: A4V41, chip version: AB
2022-05-17 13:12:21:auto_adapt.c:273:is_sweep_failed_before: open sweep tag failed
voltage_ref = 1800
2100  2100  2100  2100  2100  2100  
2100  2100  2100  2100  2100  2100  
2100  2100  2100  2100  2100  2100  
2100  2100  2100  2100  2100  2050  
2100  2100  2100  2100  2060  1990  
2060  2050  2040  2030  1990  1920  
1990  1980  1970  1960  1930  1870  
1940  1920  1910  1900  1860  1810  
1940  1920  1910  1900  1860  1810  

2022-05-17 13:12:21:thread.c:1523:create_read_nonce_reg_thread: create thread
2022-05-17 13:12:21:driver-btm-api.c:698:dump_pcb_bom_version: Chain [0] PCB Version: 0x010a
2022-05-17 13:12:21:driver-btm-api.c:699:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100
2022-05-17 13:12:21:driver-btm-api.c:698:dump_pcb_bom_version: Chain [1] PCB Version: 0x010a
2022-05-17 13:12:21:driver-btm-api.c:699:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2022-05-17 13:12:21:driver-btm-api.c:698:dump_pcb_bom_version: Chain [2] PCB Version: 0x010a
2022-05-17 13:12:21:driver-btm-api.c:699:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2022-05-17 13:12:28:driver-btm-api.c:2344:bitmain_board_init: Fan check passed.
2022-05-17 13:12:29:board.c:81:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2022-05-17 13:12:31:board.c:94:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2022-05-17 13:12:32:board.c:81:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2022-05-17 13:12:34:board.c:94:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2022-05-17 13:12:35:board.c:81:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2022-05-17 13:12:37:board.c:94:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2022-05-17 13:12:37:thread.c:1518:create_pic_heart_beat_thread: create thread
2022-05-17 13:12:39:power_api.c:241:power_init: power type version: 0x0042
2022-05-17 13:12:40:power_api.c:259:power_init: Power init:
2022-05-17 13:12:40:power_api.c:260:power_init: current_voltage_raw     = 2136
2022-05-17 13:12:40:power_api.c:261:power_init: highest_voltage_raw     = 2000
2022-05-17 13:12:40:power_api.c:262:power_init: working_voltage_raw     = 1800
2022-05-17 13:12:40:power_api.c:263:power_init: higher_voltage_raw      = 1850
2022-05-17 13:12:40:power_api.c:264:power_init: check_asic_voltage_raw  = 1800
2022-05-17 13:12:40:driver-btm-api.c:2354:bitmain_board_init: Enter 60s sleep to make sure power release finish.
2022-05-17 13:13:42:driver-btm-api.c:1123:check_asic_number_until_volt_balance: THIS is No.1 time boost asic:
2022-05-17 13:13:42:power_api.c:334:modify_check_asic_voltage: check_asic_voltage_raw  = 1800
2022-05-17 13:13:45:power_api.c:298:set_to_check_asic_voltage_by_steps: Set to voltage raw 1800, step by step.
2022-05-17 13:14:06:uart.c:69:set_baud: set UART baud to 115200
chain 0, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x 7777777
2022-05-17 13:14:12:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[0]: find 78 asic, times 0
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x 7777777
2022-05-17 13:14:16:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 0
2022-05-17 13:14:17:board.c:81:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2022-05-17 13:14:19:board.c:94:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2022-05-17 13:14:19:power_api.c:334:modify_check_asic_voltage: check_asic_voltage_raw  = 1900
2022-05-17 13:14:19:power_api.c:298:set_to_check_asic_voltage_by_steps: Set to voltage raw 1900, step by step.
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x 7777777
2022-05-17 13:14:36:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 1
2022-05-17 13:14:37:board.c:81:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2022-05-17 13:14:39:board.c:94:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2022-05-17 13:14:39:power_api.c:334:modify_check_asic_voltage: check_asic_voltage_raw  = 2000
2022-05-17 13:14:39:power_api.c:298:set_to_check_asic_voltage_by_steps: Set to voltage raw 2000, step by step.
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x 7777777
2022-05-17 13:14:57:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 2
2022-05-17 13:14:58:board.c:81:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2022-05-17 13:15:00:board.c:94:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2022-05-17 13:15:00:power_api.c:334:modify_check_asic_voltage: check_asic_voltage_raw  = 2100
2022-05-17 13:15:00:power_api.c:298:set_to_check_asic_voltage_by_steps: Set to voltage raw 2100, step by step.
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x 7777777
2022-05-17 13:15:17:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 3
2022-05-17 13:15:18:board.c:81:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2022-05-17 13:15:21:board.c:94:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2022-05-17 13:15:21:power_api.c:334:modify_check_asic_voltage: check_asic_voltage_raw  = 1800
2022-05-17 13:15:21:power_api.c:298:set_to_check_asic_voltage_by_steps: Set to voltage raw 1800, step by step.
2022-05-17 13:15:41:driver-btm-api.c:1217:check_asic_number: Chain 1 only find 0 asic, will power off hash board 1
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x 7777777
2022-05-17 13:15:46:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 0
2022-05-17 13:15:47:board.c:81:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2022-05-17 13:15:49:board.c:94:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2022-05-17 13:15:49:power_api.c:334:modify_check_asic_voltage: check_asic_voltage_raw  = 1900
2022-05-17 13:15:49:power_api.c:298:set_to_check_asic_voltage_by_steps: Set to voltage raw 1900, step by step.
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x 7777777
2022-05-17 13:16:03:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 1
2022-05-17 13:16:04:board.c:81:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2022-05-17 13:16:06:board.c:94:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2022-05-17 13:16:06:power_api.c:334:modify_check_asic_voltage: check_asic_voltage_raw  = 2000
2022-05-17 13:16:06:power_api.c:298:set_to_check_asic_voltage_by_steps: Set to voltage raw 2000, step by step.
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x 7777777
2022-05-17 13:16:21:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 2
2022-05-17 13:16:22:board.c:81:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2022-05-17 13:16:24:board.c:94:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2022-05-17 13:16:24:power_api.c:334:modify_check_asic_voltage: check_asic_voltage_raw  = 2100
2022-05-17 13:16:24:power_api.c:298:set_to_check_asic_voltage_by_steps: Set to voltage raw 2100, step by step.
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x 7777777
2022-05-17 13:16:38:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 3
2022-05-17 13:16:39:board.c:81:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2022-05-17 13:16:41:board.c:94:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2022-05-17 13:16:41:power_api.c:334:modify_check_asic_voltage: check_asic_voltage_raw  = 1800
2022-05-17 13:16:41:power_api.c:298:set_to_check_asic_voltage_by_steps: Set to voltage raw 1800, step by step.
2022-05-17 13:16:58:driver-btm-api.c:1217:check_asic_number: Chain 2 only find 0 asic, will power off hash board 2
2022-05-17 13:17:00:driver-btm-api.c:1163:check_asic_number_until_volt_balance: PASS: volt balance at No.1 time boost asic.
2022-05-17 13:17:00:power_api.c:364:set_to_highest_voltage_by_steps: Set to voltage raw 2000, step by step.
2022-05-17 13:17:14:driver-hash-chip.c:876:set_uart_relay: set uart relay to 0x330003
2022-05-17 13:17:14:driver-hash-chip.c:1264:set_ldo_ctrl: Set LDO to 0x2000203
2022-05-17 13:17:15:driver-hash-chip.c:737:dump_adc_voltage_v2: get ADC_DATAOUT from chain 0 with 0 regs timeout.
chain 0 domain  0:   d0 0.384,   d1 0.385,   d2 0.385,   d3 0.384,   sum = 1.538086
chain 0 domain  1:   d0 0.393,   d1 0.380,   d2 0.393,   d3 0.332,   sum = 1.498169
chain 0 domain  2:   d0 0.375,   d1 0.375,   d2 0.376,   d3 0.360,   sum = 1.486145
chain 0 domain  3:   d0 0.389,   d1 0.391,   d2 0.386,   d3 0.389,   sum = 1.554688
chain 0 domain  4:   d0 0.368,   d1 0.365,   d2 0.363,   d3 0.360,   sum = 1.455322
chain 0 domain  5:   d0 0.386,   d1 0.376,   d2 0.383,   d3 0.345,   sum = 1.489624
chain 0 domain  6:   d0 0.402,   d1 0.405,   d2 0.406,   d3 0.404,   sum = 1.617126
chain 0 domain  7:   d0 0.398,   d1 0.387,   d2 0.400,   d3 0.395,   sum = 1.579102
chain 0 domain  8:   d0 0.378,   d1 0.380,   d2 0.358,   d3 0.375,   sum = 1.491211
chain 0 domain  9:   d0 0.399,   d1 0.391,   d2 0.393,   d3 0.395,   sum = 1.578430
chain 0 domain 10:   d0 0.392,   d1 0.399,   d2 0.381,   d3 0.391,   sum = 1.562744
chain 0 domain 11:   d0 0.371,   d1 0.362,   d2 0.366,   d3 0.349,   sum = 1.447571
chain 0 domain 12:   d0 0.368,   d1 0.369,   d2 0.364,   d3 0.359,   sum = 1.459961
2022-05-17 13:17:15:driver-hash-chip.c:493:check_adc_voltage: PASS domainn volt check: request 0.800 (index 0, open_core)
2022-05-17 13:17:16:temperature.c:272:calibrate_temp_sensor_one_chain: chain 0 temp sensor NCT218
2022-05-17 13:17:22:driver-btm-api.c:311:check_bringup_temp: Bring up temperature is 23
2022-05-17 13:17:22:uart.c:69:set_baud: set UART baud to 3000000
2022-05-17 13:17:22 voltage[0] = 1800
2022-05-17 13:17:22:power_api.c:272:set_working_voltage_raw: working_voltage_raw = 1800
2022-05-17 13:17:22:thread.c:1538:create_check_miner_status_thread: create thread
2022-05-17 13:17:22:thread.c:1528:create_show_miner_status_thread: create thread
2022-05-17 13:17:22:thread.c:1503:create_temperature_monitor_thread: create thread
2022-05-17 13:17:22:thread.c:1580:create_fan_monitor_thread: create thread
2022-05-17 13:17:22:frequency.c:578:inc_freq_with_fixed_vco: chain = 255, freq = 550, is_higher_voltage = true
2022-05-17 13:17:28:frequency.c:623:inc_freq_with_fixed_vco: get pcb 24 ~ 26, chip_temp 28 ~ 29, now 6.0s, target 29.0
2022-05-17 13:17:29:frequency.c:623:inc_freq_with_fixed_vco: get pcb 23 ~ 26, chip_temp 27 ~ 29, now 7.0s, target 29.2
2022-05-17 13:17:30:frequency.c:623:inc_freq_with_fixed_vco: get pcb 23 ~ 26, chip_temp 27 ~ 29, now 8.0s, target 29.3
2022-05-17 13:17:31:frequency.c:623:inc_freq_with_fixed_vco: get pcb 25 ~ 26, chip_temp 27 ~ 29, now 9.0s, target 29.5
2022-05-17 13:17:32:frequency.c:623:inc_freq_with_fixed_vco: get pcb 23 ~ 26, chip_temp 28 ~ 30, now 10.0s, target 29.7
2022-05-17 13:17:32:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 30 > 29.7 target_temp.
2022-05-17 13:17:38:frequency.c:623:inc_freq_with_fixed_vco: get pcb 24 ~ 27, chip_temp 28 ~ 31, now 16.0s, target 30.7
2022-05-17 13:17:38:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 31 > 30.7 target_temp.
2022-05-17 13:17:44:frequency.c:623:inc_freq_with_fixed_vco: get pcb 26 ~ 27, chip_temp 29 ~ 31, now 22.0s, target 31.7
2022-05-17 13:17:45:frequency.c:623:inc_freq_with_fixed_vco: get pcb 25 ~ 27, chip_temp 29 ~ 31, now 23.0s, target 31.8
2022-05-17 13:17:46:frequency.c:623:inc_freq_with_fixed_vco: get pcb 25 ~ 27, chip_temp 29 ~ 31, now 24.0s, target 32.0
2022-05-17 13:17:47:frequency.c:623:inc_freq_with_fixed_vco: get pcb 25 ~ 27, chip_temp 29 ~ 32, now 25.0s, target 32.2
2022-05-17 13:17:48:frequency.c:623:inc_freq_with_fixed_vco: get pcb 25 ~ 28, chip_temp 30 ~ 33, now 26.0s, target 32.3
2022-05-17 13:17:48:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 33 > 32.3 target_temp.
2022-05-17 13:17:54:frequency.c:623:inc_freq_with_fixed_vco: get pcb 26 ~ 27, chip_temp 30 ~ 34, now 32.0s, target 33.3
2022-05-17 13:17:54:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 34 > 33.3 target_temp.
2022-05-17 13:18:00:frequency.c:623:inc_freq_with_fixed_vco: get pcb 26 ~ 29, chip_temp 31 ~ 33, now 38.0s, target 34.3
2022-05-17 13:18:01:frequency.c:623:inc_freq_with_fixed_vco: get pcb 25 ~ 28, chip_temp 31 ~ 32, now 39.0s, target 34.5
2022-05-17 13:18:01:frequency.c:657:inc_freq_with_fixed_vco: [0] _POSTDIV1 = 7, _POSTDIV2 = 7, USER_DIV = 1, freq = 44
2022-05-17 13:18:07:frequency.c:623:inc_freq_with_fixed_vco: get pcb 27 ~ 29, chip_temp 31 ~ 33, now 45.0s, target 35.5
2022-05-17 13:18:07:frequency.c:657:inc_freq_with_fixed_vco: [1] _POSTDIV1 = 7, _POSTDIV2 = 6, USER_DIV = 1, freq = 52
2022-05-17 13:18:07:frequency.c:665:inc_freq_with_fixed_vco: set to 52M, get pcb 27 ~ 29, chip_temp 31 ~ 33
2022-05-17 13:18:07:power_api.c:376:set_to_voltage_by_steps: Set to voltage raw 2100, step by step.
2022-05-17 13:18:15:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2022-05-17 13:18:15:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 52 clock_counter_limit 5, no check, skip.
2022-05-17 13:18:23:frequency.c:623:inc_freq_with_fixed_vco: get pcb 28 ~ 30, chip_temp 31 ~ 34, now 61.3s, target 38.2
2022-05-17 13:18:23:frequency.c:657:inc_freq_with_fixed_vco: [2] _POSTDIV1 = 6, _POSTDIV2 = 6, USER_DIV = 1, freq = 61
2022-05-17 13:18:23:frequency.c:665:inc_freq_with_fixed_vco: set to 61M, get pcb 28 ~ 30, chip_temp 31 ~ 34
2022-05-17 13:18:23:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2022-05-17 13:18:23:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 61 clock_counter_limit 6, no check, skip.
2022-05-17 13:18:31:frequency.c:623:inc_freq_with_fixed_vco: get pcb 27 ~ 31, chip_temp 34 ~ 36, now 69.3s, target 39.6
2022-05-17 13:18:31:frequency.c:657:inc_freq_with_fixed_vco: [3] _POSTDIV1 = 7, _POSTDIV2 = 5, USER_DIV = 1, freq = 62
2022-05-17 13:18:31:frequency.c:665:inc_freq_with_fixed_vco: set to 62M, get pcb 27 ~ 31, chip_temp 34 ~ 36
2022-05-17 13:18:31:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2022-05-17 13:18:31:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 62 clock_counter_limit 6, no check, skip.
2022-05-17 13:18:39:frequency.c:623:inc_freq_with_fixed_vco: get pcb 28 ~ 32, chip_temp 33 ~ 36, now 77.3s, target 40.9
2022-05-17 13:18:39:frequency.c:657:inc_freq_with_fixed_vco: [4] _POSTDIV1 = 6, _POSTDIV2 = 5, USER_DIV = 1, freq = 73
2022-05-17 13:18:39:frequency.c:665:inc_freq_with_fixed_vco: set to 73M, get pcb 28 ~ 32, chip_temp 33 ~ 36
2022-05-17 13:18:39:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2022-05-17 13:18:39:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 73 clock_counter_limit 8, no check, skip.
2022-05-17 13:18:47:frequency.c:623:inc_freq_with_fixed_vco: get pcb 27 ~ 32, chip_temp 34 ~ 37, now 85.4s, target 42.2
2022-05-17 13:18:47:frequency.c:657:inc_freq_with_fixed_vco: [5] _POSTDIV1 = 7, _POSTDIV2 = 4, USER_DIV = 1, freq = 78
2022-05-17 13:18:47:frequency.c:665:inc_freq_with_fixed_vco: set to 78M, get pcb 27 ~ 32, chip_temp 34 ~ 37
2022-05-17 13:18:47:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2022-05-17 13:18:47:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 78 clock_counter_limit 9, no check, skip.
2022-05-17 13:18:55:frequency.c:623:inc_freq_with_fixed_vco: get pcb 28 ~ 34, chip_temp 35 ~ 38, now 93.4s, target 40.6
2022-05-17 13:18:55:frequency.c:657:inc_freq_with_fixed_vco: [6] _POSTDIV1 = 5, _POSTDIV2 = 5, USER_DIV = 1, freq = 88
2022-05-17 13:18:55:frequency.c:665:inc_freq_with_fixed_vco: set to 88M, get pcb 28 ~ 34, chip_temp 35 ~ 38
2022-05-17 13:18:55:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2022-05-17 13:18:55:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 88 clock_counter_limit 11, no check, skip.
2022-05-17 13:19:03:frequency.c:623:inc_freq_with_fixed_vco: get pcb 28 ~ 34, chip_temp 37 ~ 39, now 101.4s, target 41.9
2022-05-17 13:19:03:frequency.c:657:inc_freq_with_fixed_vco: [7] _POSTDIV1 = 6, _POSTDIV2 = 4, USER_DIV = 1, freq = 91
2022-05-17 13:19:03:frequency.c:665:inc_freq_with_fixed_vco: set to 91M, get pcb 28 ~ 34, chip_temp 37 ~ 39
2022-05-17 13:19:03:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2022-05-17 13:19:03:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 91 clock_counter_limit 11, no check, skip.
2022-05-17 13:19:11:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 35, chip_temp 36 ~ 40, now 109.4s, target 43.2
2022-05-17 13:19:11:frequency.c:657:inc_freq_with_fixed_vco: [8] _POSTDIV1 = 7, _POSTDIV2 = 3, USER_DIV = 1, freq = 104
2022-05-17 13:19:11:frequency.c:665:inc_freq_with_fixed_vco: set to 104M, get pcb 29 ~ 35, chip_temp 36 ~ 40
2022-05-17 13:19:11:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2022-05-17 13:19:11:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 104 clock_counter_limit 13, no check, skip.
2022-05-17 13:19:19:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 35, chip_temp 37 ~ 41, now 117.4s, target 44.6
2022-05-17 13:19:19:frequency.c:657:inc_freq_with_fixed_vco: [9] _POSTDIV1 = 5, _POSTDIV2 = 4, USER_DIV = 1, freq = 110
2022-05-17 13:19:19:frequency.c:665:inc_freq_with_fixed_vco: set to 110M, get pcb 29 ~ 35, chip_temp 37 ~ 41
2022-05-17 13:19:19:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2022-05-17 13:19:19:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 110 clock_counter_limit 14, no check, skip.
2022-05-17 13:19:27:frequency.c:623:inc_freq_with_fixed_vco: get pcb 30 ~ 37, chip_temp 38 ~ 43, now 125.4s, target 45.9
2022-05-17 13:19:27:frequency.c:657:inc_freq_with_fixed_vco: [10] _POSTDIV1 = 6, _POSTDIV2 = 3, USER_DIV = 1, freq = 122
2022-05-17 13:19:27:frequency.c:665:inc_freq_with_fixed_vco: set to 122M, get pcb 30 ~ 37, chip_temp 38 ~ 43
2022-05-17 13:19:27:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2022-05-17 13:19:27:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 122 clock_counter_limit 16, no check, skip.
2022-05-17 13:19:35:frequency.c:623:inc_freq_with_fixed_vco: get pcb 30 ~ 37, chip_temp 38 ~ 44, now 133.4s, target 47.2
2022-05-17 13:19:35:frequency.c:657:inc_freq_with_fixed_vco: [11] _POSTDIV1 = 4, _POSTDIV2 = 4, USER_DIV = 1, freq = 137
2022-05-17 13:19:35:frequency.c:665:inc_freq_with_fixed_vco: set to 137M, get pcb 30 ~ 37, chip_temp 38 ~ 44
2022-05-17 13:19:35:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2022-05-17 13:19:35:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 137 clock_counter_limit 18, no check, skip.
2022-05-17 13:19:43:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 38, chip_temp 41 ~ 45, now 141.4s, target 48.6
2022-05-17 13:19:43:frequency.c:657:inc_freq_with_fixed_vco: [12] _POSTDIV1 = 5, _POSTDIV2 = 3, USER_DIV = 1, freq = 146
2022-05-17 13:19:43:frequency.c:665:inc_freq_with_fixed_vco: set to 146M, get pcb 29 ~ 38, chip_temp 41 ~ 45
2022-05-17 13:19:43:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2022-05-17 13:19:43:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 146 clock_counter_limit 20, no check, skip.
2022-05-17 13:19:51:frequency.c:623:inc_freq_with_fixed_vco: get pcb 32 ~ 39, chip_temp 43 ~ 46, now 149.4s, target 49.9
2022-05-17 13:19:51:frequency.c:657:inc_freq_with_fixed_vco: [13] _POSTDIV1 = 7, _POSTDIV2 = 2, USER_DIV = 1, freq = 157
2022-05-17 13:19:51:frequency.c:665:inc_freq_with_fixed_vco: set to 157M, get pcb 32 ~ 39, chip_temp 43 ~ 46
2022-05-17 13:19:51:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2022-05-17 13:19:51:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 157 clock_counter_limit 22, no check, skip.
2022-05-17 13:19:59:frequency.c:623:inc_freq_with_fixed_vco: get pcb 31 ~ 40, chip_temp 42 ~ 49, now 157.4s, target 51.2
2022-05-17 13:19:59:frequency.c:657:inc_freq_with_fixed_vco: [14] _POSTDIV1 = 4, _POSTDIV2 = 3, USER_DIV = 1, freq = 183
2022-05-17 13:19:59:frequency.c:665:inc_freq_with_fixed_vco: set to 183M, get pcb 31 ~ 40, chip_temp 42 ~ 49
2022-05-17 13:19:59:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2022-05-17 13:19:59:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 183 clock_counter_limit 26, no check, skip.
2022-05-17 13:20:07:frequency.c:623:inc_freq_with_fixed_vco: get pcb 32 ~ 42, chip_temp 45 ~ 51, now 165.4s, target 52.6
2022-05-17 13:20:08:frequency.c:623:inc_freq_with_fixed_vco: get pcb 30 ~ 43, chip_temp 46 ~ 51, now 166.4s, target 52.7
2022-05-17 13:20:09:frequency.c:623:inc_freq_with_fixed_vco: get pcb 33 ~ 42, chip_temp 45 ~ 52, now 167.4s, target 52.9
2022-05-17 13:20:10:frequency.c:623:inc_freq_with_fixed_vco: get pcb 33 ~ 42, chip_temp 45 ~ 51, now 168.4s, target 53.1
2022-05-17 13:20:10:frequency.c:657:inc_freq_with_fixed_vco: [15] _POSTDIV1 = 6, _POSTDIV2 = 2, USER_DIV = 1, freq = 183
2022-05-17 13:20:10:frequency.c:665:inc_freq_with_fixed_vco: set to 183M, get pcb 33 ~ 42, chip_temp 45 ~ 51
2022-05-17 13:20:10:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2022-05-17 13:20:10:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 183 clock_counter_limit 26, no check, skip.
2022-05-17 13:20:18:frequency.c:623:inc_freq_with_fixed_vco: get pcb 33 ~ 44, chip_temp 46 ~ 53, now 176.4s, target 54.4
2022-05-17 13:20:19:frequency.c:623:inc_freq_with_fixed_vco: get pcb 33 ~ 44, chip_temp 46 ~ 53, now 177.4s, target 54.6
2022-05-17 13:20:20:frequency.c:623:inc_freq_with_fixed_vco: get pcb 33 ~ 44, chip_temp 46 ~ 53, now 178.4s, target 54.7
2022-05-17 13:20:21:frequency.c:623:inc_freq_with_fixed_vco: get pcb 32 ~ 45, chip_temp 48 ~ 53, now 179.4s, target 54.9
2022-05-17 13:20:22:frequency.c:623:inc_freq_with_fixed_vco: get pcb 34 ~ 44, chip_temp 47 ~ 53, now 180.4s, target 55.1
2022-05-17 13:20:22:frequency.c:657:inc_freq_with_fixed_vco: [16] _POSTDIV1 = 5, _POSTDIV2 = 2, USER_DIV = 1, freq = 220
2022-05-17 13:20:22:frequency.c:665:inc_freq_with_fixed_vco: set to 220M, get pcb 34 ~ 44, chip_temp 47 ~ 53
2022-05-17 13:20:22:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2022-05-17 13:20:22:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 220 clock_counter_limit 32, no check, skip.
2022-05-17 13:20:30:frequency.c:623:inc_freq_with_fixed_vco: get pcb 34 ~ 46, chip_temp 48 ~ 56, now 188.5s, target 56.4
2022-05-17 13:20:31:frequency.c:623:inc_freq_with_fixed_vco: get pcb 33 ~ 46, chip_temp 50 ~ 57, now 189.5s, target 56.6
2022-05-17 13:20:31:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 57 > 56.6 target_temp.
2022-05-17 13:20:37:frequency.c:623:inc_freq_with_fixed_vco: get pcb 35 ~ 48, chip_temp 50 ~ 58, now 195.5s, target 57.6
2022-05-17 13:20:37:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 58 > 57.6 target_temp.
2022-05-17 13:20:43:frequency.c:623:inc_freq_with_fixed_vco: get pcb 34 ~ 49, chip_temp 52 ~ 59, now 201.5s, target 58.6
2022-05-17 13:20:43:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 59 > 58.6 target_temp.
2022-05-17 13:20:49:frequency.c:623:inc_freq_with_fixed_vco: get pcb 35 ~ 50, chip_temp 51 ~ 60, now 207.5s, target 59.6
2022-05-17 13:20:49:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 60 > 59.6 target_temp.
2022-05-17 13:20:55:frequency.c:623:inc_freq_with_fixed_vco: get pcb 34 ~ 50, chip_temp 51 ~ 62, now 213.5s, target 60.6
2022-05-17 13:20:55:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 62 > 60.6 target_temp.
2022-05-17 13:21:01:frequency.c:623:inc_freq_with_fixed_vco: get pcb 36 ~ 52, chip_temp 52 ~ 64, now 219.5s, target 61.6
2022-05-17 13:21:01:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 64 > 61.6 target_temp.
2022-05-17 13:21:07:frequency.c:623:inc_freq_with_fixed_vco: get pcb 34 ~ 52, chip_temp 51 ~ 63, now 225.5s, target 62.6
2022-05-17 13:21:07:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 63 > 62.6 target_temp.
2022-05-17 13:21:13:frequency.c:623:inc_freq_with_fixed_vco: get pcb 35 ~ 53, chip_temp 51 ~ 64, now 231.5s, target 63.6
2022-05-17 13:21:13:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 64 > 63.6 target_temp.
2022-05-17 13:21:19:frequency.c:623:inc_freq_with_fixed_vco: get pcb 33 ~ 54, chip_temp 51 ~ 66, now 237.5s, target 64.6
2022-05-17 13:21:19:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 66 > 64.6 target_temp.
2022-05-17 13:21:25:frequency.c:623:inc_freq_with_fixed_vco: get pcb 34 ~ 53, chip_temp 47 ~ 65, now 243.5s, target 65.6
2022-05-17 13:21:26:frequency.c:623:inc_freq_with_fixed_vco: get pcb 34 ~ 54, chip_temp 47 ~ 65, now 244.5s, target 65.7
2022-05-17 13:21:27:frequency.c:623:inc_freq_with_fixed_vco: get pcb 32 ~ 54, chip_temp 48 ~ 65, now 245.5s, target 65.9
2022-05-17 13:21:28:frequency.c:623:inc_freq_with_fixed_vco: get pcb 32 ~ 54, chip_temp 48 ~ 65, now 246.5s, target 66.1
2022-05-17 13:21:29:frequency.c:623:inc_freq_with_fixed_vco: get pcb 34 ~ 54, chip_temp 47 ~ 65, now 247.5s, target 66.2
2022-05-17 13:21:30:frequency.c:623:inc_freq_with_fixed_vco: get pcb 34 ~ 53, chip_temp 47 ~ 65, now 248.5s, target 66.4
2022-05-17 13:21:31:frequency.c:623:inc_freq_with_fixed_vco: get pcb 33 ~ 53, chip_temp 46 ~ 64, now 249.5s, target 66.6
2022-05-17 13:21:31:frequency.c:657:inc_freq_with_fixed_vco: [17] _POSTDIV1 = 4, _POSTDIV2 = 2, USER_DIV = 1, freq = 275
2022-05-17 13:21:31:frequency.c:665:inc_freq_with_fixed_vco: set to 275M, get pcb 33 ~ 53, chip_temp 46 ~ 64
2022-05-17 13:21:31:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2022-05-17 13:21:31:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 275 clock_counter_limit 41, no check, skip.
2022-05-17 13:21:39:frequency.c:623:inc_freq_with_fixed_vco: get pcb 34 ~ 54, chip_temp 48 ~ 65, now 257.5s, target 67.9
2022-05-17 13:21:39:frequency.c:657:inc_freq_with_fixed_vco: [18] _POSTDIV1 = 7, _POSTDIV2 = 1, USER_DIV = 1, freq = 314
2022-05-17 13:21:39:frequency.c:665:inc_freq_with_fixed_vco: set to 314M, get pcb 34 ~ 54, chip_temp 48 ~ 65
2022-05-17 13:21:39:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2022-05-17 13:21:39:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 314 clock_counter_limit 47, no check, skip.
2022-05-17 13:21:42:driver-hash-chip.c:737:dump_adc_voltage_v2: get ADC_DATAOUT from chain 0 with 0 regs timeout.
chain 0 domain  0:   d0 0.406,   d1 0.405,   d2 0.397,   d3 0.403,   sum = 1.610657
chain 0 domain  1:   d0 0.412,   d1 0.396,   d2 0.419,   d3 0.408,   sum = 1.634155
chain 0 domain  2:   d0 0.406,   d1 0.396,   d2 0.413,   d3 0.405,   sum = 1.619873
chain 0 domain  3:   d0 0.409,   d1 0.399,   d2 0.415,   d3 0.407,   sum = 1.629822
chain 0 domain  4:   d0 0.401,   d1 0.406,   d2 0.376,   d3 0.394,   sum = 1.577026
chain 0 domain  5:   d0 0.409,   d1 0.405,   d2 0.381,   d3 0.398,   sum = 1.592529
chain 0 domain  6:   d0 0.406,   d1 0.412,   d2 0.398,   d3 0.405,   sum = 1.621765
chain 0 domain  7:   d0 0.404,   d1 0.406,   d2 0.409,   d3 0.406,   sum = 1.625732
chain 0 domain  8:   d0 0.395,   d1 0.396,   d2 0.386,   d3 0.392,   sum = 1.567993
chain 0 domain  9:   d0 0.405,   d1 0.395,   d2 0.409,   d3 0.403,   sum = 1.612427
chain 0 domain 10:   d0 0.407,   d1 0.395,   d2 0.391,   d3 0.398,   sum = 1.590820
chain 0 domain 11:   d0 0.393,   d1 0.385,   d2 0.386,   d3 0.388,   sum = 1.553101
chain 0 domain 12:   d0 0.390,   d1 0.387,   d2 0.385,   d3 0.387,   sum = 1.549255
2022-05-17 13:21:42:driver-hash-chip.c:493:check_adc_voltage: PASS domainn volt check: request 0.800 (index 0, open_core)
2022-05-17 13:21:48:frequency.c:623:inc_freq_with_fixed_vco: get pcb 33 ~ 53, chip_temp 51 ~ 66, now 266.0s, target 69.3
2022-05-17 13:21:48:frequency.c:657:inc_freq_with_fixed_vco: [19] _POSTDIV1 = 6, _POSTDIV2 = 1, USER_DIV = 1, freq = 366
2022-05-17 13:21:48:frequency.c:665:inc_freq_with_fixed_vco: set to 366M, get pcb 33 ~ 53, chip_temp 51 ~ 66
2022-05-17 13:21:48:power_api.c:376:set_to_voltage_by_steps: Set to voltage raw 2050, step by step.
2022-05-17 13:21:55:driver-hash-chip.c:737:dump_adc_voltage_v2: get ADC_DATAOUT from chain 0 with 0 regs timeout.
chain 0 domain  0:   d0 0.397,   d1 0.392,   d2 0.395,   d3 0.394,   sum = 1.577209
chain 0 domain  1:   d0 0.398,   d1 0.388,   d2 0.406,   d3 0.397,   sum = 1.589783
chain 0 domain  2:   d0 0.394,   d1 0.389,   d2 0.391,   d3 0.392,   sum = 1.566711
chain 0 domain  3:   d0 0.398,   d1 0.391,   d2 0.393,   d3 0.394,   sum = 1.576599
chain 0 domain  4:   d0 0.389,   d1 0.384,   d2 0.394,   d3 0.388,   sum = 1.554199
chain 0 domain  5:   d0 0.399,   d1 0.382,   d2 0.381,   d3 0.387,   sum = 1.550110
chain 0 domain  6:   d0 0.400,   d1 0.391,   d2 0.406,   d3 0.399,   sum = 1.596252
chain 0 domain  7:   d0 0.402,   d1 0.388,   d2 0.398,   d3 0.396,   sum = 1.584167
chain 0 domain  8:   d0 0.394,   d1 0.378,   d2 0.393,   d3 0.388,   sum = 1.553528
chain 0 domain  9:   d0 0.402,   d1 0.384,   d2 0.408,   d3 0.398,   sum = 1.591309
chain 0 domain 10:   d0 0.397,   d1 0.384,   d2 0.402,   d3 0.394,   sum = 1.577026
chain 0 domain 11:   d0 0.384,   d1 0.376,   d2 0.377,   d3 0.359,   sum = 1.494812
chain 0 domain 12:   d0 0.380,   d1 0.377,   d2 0.376,   d3 0.360,   sum = 1.493958
2022-05-17 13:21:55:driver-hash-chip.c:493:check_adc_voltage: PASS domainn volt check: request 0.800 (index 0, open_core)
2022-05-17 13:21:55:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2022-05-17 13:21:55:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 366 clock_counter_limit 55, no check, skip.
2022-05-17 13:21:57:driver-hash-chip.c:737:dump_adc_voltage_v2: get ADC_DATAOUT from chain 0 with 0 regs timeout.
chain 0 domain  0:   d0 0.396,   d1 0.394,   d2 0.391,   d3 0.394,   sum = 1.574829
chain 0 domain  1:   d0 0.397,   d1 0.387,   d2 0.398,   d3 0.394,   sum = 1.575867
chain 0 domain  2:   d0 0.394,   d1 0.392,   d2 0.386,   d3 0.391,   sum = 1.562988
chain 0 domain  3:   d0 0.398,   d1 0.390,   d2 0.396,   d3 0.394,   sum = 1.578125
chain 0 domain  4:   d0 0.394,   d1 0.382,   d2 0.388,   d3 0.388,   sum = 1.551575
chain 0 domain  5:   d0 0.399,   d1 0.392,   d2 0.394,   d3 0.395,   sum = 1.580444
chain 0 domain  6:   d0 0.400,   d1 0.389,   d2 0.404,   d3 0.398,   sum = 1.590881
chain 0 domain  7:   d0 0.402,   d1 0.386,   d2 0.382,   d3 0.390,   sum = 1.559021
chain 0 domain  8:   d0 0.388,   d1 0.393,   d2 0.373,   d3 0.351,   sum = 1.505249
chain 0 domain  9:   d0 0.401,   d1 0.383,   d2 0.409,   d3 0.398,   sum = 1.590698
chain 0 domain 10:   d0 0.395,   d1 0.386,   d2 0.386,   d3 0.389,   sum = 1.555908
chain 0 domain 11:   d0 0.385,   d1 0.377,   d2 0.377,   d3 0.356,   sum = 1.494934
chain 0 domain 12:   d0 0.381,   d1 0.377,   d2 0.376,   d3 0.360,   sum = 1.494324
2022-05-17 13:21:58:driver-hash-chip.c:493:check_adc_voltage: PASS domainn volt check: request 0.800 (index 0, open_core)
2022-05-17 13:22:04:frequency.c:623:inc_freq_with_fixed_vco: get pcb 33 ~ 52, chip_temp 53 ~ 65, now 281.7s, target 72.0
2022-05-17 13:22:04:frequency.c:657:inc_freq_with_fixed_vco: [20] _POSTDIV1 = 5, _POSTDIV2 = 1, USER_DIV = 1, freq = 440
2022-05-17 13:22:04:frequency.c:665:inc_freq_with_fixed_vco: set to 440M, get pcb 33 ~ 52, chip_temp 53 ~ 65
2022-05-17 13:22:04:power_api.c:376:set_to_voltage_by_steps: Set to voltage raw 1990, step by step.
2022-05-17 13:22:11:driver-hash-chip.c:737:dump_adc_voltage_v2: get ADC_DATAOUT from chain 0 with 0 regs timeout.
chain 0 domain  0:   d0 0.384,   d1 0.383,   d2 0.381,   d3 0.350,   sum = 1.498413
chain 0 domain  1:   d0 0.393,   d1 0.375,   d2 0.378,   d3 0.378,   sum = 1.523560
chain 0 domain  2:   d0 0.383,   d1 0.380,   d2 0.376,   d3 0.356,   sum = 1.495117
chain 0 domain  3:   d0 0.387,   d1 0.378,   d2 0.386,   d3 0.384,   sum = 1.534851
chain 0 domain  4:   d0 0.380,   d1 0.371,   d2 0.386,   d3 0.354,   sum = 1.492004
chain 0 domain  5:   d0 0.381,   d1 0.381,   d2 0.368,   d3 0.364,   sum = 1.495056
chain 0 domain  6:   d0 0.390,   d1 0.386,   d2 0.371,   d3 0.352,   sum = 1.498230
chain 0 domain  7:   d0 0.382,   d1 0.382,   d2 0.387,   d3 0.373,   sum = 1.523071
chain 0 domain  8:   d0 0.374,   d1 0.369,   d2 0.370,   d3 0.365,   sum = 1.478638
chain 0 domain  9:   d0 0.383,   d1 0.376,   d2 0.377,   d3 0.357,   sum = 1.492798
chain 0 domain 10:   d0 0.380,   d1 0.375,   d2 0.384,   d3 0.354,   sum = 1.492798
chain 0 domain 11:   d0 0.373,   d1 0.366,   d2 0.366,   d3 0.367,   sum = 1.470886
chain 0 domain 12:   d0 0.368,   d1 0.366,   d2 0.364,   d3 0.364,   sum = 1.462341
2022-05-17 13:22:11:driver-hash-chip.c:493:check_adc_voltage: PASS domainn volt check: request 0.800 (index 0, open_core)
2022-05-17 13:22:11:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2022-05-17 13:22:11:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 440 clock_counter_limit 67, no check, skip.
2022-05-17 13:22:13:driver-hash-chip.c:737:dump_adc_voltage_v2: get ADC_DATAOUT from chain 0 with 0 regs timeout.
chain 0 domain  0:   d0 0.384,   d1 0.382,   d2 0.381,   d3 0.351,   sum = 1.497864
chain 0 domain  1:   d0 0.392,   d1 0.376,   d2 0.375,   d3 0.380,   sum = 1.522400
chain 0 domain  2:   d0 0.383,   d1 0.378,   d2 0.376,   d3 0.358,   sum = 1.496216
chain 0 domain  3:   d0 0.386,   d1 0.385,   d2 0.379,   d3 0.383,   sum = 1.533325
chain 0 domain  4:   d0 0.378,   d1 0.374,   d2 0.385,   d3 0.357,   sum = 1.493896
chain 0 domain  5:   d0 0.381,   d1 0.377,   d2 0.387,   d3 0.348,   sum = 1.491943
chain 0 domain  6:   d0 0.386,   d1 0.379,   d2 0.389,   d3 0.344,   sum = 1.498535
chain 0 domain  7:   d0 0.381,   d1 0.383,   d2 0.379,   d3 0.355,   sum = 1.496826
chain 0 domain  8:   d0 0.378,   d1 0.367,   d2 0.382,   d3 0.356,   sum = 1.483643
chain 0 domain  9:   d0 0.384,   d1 0.387,   d2 0.377,   d3 0.346,   sum = 1.493469
chain 0 domain 10:   d0 0.380,   d1 0.375,   d2 0.373,   d3 0.365,   sum = 1.493042
chain 0 domain 11:   d0 0.373,   d1 0.367,   d2 0.366,   d3 0.364,   sum = 1.469971
chain 0 domain 12:   d0 0.368,   d1 0.366,   d2 0.365,   d3 0.364,   sum = 1.462463
2022-05-17 13:22:13:driver-hash-chip.c:493:check_adc_voltage: PASS domainn volt check: request 0.800 (index 0, open_core)
2022-05-17 13:22:19:frequency.c:623:inc_freq_with_fixed_vco: get pcb 32 ~ 51, chip_temp 54 ~ 66, now 297.6s, target 70.6
2022-05-17 13:22:19:frequency.c:657:inc_freq_with_fixed_vco: [21] _POSTDIV1 = 4, _POSTDIV2 = 1, USER_DIV = 1, freq = 550
2022-05-17 13:22:19:frequency.c:665:inc_freq_with_fixed_vco: set to 550M, get pcb 32 ~ 51, chip_temp 54 ~ 66
2022-05-17 13:22:19:power_api.c:376:set_to_voltage_by_steps: Set to voltage raw 1870, step by step.
2022-05-17 13:22:29:driver-hash-chip.c:737:dump_adc_voltage_v2: get ADC_DATAOUT from chain 0 with 0 regs timeout.
chain 0 domain  0:   d0 0.360,   d1 0.359,   d2 0.357,   d3 0.356,   sum = 1.432861
chain 0 domain  1:   d0 0.363,   d1 0.354,   d2 0.368,   d3 0.335,   sum = 1.418945
chain 0 domain  2:   d0 0.359,   d1 0.356,   d2 0.356,   d3 0.355,   sum = 1.425781
chain 0 domain  3:   d0 0.367,   d1 0.354,   d2 0.356,   d3 0.367,   sum = 1.444824
chain 0 domain  4:   d0 0.355,   d1 0.352,   d2 0.352,   d3 0.361,   sum = 1.419800
chain 0 domain  5:   d0 0.358,   d1 0.351,   d2 0.362,   d3 0.349,   sum = 1.419006
chain 0 domain  6:   d0 0.361,   d1 0.357,   d2 0.359,   d3 0.358,   sum = 1.434753
chain 0 domain  7:   d0 0.359,   d1 0.351,   d2 0.354,   d3 0.351,   sum = 1.413940
chain 0 domain  8:   d0 0.350,   d1 0.354,   d2 0.347,   d3 0.344,   sum = 1.394592
chain 0 domain  9:   d0 0.361,   d1 0.364,   d2 0.343,   d3 0.344,   sum = 1.412476
chain 0 domain 10:   d0 0.356,   d1 0.351,   d2 0.356,   d3 0.351,   sum = 1.413879
chain 0 domain 11:   d0 0.350,   d1 0.344,   d2 0.345,   d3 0.343,   sum = 1.381348
chain 0 domain 12:   d0 0.345,   d1 0.344,   d2 0.342,   d3 0.341,   sum = 1.372192
2022-05-17 13:22:29:driver-hash-chip.c:493:check_adc_voltage: PASS domainn volt check: request 0.800 (index 0, open_core)
2022-05-17 13:22:29:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0
2022-05-17 13:22:29:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 550 clock_counter_limit 85, no check, skip.
2022-05-17 13:22:31:driver-hash-chip.c:737:dump_adc_voltage_v2: get ADC_DATAOUT from chain 0 with 0 regs timeout.
chain 0 domain  0:   d0 0.359,   d1 0.357,   d2 0.358,   d3 0.356,   sum = 1.430725
chain 0 domain  1:   d0 0.363,   d1 0.351,   d2 0.350,   d3 0.358,   sum = 1.423279
chain 0 domain  2:   d0 0.358,   d1 0.357,   d2 0.355,   d3 0.352,   sum = 1.422058
chain 0 domain  3:   d0 0.364,   d1 0.355,   d2 0.363,   d3 0.357,   sum = 1.439453
chain 0 domain  4:   d0 0.355,   d1 0.355,   d2 0.350,   d3 0.350,   sum = 1.410950
chain 0 domain  5:   d0 0.359,   d1 0.350,   d2 0.358,   d3 0.344,   sum = 1.411194
chain 0 domain  6:   d0 0.360,   d1 0.357,   d2 0.358,   d3 0.356,   sum = 1.432129
chain 0 domain  7:   d0 0.358,   d1 0.352,   d2 0.352,   d3 0.368,   sum = 1.430603
chain 0 domain  8:   d0 0.353,   d1 0.359,   d2 0.334,   d3 0.342,   sum = 1.387817
chain 0 domain  9:   d0 0.364,   d1 0.360,   d2 0.346,   d3 0.344,   sum = 1.414185
chain 0 domain 10:   d0 0.359,   d1 0.364,   d2 0.351,   d3 0.360,   sum = 1.434448
chain 0 domain 11:   d0 0.351,   d1 0.345,   d2 0.344,   d3 0.344,   sum = 1.384705
chain 0 domain 12:   d0 0.345,   d1 0.343,   d2 0.342,   d3 0.341,   sum = 1.371948
2022-05-17 13:22:31:driver-hash-chip.c:493:check_adc_voltage: PASS domainn volt check: request 0.800 (index 0, open_core)
2022-05-17 13:22:31:power_api.c:376:set_to_voltage_by_steps: Set to voltage raw 1810, step by step.
2022-05-17 13:22:39:driver-hash-chip.c:737:dump_adc_voltage_v2: get ADC_DATAOUT from chain 0 with 0 regs timeout.
chain 0 domain  0:   d0 0.348,   d1 0.346,   d2 0.346,   d3 0.344,   sum = 1.383789
chain 0 domain  1:   d0 0.351,   d1 0.354,   d2 0.343,   d3 0.325,   sum = 1.372375
chain 0 domain  2:   d0 0.346,   d1 0.346,   d2 0.344,   d3 0.342,   sum = 1.378113
chain 0 domain  3:   d0 0.353,   d1 0.346,   d2 0.346,   d3 0.344,   sum = 1.388550
chain 0 domain  4:   d0 0.344,   d1 0.341,   d2 0.347,   d3 0.337,   sum = 1.369080
chain 0 domain  5:   d0 0.346,   d1 0.340,   d2 0.343,   d3 0.336,   sum = 1.364746
chain 0 domain  6:   d0 0.349,   d1 0.347,   d2 0.347,   d3 0.344,   sum = 1.387146
chain 0 domain  7:   d0 0.352,   d1 0.345,   d2 0.330,   d3 0.356,   sum = 1.382263
chain 0 domain  8:   d0 0.341,   d1 0.347,   d2 0.324,   d3 0.350,   sum = 1.362427
chain 0 domain  9:   d0 0.344,   d1 0.347,   d2 0.337,   d3 0.369,   sum = 1.397400
chain 0 domain 10:   d0 0.349,   d1 0.348,   d2 0.327,   d3 0.364,   sum = 1.387756
chain 0 domain 11:   d0 0.340,   d1 0.334,   d2 0.333,   d3 0.335,   sum = 1.341553
chain 0 domain 12:   d0 0.334,   d1 0.333,   d2 0.330,   d3 0.331,   sum = 1.327942
2022-05-17 13:22:39:driver-hash-chip.c:493:check_adc_voltage: PASS domainn volt check: request 0.800 (index 0, open_core)
2022-05-17 13:22:39:frequency.c:442:inc_asic_diff_freq_by_steps: chain = 0, start = 550, freq_step = 5
2022-05-17 13:22:48:driver-btm-api.c:666:set_timeout: freq = 610, percent = 90, hcn = 707788, timeout = 1160
2022-05-17 13:22:48:power_api.c:353:set_to_working_voltage_by_steps: Set to voltage raw 1800, step by step.
2022-05-17 13:22:53:thread.c:1533:create_check_system_status_thread: create thread
2022-05-17 13:22:53:thread.c:1508:create_asic_status_monitor_thread: create thread
2022-05-17 13:22:53:driver-btm-api.c:2599:bitmain_soc_init: Init done!
2022-05-17 13:22:58:driver-btm-api.c:247:set_miner_status: STATUS_OKAY
2022-05-17 13:22:59:frequency.c:107:get_ideal_hash_rate_GH: ideal_hash_rate = 17378
2022-05-17 13:22:59:frequency.c:128:get_sale_hash_rate_GH: sale_hash_rate = 16000
2022-05-17 13:23:03:driver-btm-api.c:1634:dhash_chip_send_job: Version num 8
2022-05-17 13:23:03:driver-btm-api.c:1778:dhash_chip_send_job: stime.tv_sec 1652793783, block_ntime 1652793768

EDIT: i turn it off/on and second chain come up....3rd not, but i am really confused...what can cause this?

2022-05-17 13:31:51:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[0]: find 78 asic, times 0
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x 7777777
2022-05-17 13:31:55:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 0
2022-05-17 13:31:56:board.c:81:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2022-05-17 13:31:58:board.c:94:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2022-05-17 13:31:58:power_api.c:334:modify_check_asic_voltage: check_asic_voltage_raw  = 1900
2022-05-17 13:31:58:power_api.c:298:set_to_check_asic_voltage_by_steps: Set to voltage raw 1900, step by step.
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x 7777777
2022-05-17 13:32:16:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 1
2022-05-17 13:32:17:board.c:81:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2022-05-17 13:32:19:board.c:94:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2022-05-17 13:32:19:power_api.c:334:modify_check_asic_voltage: check_asic_voltage_raw  = 2000
2022-05-17 13:32:19:power_api.c:298:set_to_check_asic_voltage_by_steps: Set to voltage raw 2000, step by step.
chain 1, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x 7777777
2022-05-17 13:32:37:driver-btm-api.c:1035:check_asic_number_with_power_on:

[BitMaxz]

You will need a tool that can edit the EEPROM and change the serial number and should be matched on the working hashboard the tool looks like this "Antminer hashboard code editor"
Since you don't have a Hashboard code editor(EEPROM editor) I think you can try to flash your unit with Braiins OS others said it can bypass the serial mismatched.

But if the issue is still the same then you have broken hashboards with dead ASIC chips that need to replace with working ASIC chips.

[X-ALI_X]

Hi Guys, new in this forum.. however i appreciate if anyone can help me, I have s17+ antminer its been running for 20Hours only and one of the hashboards are giving HW 44,700..  now i have read in multiple places that HW is not to worry about, but 44,700 in less than a day i dont think this is something to ignore !! would anyone agree with me, or still nothing to worry about meanwhile the other 2 hasboards are giving 200 / 190 ...

[BitMaxz]

Hi Guys, new in this forum.. however i appreciate if anyone can help me, I have s17+ antminer its been running for 20Hours only and one of the hashboards are giving HW 44,700..  now i have read in multiple places that HW is not to worry about, but 44,700 in less than a day i dont think this is something to ignore !! would anyone agree with me, or still nothing to worry about meanwhile the other 2 hasboards are giving 200 / 190 ...

That value for hardware error is pretty high it could be due to overheating do you mind posting the whole kernel logs?
You can find the kernel logs under the system tab then copy all kernel logs and post it here don't forget to put them inside the insert code tag(a # button) or use pastebin.com and paste the URL here.

It would be easier for us to troubleshoot if you can provide these kernel logs here because all of the problems of your unit should under your kernel logs

[lord jones]

Hashboard needs repair

[MinerMEDIC]

The number one major design flaw of these high density 17 Series is the fact that soldered on the heatsinks only sound good in theory. In reality you have to bond copper to Silicon in order for the heatsinks to have something to solder onto. Things really turn to shit though when the ASIC gets hot enough so that the copper coating actually dissolves into the solder! Of course when there’s no surface to cling to anymore the heat sink simply falls off, sometimes they call this black ASIC. Once this occurs, you either have to replace the chip or use a thermal heat sink epoxy. You cannot rely on any other adhesive at these temperatures, the old Bitmain vinyl thermal set adhesive can’t do it, silicone can’t do it, etc.

I noticed some heat warnings in the log, if you have a Heatsinks hanging on by a thread they are certainly not carrying away heat like they are supposed to.

[EastCoastASICRepair]

Give them the baking treatment at 400 degrees for 10 mins, then at least 20 minutes to cooldown in the oven before any other diagnostics. 0 asic means there is a chip down the chain that is breaking the communications. Likely a loose solder connection or a bad chip.