Title: Antminer T17e two hash boards not responding out of three.
Post by: fsofia on March 13, 2021, 07:36:01 PM
I bought a used miner but it seems to be partially broken. This is what I did: I powered on the miner, already connected with wired LAN, DHCP ok, web management ok with initial root password. I configured the mining with my account and worker on f2pool. After some initial hashing, no hashing was definitely present (unfortunately I don't have the kernel log. I then tried di connect one by one the hash boards on the different Chains just to cross-check both the controller and the hash boards. As far I can understand the result of the test is the folowing: 1. the control board is working for all the 4 Chains (0,1,2,3) 2. One hash board - originally connected to Chain(0) - is working and reaches a stable hasrate after about 15 minutes. 3. the other two hash boards have problems. Here the kernel log for one of them (the other is similar): 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: 195672K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 33704K 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: 20664K (cc6d2000 - cdb00000) 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: 13/6, 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: 5846/4013, 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 2021-03-13 08:55:16:thread.c:1555:create_bitmain_soc_init_thread: create thread 2021-03-13 08:55:16:driver-btm-api.c:682:init_freq_mode: This is scan-user version 2021-03-13 08:55:16:driver-btm-api.c:2518:bitmain_soc_init: Miner compile time: Thu Oct 22 07:35:06 CST 2020 type: Antminer T17e 2021-03-13 08:55:16:driver-btm-api.c:2519:bitmain_soc_init: commit version: 037ddcd 2020-10-21 22:42:21, build by: jenkins 2020-10-22 07:39:39 2021-03-13 08:55:16:driver-btm-api.c:2520:bitmain_soc_init: opt_multi_version = 1 2021-03-13 08:55:16:driver-btm-api.c:2521:bitmain_soc_init: opt_bitmain_ab = 1 2021-03-13 08:55:16:driver-btm-api.c:2522:bitmain_soc_init: mid_auto_gen = 0 2021-03-13 08:55:16:driver-btm-api.c:2523:bitmain_soc_init: work_mode = 0 2021-03-13 08:55:16:driver-btm-api.c:2524:bitmain_soc_init: power_feedback_en = true 2021-03-13 08:55:16:driver-btm-api.c:2067:show_sn: no SN got, please write SN to /config/sn 2021-03-13 08:55:16:driver-btm-api.c:1384:miner_device_init: Detect 256MB control board of XILINX 2021-03-13 08:55:16:driver-btm-api.c:1325:init_fan_parameter: fan_eft : 0 fan_pwm : 0 2021-03-13 08:55:22:driver-btm-api.c:1309:init_miner_version: miner ID : 81280c042b10481c 2021-03-13 08:55:22:driver-btm-api.c:1315:init_miner_version: FPGA Version = 0xB023 2021-03-13 08:55:23:auto_adapt.c:100:_get_board_info: chain[2] board bin: 1, chip bin: 1, chip ft: A4V4, chip version: AB 2021-03-13 08:55:23:driver-btm-api.c:2164:get_calibration_voltage: calibration voltage flag is error data. 2021-03-13 08:55:23 voltage[2] = 1840 2021-03-13 08:55:23:auto_adapt.c:273:is_sweep_failed_before: open sweep tag failed voltage_ref = 1840 2100 2100 2100 2100 2100 2100 2100 2100 2100 2100 2100 2100 2100 2100 2100 2100 2100 2100 2100 2100 2100 2100 2100 2100 2070 2070 2060 2060 2050 2020 2020 2010 2010 2000 1980 1980 1970 1960 1950 1910 1980 1970 1960 1950 1910
2021-03-13 08:55:23:thread.c:1523:create_read_nonce_reg_thread: create thread 2021-03-13 08:55:23:driver-btm-api.c:698:dump_pcb_bom_version: Chain [2] PCB Version: 0x010a 2021-03-13 08:55:23:driver-btm-api.c:699:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100 2021-03-13 08:55:30:driver-btm-api.c:2344:bitmain_board_init: Fan check passed. 2021-03-13 08:55:31:board.c:81:jump_and_app_check_restore_pic: chain[2] PIC jump to app 2021-03-13 08:55:33:board.c:94:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88 2021-03-13 08:55:33:thread.c:1518:create_pic_heart_beat_thread: create thread 2021-03-13 08:55:35:power_api.c:241:power_init: power type version: 0x0042 2021-03-13 08:55:36:power_api.c:259:power_init: Power init: 2021-03-13 08:55:36:power_api.c:260:power_init: current_voltage_raw = 2136 2021-03-13 08:55:36:power_api.c:261:power_init: highest_voltage_raw = 2000 2021-03-13 08:55:36:power_api.c:262:power_init: working_voltage_raw = 1800 2021-03-13 08:55:36:power_api.c:263:power_init: higher_voltage_raw = 1850 2021-03-13 08:55:36:power_api.c:264:power_init: check_asic_voltage_raw = 1800 2021-03-13 08:55:36:driver-btm-api.c:2354:bitmain_board_init: Enter 60s sleep to make sure power release finish. 2021-03-13 08:56:38:driver-btm-api.c:1123:check_asic_number_until_volt_balance: THIS is No.1 time boost asic: 2021-03-13 08:56:38:power_api.c:334:modify_check_asic_voltage: check_asic_voltage_raw = 1800 2021-03-13 08:56:41:power_api.c:298:set_to_check_asic_voltage_by_steps: Set to voltage raw 1800, step by step. 2021-03-13 08:56:58:uart.c:69:set_baud: set UART baud to 115200 chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x 7777777 2021-03-13 08:57:02:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 0 2021-03-13 08:57:03:board.c:81:jump_and_app_check_restore_pic: chain[2] PIC jump to app 2021-03-13 08:57:05:board.c:94:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88 2021-03-13 08:57:05:power_api.c:334:modify_check_asic_voltage: check_asic_voltage_raw = 1900 2021-03-13 08:57:05: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 2021-03-13 08:57:17:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 1 2021-03-13 08:57:19:board.c:81:jump_and_app_check_restore_pic: chain[2] PIC jump to app 2021-03-13 08:57:21:board.c:94:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88 2021-03-13 08:57:21:power_api.c:334:modify_check_asic_voltage: check_asic_voltage_raw = 2000 2021-03-13 08:57:21: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 2021-03-13 08:57:33:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 2 2021-03-13 08:57:35:board.c:81:jump_and_app_check_restore_pic: chain[2] PIC jump to app 2021-03-13 08:57:37:board.c:94:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88 2021-03-13 08:57:37:power_api.c:334:modify_check_asic_voltage: check_asic_voltage_raw = 2100 2021-03-13 08:57:37: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 2021-03-13 08:57:49:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 3 2021-03-13 08:57:50:board.c:81:jump_and_app_check_restore_pic: chain[2] PIC jump to app 2021-03-13 08:57:52:board.c:94:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88 2021-03-13 08:57:52:power_api.c:334:modify_check_asic_voltage: check_asic_voltage_raw = 1800 2021-03-13 08:57:52:power_api.c:298:set_to_check_asic_voltage_by_steps: Set to voltage raw 1800, step by step. 2021-03-13 08:58:08:driver-btm-api.c:1217:check_asic_number: Chain 2 only find 0 asic, will power off hash board 2 2021-03-13 08:58:09:driver-btm-api.c:247:set_miner_status: ERROR_SOC_INIT 2021-03-13 08:58:09:driver-btm-api.c:176:stop_mining: stop mining: soc init failed! 2021-03-13 08:58:09:thread.c:1595:cancel_read_nonce_reg_thread: cancel thread 2021-03-13 08:58:09:driver-btm-api.c:147:killall_hashboard: ****power off hashboard****
I think the problem start with: 2021-03-13 08:57:02:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 0Any suggestion welcome, thanks.
Title: Re: Antminer T17e two hash boards not responding out of three.
Post by: mikeywith on March 14, 2021, 12:25:03 AM
2021-03-13 08:57:02:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 0
In a nutshell, this means, the hashboard is dead, it's usually caused by a bad chip or a losen heatsink, this is a very common issue that happens to well over 30% of the miners based on an old large sample data ( a few months after release), it's safe to assume that by now it's over 50%, so it really isn't anything unusual. However, the kernel log isn't showing any signs of the other 2 boards, they are either disconnected from the PSU, or the ribbon cable is out, did you tighten all the screws on all rails?
Title: Re: Antminer T17e two hash boards not responding out of three.
Post by: fsofia on March 14, 2021, 08:58:49 AM
@mikeywith, thanks for the info, so it seems I've bought a broken miner. Shame on the seller! The kernel log isn't showing any signs of the other 2 boards because it was taken when they were disconnected because I was trying them one by one. I post the kernel log (starting from a certain point) with all the three boards connected, in case there are any other useful informations. 2021-03-14 08:22:29:thread.c:1523:create_read_nonce_reg_thread: create thread 2021-03-14 08:22:29:driver-btm-api.c:698:dump_pcb_bom_version: Chain [0] PCB Version: 0x010a 2021-03-14 08:22:29:driver-btm-api.c:699:dump_pcb_bom_version: Chain [0] BOM Version: 0x0100 2021-03-14 08:22:29:driver-btm-api.c:698:dump_pcb_bom_version: Chain [1] PCB Version: 0x010a 2021-03-14 08:22:29:driver-btm-api.c:699:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100 2021-03-14 08:22:29:driver-btm-api.c:698:dump_pcb_bom_version: Chain [2] PCB Version: 0x010a 2021-03-14 08:22:29:driver-btm-api.c:699:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100 2021-03-14 08:22:35:driver-btm-api.c:2344:bitmain_board_init: Fan check passed. 2021-03-14 08:22:36:board.c:81:jump_and_app_check_restore_pic: chain[0] PIC jump to app 2021-03-14 08:22:39:board.c:94:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88 2021-03-14 08:22:40:board.c:81:jump_and_app_check_restore_pic: chain[1] PIC jump to app 2021-03-14 08:22:42:board.c:94:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88 2021-03-14 08:22:43:board.c:81:jump_and_app_check_restore_pic: chain[2] PIC jump to app 2021-03-14 08:22:45:board.c:94:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88 2021-03-14 08:22:45:thread.c:1518:create_pic_heart_beat_thread: create thread 2021-03-14 08:22:46:power_api.c:241:power_init: power type version: 0x0042 2021-03-14 08:22:48:power_api.c:259:power_init: Power init: 2021-03-14 08:22:48:power_api.c:260:power_init: current_voltage_raw = 2136 2021-03-14 08:22:48:power_api.c:261:power_init: highest_voltage_raw = 2000 2021-03-14 08:22:48:power_api.c:262:power_init: working_voltage_raw = 1800 2021-03-14 08:22:48:power_api.c:263:power_init: higher_voltage_raw = 1850 2021-03-14 08:22:48:power_api.c:264:power_init: check_asic_voltage_raw = 1800 2021-03-14 08:22:48:driver-btm-api.c:2354:bitmain_board_init: Enter 60s sleep to make sure power release finish. 2021-03-14 08:23:50:driver-btm-api.c:1123:check_asic_number_until_volt_balance: THIS is No.1 time boost asic: 2021-03-14 08:23:50:power_api.c:334:modify_check_asic_voltage: check_asic_voltage_raw = 1800 2021-03-14 08:23:53:power_api.c:298:set_to_check_asic_voltage_by_steps: Set to voltage raw 1800, step by step. 2021-03-14 08:24:14:uart.c:69:set_baud: set UART baud to 115200 chain 0, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x 7777777 2021-03-14 08:24:19: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 2021-03-14 08:24:23:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 0 2021-03-14 08:24:24:board.c:81:jump_and_app_check_restore_pic: chain[1] PIC jump to app 2021-03-14 08:24:26:board.c:94:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88 2021-03-14 08:24:26:power_api.c:334:modify_check_asic_voltage: check_asic_voltage_raw = 1900 2021-03-14 08:24:26: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 2021-03-14 08:24:44:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 1 2021-03-14 08:24:45:board.c:81:jump_and_app_check_restore_pic: chain[1] PIC jump to app 2021-03-14 08:24:47:board.c:94:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88 2021-03-14 08:24:47:power_api.c:334:modify_check_asic_voltage: check_asic_voltage_raw = 2000 2021-03-14 08:24:47: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 2021-03-14 08:25:05:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 2 2021-03-14 08:25:07:board.c:81:jump_and_app_check_restore_pic: chain[1] PIC jump to app 2021-03-14 08:25:09:board.c:94:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88 2021-03-14 08:25:09:power_api.c:334:modify_check_asic_voltage: check_asic_voltage_raw = 2100 2021-03-14 08:25:09: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 2021-03-14 08:25:25:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 3 2021-03-14 08:25:27:board.c:81:jump_and_app_check_restore_pic: chain[1] PIC jump to app 2021-03-14 08:25:29:board.c:94:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88 2021-03-14 08:25:29:power_api.c:334:modify_check_asic_voltage: check_asic_voltage_raw = 1800 2021-03-14 08:25:29:power_api.c:298:set_to_check_asic_voltage_by_steps: Set to voltage raw 1800, step by step. 2021-03-14 08:25:49: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 2021-03-14 08:25:54:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 0 2021-03-14 08:25:55:board.c:81:jump_and_app_check_restore_pic: chain[2] PIC jump to app 2021-03-14 08:25:57:board.c:94:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88 2021-03-14 08:25:57:power_api.c:334:modify_check_asic_voltage: check_asic_voltage_raw = 1900 2021-03-14 08:25:57: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 2021-03-14 08:26:11:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 1 2021-03-14 08:26:12:board.c:81:jump_and_app_check_restore_pic: chain[2] PIC jump to app 2021-03-14 08:26:14:board.c:94:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88 2021-03-14 08:26:14:power_api.c:334:modify_check_asic_voltage: check_asic_voltage_raw = 2000 2021-03-14 08:26:14: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 2021-03-14 08:26:29:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 2 2021-03-14 08:26:30:board.c:81:jump_and_app_check_restore_pic: chain[2] PIC jump to app 2021-03-14 08:26:32:board.c:94:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88 2021-03-14 08:26:32:power_api.c:334:modify_check_asic_voltage: check_asic_voltage_raw = 2100 2021-03-14 08:26:32: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 2021-03-14 08:26:46:driver-btm-api.c:1035:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 3 2021-03-14 08:26:47:board.c:81:jump_and_app_check_restore_pic: chain[2] PIC jump to app 2021-03-14 08:26:49:board.c:94:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88 2021-03-14 08:26:49:power_api.c:334:modify_check_asic_voltage: check_asic_voltage_raw = 1800 2021-03-14 08:26:49:power_api.c:298:set_to_check_asic_voltage_by_steps: Set to voltage raw 1800, step by step. 2021-03-14 08:27:07:driver-btm-api.c:1217:check_asic_number: Chain 2 only find 0 asic, will power off hash board 2 2021-03-14 08:27:08:driver-btm-api.c:1163:check_asic_number_until_volt_balance: PASS: volt balance at No.1 time boost asic. 2021-03-14 08:27:08:power_api.c:364:set_to_highest_voltage_by_steps: Set to voltage raw 2000, step by step. 2021-03-14 08:27:22:driver-hash-chip.c:876:set_uart_relay: set uart relay to 0x330003 2021-03-14 08:27:22:driver-hash-chip.c:1264:set_ldo_ctrl: Set LDO to 0x2000203 2021-03-14 08:27:23:driver-hash-chip.c:717:dump_adc_voltage_v2: chain 0 domain 03 core_domain 3: range too wide 1.496704 ~ 1.607300 = 0.110596 2021-03-14 08:27:23: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.392, d1 0.400, d2 0.380, d3 0.390, sum = 1.561523 chain 0 domain 1: d0 0.380, d1 0.379, d2 0.392, d3 0.374, sum = 1.525208 chain 0 domain 2: d0 0.380, d1 0.380, d2 0.369, d3 0.367, sum = 1.495483 chain 0 domain 3: d0 0.391, d1 0.388, d2 0.389, d3 0.386, sum = 1.553223 chain 0 domain 4: d0 0.384, d1 0.379, d2 0.389, d3 0.380, sum = 1.530701 chain 0 domain 5: d0 0.404, d1 0.398, d2 0.391, d3 0.398, sum = 1.590515 chain 0 domain 6: d0 0.377, d1 0.381, d2 0.375, d3 0.361, sum = 1.494934 chain 0 domain 7: d0 0.372, d1 0.367, d2 0.380, d3 0.366, sum = 1.484985 chain 0 domain 8: d0 0.371, d1 0.364, d2 0.377, d3 0.360, sum = 1.471252 chain 0 domain 9: d0 0.384, d1 0.384, d2 0.370, d3 0.365, sum = 1.502380 chain 0 domain 10: d0 0.376, d1 0.375, d2 0.375, d3 0.367, sum = 1.494141 chain 0 domain 11: d0 0.377, d1 0.368, d2 0.366, d3 0.373, sum = 1.483948 chain 0 domain 12: d0 0.366, d1 0.368, d2 0.366, d3 0.366, sum = 1.466309 chain 0 domain 00 core_domain 0: 0.392 0.000 -0.002 0.001 0.001 0.001 chain 0 domain 00 core_domain 1: 0.791 0.002 -0.003 0.003 -0.002 0.002 chain 0 domain 00 core_domain 2: 1.169 0.004 -0.005 0.005 -0.001 0.004 chain 0 domain 00 core_domain 3: 1.559 0.005 -0.007 0.007 -0.002 0.005 chain 0 domain 01 core_domain 0: 0.380 -0.001 0.000 0.001 0.001 -0.002 chain 0 domain 01 core_domain 1: 0.766 -0.010 -0.000 0.001 0.003 -0.003 chain 0 domain 01 core_domain 2: 1.140 0.011 -0.000 0.003 0.005 -0.005 chain 0 domain 01 core_domain 3: 1.498 0.036 -0.036 0.038 0.007 -0.006 chain 0 domain 02 core_domain 0: 0.375 0.005 0.001 0.000 -0.001 0.000 chain 0 domain 02 core_domain 1: 0.748 0.014 0.001 0.001 -0.002 0.001 chain 0 domain 02 core_domain 2: 1.139 -0.011 0.000 -0.001 -0.003 0.001 chain 0 domain 02 core_domain 3: 1.495 0.002 -0.001 -0.000 -0.001 0.000 chain 0 domain 03 core_domain 0: 0.383 0.001 0.003 -0.002 0.019 -0.001 chain 0 domain 03 core_domain 1: 0.761 0.006 0.003 -0.003 0.040 -0.003 chain 0 domain 03 core_domain 2: 1.138 0.015 0.004 -0.006 0.055 -0.005 chain 0 domain 03 core_domain 3: 1.497 0.040 0.006 -0.008 0.073 -0.006 chain 0 domain 04 core_domain 0: 0.379 0.007 -0.001 -0.000 0.000 0.000 chain 0 domain 04 core_domain 1: 0.765 -0.001 -0.002 -0.002 0.001 0.002 chain 0 domain 04 core_domain 2: 1.142 0.014 -0.004 -0.002 0.001 0.002 chain 0 domain 04 core_domain 3: 1.498 0.044 -0.005 -0.003 0.002 0.003 chain 0 domain 05 core_domain 0: 0.399 0.006 -0.001 0.002 -0.002 0.002 chain 0 domain 05 core_domain 1: 0.794 0.010 -0.003 0.004 -0.004 0.003 chain 0 domain 05 core_domain 2: 1.198 -0.007 -0.002 0.006 -0.004 0.004 chain 0 domain 05 core_domain 3: 1.597 -0.009 -0.003 0.008 -0.006 0.005 chain 0 domain 06 core_domain 0: 0.380 -0.003 -0.001 0.000 -0.000 0.001 chain 0 domain 06 core_domain 1: 0.755 0.005 -0.003 0.001 0.001 0.000 chain 0 domain 06 core_domain 2: 1.142 -0.008 -0.004 0.001 0.000 0.000 chain 0 domain 06 core_domain 3: 1.499 -0.004 -0.001 0.000 -0.000 0.000 chain 0 domain 07 core_domain 0: 0.376 -0.004 -0.001 0.002 -0.003 0.001 chain 0 domain 07 core_domain 1: 0.743 -0.004 -0.004 0.005 -0.003 0.001 chain 0 domain 07 core_domain 2: 1.102 0.022 -0.005 0.005 -0.004 0.003 chain 0 domain 07 core_domain 3: 1.480 0.009 -0.007 0.007 -0.007 0.004 chain 0 domain 08 core_domain 0: 0.367 0.006 -0.001 0.001 -0.003 0.002 chain 0 domain 08 core_domain 1: 0.733 0.002 -0.001 0.002 -0.003 0.001 chain 0 domain 08 core_domain 2: 1.107 0.005 -0.002 0.004 -0.003 0.002 chain 0 domain 08 core_domain 3: 1.462 0.011 -0.002 0.005 -0.004 0.001 chain 0 domain 09 core_domain 0: 0.386 -0.003 0.001 0.000 -0.003 0.001 chain 0 domain 09 core_domain 1: 0.760 0.007 0.003 0.001 -0.005 0.003 chain 0 domain 09 core_domain 2: 1.148 -0.016 0.006 0.002 -0.007 0.004 chain 0 domain 09 core_domain 3: 1.531 -0.035 0.002 0.000 -0.002 0.000 chain 0 domain 10 core_domain 0: 0.379 -0.002 -0.001 0.000 -0.001 0.000 chain 0 domain 10 core_domain 1: 0.760 -0.009 -0.001 0.001 -0.003 0.001 chain 0 domain 10 core_domain 2: 1.141 -0.017 -0.001 0.001 -0.003 0.004 chain 0 domain 10 core_domain 3: 1.496 -0.002 -0.001 0.001 -0.001 0.001 chain 0 domain 11 core_domain 0: 0.373 0.005 -0.001 -0.000 -0.000 0.001 chain 0 domain 11 core_domain 1: 0.746 -0.001 -0.001 0.001 -0.001 0.001 chain 0 domain 11 core_domain 2: 1.123 -0.015 -0.001 0.001 -0.001 0.002 chain 0 domain 11 core_domain 3: 1.484 0.001 -0.002 0.002 -0.001 0.002 chain 0 domain 12 core_domain 0: 0.365 0.002 -0.001 0.000 -0.001 0.001 chain 0 domain 12 core_domain 1: 0.733 0.001 0.001 0.000 -0.001 0.001 chain 0 domain 12 core_domain 2: 1.099 0.000 0.001 0.001 -0.001 0.002 chain 0 domain 12 core_domain 3: 1.466 -0.001 0.001 0.001 -0.001 0.002 2021-03-14 08:27:23:driver-hash-chip.c:493:check_adc_voltage: PASS domainn volt check: request 0.800 (index 0, open_core) 2021-03-14 08:27:25:temperature.c:272:calibrate_temp_sensor_one_chain: chain 0 temp sensor TMP451 2021-03-14 08:27:30:driver-btm-api.c:311:check_bringup_temp: Bring up temperature is 19 2021-03-14 08:27:30:uart.c:69:set_baud: set UART baud to 3000000 2021-03-14 08:27:30 voltage[0] = 1840 2021-03-14 08:27:31:power_api.c:272:set_working_voltage_raw: working_voltage_raw = 1840 2021-03-14 08:27:31:thread.c:1538:create_check_miner_status_thread: create thread 2021-03-14 08:27:31:thread.c:1528:create_show_miner_status_thread: create thread 2021-03-14 08:27:31:thread.c:1503:create_temperature_monitor_thread: create thread 2021-03-14 08:27:31:thread.c:1580:create_fan_monitor_thread: create thread 2021-03-14 08:27:31:frequency.c:578:inc_freq_with_fixed_vco: chain = 255, freq = 615, is_higher_voltage = true 2021-03-14 08:27:37:frequency.c:623:inc_freq_with_fixed_vco: get pcb 19 ~ 21, chip_temp 24 ~ 26, now 6.0s, target 27.0 2021-03-14 08:27:38:frequency.c:623:inc_freq_with_fixed_vco: get pcb 20 ~ 21, chip_temp 24 ~ 26, now 7.0s, target 27.2 2021-03-14 08:27:39:frequency.c:623:inc_freq_with_fixed_vco: get pcb 20 ~ 21, chip_temp 24 ~ 26, now 8.0s, target 27.3 2021-03-14 08:27:40:frequency.c:623:inc_freq_with_fixed_vco: get pcb 20 ~ 21, chip_temp 24 ~ 27, now 9.0s, target 27.5 2021-03-14 08:27:41:frequency.c:623:inc_freq_with_fixed_vco: get pcb 20 ~ 21, chip_temp 24 ~ 27, now 10.0s, target 27.7 2021-03-14 08:27:42:frequency.c:623:inc_freq_with_fixed_vco: get pcb 20 ~ 21, chip_temp 24 ~ 27, now 11.0s, target 27.8 2021-03-14 08:27:43:frequency.c:623:inc_freq_with_fixed_vco: get pcb 20 ~ 21, chip_temp 24 ~ 27, now 12.0s, target 28.0 2021-03-14 08:27:44:frequency.c:623:inc_freq_with_fixed_vco: get pcb 20 ~ 21, chip_temp 24 ~ 27, now 13.0s, target 28.2 2021-03-14 08:27:45:frequency.c:623:inc_freq_with_fixed_vco: get pcb 20 ~ 21, chip_temp 25 ~ 27, now 14.0s, target 28.3 2021-03-14 08:27:46:frequency.c:623:inc_freq_with_fixed_vco: get pcb 20 ~ 21, chip_temp 25 ~ 27, now 15.0s, target 28.5 2021-03-14 08:27:47:frequency.c:623:inc_freq_with_fixed_vco: get pcb 20 ~ 21, chip_temp 25 ~ 27, now 16.0s, target 28.7 2021-03-14 08:27:48:frequency.c:623:inc_freq_with_fixed_vco: get pcb 20 ~ 21, chip_temp 25 ~ 27, now 17.0s, target 28.8 2021-03-14 08:27:49:frequency.c:623:inc_freq_with_fixed_vco: get pcb 20 ~ 21, chip_temp 25 ~ 28, now 18.0s, target 29.0 2021-03-14 08:27:50:frequency.c:623:inc_freq_with_fixed_vco: get pcb 20 ~ 21, chip_temp 25 ~ 28, now 19.0s, target 29.2 2021-03-14 08:27:51:frequency.c:623:inc_freq_with_fixed_vco: get pcb 20 ~ 22, chip_temp 25 ~ 28, now 20.0s, target 29.3 2021-03-14 08:27:52:frequency.c:623:inc_freq_with_fixed_vco: get pcb 20 ~ 22, chip_temp 25 ~ 28, now 21.0s, target 29.5 2021-03-14 08:27:53:frequency.c:623:inc_freq_with_fixed_vco: get pcb 21 ~ 22, chip_temp 25 ~ 28, now 22.0s, target 29.7 2021-03-14 08:27:54:frequency.c:623:inc_freq_with_fixed_vco: get pcb 21 ~ 22, chip_temp 26 ~ 28, now 23.0s, target 29.8 2021-03-14 08:27:55:frequency.c:623:inc_freq_with_fixed_vco: get pcb 21 ~ 22, chip_temp 26 ~ 28, now 24.0s, target 30.0 2021-03-14 08:27:55:frequency.c:657:inc_freq_with_fixed_vco: [0] _POSTDIV1 = 7, _POSTDIV2 = 7, USER_DIV = 1, freq = 62 2021-03-14 08:27:55:frequency.c:665:inc_freq_with_fixed_vco: set to 62M, get pcb 21 ~ 22, chip_temp 26 ~ 28 2021-03-14 08:27:55:power_api.c:376:set_to_voltage_by_steps: Set to voltage raw 2100, step by step. 2021-03-14 08:28:03:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0 2021-03-14 08:28:03:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 62 clock_counter_limit 6, no check, skip. 2021-03-14 08:28:11:frequency.c:623:inc_freq_with_fixed_vco: get pcb 22 ~ 24, chip_temp 28 ~ 30, now 40.4s, target 32.7 2021-03-14 08:28:11:frequency.c:657:inc_freq_with_fixed_vco: [1] _POSTDIV1 = 7, _POSTDIV2 = 6, USER_DIV = 1, freq = 73 2021-03-14 08:28:11:frequency.c:665:inc_freq_with_fixed_vco: set to 73M, get pcb 22 ~ 24, chip_temp 28 ~ 30 2021-03-14 08:28:11:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0 2021-03-14 08:28:11:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 73 clock_counter_limit 8, no check, skip. 2021-03-14 08:28:19:frequency.c:623:inc_freq_with_fixed_vco: get pcb 22 ~ 25, chip_temp 29 ~ 32, now 48.4s, target 34.1 2021-03-14 08:28:19:frequency.c:657:inc_freq_with_fixed_vco: [2] _POSTDIV1 = 6, _POSTDIV2 = 6, USER_DIV = 1, freq = 85 2021-03-14 08:28:19:frequency.c:665:inc_freq_with_fixed_vco: set to 85M, get pcb 22 ~ 25, chip_temp 29 ~ 32 2021-03-14 08:28:19:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0 2021-03-14 08:28:19:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 85 clock_counter_limit 10, no check, skip. 2021-03-14 08:28:27:frequency.c:623:inc_freq_with_fixed_vco: get pcb 23 ~ 26, chip_temp 31 ~ 33, now 56.4s, target 35.4 2021-03-14 08:28:27:frequency.c:657:inc_freq_with_fixed_vco: [3] _POSTDIV1 = 7, _POSTDIV2 = 5, USER_DIV = 1, freq = 87 2021-03-14 08:28:27:frequency.c:665:inc_freq_with_fixed_vco: set to 87M, get pcb 23 ~ 26, chip_temp 31 ~ 33 2021-03-14 08:28:27:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0 2021-03-14 08:28:27:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 87 clock_counter_limit 10, no check, skip. 2021-03-14 08:28:35:frequency.c:623:inc_freq_with_fixed_vco: get pcb 23 ~ 27, chip_temp 32 ~ 34, now 64.4s, target 36.7 2021-03-14 08:28:35:frequency.c:657:inc_freq_with_fixed_vco: [4] _POSTDIV1 = 6, _POSTDIV2 = 5, USER_DIV = 1, freq = 102 2021-03-14 08:28:35:frequency.c:665:inc_freq_with_fixed_vco: set to 102M, get pcb 23 ~ 27, chip_temp 32 ~ 34 2021-03-14 08:28:35:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0 2021-03-14 08:28:35:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 102 clock_counter_limit 13, no check, skip. 2021-03-14 08:28:43:frequency.c:623:inc_freq_with_fixed_vco: get pcb 24 ~ 28, chip_temp 34 ~ 35, now 72.4s, target 38.1 2021-03-14 08:28:43:frequency.c:657:inc_freq_with_fixed_vco: [5] _POSTDIV1 = 7, _POSTDIV2 = 4, USER_DIV = 1, freq = 109 2021-03-14 08:28:43:frequency.c:665:inc_freq_with_fixed_vco: set to 109M, get pcb 24 ~ 28, chip_temp 34 ~ 35 2021-03-14 08:28:43:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0 2021-03-14 08:28:43:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 109 clock_counter_limit 14, no check, skip. 2021-03-14 08:28:51:frequency.c:623:inc_freq_with_fixed_vco: get pcb 24 ~ 29, chip_temp 35 ~ 37, now 80.4s, target 39.4 2021-03-14 08:28:51:frequency.c:657:inc_freq_with_fixed_vco: [6] _POSTDIV1 = 5, _POSTDIV2 = 5, USER_DIV = 1, freq = 123 2021-03-14 08:28:51:frequency.c:665:inc_freq_with_fixed_vco: set to 123M, get pcb 24 ~ 29, chip_temp 35 ~ 37 2021-03-14 08:28:51:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0 2021-03-14 08:28:51:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 123 clock_counter_limit 16, no check, skip. 2021-03-14 08:28:59:frequency.c:623:inc_freq_with_fixed_vco: get pcb 25 ~ 30, chip_temp 37 ~ 38, now 88.4s, target 40.7 2021-03-14 08:28:59:frequency.c:657:inc_freq_with_fixed_vco: [7] _POSTDIV1 = 6, _POSTDIV2 = 4, USER_DIV = 1, freq = 128 2021-03-14 08:28:59:frequency.c:665:inc_freq_with_fixed_vco: set to 128M, get pcb 25 ~ 30, chip_temp 37 ~ 38 2021-03-14 08:28:59:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0 2021-03-14 08:28:59:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 128 clock_counter_limit 17, no check, skip. 2021-03-14 08:29:07:frequency.c:623:inc_freq_with_fixed_vco: get pcb 25 ~ 32, chip_temp 38 ~ 40, now 96.4s, target 42.1 2021-03-14 08:29:07:frequency.c:657:inc_freq_with_fixed_vco: [8] _POSTDIV1 = 7, _POSTDIV2 = 3, USER_DIV = 1, freq = 146 2021-03-14 08:29:07:frequency.c:665:inc_freq_with_fixed_vco: set to 146M, get pcb 25 ~ 32, chip_temp 38 ~ 40 2021-03-14 08:29:07:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0 2021-03-14 08:29:07:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 146 clock_counter_limit 20, no check, skip. 2021-03-14 08:29:15:frequency.c:623:inc_freq_with_fixed_vco: get pcb 26 ~ 33, chip_temp 40 ~ 42, now 104.4s, target 43.4 2021-03-14 08:29:16:frequency.c:623:inc_freq_with_fixed_vco: get pcb 26 ~ 33, chip_temp 40 ~ 42, now 105.4s, target 43.6 2021-03-14 08:29:17:frequency.c:623:inc_freq_with_fixed_vco: get pcb 26 ~ 34, chip_temp 40 ~ 43, now 106.4s, target 43.7 2021-03-14 08:29:18:frequency.c:623:inc_freq_with_fixed_vco: get pcb 26 ~ 34, chip_temp 40 ~ 43, now 107.4s, target 43.9 2021-03-14 08:29:19:frequency.c:623:inc_freq_with_fixed_vco: get pcb 26 ~ 34, chip_temp 40 ~ 43, now 108.4s, target 44.1 2021-03-14 08:29:20:frequency.c:623:inc_freq_with_fixed_vco: get pcb 26 ~ 34, chip_temp 40 ~ 43, now 109.4s, target 44.2 2021-03-14 08:29:21:frequency.c:623:inc_freq_with_fixed_vco: get pcb 26 ~ 34, chip_temp 40 ~ 44, now 110.5s, target 44.4 2021-03-14 08:29:22:frequency.c:623:inc_freq_with_fixed_vco: get pcb 26 ~ 35, chip_temp 40 ~ 44, now 111.5s, target 44.6 2021-03-14 08:29:23:frequency.c:623:inc_freq_with_fixed_vco: get pcb 27 ~ 35, chip_temp 41 ~ 44, now 112.5s, target 44.7 2021-03-14 08:29:24:frequency.c:623:inc_freq_with_fixed_vco: get pcb 27 ~ 35, chip_temp 41 ~ 44, now 113.5s, target 44.9 2021-03-14 08:29:25:frequency.c:623:inc_freq_with_fixed_vco: get pcb 27 ~ 35, chip_temp 41 ~ 45, now 114.5s, target 45.1 2021-03-14 08:29:26:frequency.c:623:inc_freq_with_fixed_vco: get pcb 27 ~ 35, chip_temp 41 ~ 45, now 115.5s, target 45.2 2021-03-14 08:29:27:frequency.c:623:inc_freq_with_fixed_vco: get pcb 27 ~ 35, chip_temp 41 ~ 45, now 116.5s, target 45.4 2021-03-14 08:29:28:frequency.c:623:inc_freq_with_fixed_vco: get pcb 27 ~ 36, chip_temp 41 ~ 45, now 117.5s, target 45.6 2021-03-14 08:29:29:frequency.c:623:inc_freq_with_fixed_vco: get pcb 27 ~ 36, chip_temp 41 ~ 45, now 118.5s, target 45.7 2021-03-14 08:29:30:frequency.c:623:inc_freq_with_fixed_vco: get pcb 27 ~ 36, chip_temp 41 ~ 46, now 119.5s, target 45.9 2021-03-14 08:29:30:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 46 > 45.9 target_temp. 2021-03-14 08:29:36:frequency.c:623:inc_freq_with_fixed_vco: get pcb 27 ~ 37, chip_temp 42 ~ 47, now 125.5s, target 46.9 2021-03-14 08:29:36:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 47 > 46.9 target_temp. 2021-03-14 08:29:42:frequency.c:623:inc_freq_with_fixed_vco: get pcb 28 ~ 38, chip_temp 42 ~ 48, now 131.5s, target 47.9 2021-03-14 08:29:42:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 48 > 47.9 target_temp. 2021-03-14 08:29:48:frequency.c:623:inc_freq_with_fixed_vco: get pcb 28 ~ 39, chip_temp 42 ~ 50, now 137.5s, target 48.9 2021-03-14 08:29:48:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 50 > 48.9 target_temp. 2021-03-14 08:29:54:frequency.c:623:inc_freq_with_fixed_vco: get pcb 28 ~ 40, chip_temp 42 ~ 50, now 143.5s, target 49.9 2021-03-14 08:29:54:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 50 > 49.9 target_temp. 2021-03-14 08:30:00:frequency.c:623:inc_freq_with_fixed_vco: get pcb 28 ~ 41, chip_temp 42 ~ 51, now 149.5s, target 50.9 2021-03-14 08:30:00:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 51 > 50.9 target_temp. 2021-03-14 08:30:06:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 42, chip_temp 43 ~ 53, now 155.5s, target 51.9 2021-03-14 08:30:06:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 53 > 51.9 target_temp. 2021-03-14 08:30:12:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 43, chip_temp 42 ~ 54, now 161.5s, target 52.9 2021-03-14 08:30:12:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 54 > 52.9 target_temp. 2021-03-14 08:30:18:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 44, chip_temp 43 ~ 55, now 167.5s, target 53.9 2021-03-14 08:30:18:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 55 > 53.9 target_temp. 2021-03-14 08:30:24:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 45, chip_temp 43 ~ 55, now 173.5s, target 54.9 2021-03-14 08:30:24:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 55 > 54.9 target_temp. 2021-03-14 08:30:30:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 45, chip_temp 43 ~ 56, now 179.5s, target 55.9 2021-03-14 08:30:30:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 56 > 55.9 target_temp. 2021-03-14 08:30:36:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 46, chip_temp 43 ~ 57, now 185.5s, target 56.9 2021-03-14 08:30:36:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 57 > 56.9 target_temp. 2021-03-14 08:30:42:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 47, chip_temp 43 ~ 58, now 191.5s, target 57.9 2021-03-14 08:30:42:frequency.c:644:inc_freq_with_fixed_vco: heat speed too fast! current_temp 58 > 57.9 target_temp. 2021-03-14 08:30:48:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 47, chip_temp 43 ~ 58, now 197.5s, target 58.9 2021-03-14 08:30:49:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 48, chip_temp 43 ~ 58, now 198.5s, target 59.1 2021-03-14 08:30:50:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 48, chip_temp 43 ~ 59, now 199.5s, target 59.2 2021-03-14 08:30:51:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 48, chip_temp 43 ~ 59, now 200.5s, target 59.4 2021-03-14 08:30:52:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 48, chip_temp 43 ~ 59, now 201.5s, target 59.6 2021-03-14 08:30:53:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 48, chip_temp 43 ~ 59, now 202.5s, target 59.7 2021-03-14 08:30:54:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 48, chip_temp 43 ~ 59, now 203.5s, target 59.9 2021-03-14 08:30:55:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 48, chip_temp 43 ~ 59, now 204.5s, target 60.1 2021-03-14 08:30:56:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 48, chip_temp 43 ~ 59, now 205.5s, target 60.2 2021-03-14 08:30:57:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 48, chip_temp 43 ~ 59, now 206.5s, target 60.4 2021-03-14 08:30:58:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 48, chip_temp 43 ~ 59, now 207.5s, target 60.6 2021-03-14 08:30:59:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 48, chip_temp 43 ~ 59, now 208.5s, target 60.8 2021-03-14 08:31:00:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 48, chip_temp 43 ~ 59, now 209.5s, target 60.9 2021-03-14 08:31:01:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 49, chip_temp 43 ~ 60, now 210.5s, target 61.1 2021-03-14 08:31:02:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 49, chip_temp 43 ~ 60, now 211.5s, target 61.3 2021-03-14 08:31:03:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 49, chip_temp 43 ~ 60, now 212.5s, target 61.4 2021-03-14 08:31:04:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 49, chip_temp 43 ~ 60, now 213.5s, target 61.6 2021-03-14 08:31:05:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 49, chip_temp 43 ~ 60, now 214.5s, target 61.8 2021-03-14 08:31:06:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 49, chip_temp 43 ~ 60, now 215.5s, target 61.9 2021-03-14 08:31:07:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 49, chip_temp 43 ~ 60, now 216.5s, target 62.1 2021-03-14 08:31:07:frequency.c:657:inc_freq_with_fixed_vco: [9] _POSTDIV1 = 5, _POSTDIV2 = 4, USER_DIV = 1, freq = 153 2021-03-14 08:31:07:frequency.c:665:inc_freq_with_fixed_vco: set to 153M, get pcb 29 ~ 49, chip_temp 43 ~ 60 2021-03-14 08:31:07:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0 2021-03-14 08:31:07:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 153 clock_counter_limit 21, no check, skip. 2021-03-14 08:31:15:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 49, chip_temp 43 ~ 61, now 224.5s, target 63.4 2021-03-14 08:31:15:frequency.c:657:inc_freq_with_fixed_vco: [10] _POSTDIV1 = 6, _POSTDIV2 = 3, USER_DIV = 1, freq = 170 2021-03-14 08:31:15:frequency.c:665:inc_freq_with_fixed_vco: set to 170M, get pcb 29 ~ 49, chip_temp 43 ~ 61 2021-03-14 08:31:15:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0 2021-03-14 08:31:15:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 170 clock_counter_limit 24, no check, skip. 2021-03-14 08:31:23:frequency.c:623:inc_freq_with_fixed_vco: get pcb 30 ~ 50, chip_temp 44 ~ 62, now 232.5s, target 64.8 2021-03-14 08:31:23:frequency.c:657:inc_freq_with_fixed_vco: [11] _POSTDIV1 = 5, _POSTDIV2 = 3, USER_DIV = 1, freq = 205 2021-03-14 08:31:23:frequency.c:665:inc_freq_with_fixed_vco: set to 205M, get pcb 30 ~ 50, chip_temp 44 ~ 62 2021-03-14 08:31:23:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0 2021-03-14 08:31:23:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 205 clock_counter_limit 29, no check, skip. 2021-03-14 08:31:31:frequency.c:623:inc_freq_with_fixed_vco: get pcb 30 ~ 51, chip_temp 46 ~ 64, now 240.5s, target 66.1 2021-03-14 08:31:31:frequency.c:657:inc_freq_with_fixed_vco: [12] _POSTDIV1 = 7, _POSTDIV2 = 2, USER_DIV = 1, freq = 219 2021-03-14 08:31:31:frequency.c:665:inc_freq_with_fixed_vco: set to 219M, get pcb 30 ~ 51, chip_temp 46 ~ 64 2021-03-14 08:31:31:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0 2021-03-14 08:31:31:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 219 clock_counter_limit 32, no check, skip. 2021-03-14 08:31:39:frequency.c:623:inc_freq_with_fixed_vco: get pcb 30 ~ 51, chip_temp 47 ~ 64, now 248.5s, target 67.4 2021-03-14 08:31:39:frequency.c:657:inc_freq_with_fixed_vco: [13] _POSTDIV1 = 6, _POSTDIV2 = 2, USER_DIV = 1, freq = 256 2021-03-14 08:31:39:frequency.c:665:inc_freq_with_fixed_vco: set to 256M, get pcb 30 ~ 51, chip_temp 47 ~ 64 2021-03-14 08:31:39:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0 2021-03-14 08:31:39:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 256 clock_counter_limit 37, no check, skip. 2021-03-14 08:31:47:frequency.c:623:inc_freq_with_fixed_vco: get pcb 30 ~ 51, chip_temp 49 ~ 65, now 256.5s, target 68.8 2021-03-14 08:31:47:frequency.c:657:inc_freq_with_fixed_vco: [14] _POSTDIV1 = 5, _POSTDIV2 = 2, USER_DIV = 1, freq = 307 2021-03-14 08:31:47:frequency.c:665:inc_freq_with_fixed_vco: set to 307M, get pcb 30 ~ 51, chip_temp 49 ~ 65 2021-03-14 08:31:47:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0 2021-03-14 08:31:47:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 307 clock_counter_limit 46, no check, skip. 2021-03-14 08:31:50: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.413, d1 0.408, d2 0.412, d3 0.411, sum = 1.643982 chain 0 domain 1: d0 0.409, d1 0.402, d2 0.404, d3 0.405, sum = 1.619568 chain 0 domain 2: d0 0.401, d1 0.395, d2 0.396, d3 0.397, sum = 1.589417 chain 0 domain 3: d0 0.403, d1 0.396, d2 0.396, d3 0.398, sum = 1.592224 chain 0 domain 4: d0 0.408, d1 0.401, d2 0.403, d3 0.404, sum = 1.615417 chain 0 domain 5: d0 0.411, d1 0.402, d2 0.407, d3 0.407, sum = 1.626709 chain 0 domain 6: d0 0.399, d1 0.396, d2 0.395, d3 0.396, sum = 1.586365 chain 0 domain 7: d0 0.400, d1 0.394, d2 0.392, d3 0.395, sum = 1.580566 chain 0 domain 8: d0 0.397, d1 0.393, d2 0.389, d3 0.393, sum = 1.571228 chain 0 domain 9: d0 0.400, d1 0.391, d2 0.391, d3 0.394, sum = 1.576538 chain 0 domain 10: d0 0.399, d1 0.393, d2 0.393, d3 0.395, sum = 1.579773 chain 0 domain 11: d0 0.395, d1 0.385, d2 0.383, d3 0.388, sum = 1.551575 chain 0 domain 12: d0 0.392, d1 0.388, d2 0.388, d3 0.389, sum = 1.556519 2021-03-14 08:31:50:driver-hash-chip.c:493:check_adc_voltage: PASS domainn volt check: request 0.800 (index 0, open_core) 2021-03-14 08:31:56:frequency.c:623:inc_freq_with_fixed_vco: get pcb 30 ~ 51, chip_temp 51 ~ 66, now 265.2s, target 70.2 2021-03-14 08:31:56:frequency.c:657:inc_freq_with_fixed_vco: [15] _POSTDIV1 = 7, _POSTDIV2 = 1, USER_DIV = 1, freq = 439 2021-03-14 08:31:56:frequency.c:665:inc_freq_with_fixed_vco: set to 439M, get pcb 30 ~ 51, chip_temp 51 ~ 66 2021-03-14 08:31:56:power_api.c:376:set_to_voltage_by_steps: Set to voltage raw 2070, step by step. 2021-03-14 08:32:01: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.407, d1 0.403, d2 0.404, d3 0.405, sum = 1.618958 chain 0 domain 1: d0 0.402, d1 0.398, d2 0.396, d3 0.399, sum = 1.594666 chain 0 domain 2: d0 0.396, d1 0.391, d2 0.390, d3 0.392, sum = 1.568726 chain 0 domain 3: d0 0.398, d1 0.390, d2 0.390, d3 0.393, sum = 1.571228 chain 0 domain 4: d0 0.401, d1 0.397, d2 0.396, d3 0.398, sum = 1.591492 chain 0 domain 5: d0 0.404, d1 0.401, d2 0.395, d3 0.400, sum = 1.600525 chain 0 domain 6: d0 0.394, d1 0.390, d2 0.388, d3 0.391, sum = 1.562561 chain 0 domain 7: d0 0.395, d1 0.387, d2 0.385, d3 0.389, sum = 1.555969 chain 0 domain 8: d0 0.391, d1 0.386, d2 0.383, d3 0.387, sum = 1.547546 chain 0 domain 9: d0 0.395, d1 0.386, d2 0.386, d3 0.389, sum = 1.556091 chain 0 domain 10: d0 0.393, d1 0.387, d2 0.388, d3 0.389, sum = 1.557739 chain 0 domain 11: d0 0.390, d1 0.380, d2 0.376, d3 0.351, sum = 1.497986 chain 0 domain 12: d0 0.385, d1 0.381, d2 0.381, d3 0.357, sum = 1.504333 2021-03-14 08:32:01:driver-hash-chip.c:493:check_adc_voltage: PASS domainn volt check: request 0.800 (index 0, open_core) 2021-03-14 08:32:01:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0 2021-03-14 08:32:01:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 439 clock_counter_limit 67, no check, skip. 2021-03-14 08:32:04: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.404, d1 0.400, d2 0.400, d3 0.401, sum = 1.605042 chain 0 domain 1: d0 0.402, d1 0.395, d2 0.396, d3 0.397, sum = 1.589417 chain 0 domain 2: d0 0.394, d1 0.389, d2 0.390, d3 0.391, sum = 1.564575 chain 0 domain 3: d0 0.397, d1 0.389, d2 0.390, d3 0.392, sum = 1.568115 chain 0 domain 4: d0 0.401, d1 0.395, d2 0.397, d3 0.397, sum = 1.589661 chain 0 domain 5: d0 0.403, d1 0.396, d2 0.395, d3 0.398, sum = 1.591309 chain 0 domain 6: d0 0.394, d1 0.390, d2 0.388, d3 0.390, sum = 1.561279 chain 0 domain 7: d0 0.395, d1 0.388, d2 0.388, d3 0.390, sum = 1.561035 chain 0 domain 8: d0 0.392, d1 0.387, d2 0.386, d3 0.388, sum = 1.552307 chain 0 domain 9: d0 0.395, d1 0.386, d2 0.387, d3 0.389, sum = 1.556396 chain 0 domain 10: d0 0.394, d1 0.388, d2 0.390, d3 0.390, sum = 1.562256 chain 0 domain 11: d0 0.389, d1 0.379, d2 0.377, d3 0.352, sum = 1.496826 chain 0 domain 12: d0 0.385, d1 0.381, d2 0.381, d3 0.352, sum = 1.498840 2021-03-14 08:32:04:driver-hash-chip.c:493:check_adc_voltage: PASS domainn volt check: request 0.800 (index 0, open_core) 2021-03-14 08:32:10:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 51, chip_temp 56 ~ 68, now 279.3s, target 72.5 2021-03-14 08:32:10:frequency.c:657:inc_freq_with_fixed_vco: [16] _POSTDIV1 = 6, _POSTDIV2 = 1, USER_DIV = 1, freq = 512 2021-03-14 08:32:10:frequency.c:665:inc_freq_with_fixed_vco: set to 512M, get pcb 29 ~ 51, chip_temp 56 ~ 68 2021-03-14 08:32:10:power_api.c:376:set_to_voltage_by_steps: Set to voltage raw 1980, step by step. 2021-03-14 08:32:17: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.386, d1 0.382, d2 0.384, d3 0.367, sum = 1.519165 chain 0 domain 1: d0 0.384, d1 0.379, d2 0.379, d3 0.360, sum = 1.502014 chain 0 domain 2: d0 0.378, d1 0.373, d2 0.374, d3 0.368, sum = 1.491882 chain 0 domain 3: d0 0.380, d1 0.374, d2 0.374, d3 0.364, sum = 1.491943 chain 0 domain 4: d0 0.384, d1 0.378, d2 0.380, d3 0.355, sum = 1.496948 chain 0 domain 5: d0 0.386, d1 0.378, d2 0.380, d3 0.353, sum = 1.496826 chain 0 domain 6: d0 0.376, d1 0.372, d2 0.373, d3 0.369, sum = 1.490295 chain 0 domain 7: d0 0.378, d1 0.371, d2 0.372, d3 0.368, sum = 1.489624 chain 0 domain 8: d0 0.375, d1 0.370, d2 0.369, d3 0.370, sum = 1.484070 chain 0 domain 9: d0 0.377, d1 0.371, d2 0.370, d3 0.369, sum = 1.487732 chain 0 domain 10: d0 0.377, d1 0.373, d2 0.373, d3 0.368, sum = 1.490295 chain 0 domain 11: d0 0.372, d1 0.363, d2 0.361, d3 0.362, sum = 1.458618 chain 0 domain 12: d0 0.367, d1 0.364, d2 0.364, d3 0.365, sum = 1.459534 2021-03-14 08:32:17:driver-hash-chip.c:493:check_adc_voltage: PASS domainn volt check: request 0.800 (index 0, open_core) 2021-03-14 08:32:17:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0 2021-03-14 08:32:17:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 512 clock_counter_limit 78, no check, skip. 2021-03-14 08:32:19: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.385, d1 0.382, d2 0.382, d3 0.367, sum = 1.515747 chain 0 domain 1: d0 0.384, d1 0.377, d2 0.379, d3 0.356, sum = 1.496704 chain 0 domain 2: d0 0.377, d1 0.372, d2 0.373, d3 0.369, sum = 1.491211 chain 0 domain 3: d0 0.380, d1 0.372, d2 0.374, d3 0.366, sum = 1.492126 chain 0 domain 4: d0 0.383, d1 0.380, d2 0.379, d3 0.355, sum = 1.496521 chain 0 domain 5: d0 0.385, d1 0.378, d2 0.379, d3 0.355, sum = 1.496582 chain 0 domain 6: d0 0.376, d1 0.372, d2 0.372, d3 0.370, sum = 1.490540 chain 0 domain 7: d0 0.378, d1 0.372, d2 0.372, d3 0.368, sum = 1.490356 chain 0 domain 8: d0 0.375, d1 0.371, d2 0.370, d3 0.370, sum = 1.485413 chain 0 domain 9: d0 0.377, d1 0.369, d2 0.372, d3 0.370, sum = 1.487366 chain 0 domain 10: d0 0.377, d1 0.372, d2 0.374, d3 0.368, sum = 1.490723 chain 0 domain 11: d0 0.371, d1 0.363, d2 0.362, d3 0.362, sum = 1.457458 chain 0 domain 12: d0 0.367, d1 0.363, d2 0.364, d3 0.365, sum = 1.458801 2021-03-14 08:32:20:driver-hash-chip.c:493:check_adc_voltage: PASS domainn volt check: request 0.800 (index 0, open_core) 2021-03-14 08:32:26:frequency.c:623:inc_freq_with_fixed_vco: get pcb 29 ~ 49, chip_temp 57 ~ 66, now 295.1s, target 75.2 2021-03-14 08:32:26:frequency.c:657:inc_freq_with_fixed_vco: [17] _POSTDIV1 = 5, _POSTDIV2 = 1, USER_DIV = 1, freq = 615 2021-03-14 08:32:26:frequency.c:665:inc_freq_with_fixed_vco: set to 615M, get pcb 29 ~ 49, chip_temp 57 ~ 66 2021-03-14 08:32:26:power_api.c:376:set_to_voltage_by_steps: Set to voltage raw 1910, step by step. 2021-03-14 08:32:33: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.371, d1 0.368, d2 0.370, d3 0.367, sum = 1.476318 chain 0 domain 1: d0 0.371, d1 0.365, d2 0.365, d3 0.367, sum = 1.467102 chain 0 domain 2: d0 0.363, d1 0.360, d2 0.361, d3 0.362, sum = 1.445557 chain 0 domain 3: d0 0.366, d1 0.360, d2 0.361, d3 0.363, sum = 1.450439 chain 0 domain 4: d0 0.370, d1 0.366, d2 0.365, d3 0.367, sum = 1.468201 chain 0 domain 5: d0 0.371, d1 0.366, d2 0.365, d3 0.366, sum = 1.468689 chain 0 domain 6: d0 0.363, d1 0.360, d2 0.360, d3 0.359, sum = 1.442444 chain 0 domain 7: d0 0.365, d1 0.359, d2 0.359, d3 0.359, sum = 1.442322 chain 0 domain 8: d0 0.361, d1 0.357, d2 0.356, d3 0.358, sum = 1.432434 chain 0 domain 9: d0 0.364, d1 0.356, d2 0.359, d3 0.360, sum = 1.438660 chain 0 domain 10: d0 0.364, d1 0.359, d2 0.360, d3 0.360, sum = 1.443237 chain 0 domain 11: d0 0.359, d1 0.351, d2 0.347, d3 0.349, sum = 1.406921 chain 0 domain 12: d0 0.353, d1 0.351, d2 0.350, d3 0.351, sum = 1.405457 2021-03-14 08:32:33:driver-hash-chip.c:493:check_adc_voltage: PASS domainn volt check: request 0.800 (index 0, open_core) 2021-03-14 08:32:33:frequency.c:671:inc_freq_with_fixed_vco: freq_mode 1=1 FREQ_MODE_USER, Conf.Check_Clock_Cnt=0 2021-03-14 08:32:33:driver-btm-api.c:1941:check_clock_counter_domain_last_core: freq 615 clock_counter_limit 95, no check, skip. 2021-03-14 08:32:35: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.370, d1 0.367, d2 0.367, d3 0.368, sum = 1.473145 chain 0 domain 1: d0 0.369, d1 0.364, d2 0.365, d3 0.364, sum = 1.462463 chain 0 domain 2: d0 0.363, d1 0.360, d2 0.359, d3 0.360, sum = 1.442383 chain 0 domain 3: d0 0.366, d1 0.360, d2 0.360, d3 0.361, sum = 1.446838 chain 0 domain 4: d0 0.369, d1 0.365, d2 0.366, d3 0.364, sum = 1.464722 chain 0 domain 5: d0 0.370, d1 0.364, d2 0.365, d3 0.365, sum = 1.465088 chain 0 domain 6: d0 0.363, d1 0.359, d2 0.359, d3 0.359, sum = 1.440674 chain 0 domain 7: d0 0.365, d1 0.359, d2 0.359, d3 0.359, sum = 1.441711 chain 0 domain 8: d0 0.361, d1 0.358, d2 0.357, d3 0.357, sum = 1.433594 chain 0 domain 9: d0 0.363, d1 0.357, d2 0.358, d3 0.358, sum = 1.436523 chain 0 domain 10: d0 0.364, d1 0.359, d2 0.360, d3 0.359, sum = 1.442261 chain 0 domain 11: d0 0.358, d1 0.349, d2 0.350, d3 0.345, sum = 1.402588 chain 0 domain 12: d0 0.353, d1 0.350, d2 0.351, d3 0.351, sum = 1.404968 2021-03-14 08:32:35:driver-hash-chip.c:493:check_adc_voltage: PASS domainn volt check: request 0.800 (index 0, open_core) 2021-03-14 08:32:35:driver-btm-api.c:666:set_timeout: freq = 615, percent = 90, hcn = 707788, timeout = 1150 2021-03-14 08:32:35:power_api.c:353:set_to_working_voltage_by_steps: Set to voltage raw 1840, step by step. 2021-03-14 08:32:42:thread.c:1533:create_check_system_status_thread: create thread 2021-03-14 08:32:42:thread.c:1508:create_asic_status_monitor_thread: create thread 2021-03-14 08:32:42:driver-btm-api.c:2599:bitmain_soc_init: Init done! 2021-03-14 08:32:47:driver-btm-api.c:247:set_miner_status: STATUS_OKAY 2021-03-14 08:32:48:frequency.c:107:get_ideal_hash_rate_GH: ideal_hash_rate = 18328 2021-03-14 08:32:48:frequency.c:128:get_sale_hash_rate_GH: sale_hash_rate = 16000 2021-03-14 08:32:51:driver-btm-api.c:1634:dhash_chip_send_job: Version num 8 2021-03-14 08:32:51:driver-btm-api.c:1778:dhash_chip_send_job: stime.tv_sec 1615710771, block_ntime 1615710769
This is the screenshot of the miner status: https://imgur.com/a/8lA9HcP Is it worth attempting some other actions (firmware, reset, etc?) Or, having two boards dead (and assuming it's not possible to repair them) what are the convenient alternatives? To mine with less hashrate, to buy some good working hasboard (but where?). Thanks.
Title: Re: Antminer T17e two hash boards not responding out of three.
Post by: mikeywith on March 14, 2021, 06:33:15 PM
Is it worth attempting some other actions (firmware, reset, etc?) Yes, it's worth trying custom firmware like Vnish, and of course, the freezer trick (https://bitcointalk.org/index.php?topic=5319411.msg56416650#msg56416650), the success rate on these tricks isn't all great, but since they cost you nothing, you lose nothing. Or, having two boards dead (and assuming it's not possible to repair them) what are the convenient alternatives?
It's possible to have them repaired (by someone else of course), check this topic (https://bitcointalk.org/index.php?topic=5297994.0) To mine with less hashrate
Yup, that's your last resort. to buy some good working hasboard (but where?).
Check on Zuesbtc, although I am sure if you find any, the price will be about 30% of the current price of the mining gear itself, and it could fail at any point, the failure rate on the 17 series gears is so high, I would advise against risking more money, if you can't have them fixed, don't replace them.
Title: Re: Antminer T17e two hash boards not responding out of three.
Post by: Svitakwilliam on March 16, 2021, 01:58:43 AM
Have the same issue with my t17. Bought used and 1 board went out. It was due to heat sinks falling off, but the issue was clear as I got a temp error on the board. Once I fixed the heat sinks that board was fine, but a second board had the 0 ASICS found issue. I pulled the board and it was date stamped for Jan, 2021. I also bought used so I don’t know where the stamp comes from, but the board had clearly been repaired by someone. I commented on a ZuesBTC video and they too thought that a chip may be the culprit. I reached out to bitmain and went through the standard troubleshooting procedures to no avail. They want me to send the board back to them to Hong Kong. Not sure if that’s worth it, but I’m looking into that option. Didn't see the boards for sale on the Zues website so not even sure if they have any available. Seems like this may not be an easy fix for a new miner and not sure if it’s worth spending money on a tester and all parts to replace a chip. If I decide to go the Bitmain route I’ll let you know my experience, but wanted to share as it seems like the board itself is the culprit. From a person that is used to fixing everything myself, not being able to make repairs or even find parts is very discouraging. I wanted to purchase a couple more t17’s, but now I’m afraid of coming across the same issues. Mining just doesn’t seem practical for the individual anymore.
Title: Re: Antminer T17e two hash boards not responding out of three.
Post by: fsofia on March 17, 2021, 06:44:55 PM
I tried a different official firmware but same result.
Also tried to ask ZeusBTC but they don't have spare hasboard. I'd like to test with some custom firmware but I cannot find one. I found some custom firmware for T17 but I'm not sure if it can suit the T17e.
Can anyone provide me a link to a custom link for T1te with clear instructions? Thanks.
Title: Re: Antminer T17e two hash boards not responding out of three.
Post by: mikeywith on March 18, 2021, 12:04:31 AM
Sadly, both BOs and Vnish have not finished the S17e and T17e firmware (they have been saying it's coming soon for a very long time) which probably means it's not coming at all, but thierry4wd has a modded (https://bitcointalk.org/index.php?topic=5264828.0) version, you might want to give it a try.
Title: Re: Antminer T17e two hash boards not responding out of three.
Post by: fsofia on March 18, 2021, 06:24:50 PM
It seems like he tested just on S17e and not T17e. Not sure if I can use it.
Update, I wanted to see the hashboard and this is the state: https://imgur.com/DKoCSA5 https://imgur.com/H4wRX28 https://imgur.com/bns8N3k I think they are broken and nothing can be done to fix or repair. Can anyone confirm that? Thanks.
Title: Re: Antminer T17e two hash boards not responding out of three.
Post by: mikeywith on March 18, 2021, 10:47:59 PM
I think they are broken and nothing can be done to fix or repair.
Can anyone confirm that?
They are beyond repair by the average person, you will need someone who has the skills as well as the tools to fix them, which isn't something you can easily find, where are you located? there might be a repair shop nearby, the worst-case scenario, you could just sell the hashboard as is to get back some of the money you spent. As for the firmware, the hardware damage negates the need for testing a different firmware, the chip has fallen off and no firmware on earth will make it work, sorry.
Title: Re: Antminer T17e two hash boards not responding out of three.
Post by: fsofia on March 19, 2021, 12:00:46 PM
I'm in Italy, so I look for some repair center possibly in European Union.
Title: Re: Antminer T17e two hash boards not responding out of three.
Post by: mikeywith on March 21, 2021, 12:48:56 AM
I'm in Italy, so I look for some repair center possibly in European Union.
The nearest which I know of would be either in Netherlands or Georgia, both locations are listed on Zeusbtc, please refer to this topic (https://bitcointalk.org/index.php?topic=5297994.0) under "Europe", you should also keep in mind that: While ZeusBtc is a trusted company with a great reputation, the repair centers displayed on their home page are not owned by them.
Good luck.
Title: Re: Antminer T17e two hash boards not responding out of three.
Post by: Tebykun on May 11, 2021, 08:19:44 PM
Hi, I’m experiencing the same problem with my T17e and I’m also from Italy. Did you found a solution?
|