This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

PROCESSOR-SDK-Linux-OMAPL138: Unable to Boot from SD Card

Part Number: PROCESSOR-SDK-OMAPL138
Other Parts Discussed in Thread: OMAP-L138, OMAPL138

I have tried to generate a bootable SD card from the prebuilt images provided by the new Processor SDK package, both to get my head around building the SDK/images and to update the provided SD card which only contained the MCSDK.

We are in very early development stages, and thought it would be a good fit to use the newly released Processor SDK package for the OMAP-L138-LCDK board.

I've used the supplied bin/create_sdcard.sh script and can see no errors in creating the required partitions... There is a message stating that the MLO file was not found while copying the boot partition. Im not sure if this is important.

I then use the prepared SD card to boot the device, and I see the following messages:

MMC:   davinci: 0
Bad block table found at page 262080, version 0x01
Bad block table found at page 262016, version 0x01
In:    serial
Out:   serial
Err:   serial
ARM Clock : 456000000 Hz
DDR Clock : 150000000 Hz
Net:   Ethernet PHY: GENERIC @ 0x07
DaVinci-EMAC
Hit any key to stop autoboot:  0 
MMC: block number 0x1 exceeds max(0x0)
** Can't read from device 0 **

** Unable to use mmc 0:1 for fatload **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
U-Boot >

I have seen similar messages on this forum so I have tried more than one SD card...

I have also tried to use a number of different TI scripts to generate SD cards (from linux SDK package), most of which are out of data and provide incorrect parameters to sfdisk.

I have worked with beagle bone in previous projects, and did not think this would be so hard...

