Getting Started with the EMAC OE SDK

Revision as of 12:55, 6 April 2015 by Bserrano (talk | contribs)
Jump to: navigation, search
TODO: {{#todo: InProgress (03.31.2015-13:42->BS+)|Brian Serrano|OE 5.0,BS}}

Put the page description text here.

General Information

The EMAC Open Embedded SDK is distributed in an archive that can be extracted and used from a Linux terminal or from within an integrated development environment such as Qt Creator.

Each SDK includes the C/C++ header files and libraries compatible with the target hardware. It also includes the C/C++ cross-compiler toolchain components necessary to compile and debug custom application code. Follow the links below to get started building and running the example projects on the target hardware.

Getting Started with the EMAC OE SDK

Connecting to a Target Board

The next step after establishing a physical connection to the board is logging in. EMAC OE Linux allows login from getty, and SSH (Secure Shell). A getty uses the serial connection or console while SSH utilizes a network connection. For more information visit the System Log In page.

Setting up the Filesystem Read-Write

To set up the root filesytem read-write, enter the following into the terminal:

root@ipac9x25:~# oemntrw

To revert back the root filesytem to read-only, enter the following into the terminal:

root@ipac9x25:~# oemntrw -r

Transferring Files

The command line syntax for transferring a file using the SSH protocol is scp file user@host:/directory. SCP or Secure Copy is a way of securely transferring files between a local and remote host. For example, to send the file example.text to the /home directory of a system with the IP address, enter the following command:

developer@ldc:~# scp example.text root@

Be aware that this copy operation will fail if the filesystem on the remote machine is mounted read-only, which is the default on most EMAC systems.



Further Information

Where to Go Next
Pages with Related Content