2014

First, make sure we are at the current path and have the file we just downloaded.

    $ pwd
    /home/iotchampion/Workspace
    $ ls
    edison-src-rel1-maint-rel1-ww42-14.tgz

Extract the contents of the edison-src-rel1-maint-rel1-ww42-14.tgz file you just downloaded and change directory to the one just extracted.

    $ tar xvf edison-src-rel1-maint-rel1-ww42-14.tgz
    edison-src/
    edison-src/Makefile
    edison-src/meta-intel-edison/
    edison-src/meta-intel-edison/README
    edison-src/meta-intel-edison/MAINTAINERS
            .
            .
            .
    edison-src/arduino/clloader/long-options.h
    edison-src/arduino/clloader/clloader.h
    edison-src/arduino/clloader/crctab.c
    edison-src/arduino/clloader/zmodem.h

    $ ls
    edison-src  edison-src-rel1-maint-rel1-ww42-14.tgz

    $ cd edison-src/
    $ pwd
    /home/iotchampion/Workspace/edison-src
    $ ls
    arduino  broadcom_cws  device-software  mw

Connect two USB cables to the Edison board and to the computer where the commands are executing, move the switch next to the microUSBs slots towards the microUSBs.

Use the setup.sh script that is inside the folder meta-intel-edison. This script initializes the build environment for Edison. Type

    $ ./device-software/setup.sh 
    We are building in external mode
    Extracting upstream Yocto tools in the poky/ directory from archive
    Unpacking Mingw layer to poky/meta-mingw/ directory from archive
    Unpacking Darwin layer to poky/meta-darwin/ directory from archive
    Initializing yocto build environment
    Setting up yocto configuration file (in build/conf/local.conf)
    ** Success **
    SDK will be generated for linux64 host
    Now run these two commands to setup and build the flashable image:
    source poky/oe-init-build-env
    bitbake edison-image
    *************

Configure the shell environment with the following source command

    $ source poky/oe-init-build-env

    ### Shell environment set up for builds. ###

    You can now run 'bitbake <target>'

    Common targets are:
        core-image-minimal
        core-image-sato
        meta-toolchain
        adt-installer
        meta-ide-support

    You can also run generated qemu images with a command like 'runqemu qemux86'

Verify again we are working under the right path:

    $ pwd
    /home/iotchampion/Old/edison-src/build
    $ ls
    conf

Now, we are ready to build a full Edison image with the following bitbake command.

    $ bitbake edison-image
    Loading cache: 100% |###################################################################################################| ETA:  00:00:00
    Loaded 1365 entries from dependency cache.
    NOTE: Resolving any missing task queue dependencies

    Build Configuration:
    BB_VERSION        = "1.24.0"
    BUILD_SYS         = "x86_64-linux"
            .
            .
            .
    NOTE: Tasks Summary: Attempted 3757 tasks of which 568 didn't need to be rerun and all succeeded.

    Summary: There were 26 WARNING messages shown.

It is important to build a full image for the first time before making any changes to the Edison image. Be patient, this process takes from 2 to 5 or more hours depending on the hardware of the host machine.

After successfully building the edison-image, we have to modify the postBuild.sh script in order to have the correct paths. Let's change directory and verify we are editing the correct file.

    $ ls
    bitbake.lock  cache  conf  downloads  sstate-cache  tmp
    $ cd ../../../
    $ pwd
    /home/iotchampion/Workspace/edison-src
    $ ls
    bbcache  Makefile  meta-arduino  meta-intel-edison  out

    $ ../device-software/utils/flash/postBuild.sh  
    1+0 records in
    1+0 records out
    4194304 bytes (4.2 MB) copied, 0.0030999 s, 1.4 GB/s
            .
            .
            .

    **** Done ***
    Files ready to flash in /home/iotchampion/Old/edison-src/build/toFlash/
    Run the flashall script there to start flashing.
    *************

