UDOO x86 Yocto support

Discussion in 'Yocto' started by graugans, May 14, 2017.

  1. graugans

    graugans Administrator Staff Member

    Joined:
    Sep 17, 2015
    Messages:
    328
    Likes Received:
    141
    I just added basic support for the new UDOO x86 boards. I did not tried to boot my UDOO x86 ADVANCED. Is there someone who owns an UDOO x86 BASIC?
     
    modjo and waltervl like this.
  2. graugans

    graugans Administrator Staff Member

    Joined:
    Sep 17, 2015
    Messages:
    328
    Likes Received:
    141
    Build instructions

    local/bblayers.conf
    Code:
    POKY_BBLAYERS_CONF_VERSION = "2"
    
    BBPATH = "${TOPDIR}"
    BSPDIR := "${@os.path.abspath(os.path.dirname(d.getVar('FILE', True)) + '/../..')}"
    
    BBFILES ?= ""
    BBLAYERS = " \
      ${BSPDIR}/sources/poky/meta \
      ${BSPDIR}/sources/poky/meta-poky \
      \
      ${BSPDIR}/sources/meta-openembedded/meta-oe \
      ${BSPDIR}/sources/meta-openembedded/meta-multimedia \
      ${BSPDIR}/sources/meta-openembedded/meta-python \
      ${BSPDIR}/sources/meta-openembedded/meta-networking \
      \
      ${BSPDIR}/sources/meta-qt5 \
      \
      ${BSPDIR}/sources/meta-freescale \
      ${BSPDIR}/sources/meta-freescale-3rdparty \
      ${BSPDIR}/sources/meta-freescale-distro \
      ${BSPDIR}/sources/meta-ros \
      ${BSPDIR}/sources/meta-intel \
      ${BSPDIR}/sources/meta-udoo \
    "
    
    Code:
    MACHINE=udoox86 bitbake udoo-image-full-cmdline
    
    Flash image to a USB thumb drive

    Code:
    umount /dev/sd<disk>; sudo dd if=/tmp/udoo-image-full-cmdline-udoox86-20170521180922.hddimg of=/dev/sd<disk> bs=32M
    
    Connect a USB to serial adapter
    ATTENTION: The Braswell CPU is 1.8V!!! Do not connect 3.3V!!!


    Check the UDOO x86 Docs for advice.

    • Run a terminal program like minicom
    Code:
    minicom -D /dev/ttyUSB0
    • Connect a keyboard
    • Connect an HDMI/DP Monitor
    • Plug-in the USB thumb drive
    • Power on the board
    • Enter the UEFI GUI by pressing <ESC>
    • Select the USB-Thumb drive (EFI)
    • Select install
    • switch to serial console and select the disk in the UI
     
  3. skipgeldens

    skipgeldens New Member

    Joined:
    Dec 5, 2017
    Messages:
    2
    Likes Received:
    0
    Hi, I am working with the Udoo X86 board for a project, and I am working on getting Yocto to work on this board. I found this post about your Yocto setup, but i'm having trouble implementing it. The problem is in the do_image_wic function of the udoo-image-full-cmdline image. I get the following errors:

    Code:
    ERROR: udoo-image-full-cmdline-1.0-r0 do_image_wic: No kickstart files from WKS_FILES were found: systemd-bootdisk-uuid.wks udoo-image-full-cmdline.wks. Please set WKS_FILE or WKS_FILES appropriately.
    ERROR: udoo-image-full-cmdline-1.0-r0 do_image_wic: Function failed: do_image_wic (log file is located at /media/buildmachine/Data/yocto/x86-build/tmp/work/udoox86-poky-linux/udoo-image-full-cmdline/1.0-r0/temp/log.do_image_wic.5196)
    ERROR: Logfile of failure stored in: /media/buildmachine/Data/yocto/x86-build/tmp/work/udoox86-poky-linux/udoo-image-full-cmdline/1.0-r0/temp/log.do_image_wic.5196
    ERROR: Task (/home/buildmachine/yocto/sources/meta-udoo/recipes-udoo/images/udoo-image-full-cmdline.bb:do_image_wic) failed with exit code '1'
    
    The build system can't find the needed kickstart files for wic so it seems...

    I followed this post, so all layers are included in the build, even the Freescale layers (which I don't think are needed for a X86 build)

    Any help here would be greatly appreciated!
     
  4. graugans

    graugans Administrator Staff Member

    Joined:
    Sep 17, 2015
    Messages:
    328
    Likes Received:
    141
    Could you please be so kind and post the Yocto header which is printed on console before the actual build starts. This contains the sha1 sums and branch names zou have used.
     
  5. skipgeldens

    skipgeldens New Member

    Joined:
    Dec 5, 2017
    Messages:
    2
    Likes Received:
    0
    This is my Yocto header after running 'bitbake udoo-image-full-cmdline'. I have not included the meta-qt layer, because I have no plans using QT in my project. I do have a personal layer called meta-elc in this build, and the distro is our own, but this just inherits Poky and changes some parameters. So I don't think this will interfere with the build too much...

    Code:
    bitbake udoo-image-full-cmdline
    WARNING: /home/buildmachine/yocto/sources/meta-udoo/recipes-udoo/environment/uenv_0.1.bb: Unable to get checksum for uenv SRC_URI entry uEnv.txt: file could not be found
    Parsing recipes: 100% |##############################################################################| Time: 0:00:57
    Parsing of 2688 .bb files complete (0 cached, 2688 parsed). 3482 targets, 383 skipped, 0 masked, 0 errors.
    NOTE: Resolving any missing task queue dependencies
    
    Build Configuration:
    BB_VERSION        = "1.34.0"
    BUILD_SYS         = "x86_64-linux"
    NATIVELSBSTRING   = "universal"
    TARGET_SYS        = "x86_64-poky-linux"
    MACHINE           = "udoox86"
    DISTRO            = "elcdistro"
    DISTRO_VERSION    = "v0.1"
    TUNE_FEATURES     = "m64 corei7"
    TARGET_FPU        = ""
    meta            
    meta-poky         = "pyro:072430b9b3a78b318b66371c36e2986d2ed5cba4"
    meta-oe          
    meta-multimedia  
    meta-gnome      
    meta-python      
    meta-networking  
    meta-efl          = "pyro:5e82995148a2844c6f483ae5ddd1438d87ea9fb7"
    meta-intel        = "pyro:4cd63f57820ce0e4ebd598251d3a13b5a4b9b791"
    meta-freescale    = "pyro:06178400afbd641a6709473fd21d893dcd3cfbfa"
    meta-freescale-3rdparty = "pyro:9613dbc02ca970122a01c935bc9e5789ced73a9d"
    meta-freescale-distro = "pyro:cd5c7a2539f40004f74126e9fdf08254fd9a6390"
    meta-ros          = "master:121b182599a06335c0e648d90f781e66007bcd18"
    meta-udoo         = "pyro:79350fc9baf5b75e929fd2dbd59d3e3dbd8cc402"
    meta-elc          = "pyro:d4e2e0f00cd5dc8c00ac4c664ac442e9f9a1d6d0"
    
     

Share This Page