DOCSLIB.ORG

CP/M-86™ Operating System System Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

CP/M-86™ Operating System System Guide Copyright © 1981 Digit al . Research P.O. Box 579 801 Light house Avenue Pacific Grove, CA 93950 (408) 649-3896 TWX 910 360 5001 All Rights Reserved COPYRIGHT Copyright © 1981 by Digital Research. All rights may be r eserv e d . No part of this publication reproduced, transmitted, transcribed, s tored i n a retrieval system, or translated into any language or computer language, in any form or b y a n y means, electronic, mechanical, magnetic, optical, chemical, w rit t e n manual or otherwise, without the prior permission of Digital Research, Post Office Box 579, Pacific Grove, California, 93950. DISCLAIMER Digital Research makes no r e p r e s e n t a t i o ns or warranties with respect to the contents hereof and specifically disclaims any impli ed warranties of merchantability or fitness for a ny p a r t i c u l a r purpose. F u rther, Digital Research reserves the right to revise this publication and to make changes from time to time in the content hereof without obligation of Digital Research to notify any person of such r e v i s i o n o r c h a n ges . TRADEMARKS CP/M, CP/M-86, and CP/NET are registered trademarks of Digital Research. ASM-86, CP/M-80, DDT-86, LINK­ 80, MP/M, MP/M-86, and TEX are trademarks of Digital Research. Intel is a registered trademark of Intel Corporation. The CP/M-86 0 eratin S stem S stem Guide was prepared using the D igital Research TEX Text Formatter and printed in the United States of America. * ***** * * * * A* * * * * * * * * * * * * * * * * * * * * * First Edition: June 1981 * * S econd Edi t i o n : June 1983 * ***** * * * A** * * * * A* * * * * * * * * * A* * * * Foreword The CP M-86 0 eratin S stem S stem Guide presents the system programming aspects of CP M-86 , a single-user operating system for the Inteltt' 8086 and 8088 16-bit microprocessors. T he di s c u s s i o n assumes that you are familiar with CP/M®, the Digital Research 8­ bit operating system. To clarify specific differences with CP/M-86, t his document refers to the 8-bit version of CP/M as CP/M-80™ . Elements common to both systems are simply called CP/M features. The CP/M-86 package also includes the CP M-86 0 eratin S stem User's Guide and t he CP M-86 0 e ratin S stem Pr o r ammer's ~ •• 8086 assembler and interactive debugger. This System Guide presents an o verview of th e C P/M-86 programming interface conventions. It also describes procedures for adapting CP/M-86 to a custom hardware environment. Section 1 gives an overview of CP/M-86 and summarizes its differences with CP/M-80. Section 2 describes the general execution environment while Section 3 tells how to generate command files. Sections 4 and 5 respectively define the programming interfaces to the Basic Disk Operating System and the Basic Input/Output System. Section 6 discusses alteration of the BIOS to support custom disk configurations, and Section 7 describes the loading operation and the organization of the CP/M-86 system file. Table of Contents CP/M-86 System Overview 1.1 CP/M-86 General Characteristics . 1 1.2 CP/M-80 and CP/M-86 Differences . 3 Command Setup and Execution Under CP/M-86 2.1 CCP Built-in and Transient Commands 78 2.2 Transient Program Execution Models 2.3 The 8080 Memory Model 9 2.4 The Small Memory Model 10 2.5 The Compact Memory Model 11 2.6 Base Page I n i t i al i zat i on 13 2.7 Transient Program Load and Exit 14 Command (CND) File Generation 3.1 Intel Hex File Format 15 3.2 Operatio n o f G ENCMD 16 3.3 Operat i o n o f LMCMD 19 3.4 Command (CMD) Fil e F o r mat 20 Basic Disk Operating System (BDOS) Functions 4.1 BDOS Parameters and Function Codes 23 4.2 Simple BDOS Calls 25 4.3 BDOS File Operations 30 4.4 BDOS Memory Management and Load 48 Basic I/O System (BIOS) Organization 5.1 Organization of the BIOS 55 5.2 The BIOS Jump Vector 56 5.3 Simple Peripheral Devices 57 5.4 BIOS Subroutine Entry Points 60 BIOS Disk Definition Tables 6.1 Disk Parameter Table Format • • • • • • • • • • • 67 • 72 6.2 Table Generation Using GENDEF • • • • • • • • • • • • • • 77 6.3 GRNDEF Output • • • • • • • CP/M-86 Bootstrap and Adaptation Procedures 7.1 The Cold Start Load Operation . 8l 7.2 Organization of CPM.SYS . 84 Appendixes A Blocking and Deblocking Algorithms 87 8 Random Access Sample Program 95 C Listing of the Boot Rom 103 D L D BIOS Lis t i ng 113 E BIOS Listing 121 F C B IOS Lis t i ng 137 Section 1 CP/M-86 System Overview 1.1 CP/M-86 General Characteristics CP/M-86 contains all facilities of CP/M-80 with additional features to account for increased processor address space of up to a megabyte (1,048,576) of main memory. Further, CP/M-86 maintains file compatibility with all previous versions of CP/M. The file structure of version 2 of CP/M is used, allowing as many as sixteen drives with up to eight megabytes on each drive. Thus, CP/M-80 and CP/M-86 systems may exchange files without modifying the file format. CP/M-86 resides in the file CPM.SYS, which is loaded into memory by a cold start loader during system initialization. The cold start loader resides on the first two tracks of the system disk. CPM.SYS contains three program modules: the Console Command Processor (CCP), the Basic Disk Operating System (BDOS), and the user-configurable Basic I/O System (BIOS). T h e CCP and BDOS portions occupy approximately 10K bytes, while the size of the BIOS varies with the implementation. The operating system executes in any portion of memory above the reserved interrupt locations, while the remainder of the address space is partitioned into as many as eight non-contiguous regions, as defined in a BIOS table. Unlike CP/M-80, the CCP area cannot be used as a data area subsequent to transient program load; all CP/M-86 modules remain in memory at all times, and are not reloaded at a warm start. Similar to CP/M-80, CP/M-86 loads and executes memory image files from disk. M emory image files are preceded by a "header record," defined in this document, which provides information required for proper program loading and execution. Memory image files under CP/M-86 are identified by a "CMD" file type. Unlike CP/M-80, CP/N-86 does not use absolute locations for system entry or default variables. Th e BDOS entry takes place through a reserved software interrupt, while entry to the BIOS is provided by a new BDOS call. Two variables maintained in low memory under CP/M-80, the default disk number and I/O Byte, are placed in the CCP and BIOS, respectively. Dependence upon absolute addresses i s mini mi zed i n C P/ M-86 by mai n t a i n i n g i ni t i al "ba s e p a ge " v a l u e s < such as the default FCB and default command buffer, in the transient p rogram data a r e a . Utility programs such as ED, PIP, STAT and SUBMIT operate in the same manner under Cp/M-86 and Cp/M-80. In its operation, DDT-86 resembles DDT supplied with CP/M-80. It a l lows interactive debugging of 8086 and 8088 machine code. Similarly, ASM-86 allows assembly language programming and development for the 8086 and 8088 using Intel-like mnemonics. CP/M-86 System Guide 1.1 CP/N-86 General Characteristics The GENCND (Generate CND) utility replaces the LOAD program of CP/N-89, and converts the hex files produced by ASM-86 or Intel utilities into memory image format suitable for execution under CP/M-86. Further, the LDCOPY (Loader Copy) program replaces SYSGEN, and is used to copy the cold start loader from a system disk for replication. In addition, a variation of GENCMD, called LMCMD, converts output from the Intel LOC86 utility into CND format. Finally, GENDEF (Generate DISKDEF) is erovided as an aid in producing custom disk parameter tables. ASM-86, GENCMD, LNCMD, and GENDEF are also supplied in "COM" file format for cross-development under CP/M-80. Several terms used throughout this manual are defined in Table l - l b e l o w : Table l-l. CP/M-86 Teras Term Meaning Nibble 4-bit half-byte Byte 8 -bit v a l u e Word 1 6-bit v a l u e Double Word 3 2-bit va l u e Paragraph 1 6 cont i g u ous b y t e s Paragraph Boundary An address divisible evenly by 16 ( l o w o r d e r n i bb l e 0) Segment tJp to 64K contiguous bytes Segment Register One of CS , DS , ES , o r SS Offset 16-bit displacement from a segment register Group A segment-register-relative relocatable program unit Address The effective memory address derived from the composition of a segment register value with an offset value A group consists of segments that are loaded into memory as a single unit.
Recommended publications
  • OS 386 Multiuser/Multitasking Operating System

    OS 386 Multiuser/Multitasking Operating System

    OS 386 Multiuser/Multitasking Operating System REFERENCE GUIDE [Q] DIGITAL RESEARCH@ os REFERENCE GUIDE [jill DIGITAL RESEARCH~ COPYRIGHT Copyright © 1987 Digital Research Inc. All rights reserved. No part of this publication may be reproduced, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual or otherwise without the prior written permission of Digital Research Inc, 60 Garden Court, Box DRI, Monterey, California 93942 DISCLAIMER DIGITAL RESEARCH MAKES NO REPRESENTATIONS OR WARRANTIES WITH RESPECT TO THE CONTENTS HEREOF AND SPECIFICALLY DISCLAIMS ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE. Further Digital Research Inc. reserves the right to revise this publication and to make changes from time to time in the content hereof without obligation of Digital Research Inc to notify any person of such revision or changes. NOTICE TO USER This manual should not be construed as any representation or warranty with respect to the software named herein. Occasionally changes or variations exist in the software that are not reflected in the manual. Generally, if such changes or variations are known to exist and to affect the product significantly, a release note or READ.ME file accompanies the manual and the distribution disks. In that event, be sure to read the release note or READ.ME file before using the product. ii TRADEMARKS Digital Research and its logo, CP/M, and CP/M-86 are registered trademarks of Digital Research Inc. Cardfile, Concurrent, Concurrent DOS 386, Concurrent DOS XM, DR EDIX, DOS Plus and MP/M-86 are trademarks of Digital Research Inc.
  • Chapter 10 Introduction to Batch Files

    Chapter 10 Introduction to Batch Files

    Instructor’s Manual Chapter 10 Lecture Notes Introduction to Batch Files Chapter 10 Introduction to Batch Files LEARNING OBJECTIVES 1. Compare and contrast batch and interactive processing. 2. Explain how batch files work. 3. Explain the purpose and function of the REM, ECHO, and PAUSE commands. 4. Explain how to stop or interrupt the batch file process. 5. Explain the function and use of replaceable parameters in batch files. 6. Explain the function of pipes, filters, and redirection in batch files. STUDENT OUTCOMES 1. Use Edit to write batch files. 2. Use COPY CON to write batch files. 3. Write and execute a simple batch file. 4. Write a batch file to load an application program. 5. Use the REM, PAUSE, and ECHO commands in batch files. 6. Terminate a batch file while it is executing. 7. Write batch files using replaceable parameters. 8. Write a batch file using pipes, filters, and redirection. CHAPTER SUMMARY 1. Batch processing means running a series of instructions without interruption. 2. Interactive processing allows the user to interface directly with the computer and update records immediately. 3. Batch files allow a user to put together a string of commands and execute them with one command. 4. Batch files must have the .BAT or .CMD file extension. 5. Windows looks first internally for a command, then for a .COM files extension, then for a .EXE file extension, and finally for a .BAT or .CMD file extension. 6. Edit is a full-screen text editor used to write batch files. 7. A word processor, if it has a means to save files in ASCII, can be used to write batch files.
  • 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.
  • IBM Tivoli Monitoring: Administrator's Guide Private Situation Operation

    IBM Tivoli Monitoring: Administrator's Guide Private Situation Operation

    IBM Tivoli Monitoring Version 6.2.3 Fix Pack 1 Administrator's Guide SC32-9408-05 IBM Tivoli Monitoring Version 6.2.3 Fix Pack 1 Administrator's Guide SC32-9408-05 Note Before using this information and the product it supports, read the information in “Notices” on page 467. This edition applies to version 6, release 2, modification 3, fix pack 1 of IBM Tivoli Monitoring (product number 5724-C04 ) and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright IBM Corporation 2005, 2012. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures ..............vii Enabling the HTTP proxy server ......49 Setting application properties for Linux and Tables ...............ix UNIX systems ............50 Setting the environment variable when the hub is on a z/OS system ...........51 About this information ........xi Tivoli Enterprise Portal Server configuration settings 52 Editing the portal server environment file . 52 Chapter 1. Introduction ........1 Portal server environment variables .....53 New in this release ............1 Pruning events on the portal server database . 54 New in Version 6.2.3 Fix Pack 1 .......1 Controlling the size of event attachments . 55 New in Version 6.2.3...........2 Controlling the number of logon attempts . 56 New in Version 6.2.2 Fix Pack 2 .......4 Duper process for optimizing situations ....57 New in Version 6.2.2 Fix Pack 1 .......8 New in Version 6.2.2...........9 Chapter 4. Setting up asymmetric New in Version 6.2.1 ..........12 encryption .............59 New in Version 6.2.0 ..........15 Setting the JRE for GSKit and starting Key Manager 59 IBM Tivoli Monitoring family of products ....18 Creating a new key database ........60 Tivoli Management Services components ....19 Creating a new public-private key pair and Tivoli Enterprise Portal client ........20 certificate request ............60 Desktop, Browser, and Java Web Start clients .
  • 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.
  • 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.
  • Windows in Concurrent PC

    Windows in Concurrent PC

    Using Concurrent PC DOS OTHER BOOKS BY THE AUTHOR Microcomputer Operating Systems (1982) The Byte Guide to CP/M-86 (1984) Using Concurrent PC DOS Mark Dahmke McGraw-Hili Book Company New York St. Louis San Francisco Auckland Bogota Hamburg Johannesburg London Madrid Mexico Montreal New Delhi Panama Paris Sao Paulo Singapore Sydney Tokyo Toronto Library of Congress Cataloging-in-Publication Data Dahmke, Mark. U sing Concurrent PC DOS. Bibliography: p. Includes index. 1. Concurrent PC DOS (Computer operation system) 1. Title. QA76.76.063D34 1986 005.4' 469 85-15473 ISBN 0-07-015073-7 Copyright © 1986 by McGraw-Hili, Inc. All rights reserved. Printed in the United States of America. Except as permitted under the United States Copyright Act of 1976, no part of this publication may be reproduced or distributed in any form or by any means, or stored in a data base or retrieval system, without the prior written permission of the publisher. 1234567890 DOC/DOC 893210876 ISBN 0-07-015073-7 The editors for this book were Steven Guty and Vivian Koenig, the designer was Naomi Auerbach, and the production supervisor was Teresa F. Leaden. It was set in Century Schoolbook by Byrd Data Imaging. Printed and bound by R. R. Donnelley & Sons Company. To my sister Patricia Contents Chapter 1. Introduction 1 What Is Concurrent PC DOS? 1 What Is an Operating System? 1 The DOS Family Tree 3 The Scope of This Book 5 Chapter 2. Concurrent PC DOS Compatibility 6 Concurrent PC DOS Compatibility 6 PC·DOS, TopView, and the IBM PC AT 7 Concurrent CP/M·86 9 Chapter 3.
  • 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.
  • 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.
  • PG-FP4 Flash Programmer User's Manual

    PG-FP4 Flash Programmer User's Manual

    User’s Manual PG-FP4 Flash Programmer Document No. U15260EE3V1UM00 Date Published May 2006 © NEC Electronics Corporation 2006 Printed in Germany © NEC Corporation 2006 2 User’s Manual U15260EE3V1UM00 The information in this document is subject to change without notice. No part of this document may be copied or reproduced in any form or by any means without the prior written consent of NEC. NEC assumes no liability for infringement of patents or copyrights of third parties by or arising from use of a product described herein. NEC Corporation (NEC) established proven quality assurance procedures for all products manufactured by or on behalf of NEC. As part of product qualification process an intensive release test procedure has been established and executed before the products are released for mass production and delivered to our clients. NEC Electronics Europe GmbH (NEC-EE) on behalf of NEC would like to inform, that the standard quality assurance procedure(s) have not been fully applied to this product and its documentation and that NEC cannot assure the full and error free function and/or the standard quality level. User’s Manual U15260EE3V1UM00 3 FP4 complies with the EMC protection requirements WARNING This is a ‘Class A’ ( EN 55022 : 1998) equipment. This equipment can cause radio frequency noise when used in the residential area. In such cases, the user/operator of the equipment may be required to take appropriate countermeasures under his responsibility. EEDT-ST-001-11 CAUTION This equipment should be handled like a CMOS semiconductor device. The user must take all precautions to avoid build-up of static electricity while working with this equipment.
  • Python Intelhex Library Documentation Release 2.2.1

    Python Intelhex Library Documentation Release 2.2.1

    Python IntelHex library Documentation Release 2.2.1 Alexander Belchenko Jan 30, 2018 Contents 1 Introduction 3 1.1 About...................................................3 1.1.1 Motivation............................................3 1.2 License..................................................4 1.3 Installation................................................4 1.3.1 Installing with pip........................................4 1.3.2 Download sources........................................4 1.3.3 Get source code with git....................................4 1.3.4 Install from sources.......................................5 1.3.5 Note for Windows users....................................5 1.4 Python 3 compatibility..........................................5 1.4.1 Which Python version should you use?.............................5 2 Basic API and usage 7 2.1 Initializing the class...........................................7 2.2 Reading data...............................................7 2.3 Basic data inspection...........................................8 2.4 More data inspection...........................................8 2.4.1 Summarizing the data chunks.................................. 10 2.5 Writing out data............................................. 10 2.5.1 Data converters......................................... 10 2.5.2 Writing data in chunks..................................... 11 2.6 Merging two hex files.......................................... 11 2.7 Creating Intel Hex files from scratch................................... 11