The Open Source Hardware OLinuXino boards are with new Linux Kernel 5.6 scripts to move Linux OS to eMMC or SATA are included


We are pleased to announce that now the images at http://images.olimex.com/release/ are with the lates Linux Kernel 5.6

All these are build with our Olimage script.

We still keep Ubuntu Bionic 18.04 LTS distribution and didn’t move to 20.04 LTS yet.

To addition for script which set boot from eMMC we add new one which allow you to boot from SATA.

The boot from eMMC and SATA is enabled for OLinuXino boards which has SPI Flash on them like:

  • A20-OLinuXino-LIME-e16Gs16M
  • A20-OLinuXino-LIME-e4Gs16M
  • A20-OLinuXino-LIME-s16M
  • T2-OLinuXino-LIME-e8Gs16M-IND
  • T2-OLinuXino-LIME-s16M-IND
  • A20-OLinuXino-LIME2-e16Gs16M
  • A20-OLinuXino-LIME2-e4Gs16M
  • A20-OLinuXino-LIME2-s16M
  • T2-OLinuXino-LIME2-e8Gs16M-IND
  • T2-OLinuXino-LIME2-s16M-IND
  • A20-OLinuXino-MICRO-e16Gs16M
  • A20-OLinuXino-MICRO-e4Gs16M
  • A20-OLinuXino-MICRO-s16M
  • T2-OLinuXino-MICRO-e8Gs16M-IND
  • T2-OLinuXino-MICRO-s16M-IND
  • A20-SOM-e16Gs16M
  • T2-SOM-e8Gs16M-IND
  • A20-SOM204-1Gs16Me16G-MC
  • T2-SOM204-1Gs16Me4G-C-I
  • T2-SOM204-1Gs16Me8G-MC-I

To make board booting from eMMC you have to boot from SD-card then execute:

$ sudo olinuxino-sd-to-emmc

then wait until script moves the OS to eMMC, remove the SD-card and reboot.

Similar if you want to make board boot from SATA you have to boot from SD-card then execute:

$ sudo olinuxino-sd-to-sata

