Bitcoin Forum>Bitcoin>Mining>Mining support
Author

Topic: S17+ Various number of ASICS found - ERROR_SOC_INIT (Read 123 times)

mikeywith
legendary
Activity: 2394
Merit: 6581
be constructive or S.T.F.U
S17+ Various number of ASICS found - ERROR_SOC_INIT
June 02, 2024, 06:19:27 PM
#8
Quote from: bitcoinlover39 on June 01, 2024, 12:44:01 PM
Ps : can I upload photos in message ?!

Go here https://www.talkimg.com/

Upload the image and post the link, one of us will [image] it for you and it would be visible to everyone without having to visit the link.

As for what I think happened to your hashboard, the air was way too strong, it moved some of the chips and now they have bad contact with the PCB, the Antminer S17 series has a very common issue which is the cheap/low-quality solder used to attach chips, the chip count test is done by sending power across all the chips and see where it stops it, in the process and given that the chips are pretty loose, the signal may comeback at times but not at others, it's very common, if you cool it in the fridge or heat it a little you will get different results, heck even shaking the miner really hard would result in different results, this miner is the worst electronic piece the world has ever made.

Before heating it, i would go the opposite direction which is slightly safer, and that would be freezing it, I did that and had some luck, just rap it in a plastic bag, make sure it's airtight, and freeze it for 24-48 hours see if you get lucky.


Obviously, this assumes you did the basic checking and tried another ribbon cable and used a different port in the control board.

Quote from: philipma1957 on May 26, 2024, 11:51:19 AM
The heatsinks are glued on. The glue gets brittle the cleaning you did likely did a fracture in the chip to heat sink attachment.

I do think he broke it, but here is a small correction, it's a chip issue not the heatsink, you can literally remove the heatsink on one or some of the chips and the count will go through perfectly, you will even see the miner hash for a few seconds at full speed and then an over-temp error will appear in the kernel log and the miner will stop hashing.
NotFuzzyWarm
legendary
Activity: 3822
Merit: 2703
Evil beware: We have waffles!
Re: S17+ Various number of ASICS found - ERROR_SOC_INIT
June 01, 2024, 05:09:40 PM
#7
@OP Merit given for one of the most concise newbie posts in a long time.
Clear, to the point, und ya even know how to use the code # tag  Grin

That link for zeusebtc that BitMaxz gave should give you all the info you need. If you are thinking of reflowing the chips - be very careful. The oldest s17's used a black epoxy thermal glue to attach the heat sinks. It softens around 150C well before the solder melts. Later ones use a low-temp aluminum solder to attach them.
BitMaxz
legendary
Activity: 3374
Merit: 3095
Playbet.io - Crypto Casino and Sportsbook
Re: S17+ Various number of ASICS found - ERROR_SOC_INIT
June 01, 2024, 02:53:27 PM
#6
Quote from: bitcoinlover39 on June 01, 2024, 12:44:01 PM
Only thing I did not do : heating in my oven ! I keep it for next step.


I don't think that's a bright idea without confirming if it's a software or hardware issue.

Usually, soc init fails are software issue related it can be fixed mostly by flashing the unit firmware since you said it didn't work by upgrading it with the latest version try other software way before you heat them into the oven because if you do that the result might be worst until you can't able to repair the hashboard.

Have you tried to flash the unit or boot the unit with Braiins OS to test? If not try it first.

If it didn't work, check the test points to confirm if it's a hardware issue.
You can find the test points below, including instructions on how to repair it.

- https://www.zeusbtc.com/manuals/Antminer-S17-plus-Hash-Board-Repair-Guide.asp
bitcoinlover39
newbie
Activity: 2
Merit: 5
Re: S17+ Various number of ASICS found - ERROR_SOC_INIT
June 01, 2024, 12:44:01 PM
#5
Hello,

Thank you a lot for your answers, it permits me to update this S17+ because I have no idea :O

To answer to some question :
  • I've never changed firmware I used Antminer FW --> No overclocking
  • The cleaning was only compressed air
  • Now, I don't have the two other hashboard

What i've done since you wrote me :
  • Busbar is well connected, I used my voltmeter, I have the same voltage as written in log (21V).
  • I checked connections and I think it is ok : 4 same sockets from PSU / 1 socket from PSU / 1 socket from PSU / Ethernet cable / 1 socket used to hashboard --> 8 cables in total.
  • I replace the signal cable between hashboard and control board --> norhing happened.

Only thing I did not do : heating in my oven ! I keep it for next step.

Some dumb questions : How is it possible to count different number of ASIC ? If an ASIC on hashboard was broken, it would count the same number of ASIC every time ? I was convinced that this error (socket init failed) was linked to control board, not hashboard...
Intelligent question : do you see anything weird on the picture ?! I think it is probably a wiring issue...

Thank you a lot if you have any advice more ! I'm investigating only during end of the week !!

Ps : can I upload photos in message ?!
BitMaxz
legendary
Activity: 3374
Merit: 3095
Playbet.io - Crypto Casino and Sportsbook
Re: S17+ Various number of ASICS found - ERROR_SOC_INIT
May 26, 2024, 12:13:47 PM
#4
If it was working before how did you exactly clean up the hashboard? If it is just a compressed air it shouldn't turn like this there might be something that you forgot to check after reassembling the unit.

Would you mind to try the busbar maybe it is not connected properly which is why it is not supplying enough power to the hashboard also try to clean all terminals on the control board use lacquer flo thinner or isopropyl alcohol to clean all terminals and connectors.
And don't forget to clean the busbar use sandpaper to remove the rust or to make sure it is clean sometimes dirt and rust are the reasons why the hashboard can't run well.
philipma1957
legendary
Activity: 4256
Merit: 8551
'The right to privacy matters'
Re: S17+ Various number of ASICS found - ERROR_SOC_INIT
May 26, 2024, 11:51:19 AM
#3
You broke it.  you could try a different white cable from controller to the single board in it.


If you have the other two boards you could try them.


Must likely cleaning the board broke it.

The heatsinks are glued on. The glue gets brittle the cleaning you did likely did a fracture in the chip to heat sink attachment.

You could get lucky if you put it in an oven at 225f-225f  tall heatsinks up for ten minutes.


I had 29 s17's I moved them and cleaned them and 11 were no longer good.

I saved a few heating up in an oven.

DaCryptoRaccoon
hero member
Activity: 1220
Merit: 612
OGRaccoon
Re: S17+ Various number of ASICS found - ERROR_SOC_INIT
May 26, 2024, 11:02:41 AM
#2
Looks like you have a few issues.

Multiple entries like check_asic_number_with_power_on showing inconsistent ASIC counts (from 1 to 24 to 0).

The voltage readings and adjustments appear to be fluctuating.

The log ends with ERROR_SOC_INIT and stop mining: soc init failed!, indicating a system-on-chip initialization failure.

Check your PSU is not on dying this can be a issue with voltage.  Ensure all power and data cables are securely connected. Loose connections can lead to intermittent ASIC detection.

Verify that the power supply is stable and providing consistent voltage. Fluctuations in power can lead to initialization failures.

Have you over/under clocked the device?  

Are you using the Bitmain firmware?

You could try re-install the firmware see if this works.

https://shop.bitmain.com/support/download

If this fails you may have a faulty board and may need repair.
bitcoinlover39
newbie
Activity: 2
Merit: 5
Re: S17+ Various number of ASICS found - ERROR_SOC_INIT
May 26, 2024, 06:03:08 AM
#1
Hello,

This is my first time on this forum, I hope I post on the good topic, thank you for your understanding Smiley

My miner is an S17+ containing only one hashboard (to eliminate debugging problems). Context : I decided to clean my miner from dust --> openned it and remove Hashboard, clean it, reassemble it and here is the issue "ERROR_SOC_INIT". I checked connections 10 times : Hashboard is plugged into the control board, ... Everything should be connected.
I followed the "Reboot / Firmware update / Verification Configuration Pool / Internet connection check" procedure. I've reached a stage where I don't know what to test.
I'll let you have a look at the code below: Socket Init error announced, but you can see that the number of ASICs detected varies according to the tests. Does anyone have any idea how to interpret the evolution of the number of chips found?

Thank you !

Here is my log kernel :
Code:
Booting Linux on physical CPU 0x0
Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
  Normal zone: 480 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 203432K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25944K 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
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: 12904K (cce67000 - cdb01000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAEAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
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: 119/55, WL threshold: 4096, image sequence number: 262741923
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 A9E8BDA4-70DE-45D9-83BE-2DD9F129C0C6, 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: 4108/1185, WL threshold: 4096, image sequence number: 3563076859
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 A21581E4-693A-4BBF-A66A-FCE5ACD2EF7F, 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 = 0xb023
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
2024-05-26 10:35:08 driver-btm-api.c:779:init_freq_mode: This is scan-user version
2024-05-26 10:35:08 driver-btm-api.c:2451:bitmain_soc_init: opt_multi_version     = 1
2024-05-26 10:35:08 driver-btm-api.c:2452:bitmain_soc_init: opt_bitmain_ab        = 1
2024-05-26 10:35:08 driver-btm-api.c:2453:bitmain_soc_init: opt_bitmain_work_mode = 0
2024-05-26 10:35:08 driver-btm-api.c:2454:bitmain_soc_init: Miner compile time: Tue Jun  2 10:31:07 CST 2020 type: Antminer S17+
2024-05-26 10:35:08 driver-btm-api.c:2455:bitmain_soc_init: commit version: 1ca50a5 2020-06-01 18:51:22, build by: lol 2020-06-02 10:37:21
2024-05-26 10:35:08 driver-btm-api.c:2083:show_sn: len:16, 8114f44a7910481c
2024-05-26 10:35:08 driver-btm-api.c:2461:bitmain_soc_init: show sn return 1
2024-05-26 10:35:08 driver-btm-api.c:2103:handle_sn_for_factory_mode: show sn return 1
2024-05-26 10:35:08 driver-btm-api.c:2141:handle_sn_for_factory_mode: read sn success, 8114f44a7910481c
2024-05-26 10:35:08 fan.c:284:front_fan_power_on: Note: front fan is power on!
2024-05-26 10:35:08 fan.c:296:rear_fan_power_on: Note: rear fan is power on!
2024-05-26 10:35:08 driver-btm-api.c:1314:miner_device_init: Detect 256MB control board of XILINX
2024-05-26 10:35:08 driver-btm-api.c:1255:init_fan_parameter: fan_eft : 0  fan_pwm : 0
2024-05-26 10:35:14 driver-btm-api.c:1239:init_miner_version: miner ID : 8114f44a7910481c
2024-05-26 10:35:14 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2024-05-26 10:35:16 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2024-05-26 10:35:16 driver-btm-api.c:2234:update_conf_by_power_feedback: Power feedback is disabled
2024-05-26 10:35:16 driver-btm-api.c:2202:get_calibration_voltage: calibration voltage flag is error data.
2024-05-26 10:35:16 driver-btm-api.c:2268:update_conf_by_power_feedback: Note: no calibration voltage, default diff = 0
2024-05-26 10:35:16 frequency.c:1457:adjust_higer_max_vol_table: adjust_higer_max_vol_table, adjust_vol = 0
2024-05-26 10:35:16 thread.c:1363:create_read_nonce_reg_thread: create thread
2024-05-26 10:35:22 driver-btm-api.c:1239:init_miner_version: miner ID : 8114f44a7910481c
2024-05-26 10:35:22 driver-btm-api.c:1245:init_miner_version: FPGA Version = 0xB023
2024-05-26 10:35:24 driver-btm-api.c:837:get_product_id: product_id[2] = 0
2024-05-26 10:35:24 driver-btm-api.c:792:_set_project_type: project:0
2024-05-26 10:35:24 driver-btm-api.c:813:_set_project_type: Project type: Antminer S17+
2024-05-26 10:35:24 driver-btm-api.c:824:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2024-05-26 10:35:24 driver-btm-api.c:825:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2024-05-26 10:35:26 driver-btm-api.c:2372:bitmain_board_init: Fan check passed.
2024-05-26 10:35:27 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2024-05-26 10:35:29 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2024-05-26 10:35:29 thread.c:1358:create_pic_heart_beat_thread: create thread
2024-05-26 10:35:29 power_api.c:213:power_init: Power init:
2024-05-26 10:35:29 power_api.c:214:power_init: current_voltage_raw = 0
2024-05-26 10:35:29 power_api.c:215:power_init: highest_voltage_raw = 2100
2024-05-26 10:35:29 power_api.c:216:power_init: working_voltage_raw = 1950
2024-05-26 10:35:29 power_api.c:217:power_init: higher_voltage_raw  = 2040
2024-05-26 10:35:29 power_api.c:218:power_init: check_asic_voltage_raw  = 2100
2024-05-26 10:35:29 driver-btm-api.c:2382:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2024-05-26 10:35:29 power_api.c:186:power_off: init gpio907
2024-05-26 10:36:01 power_api.c:324:set_to_highest_voltage_by_steps: Set to voltage raw 2100, step by step.
2024-05-26 10:36:27 power_api.c:85:check_voltage_multi: retry time: 0
2024-05-26 10:36:28 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.287706
2024-05-26 10:36:28 power_api.c:53:_get_avg_voltage: average_voltage = 21.287706
2024-05-26 10:36:28 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.29, check voltage passed.
2024-05-26 10:36:28 uart.c:72:set_baud: set fpga_baud to 115200
2024-05-26 10:36:39 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 5 asic, times 0
2024-05-26 10:36:50 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 24 asic, times 1
2024-05-26 10:37:01 driver-btm-api.c:1134:check_asic_number_with_power_on: Chain[2]: find 1 asic, times 2
2024-05-26 10:37:01 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw  = 2100
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2024-05-26 10:37:10 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[2]: find 5 asic, times 3
2024-05-26 10:37:10 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw  = 2050
2024-05-26 10:37:10 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2050, step by step.
2024-05-26 10:37:14 power_api.c:85:check_voltage_multi: retry time: 0
2024-05-26 10:37:15 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.755695
2024-05-26 10:37:15 power_api.c:53:_get_avg_voltage: average_voltage = 20.755695
2024-05-26 10:37:15 power_api.c:71:check_voltage: target_vol = 20.50, actural_vol = 20.76, check voltage passed.
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2024-05-26 10:37:24 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 4
2024-05-26 10:37:24 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw  = 2000
2024-05-26 10:37:24 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2000, step by step.
2024-05-26 10:37:27 power_api.c:85:check_voltage_multi: retry time: 0
2024-05-26 10:37:28 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 20.276299
2024-05-26 10:37:28 power_api.c:53:_get_avg_voltage: average_voltage = 20.276299
2024-05-26 10:37:28 power_api.c:71:check_voltage: target_vol = 20.00, actural_vol = 20.28, check voltage passed.
chain 2, IO_DRIVE_STRENGTH_CONFIGURATION reg = 0x f1fffff
2024-05-26 10:37:38 register.c:313:get_register: !!! REG_TYPE = 1. 1073741826
2024-05-26 10:37:38 register.c:313:get_register: !!! REG_TYPE = 1. 1073741826
2024-05-26 10:37:40 driver-btm-api.c:1157:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 5
2024-05-26 10:37:40 power_api.c:380:modify_check_asic_voltage: check_asic_voltage_raw  = 2100
2024-05-26 10:37:40 power_api.c:364:set_to_check_asic_voltage_by_steps: Set to voltage raw 2100, step by step.
2024-05-26 10:37:45 power_api.c:85:check_voltage_multi: retry time: 0
2024-05-26 10:37:46 power_api.c:40:_get_avg_voltage: chain = 2, voltage = 21.260758
2024-05-26 10:37:46 power_api.c:53:_get_avg_voltage: average_voltage = 21.260758
2024-05-26 10:37:46 power_api.c:71:check_voltage: target_vol = 21.00, actural_vol = 21.26, check voltage passed.
2024-05-26 10:37:46 driver-btm-api.c:1193:check_asic_number: Chain 2 only find 0 asic, will power off hash board 2
2024-05-26 10:37:47 driver-btm-api.c:1195:check_asic_number: Chain 2 voltage: an0 = 2.832258, an2 2.851613, an6 2.548387.
2024-05-26 10:37:48 driver-btm-api.c:222:set_miner_status: ERROR_SOC_INIT
2024-05-26 10:37:48 driver-btm-api.c:156:stop_mining: stop mining: soc init failed!
2024-05-26 10:37:48 thread.c:1403:cancel_read_nonce_reg_thread: cancel thread
2024-05-26 10:37:48 driver-btm-api.c:141:killall_hashboard: ****power off hashboard****
Bitcoin Forum>Bitcoin>Mining>Mining support
Jump to: