DOCSLIB.ORG

ARM® IAR C/C++ Compiler Reference Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
ARM® IAR C/C++ Compiler Reference Guide ARM® IAR C/C++ Compiler Reference Guide for Advanced RISC Machines Ltd’s ARM Cores CARM-10 COPYRIGHT NOTICE © Copyright 1999–2004 IAR Systems. All rights reserved. No part of this document may be reproduced without the prior written consent of IAR Systems. The software described in this document is furnished under a license and may only be used or copied in accordance with the terms of such a license. DISCLAIMER The information in this document is subject to change without notice and does not represent a commitment on any part of IAR Systems. While the information contained herein is assumed to be accurate, IAR Systems assumes no responsibility for any errors or omissions. In no event shall IAR Systems, its employees, its contractors, or the authors of this document be liable for special, direct, indirect, or consequential damage, losses, costs, charges, claims, demands, claim for lost profits, fees, or expenses of any nature or kind. TRADEMARKS IAR, IAR Embedded Workbench, IAR XLINK Linker, IAR XAR Library Builder, IAR XLIB Librarian, IAR MakeApp, and IAR PreQual are trademarks owned by IAR Systems. C-SPY is a trademark registered in Sweden by IAR Systems. IAR visualSTATE is a registered trademark owned by IAR Systems. ARM and Thumb are registered trademarks of Advanced RISC Machines Ltd. Microsoft and Windows are registered trademarks of Microsoft Corporation. Intel and Pentium are registered trademarks and XScale a trademark of Intel Corporation. All other product names are trademarks or registered trademarks of their respective owners. EDITION NOTICE Tenth edition: February 2004 Part number: CARM-10 This guide applies to version 4.x of the ARM IAR Embedded Workbench™. CARM-10 Brief contents Tables ..................................................................................................................... xiii Preface .................................................................................................................... xv Part 1. Using the compiler ......................................................... 1 Getting started .................................................................................................... 3 Data storage ...................................................................................................... 11 Functions ............................................................................................................. 15 Placing code and data .................................................................................... 23 The DLIB runtime environment ............................................................... 37 Assembler language interface ................................................................... 67 Using C++ ............................................................................................................ 83 Efficient coding for embedded applications ........................................ 87 Part 2. Compiler reference .................................................... 101 Data representation ...................................................................................... 103 Segment reference ......................................................................................... 113 Compiler options ........................................................................................... 121 Extended keywords ....................................................................................... 147 Pragma directives ............................................................................................ 153 Predefined symbols ........................................................................................ 165 Intrinsic functions ........................................................................................... 171 Library functions ............................................................................................. 177 Implementation-defined behavior .......................................................... 183 iii CARM-10 IAR language extensions ............................................................................. 195 Diagnostics ......................................................................................................... 207 Index ..................................................................................................................... 209 ARM® IAR C/C++ Compiler iv Reference Guide CARM-10 Contents Tables ..................................................................................................................... xiii Preface .................................................................................................................... xv Who should read this guide ............................................................... xv How to use this guide .......................................................................... xv What this guide contains ....................................................................xvi Other documentation .........................................................................xvii Further reading .................................................................................xvii Document conventions .....................................................................xviii Typographic conventions ................................................................xviii Part 1. Using the compiler ......................................................... 1 Getting started .................................................................................................... 3 IAR language overview ........................................................................... 3 Building applications—an overview .................................................. 4 Compiling ............................................................................................. 4 Linking ................................................................................................. 4 Basic settings for project configuration .......................................... 5 Processor variant .................................................................................. 5 CPU mode ............................................................................................ 6 Interworking ......................................................................................... 6 VFP and floating-point arithmetic ....................................................... 7 Byte order ............................................................................................. 7 Optimization for speed and size ........................................................... 7 Runtime environment ........................................................................... 8 Special support for embedded systems .......................................... 9 Extended keywords .............................................................................. 9 Predefined symbols ............................................................................ 10 Special function types ........................................................................ 10 Header files for I/O ............................................................................ 10 Accessing low-level features ............................................................. 10 v CARM-10 Data storage ...................................................................................................... 11 Introduction .............................................................................................. 11 The stack and auto variables ............................................................. 11 Dynamic memory on the heap ........................................................ 13 Functions ............................................................................................................. 15 ARM and Thumb code ........................................................................ 15 Keywords for functions ........................................................................ 15 Execution in RAM ................................................................................... 16 Interrupt functions ................................................................................. 17 Interrupts and fast interrupts .............................................................. 17 Nested interrupts ................................................................................ 18 Software interrupts ............................................................................. 19 Installing interrupt functions .............................................................. 20 Interrupt operations ............................................................................ 20 Monitor functions ............................................................................... 21 C++ and special function types ......................................................... 22 Function directives ................................................................................. 22 Placing code and data .................................................................................... 23 Segments and memory ........................................................................ 23 What is a segment? ............................................................................ 23 Placing segments in memory ............................................................ 24 Customizing the linker command file ................................................ 25 Data segments
Load more