23 Comments (+add yours?)

  1. Focussing
    Jun 08, 2020 @ 14:04:42

    The new kernel 5.6 image A20-OLinuXino-bionic-base-20200601-141356.img is not stable on Lime2. After first startup, login and giving reboot cli command, it reboots, but hangs during startup.

    Furthermore the blog is confusing to me because I received an email message from Olimex support:
    “olinuxino-sd-to-sata makes the board boot from SPI memory AND sets the
    file system to SATA at the same time. Using this script it is not
    possible to boot from SD card and have file system on SATA, but it can
    be used as basis on what can be done to accomplish what you need.”

    Reply

    • OLIMEX Ltd
      Jun 08, 2020 @ 14:30:33

      define “not stabile”, we run these images here for days and there is no stability issues, when you report problem you have to describe all info – board revision, power supply used, attached peripherials so we have ground for speculation.
      olinuxino-sd-to-sata was included last week, so I guess your question about how to implement was answered before we have it.

      here is the result from booting A20-OLinuXino-LIME2 with latest image 5.6 login and reboot:

      https://pastebin.com/raw/4taWQZdJ

      as you can see board reboots normally, what i use is A20-OLinuXino-LIME2-e16Gs16M Rev.K
      If you do not have latest Linux kernel and image you do not need to write new card just do:

      $sudo apt update
      $sudo apt upgrade
      $sudo reboot now

      and you will have the latest up to date image

      Reply

      • Focussing
        Jun 08, 2020 @ 14:42:13

        Yesterday I sent a full detailled report at 17:18…
        I am already struggling with getting things working for days and days…

        Narrowed it down to the following simple to reproduce steps:

        board: T2-OLinuXino-LIME2-e8Gs16M-IND Rev.K2

        1 create SD-card using A20-OLinuXino-bionic-base-20200601-141356.img
        2 insert SD-card and power up board using olimex power adapter
        3 login as root/olimex
        4 enter “reboot” command on command line (leaving SD-card in the system)
        5 system starts up but hangs (see below)
        6 power cycle does not help; when flashing image to disk again, same happens

        U-Boot SPL 2020.01+olimex-1-20200414.120156 (Jan 30 2020 – 11:10:18 +0000)
        DRAM: 1024 MiB
        CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
        Loading configuration from EEPROM: OK
        Verifying data: OK
        Trying to boot from MMC2

        U-Boot 2020.01+olimex-1-20200414.120156 (Jan 30 2020 – 11:10:18 +0000) Allwinner Technology

        CPU: Allwinner A20 (SUN7I)
        ID: T2-OLinuXino-LIME2-e8Gs16M-IND Rev.K2
        SN: 00011B62
        MAC: 30:1F:9A:D0:8E:7E
        I2C: ready
        DRAM: 1 GiB
        SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
        MMC: mmc@1c0f000: 0, mmc@1c11000: 1
        Loading Environment from EXT4… OK
        HDMI connected: Setting up a 1920×1080 hdmi console (overscan 0x0)
        In: serial
        Out: vga
        Err: vga
        Allwinner mUSB OTG (Peripheral)
        Net: eth0: ethernet@1c50000
        Warning: usb_ether using MAC address from ROM
        , eth1: usb_ether
        starting USB…
        Bus usb@1c14000: USB EHCI 1.00
        Bus usb@1c14400: USB OHCI 1.0
        Bus usb@1c1c000: USB EHCI 1.00
        Bus usb@1c1c400: USB OHCI 1.0
        scanning bus usb@1c14000 for devices… EHCI timed out on TD – token=0x80008c80
        EHCI timed out on TD – token=0x80008c80
        EHCI timed out on TD – token=0x80008c80
        2 USB Device(s) found
        scanning bus usb@1c14400 for devices… 1 USB Device(s) found
        scanning bus usb@1c1c000 for devices… 1 USB Device(s) found
        scanning bus usb@1c1c400 for devices… 2 USB Device(s) found
        scanning usb for storage devices… 0 Storage Device(s) found
        Hit any key to stop autoboot: 0
        switch to partitions #0, OK
        mmc1(part 0) is current device
        Scanning mmc 1:1…
        Found U-Boot script /boot/boot.scr
        1933 bytes read in 2 ms (943.4 KiB/s)
        ## Executing script at 43100000
        Boot script loaded from mmc
        Checking for /uEnv.txt…
        Checking for /boot/uEnv.txt…
        1093 bytes read in 2 ms (533.2 KiB/s)
        Loaded environment from /boot/uEnv.txt
        Loading FIT image…
        15703987 bytes read in 866 ms (17.3 MiB/s)
        ## Loading kernel from FIT Image at 58000000 …
        Using ‘config-9243’ configuration
        Trying ‘kernel-1’ kernel subimage
        Description: Linux kernel 5.5.9-olimex
        Type: Kernel Image
        Compression: uncompressed
        Data Start: 0x580000d0
        Data Size: 7988384 Bytes = 7.6 MiB
        Architecture: ARM
        OS: Linux
        Load Address: 0x40080000
        Entry Point: 0x40080000
        Hash algo: crc32
        Hash value: ba358770
        Hash algo: sha1
        Hash value: e62c176092d9199a849b486553a89c3430e6645a
        Verifying Hash Integrity … crc32+ sha1+ OK
        ## Loading ramdisk from FIT Image at 58000000 …
        Using ‘config-9243’ configuration
        Trying ‘ramdisk-1’ ramdisk subimage
        Description: Ramdisk for kernel 5.5.9-olimex
        Type: RAMDisk Image
        Compression: Unknown Compression
        Data Start: 0x5879e6a0
        Data Size: 7279209 Bytes = 6.9 MiB
        Architecture: ARM
        OS: Linux
        Load Address: 0x4fe00000
        Entry Point: 0x4fe00000
        Hash algo: crc32
        Hash value: 8fb1e504
        Hash algo: sha1
        Hash value: 5a5f923219f91edcddd4cbb61a4d2d8581bfe4ed
        Verifying Hash Integrity … crc32+ sha1+ OK
        Loading ramdisk from 0x5879e6a0 to 0x4fe00000
        WARNING: ‘compression’ nodes for ramdisks are deprecated, please fix your .its file!
        ## Loading fdt from FIT Image at 58000000 …
        Using ‘config-9243’ configuration
        Trying ‘fdt-4’ fdt subimage
        Description: unavailable
        Type: Flat Device Tree
        Compression: uncompressed
        Data Start: 0x58ead63c
        Data Size: 42406 Bytes = 41.4 KiB
        Architecture: ARM
        Load Address: 0x4fa00000
        Hash algo: crc32
        Hash value: 674b6c56
        Hash algo: sha1
        Hash value: 8ce912f8df7ca681c86ec7a392b31226b7bdeb93
        Verifying Hash Integrity … crc32+ sha1+ OK
        Loading fdt from 0x58ead63c to 0x4fa00000
        ## Loading fdt from FIT Image at 58000000 …
        Trying ‘overlay-1’ fdt subimage
        Description: unavailable
        Type: Flat Device Tree
        Compression: uncompressed
        Data Start: 0x58ef6aa4
        Data Size: 1001 Bytes = 1001 Bytes
        Architecture: ARM
        Load Address: 0x4fa10000
        Hash algo: crc32
        Hash value: d1d51f29
        Hash algo: sha1
        Hash value: fa0c14efb55dbe4bdf8aa7241a3e600b486e3ef6
        Verifying Hash Integrity … crc32+ sha1+ OK
        Loading fdt from 0x58ef6aa4 to 0x4fa10000
        ## Loading fdt from FIT Image at 58000000 …
        Trying ‘overlay-2’ fdt subimage
        Description: unavailable
        Type: Flat Device Tree
        Compression: uncompressed
        Data Start: 0x58ef6f70
        Data Size: 436 Bytes = 436 Bytes
        Architecture: ARM
        Load Address: 0x4fa20000
        Hash algo: crc32
        Hash value: 00f3a93c
        Hash algo: sha1
        Hash value: efa518e1ffcc7c09a7d8010de6a7b363f1345b30
        Verifying Hash Integrity … crc32+ sha1+ OK
        Loading fdt from 0x58ef6f70 to 0x4fa20000
        Booting using the fdt blob at 0x4fa00000
        EHCI failed to shut down host controller.
        Loading Kernel Image
        Loading Ramdisk to 4990e000, end 49fff269 … OK
        Loading Device Tree to 49900000, end 4990d784 … OK
        Applying overlay: ‘/usr/lib/olinuxino-overlays/sun7i-a20/spi1-spidev.dtbo’…
        408 bytes read in 7 ms (56.6 KiB/s)
        Applying overlay: ‘/usr/lib/olinuxino-overlays/sun7i-a20/spi2-spidev.dtbo’…
        408 bytes read in 7 ms (56.6 KiB/s)
        Applying overlay: ‘/usr/lib/olinuxino-overlays/sun7i-a20/sun7i-a20-i2c2.dtbo’…
        726 bytes read in 7 ms (100.6 KiB/s)
        Applying overlay: ‘/usr/lib/olinuxino-overlays/sun7i-a20/sun7i-a20-spi0.dtbo’…
        1001 bytes read in 7 ms (139.6 KiB/s)
        Applying overlay: ‘/usr/lib/olinuxino-overlays/sun7i-a20/sun7i-a20-spi1.dtbo’…
        1005 bytes read in 7 ms (139.6 KiB/s)
        Applying overlay: ‘/usr/lib/olinuxino-overlays/sun7i-a20/sun7i-a20-spi2.dtbo’…
        1005 bytes read in 7 ms (139.6 KiB/s)
        Applying overlay: ‘/usr/lib/olinuxino-overlays/sun7i-a20/sun7i-a20-uart3.dtbo’…
        863 bytes read in 7 ms (120.1 KiB/s)
        Applying overlay: ‘/usr/lib/olinuxino-overlays/sun7i-a20/sun7i-a20-uart4.dtbo’…
        867 bytes read in 7 ms (120.1 KiB/s)
        Applying overlay: ‘/usr/lib/olinuxino-overlays/sun7i-a20/sun7i-a20-uart5.dtbo’…
        867 bytes read in 6 ms (140.6 KiB/s)
        Applying overlay: ‘/usr/lib/olinuxino-overlays/sun7i-a20/sun7i-a20-uart6.dtbo’…
        867 bytes read in 7 ms (120.1 KiB/s)
        Applying overlay: ‘/usr/lib/olinuxino-overlays/sun7i-a20/sun7i-a20-uart7.dtbo’…
        867 bytes read in 7 ms (120.1 KiB/s)
        Applying overlay: ‘/usr/lib/olinuxino-overlays/sun7i-a20/sun7i-a20-can.dtbo’…
        732 bytes read in 7 ms (101.6 KiB/s)

        Starting kernel …

        [ 0.003363] /cpus/cpu@0 missing clock-frequency property
        [ 0.003396] /cpus/cpu@1 missing clock-frequency property
        [ 3.056712] sun4i-usb-phy 1c13400.phy: Couldn’t request ID GPIO
        [ 3.165318] sun4i-pinctrl 1c20800.pinctrl: Couldn’t get bank PG regulator
        [ 3.172126] sun4i-pinctrl 1c20800.pinctrl: request() failed for pin 198
        [ 3.178744] sun4i-pinctrl 1c20800.pinctrl: pin-198 (1c28c00.serial) status -517
        [ 3.186058] sun4i-pinctrl 1c20800.pinctrl: could not request pin 198 (PG6) from group PG6 on device 1c20800.pinctrl
        [ 3.196574] dw-apb-uart 1c28c00.serial: Error applying setting, reverse things back
        [ 3.204337] sun4i-pinctrl 1c20800.pinctrl: Couldn’t get bank PG regulator
        [ 3.211135] sun4i-pinctrl 1c20800.pinctrl: request() failed for pin 202
        [ 3.217763] sun4i-pinctrl 1c20800.pinctrl: pin-202 (1c29000.serial) status -517
        [ 3.225076] sun4i-pinctrl 1c20800.pinctrl: could not request pin 202 (PG10) from group PG10 on device 1c20800.pinctrl
        [ 3.235764] dw-apb-uart 1c29000.serial: Error applying setting, reverse things back
        [ 3.453804] sun7i-dwmac 1c50000.ethernet: IRQ eth_wake_irq not found
        [ 3.460226] sun7i-dwmac 1c50000.ethernet: IRQ eth_lpi not found
        Loading, please wait…
        starting version 237

  2. OLIMEX Ltd
    Jun 08, 2020 @ 15:44:34

    I just try your setup T2-OLinuXino-LIME2-e8Gs16M and http://images.olimex.com/release/a20/A20-OLinuXino-bionic-base-20200601-141356.img.7z and as expected everything works fine!

    Here is boot log https://pastiebin.com/5ede2c620b584

    You can see the differences between this log and yours.

    1. you claim you write A20-OLinuXino-bionic-base-20200601-141356.img.7z but your boot log show that you start old Uboot “U-Boot SPL 2020.01+olimex-1-20200414.120156 (Jan 30 2020 – 11:10:18 +0000)” which is probably in your SPI flash on board.

    in A20-OLinuXino-bionic-base-20200601-141356.img.7z Uboot is “U-Boot SPL 2020.01+olimex-1-20200601.115346 (Jan 30 2020 – 11:10:18 +0000)”

    Then the SPI uboot loads Linux kernel 5.5.9 from your eMMC which may be or may not be written correctly also.

    Clean your eMMC Flash with this command:

    dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=100

    and in Uboot to erase SPI Flash with:

    => sf probe
    SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
    => sf erase 0 200000
    SF: 2097152 bytes @ 0x0 Erased: OK
    =>

    The two above steps are not necessary as SD-card has always boot priority so if you write correct Linux image in your card the OLinuXino will boot from the SD-card and ignore the SPI and EMMC Flash.

    What I would suggest you is to use balena-etcher to write your SD-card. Also you need to uncompress the .7z file to .img file before you write it to the SD-card.

    Then insert your SD-card and watch your boot log to see if you boot latest Uboot and Kernel. Then let us know the results.

    Reply

  3. Focussing
    Jun 08, 2020 @ 15:50:44

    Found something that might help you:

    1) created new SD-card based on A20-OLinuXino-bionic-base-20200417-140212.img (which is not present anymore on images.olimex.com in the releases/5.5 folder !!)

    2) on this SD-card created 2 files in /usr/sbin folder, contents copied from olimex github
    – olinuxino-sd-to-sata
    – library.sd

    3) power up my Lime2 board with this SD-card and tried several reboots; no problems

    4) started olinuxino-sd-to-sata

    5) after ready tried several reboots; system starts up without issues and runs fine

    6) there is a “filesystem” folder visible in the user interface, created a file in home directory and connected the SSD to a linux system, the file is there so file system is on the SSD card

    My conclusion: either apt upgrade my 5.5 release to 5.6 or creating a fresh 5.6 SD-card creates issues.

    Reply

    • OLIMEX Ltd
      Jun 08, 2020 @ 15:56:00

      Why is do difficult for you to write your card with the latest image but make such mess?
      My guess is that you write garbage to your SD card and it always boot from your eMMC/SPI

      Reply

  4. Focussing
    Jun 08, 2020 @ 16:01:41

    Found something that might help:

    1) created fresh SD-card based on A20-OLinuXino-bionic-base-20200417-140212.img (from the release/5.5 folder which is not present anymore…)

    2) created 2 files on this SD-card; content copied from olimex github olimex tools
    – olinuxino-sd-to-sata
    – library.sh

    3) powered up Lime2 board, tried few reboots; no problems as with 5.6 SD-card

    4) performed tool olinuxino-sd-to-sata, after ready reboot and create file in home folder of file system

    5) shutdown and connect SSD to linux system, file in home folder is present.

    Conclusion 1: tool works fine even with 5.5 kernel flashed SD-card
    Conclusion 2: boot with freshly created 5.6 SD-card gives issues

    Reply

  5. OLIMEX Ltd
    Jun 08, 2020 @ 16:19:26

    you logs show that you do not boot from SD-card, so you think that you boot image 5.6. but actually always boot some old image you have in the eMMC on the board

    Reply

  6. Focussing
    Jun 08, 2020 @ 19:05:25

    I did a lot of testing; could you please read this carefully, we are in a really important phase of evaluation. Many thanks on forehand.

    1) based on Lub’s replies I tested both with and without SD-card

    2) I always use Etcher to write images and do not write .7z files – am not Linux expert and also not a fool 🙂

    3) it might be that there is something in eMMC/SPI but if I write that I start with SD-card, I really do… sorry…

    4) on the above system tested new flash kernel 5.5
    around 10 reboots via command line, and 10 reboots via shutdown command & power cycle, 2 times system did not start. could there be an issue between power-on/waking-up behaviour of SD-card in compared to eMMC/SPI?

    5) tested a reboot without SD-card, no issues, so it starts from what? eMMC or SPI? how can I say?

    6) as reported last week I started with kernel 5.5 SD-card (my working system since weeks) and did the apt update and apt upgrade commands as proposed by support@olimex.com followed by olinuxino-sd-to-sata. Reboot and it hangs. So no doubts about flashing images…

    7) new situation created fresh SD-card copy for kernel 5.6;
    cleared emmc/spi (your suggestion, thanks)
    did the olinuxino-sd-to-sata
    several “shutdown now” and power cycle with SD-card => sometimes it hangs like the log below, sometimes it runs fine.
    several “reboot” with SD-card => sometimes it hangs like the log below, sometimes it runs fine.
    It is not stable.

    The filesystem is not on the SSD, however SSD drive is recognized and can be mounted.

    The log:

    ******************

    U-Boot SPL 2020.01+olimex-1-20200601.115346 (Jan 30 2020 – 11:10:18 +0000)
    DRAM: 1024 MiB
    CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
    Loading configuration from EEPROM: OK
    Verifying data: OK
    Trying to boot from MMC1

    U-Boot 2020.01+olimex-1-20200601.115346 (Jan 30 2020 – 11:10:18 +0000) Allwinner Technology

    CPU: Allwinner A20 (SUN7I)
    ID: T2-OLinuXino-LIME2-e8Gs16M-IND Rev.K2
    SN: 00011B62
    MAC: 30:1F:9A:D0:8E:7E
    I2C: ready
    DRAM: 1 GiB
    SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
    MMC: mmc@1c0f000: 0, mmc@1c11000: 1
    Loading Environment from EXT4… OK
    HDMI connected: Setting up a 1920×1080 hdmi console (overscan 0x0)
    In: serial
    Out: vga
    Err: vga
    Allwinner mUSB OTG (Peripheral)
    Net: eth0: ethernet@1c50000
    Warning: usb_ether using MAC address from ROM
    , eth1: usb_ether
    starting USB…
    Bus usb@1c14000: USB EHCI 1.00
    Bus usb@1c14400: USB OHCI 1.0
    Bus usb@1c1c000: USB EHCI 1.00
    Bus usb@1c1c400: USB OHCI 1.0
    scanning bus usb@1c14000 for devices… EHCI timed out on TD – token=0x80008c80
    EHCI timed out on TD – token=0x80008c80
    EHCI timed out on TD – token=0x80008c80
    2 USB Device(s) found
    scanning bus usb@1c14400 for devices… 1 USB Device(s) found
    scanning bus usb@1c1c000 for devices… 1 USB Device(s) found
    scanning bus usb@1c1c400 for devices… 2 USB Device(s) found
    scanning usb for storage devices… 0 Storage Device(s) found
    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
    2274 bytes read in 3 ms (740.2 KiB/s)
    ## Executing script at 43100000
    Boot script loaded from mmc
    Checking for /uEnv.txt…
    Checking for /boot/uEnv.txt…
    1093 bytes read in 2 ms (533.2 KiB/s)
    Loaded environment from /boot/uEnv.txt
    Loading FIT image…
    15755539 bytes read in 871 ms (17.3 MiB/s)
    ## Loading kernel from FIT Image at 58000000 …
    Using ‘config-9243’ configuration
    Trying ‘kernel-1’ kernel subimage
    Description: Linux kernel 5.6.14-olimex
    Type: Kernel Image
    Compression: uncompressed
    Data Start: 0x580000d0
    Data Size: 8003272 Bytes = 7.6 MiB
    Architecture: ARM
    OS: Linux
    Load Address: 0x40080000
    Entry Point: 0x40080000
    Hash algo: crc32
    Hash value: 859529c9
    Hash algo: sha1
    Hash value: e505731205391def2ce37e0e9f13fb2139621007
    Verifying Hash Integrity … crc32+ sha1+ OK
    ## Loading ramdisk from FIT Image at 58000000 …
    Using ‘config-9243’ configuration
    Trying ‘ramdisk-1’ ramdisk subimage
    Description: Ramdisk for kernel 5.6.14-olimex
    Type: RAMDisk Image
    Compression: Unknown Compression
    Data Start: 0x587a20cc
    Data Size: 7306847 Bytes = 7 MiB
    Architecture: ARM
    OS: Linux
    Load Address: 0x4fe00000
    Entry Point: 0x4fe00000
    Hash algo: crc32
    Hash value: e0b96064
    Hash algo: sha1
    Hash value: 555c44bdcedebe93989d2ca1b679a0e65063950a
    Verifying Hash Integrity … crc32+ sha1+ OK
    Loading ramdisk from 0x587a20cc to 0x4fe00000
    WARNING: ‘compression’ nodes for ramdisks are deprecated, please fix your .its file!
    ## Loading fdt from FIT Image at 58000000 …
    Using ‘config-9243’ configuration
    Trying ‘fdt-4’ fdt subimage
    Description: unavailable
    Type: Flat Device Tree
    Compression: uncompressed
    Data Start: 0x58eb86dc
    Data Size: 43302 Bytes = 42.3 KiB
    Architecture: ARM
    Load Address: 0x4fa00000
    Hash algo: crc32
    Hash value: c9a50b69
    Hash algo: sha1
    Hash value: 068ed0c0648a745ea2a821b6af44ce3bf598b09e
    Verifying Hash Integrity … crc32+ sha1+ OK
    Loading fdt from 0x58eb86dc to 0x4fa00000
    ## Loading fdt from FIT Image at 58000000 …
    Trying ‘overlay-1’ fdt subimage
    Description: unavailable
    Type: Flat Device Tree
    Compression: uncompressed
    Data Start: 0x58f033c4
    Data Size: 1001 Bytes = 1001 Bytes
    Architecture: ARM
    Load Address: 0x4fa10000
    Hash algo: crc32
    Hash value: d1d51f29
    Hash algo: sha1
    Hash value: fa0c14efb55dbe4bdf8aa7241a3e600b486e3ef6
    Verifying Hash Integrity … crc32+ sha1+ OK
    Loading fdt from 0x58f033c4 to 0x4fa10000
    ## Loading fdt from FIT Image at 58000000 …
    Trying ‘overlay-2’ fdt subimage
    Description: unavailable
    Type: Flat Device Tree
    Compression: uncompressed
    Data Start: 0x58f03890
    Data Size: 436 Bytes = 436 Bytes
    Architecture: ARM
    Load Address: 0x4fa20000
    Hash algo: crc32
    Hash value: 00f3a93c
    Hash algo: sha1
    Hash value: efa518e1ffcc7c09a7d8010de6a7b363f1345b30
    Verifying Hash Integrity … crc32+ sha1+ OK
    Loading fdt from 0x58f03890 to 0x4fa20000
    Booting using the fdt blob at 0x4fa00000
    EHCI failed to shut down host controller.
    Loading Kernel Image
    Loading Ramdisk to 49908000, end 49fffe5f … OK
    Loading Device Tree to 498fa000, end 49907b04 … OK
    Applying overlay: ‘/usr/lib/olinuxino-overlays/sun7i-a20/spi1-spidev.dtbo’…
    408 bytes read in 7 ms (56.6 KiB/s)
    Applying overlay: ‘/usr/lib/olinuxino-overlays/sun7i-a20/spi2-spidev.dtbo’…
    408 bytes read in 6 ms (66.4 KiB/s)
    Applying overlay: ‘/usr/lib/olinuxino-overlays/sun7i-a20/sun7i-a20-i2c2.dtbo’…
    726 bytes read in 7 ms (100.6 KiB/s)
    Applying overlay: ‘/usr/lib/olinuxino-overlays/sun7i-a20/sun7i-a20-spi0.dtbo’…
    1001 bytes read in 7 ms (139.6 KiB/s)
    Applying overlay: ‘/usr/lib/olinuxino-overlays/sun7i-a20/sun7i-a20-spi1.dtbo’…
    1005 bytes read in 7 ms (139.6 KiB/s)
    Applying overlay: ‘/usr/lib/olinuxino-overlays/sun7i-a20/sun7i-a20-spi2.dtbo’…
    1005 bytes read in 7 ms (139.6 KiB/s)
    Applying overlay: ‘/usr/lib/olinuxino-overlays/sun7i-a20/sun7i-a20-uart3.dtbo’…
    863 bytes read in 7 ms (120.1 KiB/s)
    Applying overlay: ‘/usr/lib/olinuxino-overlays/sun7i-a20/sun7i-a20-uart4.dtbo’…
    867 bytes read in 8 ms (105.5 KiB/s)
    Applying overlay: ‘/usr/lib/olinuxino-overlays/sun7i-a20/sun7i-a20-uart5.dtbo’…
    867 bytes read in 7 ms (120.1 KiB/s)
    Applying overlay: ‘/usr/lib/olinuxino-overlays/sun7i-a20/sun7i-a20-uart6.dtbo’…
    867 bytes read in 7 ms (120.1 KiB/s)
    Applying overlay: ‘/usr/lib/olinuxino-overlays/sun7i-a20/sun7i-a20-uart7.dtbo’…
    867 bytes read in 7 ms (120.1 KiB/s)
    Applying overlay: ‘/usr/lib/olinuxino-overlays/sun7i-a20/sun7i-a20-can.dtbo’…
    732 bytes read in 7 ms (101.6 KiB/s)

    Starting kernel …

    [ 0.003402] /cpus/cpu@0 missing clock-frequency property
    [ 0.003435] /cpus/cpu@1 missing clock-frequency property
    [ 3.133978] sun4i-usb-phy 1c13400.phy: Couldn’t request ID GPIO
    [ 3.219965] sun4i-pinctrl 1c20800.pinctrl: Couldn’t get bank PG regulator
    [ 3.226799] sun4i-pinctrl 1c20800.pinctrl: request() failed for pin 198
    [ 3.233426] sun4i-pinctrl 1c20800.pinctrl: pin-198 (1c28c00.serial) status -517
    [ 3.240742] sun4i-pinctrl 1c20800.pinctrl: could not request pin 198 (PG6) from group PG6 on device 1c20800.pinctrl
    [ 3.251261] dw-apb-uart 1c28c00.serial: Error applying setting, reverse things back
    [ 3.259028] sun4i-pinctrl 1c20800.pinctrl: Couldn’t get bank PG regulator
    [ 3.265829] sun4i-pinctrl 1c20800.pinctrl: request() failed for pin 202
    [ 3.272460] sun4i-pinctrl 1c20800.pinctrl: pin-202 (1c29000.serial) status -517
    [ 3.279794] sun4i-pinctrl 1c20800.pinctrl: could not request pin 202 (PG10) from group PG10 on device 1c20800.pinctrl
    [ 3.290490] dw-apb-uart 1c29000.serial: Error applying setting, reverse things back
    Loading, please wait…
    starting version 237
    [ 5.178884] lima 1c40000.gpu: IRQ ppmmu2 not found
    [ 5.178897] lima 1c40000.gpu: IRQ ppmmu3 not found
    [ 5.179145] lima 1c40000.gpu: IRQ pp2 not found
    [ 5.179154] lima 1c40000.gpu: IRQ pp3 not found

    ******************

    It hangs around this point

    When starting without SD-card, it sometimes hangs also and it sometimes runs okay. It seems a bit more stable than starting with SD-card…
    When it runs okay this is the first part of the log; it looks like it boots from SSD.
    First the SSD gets a timeout, then it is found.

    ******************

    U-Boot SPL 2020.01+olimex-1-20200601.115346 (Jan 30 2020 – 11:10:18 +0000)
    DRAM: 1024 MiB
    CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
    Loading configuration from EEPROM: OK
    Verifying data: OK
    Trying to boot from sunxi SPI

    U-Boot 2020.01+olimex-1-20200601.115346 (Jan 30 2020 – 11:10:18 +0000) Allwinner Technology

    CPU: Allwinner A20 (SUN7I)
    ID: T2-OLinuXino-LIME2-e8Gs16M-IND Rev.K2
    SN: 00011B62
    MAC: 30:1F:9A:D0:8E:7E
    I2C: ready
    DRAM: 1 GiB
    SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
    MMC: mmc@1c0f000: 0, mmc@1c11000: 1
    Loading Environment from EXT4…
    ** Unable to use mmc 1:auto for loading the env **
    Loading Environment from FAT… Unable to use mmc 1:0… HDMI connected: Setting up a 1920×1080 hdmi console (overscan 0x0)
    In: serial
    Out: vga
    Err: vga
    Allwinner mUSB OTG (Peripheral)
    Net: eth0: ethernet@1c50000
    Warning: usb_ether using MAC address from ROM
    , eth1: usb_ether
    starting USB…
    Bus usb@1c14000: USB EHCI 1.00
    Bus usb@1c14400: USB OHCI 1.0
    Bus usb@1c1c000: USB EHCI 1.00
    Bus usb@1c1c400: USB OHCI 1.0
    scanning bus usb@1c14000 for devices… EHCI timed out on TD – token=0x80008c80
    EHCI timed out on TD – token=0x80008c80
    EHCI timed out on TD – token=0x80008c80
    2 USB Device(s) found
    scanning bus usb@1c14400 for devices… 1 USB Device(s) found
    scanning bus usb@1c1c000 for devices… 1 USB Device(s) found
    scanning bus usb@1c1c400 for devices… 2 USB Device(s) found
    scanning usb for storage devices… 0 Storage Device(s) found
    Hit any key to stop autoboot: 0
    switch to partitions #0, OK
    mmc1(part 0) is current device
    ** No partition table – mmc 1 **
    Card did not respond to voltage select!
    scanning bus for devices…
    Target spinup took 0 ms.
    AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
    flags: ncq stag pm led clo only pmp pio slum part ccc apst
    Device 0: (0:0) Vendor: ATA Prod.: KINGSTON SA400S3 Rev: SBFK
    Type: Hard Disk
    Capacity: 114473.4 MB = 111.7 GB (234441648 x 512)
    timeout exit!

    Device 0: (0:0) Vendor: ATA Prod.: KINGSTON SA400S3 Rev: SBFK
    Type: Hard Disk
    Capacity: 114473.4 MB = 111.7 GB (234441648 x 512)
    … is now current device
    Scanning scsi 0:1…
    Found U-Boot script /boot/boot.scr
    2274 bytes read in 7 ms (316.4 KiB/s)
    ## Executing script at 43100000
    Boot script loaded from scsi
    Checking for /uEnv.txt…
    Checking for /boot/uEnv.txt…

    ******************

    Almost every time it does a check on the disk (why?) even when a proper “shutdown now” is performed

    [ OK ] Mounted Kernel Configuration File System.
    [ OK ] Started Create Static Device Nodes in /dev.
    [ OK ] Started Apply Kernel Variables.
    [ OK ] Started Set the console keyboard layout.
    [ OK ] Started Journal Service.
    [ OK ] Started udev Coldplug all Devices.te)
    Checking in progress on 1 disk (20.8% complete)

    The SSD becomes the file system (checked that with a file I placed on the SSD).

    8) I will make another copy of my 5.5 SD-card (my whole sw development system is on there) which will take a while and do the apt update/upgrade cycle again. That has to work out of the box otherwise I have a lot of work to install all tools again. It is always not funny to get a system up and running after installing a new image…

    9) sorry but for me it is not clear what olinuxino-sd-to-sata exactly does:
    Olimex support:
    “olinuxino-sd-to-sata makes the board boot from SPI memory AND sets the
    file system to SATA at the same time. Using this script it is not
    possible to boot from SD card and have file system on SATA, but it can
    be used as basis on what can be done to accomplish what you need.”

    Blog above:
    “Similar if you want to make board boot from SATA you have to boot from SD-card then execute: $ sudo olinuxino-sd-to-sata”

    Looking forward to hearing from you.

    We are evaluating 2 systems right now for future developments; LIME2 board (in configurations like T2-OLinuXino-LIME2-e8Gs16M-IND and A20-OlinuXino-Lime2-n8G), and A20SOM board.
    We would preferably have a similar setup that works identical on both boards, with respect to startup and to have the file system residing on SSD because of large data gathering and access speed.

    Reply

    • Lub
      Jun 09, 2020 @ 08:16:15

      It is important to format eMMC and SPI with the commands that Tsvetan posted. After that re-install the image to the eMMC with the script. My fear is that some boot information from previous releases remained on the memory and the installer doesn’t format the memory properly before new install.

      Reply

      • Ungf
        Jun 09, 2020 @ 12:27:12

        To check, whether the right image is written to the correct offsets on SD card and flash, you should get a hash for the image, using, for instance, “md5sum” command line tool. Then, after you have written the image to SD card using the “dd” command line tool, use “dd” again, but now using the SD card as your input file and restrict your reading using “offset=0” and “count=[number of blocks to match image size]” parameters and pipe the “dd” output to the “md5sum” command. If hashes don’t match, then there might be a problem with the SD card itself or with the process writing to it. Same procedure with eMMC.

  7. Vincenzo
    Jun 11, 2020 @ 12:41:15

    Are there any plans to support also openwrt building in the olimage script?

    Reply

  8. onekk
    Jul 02, 2020 @ 18:40:41

    VGA output is working with this new images?

    Reply

  9. Michal
    Jul 12, 2020 @ 18:33:29

    There are Focal (Ubuntu 20.04 LTS) images generated in repository, In article is mentioned “We still keep Ubuntu Bionic 18.04 LTS distribution and didn’t move to 20.04 LTS yet.”
    What is missing/failing in Focal images please ?

    Reply

    • OLIMEX Ltd
      Jul 14, 2020 @ 19:12:51

      When the article was written there were no Ubuntu 20.04 images, many people still prefer 18.04 so we will keep both for a while (for the same reason I keep 18.04 on my desktop) lot of things stop working when I installed 20.04 on my laptop, FreeCad for instance still uses Python 2.7 and disappeared from the left side Dock, now I have to run it from cli…

      Reply

  10. Michal
    Jul 15, 2020 @ 10:53:31

    Thank you for the clarification. Do you experience HW related issues with headless-server deployments related to Ubuntu 20.04 and A20-LIME2 please ?

    Reply

    • OLIMEX Ltd
      Jul 15, 2020 @ 11:13:55

      I’m not sure I understand your question, how hardware related issues will be related to particular software? If the issue is in hardware it will be there no matter what software you run on it.

      Reply

  11. mauricio
    Jul 16, 2020 @ 07:19:34

    Hello

    I’ve installed A13-OLinuXino-buster-base-20200701-210856.img.7z on my A13-OlinuXino rev.F board. (micro SD card)

    At first boot it recognizes Realtek rtl8192cu wifi module

    But at second and later boot it wont

    Sometimes (at first boot) it detects my home WiFi network, sometimes not

    What can it be ? How to solve or debug ?

    Thanks !

    Reply

  12. Michal
    Jul 16, 2020 @ 13:23:31

    In my understanding HW related issues connected with SW controlling that HW are e.g. inability to use that HW, HW unstability (e.g. data transfer errors), maintenance malfunctions, hot-plug issues, etc. So anything related exactly LIME2+distro.
    In other words, I am not asking for experience related to user applications like FreeCad who are not LIME2 specific.

    Reply

  13. stable
    Aug 01, 2020 @ 21:19:37

    I’ve been using armbian on my Lime2 and wanted to try the new image. Downloaded the minimal buster image and burned to sd card. All went fine but cannot get past login — tried root as login & 1234 as password, used ‘root 1234’ for both login and password and other combinations but nothing. If you could point out what I’m doing wrong it would be most appreciated.

    Reply

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: