DOCSLIB.ORG

Reference Manual

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Reference Manual SRecord Reference Manual Scott Finneran <[email protected]> Peter Miller <[email protected]> . This document describes SRecord version 1.64 and was prepared 22 June 2014. This document describing the SRecord program, and the SRecord program itself, are Copyright 2014 Scott Finneran <[email protected]> Copyright Peter Miller <[email protected]> This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) anylater version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without eventhe implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICU- LAR PURPOSE. See the GNU General Public License for more details. Youshould have receivedacopyofthe GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>. 0 Table of Contents(SRecord) Table of Contents(SRecord) The README file . ................. 1 Release Notes ................... 5 Howtobuild SRecord ................. 16 Howtoadd a newfile format ............... 20 Howtoadd a newfilter . ................ 24 srec_cat(1) Manipulate EPROM load files . ............. 27 srec_cmp(1) Compare twoEPROM load files for equality .......... 35 srec_examples(1) Examples of howtouse SRecord ............. 38 srec_info(1) Information about EPROM load files . ........... 51 srec_input(1) Input file specifications . ............... 54 srec_license(1) GNU General Public License ............... 68 srecord_license(3) GNU Lesser General Public License ............ 78 srec_aomf(5) Intel Absolute Object Module Format . ........... 81 srec_ascii_hex(5) Ascii-Hexfile format ................. 83 srec_atmel_generic(5) Atmel Generic file format ................ 84 srec_binary(5) Binary file format .................. 85 srec_brecord(5) Freescale MC68EZ328 Dragonball bootstrap record format ..... 87 srec_coe(5) Xilinx Coefficient File Format . ............. 88 srec_cosmac(5) RCA Cosmac Elf file format ............... 89 srec_dec_binary(5) DEC Binary (XXDP) file format .............. 90 srec_emon52(5) Elektor Monitor (EMON52) file format ........... 91 srec_fairchild(5) Fairchild Fairbug file format ............... 93 srec_fastload(5) LSI Logic Fast Load file format .............. 94 srec_formatted_binary(5) Formatted Binary file format ............... 95 srec_forth(5) FORTH file format .................. 96 srec_fpc(5) Four Packed Code (FPC) file format ............ 97 srec_idt(5) IDT/sim binary file format ...............100 srec_intel16(5) Intel Hexadecimal 16-bit file format specification . .......101 srec_intel(5) Intel Hexadecimal object file format specification . .......105 srec_logisim(5) format Logisim EPROM load files . ............111 srec_mem(5) Lattice Memory Initialization format ............112 srec_mif(5) Memory Initialization File (MIF) format ...........114 srec_mips_flash(5) MIPS-Flash file format .................117 srec_mos_tech(5) MOS Technology file format ...............119 srec_motorola(5) Motorola S-Record hexadecimal file format ..........121 srec_msbin(5) Windows CE Binary Image Data Format . ..........123 srec_needham(5) Needham EMP-series programmer ASCII file format .......125 srec_os65v(5) OS65V Loader file format ................126 srec_ppb(5) Stag Prom Programmer binary format ............127 srec_ppx(5) Stag Prom Programmer hexadecimal format ..........128 srec_signetics(5) Signetics file format ..................129 srec_spasm(5) SPASM file format ..................131 srec_spectrum(5) Spectrum file format .................132 srec_stewie(5) Stewie’sbinary file format ................133 srec_tektronix(5) Tektronix hexadecimal file format .............135 srec_tektronix_extended(5) Tektronix Extended hexadecimal file format ..........137 srec_ti_tagged_16(5) Texas Instruments Tagged (SDSMAC320) file format .......138 srec_ti_tagged(5) Texas Instruments Tagged (SDSMAC) file format ........141 srec_ti_txt(5) Texas Instruments ti-txt (MSP430) file format .........144 srec_trs80(5) Radio Shack TRS-80 object file format specification . ......145 srec_vmem(5) VMEM file format ..................147 srec_wilson(5) Wilson file format ..................
Load more

