Jump to content


  • Posts

  • Joined

  • Last visited

Posts posted by Gediz

  1. 18 hours ago, Digitalman1983 said:

    Thanks for that, Gediz,


    In looking at the Olimex forum post https://www.olimex.com/forum/index.php?topic=4463.0 regarding the A13, as well as http://linux-sunxi.org/LCD it would appear that the CONFIG_VIDEO_LCD_MODE is indeed part of the configuration for U-Boot, which requires U-boot to be custom built:


    git clone git://git.denx.de/u-boot.git
    cd u-boot/
    git checkout v2015.04 -b tmp


    tar -xvf gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu.tar.xz

    make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- a64-olinuxino_defconfig

    make menuconfig


    This allows the configuration of U-boot where the LCD can be properly enabled.


    I'm working on the next step, which is properly linking the compiler to build the U-boot image, as well as adding a user patch to armbian build tools to allow use of the custom U-boot binary.  Stay tuned.


    You're welcome. If you don't mind, I'd recommend you to use a more recent U-Boot version if there isn't any special purpose to use v2015.04.


    By the way, I had to spend a little bit amount of time to integrate a custom U-Boot and Linux to Armbian for my own use case. I thought that it'd help to see what/where should i add/modify back in then. Maybe this may help you a bit. By the way, do not mind FEX. It was for a really old kernel.


    ├── config
    │   ├── boards
    │   │   └── myboard-a13.csc
    │   ├── fex
    │   │   └── olinux-som-a13.fex
    │   ├── kernel
    │   │   └── linux-sun5i-default.config
    │   └── sources
    │       └── sun5i.conf
    ├── defconfig
    │   └── u-boot
    │       └── myboard-a13_defconfig
    └── userpatches
        ├── config-myboard.conf
        └── u-boot
            └── u-boot-sunxi-legacy
                └── myboard-a13_defconfig.patch


    Just after copying an overlay like this to your Armbian build directory, then ./compile.sh myboard


    This configuration may be outdated to an extent. It's been some months.

  2. On 11/20/2020 at 7:05 PM, Digitalman1983 said:

    One additional comment,


    I noticed according to the hardware notes in armbian docs that CONFIG_VIDEO_LCD_MODE must be enabled in kernel configuration.


    I just checked my kernel configuration and that option does not exist.

    I do not know about the other issues but if i recall correctly CONFIG_VIDEO_LCD_MODE is actually an option in U-Boot, not kernel.

  3. 17 hours ago, Michael2 said:



    I'm using Armbian Linux on a Cubietruck A20 device configured as a media, file and backup server. Unfortunately while trying to fix a persistent SATA-cable connection problem I accidentally pushed the FEL button on the device. Now the device is always booting in FEL mode searching for USB devices, and I'm unable to reverse this.


    I have been looking at multiple pages about the FEL mode but I'm unable to find useful information on how to quit or exit this FEL mode and to have the cubietruck booting as it did before. Although I'm not a Linux novice, the information about FEL is quite complex and I have to admit I'm clueless about how to fix this situation. Please, any help on how to disable this FEL mode is really appreciated. It is heartbreaking to lose my server, files, music and all :-\




    Kind regards,



    I'm not familiar with Cubietruck A20 hardware but as far as I know, FEL is not something static that stays on once enabled even after a power-off or a reboot.


    On each boot process, as long as you do not hold FEL button, Boot ROM (BROM) looks for a magic string (eGON) to find a proper medium. This magic string is searched in the header part of the storage mediums attached to MMC0, NAND, MMC2 and SPI flash, respectively. If no valid eGON header is found in any of these mentioned interfaces, FEL mode is executed as a fallback.


    So, if your device it automatically jumps to the FEL mode, chances are FEL button may be somehow (i think it's unlikely) stuck or the header part of attached storage devices are either corrupt or cannot be read.

  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines