Installing EMAC OE 4.0 SDK

TODO: {{#todo:Revise (11.15.13-15:12->KY+);(11.15.13-19:30->MD+);(02.12.14-13:25->MD-);(02.13.14-11:25->MG+)|Michael Gloff|oe 4, mg,ky,md,Review}}

TODO: This page needs information about the dependencies needing to be installed. This will have to be a generic list of dependencies which you should be able to extrapolate from our Ubuntu list (to_apt_get_install_hw). Incidentally, please change the name of that file before you post it online for the other wiki page (installing on Ubuntu). When I made that file originally, I named it hastily and never intended to share it with anyone (even internally), so it needs a better name. Also, things specifically for the LDC can be removed from it (chrome aptitude htop iftop vim-doc vim-addon-manager vim-puppet vim-scripts abs-guide screen subversion subversion-tools git git-doc git-man gitk easygit git-all svn-buildpackage w3m unrar p7zip-full cabextract ntp nmap tmux cifs-utils samba tftpd tftp expect)

Before beginning installation of the SDK, it is important that the development system has the required tools. These tools can either be command line interface (CLI) or graphical utilities. Both options are described in this guide.

Required tools

The following is a generic list of tools that need to be installed on a development machine to fully use the SDK. The method to install these tools varies according to the distribution of Linux used.

• Web browser (recommended: Mozilla Firefox or Google Chrome)
• C/C++ compiler and debugger
• wput
• minicom
• ssh client
• Archiving tool. These options are available:
  • Graphical: Ark for KDE, File Roller for GNOME
  • CLI: Tar is standard

Recommendations

The following are some recommended install options:

• The SDK should be kept in the user's home directory. For example,

# /path/to/sdk/ might be located on the filesystem at:
/home/user_name/EMAC-OE-arm-linux-gnueabi-SDK_XX.YY/

This is the location where the downloaded SDK eg. EMAC-OE-arm-linux-gnueabi-SDK_XX.YY/ will end up.

• The default SDK root folder name should be kept at its default name since this preserves the version information for the EMAC OE SDK.

Procedure

1. Download the SDK. The latest version can be found on the EMAC ftp site. Be sure to download the SDK that matches the architecture of your target system.

2. Uncompress the SDK.

   • Using a graphical archiving tool, double click the archive file and click extract. If you need assistance with this, please see the documentation for your graphical archiving tool.

   • Alternatively, you can uncompress the archive from the CLI using tar:

      developer@ldc:~$ cd /install/directory
      developer@ldc:~$ tar -xjvf /download/directory/EMAC-OE-arm-linux-gnuabi-SDK_XX.YY.rZZ.tar.bz2
     

   The list of extracted files will be output to the screen. This may take a minute.

    developer@ldc:~$ ls
   

   A subdirectory within the installation directory will be created containing the SDK:

    ...
    EMAC-OE-arm-linux-gnueabi-SDK_XX.YY/
    ...
   

Next Steps

Once the EMAC SDK is installed, the next step is to configure the SDK .