Disconnect the two USB cables to the Edison board and the computer where the commands are executing, connect them after the execution of the script, the terminal will display Please plug and reboot the board, make sure the switch next to the microUSBs slots is-towards the microUSBs.

And finally Flash Intel Edison image

    sudo ./toFlash/flashall.sh

Wait for a few minutes as the output says, and type the following command to enter the Edison and verify everything went ok. Hit Enter a few times until the edison log in appears. The default username is root, without password.

    sudo screen /dev/ttyUSB0 115200

Let's change to our edison-src folder and verify we see these files:

    $ cd ~/Workspace/edison-src/
    $ pwd
    /home/iotchampion/Workspace/edison-src
    $ ls
    arduino  broadcom_cws  build  device-software  mw  poky

Create a directory called Patches and then switch to it

    $ mkdir Patches
    $ cd Patches
    $ pwd
    /home/iotchampion/Workspace/edison-src/Patches

and use wget to download the Real Time patches

    $ wget http://yoneken.sakura.ne.jp/share/rt_edison.tar.bz2
    --2016-01-06 13:27:36--  http://yoneken.sakura.ne.jp/share/rt_edison.tar.bz2
    Resolving yoneken.sakura.ne.jp (yoneken.sakura.ne.jp)... 219.94.129.103
    Connecting to yoneken.sakura.ne.jp (yoneken.sakura.ne.jp)|219.94.129.103|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 686080 (670K) [application/x-bzip2]
    Saving to: `rt_edison.tar.bz2'

    100%[=========================================================================================================================================================================>] 686,080      325K/s   in 2.1s    

    2016-01-06 13:27:38 (325 KB/s) - `rt_edison.tar.bz2' saved [686080/686080]

Decompress the bz2 file and see we have the following files:

    $ tar -xaf rt_edison.tar.bz2
    $ ls
    intel_mid_rpmsg.c.patch  patch-3.10.17-rt12_edison.patch  rt_edison.tar.bz2

Move the patches we have just untar to the following directory and verify they were copied.

    $ cp *.patch ../device-software/meta-edison/recipes-kernel/linux/files  
    $ ls ../device-software/meta-edison/recipes-kernel/linux/files  
    defconfig                patch-3.10.17-rt12_edison.patch
    intel_mid_rpmsg.c.patch  upstream_to_edison.patch

Move to the linux directory, one directory above the files directory where we have just copied the patches and verify the path we currently are.

    $ cd ../device-software/meta-edison/recipes-kernel/linux/
    $ pwd
    /home/iotchampion/Old/edison-src/device-software/meta-edison/recipes-kernel/linux
    $ ls    
    files  linux-yocto_3.10.bbappend

Edit de bbappend file (now we use another editor called gedit for variety purposes, assuming the edition happens under a Debian based Linux distribution; otherwise use a simple text editor like nano, vi, vim or emacs)

    $ gedit linux-yocto_3.10.bbappend

Replace the content of the file to have the following:

    FILESEXTRAPATHS_prepend := "${THISDIR}/files:"  
    COMPATIBLE_MACHINE = "edison"  
    LINUX_VERSION = "3.10.17"  
    SRCREV_machine = "c03195ed6e3066494e3fb4be69154a57066e845b"  
    SRCREV_meta = "6ad20f049abd52b515a8e0a4664861cfd331f684"  

    SRC_URI += "file://defconfig"  
    SRC_URI += "file://upstream_to_edison.patch"  
    SRC_URI += "file://patch-3.10.17-rt12_edison.patch"  
    SRC_URI += "file://intel_mid_rpmsg.c.patch"  

    do_configure() {  
      cp "${WORKDIR}/defconfig" "${B}/.config"  
    }  

    do_kernel_configme() {  
      cp "${WORKDIR}/defconfig" "${B}/.config"  
    }  

    do_patch() {  
      cd ${S}  
      git am "${WORKDIR}/upstream_to_edison.patch"  
      git apply "${WORKDIR}/patch-3.10.17-rt12_edison.patch"  
      git apply "${WORKDIR}/intel_mid_rpmsg.c.patch"  
    }

