New control board for s17pro not working.

[miner0069]

SO i changed password on s17pro and forgot it and couldnt use sd card to change it. so i got a new control board and now i can get into miner but wont connect or upgrade firmware, the last C.B. would not upgrade from sd card either.

I get  driver-btm-api.c:1056:check_asic_number: Chain 0 only find 48 asic, will power off hash board 0.

I was getting target voltage over 17v, i reconnected all the wires and got it to read the hash boards but now this, and i cant change firmware with upgrade via web Installer Not Signtured and sd card or awesome miner tool dont work???

maybe Change cables to hashboards?

It worked before i changed password, idk?


Miner Type   Antminer X17
Hostname   antMiner
Model   GNU/Linux
Hardware Version   Socket connect failed: Connection refused
Kernel Version   Linux 4.6.0-xilinx-gff8137b-dirty #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
File System Version   Wed Dec 25 16:31:06 CST 2019.


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
• 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: 195320K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 34056K 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: 21016K (cc67a000 - 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: 18/7, WL threshold: 4096, image sequence number: 306349061
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): 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 038216C1-D266-46DA-A76E-C04B142933A3, 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: 3171/468, WL threshold: 4096, image sequence number: 1751317449
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): 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 51C7124B-A562-4AA0-948B-184BE8DB9030, 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 0xcfb38000
*base_vir_addr = 0xab013
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2023-10-11 02:38:23 driver-btm-api.c:650:init_freq_mode: This is scan-user version
2023-10-11 02:38:23 driver-btm-api.c:2016:bitmain_soc_init: opt_multi_version     = 1
2023-10-11 02:38:23 driver-btm-api.c:2017:bitmain_soc_init: opt_bitmain_ab        = 1
2023-10-11 02:38:23 driver-btm-api.c:2018:bitmain_soc_init: opt_bitmain_work_mode = 0
2023-10-11 02:38:23 driver-btm-api.c:2019:bitmain_soc_init: Miner compile time: Wed Dec 25 16:31:06 CST 2019 type: Antminer X17
2023-10-11 02:38:23 driver-btm-api.c:2020:bitmain_soc_init: commit version: 9ee4e2a 2019-12-25 16:11:51, build by: lol 2019-12-25 16:38:57
2023-10-11 02:38:23 driver-btm-api.c:1829:show_sn: no SN got, please write SN to /nvdata/sn
2023-10-11 02:38:23 driver-btm-api.c:1154:miner_device_init: Detect 256MB control board of XILINX
2023-10-11 02:38:23 driver-btm-api.c:1102:init_fan_parameter: fan_eft : 0  fan_pwm : 0
2023-10-11 02:38:23 freq_tuning.c:2809:ehr_tuning_voltage:  tuning for ehr 0 GH
2023-10-11 02:38:23 thread.c:789:create_read_nonce_reg_thread: create thread
2023-10-11 02:38:29 driver-btm-api.c:1086:init_miner_version: miner ID : 80784c2679104814
2023-10-11 02:38:29 driver-btm-api.c:1092:init_miner_version: FPGA Version = 0xB013
2023-10-11 02:38:31 Cgminer CRC check fail.
2023-10-11 02:38:31 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2023-10-11 02:38:33 Cgminer CRC check fail.
2023-10-11 02:38:33 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2023-10-11 02:38:35 Cgminer CRC check fail.
2023-10-11 02:38:35 eeprom.c:425:check_pattern_test_level: invalid pattern test result. ignore
2023-10-11 02:38:35 ex_hash_rate.c:48:_get_ex_conf: ex_hash_rate_GH = 0, ex_freq = 0, ex_voltage = 0, ex_hash_rate = 0
2023-10-11 02:38:35 driver-btm-api.c:724:get_product_id: product_id[0] = 0
2023-10-11 02:38:35 driver-btm-api.c:724:get_product_id: product_id[1] = 0
2023-10-11 02:38:35 driver-btm-api.c:724:get_product_id: product_id[2] = 0
2023-10-11 02:38:35 driver-btm-api.c:1652:get_ccdly_opt: ccdly_opt[0] = 112
2023-10-11 02:38:35 driver-btm-api.c:1652:get_ccdly_opt: ccdly_opt[1] = 112
2023-10-11 02:38:35 driver-btm-api.c:1652:get_ccdly_opt: ccdly_opt[2] = 112
2023-10-11 02:38:35 driver-btm-api.c:1896:bitmain_board_init: g_ccdly_opt = 112
2023-10-11 02:38:35 Cgminer crc check is not pass.
2023-10-11 02:38:35 Cgminer crc check is not pass.
2023-10-11 02:38:35 Project type is X17.
2023-10-11 02:38:35 driver-btm-api.c:663:_set_project_type: project:3
2023-10-11 02:38:35 driver-btm-api.c:693:_set_project_type: Project type: Antminer X17
2023-10-11 02:38:35 driver-btm-api.c:704:dump_pcb_bom_version: Chain

