DOCSLIB.ORG

Vectorcast/RSP for C/C++

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Vectorcast/RSP for C/C++ USER'S GUIDE Version 6.4 New editions of this guide incorporate all material added or changed since the previous edition. Update packages may be used between editions. The manual printing date changes when a new edition is printed. The contents and format of this manual are subject to change without notice. Generated: 10/1/2017, 8:10 PM Rev: cb0043d Part Number: User's Guide for VectorCAST/C++ RSP v.6.4 VectorCAST is a trademark of Vector Software, Inc. © Copyright 2017, Vector Software, Inc. All rights reserved. No part of the material protected by this copyright notice may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying, recording, or by any informational storage and retrieval system, without written permission from the copyright owner. U.S. Government Restricted Rights This computer software and related documentation are provided with Restricted Rights. Use, duplication or disclosure by the Government is subject to restrictions as set forth in the governing Rights in Technical Data and Computer Software clause of DFARS 252.227-7015 (June 1995) and DFARS 227.7202-3(b). Manufacturer is Vector Software, Inc. East Greenwich RI 02818, USA. Vector Software reserves the right to make changes in specifications and other information contained in this document without prior notice. Contact Vector Software to determine whether such changes have been made. Third-Party copyright notices are contained in the file: 3rdPartyLicenses.txt, located in the VectorCAST installation directory. 2 Table of Contents INTRODUCTION 10 About This Manual 11 Introduction 11 Overview 11 VectorCAST/RSP Concepts 11 Harness Architecture 11 RSP Communication Overview 12 RSP Communication Details 13 Execute Commands 14 Flags 18 Execution Methods 21 USING VECTORCAST/RSP 22 Introduction 23 Combining Host- and Target-based Testing 23 CLICAST - Command Line VectorCAST 23 QuickStart 23 Command Format 24 The C/C++ Options 26 The Target Options 29 CLICAST-Only Options 41 TARGET REFERENCE 43 Analog Devices VisualDSP 44 Configuration 44 Target Execution 46 ARM RVDS 48 Configuration 48 Target Execution 48 Target Debug Execution 50 Code Composer Studio 52 Configuration 52 Target Execution with Code Composer Studio 4.0 53 Target Execution with Code Composer Studio 3.3 55 Target Execution with Code Composer Studio 2 57 DSP/BIOS support on Code Composer Studio 3.3 and 4.x 61 Configuration 61 3 DSP/BIOS Configuration 61 Code Composer Studio on ezDSP28335 target board 65 Configuration 65 Target Execution with Code Composer Studio 3.3 67 Target Execution with Debug in Code Composer Studio 3.3 68 Code Composer Studio on DSK 6713 target board 69 Configuration 69 DSP/BIOS Configuration 69 Target Execution with Code Composer Studio 3.3 73 Target Execution with Debug in Code Composer Studio 3.3 74 Code Composer Studio on OMAP 35x EVM target board 75 Configuration 75 DSP/BIOS Configuration 75 Running in a Heterogeneous Multi-core environment with Code Composer Studio 3.3 79 Target Execution with Code Composer Studio 3.3 81 Target Execution with Debug in Code Composer Studio 3.3 82 Code Composer Studio v4.2.4 on TI Stellaris EKT-LM3S9B92 EVB 83 Target Configuration 83 Configuration 83 Target Execution with Code Composer Studio 4.2 85 Target Debug Execution in Code Composer Studio 4.x 87 Code Composer Studio v4.2.4 on TI TMS570LS31xHercules USB Stick 91 Target Configuration 91 Configuration 91 Target Execution with CCS 4.2 on the TMS570LS31x USB Stick 94 Target Debug Execution in Code Composer Studio 4.x 96 CodeWarrior DSP56800E 103 Configuration 103 Target Execution 105 Target Debug Execution 106 CodeWarrior StarCore SC140e 108 Configuration 108 Target Execution 109 Target Debug Execution 109 CodeWarrior for HC12 113 Configuration 113 Banked Memory Model 116 Target Execution 117 Target Debug Execution 118 CodeWarrior for HCS08 119 Configuration 119 Target Simulator Execution 123 Target Simulator Debug Execution 124 CodeWarrior for MPC 5554 126 Configuration 126 4 Target Execution 127 Target Debug Execution 128 CodeWarrior for MPC 8315 129 CodeWarrior USB TAP Installation 129 Configuration 133 Target Execution 134 Target Debug Execution 136 CodeWarrior for MPC5121 138 Configuration 138 Target Execution 139 Target Debug Execution 142 Cosmic 68HC12 and HCS12X 143 Configuration for 68HC12 143 Configuration for HCS12X 145 Target Execution 149 Target Debug Execution 151 Cosmic STM8 152 Configuration for Cosmic STM8 on ZAP Simulator 152 Configuration for Cosmic STM8 on STVD Simulator 153 Target Execution 154 Target Debug Execution 155 EVP for VD3204x 156 Configuration 156 Fujitsu Softune for FFMC Chips 159 Configuration 159 Target Execution 160 Target Debug Execution 160 Fujitsu Softune Simulator 161 Configuration 161 Target Execution 162 Target Debug Execution 162 Green Hills Simulator/Bare Target 163 Configuration 163 Configuration for a Target Board 163 Target Execution 164 Target Execution with Green Hills Multi Debugger 164 Improving Target Execution Speed 165 Green Hills INTEGRITY Simulator 167 Configuration 167 Target Execution 167 Target Execution with Green Hills Multi Debugger 168 Improving Target Execution Speed 168 Green Hills INTEGRITY mpserv 169 Configuration 169 Target Execution 171 5 Target Execution with Green Hills Multi Debugger 171 Improving Target Execution Speed 171 Green Hills INTEGRITY rtserv 172 Configuration 172 Target Execution 174 Target Execution with Green Hills Multi Debugger 175 Improving Target Execution Speed 176 HighTec TriCore-gcc 178 Configuration 178 Target Execution 181 Target Debug Execution 182 IAR Embedded Workbench 3.x MSP430 183 Configuration 183 Target Execution 184 Target Debug Execution 185 IAR Embedded Workbench 6.0MSP430X Large Memory Model 5.x 187 Configuration 187 Target Execution 189 Target Debug Execution 189 IAR Embedded Workbench 4.x ARM 9 192 Configuration 192 Target Execution 194 Target Debug Execution 195 IAR Embedded Workbench 5.x ARM 9 198 Configuration 198 Target Execution 200 Target Debug Execution 201 IAR Embedded Workbench v6.3for Amtel SAM3N 204 Configuration 204 Target Execution 206 Target Debug Execution 207 IAR Embedded Workbench for dsPIC 209 Configuration 209 Target Execution 211 Target Debug Execution 212 IAR Embedded Workbench for PIC24 target 214 Configuration 214 Target Execution 215 Target Debug Execution 217 IAR Embedded Workbench 5.x for Amtel AVR 220 Configuration 220 Target Execution 221 Target Debug Execution 222 Keil 224 6 Configuration for the C166 224 Configuration for the C51 227 Target Execution 229 Target Debug Execution 229 Keil for ARM 231 Configuration 231 Target Execution 232 Target Debug Execution 233 Keil for ARM Cortex M3 235 Configuration 235 Instrumentation Trace Macrocell (ITM) Configuration 236 Integration Notes 238 Target Execution 239 Target Debug Execution 239 Lauterbach TRACE32 242 Configuration 242 Target Execution 244 Target Debug Execution 244 Microchip MPLAB dsPIC (PIC30) and PIC24 246 Configuration 246 Target Execution 247 Target Debug Execution 248 Microchip MPLAB C30for PIC24 on Explorer 16 249 Configuration 249 Target Execution 250 Target Debug Execution 253 NEC V850 254 Configuration 254 Target Execution 257 Target Debug Execution 257 Paradigm for 80186 259 Configuration 259 Target Execution 261 Target Debug Execution 262 Paradigm for SC520 264 Configuration 264 Target Connections and Configuration 264 Target Execution 267 Target Debug Execution 268 QNX Neutrino & QNX Momentics 270 Configuration 270 Target Execution 271 Target Debug Execution 271 Renesas HEW – M16C/R8C 273 Configuring for Renesas HEW – M16C/R8C 273 7 Target Execution 273 Target Debug Execution 282 Troubleshooting 283 Compatibility 283 Renesas HEW SuperH (SH) chips 285 Configuration for Renesas HEW - SH 285 Target Execution 286 Target Debug Execution 288 Troubleshooting 288 Compatibility 290 TASKING 56k C Compiler 291 Configuration 291 Target Execution 291 Target Debug Execution 292 TASKING 563xx C Compiler 293 Configuration 293 Target Execution 293 Target Debug Execution 294 TASKING C166 Classic 296 Configuration 296 Target Execution 297 Target Debug Execution 297 TASKING C166 VX 298 Configuration 298 Target Execution 299 Target Debug Execution 299 TASKING TriCore 300 Configuration 300 Target Execution 301 Target Debug Execution 301 Tasking C166 Classic withTRACE32 Simulator on Linux 302 Configuration 302 Target Execution 302 Target Debug Execution 303 TriMedia 305 Configuration 305 Target Execution 307 Target Debug Execution 307 Wind River Diab/SingleStep Simulator 309 Configuration 309 Target Execution 309 Wind River Diab withTRACE32 Simulator on Linux 312 Configuration 312 Target Execution 313 Target Debug Execution 313 8 Wind River vxWorks 315 Overview 315 Starting vxSim in Tornado 315 Setting up the Command Line Tools for Tornado 316 Starting vxSim in Workbench 316 Setting up the Command Line Tools for Workbench 317 Configuration 318 Target Execution 318 Target Execution with vxWorks 653 319 Example Using vxSim 320 Example Using SBC 323 Troubleshooting a vxWorks Target Connection 326 Improving I/O Performance 331 Debugging with Tornado Crosswind on Windows 333 EXECUTION METHODS 336 EXECUTION VIA A REMOTE SHELL 337 Introduction 337 Execution via a Remote Shell 337 Introduction 337 Setting Up NFS 337 Setting Up Anonymous FTP 338 Setting Up scp 339 Setting Up rsh 339 Setting Up ssh 340 VectorCAST Configuration for Remote Shell Execution 342 Target Execution Using a Remote Shell 345 Target Debug Execution 345 Standard I/O 347 Introduction 347 Configuring
Load more

