DOCSLIB.ORG

Sirius 1 CP/M-86 Manuals

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

SIRIUS 1 User’s Guide for CP/M-86 sinus NOTICES COPYRIGHT © Sirius Systems Technology, Inc., 1982. All rights reserved. © Digital Research, Inc. 1982. All rights reserved. TRADEMARKS CP/M is a registered trademark of Digital Research, Inc. ASM-S-5, CBASIC-86, CP/M-86, and DDT-86 are trademarks of Digital Research, Inc. DISCLAIMER Sirius Systems Technology, Inc. makes no representations or warranties of any kind with respect to the contents hereof and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose. Sirius shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material. Further, Sirius reserves the right periodically to revise this publication and to make changes in the content hereof without obligation of Sirius to notify any person of such revision or changes. > „ PROPRIETARY This document contains proprietary information which is protected by NOTICE copyright. All rights reserved. No part of this publication may be reproduced, transcribed, stored in a retrieval system, translated into any language or computer or transmitted in any form, without the prior written consent of Sirius Systems Technology, Inc., 380 El Pueblo Road, Scotts Valley, California 95066. PART NUMBER 100919-01 Printed in U.S.A. CONTENTS (1 S E f\ Gi u < D 1. Introduction 1.1 Manual Contents .............................................................................. 1 12 Manual Conventions ....................................................................... 2 1.3 Related Publications .............................. ......................................... 2 2. CP/M-86 Overview 2.1 Components ................................................................................... 5 22 Input/Output Devices ..................................................................... 5 2.3 Basic Operating Principles and Notes ............... ............................ 6 2.4 Entering and Modifying CP/M-86 Commands .............................. 7 2.5 File System .................................................................................... 7 2.5.1 File Specifiers ............................................................................... 7 2.52 CP/M-86 File Extension Conventions ......................................... 10 2.5.3 Valid and Invalid Fiie Specifiers ........................ .......................... 10 2.5.4 Wild-Card Characters .................................................................. 11 3. CP/M-86 3.1 Loading CP/M-86 . ........................................................................ 13 Basic Operating 32 Changing the Default Drive ............................................................ 13 Procedures 3.3 Changing Diskettes at the CP/M-86 System Level ........................ 13 3.4 Controlling Console Output ............................................................ 14 3.5 Loading CP/M-86 or Programs from Drive B ................................ 14 4. Device and 4.1 Diskette Formatting — The FORMAT Program ............................. 17 Media Management 4.1.1 Using FORMAT ............................... ........................................... 17 4.12 Using FORMAT Switches ............................................................ 18 42 Diskette Backup — The DCOPY Program .................................... 19 42.1 Using DCOPY with Interactive System Prompts ............................. 20 422 Using DCOPY without System Prompts ..................................... 21 4.3 Operating System Copy — The BOOTCOPY Program ............... 22 4.4 Device and Fiie Status — The STAT Program ............................ 23 4.4.1 Available Space on All Drives .................................................... 24 4.42 Available Space on a Specified D rive ......................................... 25 4.4.3 File Information ............................................................................. 25 4.4.4 Setting a Fiie or Diskette to Read-Only or Read-Write Status . 26 4.4.5 Excluding Fiie Names from the Directory .................................... 26 4.4.6 Displaying STAT Command Parameters .................................... 27 4.4.7 Displaying Drive Characteristics .................................................. 27 4.4.8 Physicai-to-Logicai Device Assignments .................................... 28 5. File System 5.1 The DIR Command ......................................................................... 29 Management 5.1.1 DIR Command Format ................................................................. 29 5.12 DIR Command Examples ............................................................ 29 52 The TYPE (Display) Command ...................................................... 30 5.3 The ERA (Delete) Command ........................................................ 31 5.4 The REN (Rename) Command ...................................................... 31 5.5 PIP — Peripheral Interchange Program ......................................... 32 5.5.1 Loading PIP ................................................................................ 32 5.52 Copying Files With PIP ............................................................... 33 5.5.3 Using PIP Parameters ................................................................. 35 5.5.4 Outputting Files To Logical Devices With PIP ............................ 36 5.5 The SUBMIT Command and .SUB Fiies ....................................... 38 U S t (ilO (Df 6. Creating and Editing 6.1 Activating the Text Editor ................................................................. 41 Text Files 62 Basic Operating Principles ............................................................... 41 6.3 Creating a Text F ile ......................................................................... 42 6.4 Editing an Existing File .................................................................... 42 6.5 Text Transfers Between the Edit Buffer and ASCII Files ............... 43 6.6 The Character Pointer ..................................................................... 45 6.7 Modifying Text ................................................................................. 46 6.8 Command String Usage .................................................................. 47 6.9 Sample ED Session ......................................................................... 48 6.10 ED Error Message and Error Indicators ........................................ 49 6.11 Alternate Character Summary ....................................................... 49 6.12 ED Command Summary................................................................ 50 Appendixes Appendix A: CP/M-86 Command Format Summary .......................... 51 Appendix B: CP/M-86 Error Messages ....................... ........................ 53 Appendix C: BDOS Error Messages ..................................................... 55 Appendix D: Error Codes and Definitions ............................................. 57 Appendix E SIRIUS Utility Error Messages ......................................... 59 VI FIGURES 2-1: File Specifier Structure................................................................ 9 6-1: Edit Buffer/Edit Fiie Interaction................................................... 44 TABLES 2-1: Logical and Physical Devices .................................................... 6 2-2: Alternate-Key Command-Line Editing Functions ....................... 7 2- 3: CP/M-86 Fiie Extension Conventions .................................... 10 3- 1: Console Output Alternate Characters .................................... 14 4- 1: STAT Command Options ....................................................... 24 4- 2: Physical-to-Logical Device Assignments................................. 28 5- 1: PIP Command Parameters ..................................................... 35 5- 2: Logical Devices and Special Terms Used With PIP .............. 37 6- 1: Edit Buffer - Text Fiie Transfer Command ............................ 43 6-2: Character-Pointer Related Commands ...................................... 45 6-3: Text Modification Commands .................................................... 46 6-4: Command String Alternate-Characters ...................................... 47 6-5: ED Error Indicators .................................................. .................. 49 6-6: Text Editor Alternate-Character Commands .............................. 49 6-7: Alphabetical List of ED Commands ........................................... 50 A-1: CP/M-86 Command Format Summary...................................... 51 B-1: CP/M-86 Error Messages ........................................................ 54 D-1: SIRIUS Error Code Definitions ................................................... 58 E-1: SIRIUS Utility Error Messages .................................................. 59 IX MANUAL PRINTING CONVENTIONS This manual uses two-color printing in examples to differentiate computer messages from user entries. Computer output is black, and user entries are grey. The following symbols and abbreviations are used in examples to represent pressing certain keys: -«-* represents pressing the Return key, and represents pressing the Space bar. Examples and parts of tables show Alternate function (Alt key) characters as bold face upper case letters. For example, the key sequence Alt C is indicated as C. XI 1 INTRODUCTION 1. INTRODUCTION This manual describes the CP/M-86 operating system,
Recommended publications
  • Club-80 Heft 41 (Bw Ocr).Pdf

    Club-80 Heft 41 (Bw Ocr).Pdf

    Inhaltsverzeichnis * . Autor & Seite Autor & Seite Clubinternes Hardware Zusammenfassung Fragebogenaktion 1-5 Floppy-Tester 65- 66 Jens Neueder Artikel aus Elektor Neues vom Vorstand 6 - 8 Club 80-Neumitglieder aus "CP/M-aktuell"-Usergruppe Auswertung der Fragebogen zur Mitgliederkarteiaktualisierung Nachträge zum Vorwort 9-10 Club 80 Börse 67 Hartmut Obermann Suche... Uwe Schobert Clubinfo H - 12 Termine 13 Jens Neueder Sonstiges Neuigkeiten für CP/M 69 Vorstellung 13 - 14 Alexander Schmid Jörg Lindner Genie News: Neue Preisstrukturen 70- 71 Software Wissenswertes ZCPR oder Z3Plus 72- 73 Literaturrecherche: USA, England, Deutschland 73-85 Austausch von Grafiken DOS -> CP/M 15 - 18 Egbert Schröer Alexander Schmid Wichtige T ip s... Elektrikers 86 Grafik des Gills unter Holte CP/M + 19-26 Alexander Schmid Volker Dose, Egbert Schröer Model 4 intern: Dem Interpreter aufs Bit geschaut 27 - 35 Artikel aus CP Die letzten Seiten Impressum 87 MSDOS-Trick: Command /F 35 Schluß 88 Insider-Info: Windows-Fehler 68 Redaktion Hartmut Obermann Mitgliederadressenliste am INFO-Ende Microsoft Link80 und .SYM-Datei 36 Sonderheft: Wissenswertes rund um den Z280 am INFO-Ende Uwe Schobert Software-Technik und Compilerbau 37-38 Artikel aus PASCAL IMP - ein DFÜ-Programm für CP/M 39-44 Günther W. Braun Internet und UUCP mit CP/M 45- 58 Volker Dose Internet via Genie 59- 62 GE-Mail aud Internet Access 63- 64 Egbert Schröer Fragebogenaktion Auswertung/Zusammenfassung Von 70 versandten Fragebögen erhielten wir bisher 43 mehr oder weniger vorhandene Erfahrungen: ausgefüllt wieder zurück. Die folgenden Seiten geben eine Zusammenfassung 21 Club-Mitglieder würden gern ihre Hard- und/oder Softwareerfahrungen den Eurer Antworten/Angaben wieder.
  • 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.
  • DOS Technical Reference

    DOS Technical Reference

    -------- - ---- Personal Computer - ---- - --- ------ - . - Programming Family DOS Technical Reference 6138536 Preliminary First Edition (February 1985) The following paragraph does not apply to the United Kingdom or any country where such provisions are inconsistent ~ith local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES TIllS PUBLICATION "AS IS" wrrnom WARRANTY OF ANY KIND, EmlER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 1HE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. lbis publication could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and!or changes in the product(s) and/or the program(s) described in this pUblication at any time. It is possible that this publication may contain reference to, or information about, IBM products (machines and programs), programming, or services that are not announced in your country. Such references or information must not be construed to mean that IBM intends to announce such IBM products, programming, or services in your country. Products are not stocked at the address below. Requests for copies of this publication and for technical information about IBM Personal Computer products should be made to your authorized IBM Personal Computer dealer, IBM Product Center, or your IBM Marketing Representative. The following paragraph applies only to the United States and Puerto Rico: A Reader's Comment Form is provided at the back of this publication. If the form has been removed.
  • 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.
  • PC DOS 7 Technical Update

    PC DOS 7 Technical Update

    PC DOS 7 Technical Update Document Number GG24-4459-00 February 1995 International Technical Support Organization Boca Raton Center Take Note! Before using this information and the product it supports, be sure to read the general information under “Special Notices” on page xiii. First Edition (February 1995) This edition applies to PC DOS Version 7. Order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at the address given below. An ITSO Technical Bulletin Evaluation Form for reader′s feedback appears facing Chapter 1. If the form has been removed, comments may be addressed to: IBM Corporation, International Technical Support Organization Dept. 91J Building 235-2 Internal Zip 4423 901 NW 51st Street Boca Raton, Florida 33431-1328 When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. Copyright International Business Machines Corporation 1995. All rights reserved. Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. Abstract IBM PC DOS 7 has been designed for all types of users who need an efficient single tasking personal computer operating system. It incorporates many new utilities such as anti-virus software, comprehensive backup programs, PCMCIA support and DOS Pen extensions. Also incorporated are new features to enhance the available memory and disk space. This book is a technical reference, upgraded from IBM DOS 5.02 and written for DOS programmers, who develop applications for IBM Personal Computers or compatible systems.
  • 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