Recommended publications
  • Hacker's Handbook for Ringzer0 Training, by Steve Lord
    Hacker’s Handbook For Ringzer0 Training, by Steve Lord This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License. Copyright ©2021 Raw Hex Ltd. All Rights Reserved. Retro Zer0 is a trademark of Ring Zer0 Training. Raw Hex is a trademark of Raw Hex Ltd. All other trademarks are the property of their respective owners. Raw Hex Ltd reserve the right to make changes or improvements to equipment, software and documentation herein described at any time and without notice. Notice: Please be advised that your Retro Zer0 has no warranty, and that tampering with the internal hardware and software of your Ring Zer0 is widely encouraged as long as you do so with appropriate regard to safety. Contents 1 Preface 5 1.1 Safety ........................... 6 1.2 Understanding This Document ............ 6 2 Before You Start 7 2.1 Check You Have Everything .............. 7 2.2 Back Up The SD Card ................. 8 2.3 Connecting Up Your Retro Zer0 ............ 8 2.4 Powering Up ....................... 10 2.5 Resetting Your Retro Zer0 . 10 2.6 Powering Down ..................... 10 3 First Steps 11 3 4 CONTENTS 3.1 Testing The Keyboard . 11 3.2 Using CP/M ....................... 12 3.3 Would You Like To Play A Game? . 14 3.4 MultiCPM Extras ..................... 17 3.5 Useful Tools ....................... 19 3.6 What’s On The Card? . 20 3.7 Putting It All Together . 23 3.8 Where To Read More . 25 4 Being Productive With Retro Zer0 27 4.1 WordStar .........................27 4.2 Supercalc .........................30 4.3 DBase ...........................32 4.4 Microsoft BASIC .....................32 4.5 Turbo Pascal .......................34 4.6 Forth 83 .........................36 4.7 ZDE ............................38 4.8 Z80 Assembler .....................39 4.9 Hi-Tech C .........................43 4.10 XLisp ...........................46 CONTENTS 5 4.11 Installing New Software .
    [Show full text]
  • The Control of Routine Fish Maneuvers: Connecting Midline Kinematics to Turn Outcomes
    Received: 16 June 2020 | Accepted: 17 June 2020 DOI: 10.1002/jez.2398 RESEARCH PAPER The control of routine fish maneuvers: Connecting midline kinematics to turn outcomes Stephen P. Howe | Henry C. Astley Department of Biology, Biomimicry Research and Innovation Center, University of Akron, Abstract Akron, Ohio Maneuverability is an important factor in determining an animal's ability to navigate Correspondence its environment and succeed in predator–prey interactions. Although fish are cap- Stephen P. Howe, Department of Biology, Biomimicry Research and Innovation Center, able of a wide range of maneuvers, most of the literature has focused on escape University of Akron, 235 Carroll St., Rm D401, maneuvers while less attention has been paid to routine maneuvers, such as those Akron, OH 44325‐3908. Email: [email protected] used for habitat navigation. The quantitative relationships between body deforma- tions and maneuver outcomes (displacement of the center of mass and change in trajectory) are fundamental to understanding how fish control their maneuvers, yet remain unknown in routine maneuvers. We recorded high‐speed video of eight giant danios (Devario aquepinnatus) performing routine and escape maneuvers and quan- tified the deformation of the midline, the heading of the anterior body, and the kinematics of the centroid (a proxy for center of mass). We found that both routine and escape behaviors used qualitatively similar independent body bending events, which we curvature pulses, that propagate from head to tail but show quantitative differences in midline kinematics and turn outcomes. In routine maneuvers, the direction change and acceleration of the fish are influenced by both the magnitude of the bending pulse and by the duration of the pulse, whereas in escape maneuvers, only pulse duration influenced direction change and turn acceleration.
    [Show full text]
  • ACUCOBOL-GT® Version 8.1.3
    User’s Guide ACUCOBOL-GT® Version 8.1.3 Micro Focus 9920 Pacific Heights Blvd San Diego, CA 92121 858.795.1900 © Copyright Micro Focs (IP) LTD. 1998-2010. All rights reserved. Acucorp, ACUCOBOL-GT, Acu4GL, AcuBench, AcuConnect, AcuServer, AcuSQL, AcuXDBC, extend, and “The new face of COBOL” are registered trademarks or registered service marks of Micro Focus. “COBOL Virtual Machine” is a trademark of Micro Focus. Acu4GL is protected by U.S. patent 5,640,550, and AcuXDBC is protected by U.S. patent 5,826,076. Microsoft and Windows are registered trademarks of Microsoft Corporation in the United States and/or other countries. UNIX is a registered trademark of the Open Group in the United States and other countries. Solaris is a trademark of Sun Microsystems, Inc., in the United States and other countries. Other brand and product names are trademarks or registered trademarks of their respective holders. E-01-UG-100501-ACUCOBOL-GT-8.1.3 Contents Chapter 1: Introduction 1.1 ACUCOBOL-GT Documentation ................................................................................... 1-2 1.2 Product Overview ............................................................................................................1-2 1.2.1 Portability and Compatibility ................................................................................ 1-4 1.2.2 Native Instructions................................................................................................. 1-4 1.2.3 The ACUCOBOL-GT Runtime............................................................................
    [Show full text]
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • SAF1761 Hi-Speed Universal Serial Bus On-The-Go Controller Rev
    SAF1761 Hi-Speed Universal Serial Bus On-The-Go controller Rev. 2 — 19 June 2012 Product data sheet 1. General description The SAF1761 is a single-chip Hi-Speed Universal Serial Bus (USB) On-The-Go (OTG) Controller integrated with advanced NXP slave host controller and the peripheral controller. The Hi-Speed USB host controller and peripheral controller comply to Ref. 1 “Universal Serial Bus Specification Rev. 2.0” and support data transfer speeds of up to 480 Mbit/s. The Enhanced Host Controller Interface (EHCI) core implemented in the host controller is adapted from Ref. 2 “Enhanced Host Controller Interface Specification for Universal Serial Bus Rev. 1.0”. The OTG controller adheres to Ref. 3 “On-The-Go Supplement to the USB Specification Rev. 1.3”. The SAF1761 has three USB ports. Port 1 can be configured to function as a downstream port, an upstream port or an OTG port; ports 2 and 3 are always configured as downstream ports. The OTG port can switch its role from host to peripheral, and peripheral to host. The OTG port can become a host through the Host Negotiation Protocol (HNP) as specified in the OTG supplement. 2. Features and benefits Automotive qualified in accordance with AEC-Q100 Compliant with Ref. 1 “Universal Serial Bus Specification Rev. 2.0”; supporting data transfer at high-speed (480 Mbit/s), full-speed (12 Mbit/s) and low-speed (1.5 Mbit/s) Integrated Transaction Translator (TT) for original USB (full-speed and low-speed) peripheral support Three USB ports that support three operational modes: Mode 1: Port 1
    [Show full text]
  • Practical C++ Programming Copyright 2003 O'reilly and Associates Page 1 I/O Packages
    Chapter - 16 File Input/ Output Practical C++ Programming Copyright 2003 O'Reilly and Associates Page 1 I/O Packages There are 3 different I/O packages available to the C++ programmer: • The C++ streams package. This package is used for most I/O. • The unbuffered I/O package. Used primarily for large file I/O and other special operations. • The C stdio package. Many older, C-- programs use this package. (A C-- program is a C program that has been updated to compile with a C++ compiler, but uses none of the new features of the new language.) This package is useful for some special operations. Practical C++ Programming Copyright 2003 O'Reilly and Associates Page 2 C++ I/O C++ provides four standard class variables for standard I/O. Variable Use std::cin Console in (standard input) std::cout Console output (standard output) std::cerr Console error (standard error) std::clog Console log Normally std::cin reads from the keyboard, and std::cout, cerr, and clog go to the screen. Most operating systems allow I/O redirection my_prog <file.in my_prog >file.out Practical C++ Programming Copyright 2003 O'Reilly and Associates Page 3 File I/O File I/O is accomplished using the <fstream.h> package. Input is done with the ifstream class and output with the ofstream class. Example: ifstream data_file; // File for reading the data from data_file.open("numbers.dat"); for (i = 0; i < 100; ++i) data_file >> data_array[i]; data_file.close(); Open can be consolidated with the constructor. ifstream data_file("numbers.dat"); The close will automatically be done by the destructor.
    [Show full text]
  • HUMBUG® 68000 Version
    HUMBUG® 68000 Version by Peter A. Stark Copyright © 1986 - 1990 by Peter A. Stark Star-K Software Systems Corporation P. O. Box 209 Mt. Kisco, N. Y. 10549 All rights reserved Copyright © 1986 - 1990 by Peter A. Stark All Star-K computer programs are licensed on an "as is" basis without warranty. Star-K Software Systems Corporation shall have no liability or responsibility to customer or any other person or entity with respect to any liability, loss or damage caused or alleged to be caused directly or indirectly by computer equipment or programs sold by Star-K, including but not limited to any interruption of service, loss of business or anticipatory profits or consequential damages resulting from the use or operation of such computer or computer programs. Good data processing procedure dictates that the user test the program, run and test sample sets of data, and run the system in parallel with the system previously in use for a period of time adequate to insure that results of operation of the computer or program are satisfactory. SOFTWARE LICENSE A. Star-K Software Systems Corp. grants to customer a non-exclusive, paid up license to use on customer's computer the Star-K computer software received. Title to the media on which the software is recorded (cassette and/or disk) or stored (ROM) is transferred to customer, but not title to the software. B. In consideration of this license, customer shall not reproduce copies of Star-K software except to reproduce the number of copies required for use on customer's computer and shall include the copyright notice on all copies of software reproduced in whole or in part.
    [Show full text]
  • Assembly Language Step-By-Step: Programming with DOS and Linux
    Assembly Language Step-by-Step: Programming with DOS and Linux, Second Edition by Jeff Duntemann ISBN:0471375233 John Wiley & Sons © 2000 (613 pages) A “Lost World” journey into 16-bit assembler programming concepts and techniques. <?xml version="1.0" encoding="ISO-8859-1"?> Table of Contents Assembly Language Step-by-Step—Programming with DOS and Linux, Second Edition Foreword Introduction - "Why Would You Want to Do That?" Another Pleasant Valley Saturday Understanding What Computers Chapter 1 - Really Do Chapter 2 - Alien Bases Getting Your Arms around Binary and Hexadecimal Chapter 3 - Lifting the Hood Discovering What Computers Actually Are The Right to Assemble The Process of Making Assembly Language Chapter 4 - Programs NASM-IDE: A Place to Stand Give me a lever long enough, and a Chapter 5 - place to stand, and I will move the Earth. An Uneasy Alliance The x86 CPU and Its Segmented Memory Chapter 6 - System Following Your Instructions Meeting Machine Instructions up Close Chapter 7 - and Personal Chapter 8 - Our Object All Sublime Creating Programs that Work Dividing and Conquering Using Procedures and Macros to Battle Chapter 9 - Complexity Bits, Flags, Branches, and Tables Easing into Mainstream Chapter 10 - Assembly Programming Chapter 11 - Stringing Them Up Those Amazing String Instructions The Programmer's View of Linux Tools and Skills to Help You Write Chapter 12 - Assembly Code under a True 32-Bit OS Coding for Linux Applying What You've Learned to a True Chapter 13 - Protected Mode Operating System Conclusion - Not the End, But Only the Beginning Appendix A - Partial 8086/8088 Instruction Set Reference Appendix B - Segment Register Assumptions for Real Mode Segmented Model Appendix C - Web URLs for Assembly Programmers Appendix D - Segment Register Assumptions Appendix E - What's on the CD-ROM? Index List of Figures List of Tables Back Cover The bestselling guide to assembly language--now updated and expanded to include coverage of Linux.
    [Show full text]
  • ISP1761 Hi-Speed Universal Serial Bus On-The-Go Controller Rev
    ISP1761 Hi-Speed Universal Serial Bus On-The-Go controller Rev. 04 — 5 March 2007 Product data sheet 1. General description The ISP1761 is a single-chip Hi-Speed Universal Serial Bus (USB) On-The-Go (OTG) Controller integrated with advanced NXP slave Host Controller and the NXP ISP1582 Peripheral Controller. The Hi-Speed USB Host Controller and Peripheral Controller comply to Ref. 1 “Universal Serial Bus Specification Rev. 2.0” and support data transfer speeds of up to 480 Mbit/s. The Enhanced Host Controller Interface (EHCI) core implemented in the Host Controller is adapted from Ref. 2 “Enhanced Host Controller Interface Specification for Universal Serial Bus Rev. 1.0”. The OTG Controller adheres to Ref. 3 “On-The-Go Supplement to the USB Specification Rev. 1.2”. The ISP1761 has three USB ports. Port 1 can be configured to function as a downstream port, an upstream port or an OTG port; ports 2 and 3 are always configured as downstream ports. The OTG port can switch its role from host to peripheral, and peripheral to host. The OTG port can become a host through the Host Negotiation Protocol (HNP) as specified in the OTG supplement. 2. Features n Compliant with Ref. 1 “Universal Serial Bus Specification Rev. 2.0”; supporting data transfer at high-speed (480 Mbit/s), full-speed (12 Mbit/s) and low-speed (1.5 Mbit/s) n Integrated Transaction Translator (TT) for Original USB (full-speed and low-speed) peripheral support n Three USB ports that support three operational modes: u Mode 1: Port 1 is an OTG Controller port, and ports 2 and 3 are Host
    [Show full text]