DOCSLIB.ORG

Yocto Project Application Developer's Guide Is for the 1.6.3 Release of the Yocto Project

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Yocto Project Application Developer's Guide Is for the 1.6.3 Release of the Yocto Project Jessica Zhang, Intel Corporation <[email protected]> by Jessica Zhang Copyright © 2010-2015 Linux Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-Share Alike 2.0 UK: England & Wales [http://creativecommons.org/licenses/by-sa/2.0/uk/] as published by Creative Commons. Manual Notes • This version of the Yocto Project Application Developer's Guide is for the 1.6.3 release of the Yocto Project. To be sure you have the latest version of the manual for this release, go to the Yocto Project documentation page [http://www.yoctoproject.org/documentation] and select the manual from that site. Manuals from the site are more up-to-date than manuals derived from the Yocto Project released TAR files. • If you located this manual through a web search, the version of the manual might not be the one you want (e.g. the search might have returned a manual much older than the Yocto Project version with which you are working). You can see all Yocto Project major releases by visiting the Releases [https://wiki.yoctoproject.org/wiki/Releases] page. If you need a version of this manual for a different Yocto Project release, visit the Yocto Project documentation page [http://www.yoctoproject.org/ documentation] and select the manual set by using the "ACTIVE RELEASES DOCUMENTATION" or "DOCUMENTS ARCHIVE" pull-down menus. • To report any inaccuracies or problems with this manual, send an email to the Yocto Project discussion group at [email protected] or log into the freenode #yocto channel. Table of Contents 1. Introduction ............................................................................................................................ 1 2. The Application Development Toolkit (ADT) ............................................................................. 2 2.1. The Cross-Development Toolchain ................................................................................ 2 2.2. Sysroot ........................................................................................................................ 2 2.3. Eclipse Yocto Plug-in .................................................................................................... 2 2.4. The QEMU Emulator .................................................................................................... 2 2.5. User-Space Tools ......................................................................................................... 3 3. Preparing for Application Development ................................................................................... 4 3.1. Installing the ADT and Toolchains ................................................................................ 4 3.1.1. Using the ADT Installer ..................................................................................... 4 3.1.2. Using a Cross-Toolchain Tarball .......................................................................... 6 3.1.3. Using BitBake and the Build Directory ............................................................... 7 3.2. Setting Up the Cross-Development Environment .......................................................... 7 3.3. Securing Kernel and Filesystem Images ....................................................................... 8 3.3.1. Getting the Images ........................................................................................... 8 3.3.2. Extracting the Root Filesystem .......................................................................... 9 3.4. Optionally Building a Toolchain Installer ....................................................................... 9 4. Optionally Customizing the Development Packages Installation ............................................. 11 4.1. Package Management Systems .................................................................................. 11 4.2. Configuring the PMS .................................................................................................. 11 5. Using the Command Line ..................................................................................................... 13 5.1. Autotools-Based Projects ............................................................................................ 13 5.1.1. Creating and Running a Project Based on GNU Autotools ................................. 13 5.1.2. Passing Host Options ...................................................................................... 15 5.2. Makefile-Based Projects ............................................................................................. 15 iii Chapter 1. Introduction Welcome to the Yocto Project Application Developer's Guide. This manual provides information that lets you begin developing applications using the Yocto Project. The Yocto Project provides an application development environment based on an Application Development Toolkit (ADT) and the availability of stand-alone cross-development toolchains and other tools. This manual describes the ADT and how you can configure and install it, how to access and use the cross-development toolchains, how to customize the development packages installation, how to use command line development for both Autotools-based and Makefile-based projects, and an introduction to the Eclipse™ IDE Yocto Plug-in. Note The ADT is distribution-neutral and does not require the Yocto Project reference distribution, which is called Poky. This manual, however, uses examples that use the Poky distribution. 1 Chapter 2. The Application Development Toolkit (ADT) Part of the Yocto Project development solution is an Application Development Toolkit (ADT). The ADT provides you with a custom-built, cross-development platform suited for developing a user-targeted product application. Fundamentally, the ADT consists of the following: • An architecture-specific cross-toolchain and matching sysroot both built by the OpenEmbedded build system. The toolchain and sysroot are based on a Metadata [http://www.yoctoproject.org/ docs/1.6.3/dev-manual/dev-manual.html#metadata] configuration and extensions, which allows you to cross-develop on the host machine for the target hardware. • The Eclipse IDE Yocto Plug-in. • The Quick EMUlator (QEMU), which lets you simulate target hardware. • Various user-space tools that greatly enhance your application development experience. 2.1. The Cross-Development Toolchain The Cross-Development Toolchain [http://www.yoctoproject.org/docs/1.6.3/dev-manual/dev- manual.html#cross-development-toolchain] consists of a cross-compiler, cross-linker, and cross- debugger that are used to develop user-space applications for targeted hardware. This toolchain is created either by running the ADT Installer script, a toolchain installer script, or through a Build Directory [http://www.yoctoproject.org/docs/1.6.3/dev-manual/dev- manual.html#build-directory] that is based on your Metadata configuration or extension for your targeted device. The cross-toolchain works with a matching target sysroot. 2.2. Sysroot The matching target sysroot contains needed headers and libraries for generating binaries that run on the target architecture. The sysroot is based on the target root filesystem image that is built by the OpenEmbedded build system and uses the same Metadata configuration used to build the cross- toolchain. 2.3. Eclipse Yocto Plug-in The Eclipse IDE is a popular development environment and it fully supports development using the Yocto Project. When you install and configure the Eclipse Yocto Project Plug-in into the Eclipse IDE, you maximize your Yocto Project experience. Installing and configuring the Plug-in results in an environment that has extensions specifically designed to let you more easily develop software. These extensions allow for cross-compilation, deployment, and execution of your output into a QEMU emulation session. You can also perform cross-debugging and profiling. The environment also supports a suite of tools that allows you to perform remote profiling, tracing, collection of power data, collection of latency data, and collection of performance data. For information about the application development workflow that uses the Eclipse IDE and for a detailed example of how to install and configure the Eclipse Yocto Project Plug-in, see the "Working Within Eclipse [http://www.yoctoproject.org/docs/1.6.3/dev-manual/dev-manual.html#adt- eclipse]" section of the Yocto Project Development Manual. 2.4. The QEMU Emulator The QEMU emulator allows you to simulate your hardware while running your application or image. QEMU is made available a number of ways: • If you use the ADT Installer script to install ADT, you can specify whether or not to install QEMU. 2 The Application Development Toolkit (ADT) • If you have cloned the poky Git repository to create a Source Directory [http://www.yoctoproject.org/ docs/1.6.3/dev-manual/dev-manual.html#source-directory] and you have sourced the environment setup script, QEMU is installed and automatically available. • If you have downloaded a Yocto Project release and unpacked it to create a Source Directory [http://www.yoctoproject.org/docs/1.6.3/dev-manual/dev-manual.html#source-directory] and you have sourced the environment setup script, QEMU is installed and automatically available. • If you have installed the cross-toolchain tarball and you have sourced the toolchain's setup environment script, QEMU is also installed and automatically available. 2.5. User-Space Tools User-space tools are included as part of the distribution.
Load more

Recommended publications
  • Toolchains Instructor: Prabal Dutta Date: October 2, 2012
    EECS 373: Design of Microprocessor-Based Systems Fall 2012 Lecture 3: Toolchains Instructor: Prabal Dutta Date: October 2, 2012 Note: Unless otherwise specified, these notes assume: (i) an ARM Cortex-M3 processor operating in little endian mode; (ii) the ARM EABI application binary interface; and (iii) the GNU GCC toolchain. Toolchains A complete software toolchain includes programs to convert source code into binary machine code, link together separately assembled/compiled code modules, disassemble the binaries, and convert their formats. Binary program file (.bin) Assembly Object Executable files (.s) files (.o) image file objcopy ld (linker) as objdump (assembler) Memory layout Disassembled Linker code (.lst) script (.ld) Figure 0.1: Assembler Toolchain. A typical GNU (GNU's Not Unix) assembler toolchain includes several programs that interact as shown in Figure 0.1 and perform the following functions: • as is the assembler and it converts human-readable assembly language programs into binary machine language code. It typically takes as input .s assembly files and outputs .o object files. • ld is the linker and it is used to combine multiple object files by resolving their external symbol references and relocating their data sections, and outputting a single executable file. It typically takes as input .o object files and .ld linker scripts and outputs .out executable files. • objcopy is a translation utility that copies and converts the contents of an object file from one format (e.g. .out) another (e.g. .bin). • objdump is a disassembler but it can also display various other information about object files. It is often used to disassemble binary files (e.g.
    [Show full text]
  • Linux from Scratch Version 6.2
    Linux From Scratch Version 6.2 Gerard Beekmans Linux From Scratch: Version 6.2 by Gerard Beekmans Copyright © 1999–2006 Gerard Beekmans Copyright (c) 1999–2006, Gerard Beekmans All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: • Redistributions in any form must retain the above copyright notice, this list of conditions and the following disclaimer • Neither the name of “Linux From Scratch” nor the names of its contributors may be used to endorse or promote products derived from this material without specific prior written permission • Any material derived from Linux From Scratch must contain a reference to the “Linux From Scratch” project THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Linux From Scratch - Version 6.2 Table of Contents Preface
    [Show full text]
  • Anatomy of Cross-Compilation Toolchains
    Embedded Linux Conference Europe 2016 Anatomy of cross-compilation toolchains Thomas Petazzoni free electrons [email protected] Artwork and Photography by Jason Freeny free electrons - Embedded Linux, kernel, drivers - Development, consulting, training and support. http://free-electrons.com 1/1 Thomas Petazzoni I CTO and Embedded Linux engineer at Free Electrons I Embedded Linux specialists. I Development, consulting and training. I http://free-electrons.com I Contributions I Kernel support for the Marvell Armada ARM SoCs from Marvell I Major contributor to Buildroot, an open-source, simple and fast embedded Linux build system I Living in Toulouse, south west of France Drawing from Frank Tizzoni, at Kernel Recipes 2016 free electrons - Embedded Linux, kernel, drivers - Development, consulting, training and support. http://free-electrons.com 2/1 Disclaimer I I am not a toolchain developer. Not pretending to know everything about toolchains. I Experience gained from building simple toolchains in the context of Buildroot I Purpose of the talk is to give an introduction, not in-depth information. I Focused on simple gcc-based toolchains, and for a number of examples, on ARM specific details. I Will not cover advanced use cases, such as LTO, GRAPHITE optimizations, etc. I Will not cover LLVM free electrons - Embedded Linux, kernel, drivers - Development, consulting, training and support. http://free-electrons.com 3/1 What is a cross-compiling toolchain? I A set of tools that allows to build source code into binary code for
    [Show full text]
  • GCC Toolchain Eclipse Setup Guide
    !"#$ % '#((#()*!+,-.#)/$01234 GCC Toolchain Eclipse Setup Guide WP0001 Version 5 September 23, 2020 Copyright © 2017-2020 JBLopen Inc. All rights reserved. No part of this document and any associated software may be reproduced, distributed or transmitted in any form or by any means without the prior written consent of JBLopen Inc. Disclaimer While JBLopen Inc. has made every attempt to ensure the accuracy of the information contained in this publication, JBLopen Inc. cannot warrant the accuracy of completeness of such information. JBLopen Inc. may change, add or remove any content in this publication at any time without notice. All the information contained in this publication as well as any associated material, including software, scripts, and examples are provided “as is”. JBLopen Inc. makes no express or implied warranty of any kind, including warranty of merchantability, noninfringement of intellectual property, or fitness for a particular purpose. In no event shall JBLopen Inc. be held liable for any damage resulting from the use or inability to use the information contained therein or any other associated material. Trademark JBLopen, the JBLopen logo, TREEspanTM and BASEplatformTM are trademarks of JBLopen Inc. All other trademarks are trademarks or registered trademarks of their respective owners. Contents 1 Overview 1 1.1 About Eclipse ............................................. 1 2 Eclipse Setup Guide (Windows) 2 2.1 MSYS2 Installation .......................................... 2 2.2 Eclipse Installation .......................................... 11 2.3 Toolchain Installation ......................................... 16 2.4 Environment Variable Setup ..................................... 17 2.4.1 PATH Environnement Variable Setup ........................... 17 3 Eclipse Setup Guide (Linux) 22 3.1 Eclipse Installation .......................................... 22 3.2 Toolchain Installation ......................................... 27 3.3 GNU Make Installation .......................................
    [Show full text]
  • The GNU Toolchain for ARM Targets HOWTO Wookey Chris Rutter Jeff Sutherland Paul Webb
    This chapter contains information on building a GNU toolchain for ARM targets. The GNU Toolchain for ARM targets HOWTO Wookey Chris Rutter Jeff Sutherland Paul Webb This document contains information on setting up a GNU toolchain for ARM targets. It details both some pre-compiled toolchains which you can install, and how to compile your own toolchain, as either a native or a cross-compiler. 1. Credits This document is based on the work of Chris Rutter (now, sadly, deceased) who’s ’Building the GNU toolchain for ARM targets’ document was gospel for some time. It eventually became out of date so Wookey (<[email protected]>) updated it and gave it a substantion rewrite, adding the pre-built toolchain info at the same time. Paul Webb (<[email protected]>) did the initial conversion to DocBook, Phil 1 The GNU Toolchain for ARM targets HOWTO Blundell (<[email protected]>) provided info on the current state of the art and comments on the draft. Jeff Sutherland (<[email protected]>) then fixed the bits that were still wrong, and now maintains the doc, along with Wookey. Thanx to all. As well as being on-line as a stand-alone HOWTO, this document is also available as a chapter of the book: A ’Guide to ARMLinux for Developers’ (http://www.aleph1.co.uk/armlinux/thebook.html) 2 This chapter contains information on building a GNU toolchain for ARM targets. 1. Toolchain overview The toolchain actually consists of a number of components. The main one is the compiler itself gcc, which can be native to the host or a cross-compiler.
    [Show full text]
  • Exploring the Construction of a Domain-Aware Toolchain for High-Performance Computing
    Exploring the Construction of a Domain-Aware Toolchain for High-Performance Computing Patrick McCormick, Christine Sweeney, Nick Moss, Dean Prichard, Samuel K. Gutierrez, Kei Davis, Jamaludin Mohd-Yusof Los Alamos National Laboratory Los Alamos, NM, USA Abstract—The push towards exascale computing has sparked in such a way that we can maintain the benefits of a general- a new set of explorations for providing new productive pro- purpose toolchain but also maintain a domain awareness within gramming environments. While many efforts are focusing on the entire toolchain. Scout is a strict superset of the C and the design and development of domain-specific languages (DSLs), C++ languages and extends the general-purpose toolchain few have addressed the need for providing a fully domain-aware to maintain this domain context throughout the compilation toolchain. Without such domain awareness critical features for process. This step is critical to enable support for a produc- achieving acceptance and adoption, such as debugger support, pose a long-term risk to the overall success of the DSL approach. tive and complete, domain-aware environment for developing, In this paper we explore the use of language extensions to debugging, and profiling applications. design and implement the Scout DSL and a supporting toolchain infrastructure. We highlight how language features and the A. Domain-Specific Languages software design methodologies used within the toolchain play a significant role in providing a suitable environment for DSL Although domain-specific languages have only recently development. become popular in the high-performance computing (HPC) research community, they have been a common part of com- Keywords—Domain Specific Language, Compiler, Debugging, puting for decades [2].
    [Show full text]
  • Migrating to Swift from Flash and Actionscript
    ©Radoslava Leseva Adams & Hristo Lesev Migrating to Swift from Flash and ActionScript Radoslava Leseva Adams Hristo Lesev ©Radoslava Leseva Adams & Hristo Lesev Contents at a Glance About the Authors ...................................................................................................xxi About the Technical Reviewer ..............................................................................xxiii Acknowledgments .................................................................................................xxv Preface ................................................................................................................xxvii ■ Part I: Tool Migration ..........................................................................1 ■ Chapter 1: Setting Up Your Environment ............................................................... 3 ■ Chapter 2: Hello, Xcode! ...................................................................................... 15 ■ Chapter 3: Introducing the Xcode Debugger ....................................................... 39 ■ Chapter 4: Additional Development Tools ............................................................51 ■ Part II: Workfl ow Migration .............................................................. 69 ■ Chapter 5: “Hello, Swift!”—A Tutorial for Building an iOS App ...........................71 ■ Chapter 6: Adding a More Complex UI ...............................................................105 ■ Chapter 7: Concurrency .....................................................................................171
    [Show full text]
  • LFS-BOOK.Pdf
    Linux From Scratch Версия 7.3 Автор Gerard Beekmans Редакторы Matthew Burgess и Bruce Dubbs Перевод Иван Лабутин Linux From Scratch: Версия 7.3 by Автор Gerard Beekmans, Редакторы Matthew Burgess и Bruce Dubbs, Перевод Иван Лабутин Copyright © 1999-2013 Gerard Beekmans Copyright © 1999-2013, Gerard Beekmans Все права защищены. Эта книга выпущена под лицензией Creative Commons License. Команды для компьютера могут быть извлечены из книги под лицензией MIT License. Linux® зарегистрированная торговая марка Linus Torvalds. Linux From Scratch - Версия 7.3 Содержание Пролог ......................................................................................................................... viii i. Предисловие ........................................................................................................ viii ii. Кому адресована эта книга? ............................................................................... ix iii. Целевые архитектуры LFS .................................................................................. x iv. LFS и стандарты .................................................................................................. x v. Пояснения к выбранным пакетам ..................................................................... xii vi. Необходимые знания ....................................................................................... xvii vii. Требования к хост-системе ........................................................................... xviii viii. Соглашения, используемые в книге .............................................................
    [Show full text]
  • Entertainment Software Association
    Long Comment Regarding a Proposed Exemption Under 17 U.S.C. 1201 [ ] Check here if multimedia evidence is being provided in connection with this comment Item 1. Commenter Information The Entertainment Software Association (“ESA”) represents all of the major platform providers and nearly all of the major video game publishers in the United States.1 It is the U.S. association exclusively dedicated to serving the business and public affairs needs of companies that publish computer and video games for video game consoles, personal computers, and the Internet. Any questions regarding these comments should be directed to: Cory Fox Simon J. Frankel Ehren Reynolds Lindsey L. Tonsager ENTERTAINMENT SOFTWARE ASSOCIATION COVINGTON & BURLING LLP 575 7th Street, NW One Front Street Suite 300 35th Floor Washington, DC 20004 San Francisco, CA 94111 Telephone: (202) 223-2400 Telephone: (415) 591-6000 Facsimile: (202) 223-2401 Facsimile: (415) 591-6091 Item 2. Proposed Class Addressed Proposed Class 19: Jailbreaking—Video Game Consoles Item 3. Overview A. Executive Summary Proposed Class 19 is virtually identical to the video game console “jailbreaking” exemption that the Librarian denied in the last rulemaking proceeding. As in the last proceeding, “the evidentiary record fail[s] to support a finding that the inability to circumvent access controls on video game consoles has, or over the course of the next three years likely would have, a substantial adverse impact on the ability to make noninfringing uses.”2 Proponents offer no more than the same de minimis, hypothetical, 1 See http://www.theesa.com/about-esa/members/ (listing ESA’s members).
    [Show full text]
  • RISC-V Software Ecosystem
    RISC-V Software Ecosystem Andrew Waterman UC Berkeley [email protected]! Tethered vs. Standalone Systems § Tethered systems are those that cannot stand alone - They depend on a host system to boot - They may not have complete I/O facilities § RISC-V HW implementations at Berkeley are test chips and so are tethered § Working on software infrastructure for both kinds of systems 2 Tethered RISC-V Systems RISC-V Target x86 Host (runs proxy kernel) HTIF (runs frontend server) § Proxy Kernel runs on RISC-V target machine - Supports a single user process - I/O-related system calls are forwarded to host - Implements subset of Linux ABI § Frontend Server runs on host machine - Executes I/O syscalls on behalf of proxy kernel - Serves as boot loader (loads kernel ELF image into target memory) § Host-Target Interface (HTIF) - Simple protocol for host to interact with target state 3 Software Implementations of RISC-V ISA Spike ISA Simulator § ISA interpreter; models tethered RISC-V systems § Named for golden spike that marked completion of transcontinental railroad - Designed to be the golden model for functional correctness § Reasonably fast but designed to be very easy to modify § Github: https://github.com/ucb-bar/riscv-isa-sim 5 ANGEL JavaScript-based ISA Simulator § Simulates an RV64IMA system § Boots Linux § Implemented purely client-side in JavaScript § Designed for education & outreach § Challenging to implement when only numeric type is 64-bit IEEE float! § 13 MIPS & rising on Chrome 39.0 § riscv.org/angel 6 QEMU Full-System Simulator § RV64G port of popular full-system simulator § Device support - 8250 UART console - Virtio for network, disks, etc.
    [Show full text]
  • A Compiler Toolchain for Data Intensive Scientific Workflows
    A COMPILER TOOLCHAIN FOR DISTRIBUTED DATA INTENSIVE SCIENTIFIC WORKFLOWS A Dissertation Submitted to the Graduate School of the University of Notre Dame in Partial Fulfillment of the Requirements for the Degree of Doctor of Philosophy by Peter Bui Dr. Douglas Thain, Director Graduate Program in Computer Science and Engineering Notre Dame, Indiana June 2012 © Copyright by Peter Bui 2012 All Rights Reserved A COMPILER TOOLCHAIN FOR DISTRIBUTED DATA INTENSIVE SCIENTIFIC WORKFLOWS Abstract by Peter Bui With the growing amount of computational resources available to researchers today and the explosion of scientific data in modern research, it is imperative that scientists be able to construct data processing applications that harness these vast computing systems. To address this need, I propose applying concepts from tradi- tional compilers, linkers, and profilers to the construction of distributed workflows and evaluate this approach by implementing a compiler toolchain that allows users to compose scientific workflows in a high-level programming language. In this dissertation, I describe the execution and programming model of this compiler toolchain. Next, I examine four compiler optimizations and evaluate their effectiveness at improving the performance of various distributed workflows. Afterwards, I present a set of linking utilities for packaging workflows and a group of profiling tools for analyzing and debugging workflows. Finally, I discuss modifi- cations made to the run-time system to support features such as enhanced prove- nance information and garbage collection. Altogether, these components form a compiler toolchain that demonstrates the effectiveness of applying traditional compiler techniques to the challenges of constructing distributed data intensive scientific workflows. CONTENTS FIGURES .
    [Show full text]
  • Getting the Renesas Synergy™ Platform Toolchain up and Running
    BASICS OF THE RENESAS SYNERGY TM PLATFORM Richard Oed 2020.04 02 CHAPTER 4 GETTING THE RENESAS SYNERGY™ PLATFORM TOOLCHAIN UP AND RUNNING CONTENTS 4 GETTING THE RENESAS SYNERGY™ PLATFORM TOOLCHAIN UP AND RUNNING 03 4.1 Introduction to the Synergy Solutions Gallery 03 4.2 Downloading and Installing e2 studio and the Synergy Software Package 04 4.2.1 Download of e2 studio and the SSP 04 4.2.2 Installing the Tools Using the Platform Installer 05 4.2.3 Installing the Tools Using the Standalone Installers 07 4.2.4 Starting for the First Time 10 4.2.5 Keeping Your Installation Up-To-Date 11 4.3 Downloading and Installing the IAR Embedded Workbench® for Renesas Synergy™ 12 4.3.1 Download of the Various Installers 12 4.3.2 Installing the Toolchain Using the Platform Installer 13 4.3.3 Installing the Toolchain Using the Standalone Installers 15 4.3.4 Starting for the First Time 17 4.3.5 Keeping Your Installation Up-To-Date 20 4.4 Installing the IAR Compiler into e2 studio™ 20 4.5 Summary 20 Disclaimer 21 03 4 GETTING THE RENESAS SYNERGY™ PLATFORM TOOLCHAIN UP AND RUNNING What you will learn in this chapter: ¡ Where to get and how to install the toolchain(s) for the Synergy Platform. ¡ Steps to be performed during the first startup of the Integrated Solutions Development Environment (ISDE). In this chapter we will download and install the tools necessary to work on software projects for the Synergy Platform. You have the choice between two different toolchains: The e 2 studio ISDE with the Synergy Software Package (SSP) or the IAR Embedded Workbench® for Renesas Synergy™ (IAR EW for Synergy) together with the Synergy Standalone Configurator (SSC) and the SSP.
    [Show full text]