DOCSLIB.ORG

Tricore C Compiler, Assembler, Linker User's Manual

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

MA060−024−00−00 Doc. ver.: 1.7 TriCore v2.5 C Compiler, Assembler, Linker User’s Manual A publication of Altium BV Documentation Department Copyright 2002−2006 Altium BV All rights reserved. Reproduction in whole or part is prohibited without the written consent of the copyright owner. TASKING is a brand name of Altium Limited. The following trademarks are acknowledged: FLEXlm is a registered trademark of Macrovision Corporation. Intel is a trademark of Intel Corporation. Motorola is a registered trademark of Motorola, Inc. MS−DOS and Windows are registered trademarks of Microsoft Corporation. SUN is a trademark of Sun Microsystems, Inc. UNIX is a registered trademark of X/Open Company, Ltd. All other trademarks are property of their respective owners. Data subject to alteration without notice. http://www.tasking.com http://www.altium.com The information in this document has been carefully reviewed and is believed to be accurate and reliable. However, Altium assumes no liabilities for inaccuracies in this document. Furthermore, the delivery of this information does not convey to the recipient any license to use or copy the software or documentation, except as provided in an executed license agreement covering the software and documentation. Altium reserves the right to change specifications embodied in this document without prior notice. CONTENTS TABLE OF CONTENTS IV Table of Contents CONTENTS CONTENTS Table of Contents V SOFTWARE INSTALLATION AND CONFIGURATION 1−1 1.1 Introduction. 1−3 1.2 Software Installation. 1−3 1.2.1 Installation for Windows. 1−3 1.2.2 Installation for Linux. 1−4 1.2.3 Installation for UNIX Hosts. 1−6 1.3 Software Configuration. 1−7 1.3.1 Configuring the Embedded Development Environment 1−7 1.3.2 Configuring the Command Line Environment. 1−9 1.4 Licensing TASKING Products. 1−12 1.4.1 Obtaining License Information. 1−12 1.4.2 Installing Node−Locked Licenses. 1−13 1.4.3 Installing Floating Licenses. 1−14 1.4.4 Modifying the License File Location. 1−16 1.4.5 How to Determine the Host ID. 1−17 1.4.6 How to Determine the Host Name . 1−17 GETTING STARTED 2−1 2.1 Introduction. 2−3 2.2 Working With Projects in EDE. 2−7 2.3 Start EDE. 2−8 2.4 Using the Sample Projects. 2−9 2.5 Create a New Project Space with a Project. 2−9 2.6 Set Options for the Tools in the Toolchain. 2−14 2.7 Build your Application. 2−16 2.8 How to Build Your Application on the Command Line 2−17 2.9 Debug getstart.elf. 2−18 TRICORE C LANGUAGE 3−1 3.1 Introduction. 3−3 3.2 Data Types. 3−3 3.2.1 Fundamental Data Types. 3−3 3.2.2 Fractional Data Types. 3−5 •••••••• VI Table of Contents 3.2.3 Bit Data Type. 3−7 3.2.4 Packed Data Types. 3−8 3.3 Memory Qualifiers. 3−10 3.3.1 Declare a Data Object in a Special Part of Memory. 3−10 3.3.2 Declare a Data Object at an Absolute Address: __at() and __atbit() . 3−13 3.4 Data Type Qualifiers. 3−15 3.4.1 Circular Buffers: __circ. 3−15 3.4.2 Declare an SFR Bit field: __sfrbit16 and __sfrbit32. 3−16 3.4.3 Saturation: __sat . 3−18 3.5 Intrinsic Functions. 3−19 3.6 Using Assembly in the C Source: __asm(). 3−20 3.7 Controlling the Compiler: Pragmas. 3−26 3.8 Predefined Macros. 3−30 3.9 Functions. 3−31 3.9.1 Inlining Functions: inline. 3−31 3.9.2 Interrupt and Trap Functions. 3−33 3.9.2.1 Defining an Interrupt Service Routine. 3−34 3.9.2.2 Defining a Trap Service Routine. 3−35 3.9.2.3 Defining a Trap Service Routine Class 6: __syscallfunc() 3−37 3.9.2.4 Enabling Interrupt Requests: __enable_, __bisr_(). 3−38 3.9.3 Function Calling Modes: __indirect. 3−39 3.9.4 Parameter Passing and the Stack Model: __stackparm. 3−40 3.10 Compiler Generated Sections. 3−43 3.11 Switch Statement . 3−47 3.12 Libraries. 3−48 3.12.1 Overview of Libraries. 3−49 3.12.2 Printf and Scanf Formatting Routines. 3−50 3.12.3 Rebuilding Libraries. 3−52 TRICORE ASSEMBLY LANGUAGE 4−1 4.1 Introduction. 4−3 4.2 Assembly Syntax . 4−3 4.3 Assembler Significant Characters. 4−4 CONTENTS Table of Contents VII 4.4 Operands. 4−5 4.4.1 Operands and Addressing Modes. 4−5 4.4.2 PCP Addressing Modes. 4−8 4.5 Symbol Names . 4−8 4.6 Assembly Expressions. 4−9 4.6.1 Numeric Constants . 4−10 4.6.2 Strings. 4−11 4.6.3 Expression Operators . 4−12 4.7 Built−in Assembly Functions. 4−14 4.8 Assembler Directives and Controls. 4−18 4.8.1 Overview of Assembler Directives. 4−19 4.8.2 Overview of Assembler Controls. 4−21 4.9 Working with Sections. 4−22 4.10 Macro Operations. 4−24 4.10.1 Defining a Macro. 4−24 4.10.2 Calling a Macro. 4−25 4.10.3 Using Operators for Macro Arguments. 4−27 4.10.4 Using the .DUP, .DUPA, .DUPC, .DUPF Directives as Macros . 4−31 4.10.5 Conditional Assembly: .IF, .ELIF and .ELSE Directives. 4−31 USING THE COMPILER 5−1 5.1 Introduction. 5−3 5.2 Compilation Process. 5−4 5.3 Compiler Optimizations . 5−5 5.3.1 Optimize for Size or Speed. 5−9 5.4 Calling the Compiler. 5−10 5.5 How the Compiler Searches Include Files. 5−16 5.6 Compiling for Debugging. 5−16 5.7 C Code Checking: MISRA−C. 5−17 5.8 C Compiler Error Messages. 5−19 •••••••• VIII Table of Contents USING THE ASSEMBLER 6−1 6.1 Introduction. 6−3 6.2 Assembly Process. 6−3 6.3 Assembler Optimizations . 6−4 6.4 Calling the Assembler. 6−5 6.5 Specifying a Target Processor. 6−8 6.6 How the Assembler Searches Include Files. 6−9 6.7 Generating a List File . 6−9 6.8 Assembler Error Messages. 6−10 USING THE LINKER 7−1 7.1 Introduction. 7−3 7.2 Linking Process. 7−4 7.2.1 Phase 1: Linking. 7−6 7.2.2 Phase 2: Locating. 7−7 7.2.3 Linker Optimizations . 7−9 7.3 Calling the Linker. 7−10 7.4 Linking with Libraries. 7−14 7.4.1 Specifying Libraries to the Linker. 7−15 7.4.2 How the Linker Searches Libraries. 7−17 7.4.3 How the Linker Extracts Objects from Libraries. 7−17 7.5 Incremental Linking. 7−18 7.6 Linking the C Startup Code. 7−19 7.7 Controlling the Linker with a Script. 7−20 7.7.1 Purpose of the Linker Script Language. 7−20 7.7.2 EDE and LSL . 7−21 7.7.3 Structure of a Linker Script File. 7−22 7.7.4 The Architecture Definition: Self−Designed Cores. 7−26 7.7.5 The Derivative Definition: Self−Designed Processors. 7−29 7.7.6 The Memory Definition: Defining External Memory. 7−31 7.7.7 The Section Layout Definition: Locating Sections. 7−33 7.7.8 The Processor Definition: Using Multi−Processor Systems. 7−37 CONTENTS Table of Contents IX 7.8 Linker Labels . 7−38 7.9 Generating.
Recommended publications
  • Red Hat Enterprise Linux 6 Developer Guide

    Red Hat Enterprise Linux 6 Developer Guide

    Red Hat Enterprise Linux 6 Developer Guide An introduction to application development tools in Red Hat Enterprise Linux 6 Dave Brolley William Cohen Roland Grunberg Aldy Hernandez Karsten Hopp Jakub Jelinek Developer Guide Jeff Johnston Benjamin Kosnik Aleksander Kurtakov Chris Moller Phil Muldoon Andrew Overholt Charley Wang Kent Sebastian Red Hat Enterprise Linux 6 Developer Guide An introduction to application development tools in Red Hat Enterprise Linux 6 Edition 0 Author Dave Brolley [email protected] Author William Cohen [email protected] Author Roland Grunberg [email protected] Author Aldy Hernandez [email protected] Author Karsten Hopp [email protected] Author Jakub Jelinek [email protected] Author Jeff Johnston [email protected] Author Benjamin Kosnik [email protected] Author Aleksander Kurtakov [email protected] Author Chris Moller [email protected] Author Phil Muldoon [email protected] Author Andrew Overholt [email protected] Author Charley Wang [email protected] Author Kent Sebastian [email protected] Editor Don Domingo [email protected] Editor Jacquelynn East [email protected] Copyright © 2010 Red Hat, Inc. and others. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
  • Improving Security Through Egalitarian Binary Recompilation

    Improving Security Through Egalitarian Binary Recompilation

    Improving Security Through Egalitarian Binary Recompilation David Williams-King Submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy under the Executive Committee of the Graduate School of Arts and Sciences COLUMBIA UNIVERSITY 2021 © 2021 David Williams-King All Rights Reserved Abstract Improving Security Through Egalitarian Binary Recompilation David Williams-King In this thesis, we try to bridge the gap between which program transformations are possible at source-level and which are possible at binary-level. While binaries are typically seen as opaque artifacts, our binary recompiler Egalito (ASPLOS 2020) enables users to parse and modify stripped binaries on existing systems. Our technique of binary recompilation is not robust to errors in disassembly, but with an accurate analysis, provides near-zero transformation overhead. We wrote several demonstration security tools with Egalito, including code randomization, control-flow integrity, retpoline insertion, and a fuzzing backend. We also wrote Nibbler (ACSAC 2019, DTRAP 2020), which detects unused code and removes it. Many of these features, including Nibbler, can be combined with other defenses resulting in multiplicatively stronger or more effective hardening. Enabled by our recompiler, an overriding theme of this thesis is our focus on deployable software transformation. Egalito has been tested by collaborators across tens of thousands of Debian programs and libraries. We coined this term egalitarian in the context of binary security. Simply put, an egalitarian analysis or security mechanism is one that can operate on itself (and is usually more deployable as a result). As one demonstration of this idea, we created a strong, deployable defense against code reuse attacks.
  • Chapter 1. Origins of Mac OS X

    Chapter 1. Origins of Mac OS X

    1 Chapter 1. Origins of Mac OS X "Most ideas come from previous ideas." Alan Curtis Kay The Mac OS X operating system represents a rather successful coming together of paradigms, ideologies, and technologies that have often resisted each other in the past. A good example is the cordial relationship that exists between the command-line and graphical interfaces in Mac OS X. The system is a result of the trials and tribulations of Apple and NeXT, as well as their user and developer communities. Mac OS X exemplifies how a capable system can result from the direct or indirect efforts of corporations, academic and research communities, the Open Source and Free Software movements, and, of course, individuals. Apple has been around since 1976, and many accounts of its history have been told. If the story of Apple as a company is fascinating, so is the technical history of Apple's operating systems. In this chapter,[1] we will trace the history of Mac OS X, discussing several technologies whose confluence eventually led to the modern-day Apple operating system. [1] This book's accompanying web site (www.osxbook.com) provides a more detailed technical history of all of Apple's operating systems. 1 2 2 1 1.1. Apple's Quest for the[2] Operating System [2] Whereas the word "the" is used here to designate prominence and desirability, it is an interesting coincidence that "THE" was the name of a multiprogramming system described by Edsger W. Dijkstra in a 1968 paper. It was March 1988. The Macintosh had been around for four years.
  • MSP430 Family Object Format Converter Description 10-1 Topics

    MSP430 Family Object Format Converter Description 10-1 Topics

    MSP430 Family Object Format Converter Description Topics 10 Object Format Converter Description 10-3 10.1 Object Format Converter Development Flow 10-4 10.2 Extended Tektronix Hex Object Format 10-5 10.3 Intel Hex Object Format 10-6 10.4 TI–Tagged Object Format 10-7 10.5 Motorola S Format 10-8 10.6 Invoking the Object Format Converter 10-9 10.7 Object Format Converter Examples 10-10 10.8 Halt Conditions 10-11 Figures Fig. Title Page 10.1 Object Format Converter Development Flow 10-4 10.2 Extended Tektronix Hex Object Format 10-5 10.3 Intel Hex Object Format 10-6 10.4 TI–Tagged Object Format 10-7 10.5 Motorola S Format 10-8 10-1 Object Format Converter Description MSP430 Family 10-2 MSP430 Family Object Format Converter Description 10 Object Format Converter Description Most EPROM programmers do not accept COFF object files as input. The object format converter converts a COFF object file into one of four object formats that most EPROM programmers accept as input: Extended Tektronix hex object format supports 32–bit addresses. Intel hex object format supports 16–bit addresses. Motorola S format supports 16–bit addresses. TI–tagged object format supports 16–bit addresses. 10-3 Object Format Converter Description MSP430 Family 10.1 Object Format Converter Development Flow The figure illustrates the object format converter's role in the assembly language development process. Macro Assembler Source Files Source Archiver Assembler Macro Library COFF Object Files Linker Archiver Library of Executable Object Files COFF Objekt Files Object Format Converter EPROM Absolute Software Evaluation In-Circuit MSP430 Programmer Lister Emulator Module Emulator Figure 10.1: Object Format Converter Development Flow 10-4 MSP430 Family Object Format Converter Description 10.2 Extended Tektronix Hex Object Format The Extended Tektronix hex object format supports 32–bit addresses and has three types of records: data, symbol, and termination records.
  • Sqtp File Format Specification

    Sqtp File Format Specification

    SQTP FILE FORMAT SPECIFICATION SQTPSM File Format Specification INTRODUCTION This document shows how a Serial Quick Turn Programming (SQTPSM) file is produced and used by MPLAB® IPE Integrated Programming Environment. Engineers can use this information to generate their own SQTP file. • Overview • Example SQTP File • Intel HEX File Format • MPLAB IPE SQTP File Generation • Customer Generated SQTP Files • Programming of Devices • Understanding Usage of RETLW in SQTP File for Midrange and Baseline Devices • Examples of SQTP Files for Various Memory Regions • Differences in SQTP File Behavior Between MPLAB IPE v2.35 (and Before) and MPLAB IPE v2.40 (and Later) • Differences in the SQTP Feature Between MPLAB IDE v8.xx and MPLAB IPE for the Flash Data Memory Region OVERVIEW Serialization is a method of programming microcontrollers whereby each chip is pro- grammed with a slightly different code. Typically, all locations are programmed with the same basic code, except for a few contiguous bytes. Those bytes are programmed with a different number (referred to as “key” or “ID number” or “serial number”) in a program region. Typical applications for such programming are where each unit must have a different access code, as in the Internet of Things (IoT), car alarms or garage door openers. An SQTP file (.num) contains the serial numbers to be used as each device is programmed. Microchip devices require that the serial number must reside in contiguous locations, with up to 256 locations. The minimum number of bytes in a line of SQTP should be the Word size of the memory. It can be a multiple of the Word size, up to 256 bytes.
  • CIS Ubuntu Linux 18.04 LTS Benchmark

    CIS Ubuntu Linux 18.04 LTS Benchmark

    CIS Ubuntu Linux 18.04 LTS Benchmark v1.0.0 - 08-13-2018 Terms of Use Please see the below link for our current terms of use: https://www.cisecurity.org/cis-securesuite/cis-securesuite-membership-terms-of-use/ 1 | P a g e Table of Contents Terms of Use ........................................................................................................................................................... 1 Overview ............................................................................................................................................................... 12 Intended Audience ........................................................................................................................................ 12 Consensus Guidance ..................................................................................................................................... 13 Typographical Conventions ...................................................................................................................... 14 Scoring Information ..................................................................................................................................... 14 Profile Definitions ......................................................................................................................................... 15 Acknowledgements ...................................................................................................................................... 17 Recommendations ............................................................................................................................................
  • Linux Fundamentals Paul Cobbaut Linux Fundamentals Paul Cobbaut

    Linux Fundamentals Paul Cobbaut Linux Fundamentals Paul Cobbaut

    Linux Fundamentals Paul Cobbaut Linux Fundamentals Paul Cobbaut Publication date 2015-05-24 CEST Abstract This book is meant to be used in an instructor-led training. For self-study, the intent is to read this book next to a working Linux computer so you can immediately do every subject, practicing each command. This book is aimed at novice Linux system administrators (and might be interesting and useful for home users that want to know a bit more about their Linux system). However, this book is not meant as an introduction to Linux desktop applications like text editors, browsers, mail clients, multimedia or office applications. More information and free .pdf available at http://linux-training.be . Feel free to contact the author: • Paul Cobbaut: [email protected], http://www.linkedin.com/in/cobbaut Contributors to the Linux Training project are: • Serge van Ginderachter: [email protected], build scripts and infrastructure setup • Ywein Van den Brande: [email protected], license and legal sections • Hendrik De Vloed: [email protected], buildheader.pl script We'd also like to thank our reviewers: • Wouter Verhelst: [email protected], http://grep.be • Geert Goossens: [email protected], http://www.linkedin.com/in/ geertgoossens • Elie De Brauwer: [email protected], http://www.de-brauwer.be • Christophe Vandeplas: [email protected], http://christophe.vandeplas.com • Bert Desmet: [email protected], http://blog.bdesmet.be • Rich Yonts: [email protected], Copyright 2007-2015 Netsec BVBA, Paul Cobbaut Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
  • Cubesuite+ V1.00.00 Integrated Development Environment User's Manual: V850 Build

    Cubesuite+ V1.00.00 Integrated Development Environment User's Manual: V850 Build

    User’s Manual User’s CubeSuite+ V1.00.00 Integrated Development Environment User’s Manual: V850 Build Target Device V850 Microcontroller All information contained in these materials, including products and product specifications, represents information on the product at the time of publication and is subject to change by Renesas Electronics Corp. without notice. Please review the latest information published by Renesas Electronics Corp. through various means, including the Renesas Electronics Corp. website (http://www.renesas.com). www.renesas.com Rev.1.00 Apr 2011 Notice 1. All information included in this document is current as of the date this document is issued. Such information, however, is subject to change without any prior notice. Before purchasing or using any Renesas Electronics products listed herein, please confirm the latest product information with a Renesas Electronics sales office. Also, please pay regular and careful attention to additional and different information to be disclosed by Renesas Electronics such as that disclosed through our website. 2. Renesas Electronics does not assume any liability for infringement of patents, copyrights, or other intellectual property rights of third parties by or arising from the use of Renesas Electronics products or technical information described in this document. No license, express, implied or otherwise, is granted hereby under any patents, copyrights or other intellectual property rights of Renesas Electronics or others. 3. You should not alter, modify, copy, or otherwise misappropriate any Renesas Electronics product, whether in whole or in part. 4. Descriptions of circuits, software and other related information in this document are provided only to illustrate the operation of semiconductor products and application examples.
  • PG-FP5 Flash Memory Programmer User's Manual

    PG-FP5 Flash Memory Programmer User's Manual

    User’s Manual User’s PG-FP5 Flash Memory Programmer User’s Manual All information contained in these materials, including products and product specifications, represents information on the product at the time of publication and is subject to change by Renesas Electronics Corp. without notice. Please review the latest information published by Renesas Electronics Corp. through various means, including the Renesas Electronics Corp. website (http://www.renesas.com). www.renesas.com Rev. 5.00 Dec, 2011 Notice 1. All information included in this document is current as of the date this document is issued. Such information, however, is subject to change without any prior notice. Before purchasing or using any Renesas Electronics products listed herein, please confirm the latest product information with a Renesas Electronics sales office. Also, please pay regular and careful attention to additional and different information to be disclosed by Renesas Electronics such as that disclosed through our website. 2. Renesas Electronics does not assume any liability for infringement of patents, copyrights, or other intellectual property rights of third parties by or arising from the use of Renesas Electronics products or technical information described in this document. No license, express, implied or otherwise, is granted hereby under any patents, copyrights or other intellectual property rights of Renesas Electronics or others. 3. You should not alter, modify, copy, or otherwise misappropriate any Renesas Electronics product, whether in whole or in part. 4. Descriptions of circuits, software and other related information in this document are provided only to illustrate the operation of semiconductor products and application examples. You are fully responsible for the incorporation of these circuits, software, and information in the design of your equipment.
  • Application N

    Application N

    UT32M0R500 UART Flash Download APPLICATION NOTE PRODUCT NAME MANUFACTURER SMD # DEVICE TYPE INTERNAL PIC PART NUMBER NUMBER Arm Cortex M0+ UT32M0R500 5962-17212 FlasH Download QS30 1.0 Overview This document details the process of creating and downloading a hex or srec image. Keil ARM development tools are used to create the image. Once the image is created, a Terminal Window is used to download the image via a Serial Port. For the purposes of this document, we will use the helloworld project from AppNote_UT32M0R500_Creating_Projects.pdf. Using this template, the user should be able to upload a hex or srec image file to Flash memory on the UT32M0R500 via UART using a Terminal Window. 2.0 Steps to Create and Download an Image to the UT32M0R500 1. Launch Keil uVision 2. From the Project menu, select Options for Target ‘Target 1’… (Figure 1). Figure 1: Project Setup 2/7/2019 4350 Centennial Blvd. | Colorado Springs CO 80907 USA | 1-800-645-8862 | cobhamaes.com UT32M0R500 UART Flash Download APPLICATION NOTE 3. In the Options dialog box, on the Output tab, check Create HEX file (Figure 2), and click OK. Figure 2: Output Options 4. In the Project Explorer view, click on and Rebuild the project. 2/7/2019 4350 Centennial Blvd. | Colorado Springs CO 80907 USA | 1-800-645-8862 | cobhamaes.com UT32M0R500 UART Flash Download APPLICATION NOTE 5. Once the hex file has been created, open Tera Term. From the Setup dialog box, select the correct Port… and set the port to the following settings (Figure 3). Figure 3: Serial Port Settings After you’ve configured the switches for BOOTCFG in the b’10 position, and hit RESET on the evaluation board, the Terminal window displays the following.
  • [Improving System Performance Using Application-Level Hints]

    [Improving System Performance Using Application-Level Hints]

    Improving System Performance using Application-Level Hints Björn Döbel Technische Universität Dresden, Department of Computer Science, Operating Systems Group 8th June 2005 Supervising professor: Prof. Dr. Hermann Härtig Supervisor: Dipl.-Inf. Martin Pohlack Selbständigkeitserklärung Hiermit erkläre ich, die vorliegende Arbeit selbständig verfasst zu haben. Ich habe keine anderen als die im Quellenverzeichnis angegebenen Literaturhilfsmittel verwendet. Dresden, 08.06.2005 Björn Döbel 2 Contents 1 Introduction 5 1.1 State of the art .................................. 6 1.1.1 Monitoring ............................... 7 1.1.2 Resource management ......................... 8 1.1.3 Linux kernel modules ......................... 9 1.1.4 Caches in Linux ............................ 10 1.1.5 Using prefetching to increase application performance ........ 11 1.2 Related work .................................. 14 1.2.1 Transparent Informed Prefetch ..................... 14 1.2.2 Speculative Hinting ........................... 15 1.2.3 Integrating prefetching and caching .................. 16 2 Design 19 2.1 Disk accesses and application startup ...................... 19 2.2 Design goals ................................... 20 2.3 Design decisions ................................ 21 2.3.1 Collecting data ............................. 21 2.3.2 Modifying the Linux kernel ...................... 23 2.3.3 HintMod - the kernel module ...................... 24 2.3.4 HintGen - the hint generator ...................... 25 2.3.5 Application of hints .........................
  • SB-Projects: File Formats, Intel HEX Format

    SB-Projects: File Formats, Intel HEX Format

    SB-Projects: File Formats, Intel HEX Format http://www.sbprojects.com/knowledge/fileformats/intelhex.php 1 of 5 11-12-19 2:24 PM SB-Projects: File Formats, Intel HEX Format http://www.sbprojects.com/knowledge/fileformats/intelhex.php Navigation Intel HEX format Home Intel Hex is one of the oldest file formats available and is adopted by Knowledge Base many newcomers on the market. Therefore this file format is almost always supported by various development systems and tools. File Formats Originally the Intel Hex format was designed for a 16 bit address range Binary Format (64kb). Later the file format was enhanced to accommodate larger files HEX Format with 20 bit address range (1Mb) and even 32 bit address range (4Gb). Intel HEX Format Motorola Sxx Rec FPC Format Records MOS Technology Signetics Format All data lines are called records and each record contains the following fields: Tektronix Format EMON52 Format :ccaaaarrddss : Every line starts with a colon (Hex value $3A). Improve cc The byte-count. A 2 digit value (1 byte), counting the actual data bytes in the Memory record. My Brain Solutions aaaa The address field. A 4 digit (2 byte) number representing the first address to Makes Improving be used by this record. Memory Fun & Easy. Get Started! rr Record type. A 2 digit value (1 byte) indicating the record type. This is www.MyBrainSolution… explained later in detail. dd The actual data of this record. There can be 0 to 255 data bytes per record (see cc). Memorizing Techniques ss Checksum. A 2 digit (1 byte) checksum.