Recommended publications
  • Code Compose Code Composer Studio
    Code Composer Studio Code Composer Studio Developer(s) Texas Instruments Initial release 1999; 20 years ago Stable release 8.1 (8.1.0.00011) / 13 June 2018 ; 9 months ago Operating system Windows, Linux and macOS Platform IA-32 and x86-64 Available in 1 languages Type Integrated Development Environment Website ti.com/ccstudio Code Composer Studio (CCStudio or CCS) is an integrated development environment (IDE) to develop applications for Texas Instruments (TI) embedded processors. Texas Instruments embedded processors include TMS320 DSPs, OMAP system-on-a-chip, DaVinci system- on-a-chip, Sitara applications processors, Hercules microcontrollers, Simplelink MCUs (MSP432 and Wireless connectivity[2]microcontrollers), MSP430 and Tiva/Stellaris microcontrollers. It also enables debugging on several subsystems such as Ducati,[3] IVA Accelerator[4] and PRU-ICSS.[5] Code Composer Studio is primarily designed as for embedded project design and low-level (baremetal) JTAG based debugging. However, the latest releases are based on unmodified versions of the Eclipse open source IDE, which can be easily extended to include support for OS level application debug (Linux, Android, Windows Embedded) and open source compiler suites such as GCC. Early versions included a real time kernel called DSP/BIOS and its later inception SYS/BIOS. Currently, the successor to these tools, the TI-RTOS embedded tools ecosystem, is available for downloading as a free plugin to Code Composer Studio. History Originally Code Composer was a product from a company called GO DSP located in Toronto, Canada, and it was acquired by TI in 1997.[6] After the acquisition, Code Composer was bundled with a real-time kernel named DSP/BIOS[7] and its name was appended with the word Studio.
    [Show full text]
  • FUJITSU SEMICONDUCTOR FR FamilyNew-Generation Microcomputers with Extensive Specifications
    Japan Marketing Div., Electronic Devices Shinjyuku Dai-ichi Seimei Bldg. FUJITSU LIMITED 7-1, Nishishinjuku 2-chome, Shinjuku-ku, Tokyo 163-0721 http://edevice.fujitsu.com/ Tel : +81-3-5322-3353 Fax : +81-3-5322-3386 North and South America Europe Asia Pacific Korea FUJITSU MICROELECTRONICS, INC. FUJITSU MICROELECTRONICS FUJITSU MICROELECTRONICS FUJITSU MICROELECTRONICS 3545 North First Street EUROPE GmbH ASIA PTE LTD. KOREA LTD. San Jose, CA 95134-1804, USA Am Siebenstein 6-10, #05-08, 151 Lorong Chuan, 1702 KOSMO TOWER, Tel : +1-408-922-9000 D-63303 Dreieich-Buchschlag, New Tech Park, 1002 Daechi-Dong, Fax : +1-408-922-9179 Germany Singapore 556741 Kangnam-Gu, Seoul Tel : +49-6103-690-0 Tel : +65-6281-0770 135-280, Korea Customer Response Center Fax : +49-6103-690-122 Fax : +65-6281-0220 Tel : +02-3484-7100 Mon.-Fri.: 7am-5pm (PST) http://www.fme.fujitsu.com/ http://www.fmal.fujitsu.com/ Fax : +02-3484-7111 Tel : +1-800-866-8608 http://www.fmk.fujitsu.com/ Fax : +1-408-922-9179 http://www.fma.fujitsu.com/ Specifications are subject to change without notice. For further information please contact each office. All Rights Reserved. The contents of this document are subject to change without notice. Customers are advised to consult with FUJITSU sales representatives before ordering. The information and circuit diagrams in this document are presented as examples of semiconductor device applications, and are not intended to be incorporated in devices for actual use. Also, FUJITSU is unable to assume responsibility for infringement of any patent rights or other rights of third parties arising from the use of this information or circuit diagrams.
    [Show full text]
  • Release Notes Www
    Razorcat Development GmbH Witzlebenplatz 4 14057 Berlin Germany Technical Support phone +49 - (30) - 536 357 0 fax +49 - (30) - 536 357 60 email [email protected] Release Notes www http://www.razorcat.com Addressed In: 3.0.31 (18 item(s)) CR Number: 5235 Component: TDE Fix: Possible error when copying colunmns in TDE containg dynamic INOUT objects with structs containing arrays of unions with OUT only passing direction. CR Number: 5234 Component: Support Fix: Error creating support files with path names longer than 100 characters. CR Number: 5233 Component: SCE Fix: Missleading call trace display when multiple work tasks are called in one time step (second work task was displayed as called from first work task in actual call trace view). CR Number: 5232 Component: Driver Fix: Generating test driver containing function declaration longer than 1024 characters failed. CR Number: 5231 Component: TIE Fix: Missing __attribute__((packed)) when creating synthetic struct of that type. CR Number: 5230 Component: Driver Fix: Possible error generating driver for advanced stub pointer to struct parameter. CR Number: 5227 Component: Cosmic S12X/ZAP/TRACE32 Fix: ZAP and TRACE32 cannot handle Cosmic's S12X generated short path names. Changed the makefile templates to use the long path names instead. CR Number: 5225 Component: Makefile Templates Fix: Substituted missing 'type' command by 'cat' in respective makefile templates. Razorcat Development GmbH, Witzlebenplatz 4, 14057 Berlin, Germany 1 Release Notes TESSY Addressed In: 3.0.31 (18 item(s)) CR Number: 5224 Component: IDB Fix: Possible error in interface database, when a function pointer inside a struct uses the struct itself as parameter.
    [Show full text]
  • TMS320C6000 Optimizing Compiler V8.2.X User's Guide (Rev. B)
    TMS320C6000 Optimizing Compiler v8.2.x User's Guide Literature Number: SPRUI04B May 2017 Contents Preface....................................................................................................................................... 11 1 Introduction to the Software Development Tools.................................................................... 14 1.1 Software Development Tools Overview ................................................................................. 15 1.2 Compiler Interface.......................................................................................................... 16 1.3 ANSI/ISO Standard ........................................................................................................ 16 1.4 Output Files ................................................................................................................. 17 1.5 Utilities ....................................................................................................................... 17 2 Getting Started with the Code Generation Tools .................................................................... 18 2.1 How Code Composer Studio Projects Use the Compiler ............................................................. 18 2.2 Compiling from the Command Line ..................................................................................... 19 3 Using the C/C++ Compiler ................................................................................................... 20 3.1 About the Compiler........................................................................................................
    [Show full text]
  • TMS320C6000 Optimizing Compiler V 7.3 User's Guide
    TMS320C6000 Optimizing Compiler v 7.3 User's Guide Literature Number: SPRU187T July 2011 2 SPRU187T–July 2011 Submit Documentation Feedback Copyright © 2011, Texas Instruments Incorporated Contents Preface ...................................................................................................................................... 13 1 Introduction to the Software Development Tools ................................................................... 17 1.1 Software Development Tools Overview ................................................................................ 18 1.2 C/C++ Compiler Overview ................................................................................................ 19 1.2.1 ANSI/ISO Standard ............................................................................................... 19 1.2.2 Output Files ....................................................................................................... 20 1.2.3 Compiler Interface ................................................................................................ 20 1.2.4 Utilities ............................................................................................................. 20 2 Using the C/C++ Compiler .................................................................................................. 21 2.1 About the Compiler ........................................................................................................ 22 2.2 Invoking the C/C++ Compiler ...........................................................................................
    [Show full text]
  • Testwell CTC++ Test Coverage Analyser
    Testwell CTC++ Test Coverage Analyser What is Testwell CTC++? Testwell CTC++ is the leading Code Coverage Tool for measuring Code Coverage on host and on all embedded targets (even very small ones). The tool can be used to fulfill the code coverage requirements of safety standards like DO-178C, ISO 26262, EN 50128, and IEC 60880. Hundreds of companies in more than 30 countries all over the world use Testwell CTC++ in order to insure the quality of their softwares. Testwell CTC++ is the first choice for companies which have to achieve and to proof high code coverage in aerospace, automotive, transportation, healthcare, nuclear power and other industries. Why Code Coverage? Code coverage is a measure, which describes the degree to which the source code of a program is tested. This can be considered as an indirect measure of quality of the software. Code coverage finds areas of a program which have not yet exercised by a set of test cases. This way it supports you by creating additional test cases to increase the code coverage and prevents you from writing redundant test cases. Code coverage is most useful during the module testing phase, though it also has benefit during integration testing and at other times, depending on how and what you are testing. Code coverage is « highly recommanded » (which means de facto mandatory) for safety critical software. Safety standards like DO-178C (Software Considerations in Airborne Systems and Equipment Certification), IEC/EN 61508 (functional safety of electrical/electronic, programmable electronic safety-related systems), EN 50128 (Railway applications - Communication, signalling and processing systems - Software for railway control and protection systems), IEC 60880 (nuclear power), and ISO 26262 (functional safety of road vehicles) request different levels of code coverage according to the safety level of the application.
    [Show full text]
  • Sitara Linux Software Developer's Guide Thank You for Choosing to Evaluate One of Our Sitara ARM Microprocessors [1]
    Sitara Linux Software Developer’s Guide v6.00.00.00 NOTE - This PDF is hyperlinked. Clicking on a link (typically bolded and underlined) will take you to that chapter or open the appropriate website. Contents Articles Sitara Linux Software Developer’s Guide 1 How to Build a Ubuntu Linux host under VMware 14 Sitara SDK Installer 29 Sitara Linux SDK Setup Script 32 AMSDK START HERE Script 36 Matrix Users Guide 38 AM335x Power Management User Guide 47 AM37x Power Management User Guide 51 OMAPL1: Changing the Operating Point 54 ARM Multimedia Users Guide 57 Camera Users Guide 81 Cryptography Users Guide 89 Oprofile User's Guide 97 WL127x WLAN and Bluetooth Demos 100 OMAP Wireless Connectivity OpenSource Compat Wireless Build 103 OMAP Wireless Connectivity mac80211 compat wireless implementation Architecture 104 OMAP Wireless Connectivity Battleship Game demo 106 AMSDK u-boot User's Guide 111 AMSDK Linux User's Guide 122 Code Composer Studio v5 Users Guide 127 Linux Debug in CCSv5 156 How to setup Remote System Explorer plug-in 169 How to Run GDB on CCSv5 185 Pin Mux Utility for ARM MPU Processors 193 Pin Setup Tool for AM18xx ARM Microprocessors 215 AM335x Flashing Tools Guide 223 Flash v1.6 User Guide 226 AM18x Flash Tool User's Guide 240 AMSDK File System Optimization/Customization 242 Sitara Linux Training 244 How to use a Mouse instead of the Touchscreen with Matrix 246 How to Recalibrate the Touchscreen 247 AM335x U-Boot User's Guide 248 Sitara Linux SDK Top-Level Makefile 264 Sitara Linux SDK GCC Toolchain 267 Sitara Linux SDK create SD card script 272 How to add a JVM 278 References Article Sources and Contributors 281 Image Sources, Licenses and Contributors 282 Article Licenses License 285 Sitara Linux Software Developer’s Guide 1 Sitara Linux Software Developer’s Guide For the SDG specific to your SDK release, please refer to Archived SDGs under Reference Documentation Welcome to the Sitara Linux Software Developer's Guide Thank you for choosing to evaluate one of our Sitara ARM microprocessors [1].
    [Show full text]
  • Code Composer Studio™ Integrated Development Environment (IDE) V5
    Code Composer Studio™ Integrated Development Environment (IDE) v5 Quick Start Guide Code Composer Studio™ IDE Version 5 Note: Depending on your operating system, there are some recommended steps to take: Quick Start Guide • WINDOWS®: By default, Microsoft Windows Vista and Windows 7 do not allow user level accounts to write files in the “Program Installation Requirements Files” directory. This can prevent the Code Composer Studio™ These operating platform requirements are necessary to install the IDE from starting when installed in the “Program Files” or Code Composer Studio Integrated Development Environment (IDE): “Program Files (x86)” directory, because the Code Composer Studio IDE stores configuration data by default in its install Minimum directory. Either of the following workarounds can be used to • 1.5-GHz Pentium-compatible CPU avoid this problem: • 1 GB of RAM (2 GB for Windows® 7) • Install the Code Composer Studio IDE outside the “Program • 300 MB of free hard disk space (minimal custom installation) Files” or “Program Files (x86)” directory • Local DVD-ROM drive • Instruct the Code Composer Studio IDE to store configuration data outside the “Program Files” or “Program Recommended Files (x86)” directory using the -configuration command line • Dual-core processor argument. The problem will not occur when running the Code Composer Studio IDE as the Administrator user, but • 4 GB of RAM this is not recommended because it compromises the • 2 GB of free hard disk space (typical installation) Windows Vista security model Supported operating systems • LINUX™: It is recommend to install as “root”. This avoids many issues with emulation device drivers. • Windows XP (32 and 64 bit) • Windows 7 (32 and 64 bit) • From a terminal, run the installer as sudo ccs_setup_5.x.x.xxxxxx.bin & • Linux™ • At the end of the install, DO NOT check the box Launch • Check the Wiki for more details on Linux Host support: Code Composer Studio.
    [Show full text]
  • RTA-OS FR81/Softune Port Guide Copyright
    RTA-OS FR81/Softune Port Guide Copyright The data in this document may not be altered or amended without special notification from ETAS GmbH. ETAS GmbH undertakes no further obligation in relation to this document. The software described in it can only be used if the customer is in possession of a general license agreement or single li- cense. Using and copying is only allowed in concurrence with the specifica- tions stipulated in the contract. Under no circumstances may any part of this document be copied, reproduced, transmitted, stored in a retrieval system or translated into another language without the express written permission of ETAS GmbH. ©Copyright 2008-2015 ETAS GmbH, Stuttgart. The names and designations used in this document are trademarks or brands belonging to the respective owners. Document: 10643-PG-2.0.1 EN-04-2015 2 Copyright Safety Notice This ETAS product fulfills standard quality management requirements. If re- quirements of specific safety standards (e.g. IEC 61508, ISO 26262) need to be fulfilled, these requirements must be explicitly defined and ordered by the customer. Before use of the product, customer must verify the compliance with specific safety standards. Safety Notice 3 Contents 1 Introduction6 1.1 About You..................................7 1.2 Document Conventions........................7 1.3 References.................................8 2 Installing the RTA-OS Port Plug-in9 2.1 Preparing to Install............................9 2.1.1 Hardware Requirements................9 2.1.2 Software Requirements.................9 2.2 Installation................................. 10 2.2.1 Installation Directory................... 10 2.3 Licensing................................... 11 2.3.1 Installing the ETAS License Manager.......
    [Show full text]
  • TI-RTOS 2.20 for Cc13xx/Cc26xx Simplelink™ Wireless Mcus
    TI-RTOS 2.20 for CC13xx/CC26xx SimpleLink™ Wireless MCUs Getting Started Guide Literature Number: SPRUHU7D June 2016 Contents Preface . 3 1 About TI-RTOS . 4 1.1 What is TI-RTOS? . 4 1.2 What are the TI-RTOS Components?. 5 1.3 How Can I Find Example Projects? . 6 1.4 What Compilers and Targets are Supported? . 6 1.5 What Boards and Devices Have TI-RTOS Driver Examples? . 7 1.6 What Drivers Does TI-RTOS Include? . 7 1.7 For More Information . 8 2 Installing TI-RTOS . 10 2.1 System Requirements . 10 2.2 Installing Code Composer Studio . 11 2.3 Installing TI-RTOS in Code Composer Studio . 11 2.4 Installing TI-RTOS for Use in IAR Embedded Workbench . 12 2.5 Installing TI-RTOS as a Standalone Product . 12 3 Examples for TI-RTOS . 13 3.1 Creating Example Projects Using the Resource Explorer in CCS . 14 3.1.1 Creating an Empty TI-RTOS Project . 16 3.1.2 Creating Examples to Build via a Command Line . 16 3.2 Creating Examples with IAR Embedded Workbench . 17 3.3 Driver Examples: Readme Files and Common Features . 17 3.4 CC1310/CC2650 SimpleLink Development Kit Settings & Resources. 19 3.5 CC1310 SimpleLink LaunchPad Settings & Resources . 21 3.6 CC1350 SimpleLink LaunchPad Settings & Resources . 23 3.7 CC1350 SimpleLink SensorTag Settings & Resources . 25 3.8 CC2650 SimpleLink LaunchPad Settings & Resources . 27 3.9 CC2650 SimpleLink SensorTag Settings and Resources . 28 3.10 <Board>.c File . 30 3.11 Updating driverlib for CC13xx/CC26xx . 30 3.11.1 Building with CCS .
    [Show full text]
  • Testwell CTC++ Test Coverage Analyser for C, C++, Java and C# Coverage on Host On-Target Coverage for Embedded Systems
    Testwell CTC++ Test Coverage Analyser for C, C++, Java and C# Coverage on Host On-Target Coverage for Embedded Systems Verifysoft_Technology_Company_Presentation_EN 20150724 www.verifysoft.com Agenda 1. Verifysoft Short Introduction 2. History of Testwell CTC++ 3. Why Code Coverage? 4. Safety Standards and Code Coverage 5. Different Coverage Levels 6. Compiler Support 7. How does it work? Code Instrumentation 8. Support for Embedded Targets 9. Testwell CTC++ Packages and Qualification Kit 10. Different Reports 11. Supported Platforms/IDE and Tool Integrations 12. Live Demo www.verifysoft.com 2 1. Verifysoft Short Introduction Technologiepark Offenburg In der Spoeck 10-12 77656 Offenburg Germany Phone: +49 781 127 8118-0 (Germany) Phone: +33 3 68 33 58 84 (France) Fax: +49 781 63 920-29 Email: [email protected] www.verifysoft.com www.verifysoft.com 3 2. History of Testwell CTC++ 1989 Start of CTC++ development by Nokia group 1992 Foundation of Testwell Oy, Tampere (Finland) with the mission of further development of CTC++ 2003 Foundation of Verifysoft Technology GmbH, Offenburg as distributor for Testwell tools in Europe 2013 Verifysoft purchased Testwell tools Several hundred CTC++ customers worldwide. More than 1,000 licenses successfully in use. Ongoing development. Qualification-Kit for DO-178C, IEC 61508, EN 50128, ISO 26262 www.verifysoft.com 4 3. Why Code Coverage? Code Coverage Test Coverage Requirement Coverage www.verifysoft.com 5 3. Why Code Coverage? Cause-Reason-Graph Static Testing Back-to-Back Testing Classification Tree CRUD Method (CTM) Equivalent Classes Multidimensional Equivalent Classes Rare Event Testing Realtime Testing Boundary Value Analysis Critical Value Analysis Random Testing Load Tests Informal Tests Smoke Tests Monkeytest Recovery Tests Basis Fuzzing (Fuzz Testing) Stress Tests Advanced Evolutionary Testing Control Flow Oriented Testing Pairwise Testing Established test technique for critical Embedded Systems Test-End criterion (White-Box-Tests) Necessary to fulfill requirements of safety standards.
    [Show full text]
  • MSP430 GCC User's Guide (Rev. E)
    User's Guide SLAU646E–September 2015–Revised June 2019 MSP430 GCC This manual describes the setup and basic operation of the MSP430™ GCC compiler and the software development environment. Contents 1 Introduction ................................................................................................................... 6 2 Installing MSP430 GCC Compiler ......................................................................................... 6 2.1 Installing MSP430 GCC in CCS Releases Before v7.2........................................................ 7 2.2 Installing MSP430 GCC as Stand-Alone Package ............................................................. 9 3 Using MSP430 GCC Within CCS ........................................................................................ 10 3.1 Create New Project ............................................................................................... 10 3.2 Debug Using MSP-FET, MSPFET430UIF, eZ-FET, eZ430 ................................................. 11 3.3 Build Options for MSP430 GCC................................................................................. 11 3.4 Change an Existing CCS project That Uses TI Compiler to MSP430 GCC ............................... 30 3.5 Create a New CDT Project Using MSP430 GCC ............................................................. 30 3.6 GDB With MSP430 and CCSv6 ................................................................................. 30 3.7 CCS Compared to MSP430 GCC..............................................................................
    [Show full text]