Jump to content

Steve Medley

Members
  • Posts

    5
  • Joined

  • Last visited

Posts posted by Steve Medley

  1. env print output:

    Exynos5422 # env print
    baudrate=115200
    bootargs=fb_x_res=1280 fb_y_res=720 vout=hdmi led_blink=1
    bootcmd=    cfgload;    mmc rescan 0:1; mmc rescan 0:2;    if run loadbootscript_1;         then run bootscript;     else        if run loadbootscript_2;           then run bootscript;        else            run default_bootcmd;        fi ;    fi ;
    bootdelay=1
    bootscript=source 40008000
    copy_uboot_emmc2sd=emmc open 0;movi r z f 0 40000000;emmc close 0;movi w f 1 40000000;emmc open 0;movi r z b 0 40000000;emmc close 0;movi w b 1 40000000;emmc open 0;movi r z u 0 40000000;emmc close 0;movi w u 1 40000000;emmc open 0;movi r z t 0 40000000;emmc close 0;movi w t 1 40000000;mmc write 1 0x40008000 0x4CF 0x20;
    copy_uboot_sd2emmc=movi r f 0 40000000;emmc open 1;movi w z f 1 40000000;emmc close 1;movi r b 0 40000000;emmc open 1;movi w z b 1 40000000;emmc close 1;movi r u 0 40000000;emmc open 1;movi w z u 1 40000000;emmc close 1;movi r t 0 40000000;emmc open 1;movi w z t 1 40000000;emmc close 1;mmc write 1 0x40008000 0x4CF 0x20;
    default_bootcmd=echo >>> Run Default Bootcmd <<<;movi read kernel 0 40008000;movi read rootfs 0 41000000 100000;bootz 40008000 41000000
    env_erase=mmc write 0 0x40008000 0x4CF 0x20;
    loadbootscript_1=echo >>> Load Boot Script from mmc 0:1 <<<;fatload mmc 0:1 40008000 boot.scr
    loadbootscript_2=echo >>> Load Boot Script from mmc 0:2 <<<;fatload mmc 0:2 40008000 boot.scr
    loadbootscript_3=echo >>> Load Boot Script from mmc 1:1 <<<;fatload mmc 1:1 40008000 boot.scr
    loadbootscript_4=echo >>> Load Boot Script from mmc 1:2 <<<;fatload mmc 1:2 40008000 boot.scr
    rootfslen= 100000
    stderr=serial
    stdin=serial
    stdout=serial
    
    Environment size: 1657/16380 bytes
  2.  

     

    Ext4 support is missing in odroid-specific u-boot config - added with a patch, will need a new test image

     

    Thanks. I quickly realised that was the problem when i typed help at the prompt and found the ext4load command missing.

     

    Going to download the sources next so i can build my own test images and get a bit more familiar with the build process. I have built my own Armbian images in the past for CB2, but that was before it was even called Armbian and only supported CB2 and cubietruck. A lot has changed since then

  3. OK. I finally got to boot up the image. Got the following:

    U-Boot 2012.07 (Oct 20 2016 - 10:51:36) for Exynos5422
    
    CPU: Exynos5422 Rev0.1 [Samsung SOC on SMP Platform Base on ARM CortexA7]
    APLL = 800MHz, KPLL = 800MHz
    MPLL = 532MHz, BPLL = 825MHz
    
    Board: HardKernel ODROID
    DRAM:  2 GiB
    WARNING: Caches not enabled
    
    TrustZone Enabled BSP
    BL1 version: /
    VDD_KFC: 0x44
    LDO19: 0xf2
    
    Checking Boot Mode ... SDMMC
    MMC:   S5P_MSHC2: 0, S5P_MSHC0: 1
    MMC Device 0: 7.4 GiB
    MMC Device 1: 29.1 GiB
    MMC Device 2: MMC Device 2 not found
    there are pending interrupts 0x00000001
    *** Warning - bad CRC, using default environment
    
    In:    serial
    Out:   serial
    Err:   serial
    Net:   No ethernet found.
    Press quickly 'Enter' twice to stop autoboot:  0 
    
    ** Unable to use mmc 0:1 for fatload **
    Unknown command 'ext4load' - try 'help'
    Unknown command 'ext4load' - try 'help'
    >>> Load Boot Script from mmc 0:1 <<<
    
    ** Unable to use mmc 0:1 for fatload **
    >>> Load Boot Script from mmc 0:2 <<<
    ** Partition 2 not valid on device 0 **
    
    ** Unable to use mmc 0:2 for fatload **
    >>> Run Default Bootcmd <<<
    reading kernel..device 0 Start 1263, Count 16384 
    MMC read: dev # 0, block # 1263, count 16384 ... 16384 blocks read: OK
    completed
    reading RFS..device 0 Start 17647, Count 2048 
    MMC read: dev # 0, block # 17647, count 2048 ... 2048 blocks read: OK
    completed
    Bad Linux ARM zImage magic!
    Exynos5422 # 
    
    

    Going to look into it a bit further...

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines