sescsen

Members
  • Content Count

    4
  • Joined

  • Last visited

  1. sescsen

    SolidRun MicroSoM rev. 1.5 does not boot

    Ok, thank you! I would like to host a wifi access point, but it seems like there is a Problem with the ti wl18xx driver modules. Is this known?
  2. sescsen

    SolidRun MicroSoM rev. 1.5 does not boot

    Thank you for your quick response, unfortunately this does not solve the problem. I am not using a HB2, so i added the line the resulting armbianEnv.txt is attached armbianEnv.txt Update: I am able to login using HDMI and a Keyboard. Serial Terminal still does not work.
  3. sescsen

    SolidRun MicroSoM rev. 1.5 does not boot

    This is my output, nothing happens after that: U-Boot 2017.11-armbian (Dec 15 2017 - 13:29:26 +0100) CPU: Freescale i.MX6SOLO rev1.3 996 MHz (running at 792 MHz) CPU: Commercial temperature grade (0C to 95C) at 32C Reset cause: POR Board: MX6 Hummingboard DRAM: 512 MiB MMC: FSL_SDHC: 0 *** Warning - bad CRC, using default environment No panel detected: default to HDMI Display: HDMI (1024x768) In: serial Out: serial Err: serial Net: FEC Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 1816 bytes read in 121 ms (14.6 KiB/s) ## Executing script at 12000000 0 bytes read in 78 ms (0 Bytes/s) 78 bytes read in 96 ms (0 Bytes/s) 37846 bytes read in 278 ms (132.8 KiB/s) 4333097 bytes read in 363 ms (11.4 MiB/s) 5236152 bytes read in 415 ms (12 MiB/s) ## Loading init Ramdisk from Legacy Image at 14800000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 4333033 Bytes = 4.1 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 18000000 Booting using the fdt blob at 0x18000000 Using Device Tree in place at 18000000, end 1800c3d5 Starting kernel ... Uncompressing Linux... done, booting the kernel.
  4. I am unable to boot the latest armbian version on my hummingboard using a MicroSoM i1 rev. 1.5. It seems to be an DTB problem. The boot error is "no valid device tree binary" Does anybody have the same problem or a solution?