Would it be worthwhile providing a simple bootable ISO image file so we can simply dd into our SD card?

  • Here is the complete output of the create-sdcard.sh script...

    [linux-devkit]:~/ti/ti-processor-sdk-linux-omapl138-lcdk-04.00.00.04> sudo bin/create-sdcard.sh 
    
    ################################################################################
    
    This script will create a bootable SD card from custom or pre-built binaries.
    
    The script must be run with root permissions and from the bin directory of
    the SDK
    
    Example:
     $ sudo ./create-sdcard.sh
    
    Formatting can be skipped if the SD card is already formatted and
    partitioned properly.
    
    ################################################################################
    
    
    Available Drives to write images to: 
    
    #  major   minor    size   name 
    1:   8       16 1953514584 sdb
    2:   8       32    7777280 sdc
     
    Enter Device Number or n to exit: 2
     
    sdc was selected
    
    /dev/sdc is an sdx device
    SD Card is not correctly partitioned
    
    ################################################################################
    
            Select 2 partitions if only need boot and rootfs (most users).
            Select 3 partitions if need SDK & other content on SD card.  This is
            usually used by device manufacturers with access to partition tarballs.
    
            ****WARNING**** continuing will erase all data on sdc
    
    ################################################################################
    
    Number of partitions needed [2/3] : 2
    
     
    Now partitioning sdc with 2 partitions...
     
    
    ################################################################################
    
                    Now making 2 partitions
    
    ################################################################################
    
    1024+0 records in
    1024+0 records out
    1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.353099 s, 3.0 MB/s
    DISK SIZE - 7963934720 bytes
    
    ################################################################################
    
                    Partitioning Boot
    
    ################################################################################
    mkfs.fat 4.0 (2016-05-06)
    mkfs.fat: warning - lowercase labels might not work properly with DOS or Windows
    
    ################################################################################
    
                    Partitioning rootfs
    
    ################################################################################
    mke2fs 1.43.3 (04-Sep-2016)
    /dev/sdc2 contains a ext3 file system labelled 'rootfs'
            last mounted on Wed Aug  2 14:51:51 2017
    Proceed anyway? (y,n) y
    Creating filesystem with 1922048 4k blocks and 481440 inodes
    Filesystem UUID: 960101a4-bc28-4326-b1c9-38332a4a2c1a
    Superblock backups stored on blocks: 
            32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632
    
    Allocating group tables: done                            
    Writing inode tables: done                            
    Creating journal (16384 blocks): done
    Writing superblocks and filesystem accounting information: done 
    
    
    
    ################################################################################
    
       Partitioning is now done
       Continue to install filesystem or select 'n' to safe exit
    
       **Warning** Continuing will erase files any files in the partitions
    
    ################################################################################
    
    
    Would you like to continue? [y/n] : y
    
     
     
    Mount the partitions 
     
    Emptying partitions 
     
    
    Syncing....
    
    ################################################################################
    
            Choose file path to install from
    
            1 ) Install pre-built images from SDK
            2 ) Enter in custom boot and rootfs file paths
    
    ################################################################################
    
    Choose now [1/2] : 1
    
     
    Will now install from SDK pre-built images
    now installing:  ti-processor-sdk-linux-omapl138-lcdk-04.00.00.04
    
    ################################################################################
    
       Multiple rootfs Tarballs found
    
    ################################################################################
    
             1:tisdk-server-extra-rootfs-image-omapl138-lcdk.tar.xz
             2:tisdk-server-rootfs-image-omapl138-lcdk.tar.xz
    
    Enter Number of rootfs Tarball: 1
     
    ################################################################################
    
            Copying files now... will take minutes
    
    ################################################################################
    
    Copying boot partition
    
    MLO file not found
    
    
    u-boot.bin copied
    
    
    Copying rootfs System partition
                                                                                                                                         
    
    Syncing...
     
    Un-mount the partitions 
     
    Remove created temp directories 
     
    Operation Finished

  • I have scrapped the SD card idea for now, or until someone here can help... In the meantime, I have configured TFTP boot for the kernel and an NFS share for the filesystem.

    The kernel loads as expected using the TFTP server... So I think this means what I am writing to the SD card is valid.

    However, Im now seeing a second error when trying to load the NFS filesystem...

    VFS: Unable to mount root fs via NFS, trying floppy.

    I can see mount requests on the NFS server from the board (6 total, before the board gives up), but nothing ever makes it to the board. The board finally dies with...

    VFS: Unable to mount root fs via NFS, trying floppy.
    VFS: Cannot open root device "nfs" or unknown-block(2,0)
    Please append a correct "root=" boot option; here are the available partitions:
    1f00             128 mtdblock0  (driver?)
    1f01             512 mtdblock1  (driver?)
    1f02            2048 mtdblock2  (driver?)
    1f03          521600 mtdblock3  (driver?)
    b300         7777280 mmcblk0  driver: mmcblk
      b301           71680 mmcblk0p1 00000000-0000-0000-0000-000000000mmcblk0p1
      b302         7688192 mmcblk0p2 00000000-0000-0000-0000-000000000mmcblk0p2
    Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)

    Current uBoot env is

    autoload=no
    baudrate=115200
    bootargs=console=ttyS2,115200n8 rw noinitrd root=/dev/nfs nfsroot=192.168.1.110:/nfsroot/targetNFS,nolock,rsize=1024,wsize=1024 ip=dhcp
    bootcmd=dhcp;setenv serverip 192.168.1.110;tftpboot;bootm
    bootdelay=4
    bootfile=uImage-omapl138-lcdk.bin
    ethact=DaVinci-EMAC
    ethaddr=00:00:a0:00:fb:c7
    oldbootargs=console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootwait ip=off
    serverip=192.168.1.110
    stderr=serial
    stdin=serial
    stdout=serial
    ver=U-Boot 2010.12 (May 07 2012 - 16:09:45)
    
    Environment size: 525/65532 bytes

    Any help would be appreciated! :)

  • If I boot with TFTP for the kernel, and SD card for the rootfs, the board freezes execution due to error in /dev:

    NAND:  512 MiB
    MMC:   davinci: 0
    Bad block table found at page 262080, version 0x01
    Bad block table found at page 262016, version 0x01
    In:    serial
    Out:   serial
    Err:   serial
    ARM Clock : 456000000 Hz
    DDR Clock : 150000000 Hz
    Net:   Ethernet PHY: GENERIC @ 0x07
    DaVinci-EMAC
    Hit any key to stop autoboot:  0 
    BOOTP broadcast 1
    *** Unhandled DHCP Option in OFFER/ACK: 28
    *** Unhandled DHCP Option in OFFER/ACK: 28
    DHCP client bound to address 192.168.1.126
    Using DaVinci-EMAC device
    TFTP from server 192.168.1.110; our IP address is 192.168.1.126
    Filename 'uImage-omapl138-lcdk.bin'.
    Load address: 0xc0700000
    Loading: #################################################################
             #################################################################
             ##################################
    done
    Bytes transferred = 2397856 (2496a0 hex)
    ## Booting kernel from Legacy Image at c0700000 ...
       Image Name:   Linux-3.3.0
       Image Type:   ARM Linux Kernel Image (uncompressed)
       Data Size:    2397792 Bytes = 2.3 MiB
       Load Address: c0008000
       Entry Point:  c0008000
       Verifying Checksum ... OK
       Loading Kernel Image ... OK
    OK
    
    Starting kernel ...
    
    Uncompressing Linux... done, booting the kernel.
    Booting Linux on physical CPU 0
    Linux version 3.3.0 (gtbldadm@ubuntu-12) (gcc version 4.5.3 20110311 (prerelease) (GCC) ) #1 PREEMPT Tue Nov 5 20:19:32 EST 2013
    CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
    CPU: VIVT data cache, VIVT instruction cache
    Machine: AM18x/OMAP-L138 lcdk board
    Memory policy: ECC disabled, Data cache writeback
    BUG: mapping for 0x80000000 at 0xfffe0000 out of vmalloc space
    DaVinci da850/omap-l138/am18x variant 0x1
    Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
    Kernel command line: console=ttyS2,115200n8 rw noinitrd root=/dev/mmcblk0p2 rootfstype=ext3 rootwait ip=off
    PID hash table entries: 512 (order: -1, 2048 bytes)
    Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
    Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
    Memory: 128MB = 128MB total
    Memory: 124860k/124860k available, 6212k reserved, 0K highmem
    Virtual kernel memory layout:
        vector  : 0xffff0000 - 0xffff1000   (   4 kB)
        fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
        vmalloc : 0xc8800000 - 0xff000000   ( 872 MB)
        lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
        modules : 0xbf000000 - 0xc0000000   (  16 MB)
          .text : 0xc0008000 - 0xc0475000   (4532 kB)
          .init : 0xc0475000 - 0xc049d000   ( 160 kB)
          .data : 0xc049e000 - 0xc04cf760   ( 198 kB)
           .bss : 0xc04cf784 - 0xc04eca6c   ( 117 kB)
    SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
    NR_IRQS:245
    Console: colour dummy device 80x30
    Calibrating delay loop... 227.32 BogoMIPS (lpj=1136640)
    pid_max: default: 32768 minimum: 301
    Mount-cache hash table entries: 512
    CPU: Testing write buffer coherency: ok
    Setting up static identity map for 0xc03625a0 - 0xc03625f8
    gpiochip_add: registered GPIOs 0 to 31 on device: DaVinci
    gpiochip_add: registered GPIOs 32 to 63 on device: DaVinci
    gpiochip_add: registered GPIOs 64 to 95 on device: DaVinci
    gpiochip_add: registered GPIOs 96 to 127 on device: DaVinci
    gpiochip_add: registered GPIOs 128 to 143 on device: DaVinci
    DaVinci: 144 gpio irqs
    print_constraints: dummy: 
    NET: Registered protocol family 16
    EMAC: MII PHY configured
    bio: create slab <bio-0> at 0
    SCSI subsystem initialized
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    i2c-gpio i2c-gpio.1: using pins 20 (SDA) and 21 (SCL)
    Advanced Linux Sound Architecture Driver Version 1.0.24.
    Switching to clocksource timer0_1
    musb-hdrc: version 6.0, ?dma?, otg (peripheral+host)
    musb-hdrc musb-hdrc: dma type: dma-cppi41
    MUSB255 controller's USBSS revision = 4ea11003
    Waiting for USB PHY clock good...
    musb-hdrc musb-hdrc: USB OTG mode controller at fee00000 using DMA, IRQ 58
    NET: Registered protocol family 2
    IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
    TCP established hash table entries: 4096 (order: 3, 32768 bytes)
    TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
    TCP: Hash tables configured (established 4096 bind 4096)
    TCP reno registered
    UDP hash table entries: 256 (order: 0, 4096 bytes)
    UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
    NET: Registered protocol family 1
    RPC: Registered named UNIX socket transport module.
    RPC: Registered udp transport module.
    RPC: Registered tcp transport module.
    RPC: Registered tcp NFSv4.1 backchannel transport module.
    JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
    msgmni has been set to 243
    io scheduler noop registered (default)
    da8xx_lcdc da8xx_lcdc.0: GLCD: Found VGA_Monitor panel
    Console: switching to colour frame buffer device 80x30
    Serial: 8250/16550 driver, 3 ports, IRQ sharing disabled
    serial8250.0: ttyS0 at MMIO 0x1c42000 (irq = 25) is a AR7
    serial8250.0: ttyS1 at MMIO 0x1d0c000 (irq = 53) is a AR7
    serial8250.0: ttyS2 at MMIO 0x1d0d000 (irq = 61) is a AR7
    console [ttyS2] enabled
    brd: module loaded
    ahci ahci: forcing PORTS_IMPL to 0x1
    ahci ahci: AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl platform mode
    ahci ahci: flags: ncq sntf pm led clo only pmp pio slum part ccc 
    scsi0 : ahci_platform
    ata1: SATA max UDMA/133 mmio [mem 0x01e18000-0x01e19fff] port 0x100 irq 67
    NAND device: Manufacturer ID: 0x2c, Chip ID: 0xcc (Micron NAND 512MiB 3,3V 16-bit)
    Bad block table found at page 262080, version 0x01
    Bad block table found at page 262016, version 0x01
    Creating 4 MTD partitions on "davinci_nand.1":
    0x000000000000-0x000000020000 : "u-boot env"
    0x000000020000-0x0000000a0000 : "u-boot"
    0x0000000a0000-0x0000002a0000 : "kernel"
    0x0000002a0000-0x000020000000 : "filesystem"
    davinci_nand davinci_nand.1: controller rev. 2.5
    davinci_mdio davinci_mdio.0: davinci mdio revision 1.5
    davinci_mdio davinci_mdio.0: detected phy mask ffffff7f
    davinci_mdio.0: probed
    davinci_mdio davinci_mdio.0: phy[7]: device davinci_mdio-0:07, driver SMSC LAN8710/LAN8720
    ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
    ohci ohci.0: DA8xx OHCI
    ohci ohci.0: new USB bus registered, assigned bus number 1
    Waiting for USB PHY clock good...
    ohci ohci.0: irq 59, io mem 0x01e25000
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 1 port detected
    Initializing USB Mass Storage driver...
    usbcore: registered new interface driver usb-storage
    USB Mass Storage support registered.
    input: gpio-keys-polled as /devices/platform/gpio-keys-polled.0/input/input0
    omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0
    omap_rtc: RTC power up reset detected
    i2c /dev entries driver
    watchdog watchdog: heartbeat 60 sec
    cpuidle: using governor ladder
    cpuidle: using governor menu
    davinci_mmc davinci_mmc.0: Using DMA, 4-bit mode
    usbcore: registered new interface driver usbhid
    usbhid: USB HID core driver
    usbcore: registered new interface driver snd-usb-audio
    soc-audio soc-audio.0: ASoC: Failed to create card debugfs directory
    _regulator_get: 1-0018 supply IOVDD not found, using dummy regulator
    _regulator_get: 1-0018 supply DVDD not found, using dummy regulator
    _regulator_get: 1-0018 supply AVDD not found, using dummy regulator
    ata1: SATA link down (SStatus 0 SControl 300)
    _regulator_get: 1-0018 supply DRVDD not found, using dummy regulator
    asoc: tlv320aic3x-hifi <-> davinci-mcasp.0 mapping ok
    ALSA device list:
      #0: DA850/OMAP-L138 EVM
    TCP cubic registered
    NET: Registered protocol family 17
    console [netcon0] enabled
    netconsole: network logging started
    davinci_emac davinci_emac.1: using random MAC addr: 3e:d0:ea:de:8d:a2
    omap_rtc omap_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
    Waiting for root device /dev/mmcblk0p2...
    mmc0: new high speed SD card at address 59b4
    mmcblk0: mmc0:59b4 USD   1.87 GiB 
     mmcblk0: p1 p2
    kjournald starting.  Commit interval 5 seconds
    EXT3-fs (mmcblk0p2): using internal journal
    EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
    VFS: Mounted root (ext3 filesystem) on device 179:2.
    Freeing init memory: 160K
    Failed to mount devtmpfs at /dev: No such device
    Freezing execution.

  • The sw team have been notified. Feedback will be posted here.

    Best Regards,
    Yordan
  • Hi, Juan,

    When you burnt the SD card, did you do the additional step for OMAP-L138 as described in the document, processors.wiki.ti.com/.../Processor_SDK_Linux_create_SD_card_script

    Rex
  • Hi Rex,
    I have tried again with the additional dd step as requested, but I see the same results. Im pretty sure I had tried this previously, but I've gone through all the steps again to cover all bases.

    After the create-sdcard.sh script runs, I burn the AIS bootloader to the SD card. I have added this as a step to the create-sdcard.sh script, which runs after the removal of the created temp directories -

    if [ -e "$BOOTFILEPATH""/u-boot-omapl138-lcdk.ais" ] 
    then 
        echo "Updating with AIS bootloader..." 
        sudo dd if=$BOOTFILEPATH/u-boot-omapl138-lcdk.ais of=$DRIVE seek=117 bs=512 conv=fsync 
    fi

    The u-boot display from the board is as follows -

    NAND:  512 MiB
    MMC:   davinci: 0
    Bad block table found at page 262080, version 0x01
    Bad block table found at page 262016, version 0x01
    In:    serial
    Out:   serial
    Err:   serial
    ARM Clock : 456000000 Hz
    DDR Clock : 150000000 Hz
    Net:   Ethernet PHY: GENERIC @ 0x07
    DaVinci-EMAC
    Hit any key to stop autoboot:  0 
    reading uImage
    
    ** Unable to read "uImage" from mmc 0:1 **
    Wrong Image Format for bootm command
    ERROR: can't get kernel image!

    The following are the current u-boot variables -

    U-Boot > env print
    baudrate=115200
    bootargs=console=ttyS2,115200n8 rw noinitrd root=/dev/mmcblk0p2 rootfstype=ext3 rootwait ip=off
    bootcmd=mmc rescan 0; fatload mmc 0 0xc0700000 uImage; bootm 0xc0700000
    bootdelay=4
    bootfile="uImage"
    ethact=DaVinci-EMAC
    ethaddr=00:00:a0:00:fb:c7
    oldbootargs=console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootwait ip=off
    stderr=serial
    stdin=serial
    stdout=serial
    ver=U-Boot 2010.12 (May 07 2012 - 16:09:45)
    
    Environment size: 444/65532 bytes

    This occurs on 3 different SD cards, including the one originally supplied with the LCDK.

    Here is a listing of the partitions and their contents (taken from the re-imaged 4GB SD card supplied with the LCDK)

    Model: Generic- SD/MMC (scsi)
    Disk /dev/sdi: 3965MB
    Sector size (logical/physical): 512B/512B
    Partition Table: msdos
    Disk Flags: 
    
    Number  Start   End     Size    Type     File system  Flags
     1      1049kB  74.4MB  73.4MB  primary  fat32        boot, lba
     2      74.4MB  3949MB  3874MB  primary  ext3
    

    Partition 1 when mounted contains a single file - u-boot.bin
    Partition 2 when mounted contains the linux rootfs with an empty init file

  • The only way I can get the board to load (somewhat) is by manually adding a uImage file to the boot partition of the SD card. Now, the only uImage I have available right now, is the one I previously built with the MCSDK... Im not expecting it succeed, but hey, uboot manages to load some Kernel! It fails at the same location as my TFTP boot & NFS attempt...

    I have tried updating the u-boot commands to load zImage instead, but it is telling me it is in the wrong format (as expected I guess). I don't see a bootz command available?

    If it isnt, I guess the only way to sort this out is to build my own uImage? Currently the only pre-built images I have available (from the SDK) are:

    • da850-evm.dtb
    • da850-lcdk.dtb
    • u-boot-omapl138-lcdk.ais
    • u-boot-spl.bin-omapl138-lcdk
    • zImage-omapl138-lcdk.bin

  • OK, so first attempt at building the SDK has failed...

    I have followed the steps described here processors.wiki.ti.com/.../Processor_SDK_Building_The_SDK

    However, it seems that the bitbake fails to load a valid MACHINE variable and returns (note the INVALID compiler prefix) -

    ERROR: Failed to obtain external Linaro toolchain version: Execution of '/home/juansta/gcc-linaro-6.2.1-2016.11-x86_64_arm-linux-gnueabihf/bin/INVALID-linux-gcc -v' failed: command not found
    ERROR: Failed to obtain external Linaro toolchain version: Execution of '/home/juansta/gcc-linaro-6.2.1-2016.11-x86_64_arm-linux-gnueabihf/bin/INVALID-linux-gcc -v' failed: command not found
    ERROR: Failed to obtain external Linaro toolchain version: Execution of '/home/juansta/gcc-linaro-6.2.1-2016.11-x86_64_arm-linux-gnueabihf/bin/INVALID-linux-gcc -v' failed: command not found
    ERROR: Failed to obtain external Linaro toolchain version: Execution of '/home/juansta/gcc-linaro-6.2.1-2016.11-x86_64_arm-linux-gnueabihf/bin/INVALID-linux-gcc -v' failed: command not found
    NOTE: Your conf/bblayers.conf has been automatically updated.
    ERROR: Failed to obtain external Linaro toolchain version: Execution of '/home/juansta/gcc-linaro-6.2.1-2016.11-x86_64_arm-linux-gnueabihf/bin/INVALID-linux-gcc -v' failed: command not found
    ERROR: Failed to obtain external Linaro toolchain version: Execution of '/home/juansta/gcc-linaro-6.2.1-2016.11-x86_64_arm-linux-gnueabihf/bin/INVALID-linux-gcc -v' failed: command not found
    ERROR: Failed to obtain external Linaro toolchain version: Execution of '/home/juansta/gcc-linaro-6.2.1-2016.11-x86_64_arm-linux-gnueabihf/bin/INVALID-linux-gcc -v' failed: command not found
    ERROR: Failed to obtain external Linaro toolchain version: Execution of '/home/juansta/gcc-linaro-6.2.1-2016.11-x86_64_arm-linux-gnueabihf/bin/INVALID-linux-gcc -v' failed: command not found
    NOTE: Your conf/bblayers.conf has been automatically updated.
    ERROR: Failed to obtain external Linaro toolchain version: Execution of '/home/juansta/gcc-linaro-6.2.1-2016.11-x86_64_arm-linux-gnueabihf/bin/INVALID-linux-gcc -v' failed: command not found
    ERROR: Failed to obtain external Linaro toolchain version: Execution of '/home/juansta/gcc-linaro-6.2.1-2016.11-x86_64_arm-linux-gnueabihf/bin/INVALID-linux-gcc -v' failed: command not found
    ERROR: Failed to obtain external Linaro toolchain version: Execution of '/home/juansta/gcc-linaro-6.2.1-2016.11-x86_64_arm-linux-gnueabihf/bin/INVALID-linux-gcc -v' failed: command not found
    ERROR: Failed to obtain external Linaro toolchain version: Execution of '/home/juansta/gcc-linaro-6.2.1-2016.11-x86_64_arm-linux-gnueabihf/bin/INVALID-linux-gcc -v' failed: command not found
    ERROR: Failed to obtain external Linaro toolchain version: Execution of '/home/juansta/gcc-linaro-6.2.1-2016.11-x86_64_arm-linux-gnueabihf/bin/INVALID-linux-gcc -v' failed: command not found
    ERROR: Failed to obtain external Linaro toolchain version: Execution of '/home/juansta/gcc-linaro-6.2.1-2016.11-x86_64_arm-linux-gnueabihf/bin/INVALID-linux-gcc -v' failed: command not found
    ERROR: Failed to obtain external Linaro toolchain version: Execution of '/home/juansta/gcc-linaro-6.2.1-2016.11-x86_64_arm-linux-gnueabihf/bin/INVALID-linux-gcc -v' failed: command not found
    ERROR: Failed to obtain external Linaro toolchain version: Execution of '/home/juansta/gcc-linaro-6.2.1-2016.11-x86_64_arm-linux-gnueabihf/bin/INVALID-linux-gcc -v' failed: command not found
    ERROR: Failed to obtain external Linaro toolchain version: Execution of '/home/juansta/gcc-linaro-6.2.1-2016.11-x86_64_arm-linux-gnueabihf/bin/INVALID-linux-gcc -v' failed: command not found
    ERROR: Failed to obtain external Linaro toolchain version: Execution of '/home/juansta/gcc-linaro-6.2.1-2016.11-x86_64_arm-linux-gnueabihf/bin/INVALID-linux-gcc -v' failed: command not found
    ERROR: Failed to obtain external Linaro toolchain version: Execution of '/home/juansta/gcc-linaro-6.2.1-2016.11-x86_64_arm-linux-gnueabihf/bin/INVALID-linux-gcc -v' failed: command not found
    ERROR: Failed to obtain external Linaro toolchain version: Execution of '/home/juansta/gcc-linaro-6.2.1-2016.11-x86_64_arm-linux-gnueabihf/bin/INVALID-linux-gcc -v' failed: command not found
    ERROR:  OE-core's config sanity checker detected a potential misconfiguration.
        Either fix the cause of this error or at your own risk disable the checker (see sanity.conf).                                                                                                                                           
        Following is the list of potential problems / advisories:                                                                                                                                                                               
    
        Please set a valid MACHINE in your local.conf or environment

    This was the result of starting the build process with MACHINE=omapl138 bitbake arago-core-tisdk-image

    I have tried with a different MACHINE type (am335x-evm), and the build runs. 

    Unfortunately, I believe this issue deserves it's own thread... And maybe more investigation on my behalf (Im hoping I can find a list of valid MACHINE variables that bitbake can accept)

    However, can someone confirm Im on the right path to at least get my LCDK to boot in accordance with the new processor SDK...

    Do I need a uImage, or is there a way for uBoot to load a zImage directly? Can/Should uImage be packaged with the SDK?

  • So I tried burning the SD card ISO using the Windows tool provided... With the same results.

    This lead me to think that the SD card wasn't being used at boot time at all...

    Turns out, there was a copy of uBoot already flashed to NAND... This copy did not know how to load a zImage (bootz was not a command)...

    After realising this, I changed SW1 to not allow booting from NAND but rather boot from SD! Everything seems to be working as expected now...

    processors.wiki.ti.com/.../C6748_Development_Kit_(LCDK)