Jump to content

chango

Members
  • Posts

    4
  • Joined

  1. @bunducafe After following up with the Kobol support team via email on this, I tried direct installation to eMMC via USB-C cable, but that produced the same results. It ended up with me sending it back for a replacement, which their team handled fast and smoothly to their credit, and my replacement board works well as expected, and is now running 24/7 from eMMC. I suggest persisting to trying to find a way to connect via the USB-C serial console, as this will give you sufficient info to see what may be happening and how to proceed. For me I had to cut back the USB-C cable sheathing about 1.5-2mm or so to get a snug fit in the socket, and I also had the benefit of having another computer with Linux on to help diagnose.
  2. I managed to get the serial console working via my Manjaro box (after trimming the USB-C cable sheathing as suggested in other threads; still no success using MacBook Pro though). The serial output is shown below, indicating such a possible eMMC issue ("Loading Environment from MMC... *** Warning - bad CRC, using default environment"): DDR Version 1.24 20191016 In channel 0 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 1 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 0 training pass! channel 1 training pass! change freq to 416MHz 0,1 Channel 0: LPDDR4,416MHz Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB Channel 1: LPDDR4,416MHz Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB 256B stride channel 0 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 1 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 0 training pass! channel 1 training pass! channel 0, cs 0, advanced training done channel 1, cs 0, advanced training done change freq to 856MHz 1,0 ch 0 ddrconfig = 0x101, ddrsize = 0x40 ch 1 ddrconfig = 0x101, ddrsize = 0x40 pmugrf_os_reg[2] = 0x32C1F2C1, stride = 0xD ddr_set_rate to 328MHZ ddr_set_rate to 666MHZ ddr_set_rate to 928MHZ channel 0, cs 0, advanced training done channel 1, cs 0, advanced training done ddr_set_rate to 416MHZ, ctl_index 0 ddr_set_rate to 856MHZ, ctl_index 1 support 416 856 328 666 928 MHz, current 856MHz OUT Boot1: 2019-03-14, version: 1.19 CPUId = 0x0 ChipType = 0x10, 254 SdmmcInit=2 0 BootCapSize=100000 UserCapSize=14910MB FwPartOffset=2000 , 100000 mmc0:cmd8,20 mmc0:cmd5,20 mmc0:cmd55,20 mmc0:cmd1,20 mmc0:cmd8,20 mmc0:cmd5,20 mmc0:cmd55,20 mmc0:cmd1,20 mmc0:cmd8,20 mmc0:cmd5,20 mmc0:cmd55,20 mmc0:cmd1,20 SdmmcInit=0 1 StorageInit ok = 67806 SecureMode = 0 SecureInit read PBA: 0x4 SecureInit read PBA: 0x404 SecureInit read PBA: 0x804 SecureInit read PBA: 0xc04 SecureInit read PBA: 0x1004 SecureInit read PBA: 0x1404 SecureInit read PBA: 0x1804 SecureInit read PBA: 0x1c04 SecureInit ret = 0, SecureMode = 0 atags_set_bootdev: ret:(0) GPT 0x3380ec0 signature is wrong recovery gpt... GPT 0x3380ec0 signature is wrong recovery gpt fail! LoadTrust Addr:0x4000 No find bl30.bin No find bl32.bin Load uboot, ReadLba = 2000 Load OK, addr=0x200000, size=0xdd6b0 RunBL31 0x40000 NOTICE: BL31: v1.3(debug):42583b6 NOTICE: BL31: Built : 07:55:13, Oct 15 2019 NOTICE: BL31: Rockchip release version: v1.1 INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3 INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 0 INFO: plat_rockchip_pmu_init(1190): pd status 3e INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 U-Boot 2020.07-armbian (Dec 15 2020 - 08:45:45 +0100) SoC: Rockchip rk3399 Reset cause: POR DRAM: 3.9 GiB PMIC: RK808 SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB MMC: mmc@fe320000: 1, sdhci@fe330000: 0 Loading Environment from MMC... *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Model: Helios64 Revision: 1.2 - 4GB non ECC Net: eth0: ethernet@fe300000 scanning bus for devices... Hit any key to stop autoboot: 0 Card did not respond to voltage select! switch to partitions #0, OK mmc0(part 0) is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3185 bytes read in 18 ms (171.9 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 0 166 bytes read in 15 ms (10.7 KiB/s) 14273382 bytes read in 1378 ms (9.9 MiB/s) 27507200 bytes read in 2630 ms (10 MiB/s) 81968 bytes read in 38 ms (2.1 MiB/s) 2698 bytes read in 34 ms (77.1 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 09000000 ## Loading init Ramdisk from Legacy Image at 06000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 14273318 Bytes = 13.6 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 Loading Ramdisk to f514a000, end f5ee6b26 ... OK Loading Device Tree to 00000000f50cd000, end 00000000f5149fff ... OK Starting kernel ... I've repeated the process multiple times, removing the partition (with fdisk), wiping the bootloader and partition superblock (as mentioned in the wiki troubleshooting page), and re-copying using nand-sata-install, but with the same result each time. Rebooting with the SD card in place shows the same error, but continues to boot from the SD card instead. I'm uncertain how to proceed from here. Having working on-board eMMC is a key addition to this board over the comparative unreliability of using Micro-SD. Given that the eMMC is soldered to the board, I'm guessing this requires a replacement board to resolve?
  3. @aprayoga Unfortunately I have no success with obtaining serial output. I've tried using both my MacBook Pro laptop and Manjaro desktop, and neither produces any serial output. The tty never shows up when connected to the Manjaro box, and only sometimes shows up on the MBP (/dev/tty.usbserial-DT03OFSJ), but then using screen to that device produces no output (I did initial setup via ssh instead). Is any of this useful diagnostic info stored anywhere else? Curiously the eMMC has shown up on some subsequent boots, with the following output in dmesg | grep mmc: [ 2.890213] dwmmc_rockchip fe320000.mmc: IDMAC supports 32-bit address mode. [ 2.890242] dwmmc_rockchip fe320000.mmc: Using internal DMA controller. [ 2.890257] dwmmc_rockchip fe320000.mmc: Version ID is 270a [ 2.890320] dwmmc_rockchip fe320000.mmc: DW MMC controller at irq 28,32 bit host data width,256 deep fifo [ 2.890806] dwmmc_rockchip fe320000.mmc: Got CD GPIO [ 2.903703] mmc_host mmc0: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0) [ 2.919237] mmc1: CQHCI version 5.10 [ 2.944409] mmc1: SDHCI controller on fe330000.sdhci [fe330000.sdhci] using ADMA [ 2.981416] mmc_host mmc0: Bus speed (slot 0) = 148500000Hz (slot req 150000000Hz, actual 148500000HZ div = 0) [ 3.018199] mmc1: Command Queue Engine enabled [ 3.018220] mmc1: new HS200 MMC card at address 0001 [ 3.018927] mmcblk1: mmc1:0001 AJTD4R 14.6 GiB [ 3.019196] mmcblk1boot0: mmc1:0001 AJTD4R partition 1 4.00 MiB [ 3.019471] mmcblk1boot1: mmc1:0001 AJTD4R partition 2 4.00 MiB [ 3.019722] mmcblk1rpmb: mmc1:0001 AJTD4R partition 3 4.00 MiB, chardev (243:0) [ 3.021212] mmcblk1: p1 [ 3.198007] dwmmc_rockchip fe320000.mmc: Successfully tuned phase to 213 [ 3.198034] mmc0: new ultra high speed SDR104 SDHC card at address aaaa [ 3.199120] mmcblk0: mmc0:aaaa SP32G 29.7 GiB [ 3.201559] mmcblk0: p1 [ 17.507968] EXT4-fs (mmcblk0p1): mounted filesystem with writeback data mode. Opts: (null) [ 18.800952] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,errors=remount-ro On seeing this I tried again to go through the steps to transfer the system to eMMC, but was then surprised to see the HDDs thrashing. Seems the installer requires/expects all mounts to be in /mnt/, but I have a ZFS pool mounted by its default off /poolname instead. After moving the pool mountpoint I retried the install-to-eMMC process, which went fast & smoothly (apparently), but then on powering onwithout the SD card I got the familiar static System LED, and un-pingable IP (MAC address is pre-assigned to an IP by router). Replacing the SD card allows booting again. So it seems there's some issue with the transfer/boot process with eMMC, and with serial connection. Sometimes eMMC shows up, sometimes not. Serial connection never works. While I understand this is a tinkerers' device in many respects, I would also expect the basic hardware to both function and be tested. Any possible advice on which way to proceed with this?
  4. I seem to have a very similar issue, although I'm not using OMV. Fresh Debian installation (Armbian_20.11.4_Helios64_buster_current_5.9.14.img.xz) on MicroSD card, followed by update/upgrade, then tried to move to eMMC using the armbian-config menus (option 2). After a shutdown, removed MicroSD, but system refuses to boot. Replacing MicroSD card allows it to boot successfully again. Following sucessfully restarting with MicroSD in place, this is lsblk output: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 3.7T 0 disk └─sda1 8:1 0 3.7T 0 part sdb 8:16 0 3.7T 0 disk └─sdb1 8:17 0 3.7T 0 part sdc 8:32 0 3.7T 0 disk └─sdc1 8:33 0 3.7T 0 part sdd 8:48 0 3.7T 0 disk └─sdd1 8:49 0 3.7T 0 part sde 8:64 0 3.7T 0 disk └─sde1 8:65 0 3.7T 0 part mmcblk0 179:0 0 29.7G 0 disk └─mmcblk0p1 179:1 0 29.4G 0 part / zram0 251:0 0 50M 0 disk /var/log zram1 251:1 0 1.9G 0 disk [SWAP] and this is output from dmesg | grep mmc: [ 2.887657] dwmmc_rockchip fe320000.mmc: IDMAC supports 32-bit address mode. [ 2.887687] dwmmc_rockchip fe320000.mmc: Using internal DMA controller. [ 2.887702] dwmmc_rockchip fe320000.mmc: Version ID is 270a [ 2.887763] dwmmc_rockchip fe320000.mmc: DW MMC controller at irq 28,32 bit host data width,256 deep fifo [ 2.888262] dwmmc_rockchip fe320000.mmc: Got CD GPIO [ 2.901160] mmc_host mmc0: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0) [ 2.916678] mmc1: CQHCI version 5.10 [ 2.941878] mmc1: SDHCI controller on fe330000.sdhci [fe330000.sdhci] using ADMA [ 2.978696] mmc_host mmc0: Bus speed (slot 0) = 148500000Hz (slot req 150000000Hz, actual 148500000HZ div = 0) [ 3.008237] mmc1: mmc_select_hs200 failed, error -110 [ 3.008251] mmc1: error -110 whilst initialising MMC card [ 3.118200] mmc1: mmc_select_hs200 failed, error -110 [ 3.118214] mmc1: error -110 whilst initialising MMC card [ 3.126622] dwmmc_rockchip fe320000.mmc: Successfully tuned phase to 214 [ 3.126649] mmc0: new ultra high speed SDR104 SDHC card at address aaaa [ 3.127754] mmcblk0: mmc0:aaaa SP32G 29.7 GiB [ 3.130391] mmcblk0: p1 [ 3.255877] mmc1: mmc_select_hs200 failed, error -110 [ 3.255890] mmc1: error -110 whilst initialising MMC card [ 3.431916] mmc1: mmc_select_hs200 failed, error -110 [ 3.431927] mmc1: error -110 whilst initialising MMC card [ 17.372909] EXT4-fs (mmcblk0p1): mounted filesystem with writeback data mode. Opts: (null) [ 18.620355] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,errors=remount-ro On running armbian-config again to view eMMC transfer menu, only options 1 & 5 are available. I'm not very familiar with Linux-based hardware diagnosis (yet!), but but might there may be an issue with the on-board eMMC?
×
×
  • Create New...