• PCB Version: 0x0101

2023-10-11 02:38:35 driver-btm-api.c:705:dump_pcb_bom_version: Chain

• BOM Version: 0x0103

2023-10-11 02:38:35 driver-btm-api.c:704:dump_pcb_bom_version: Chain [1] PCB Version: 0x0101
2023-10-11 02:38:35 driver-btm-api.c:705:dump_pcb_bom_version: Chain [1] BOM Version: 0x0103
2023-10-11 02:38:35 driver-btm-api.c:704:dump_pcb_bom_version: Chain [2] PCB Version: 0x0101
2023-10-11 02:38:35 driver-btm-api.c:705:dump_pcb_bom_version: Chain [2] BOM Version: 0x0103
2023-10-11 02:38:36 driver-btm-api.c:1916:bitmain_board_init: Fan check passed.
2023-10-11 02:38:37 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2023-10-11 02:38:41 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2023-10-11 02:38:43 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2023-10-11 02:38:46 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2023-10-11 02:38:48 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2023-10-11 02:38:51 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2023-10-11 02:38:51 thread.c:784:create_pic_heart_beat_thread: create thread
2023-10-11 02:38:51 power_api.c:55:power_init: power init ...
2023-10-11 02:38:51 driver-btm-api.c:1926:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2023-10-11 02:39:23 power_api.c:232:set_iic_power_to_highest_voltage: setting to voltage: 17.00 ...
2023-10-11 02:39:29 power_api.c:124:check_voltage_multi: retry time: 0
2023-10-11 02:39:31 power_api.c:86:get_average_voltage: chain[0], voltage is: 17.113916
2023-10-11 02:39:33 power_api.c:86:get_average_voltage: chain[1], voltage is: 17.120039
2023-10-11 02:39:34 power_api.c:86:get_average_voltage: chain[2], voltage is: 17.028193
2023-10-11 02:39:34 power_api.c:97:get_average_voltage: aveage voltage is: 17.087383
2023-10-11 02:39:34 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000
2023-10-11 02:39:34 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[0]: chip baud = 115200, chip_divider = 26
2023-10-11 02:39:34 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[1]: chip baud = 115200, chip_divider = 26
2023-10-11 02:39:34 driver-hash-chip.c:233:dhash_chip_set_baud_v2: chain[2]: chip baud = 115200, chip_divider = 26
2023-10-11 02:39:34 uart.c:80:set_baud: set fpga_baud = 115200, fpga_divider = 26
2023-10-11 02:39:46 driver-btm-api.c:1029:check_asic_number_with_power_on: Chain[0]: find 48 asic, times 0
2023-10-11 02:39:56 driver-btm-api.c:1029:check_asic_number_with_power_on: Chain[0]: find 48 asic, times 1
2023-10-11 02:40:06 driver-btm-api.c:1029:check_asic_number_with_power_on: Chain[0]: find 48 asic, times 2
2023-10-11 02:40:06 driver-btm-api.c:1056:check_asic_number: Chain 0 only find 48 asic, will power off hash board 0
2023-10-11 02:40:18 driver-btm-api.c:1029:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 0
2023-10-11 02:40:27 driver-btm-api.c:1029:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 1
2023-10-11 02:40:37 driver-btm-api.c:1029:check_asic_number_with_power_on: Chain[1]: find 0 asic, times 2
2023-10-11 02:40:37 driver-btm-api.c:1056:check_asic_number: Chain 1 only find 0 asic, will power off hash board 1
2023-10-11 02:40:49 driver-btm-api.c:1029:check_asic_number_with_power_on: Chain[2]: find 48 asic, times 0
2023-10-11 02:40:59 driver-btm-api.c:1029:check_asic_number_with_power_on: Chain[2]: find 48 asic, times 1
2023-10-11 02:41:09 driver-btm-api.c:1029:check_asic_number_with_power_on: Chain[2]: find 48 asic, times 2
2023-10-11 02:41:09 driver-btm-api.c:1056:check_asic_number: Chain 2 only find 48 asic, will power off hash board 2
2023-10-11 02:41:10 driver-btm-api.c:201:set_miner_status: ERROR_SOC_INIT
2023-10-11 02:41:10 driver-btm-api.c:142:stop_mining: stop mining: soc init failed!
2023-10-11 02:41:10 thread.c:834:cancel_read_nonce_reg_thread: cancel thread
2023-10-11 02:41:10 driver-btm-api.c:128:killall_hashboard: ****power off hashboard****


thanks for the help yall!!

[1714692971]

1714692971

[1714692971]

1714692971

[1714692971]

1714692971

[1714692971]

1714692971

[1714692971]

1714692971

[seek3r]

I get  driver-btm-api.c:1056:check_asic_number: Chain 0 only find 48 asic, will power off hash board 0.

This sounds like a detection problem with the ASIC chips on one of ur hashboards. Ofc there are a few indicators which can cause the problems but as u already mentioned I would start to switch the cables and check the connectors to the control board aswell.
Be careful: Overvoltage can and will damage electronic parts on the long run. If you are facing it again, I highly recommend to check if the psu is working correctly. Might swap that aswell.


So if I am right you tried these options to upgrade ur firmware, right?

• Web Interface
• SD card
• Awesome Miner Tool

If you are trying to upgrade via Web Interface due to signature error it just means that you are trying to install an unofficial version. It might be the case that its not signed correctly, so where did you find that?

The SD card option could be the same problem. If you have the wrong version/firmware it cannot work.
Make sure that you follow the Bitmain firmware upgrade guide (You can find it here: https://support.bitmain.com/hc/en-us/articles/360013786654-How-to-reload-or-upgrade-firmware-)

For the Awesome Miner Tool I cannot speak for myself because I have zero experience with it but I found this on their website:

Firmware installation failed - missing signature
Most of the recent firmware from Bitmain have a signature lock that will prevent custom firmware from being installed. When installing the Awesome Miner firmware via the Antminer web interface the result may be an error message about missing signature for the firmware.
Awesome Miner can be used to install Antminer firmware and in many cases bypass the issues related to the signature lock on the Antminer.

To install the firmware via Awesome Miner, go to the toolbar: Tools -> ASIC Tools -> Update firmware. The firmware can be selected from a list and Awesome Miner will automatically download and install the firmware on all selected miners.

Awesome Miner can bypass the Antminer signature check on most Antminers with the following exceptions:

    Antminer S9, L3+: Bitmain firmware from July 2019 or later
    Antminer S17, T17: Bitmain firmware from December 2019 or later

To install the firmware on any of the Bitmain firmware listed above, an SD card must be used. SD card images can be downloaded from the Awesome Miner Antminer firmware page.

BTW: You would get more help from users if you would post this in the Mining Support section.

[BitMaxz]

The middle hashboard only finds 0 ASIC there might be an issue with the cable or the Hashboard.

About flashing the unit through an SD card you might be trying to flash the wrong firmware(with extension tar.gz) if you want to reset the password to default then Bitmain has an SD card firmware to reset it to default you can find it on TF card service pack file name is "sd_set_default_password_enhanced_0527_S17Pro.7z".
You need 7zip to extract the files and then copy and paste all extracted files into the SD card. After that, you will need to edit "passwd.txt" to the password you want before you flash it into the control board.

The whole guide on how to do it can be found here "SD card flashing with custom password"

If flashing does not work then try to replace your SD card because maybe the SD card you using makes the image files corrupted usually fake SD card makes files corrupted.

[miner0069]

I had a brand new sd card...... but anyways, i DLed the antminer tool from bitmain, it seen miner but gave status as lost, it said successful upgrade to firmware when i tried that i got but didnt work. and said couldnt connect to port 22. 

Then i hit the dhcp tab and now i cant connect to miner at all, tired to flash with sd card nothing, restarted nothing. Tired to add miner ip to dhcp wont add it...

So now idk what is wrong is it the dhcp. Not sure what the dhcp tab did in the antminer tool....

Ill try to flash it with the control board recovery tool and see what that does...
Weird two control boards that wont flash from sd card. idk

any insights are appreciated, thanks.  

[BitMaxz]

If you switch the miner to DHCP mode it would automatically change its IP based on your current network.
This means the IP that you are trying to access is no longer the IP of this unit you need to use the IP report button to scan the right IP of your unit.

If you don't know how to do it then follow this guide below.

- https://support.bitmain.com/hc/en-us/articles/360021217114-How-to-set-up-a-new-S17-Pro-S17

[mikeywith]

So now idk what is wrong is it the dhcp. Not sure what the dhcp tab did in the antminer tool....

DHCP does not belong to your antminer -- it belongs to your router, when you set the miner to DHCP it means the miner will have to request an IP address from your router, if for whatever reason your router does not do that you can't access the miner.

So first thing first, make sure your router has DHCP enabled and that the search range on the Bitmain tool covers the entire DHCP table, or even better, get the miner's IP using the router itself.

[philipma1957]

down load angry ip or advanced ip

search all your ips

typically your range may be

192.168.1.1-255

or

192.168.0.1-255

or

192.168.2.1-255


you will get a list of every piece of gear you are running

just search each one by one

you should find the s17 that way.

[mikeywith]

down load angry ip or advanced ip

search all your ips

typically your range may be

192.168.1.1-255

or

192.168.0.1-255

or

192.168.2.1-255


you will get a list of every piece of gear you are running

just search each one by one

you should find the s17 that way.

Most home routers DHCP's table would start with 192.168.1.2, but some will have say the first hundred reserved for static ips and dhcp table starts from 192.168.1.101, also, despite not being very common, some routers come with DHCP disabled.

I have also seen many people screw up the details of the miner network page by setting a different subnet, this will make you lose the miner and you would need to reset the miner either by hard reset or sdcard.