Save the file and exit.

Now, move to our edison-src root folder

    $ cd ../../../../
    $ pwd
    /home/iotchampion/Workspace/edison-src/

Configure the shell environment again

    $ source poky/oe-init-build-env

    ### Shell environment set up for builds. ###

    You can now run 'bitbake <target>'

    Common targets are:
        core-image-minimal
        core-image-sato
        meta-toolchain
        adt-installer
        meta-ide-support

    You can also run generated qemu images with a command like 'runqemu qemux86'

and get into the Kernel Configuratin

    $ bitbake virtual/kernel -c menuconfig

When first run, you will be prompted with a screen like this

Enable Control Group Support under General setup settings

General setup  --->
 -*- Control Group support  --->

Enable High Resolution Timer Support under General setup -> Timer subsystem settings

General setup  --->
 Timers subsystem  --->
  [*] High Resolution Timer Support

Enable Fully Preemptible Kernel (RT) under Processor type and features settings

Processor type and features  --->
 Preemption Model (Fully Preemptible Kernel (RT))  --->
  (X) Fully Preemptible Kernel (RT)

Enable Timer frequency to 1000 HZ under Processor type and features -> Timer frequency settings

Processor type and features  --->
 Timer frequency (100 HZ)  --->
  (X) 1000 HZ

Disable ACPI (Advanced Configuration and Power Interface) under Power management and ACPI options settings

Power management and ACPI options  --->
 [ ] ACPI (Advanced Configuration and Power Interface) Support  --

Disable APM (Advanced Power Management) BIOS support under settings

Power management and ACPI options  --->
 < > APM (Advanced Power Management) BIOS support  --->

Disable ALSA for SoC audio support under Device Drivers -> Sound card support -> Advanced Linux Sound Architecture -> ALSA for SoC audio support settings

Device Drivers  --->
 <*> Sound card support  ---> 
  < >   Advanced Linux Sound Architecture  --->

Disable Aufs (Advanced multi layered unification filesystem) support under File systems -> Miscellaneous filesystem -> Aufs (Advanced multi layered unification filesystem) support settings

File systems  --->
 [*] Miscellaneous filesystems  --->
  < >   Aufs (Advanced multi layered unification filesystem) support

Select < Save > to keep the Kernel Configuration and then select < Exit > to go back to your console

When the Kernel configuration is complete, change directory to linux-edison-standard-build folder

    $ cd tmp/work/edison-poky-linux/linux-yocto/3.10.17+gitAUTOINC+6ad20f049a_c03195ed6e-r0/linux-edison-standard-build/

and copy the Kernel configuration to these two folders

    $ cp .config /home/iotchampion/Workspace/edison-src/meta-intel-edison/meta-intel-edison-bsp/recipes-kernel/linux/files/defconfig
    $ cp .config ../linux/arch/x86/configs/i386_edison_defconfig

Go back to our edison-src folder

    $ cd ~/Workspace/edison-src/
    $ pwd
    /home/iotchampion/Workspace/edison-src

and configure the shell environment again

    $ source poky/oe-init-build-env

Force bitbake to copy the modified configuration to the actual build directory.

    $ bitbake virtual/kernel -c configure -f -v

Now our image is ready to be built.

    $ bitbake edison-image

The whole Edison image is rebuilt using the Real Time patched Kernel.

Now, we have to run the post building script.

    $ ../device-software/utils/flash/postBuild.sh

Flash Intel Edison image.

    $ sudo ./toFlash/flashall.sh

Wait for a few minutes as the output says, and type the following command to enter the Edison and verify everything went ok. Hit Enter a few times until the edison log in appears. The default username is root, without password.

    $ sudo screen /dev/ttyUSB0 115200

Once logged in run uname -a, the name of the Kernel should have been renamed with the RT tags as shown below.

PreviousIntel EdisonNext2015

Last updated