Title: UART SERIAL INFO - BItmain ControlBoard fails to get IP, even after flashing. Post by: JessieJames13 on March 30, 2024, 01:56:48 PM I took a working s17+ control board and a non-working board. - I flashed both successfully with the same official bitmain firmware.
The working board gets an IP from my router, the non-working doesn't get an IP. The RJ45 leds light up on both boards, and flicker, as expected. What does this problem sound like? The non-working board restarts every 10 seconds. Video of Board Restart https://streamable.com/ath5kv trying now to connect with UART Title: Re: BItmain ControlBoard fails to get IP, even after flashing. How to repair? Post by: JessieJames13 on March 30, 2024, 09:12:16 PM UART Serial Connection Log, with Ethernet cable attached, No SD Card Attached.
I notice it says PHY is not detected GEM PHY init failed No ethernet found. Quote U-Boot 2016.07-g7640c9f-dirty (Feb 27 2018 - 17:57:23 +0800) [/b][/color]Model: Zynq MicroZED Board Board: Xilinx Zynq DRAM: dram_init: sys_sdram_size = 0x10000000 dram_init: sys_sdram_size = 256 MB dram_init: gd->ram_size = 0x0f000000 ECC disabled 240 MiB NAND: 256 MiB MMC: sdhci@e0100000: 0 Invalid bus 0 (err=-1) *** Warning - spi_flash_probe() failed, using default environment In: serial@e0000000 Out: serial@e0000000 Err: serial@e0000000 Model: Zynq MicroZED Board Board: Xilinx Zynq board_late_init: bootargs: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk --- boot gpio value = 0x000fff3c --- nand boot nand --- Net: --- phy_broadcom_init ZYNQ GEM: e000b000, phyaddr 0, interface gmii --- zynq_gem_probe --- mdio_register --- mdio_register 1 --- mdio_register 2 --- mdio_register 3 --- zynq_phy_init: interface = 1 --- zynq_phy_init 0000000000 PHY is not detected GEM PHY init failed No ethernet found. Hit any key to stop autoboot: 0 Copying Linux from NAND flash to RAM... NAND read: device 0 offset 0x2000000, size 0x800000 8388608 bytes read: OK NAND read: device 0 offset 0x1a00000, size 0x20000 131072 bytes read: OK Copying ramdisk... NAND read: device 0 offset 0x2800000, size 0x2000000 33554432 bytes read: OK ## Booting kernel from Legacy Image at 02000000 ... Image Name: Linux-4.6.0-xilinx-gff8137b-dirt Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 4006768 Bytes = 3.8 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy for 0, Image at 04000000 ... Image Name: Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 12155339 Bytes = 11.6 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK get ramdisk ok ## Flattened Device Tree blob at 03000000 Booting using the fdt blob at 0x3000000 Loading Kernel Image ... OK Loading Ramdisk to 0cf69000, end 0db009cb ... OK Loading Device Tree to 0cf64000, end 0cf68de1 ... OK Starting kernel ... 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 percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152 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: 204464K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 24912K 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. Trying to unpack rootfs image as initramfs... rootfs image is not initramfs (no cpio magic); looks like an initrd Freeing initrd memory: 11872K (ccf69000 - 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): warning: mounting unchecked fs, running e2fsck is recommended 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) INIT: version 2.88 booting mount: mounting devtmpfs on /dev failed: Device or resource busy Starting Bootlog daemon: bootlogd: cannot allocate pseudo tty: No such file or directory bootlogd. Starting Monitor-ipsig daemon: monitor-ipsig. EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr random: dd urandom read with 0 bits of entropy available check mouted config mounting config ubiattach /dev/ubi_ctrl -m 2 -d 0 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: 23/12, WL threshold: 4096, image sequence number: 237714726 ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40 ubi0: background thread "ubi_bgt0d" started, PID 709 UBI device number 0, total 64 LEBs (8126464 bytes, 7.8 MiB), available 0 LEBsUBIFS error (ubi0:0 pid 710): ubifs_check_node: bad CRC: calculated 0x9c9d8daa, read 0xdd1a5773 (0 bytes), LEB size 126976 bytes (124.0 KiB) ubi_attach succeeUBIFS error (ubi0:0 pid 710): ubifs_check_node: bad node at LEB 0:0 ds mount -t ubifs ubi0_0 /config magic 0x6101831 crc 0xdd1a5773 node_type 6 (superblock node) group_type 0 (no node group) sqnum 1 len 4096 key_hash 0 (R5) key_fmt 0 (simple) flags 0x0 big_lpt 0 space_fixup 0 min_io_size 2048 leb_size 126976 leb_cnt 20 max_leb_cnt 20 max_bud_bytes 380928 log_lebs 2 lpt_lebs 2 orph_lebs 2 jhead_cnt 1 fanout 8 lsave_cnt 256 default_compr 1 rp_size 69836 rp_uid 0 rp_gid 0 fmt_version 4 time_gran 1000000000 UUID FF09433B-E002-4C29-97EC-6220DDC4BB36 CPU: 0 PID: 710 Comm: mount Not tainted 4.6.0-xilinx-gff8137b-dirty #25 Hardware name: Xilinx Zynq Platform [<c010e718>] (unwind_backtrace) from [<c010a8d0>] (show_stack+0x10/0x14) [<c010a8d0>] (show_stack) from [<c02fcea4>] (dump_stack+0x84/0xa4) [<c02fcea4>] (dump_stack) from [<c02ab99c>] (ubifs_check_node+0x1d4/0x20c) [<c02ab99c>] (ubifs_check_node) from [<c02acbc4>] (ubifs_read_node+0x17c/0x258) [<c02acbc4>] (ubifs_read_node) from [<c02aa164>] (ubifs_read_sb_node+0x50/0x70) [<c02aa164>] (ubifs_read_sb_node) from [<c02aa1e4>] (ubifs_read_superblock+0x20/0xd0c) [<c02aa1e4>] (ubifs_read_superblock) from [<c02a99f4>] (ubifs_mount+0xe78/0x13fc) [<c02a99f4>] (ubifs_mount) from [<c01cb554>] (mount_fs+0xc/0x44) [<c01cb554>] (mount_fs) from [<c01e1608>] (vfs_kern_mount+0x48/0xf0) [<c01e1608>] (vfs_kern_mount) from [<c01e496c>] (do_mount+0x9cc/0xaf8) [<c01e496c>] (do_mount) from [<c01e4cbc>] (SyS_mount+0x70/0x98) [<c01e4cbc>] (SyS_mount) from [<c0106f00>] (ret_fast_syscall+0x0/0x3c) mount: mounting ubi0_0 on /config failed: Structure needs cleaning ubi_mount failed,reboot. INIT: Switching to runlevel: 6 INIT: Sending processes the TERM signalSending all processes the TERM signal... Sending all processes the KILL signal... Unmounting remote filesystems... Deactivating swap... Unmounting local filesystems... EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr �ebooting... reboot: Restarting system Title: Re: UART SERIAL INFO - BItmain ControlBoard fails to get IP, even after flashing. Post by: BitMaxz on March 31, 2024, 08:38:55 PM It seems the control board can't get a proper IP. Would you mind to check the Ethernet terminals and try to clean them with isopropyl alcohol?
Since it was bricked the only way to reflash it is by flashing it through the serial port there's a guide on Zeusbtc that you can follow check this link below - https://www.zeusbtc.com/articles/asic-miner-troubleshooting/1082-recovery-method-of-miner-serial-port-virus Title: Re: UART SERIAL INFO - BItmain ControlBoard fails to get IP, even after flashing. Post by: JessieJames13 on April 01, 2024, 01:00:49 AM It seems the control board can't get a proper IP. Would you mind to check the Ethernet terminals and try to clean them with isopropyl alcohol? Since it was bricked the only way to reflash it is by flashing it through the serial port there's a guide on Zeusbtc that you can follow check this link below - https://www.zeusbtc.com/articles/asic-miner-troubleshooting/1082-recovery-method-of-miner-serial-port-virus Ive been successful in re-flashing the board. Also, how do you know it was bricked? But I can try to clean connectors with alcohol and report back Title: Re: UART SERIAL INFO - BItmain ControlBoard fails to get IP, even after flashing. Post by: BitMaxz on April 01, 2024, 11:22:31 AM Also, how do you know it was bricked? You said that the control board fails to get the IP or the unit is inaccessible so that's the reason why it makes me think that the control board might be bricked. Any related software flashing if you flash it wrong it always ends up bricked like phones if you flash a corrupted firmware the phone might end up boot loop/bricked with no power. There's something weird in your profile how did you get -68 merits? Title: Re: UART SERIAL INFO - BItmain ControlBoard fails to get IP, even after flashing. Post by: philipma1957 on April 01, 2024, 01:24:19 PM Also, how do you know it was bricked? You said that the control board fails to get the IP or the unit is inaccessible so that's the reason why it makes me think that the control board might be bricked. Any related software flashing if you flash it wrong it always ends up bricked like phones if you flash a corrupted firmware the phone might end up boot loop/bricked with no power. There's something weird in your profile how did you get -68 merits? april fools day joke. but pay not attention to me as I am a loudmouth 😀 Title: Re: UART SERIAL INFO - BItmain ControlBoard fails to get IP, even after flashing. Post by: BitMaxz on April 01, 2024, 01:30:37 PM april fools day joke. but pay not attention to me as I am a loudmouth 😀 Ow it's April I forgot that is why my merit is also decreasing. That's a weird joke :D Title: Re: UART SERIAL INFO - BItmain ControlBoard fails to get IP, even after flashing. Post by: JessieJames13 on April 01, 2024, 07:22:29 PM Also, how do you know it was bricked? You said that the control board fails to get the IP or the unit is inaccessible so that's the reason why it makes me think that the control board might be bricked. Any related software flashing if you flash it wrong it always ends up bricked like phones if you flash a corrupted firmware the phone might end up boot loop/bricked with no power. There's something weird in your profile how did you get -68 merits? i wasnt able to flash with braiins, antminer official, hive, but zeus mining helped me with a firmware package that was successful. After zeus firmware, I was able to put any other firmware brand. I dont think its bricked as the serial log shows info I am determined to get this controlboard working. need to spend more time on it. I will report back. |