Recommended publications
  • Standard Template Library
    STANDARD TEMPLATE LIBRARY Developed By Mrs. K.M.Sanghavi STANDARD TEMPLATE LIBRARY (STL) Developed by Alexander Stepanov and Meng Lee of HP in 1979. Standard template library accepted in July 1994 into C++ ANSI Standard These are called as collection of General-purpose template classes( data structures) and functions 1 COMPONENTS OF STL Containers Algorithms Iterators 2 COMPONENTS OF STL Algorithms use iterators to interact with objects stored in containers Container Algorithm1 Algorithm 2 Object1 Object2 Iterator 1 Iterator 2 Object3 Iterator 3 Algorithm 3 3 CONTAINER Objects that hold Example : Array data (of same type) Implemented by Template Classes 4 ALGORITHM Example : These are procedures used to process the data Searching, Sorting, contained in containers. Merging, Copying, Initializing Implemented by template functions 5 ITERATOR It is an object that Used to move points to an through the element in a contents of container container They can be Connect Algorithms incremented and with Containers decremented 6 COMPONENTS OF STL Containers 7 CATEGORIES OF CONTAINERS Sequence Containers Derived Associative Containers Containers 8 CONTAINERS STL Defines 10 Containers 9 CATEGORIES OF CONTAINERS Sequence Associative Derived • vector • set • stack • deque • multiset • queue • list • map • Priority_queue • multimap 10 SEQUENCE CONTAINERS Stores elements in a linear sequence Each element is related to other elements by its position along the line They allow insertion of elements Example Element Element Element Last …….. 0 1 2 element 11 THREE TYPES OF SEQUENCE CONTAINERS vector deque list 12 Vector : Sequence Container Expandable and dynamic array Grows and shrinks in size Insertion / Deletion of elements at back Permits direct access to any element 13 Vector : Sequence Container Container Header File Iterator vector <vector> Random Access 14 vector Sequence Container Declarations ◦ vector <type> v; type: int, float, etc.
    [Show full text]
  • SEI CERT C++ Coding Standard (2016 Edition)
    SEI CERT C++ Coding Standard Rules for Developing Safe, Reliable, and Secure Systems in C++ 2016 Edition Aaron Ballman Copyright 2017 Carnegie Mellon University This material is based upon work funded and supported by the Department of Defense under Contract No. FA8721-05-C-0003 with Carnegie Mellon University for the operation of the Software Engineering Institute, a federally funded research and development center. Any opinions, findings and conclusions or recommendations expressed in this material are those of the au- thor(s) and do not necessarily reflect the views of the United States Department of Defense. References herein to any specific commercial product, process, or service by trade name, trade mark, manu- facturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation, or favoring by Carnegie Mellon University or its Software Engineering Institute. This report was prepared for the SEI Administrative Agent AFLCMC/PZM 20 Schilling Circle, Bldg 1305, 3rd floor Hanscom AFB, MA 01731-2125 NO WARRANTY. THIS CARNEGIE MELLON UNIVERSITY AND SOFTWARE ENGINEERING INSTITUTE MATERIAL IS FURNISHED ON AN “AS-IS” BASIS. CARNEGIE MELLON UNIVERSITY MAKES NO WARRANTIES OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AS TO ANY MATTER INCLUDING, BUT NOT LIMITED TO, WARRANTY OF FITNESS FOR PURPOSE OR MERCHANTABILITY, EXCLUSIVITY, OR RESULTS OBTAINED FROM USE OF THE MATERIAL. CARNEGIE MELLON UNIVERSITY DOES NOT MAKE ANY WARRANTY OF ANY KIND WITH RESPECT TO FREEDOM FROM PATENT, TRADEMARK, OR COPYRIGHT INFRINGEMENT. [Distribution Statement A] This material has been approved for public release and unlimited distribution. Please see Copyright notice for non-US Government use and distribution.
    [Show full text]
  • IAR Systems Brings Functional Safety Tools to RISC-V with Certification for IEC 61508 and ISO 26262
    Press release Date: October 20, 2020 IAR Systems brings functional safety tools to RISC-V with certification for IEC 61508 and ISO 26262 Stockholm, Sweden—October 20, 2020— IAR Systems®, the future-proof supplier of software tools and services for embedded development, further extends its strong tools offering for RISC-V by announcing a certified version of its development tools. The functional safety edition of IAR Embedded Workbench® for RISC-V will be certified by TÜV SÜD according to the requirements of IEC 61508, the international umbrella standard for functional safety, as well as ISO 26262, which is used for automotive safety-related systems. In addition, the certification covers the international standard IEC 62304, which specifies life cycle requirements for the development of medical software and software within medical devices, and the European railway standards EN 50128 and EN 50657. “We are seeing RISC-V becoming an important architecture not only in broad designs, but specifically in automotive applications,” said Stefan Skarin, CEO, IAR Systems. “By providing our development tools with certification according to ISO 26262, we enable the RISC-V community to further expand and more rapidly bring functional safety designs to the market. As a commercial tools vendor, we are able to provide global technical support as well as invest in keeping our products robust, maintained and qualified. Our certified tools will enable our customers to speed up the path to using RISC-V in safety-critical applications within automotive and other areas.” “We see a strong demand for RISC-V with safety among our customers, and the certification of IAR Embedded Workbench for RISC-V aligns perfectly with that demand,” said Frankwell Lin, President, Andes Technology.
    [Show full text]
  • IAR Systems Supports New Amazon Web Services Iot Microcontroller Operating System Amazon Freertos at Launch
    Press release Date: November 30, 2017 IAR Systems supports new Amazon Web Services IoT Microcontroller Operating System Amazon FreeRTOS at Launch Amazon FreeRTOS will be supported by the leading embedded development toolchain IAR Embedded Workbench Uppsala, Sweden—November 30, 2017—IAR Systems®, a leading supplier of software tools and services for embedded development, announces support for newly launched Internet of Things (IoT) Microcontroller Operating System, Amazon FreeRTOS. Together with Amazon Web Services (AWS), IAR Systems provides developers with easy access to high-performance, pre-integrated development tools for developing and debugging embedded and IoT-connected applications based on Amazon FreeRTOS. Amazon FreeRTOS provides tools that developers need to quickly and easily deploy a microcontroller- based connected device and develop an embedded or IoT application without having to worry about the complexity of scaling across millions of devices. Based on the FreeRTOS kernel, Amazon FreeRTOS includes software libraries which make it easy to securely connect devices locally to AWS Greengrass, directly to the cloud, and update them remotely. For new devices, developers can choose to build their embedded and IoT application on a variety of qualified microcontrollers from companies collaborating with AWS and IAR Systems, including Microchip, NXP, STMicroelectronics and Texas Instruments. Since 1983, IAR Systems’ solutions have ensured quality, reliability and efficiency in the development of over one million embedded applications. Now available for Amazon FreeRTOS users, development tools from IAR Systems deliver leading code optimizations and extensive debugging functionality. The technology is coupled with professional technical support offered globally. “AWS is pleased to be teamed with IAR Systems to provide developers with access to a high performance, pre-integrated set of development tools for developing and debugging connected applications,” says Richard Barry, Principal Engineer, Amazon Web Services, Inc.
    [Show full text]
  • Rogue Wave Standard C++ Library User's Guide and Reference
    Rogue Wave Standard C++ Library User's Guide and Reference Rogue Wave Software Corvallis, Oregon USA Standard C++ Library User's Guide and Reference for Rogue Wave's implementation of the Standard C++ Library. Based on ANSI's Working Paper for Draft Proposed International Standard for Information Systems--Programming Language C++. April 28, 1995. User's Guide Authors: Timothy A. Budd, Randy Smithey Reference Authors: Wendi Minne, Tom Pearson, and Randy Smithey Product Team: Development: Anna Dahan, Donald Fowler, Marlene Hart, Angelika Langer, Philippe Le Mouel, Randy Smithey Quality Engineering: KevinDjang, Randall Robinson, Chun Zhang Manuals: Wendi Minne, Kristi Moore, Julie Prince,Randy Smithey Support: North Krimsley Significant contributions by: Rodney Mishima Copyright © 1995-96 Rogue Wave Software, Inc. All rights reserved. Printed in the United States of America. Part # RW81-01-2-032596 Printing Date: July 1996 Rogue Wave Software, Inc., 850 SW 35th Street, Corvallis, Oregon, 97333 USA Product Information: (541) 754-5010 (800) 487-3217 Technical Support: (541) 754-2311 FAX: (541) 757-6650 World Wide Web: http://www.roguewave.com Please have your product serial number available when calling for technical support. Table of Contents 1. Introduction .........................................................................1 1.1 What is the Standard C++ Library?............................................................. 2 1.2 Does the Standard C++ Library Differ From Other Libraries? ............... 2 1.3 What are the Effects of
    [Show full text]
  • The Wrapper API's Baseline Requirements
    LASER INTERFEROMETER GRAVITATIONAL WAVE OBSERVATORY - LIGO - CALIFORNIA INSTITUTE OF TECHNOLOGY MASSACHUSETTS INSTITUTE OF TECHNOLOGY Document Type LIGO-T990097-11 - E 08/29/2000 The wrapper API’s baseline requirements James Kent Blackburn, Masha Barnes Jolien Creighton Distribution of this document: LIGO LDAS Group This is an internal working document of the LIGO Project. California Institute of Technology Massachusetts Institute of Technology LIGO Project - MS 51-33 LIGO Project - MS 20B-145 Pasadena CA 91125 Cambridge, MA 01239 Phone (818) 395-2129 Phone (617) 253-4824 Fax (818) 304-9834 Fax (617) 253-7014 E-mail: [email protected] E-mail: [email protected] WWW: http://www.ligo.caltech.edu/ Table of Contents Index file \\SIRIUS\kent\documents\LDAS\wrapperAPI\wrapperAPIReqCover.fm - printed August 29, 2000 The wrapper API’s baseline requirements James Kent Blackburn California Institute of Technology LIGO Data Analysis Group August 29, 2000 I. Introduction A. General Description: 1. The wrapperAPI is responsible for executing the advanced analysis pro- cesses which are based on MPI and executing in the LDAS distributed com- puting parallel cluster of nodes using an interpreted command language. 2. The wrapperAPI will be written entirely in C and C++. No TCL/TK will be used in this LDAS API. 3. The wrapperAPI will be initiated using the mpirun command. This command will be started solely by the mpiAPI. The mpiAPI will determine the appro- priate values for the mpirun command, as well as the appropriate commands for the wrapperAPI and pass these as command line arguments to mpirun. The wrapperAPI will interpret its own command line arguments which are automatically passed to the wrapperAPI by the mpirun command.
    [Show full text]
  • IAR Embedded Workbench® for ARM
    IAR Embedded Workbench® for ARM IAR Embedded Workbench is a set of highly sophisticated • Binary compatibility with other EABI compliant tools and easy-to-use development tools for embedded applica- • Automatic checking of MISRA C rules (MISRA C:2004) tions. It integrates the IAR C/C++ Compiler™, assembler, • Language extensions for embedded applications with linker, librarian, text editor, project manager, and C-SPY® target-speciic support Debugger in an integrated development environment • Advanced inline assembler • Support for ARM, Thumb1 and Thumb-2 processor modes (IDE). With its built-in chip-specific code optimizer, IAR • Support for the VFP9-S loating-point co-processor Embedded Workbench generates very efficient and reliable • Support for 4 Gbyte applications in all processor modes code for ARM devices. In addition to this solid technology, • Support for 64-bit long long IAR Systems also provides professional worldwide technical • 32- and 64-bit loating-point types in standard IEEE format support. • Reentrant code • Position Independent Code and Data (PIC/PID) MODULAR AND EXTENSIBLE IDE • Multiple levels of optimizations on code size and execution • A seamlessly integrated environment for building and speed allowing different transformations enabled, such as debugging embedded applications function inlining, loop unrolling etc. • Powerful project management allowing multiple projects in one workspace STATE-OF-THE-ART C-SPY® DEBUGGER • Build integration with IAR visualSTATE • Complex code and data breakpoints • Hierarchical project
    [Show full text]
  • STL) Is a Collection of Containers and Algorithms Which Is Part of the Standard C++ Library
    Containers, algorithms and more... The standard library is the collection of functions and types that is supplied with every standard-compliant C++ compiler What should be in the standard library? And equally important: what should not be? 2 Introduction to Systems Programming The standard library should: Provide basic functionality which the user can have difficulty implementing himself: Memory management Input / output Implementation-dependent information Save and simplify work: Supply useful non-primitive facilities 3 Introduction to Systems Programming The standard library cannot contain problem- specific code For example – a Student class It should contain generic classes and functions which are usable in a variety of problems: Containers – such as list, set, etc. Algorithms – such as sorting, searching Popular classes – such as string 4 Introduction to Systems Programming What are the requirements from the standard library's containers and algorithms? Simple to use Interfaces should be uniform and convenient Complete Reasonable features should be included Efficient Library code might take a large part of the execution time Extensible The user should be able to add new containers and algorithms that work with the given ones 5 Introduction to Systems Programming The containers included in the standard library should be generic We have seen several ways to implement generic containers: Using void* and pointers to functions Using templates Using subtyping and polymorphism 6 Introduction to Systems Programming
    [Show full text]
  • STL – Standard Template Library
    STL – Standard Template Library September 22, 2016 CMPE 250 STL – Standard Template Library September 22, 2016 1 / 25 STL – Standard Template Library Collections of useful classes for common data structures Ability to store objects of any type (template) Containers form the basis for treatment of data structures Container – class that stores a collection of data STL consists of 10 container classes: CMPE 250 STL – Standard Template Library September 22, 2016 2 / 25 STL Containers Sequence Container Stores data by position in linear order: First element, second element , etc. All containers Use same names for common operations Have specific operations Associate Container Stores elements by key, such as name, ID number or part number Access an element by its key which may bear no relationship to the location of the element in the container Adapter Container Contains another container as its underlying storage structure CMPE 250 STL – Standard Template Library September 22, 2016 3 / 25 STL Containers Sequence Container Vector Deque List Adapter Containers Stack Queue Priority queue Associative Container Set, multiset Map, multimap CMPE 250 STL – Standard Template Library September 22, 2016 4 / 25 How to access Components - Iterator Iterator is an object that can access a collection of like objects one object at a time. An iterator can traverse the collection of objects. Each container class in STL has a corresponding iterator that functions appropriately for the container For example: an iterator in a vector class allows random access An iterator
    [Show full text]
  • IAR C/C++ Compiler Reference Guide for V850
    IAR Embedded Workbench® IAR C/C++ Compiler Reference Guide for the Renesas V850 Microcontroller Family CV850-9 COPYRIGHT NOTICE © 1998–2013 IAR Systems AB. No part of this document may be reproduced without the prior written consent of IAR Systems AB. The software described in this document is furnished under a license and may only be used or copied in accordance with the terms of such a license. DISCLAIMER The information in this document is subject to change without notice and does not represent a commitment on any part of IAR Systems. While the information contained herein is assumed to be accurate, IAR Systems assumes no responsibility for any errors or omissions. In no event shall IAR Systems, its employees, its contractors, or the authors of this document be liable for special, direct, indirect, or consequential damage, losses, costs, charges, claims, demands, claim for lost profits, fees, or expenses of any nature or kind. TRADEMARKS IAR Systems, IAR Embedded Workbench, C-SPY, visualSTATE, The Code to Success, IAR KickStart Kit, I-jet, I-scope, IAR and the logotype of IAR Systems are trademarks or registered trademarks owned by IAR Systems AB. Microsoft and Windows are registered trademarks of Microsoft Corporation. Renesas is a registered trademark of Renesas Electronics Corporation. V850 is a trademark of Renesas Electronics Corporation. Adobe and Acrobat Reader are registered trademarks of Adobe Systems Incorporated. All other product names are trademarks or registered trademarks of their respective owners. EDITION NOTICE Ninth edition: May 2013 Part number: CV850-9 This guide applies to version 4.x of IAR Embedded Workbench® for the Renesas V850 microcontroller family.
    [Show full text]
  • FORSCHUNGSZENTRUM JÜLICH Gmbh Programming in C++ Part II
    FORSCHUNGSZENTRUM JÜLICH GmbH Jülich Supercomputing Centre D-52425 Jülich, Tel. (02461) 61-6402 Ausbildung von Mathematisch-Technischen Software-Entwicklern Programming in C++ Part II Bernd Mohr FZJ-JSC-BHB-0155 1. Auflage (letzte Änderung: 19.09.2003) Copyright-Notiz °c Copyright 2008 by Forschungszentrum Jülich GmbH, Jülich Supercomputing Centre (JSC). Alle Rechte vorbehalten. Kein Teil dieses Werkes darf in irgendeiner Form ohne schriftliche Genehmigung des JSC reproduziert oder unter Verwendung elektronischer Systeme verarbeitet, vervielfältigt oder verbreitet werden. Publikationen des JSC stehen in druckbaren Formaten (PDF auf dem WWW-Server des Forschungszentrums unter der URL: <http://www.fz-juelich.de/jsc/files/docs/> zur Ver- fügung. Eine Übersicht über alle Publikationen des JSC erhalten Sie unter der URL: <http://www.fz-juelich.de/jsc/docs> . Beratung Tel: +49 2461 61 -nnnn Auskunft, Nutzer-Management (Dispatch) Das Dispatch befindet sich am Haupteingang des JSC, Gebäude 16.4, und ist telefonisch erreich- bar von Montag bis Donnerstag 8.00 - 17.00 Uhr Freitag 8.00 - 16.00 Uhr Tel.5642oder6400, Fax2810, E-Mail: [email protected] Supercomputer-Beratung Tel. 2828, E-Mail: [email protected] Netzwerk-Beratung, IT-Sicherheit Tel. 6440, E-Mail: [email protected] Rufbereitschaft Außerhalb der Arbeitszeiten (montags bis donnerstags: 17.00 - 24.00 Uhr, freitags: 16.00 - 24.00 Uhr, samstags: 8.00 - 17.00 Uhr) können Sie dringende Probleme der Rufbereitschaft melden: Rufbereitschaft Rechnerbetrieb: Tel. 6400 Rufbereitschaft Netzwerke: Tel. 6440 An Sonn- und Feiertagen gibt es keine Rufbereitschaft. Fachberater Tel. +49 2461 61 -nnnn Fachgebiet Berater Telefon E-Mail Auskunft, Nutzer-Management, E.
    [Show full text]
  • Tools from IAR Systems for Freescale Kinetis Microcontrollers
    Tools from IAR Systems for Freescale Kinetis Microcontrollers IAR Embedded Workbench IAR KickStart Kit for Kinetis IIAR Embedded Workbench is a set of highly sophisticated and easy- IAR KickStart kit for Kinetis K60 contains all the necessary hardware to-use software development tools for Freescale Kinetis. It integrates and software for designing, developing, integrating and testing applica- the IAR C/C++ Compiler, assembler, linker, librarian, text editor, project tions. It includes: manager, and C-SPY Debugger in an integrated development environ- • 32-bit MCU module with MK60N512 MCU ment (IDE). With its built-in chip-specific code optimizer, IAR Embedded • Two elevator modules that provide power regulation circuitry, Workbench generates efficient and reliable FLASHable code for Kinetis standardized signal assignments, and act as common backplane for microcontrollers. all assembled Tower System modules Highlights: • Serial peripheral module with Ethernet, USB, RS232/485, and • Integration of Freescale MQX Software Solutions CAN interface circuitry • Power debugging for minimized power consumption • Prototyping module featuring ample perfboard area for custom • Example projects for MXQ and Tower kit circuitry • Trace debugging supporting ETM and SWD • IAR J-Link Lite for Cortex-M - a small JTAG-emulator with SWD/ • Automatic project configuration for all Kinetis devices SWO debugging support for Cortex-M devices • DVD with software development tools, example projects & RTOS BSPs, training materials and collateral • Quick Start Guide Debug probes IAR J-Link/J-Link Ultra IAR J-Link and IAR J-Link Ultra are compatible high speed JTAG/SWD probes for Kinetis microcontrollers. IAR J-Link Ultra brings better per- formance and is better suited for power debugging compared to IAR J- Link.
    [Show full text]