Home

Fluke 9010 Compiler

1. Wl Vibe E 3 9 What You Need ve csesirs acecesesscendinteiaielen s eerste eres e 3 9 Backing Up the Program Diskette 3 9 Verifying the Working Diskette 3 10 Hooking Up the 3 10 System Dependencies 3 12 eae 3 12 Disk Space ret 3 12 IBM Personal Computer 3 13 Introduction E oe 3 13 What You Need oA en ane 3 13 Backing Up the Program Diskette 3 14 Verifying the Working 3 14 Hooking 3 15 System Editor aro enner eE E ERER 3 16 RETURN Key 3 16 CONTENTS continued CP M Operating Systems cee ec ee scene 3 17 Introduction cece eee cere cee cette eee cence 3 17 What You Need ats sales 0 Wiel 3 17 Backing Up the Program Diskette 3 18 Verifying the Working 3 18 Hooking Up the 3 19 Installing Software 3 20 Editors oaea chavs eather 3
2. B04 3 4 Backing Up the Program Diskette 34 Verifying the Working Diskette 3 5 Hooking 3 6 System Dependencies ccc cee cee 3 8 Test Editor Ghia esa tae Ta eae eT 3 8 Disk Space wha So coats eae a 3 8 Compiler 3 8 i continued on page ii CONTENTS continued Fluke 1722A Instrument Controller 3 9 Introduction 3 9 3 9 Backing Up the Program Diskette 3 9 Verifying the Working Diskette 3 10 Hooking Up the System ccc cece cece cece cece 3 10 System Dependencies 3 12 Text Bde i ciate is ew a a ethan eas wae 3 12 Disk Sp te Sak ik a lS 3 12 IBM Personal Computer cc cece cece cece ee 3 13 EG SE 3 13 What You Need 3 13 Backing Up the Program Diskette 3 14 Verifying the Working Diskette 3 14 9 3 15 System Editor isset aeaa n a a EEA E RES N 3 16 RETURN 3 16 CP M Operating
3. 6 109 6 11 613 Write lace a Tater 6 115 continued on page v iv CONTENTS continued APPENDICES A ROY WOTKS EAE A l B Predefined Register Names C Optional Keywords and Keyword Abbreviations D Default Setup 5 D 1 E Patameter Limits se sesiis tenira RUE PEN ENE ENERE eed F Error Messages INDEX Vivi Section 1 Introduction CONTENTS Introduction to the 9010A Language Compiler 1 3 The Host Computer System cece cece cee eee 14 How the Compiler Works 1 5 Language 1 6 The 9010A Language Compiler Package 1 7 Disk 1 7 Compiler sec eed bie 1 7 File Transfer Program 1 7 Pod Data Piles cine acute eee areca 1 8 Use With the 9005A whew awa dere 1 8 1 1 1 2 INTRODUCTION TO 9010A LANGUAGE COMPILER The 9010A Language Compiler package is used to create test and troubleshooting programs for the Fluke 9010A Micro System Troubleshooter The 9010A is a
4. Language Compiler P N 661504 December 1983 f L LJ K f 1983 John Fluke Mfg Co Inc all rights reserved Litho in U S A This manual describes unpublished Software which contains the trade secrets and confidential proprietary information of John Fluke Mfg Co Inc and which embodies substantial creative effort ideas and expressions THE SOFTWARE IS PROVIDED UNDER LICENSE FROM FLUKE Fluke grants Licensee a perpetual non exclusive license to use this material and make up to three copies for backup purposes without written permission from Fluke THIS SOFTWARE 8 LICENSED FOR USE ON A SINGLE COMPUTER SYSTEM LIMITED WARRANTY Fluke warrants that the Software has been properly recorded on non defective diskettes Fluke does not warrant the Software to be error free Fluke will replace such diskettes without charge if Fluke in good faith determines that such diskettes were not subject to misuse and if returned to a Fluke Technical Service Center within ninety 90 days of shipment Refer to your 9010A Operator Manual for a listing of locations Fluke reserves the right to change the specifications and operating characteristics of the Software it produces over a period of time without notice FLUKE GRANTS NO OTHER WARRANTIES EITHER EXPRESSED OR IMPLIED INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABIL ITY OR FITNESS FOR A PARTICULAR PURPOSE OR USE IN NO EVENT SHALL FLUKE BE LIABLE FOR AN
5. CONTENTS Introduction bad Gee natok owe 6 3 Syntax Diagram Notation 6 4 Speci l Symbols 2 sod i5 6 5 Symbolic Names gorse scek ove ce erie oes hee Bales 6 6 EX pressions e ok Pau ews tS ea 2S 6 8 aleve wee 6 10 General Information 6 11 Statement Format 6 11 Program Comments 6 11 File eee Bina wee EEE Rees eke 6 12 SOURCE FILE SYNTAX 6 13 Source Pile dee a vais ob es VE WO ee eae 6 15 Setups ive ee went tates 6 17 Address Space 6 19 Address Descriptor 6 21 Global Declaration 6 23 Symbolic Register Name Declaration 0e000 6 25 Program 6 27 Program Body eves vice cd cen nd Bee eee wee dees ae eee 6 29 Local Declaration ey 6 31 Binary Program cee cece cee cee cere ence eee 6 33 Include Directive acc 6 35 SETUP PARAMETERS 6 37 9010A PROGRAM STATEMENTS 6 61 6 1 6 2 Language Reference
6. Compiled as PROGRAM 7 PROGRAM 20 Compiled as PROGRAM 20 PROGRAM PC Compiled as PROGRAM 21 Writing Programs Symbolic Names The following rules apply whenever a source file contains programs with actual program numbers Programs with actual program numbers must be in numeric order in the source file For example PROGRAM 5 must precede PROGRAM 20 There must be a large enough gap between two programs with actual program numbers for any intervening programs with symbolic names For example if the source file contains a PROGRAM 8 anda PROGRAM 11 PROGRAM 8 must precede PROGRAM and there can be at most two symbolically named programs between them EXAMPLE This example demonstrates the use of symbolic program names The compiler will assign PROGRAM 0 to MAIN and PROGRAM 1 to DELAY PROGRAM MAIN DPY THIS IS AN EXAMPLE EXECUTE DELAY DPY OF A VALID 9010A PROGRAM PROGRAM DELAY REG1 40 0 DEC REG1 IF REG1 gt 0 GOTO 0 4 25 Writing Programs Symbolic Names Symbolic Labels The symbolic label feature allows you to refer to a branching location with a mnemonic name providing the same advantages as symbolic program names 4 26 The following rules apply to symbolic labels Symbolic label names are not declared explicitly Simply using a name as the target of a GOTO or in a LABEL statement is sufficient to define a symbolic label name Within a single program symbolic label names cannot
7. Ws 6 3 Syntax Diagram Notation 6 4 Special Symbols 6 5 Symbolic Names lt dereie done tebe S 6 6 Expressions Sickest aie ie de a ead ease 6 8 sa be va hae ee 6 10 General Information 6 11 Statement Format ccc cece ce cee cee reece ee 6 11 Program Comments cece ecescececesees 6 11 Fil In Cl usin eae 6 12 SOURCE FILE SYNTAX 6 13 Source Pile ais nies PR eh ee TR 6 15 oles late Soe 6 17 AGGreSSS Pace ii 6 19 Address Descriptor 6 21 Global Declaration acesse ccc cee cee ce cee eee eee n eee 6 23 Symbolic Register Name Declaration ceeee 6 25 9010A Program eee cede tei a 6 27 Program Body ites nnen eane ten Pee eee 6 29 iii continued on page iv CONTENTS continued Local Declaration 6 31 Binary Program orate eed deena ethene 6 33 Include Directive 6 35 SETUP PARAMETERS 6 37 Beep es tai dls teats dee 6 39 Bus Tet SaaS
8. The 9010A Language Compiler package consists of this manual and a write protected program diskette containing the compiler itself and various other programs and data files Before using the compiler you should make a copy of the program diskette This copy should be used for normal day to day operations while the original program diskette should be kept in a safe place asa backup so that the working copy can be restored if it is ever damaged Complete instructions on how to copy diskettes can be found in the 1720A File Utility User Manual Getting Started 1720A Instrument Controller Verifying the Working Diskette Once you have created a working copy of the program diskette you should verify the integrity of its files by running VERIFY one of the programs included in the compiler package To run the VERIFY program type in response to the 1720A Console Monitor program prompt The VERIFY program checks the contents of the 1720A System Device SY0 to verify the integrity of the Compiler package files It calculates a checksum for each of the files and compares it to the checksum contained in the VERIFY DAT file VERIFY DAT is an ASCII file that contains a list of filenames and checksums for each of the files in the compiler package Results from the VERIFY program are printed in tabular form as each file is checked Missing files or checksum errors that could indicate either corrupted files or in
9. INTRODUCTION This section provides a quick reference for 9010A Language syntax As an aid to quick reference the information contained here is concise For an introduction to the language as a whole see Section 4 Writing Programs This section is organized as follows General Information Source File Syntax Setup Parameters 9010A Program Statements Program statements are introduced with a syntax diagram that illustrates the legitimate construction A complete definition of the various forms of the statement follow the syntax diagram The statement definitions use the format shown in the following example page STATEMENT NAME Syntax O gt Function A description of the function s performed by the statement appears here Characteristics implications and limitations of the statement are defined here e Example A programming example is shown here See Also Any related statements or information are listed here 6 3 Language Reference SYNTAX DIAGRAM NOTATION Syntax diagrams define correct spelling punctuation sequences of words symbols and expressions The syntax diagrams used here conform to the following guidelines Any path througha diagram starting from the left that does not run contrary to an arrowhead forms a legitimate statement Words in a circular enclosure are to be entered as shown Words can be typed in lowercase uppercase or a combination of lowercase and uppercase
10. Syntax eines Pad a c u Function Allows the operator control over 9010A error reporting and interactive handling of errors If YES isselected the 9010A displays detected error messages and prompts the operator to loop on the errors If NO is selected the errors are not reported to the operator but error messages are transmitted to the RS 232 if it is connected without the LOOP portion of the message The 9010A s default value is YES Example EXERCISE ERRORS NO See Also BEEP TRAP 6 45 6 46 LINESIZE Syntax Function Allows the programmer to specify the maximum number of characters transmitted per line when the 9010A is sending data through the AUX I F Setup parameter limits for LINESIZE are 10 255 The LINESIZE used is determined by the line size of your remote device The 9010A s default value is 79 Example LINESIZE 120 See Also NEWLINE STALL UNSTALL 6 47 6 48 NEWLINE Syntax Function When the 9010A is sending data through the AUX I F a terminator sequence is sent at the end of each line This statement allows the programmer to specify both the ASCII terminator characters to be sent and the delay between lines Setup parameter limits for NEWLINE are eight hexadecimal digits The 9010A default value is The selection of the terminator sequence allows the operator to meet the needs of a wide variety of remote devices
11. The 9010A started from a stall Check the port parameters and try again F 7 Error Messages No address descriptors to save You attempted to save address descriptors when none were transferred from the 9010A No program Information to save You attempted to save programs when none were transferred from the 90 0 Not a valld port The port name entered is not valid for the host system Use a valid port name Other Information already saved prevents entire file save You attempted to save an entire file after already saving other information Program program number already saved You attempted to save the same program more than once Program program number not found You attempted to save a program that was not transferred from the 9010A Programs already saved will cause illegal ordering You attempted to save all programs after some have already been saved Setup Information must precede program information You attempted to save setup information after saving programs Setup Information previously saved In this file You attempted to save setup information more than once F 8 Error Messages DISK VERIFICATION PROGRAM ERROR MESSAGES The following messages are the result of file configuration errors If the errors persist after an attempt to recopy the indicated files contact a Fluke Technical Service Center for advice Data file VERIFY DAT not found The file VERIFY DAT does not res
12. Writing Programs Coding Shortcuts File Inclusion To facilitate handling large collections of source code which can be shared by several programs the 9010A compiler provides a file inclusion feature This feature allows you to create a library of useful 9010A programs and use the file inclusion facility to merge them into a particular source file A line of the form INCLUDE filename in the source file will be replaced by the contents of the file filename when the program is compiled The effect is equivalent to manually entering the contents of the included file at that point in the source file EXAMPLE Assuming that the file PROMPT S contains PROGRAM 3 REG2 REG8 AND 7F REG1 REG8 SHR 7 AND 7F DPY PROBE U 1 PIN 2 then the source file PROGRAM 0 8 1A09 EXECUTE PROGRAM 3 INCLUDE PROMPT S have exactly the same effect as the source file PROGRAM 0 REG8 1A09 EXECUTE PROGRAM 3 PROGRAM 3 REG2 REG8 AND 7F REG1 REG8 SHR 7 AND DPY PROBE U 1 PIN 2 4 19 Writing Programs Coding Shortcuts Sample Program The following example is similar to the one given at the end of Part 1 but it takes full advantage of the abbreviation features The example assumes that the file PROBEI S contains the code for PROGRAM 1 PROBE2 S contains PROGRAM 2 and PROMPTSS contains PROGRAM 3 This program tests the 052 flip flop on the output side of the 8255 PIA on the NEC TK 80A single boa
13. Writing Programs General Program Format Setup Information The 9010A Language allows any or all of the setup parameters to be specified in the same form produced by the 9010A AUX I F SETUP keys The 9010A setup functions allow the operator to control the reporting of UUT errors enable microprocessor lines and specify operating parameters The 9010A Operator Manual contains complete information on the various setup parameters that can be specified The following rules apply to setup information e Setup information must appear at the beginning of the source file preceding all 9010A programs i e before the firt PROGRAM statement The setup information may appear either before or after any address space information You can specify all of the setup parameters some of them or none of them Setup parameters that are not explicitly set assume default values contained in the pod data file if a pod data file is specified or to the power up values supplied by the 9010A Some setup information is pod dependent The pod unique information includes enableable forcing lines the default bus test address and the RUN UUT address If any of your 9010A programs depend upon the pod unique features i e a forcing line needs to be disabled or a RUN UUT must be performed at the pod s default address then the appropriate Pod Data file needs to be included in the source file To do this an INCLUDE statement is used to specify the co
14. For example if the remote device provides its own Linefeed at the end of each line the terminator sequence would consist of only the Carriage Return 00000D Or if a double space is needed between lines the terminator sequence would be a Carriage Return and two Linefeeds 0 The eight hexadecimal digits have the following meaning First two digits These may have any hexadecimal value between0 and FF They must be followed by six digits as described below The two digits represent a count that corresponds to atiming delay between the transmission of lines For 9010A versions prior to 2C the timing delay is approximately 2 4 ms count providing a total timing delay range of 0 to 6 seconds The delay is 6 ms count for maximum delay of approximately 1 5 seconds with 9010A versions 2C and later Last six digits These are the ASCII terminator characters which are sent at the end of each line when the 9010A is sending data The characters are also sent once as the initial trigger when the AUX I F READ operation is selected The characters which have two digits each are sent left to right Zeros are not sent 6 49 NEWLINE Example NEWLINE OOODOAOA terminator sequence of a carriage return and 2 linefeeds NEWLINE terminator sequence of a carriage return and linefeed NEWLINE 1A00000D terminator sequence of a time delay and carriage return See Also LINESIZE STALL UNSTALL 6 50
15. POD Syntax Das ae C Function Identifies the pod to be used when executing the 9010A programs in the source file The POD statement allows the 9010A to use the data in the pod data file to configure its setup parameters to match the specified pod e At this time podname is one of the following more files will be added as new interface pods are implemented 1802 6809 40 50 8088 6502 6809E 8080 8088MX 6800 8041 8085 9900 68000 35 48 8086 280 6802 39 49 8086MX When using the 8048 pod the podname must be listed in this statement as 35 48 39 49 or 40 50 as appropriate Example POD 8080 POD 39 49 See Also Pod Data Files and 9010A Pod Interaction in Section 4 Part 1 6 51 6 52 RUN UUT Syntax hex number 9 Function Used when the address fora RUN UUT operation is allowed to default in a 9010A program e Setup parameter limits for RUN UUT are 0 FFFFFFFF IftheRUN UUT statement appears in the setup parameters section of the source file then the RUN UUT address will be as indicated If this statement was not present and a pod data file was included at the beginning of the source file the compiler supplies the definition for UUTADR Ifa pod data file was not included at the beginning of the source file the default RUN UUT address is 0000 Example RUN UUT C000 See Also Pod Data Files in Section 4 Part 1 RUN UUT in 9010A Program Statements part of this section a
16. add the following to the end of the first paragraph Data files may not be available for newer pods If a data file is not included for the pod you are using consult the Pod Instruction Manual for information about creating the proper data file You may add this new data file to the disk and INCLUDE it or you may insert the information directly into the beginning of the program On page 5 7 insert the following note between the last two paragraphs NOTE The total number of bytes required must not be more than the maximum memory size of the 9010A 10 192 bytes If the TOTAL xx bytes message printed by the Compiler program exceeds 10 192 then you must reduce the size of the source program s On page 5 8 replace the format line with device 9LC listoptions H hexfile 1 listfile srcfile lt RETURN gt On page 5 11 add the following paragraphs at the bottom of the page The CPM version of the software allows you to redirect the reporting of syntax errors to a file instead of to the display The Command Line for directing the syntax error report to a file is device 9LC listoptions hexfile L listfile srcfile gt msgfile lt RETURN gt The msgfile specified in the command line will receive all reports of syntax errors that may occur during compiling and also other status messages that would normally be printed on the display On page 6 9 replace the syntax diagram at the bottom of the page wit
17. eee ans We 6 111 WANK Ree bas Ce Sig E oa Sole 6 113 Write fia ci da ews oN Media 6 115 6 61 6 62 The syntax diagrams for the 9010A program statements are arranged alphabetically on the following pages The functional groupings of the statements are as follows FUNCTION TESTS TROUBLESHOOTING MODE TEST SEQUENCING UUT MEMORY MAPPING PROBE REGISTER OPERATION STATEMENT AUTO TEST BUS TEST IO TEST RAM TEST ROM TEST ATOG DTOG RAMP READ WALK WRITE REPT LOOP RUN UUT STOP AUX DPY EXECUTE GOTO IF LABEL LEARN PROBE SYNC REG UNARY CPL DEC INC SHL SHR ATOG Syntax dec rye eer Ce 3 REGF REG0 Function Toggles an operator specified address bit from one logic state to another Two read operations are performed one at the original address and another after the bit is toggled Ifthe bit number is explicitly specified in the expression it must have a decimal value in the range 0 n 1 where equals bits in the address bus Example ATOG 13FC BIT 7 See Also DTOG RAMP READ WALK WRITE 6 63 6 64 AUTO TEST Syntax Lem TEST Function Performs in sequence Bus Test ROM Test RAM Short Test and IO Test for versions prior to 2C For versions 2C and later the sequence is Bus Test RAM Short Test ROM Test and IO Test Errors are reported and locations are identified as described for the indi
18. Also GOTO LABEL 6 83 6 84 TEST 9 C REG A Function Tests the read write capability of all bits in I O registers described as having read write capability If an expression is used to specify the bit mask following BTS it must have a hexadecimal value in one of the following ranges 1 FF 8 bit microprocessor 1 FFFF 16 bit microprocessor 1 FFFFFF 24 bit microprocessor 1 FFFFFFFF 32 bit mocroprocessor e Bits that are equal to in the bit mask correspond to data lines that are to be tested for read write capability Bits that are equal to 0 in the bit mask correspond to data lines that are not to be tested for read write capability If no address block is specified then the 9010A performs the specified IO TEST over all blocks of memory described as I O under Address Space Information Example TEST 4010 401F BTS 3D See Also AUTO TEST BUS TEST RAM TEST ROM TEST LEARN ADDRESS DESCRIPTOR in Source File Syntax part of this section 6 85 6 86 LABEL Syntax La Function Allows the programmer to create labels i e program steps inserted into programs to provide points of entry for branching steps Identifies a specific location in a program Each label is identified by a single hexadecimal digit 0 9 and A F or with a symbolic name Within a single program symbolic label names cannot be mixed with hexadecimal label numbers 0 9 A F e 9010A
19. CONTENTS Beep se elas aie os sidan ovale We 6 39 Bus Test aie oak Riera a eae s aioe aie edn 6 41 Enable srai 6 43 Exercis Errors eta ee ee 6 45 Bo FLO SE A Ba eal 6 47 Newline 6 49 P d sacs 6 51 Ror UUT ee HY a A 6 53 soe ise wes 6 55 6 57 Trap eina 6 59 6 37 6 38 Syntax gt __BEEP ON ERR TRANSITION 1 T7 C Function Allows the programmer to control whether or not the 9010A should beep on ERR TRANSITIONS YES enables the audible beep that sounds whenever an error is detected and reported The beep also sounds whenever the error is removed The 9010A s default value is YES Example BEEP ON ERR TRANSITION NO See Also EXERCISE ERRORS TRAP 6 39 6 40 BUS TEST Syntax BUS hex number Function When the Bus Test is performed in a 9010A program testing of data lines occurs at the address listed Setup parameter limits for Bus Test are 0 FFFFFFFF Refer to the pod instruction manuals for legal addresses If the Bus Test statement appears in the Setup Parameters section of the source file then the default Bus Test address is as indicated If this statement was not present and a pod data file was
20. Entries 0 ccc cece ccc cece cee renee 4 18 File Inclusions Owed 4 19 continued on page iii CONTENTS continued Sample Program 4 20 Part 3 Symbolic Names 4 22 Introd ctiom i as uik be tae sie 4 22 Symbolic Program Names 4 24 Symbolic Labels ccc cece cece eee e 4 26 Symbolic Register 65 4 28 Predefined Register Names 4 29 sample Program oie earthen odd las 4 30 USING THE COMPILER 5 1 Introduction oi esse gore 5 3 Preparing the Source File cc 54 5 5 Interactive Mode cc cece cece cece 5 6 Command Line Mode 5 8 Listing File Options 5 10 Syntax Errors odiu bpon Peau 5 11 Transferring Programs 5 12 Transferring Programs to the 9010A 5 12 Transferring Programs from the 9010A 5 14 Source F rma t scssi Sis sie se edad aw eee Sree 5 14 EXP OTM atc 5 16 LANGUAGE REFERENCE 6 1
21. FF was used as a label number or GOTO AB was attempted Illegal option You have entered an illegal listing option fromthe interactive mode or have an illegal listing option in the command line Illegal program name A keyword was used as a program name a program name all hexadecimal characters was used or one of the predefined register names was used as a program name EXAMPLES Program test Program abcd Program bitmask F 3 Error Messages Illegal program number A program number out of the range 0 99 or a bad program number such as PROGRAM 44R was used Illegal program order Numbered programs are not in numerical order Too many symbolically named programs are between numbered programs Programs appear in the source file after program 99 Illegal register number A hexadecimal register number a single digit is out of the range 0 9 or A F 6 REG FF z 100FF Illegal signature More than four hexadecimal digits were used in a signature Illegal value A value is out of limits EXAMPLES LINESIZE 300 TIMEOUT 70000 You should check the appropriate page in Section 6 Language Reference to determine the legal range of values INCLUDEs nested too deeply INCLUDE statements are nested past the maximum depth of five Because this is a system dependency your system may not allow nesting to five Input line too long Lines longer than the maximum of 255 characters were used Invalid forcing l
22. Programs General Program Format In a few cases the 9010A Language does not correspond exactly to the keys that would be pressed if the program were being entered on the 9010A keyboard For example INC REGS is a legal statement accepted by the compiler However the keystrokes used to create this statement on the 9010A are INC 5 which would not be accepted by the compiler As another example REGA REGA INC is a legal statement accepted by the compiler but the keystrokes used to create this statement on the 9010A are REG A INC which would not be accepted In general the keywords of the 9010A Language are not identical to the wording that appears on the 9010A keyboard For example KEYBOARD 9010A LANGUAGE DISPL DPY COMPL CPL RPEAT REPT TOGGL DATA DTOG In all cases however the keywords accepted by the compiler are compatible with listings produced by the 9010A through the RS 232 C auxiliary interface Writing Programs General Program Format Program Comments The 9010A Language Compiler allows you to add comments to your programs making the programs more readable and easier to maintain The rules for using comments are Comments start with an exclamation point 1 and they extend to the end of the line A comment can be on the same line as a 9010A statement or it can be on a separate line If a comment extends over several lines each line must begin with an exclamation point A com
23. REG2 IF REG2 gt 0 GOTO 2 EXECUTE PROGRAM 2 REG8 A GOTO 3 DPY US2 TOGGLING IMPROPERLY GOTO 4 1 LABEL 1 DPY WAS PROBE IN PLACE 1 REG1 0 GOTO 0 DPY U52 OPEN GOTO 4 3 LABEL 3 DPY U52 TEST PASSED 4 LABEL 4 PROGRAM 1 SYNC FREE RUN 0 LABEL 0 REG1 50 REG2 20 1 LABEL 1 READ PROBE IF REGO AND 5000000 gt 0 GOTO 2 DEC REG1 IF REG1 gt 0 GOTO 1 REG8 1 GOTO 3 2 LABEL 2 DEC REG2 READ PROBE IF REGO AND 5000000 0 GOTO 0 IF REG2 gt 0 GOTO 2 REG8 0 3 LABEL 3 Stimulus loop Set flip flop D input high Toggle flip flop Set flip flop D input low Toggle again Loop for 10 tries Extract probe data Branch on probe count 10 Display bad toggle Exit Open node loop Query Branch if probe not ready Display U52 bad Exit Device passed End Program to detect probe placement Set counts Open count 50 Debounce count 20 Open loop Gather level information Branch on bounce level Decrement open count Loop if count gt 0 Set Open Node flag Exit Debounce loop Decrement debounce count Gather level information again Branch on open level Loop if count gt 0 Set Begin Test flag End Writing Programs General Program Format PROGRAM 2 Program to extract the probe data READ PROBE Gather probe information REG8 REGO AND 7F Extract count REG9 REGO SHR SHR SHR SHR SHR SHR SHR S
24. TEST and RUN UUT areas indicated If a pod data file is included and the pod name is specified or if a pod is connected to the 9010A when the hex file is downloaded then the specified pod s default BUS TIMEOUT 200 TEST and RUN UUT addresses will override these Default Setup Parameters POD SPECIFIC SETUP PARAMETERS ENABLEABLE DEFAULT BUS TEST RUN UUT ENE GALUE 0000 WAIT YES YES FFFFFFFE TSC YES DBE YES HALT YES 1000FFE F6000000 HALT YES BR ACK YES INTR YES 0000 FFFFFFFE MR YES HALT YES 0000 FFFFFFFE HALT YES DMA YES MR YES 0000 FFFFFFFE TSC YES HALT YES 2000 3000 UNUSED YES 1100 0000 UNUSED YES FFFF 0000 READY YES HOLD YES FFFF 0000 READY YES HOLD YES 0000 FFFFO READY YES HOLD YES INTR YES 8086MX 0000 FFFFO READY YES RQGTO YES RQGT1 YES INTR YES 0000 FFFFO READY YES HOLD YES INTR YES Default Setup Parameters 8088MX 0000 FFFFO READY YES INTR YES RQGTO YES RQGT1 YES 9900 0000 READY YES HOLD YES 280 FFFF 0000 BUSRQ YES WAIT YES D 3 D 4 Appendix E Parameter Limits SETUP PARAMETER LIMITS PARAMETER BUS TEST RUN UUT it STALL UNSTALL LINESIZE TIMEOUT NEWLINE 0 10 255 0 60000 8 Hexadecimal Digits ADDRESS DESCRIPTOR PARAMETER LIMITS PARAMETER signature ROM bit mask LIMIT 0 FFFF 1 FFFFFFFF E 1 E 2 Appendix Error Messages I
25. be either local toa single program or global to the entire source file depending on how they are declared Symbolic register names must be declared in an ASSIGN statement of the form ASSIGN REGn TO name ASSIGN statements are collected together intoa DECLARATIONS section EXAMPLE DECLARATIONS ASSIGN REG1 ERRCNT ASSIGN REG2 TO FREQ If the register names are to be used only within a particular program then the DECLARATIONS section should appear between the PROGRAM statement and the body of the program itself If the declarations are for global registers that are shared among several programs then the DECLARATIONS section must appear at the beginning of the source file before the firsts PROGRAM statement It is possible to assign several symbolic names to the same register within a program This can be done by specifying a list of names ina single ASSIGN statement or by using multiple ASSIGN statements It should be noted however that using multiple names for the same register implying multiple uses for a register can lead to programming errors It is the programmer s responsibility to ensure the integrity of the register contents Writing Programs Symbolic Names EXAMPLE PROGRAM UUTTEST DECLARATIONS ASSIGN ERRCNT REG1 will be used when ERRCNT is referred to ASSIGN REG2 TO PINCNT SETBIT Both PINCNT and SETBIT will be allocated to REG2 TEMP will also be allocated to REG2 ASSIGN REG
26. be mixed with hexadecimal label numbers A source file may contain a mixture of hexadecimal and symbolic labels but within a given program all labels must be either hexadecimal or symbolic Symbolic labels are local to the program in which they appear This means that it is possible to have duplicate label names in different programs without conflict Each program is limited to 16 label definitions even if the labels are referred to symbolically Within a given program the compiler assigns hexadecimal labels to symbolic label names sequentially starting at 0 The assignment is made upon the first appearance of the label whether it is a LABEL statement or the target of a GOTO statement Writing Programs Symbolic Names EXAMPLE PROGRAM FIND SEARCH Label 0 will be assigned to SEARCH READ REG1 INC REG1 IF REGE REG3 GOTO FOUND Label 1 will be assigned to FOUND REG1 gt REG2 GOTO NOTFOUND Label 2 will be assigned to NOTFOUND GOTO SEARCH NOTFOUND FOUND 4 27 Writing Programs Symbolic Names Symbolic Register Names 4 28 Another way to enhance program readability is to use symbolic names for registers The usage of the various 9010A registers can be made clear by choosing appropriate symbolic names Symbolic register names are a bit more complex than program or label names For example register names must be explicitly declared ina DECLARATIONS section Another difference is that register names can
27. included at the beginning of the source file the compiler supplies the definition for BUSADR e Ifa pod data file was not included at the beginning of the source file the default Bus Test address is 0000 Example BUS TEST 1C00 See Also Pod Data Files in Section 4 Part 1 BUS TEST in 9010A Program Statements part of this section and Appendix D Pod Specific Setup Parameters 6 41 6 42 Syntax ENABLE forcing line eer YES Function Allows an operator to individually enable or disable pod forcing lines Example If YES is selected the forcing line is enabled If NO is selected the forcing line is disabled Forcing lines are pod specific and include lines such as the following WAIT BR ACK READY RDY INTR BUSRQ TSC MR HOLD DBE DMA HALT UNUSED There are a maximum of eight enableable forcing lines Refer to the pod instruction manuals for specific information The appropriate pod data file must be included prior to the appearance of any ENABLE statements In addition a POD statement identifying the pod should appear in the Setup Parameters section of the source file If a pod data file was included at the beginning of the source file the forcing lines listed in the definition for FORCELNS will all have default values of YES ENABLE HALT NO See Also Pod Data Files in Section 4 Part 1 and Appendix D Pod Specific Setup Parameters POD 6 43 6 44 EXERCISE ERRORS
28. is specified the UUT begins executing the code at the address indicated If no address is specified but a RUN UUT setup parameter is present the address from the setup statement is supplied IfnoRUN UUT statement appeared in the setup section but a pod data file was included at the beginning of the source file then the value for UUTADR will be supplied Ifa pod data file was not included at the beginning of the source file the default address is 0000 Example RUN UUT RUN UUT 1000 See Also Default Setup Parameters Appendix D RUN UUT in Setup Parameters part of this section 6 105 6 106 Syntax Function Suspends program execution at desired points To cause the 9010A to resume program execution the operator must press the CONT key Example STOP 6 107 6 108 SYNC Syntax hexdigit ADDRESS Function Enables the operator to synchronize the probe operation to events in the microprocessor bus or allow the probe to oscillate at 1 kHz free run Example SYNC A SYNC FREE RUN See Also PROBE 6 109 6 110 UNARY Function Performs the specified unary operation on the contents of the indicated register Symbolic register names can be used in this statement Register identifiers must be previously declared in the local or global declaration section Unary operator shorthand may not be used in this statement 1 6 INC 3 REGS is a sy
29. letters Example Words in a rectangular enclosure represent other information that is described either in the General Information section in another syntax diagram as a note on the same page or that is in general use Example EOL An asterisk in a circular enclosure above bracketed words indicates a default register entry Only the asterisk should appear in the source file the compiler substitutes the information in the brackets Example REG F Language Reference SPECIAL SYMBOLS The following symbols are used in the syntax diagrams SYMBOL EOL FUNCTION Separates a list of symbolic names 1 6 register name declarations Indicates end of line Indicates range i e addr to addr used as a delimiter in AUX and DPY commands Relational operator Relational operator Relational operator At Separates the label name from the statement to be executed 6 5 Language Reference SYMBOLIC NAMES Symbolic names appear in the syntax diagrams as 6 6 The following rules apply to symbolic names Symbolic names must begin with a letter and they can contain any number of letters digits and underscore characters Only the first eight characters of a name are significant For example TESTMENUI and TESTMENU2 are treated as identical names 9010A Language keywords such as READ and PROGRAM cannot be used as symbolic names For example LOOP cannot be used as a symbolic label name althou
30. operators specify operationsthat may be performed on only one register at a time The five unary operators function as follows CPL Replaces the value stored in the register with its binary ones complement DEC _ Decrements the binary value of a register by 1 INC Increments the binary value of a register by 1 SHL Shifts the binary contents of the register one bit to the left The farthest left bit is discarded The farthest right bit becomes 0 SHR Shifts the binary contents of the register one bit to the right The farthest right bit is discarded The farthest left bit becomes 0 Binary operators perform an operation with two registers or with a register and a hexadecimal value or two hexadecimal values The two binary operators function as follows AND Performs the logical bit wise AND operation between two values OR Performs the logical bit wise OR operation between two values 6 8 term Language Reference Expressions In certain contexts expressions are interpreted as decimal binary or hexadecimal numbers These cases are indicated in the syntax diagram as follows dec bin hex Numeric constants in decimal expressions may contain only the digits 0 through 9 Similarly numeric constants in binary expressions may contain only the digits 0 and 1 and hexadecimal expressions may contain only the digits 0 9 A F A unary operator followed by a decimal number is the unary operator short
31. panel of the 9010A Suggested settings are 9600 baud switch setting 7 Parity Even Data bits 8 Stop bits Parity on The NEWLINE setup parameter should be set to 10000D0A for transferring files If transmission errors occur it may be necessary to change the timing delay to a largervalue See the 9010A Operator Manual for more information The 9010A setup parameters STALL and UNSTALL should be set to 13 and 11 respectively the 9010A defauli values when transferring files Set the parameters of the serial port on the host computer to correspond to those of the 9010A Refer to Installing Software in this section for further information on setting the RS 232 parameters 3 19 Getting Started CP M Operating Systems Installlng Software Editor 3 20 On CP M systems the File Transfer utility program XFER uses information from a data file for configuring RS 232 C transfers This file CONFIG PRT is automatically created for each system the first time that the File Transfer program is used The program will prompt for information about RS 232 C port parameters and use the information that you enter to create the data file on the system default disk Refer to the host computer s instruction manuals if you need further information to answer the prompts Once the CONFIG PRT data file is available on the disk it will automatically be used for subsequent file transfers with the XFER program This file contains
32. port status and data addresses an optional baud rate address and SIO initialization bytes To change the RS 232 C configuration in the CONFIG PRT file use the Configure option C in the File Transfer program The prompts will be repeated to allow you to redefine the configuration Note that the CONFIG PRT file will be created on the system default device The system disk must not be write protected at this time In order to create and maintain source files on the host system a general purpose text editor is required Any general purpose editor may be used with 9010A Language source files Section 4 Writing Programs CONTENTS ejna 4 3 Part 1 General Program Format 44 Introd ction bee 4 4 Important Details ce cece ee cee ee ee ences 4 5 Program Comments 4 7 90 Programs sec canis tae isd neti aesau lt 4 8 Address Space Information 4 8 Setup Information 4 9 Pod Data Files oie oe a 4 11 9010A Pod Interaction 0 cece eee eee eens 4 12 Sample Program os ek ie eek ia ie Sik ees 4 13 Part 2 Coding Shortcuts 4 16 ie dra ese ese ao Wo nag Wo Bae eens ws eee obra 4 16 Optional Keywords and Keyword Abbreviation
33. reason the compiler displays the program names and their corresponding program numbers as it processes the source file 5 13 Using the Compiler Transferring Programs Transferring Programs from the 9010A Programs that are transferred from the 9010A to the host system can be stored either in source format or in hex format If you have programs saved on 9010A cassettes and you want to modify them on the host system and take advantage of the features of the 9010A Language Compiler then the programs must be stored in source format Hex format is useful if you simply want to store the 9010A programs on the host system and load them back into the 9010A at a later time without any modifications Source Format To save programs from the 9010A on the host system in source format select the S option from the file transfer options menu by entering S RETURN NOTE The following examples assume that you have transferred the programs in DEMO H from the host system to the 90104 as previously described under Transferring Programs to the 90I0A XFER asks you for the name of the source file to be created on the host system Respond by entering the source file name in this case device DEMO1 S RETURN XFER then instructs you to prepare the 9010A for writing by pressing the AUX I F and WRITE keys on the 9010A When the transfer is complete the 9010A displays the message AUX SENDING COMPLETE A menu of source options will no
34. section 6 21 6 22 GLOBAL DECLARATION Syntax DECLARATIONS symbolic register name EOL declaration Function Allows the programmer to define symbolic register names with global scope Names with global scope are known throughout the entire source file and all files that are included after the global declarations Ifaregister name is redefined locally inside a 9010A program the local definition overrides the global definition and the program has no knowledge of the global declaration Global declarations must appear at the beginning of the source file before the first 9010A program is encountered Global symbolic register declarations are restricted to the global registers 8 F Example DECLARATIONS ASSIGN REG8 TO LOAD ASSIGN REG9 TO FLAG PROGRAM U10 See Also SOURCE FILE SYMBOLIC NAMES SYMBOLIC REGISTER NAME DECLARATION LOCAL DECLARATION 6 23 6 24 SYMBOLIC REGISTER NAME DECLARATION Syntax Case ect a Function Declares a symbolic name that the programmer uses in programs to refer to the indicated register e Symbolic register names must be declared in the global or local declarations section of the source file prior to being used in a program Symbolic register names can be used wherever a register reference can be made including AUX and DPY statements Several symbolic names can be assigned to the same register Example DECLARATIONS ASSIGN REG1 TO TE
35. sentence in Step 3 to read The Set Utility program SET a 1722A system program is included on the 1722A System Disk for this purpose On page 3 12 delete the second paragraph under Text Editor On page 3 15 add the NOTE at the end of Step 2 NOTE 2400 baud is the fastest data transfer rate allowable If transfer problems occur at 2400 baud try again at 1200 baud switch setting 4 Following step 3 replace both paragraphs with You may use the IBM MODE command to configure the serial port The command line for the IBM PC that is used to implement the suggested setting is MODE COM1 24 E 8 1 for 2400 baud and MODE COM1 12 E 8 1 for 1200 baud On page 3 17 between the two paragraphs under Introduction add the following NOTE NOTE The 9LC program will look for a file on the first Operational disk drive that it encounters and will hang up if that disk drive is empty If for example the 9LC disk is in drive 1 and drive 0 is empty the program will hang up looking for the file on drive 0 The disk activity indicator on drive 0 will be on and the display will show 9LC 12 84 1 9010A LC On page 3 20 Add the following to the end of the second paragraph The Kaypro version of the program will only prompt for the baud rate Replace the last sentence of the fourth paragraph with This file contains the status and data addresses The Kaypro version also includes SIO initialization bytes On page 4 11
36. to the Troubleshooter must implement this wiring scheme 1 Optional Use if your host computer requires RLSD Received Line Signal Detector to be asserted high 2 Optional Use if your host computer requires DSR Data Set Ready to be asserted high 3 Optional Use if your host computer requires RI Ring Indicator to be asserted high 12 84 6
37. 0 07FF SIG F77C 1 O 100F8 100FA BITS FF DECLARATIONS ASSIGN REG8 TO LOAD Global register declarations Used in display message ASSIGN REG8 TO FLAG ASSIGN REG8 TO COUNT PROGRAM US2TEST DECLARATIONS ASSIGN REG2 TO CNT WR 100FB 80 Flag an output from probe placement Count an output from unpacker Local declarations Beginning of program body START CNT A LOAD 1A09 EX PROMPT EX PRBPLACE IF FLAG 1 GOTO OPEN DPY TESTING 52 PROBE STIMULUS WR 100FA 1 DTOG 100F9 80 BIT 7 WR 100FA 0 DTOG 100F9 80 BIT 7 DEC CNT IF CNT gt 0 GOTO STIMULUS EX UNPACK IF COUNT A GOTO DONE DPY U52 TOGGLING IMPROPERLY GOTO OPEN DPY WAS PROBE IN PLACE 1 IF REG1 0 GOTO START DPY US2 OPEN GOTO DONE DPY U52 TEST PASSED EXIT INCLUDE PROBE1 S INCLUDE PROBE2 S INCLUDE PROMPT S Writing Programs Symbolic Names Symbolic program reference Symbolic label definition Symbolic label reference End of main program PROGRAM 1 must be renamed to PROGRAM PRBPLACE in file PROBE1 S PROGRAM 2 renamed to PROGRAM UNPACK in file PROBE2 S PROGRAM 3 renamed to PROGRAM PROMPT in file PROMPT S 4 31 4 32 Section 5 Using the Compiler CONTENTS TNUFOMUCHION 0 5 3 Preparing the Source File 5 4 Compiling 6 2 5 cheno neds Sene
38. 0 POD 6502 POD 8085 POD 6800 POD 8086 POD 68000 POD 8086MX POD 6802 POD 8088 POD 6809 POD 8088MX POD 6809E POD 9900 POD 8041 POD Z80 POD 8048 POD The setup information address space information and global declarations are all optional They may appear more than once and they may appear in any order providing that they appear before the first 9010A program 6 15 6 16 Syntax Function SETUP INFORMATION Nese ee m E parameters i B Allows the user to control the reporting of UUT errors enable microprocessor lines and specify operating parameters All setup parameters must be declared at the beginning of the source file preceding all programs Setup parameters establish initial setup conditions only Setup parameters are divided into the following categories l Reporting UUT errors or enabling microprocessor lines POD TRAP ENABLE EXERCISE ERRORS BEEP ON ERR TRANSITION Specifying operating parameters BUS TEST RUN UUT TIMEOUT Relating to operation of the AUX I F STALL UNSTALL NEWLINE LINESIZE Detailed information about setup parameters is contained in the next part of this section Setup Parameters 6 17 SETUP The compiler supplies default values as listed in Appendix D for any setup parameters that do not explicitly appear in the source file The compiler default values for setup parameters can be overridden by the pod specific values by including the appropriate
39. 05 nor can they be written to a cassette tape as they can with a 9010A Section 2 How to Use This Manual CONTENTS Intr d ction sssi iw eke Baws ed 2 3 Organization hee 2 4 Supgested Use 2 5 2 1 2 2 How to Use This Manual INTRODUCTION This manual is the reference source for the 9010A Language Compiler and the 9010A Language It is written with the assumption that the reader is already familiar with the operation of both the 9010A Micro System Troubleshooter and the host computer system If you are not familiar with the 9010A you should refer to the 9010A Operator Manual and the 9010 A Programming Manual and learn how to use the 9010A before proceeding in this manual Of course if you are not familiar with the host computer system you should read the instruction manuals provided with your system How to Use This Manual ORGANIZATION The 9010A Language Compiler User Manual is divided into the following sections l INTRODUCTION HOW TO USE THIS MANUAL GETTING STARTED WRITING PROGRAMS USING THE COMPILER LANGUAGE REFERENCE APPENDICES A F Introduces the 9010A Language Compiler and the 9010A Language and describes basic features Describes the sections of the manual and recommends how each section should be used Describes what you need to get started using the 9010A Language Compiler with your particular computer Gives an o
40. 20 3 2 BOTTI Getting Started INTRODUCTION This section provides the information needed to set up your host computer system to work with the 9010A Language Compiler For each version of the compiler the following information is presented What You Need Describes the hardware configuration required to use the compiler package Backing Up the Provides the information needed to create Program Diskette a working copy of the program diskette Hooking Up the Describes how to connect the 9010A to the System host system and how to set the RS 232 C serial interface parameters System Dependencies Presents other information that is unique to a particular host system You should carefully read the instructions that apply to your host system It is not necessary for you to read the material that relates to other host systems Getting Started FLUKE 1720A INSTRUMENT CONTROLLER Introduction The following information applies to the 1720A version of the 9010A Language Compiler What You Need The following equipment is needed in order to use the compiler package l Fluke 9005A or 9010A Micro System Troubleshooter with Option 9010A 001 RS 232 C Interface 2 Fluke 1720A Instrument Controller Option 1720A 001 128K Byte E Disk is recommended 3 Fluke Y1705 RS 232 C Null Modem Cable and Y1707 RS 232 C Interface Cable 4 9010A 920 9010A Language Compiler 1720A 1722A Version Backing Up the Program Diskette
41. 6 41 Enable gael Me ial Braise 6 43 Exercise Errors oe ee 6 45 6 47 NEWIHG ayers Suave ind otro 6 49 Pod sacs 6 51 Ron UUT eis sera eta 6 53 6 55 oat 6 57 Traps sanaaa tei ia eas 6 59 9010A PROGRAM STATEMENTS 6 61 Atop enea E E E 6 63 Auto Test 2 ccc eae dorado oe desde ieee Ae 6 65 AUK Wire 6 67 as 6 71 PR cadena loa 6 73 chee ek aha aed Bees 6 77 Execute sea 6 79 ace abe Sod es aces ase ates 6 81 E ste ays 6 83 TO Test hareran an a eee RC E RAO Cie BE TOR wD 6 85 Label socio swale E E ait cere basa aie d owas 6 87 tp nay Ne ee et 6 89 Probe Slat 6 91 ite otis 6 93 RAMP Site an aie Ja cas Sw WORSE E Dee ead 6 95 RAG bis dt 6 7 6 99 Rept Loop See E OS 6 101 eel dae 6 103 Run UU daa 6 105 Stop hide Owes ad 6 107 SYAC yaa erica ba ek oh bese
42. 6 TO MASK MASK will be allocated to REG6 ERRCNT 0 Actually sets REG1 0 SETBIT 4 Since PINCNT TEMP and SETBIT all share the same register this statement has the effect of also setting PINCNT and TEMP MASK SETBIT CPL AND FF WRITE REG3 MASK Predefined Register Names Symbolic names have been predefined for each of the dedicated registers These names can be used anywhere in a program that a register reference can be made It is not necessary to declare these symbolic register names The predefined register names and their functions are as follows DEDICATED SYMBOLIC REGISTER NAME FUNCTION A BITMASK Bit Mask B ROMSIG ROM Signature STSCTL STS CTL Information D BITNUM Bit Number E DAT Data F ADR Address 0 PBDAT Read Probe Data 4 29 Writing Programs Symbolic Names Sample Program The following example is similar to the one given at the end of Part 2 The example assumes that PROGRAM contained in the file PROBEI S has been renamed to PRBPLACE PROGRAM 2 in PROBE2 S has been renamed to PROGRAM UNPACK and PROGRAM 3 in PROMPTS S has been renamed to PROGRAM PROMPT This program tests the U52 flip flop on the output side of the 8255 PIA on the NEC TK 80A single board computer This version of the program demonstrates the use of symbolic names INCLUDE 8080 POD SETUP POD 8080 TRAP ACTIVE FORCE LINE NO TRAP ACTIVE INTERRUPT YES ADDRESS SPACE RAM 8C00 8FFF ROM 000
43. Example REG1 1FF TMP REGA SHR 4 See Also SYMBOLIC REGISTER NAME DECLARATION in General Information part of this section 6 99 6 100 LOOP Syntax test or troubleshooting statement Function REPT causes the action previously performed to be repeated once LOOP causes the action previously performed to be repeated continuously REPT and LOOP may not be specified as steps by themselves but may be specified as modifiers after a troubleshooting test or function has been specified e REPT and or LOOP can follow these test or troubleshooting statements AUTO TEST READ BUS TEST WRITE RAM TEST RAMP ROM TEST WALK 10 TEST ATOG DTOG Example RAMP REGF REPT REPT WALK 401C 1 LOOP 6 101 6 102 ROM TEST REE B Function Computes a ROM signature for each block of ROM and compares it to the reference ROM signature e If no address block is specified then the 9010A performs a ROM Test over all blocks of memory specified under Address Space Description and compares the signatures to those specified in the Address Space Information The signature expression must have a hexadecimal value in the range 0 FFFF Example ROM TEST ROM TEST 8000 9FFF SIG AFC7 See Also AUTO TEST BUS TEST IO TEST RAM TEST 6 103 6 104 RUN UUT Syntax a aT O Function Allows the interface pod microprocessor to execute the program code stored in the UUT e Ifan address
44. HR AND FFFF Extract Sig REGA REGO SHR SHR SHR SHR SHR SHR SHR SHR REGA REGA SHR SHR SHR SHR SHR SHR SHR SHR REGA REGA SHR SHR SHR SHR SHR SHR SHR SHR AND 7 Extract level PROGRAM 3 Program to prompt the operator REG2 REG8 AND 7F Register 2 pin number REG1 REG8 SHR SHR SHR SHR SHR SHR SHR AND 7F R1 Device num DPY PROBE U 1 PIN 2 Prompt for probe placement 4 15 Writing Programs PART 2 CODING SHORTCUTS Introduction The 9010A Language is designed to be compatible with the formatted listings produced by the AUX I F keys on the 9010A In this format you may find that some statements require much more typing than would be required to enter the same statement through the 9010A keyboard 4 16 To make it easier to enter large programs on the host system the 9010A Language Compiler provides several features which reduce the amount of typing required These features are Optional Keywords and Keyword Abbreviations Unary Operator Shorthand Default Entries File Inclusion Writing Programs Coding Shortcuts Optional Keywords and Keyword Abbreviations The 9010A Language provides the option of abbreviating certain keywords or leaving them out entirely Appendix C Optional Keywords and Keyword Abbreviations contains a complete list of the optional keywords and valid abbreviations Furthermore the syntax diagrams in Section 6 Language Reference indicate the abbreviated form of each statement in
45. Language keywords must not be chosen as symbolic label names such as LOOP There are 16 possible labels for each program All label names must be distinct Labels may appear in any order A label may exist without a branch GOTO step to the label lt A 9010 program statement can follow the colon Example Li DONE STOP FOUND LABEL FOUND See Also GOTO IF 6 87 6 88 LEARN Syntax addr block Function Tests each address location in sequence and identifies it as RAM ROM I O or unassigned Also creates an address descriptor foreach block of memory which was identified If no addr block is specified the Learn operation is performed on the entire microprocessor address space Refer to the pod instruction manuals for specific address information Example LEARN LEARN 1000 4FFF See Also IO TEST RAM TEST ROM TEST ADDRESS DESCRIPTOR in Source File Syntax part of this section 6 89 6 90 PROBE Syntax Function The Read Probe function places accumulated probe data into Register 0 Probe data consists of the logic levels detected the number of events counted and the signature computed at the probe tip In Register 0 event counts are assigned to bits 0 6 signatures are assigned to bits 8 23 and logic levels are assigned to bits 24 26 Example READ PROBE RD PROBE PROBE See Also SYNC 6 91 6 92 RAM TEST Syntax Function RAM SHORT quickly identifies
46. MP FLAG ASSIGN REGA TO PINNO See Also GLOBAL DECLARATION LOCAL DECLARATION SYMBOLIC NAMES Predefined Register Names in Section 4 Part 3 6 25 6 26 9010A PROGRAM Syntax decimal decimal YTES Function This syntax diagram defines the overall structure fora 9010A program Program numbers must be decimal numbers in the range 0 99 e Ifa byte count appears in the program statement the compiler compares it to the actual byte count and issues a warning messageif the byte counts differ Symbolic program names can be used in this statement The source file can contain no more than one hundred 9010A programs Numbered programs must appear in the correct order If programs with symbolic names are combined with numbered programs there must be a correct number of symbolically named programs between numbered programs For example if there are two numbered programs program 4 and program 7 thenthereis room for only two symbolically named programs between them Example PROGRAM 35 728 BYTES PROGRAM GETSIG PROGRAM KEYBD TST See Also EXECUTE Symbolic Program Names Section 4 Part 3 6 27 6 28 PROGRAM BODY Syntax ig local i declaration 9010 E u binary program Function This syntax diagram defines the body of a 9010A program The details of the 9010A statements are provided in the 9010A Program Statements portion of this section See Also LOCAL DECLARATION 9010A PR
47. N HOLD 1 HOLD is bit 1 in the enable mask FORCELN INTR 3 INTR is bit 3 in the enable mask BUSADR 0000 BUSADR is the default BUS TEST address UUT ADR FFFFO UUT ADR is the default RUN UUT address Other definitions can follow Writing Programs General Program Format 9010A Pod Interaction Setup information takes effect immediately upon loading a new hex file into the 9010A whether through READ TAPE or AUX 1 F READ An interaction takes place between the 9010A and the interface pod when the hex file is loaded and setup information may be changed to the default setting of the pod if 1 The pod name was not specified with a POD statement in the setup section or 2 A different pod is connected to the 9010A while the hex file is being loaded into the 9010A To avoid changing the parameters in pod dependent programs 1 An INCLUDE statement must be used in the setup section of the source program to include information from the appropriate Pod Data file 2 A POD statement must be used in the setup section of the source program to identify which pod is being used 3 The correct pod or no pod must be connected to the 9010A when downloading a compiled hex file 4 12 Sample Program Writing Programs General Program Format The following sample source file illustrates the concepts introduced in Part 1 Thisexample can be used as a basis for writingyourown9010A programs Before conti
48. NT listing file with S option EXECUTE 7 INC REG2 Using the Compiler Compiling D Replace Default Entries If the source file contains any default entries indicated by the listing file normally copies the statement as it appears in the source file with the in place However if the D option is specified then the listing file substitutes the appropriate default register for the EXAMPLE line from source file WRITE normal listing file WRITE listing file with D option WRITE REGF REGE A Expand Keyword Abbreviations If the source file contains the abbreviations RD WR or EX they are normally copied to the listing file in their abbreviated form just as they appear in the source file However if the A option is specified then the listing file replaces all occurrences of these abbreviated keywords with the full keyword EXAMPLE line from source file EX PROGRAM 5 normal listing file EX PROGRAM 5 listing file with A option EXECUTE PROGRAM 5 Syntax Errors All programmers eventually have an elusive syntax error to track down The compiler provides some help by pinpointing the location of the syntax error in the listing file especially if the listing option has been selected to expand any include files Even after you have found the location of the syntax error the exact cause of the problem may not be obvious Appendix F Error Messages contains a list of common syntax errors tha
49. NTRODUCTION This appendix describes error messages that may be produced by the 9010A Language Compiler programs The appendix is divided into three parts Compiler Program Error Messages 9LC File Transfer Error Messages XFER and Disk Verification Program Error Messages VERIFY Along with each error message is a description of possible causes for the error The description is not meant to be a comprehensive list other causes may also be possible Other messages may be produced by the host computer system For explanations of system dependent errors refer to System Dependencies in Section 3 and to the user manual for the host system F 1 Error Messages COMPILER PROGRAM ERROR MESSAGES Address range error In an address range the second address was incorrectly specified smaller than the first address EXAMPLE RAM 10000 1OFF Attempt to redefine symbolic name A symbolic name was used in the wrong context i e the name was already used as a program name but now you are attempting to use it as a global register name you are using a local register name as the target of a GOTO or you are using a label name as a program name in an EXECUTE statement Binary number expected Can occur if you try to write a non binary value to CTL or try to DTOG a non binary value for DTOG CTL Cannot define REGO 7 as global registers You tried to assign a symbolic name to a local register REGO 7 ina globally declared ASSIGN state
50. OGRAM STATEMENTS BINARY PROGRAM 6 29 6 30 LOCAL DECLARATION Syntax DECLARATIONS symbolic register name EOL Allows the programmer to define symbolic register names with local scope Function Names with local scope are known only within the program in which they are declared e Duplicate local names in different programs are unrelated Local declarations must appear between the program statement and the first statement of the 9010A program body No local declarations may appear inside a binary program Symbolic names may be declared locally for all registers 0 F Example PROGRAM UUTTEST DECLARATIONS ASSIGN REG1 ERRCNT ASSIGN REG2 TO PINCNT SETBIT ERRCNT 0 SETBIT 4 See Also SOURCE FILE SYMBOLIC REGISTER NAME DECLARA TION GLOBAL DECLARATION 6 31 6 32 BINARY PROGRAM Syntax line of code Function The 9000A Utility Program tape contains binary programs Binary programs are introduced by the standard program statement PROGRAM xx followed on a separate line by BINARY followed by the binary program e A binary program contains lines of hex code Each line is terminated by a one byte checksum is used to delimit a line of code from the checksum except for the last line of the program where a is used The file transfer program XFER automatically reformats binary programs into the required format when they are transferred from th
51. Set RS 232 C Utility User Manual for a complete description of how to use the SET utility Getting Started 1720A Instrument Controller NOTE The STALL option must be enabled on the 17204 if any files are to be transferred from the 9010A to the 1720A This option is not required if files are only transferred from the 1720A to the 9010A Some early versions of the 1720A Set RS 232 C Utility program do not implement the STALL option Be sure to use the Set RS 232 C Utility program that is contained in the 9010A Language Compiler package The End of Line character should be set to 10 and the End of File character should be set to 26 the 1720A default values The following example demonstrates how the SET utility can be used to select the parameters that correspond to the above 9010A settings SET KBI BR 9600 DB 8 PB E SB 1 SI E SO E EX Since the 1720A serial port parameters must be reestablished every time the 1720A is turned on you will probably want to incorporate the necessary commands into a system command file The 1720A Floppy Disk Operating System User Manual contains information on how this is done 3 7 Getting Started 1720A Instrument Controller System Dependencles Text Editor In order to create and maintain source files on the host system a general purpose text editor is required The Editor Accessory program filename ESX is the recommended editor for use with the 1720A A copy of the Editor Acces
52. Systems 3 17 Introduction eee ee 3 17 What You Need cece cece cee cee cece eee 3 17 Backing Up the Program Diskette 3 18 Verifying the Working Diskette 3 18 Hooking 3 19 Installing Software 3 20 Nar 3 20 4 WRITING PROGRAMS 4 Introduction 4 3 Part 1 General Program Format 44 Introduction sissies en Cae en Gana Fae ne eis 44 Important Details 4 5 Program Comments 4 7 9010 Programs 4 8 Address Space Information 4 8 Setup Information 0 cece cece cece eee ence 4 9 Pod Data Files cece cece ce eee eee tence nee 4 11 90 10 Pod 4 12 Sample Program 4 13 Part 2 Coding Shortcuts cece cece cece cee eenes 4 16 erry ae E wlan chee 4 16 Optional Keywords and Keyword Abbreviations 4 17 Unary Operator Shorthand 4 18 Default
53. TRAP BAD POWER SUPPLY YES TRAP ILLEGAL ADDRESS YES TRAP ACTIVE INTERRUPT NO TRAP ACTIVE FORCE LINE YES TRAP CONTROL ERROR YES TRAP ADDRESS ERROR YES TRAP DATA ERROR YES Example TRAP BAD POWER SUPPLY NO TRAP ACTIVE INTERRUPT NO See Also EXERCISE ERRORS BEEP 6 59 6 60 9010A PROGRAM STATEMENTS CONTENTS PLO Boos ase cosas ese Dae 6 63 Tecate Wer 6 65 ae eae ee aco 6 67 5 5 6 71 DPY arate whack 6 73 ase Seda hE AP Rs BO es ele ce Se 6 77 EX CUte edie cas wey eas 6 79 UT OCO race td Wade Ge T ET 6 81 tote a ea oe 6 3 KITES 6 85 Datel esses E oye descend P 6 87 Bre 6 89 Probe Sie 6 91 RAM Rest secede E E ced ies cia eh tte eee Sea AS 6 93 RAMP aie BON sels Ate 6 95 Read fice Seer Sed avis 6 97 ROG 6 99 Rept Lop arden eee loos ese 6 101 ROM Testu eoe iecre penat u r artes aks E a Bena ees 6 103 R n eis etn Me ee eee 6 105 em aan 6 107 Madea 6 109 URAL Y oie a
54. The test programmer develops the test programs on the host computer system in an ASCII source program form using the full power of the editing and file storage capabilities of the host system In this sense a 9010A program on the host system is much like a program written in any other programming language such as BASIC FORTRAN or Pascal Once the program has been written in source form the 9010A Language Compiler program converts the source program into the hex format required for transfer to the 9010A The program is then transferred to the 9010A using a transfer program that is supplied with the compiler package and the hex format program is read into Troubleshooter memory by pressing the AUX I F and READ keys on the 9010A 1 5 Introduction LANGUAGE EXTENSIONS The 9010A Language Compiler accepts any program that can be entered through the 9010A keyboard In fact the syntax of the 9010A Language is compatible with program listings obtained from the 9010A using the AUX I F SETUP AUX I F LEARN and AUX I F PROGM commands described in the 9010A Operator Manual In addition to the standard 9010A commands however the 9010A Language Compiler provides some powerful extensions These additional features are designed to make it much easier to develop and maintain large 9010A programs Some of the key features are Program Comments Allows the test programmer to incorporate documentation into the program itself Keyword Abbrevi
55. US TEST to begin at 00000 and the RUN UUT to begin at FFFFO Save this new file as file lt filename gt POD on the disk If you would like to add your new Pod data file to the list of files that are checked by the VERIFY program do the following steps 1 3 4 5 12 84 Edit file VERIFY DAT supplied on the 9LC disk and add the following line to the end of the file lt filename gt POD DDDD lt filename gt POD is the name of the new Pod data file and DDDD is a dummy checksum for the file You ll replace the dummy checksum with a real one later Save the modified VERIFY DAT file on the disk Run the VERIFY program The last two messages that it reports should be File lt filename gt POD error signature is CCCC should be DDDD zz files tested 1 bad signatures 0 missing files lt filename gt POD is the name of the new Pod data file CCCC is the correct checksum for the Pod data file and zz is the number of files tested Write down the correct checksum for the Pod data file CCCC Re edit the file VERIFY DAT and replace the dummy checksum that you entered before DDDD with the correct checksum CCCC Run the VERIFY program again to confim that all changes have been made satisfactorily The last two messages that it reports should now be File lt filename gt POD verified 9010A LC zz files tested no errors RS 232 INTERFACE CABLE The cabl used to connect the host computer
56. Y LOSS OF DATA USE PROFITS OR GOODWILL OR FOR DIRECT INDIRECT SPECIAL INCIDENTAL CONSEQUENTIAL OR OTHER SIMILAR DAMAGES AS A RESULT OF ANY MATTER RELATED TO THIS AGREEMENT REGARDLESS OF THE FORM OF THE ACTION Copyright 1983 John Fluke Mfg Co Inc P O Box C9090 Everett Washington 98206 Contents INTRODUCTION 1 1 Introduction to the 9010A Language Compiler 1 3 The Host Computer 14 How the Compiler Works 1 5 Language 6 1 6 The 9010A Language Compiler Package 1 7 Disk 1 7 Compile aie dua eee 1 7 File Transfer Program 1 7 Pod Data Fil s sr cou tae e Veale aa CUA ORG 1 8 Use With thie 9005 As AN aa baad 1 8 HOW TO USE THIS MANUAL we 2 1 Introductio Weed aan en 2 3 PS Oe ee 2 4 S ggested 2 5 GETTING STARTED 3 1 Introd ction Seve tea ete 3 3 Fluke 1720 Instrument Controller 3 4 Introduction aa Roa 6 He ne 3 4 What You Need
57. a letter and they can contain any number of letters digits and underscore characters _ Only the first eight characters of a name are significant For example TESTMENUI 1 AND TESTMENU2 are treated as identical names 9010A Language keywords such as LOOP READ and PROGRAM cannot be used as symbolic names For example although LOOP cannot be used as a symbolic label name LOOP 1 is acceptable Appendix A contains a complete list of the 9010A Language keywords Using a keyword as a symbolic name causes the compiler to issue a SYNTAX ERROR message Symbolic names must contain at least one letter other than A B C D E or F so that they can be distinguished from hexadecimal constants This means that words like BAD ACE or FADE cannot be used as symbolic names because the compiler will interpret them as hex constants Using a hex constant as a symbolic name causes the compiler to issue a SYNTAX ERROR message 4 22 Writing Programs Symbolic Names Symbolic names can be used anywhere that the corresponding actual program number register number or label number can occur in a 9010A program Forward references are permissable for program names and label names In other words an EXECUTE or GOTO statement using a symbolic name is allowed to appear either before or after corresponding PROGRAM or LABEL statements Register names may appear in DPY and AUX statements Symbolic names are case insensitive For example
58. a name can be declared in uppercase and referenced in lowercase and names can be a mixture of uppercase and lowercase letters 4 23 Writing Programs Symbolic Names Symbolic Program Names 4 24 9010A Language allows programs to be referred to by name as well as by number By choosing descriptive program names you can make your programs much more readable and maintainable Symbolic program names do not need to be declared explicitly Simply using a name in a PROGRAM statement or in an EXECUTE statement is sufficient to define that symbolic program name The compiler assigns sequential program numbers to symbolically named programs starting with PROGRAM 0 for the first program in the source file Each time a symbolic PROGRAM statement is encountered the next sequential program number is assigned to it A source file can contain any combination of programs with actual program numbers and programs with symbolic names NOTE EXECUTE statements can appear either before or after the PROGRAM statement They do not have any effect on the sequence of program numbers assigned to symbolic program names Whenever the compiler encounters a program in the source file with an actual program number rather than a symbolic name then subsequent symbolic program names are assigned program numbers that follow sequentially from the given program number EXAMPLE PROGRAM 5 Compiled as PROGRAM 5 PROGRAM PA Compiled as PROGRAM 6 PROGRAM
59. al source file name If the source file is not contained on a system default device the filename may also require a device name For example MF1 DEMO S might specify a source file named DEMO S onan optional floppy disk Consult your host computer user s manuals for information about complete filename specifications The program diskette contains a sample source file named DEMO S This file is used as an example inthe following procedures for using the compiler If you already have 9010A programs stored on 9010A cassette tapes it is possible to transfer them to your host system and use them with the compiler The procedure for doing this is described later in this section under the heading Transferring Programs from the 9010A Using the Compiler COMPILING Once you have created a source file you are ready to run the compiler The compiler reads the source file and creates an equivalent hex file which can then be transferred to the 9010A through the RS 232 C serial interface You have the option of running the compiler in either of two modes the interactive mode or the command line mode NOTE The following examples require the file DEMO S to be ona non write protected disk If your working copy of the system disk as described in Section 3 is write protected you will need to use two disk drives with a copy of the demo program DEMO S on a non write protected disk in the second drive Using the Compiler Compil
60. ameters D 1 E Parameter Limits cece cece cee eee F Error Messages goa ee Oe F 1 Identifies Setup Keywords active address and assign atog auto aux bad beep binary bit bits bts bus bytes control cpl ctl data dec declarations dpy dtog enable err error errors ex exercise execute force free goto if illegal inc include information interrupt IO label learn line linesize long loop Appendix A Keywords newline no on or pod power probe program ram ramp rd read reg rept rom run setup shl short shr sig space stall stop sts supply sync test timeout to transition trap unstall uut walk wr write yes A 1 A 2 REGISTER Appendix B Predefined Register Names SYMBOLIC NAME BITMASK ROMSIG STSCTL BITNUM DAT ADR PBDAT FUNCTION Bit Mask ROM Signature STS CTL Information Bit Number Data Address Read Probe Data B 1 B 2 Appendix C Optional Keywords and Keyword Abbreviations OPTIONAL KEYWORDS AND SYMBOLS ELEMENT LABEL x PROGRAM INFORMATION READ xx BYTES RESTRICTIONS None always optional None always optional Optional only in DPY AUX and SETUP parameters None al
61. ations Op tional Command Keywords and Shorthand Notation for Unary Operators File Inclusion Symbolic Names for Programs Labels and Registers Minimizes the typing required to enter a test program on the host system Permits common programs to be conveniently shared by many source files reducing the time required to develop test programs for new applications Allow programs to be written more clearly making them easier to understand and maintain Introduction THE 9010A LANGUAGE COMPILER PACKAGE The 9010A Language Compiler package consists of this manual and a diskette that contains several programs and data files The key software elements of the package are as follows Disk Verification Program The Disk Verification Program is a utility program that verifies the integrity of compiler package files This program is used to assure that there are no files missing that the files are not corrupted and that they are compatible versions Compller The compiler is a program that accepts the source file representation of 9010A programs including setup parameters and address descriptors and produces a corresponding hex format file that can be read into the 9010A The compiler checks for coding errors in the source file and displays an error message whenever an error is detected If the source file contains errors then a hex file is not created In addition to the hex format output file the compiler can pr
62. common RAM failures such as address decoding errors or bits that are not read writable RAM LONG performs the same tests as RAM SHORT and in addition performs a pattern sensitivity test for locating soft RAM errors If no address block is specified then the 9010A performs RAM test over all blocks of memory specified as RAM under the Address Space Information Example RAM SHORT 1000 3FFF RAM LONG See Also AUTO TEST BUS TEST IO TEST ROM TEST LEARN ADDRESS DESCRIPTOR in Source File Syntax part of this section 6 93 6 94 RAMP Syntax Function Performs a series of write operations at a programmer specified location in the UUT microprocessor system beginning with all data bits equal to zero and increasing by one until all data bits equal one Example RAMP 34 0 See Also ATOG DTOG READ WALK WRITE 6 95 6 96 READ Function Reads a programmer specified location in the UUT microprocessor system and places the data in register E READ STS reads the values of the UUT microprocessor status lines and places the corresponding value in register C Example READ REG1 g RD STS See Also PROBE READ WRITE ATOG DTOG RAMP WALK 6 97 6 98 REG Syntax Eo 39 Function Enters the specified data in the specified register Symbolic register names can be used in this statement Symbolic register names must be declared before use in the local or global declarations section
63. correct version numbers are reported If such problems occur recopy the diskette and run the VERIFY program again If problems persist and you are unable to run any of the programs contact a Fluke Technical Service Center 3 5 Getting Started 1720A Instrument Controller Hooking Up the System The 1720A must be connected to the 9010A whenever you want to transfer the hex files produced by the compiler to the 9010A for execution 3 6 l Use an RS 232 C interface cable and an RS 232 C null modem cable to connect the auxiliary interface of the 9010A to one of the serial ports on the 1720A KBI or KB2 can be chosen as the serial port on the 1720A XFER the file transfer program described in Section 5 Compiler Usage allows you to specify the port name to be used when transferring files to the 9010A Since XFER defaults to KB1 itis more convenient to connect the 9010A to KBI if KBI is not already being used for some other purpose Set the RS 232 C auxiliary interface parameters on the rear panel of the 9010A Suggested settings are 9600 baud switch setting 7 Parity even Data bits 8 Stop bits Parity on 9010A Setup parameter NEWLINE must be set to the 9010A default value for transferring files Set the parameters of the serial port on the 1720A to correspond to those of the 9010A SET a 1720A system program is included on the program diskette for this purpose Refer to the 1720A
64. ction 6 Section 5 Using the Compiler provides information onhowto use the compiler and the file transfer program This will enable you to create hex files and transfer them to the 9010A for execution Section 6 Language Reference contains much of the same information as Section 4 but the information is more detailed and it is organized to enable quick reference This section is designed for use when you are in the middle of a program and need specific syntax information in a hurry Appendices A through F provide detailed information about the 9010A Language You will probably use the appendices for quick reference after you have learned how to use the language 2 5 2 6 Section 3 Getting Started CONTENTS Introduction s 55 6 a eR OGM G a Ged a os 3 3 Fluke 1720A Instrument 3 4 Introduction 3 4 ae What You Need ba oieavekieee dieses wee ik 34 Backing Up the Program Diskette 3 4 Verifying the Working Diskette 3 5 Hooking 3 6 System Dependencies 3 8 Test Editor ond wind at pang bbs uh wera 3 8 Disk Space scree ccc tg tence sedi coens e eaa a bende 3 8 3 8 Fluke 1722A Instrument Controller 3 9 Introd UCtlON
65. ctions on how to copy diskettes can be found in the IBM Disk Operating System DOS User Manual Verifying the Working Diskette 3 14 Once you have created a working copy of the program diskette you should verify the integrity of its files by running VERIFY the programs included in the compiler package To run the VERIFY program put the working diskette in drive a and then type a VERIFY RETURN in response to the IBM system prompt The VERIFY program checks the contents of the copy to verify the integrity of the compiler package files It calculates a checksum for each of the files and compares it to the checksum contained in the VERIFY DAT file VERIFY DAT is an ASCII file that contains a list of filenames and checksums for each of the files in the compiler package Results from the VERIFY program are printed in tabular form as each file is checked Missing files or checksum errors that could indicate either corrupted files or incorrect version numbers are reported If such problems occur recopy the diskette and run the VERIFY program again If problems persist and you are unable to run any of the programs contact a Fluke Technical Service Center Getting Started IBM Personal Computer Hooking Up the System The IBM PC must be connected to the 9010A whenever you want to transfer the hex files produced by the compiler to the 9010A for execution l Use an RS 232 interface cable and an RS 232 null mo
66. dem cable to connect the auxiliary interface of the 9010A to a serial port on the IBM PC Set the RS 232 auxiliary interface parameters on the rear panel of the 9010A Suggested settings are 2400 baud switch setting 5 Parity On Data bits 8 Stop bits 1 Parity Even Set the parameters of the serial port on the IBM PC to correspond to those of the 9010A You may use the IBM MODE command to configure the serial port Refer to the IBM instruction manuals for help The NEWLINE setup parameter should be set to 10000D0A for transferring files If transmission errors occur it may be necessary to change the timing delay to a larger value See the 9010A Operator Manual for more information The 9010A setup parameters STALL and UNSTALL should be set to 13 and 11 respectively the 9010A default values when transferring files Getting Started IBM Personal Computer System Editor In order to create and maintain source files on the host system a general purpose text editor is required Any general purpose editor may be used with 9010A language source files RETURN Key References to the RETURN key in this manual refers to the key on the IBM Personal Computers Getting Started CP M OPERATING SYSTEMS Introduction The following information applies to the version of the 9010A Language Compiler for CP M systems CP M Control Program for Microcomputers is a product of Digital Research Inc It is a general purpose
67. e enter Y RETURN Using the Compiler Compiling If you request a listing file the compiler prompts you for the listing file name You should enter the required name or simply press RETURN to get the same nameas the source file with a L extension in this case DEMO L L also on the same device as DEMO S RETURN After you have specified the listing file name the compiler displays the listing file options These options are described later in this section If you simply press RETURN the compiler produces a copy of the source file with line numbers added RETURN At this point you have specified the compiler options The compiler displays the equivalent command line the significance of which is explained below and then proceeds to compile the source file While it is processing the source file the compiler displays the name of each program its program number and the number of bytes of 9010A program memory required After the compiler has processed the source files it displays the total number of bytes required and then returns to the host operating system If the compiler detects any errors in the source file it displays an appropriate error message along with the source line containing the error The error message also appears in the listing file if a listing file has been requested If the source file contains any errors then a hex file will not be created 5 7 Using the Compiler Compiling Command Li
68. e 9010A to the host system in source form Example PROGRAM 10 BINARY 514F50DDE5D0D2A2BO00DD562FDD5E 2E7 BE60F 87 87 4F0600FD2A2B00F D097 BE6F0 28 CB3FCB3F4FDD097 A E60F 87874F2A2B0009DD7 E02FD86025F DD7 E03FD8E0357DD D4 7EOOFD8E00770DD7E 01F D8E 01237 72373 2372DDE101000 0C 9284329464C554B65 CO 205645522031 SN 5E See Also 9010A PROGRAM 6 33 6 34 Syntax INCLUDE DIRECTIVE Cincuae eC gt _ filename of 01 Function Replaces the INCLUDE filename statement with the contents ofthe indicated file Equivalent to manually typing the contents of the included file in the source file at that point Example The filename must be the name of an existing file If the host computer system is case sensitive regarding filenames then the filename must be properly capitalized A source file may include a file which in turn includes another file Attempting to nest include files too deeply will result in a 9010A error message Include directives must be on a line by themselves but can occur anywhere in the source file Include directives may even appear asa statement in a 9010A program The programmer is responsible for ensuring that the contents of the indicated file can legally be inserted at that point in the source file A standard use of the INCLUDE statement is to include a pod data file include 1802 POD See Also Pod Data Files in Section 4 Part 1 6 35 6 36 SETUP PARAMETERS
69. e Transfer Program XFER 1 7 Files Inclusion 4 19 Pod Data 1 8 4 11 Source 5 4 5 14 INDEX Format General Program 4 4 Hex 5 16 Source 5 14 Fluke 1720A Instrument Controller 3 4 Fluke 1722A Instrument Controller 3 9 General Program Format 4 4 Getting Started 3 1 Hex Format 5 6 Host Computer Systems CP M Operating Systems 3 17 Fluke 1720A Instrument Controller 3 4 Fluke 1722A Instrument Controller 3 9 IBM Personal Computer 3 13 Kaypro II Personal Computer 3 17 IBM Personal Computer 3 13 Inclusion File 4 19 Information Address Space 4 8 Setup 4 9 Interaction Pod 9010A 4 12 Interactive Mode 5 6 Kaypro II Personal Computer 3 17 Keyword Abbreviations 4 17 Appendix C Index Keywords Appendix A Keywords Optional 4 17 Appendix C Labels Symbolic 4 26 Language Extensions 1 6 Listing File Options 5 10 Modes Command Line 5 8 Interactive 5 6 Names Predefined Register 4 29 Appendix B Symbolic 4 22 Symbolic Program 4 24 Symbolic Register 4 28 Operator Shorthand Unary 4 18 Optional Keywords 4 17 Options Listing File 5 11 Parameter Limits Appendix E Pod Data Files 1 8 4 11 Predefined Register Names 4 29 Appendix B Preparing Source Files 5 4 Program Comments 4 7 General Format 4 4 Names Symbolic 4 24 Transferring 5 12 Writing Section 4 Programs Compiler 1 7 Disk Verification 1 7 File Transfer 1 7 4 8 Reference La
70. ecution and waits for input When the operator enters a hexadecimal value terminated by ENTER the 9010A places the value in the designated register and resumes program execution Pressing ENTER without specifying a hexadecimal value causes the value to default to the previous contents of the register The same as for the symbol except that the 9010A accepts only a decimal entry DPY When is followed by a hexadecimal digit or symbolic register name it suspends program execution and displays the question mark 7 If the operator presses the CLEAR NO key the 9010A places a 0 in the designated register If the operator presses the ENTER YES key the 9010A places a in the designated register After the 1 or 0 is placed in the register the 9010A removes the question mark and then resumes program execution When is followed by a hexadecimal digit or symbolic register name it enables or disables asynchronous input from the operator during execution Asynchronous input is stored in the register designated by the hexadecimal digit or symbolic register name When is the first character in the specitication it causes following characters in the specification to be appended to the text that is on the displayat the time DPY is executed NOTE In order to cause one of the special symbols or to be displayed in the case where the symbol is followed by a hexadecimal digit or symbolic register name the symbol mus
71. equired if files are only transferred from the 1722A to the 9010A The End of Line character should be set to 10 and the End of File character should be set to 26 the 1722A default values The following example demonstrates how the SET utility can be used to select the parameters that correspond to the above 9010A settings SET KBI BR 9600 DB 8 PB E SB 1 SI E SO E EX Since the 1722A serial port parameters must be reestablished every time the 1722A is turned on you will probably want to incorporate the necessary commands into a system command file The 1722A System Manual contains information on how this is done Getting Started 1722A Instrument Controller System Dependencies Text Editor In order to create and maintain source files on the host system a general purpose text editor is required The Editor Accessory program filename EDIT is the recommended editor for use with the 1722A A copy of the Editor Accessory program is included on the program diskette and instructions for using the editor are included as an Addendum to this manual Disk Space 3 12 After using the Editor or Compiler programs it may be advantageous to pack the disk contents using the P option in the 1722A File Utility program to provide as much free disk space as possible Refer to the 1722A System Manual if you need help with packing the disk The message Read write past physical end of file means that there was not enough conti
72. f ROMSIG AUX tests complete See Also DPY Functions of AUX I F Characters CHARACTER ACTION CAUSED Sends a control G bell to the RS 232 interface When followed by a hexadecimal digit or symbolic register name causes the contents of the designated register to be transmitted in hexadecimal to the RS 232 interface The same as for the symbol except that the contents are transmitted in decimal When is followed by a hexadecimal digit or symbolic register name it suspends program execution waits for the next byte of data from the RS 232 interface and places the value of the byte in the designated register The upper three bytes of the register equal zero If the RS 232 interface is configured to transfer eight data bits then eight data bits appear Otherwise the eighth data bit bit 7 is zero 6 68 AUX When is followed by a hexadecimal digit or symbolic register name it places the status of the RS 232 interface in the lower five bits of the designated register The upper 27 bits are zero The five status bits are as follows Bit 0 1 Parity Error 0 No Parity Error Bit 1 1 Framing Error 0 Framing Error Bit 2 1 Overrun Error 0 No Overrun Error Bit 3 Status of Receive Buffer 1 Character Received 0 No Character Received Bit 4 Status of Transmit Buffer 1 Transmit Buffer is Empty Ready for Next Character 0 Character Still Being Sent When is foll
73. gh LOOP is acceptable Appendix A contains a complete list of the 9010A Language keywords Using a keyword as a symbolic name causes the compiler to issue a SYNTAX ERROR message Symbolic names must contain at least one letter other than A B C D E or F so that they can be distinguished from hexadecimal constants This means that words like BAD ACE or FADE cannot be used as symbolic names because the compiler will interpret them as hex constants Using a hex constant as a symbolic name causes the compiler to issue a SYNTAX ERROR message Language Reference Symbolic Names Symbolic names can be used anywhere that the corresponding actual program number register number or label number can occur in a 9010A program Forward references are permissable for program names and label names In other words an EXECUTE or GOTO statement using a symbolic name is allowed to appear either before or after the corresponding PROGRAM or LABEL statement Symbolic names are case insensitive For example a name can be declared in uppercase and referenced in lowercase and names can be a mixture of uppercase and lowercase letters 6 7 Language Reference EXPRESSIONS The syntax element is used to designate a 9010 expression Expressions consist of combinations of the following e Hexadecimal Constants e g 10FC e Register References e g REG3 Unary Operators CPL DEC INC SHL SHR Binary Operators AND OR Unary
74. guous disk space to create the output files Delete any unnecessary files pack the disk and try again Getting Started IBM PERSONAL COMPUTER Introduction The following information applies to the IBM Personal Computer PC version of the 9010A Language Compiler What You Need The following equipment is needed in order to use the compiler package 1 9005A or 9010A Micro System Troubleshooter with Option 9010A 001 RS 232 Interface 2 IBM Personal Computer model PC or XT with a b 6 A monochrome or color display Version 1 1 or 2 0 of the IBM DOS Operating System At least 128 K bytes of RAM A disk drive We recommend using two disk drives or a fixed Winchester technology disk drive An RS 232 C interface 3 Fluke Y1705 RS 232 C Null Modem Cable and Fluke Y1707 RS 232 C Interface Cable 4 Fluke 9010A 923 9010A Language Compiler IBM PC version 3 13 Getting Started IBM Personal Computer Backing Up the Program Diskette The 9010A Language Compiler package consists of this manual anda write protected program diskette containing the compiler itself and various other programs and data files Before using the compiler you should make a copy of the write protected program diskette This copy is used for normal day to day operations while the original program diskette should be kept in a safe place as a backup so that the working copy can be restored if it is ever damaged Complete instru
75. h 12 84 2 9010A LC On page 6 69 place the character in the left column at the top of the page On page D l add the following to the list of pods 28000 8051 8051X 8031 80186 80188 On page D 3 expand the table to include 28000 O800FFFE 0000 BUSREQ YES WAIT YES 8051 30000 0000 UNUSED YES 8051X 20000 0000 UNUSED YES 8031 10000 0000 UNUSED YES 80186 0000 HOLD YES EXTRDY YES 80188 0000 FFFFO HOLD YES EXTRDY YES 12 84 3 9010A LC Addendum The following supplementary information is provided to clarify or expand material in this manual COMMAND LINE SPACING Some host computers have specific requirements for mandatory spacing in the command lines You must pay particular attention to providing the correct specifying syntax For example the SET RS 232 Utility for the Fluke 1720A Instrument Controller requires that a space be inserted after KB1 and between each parameter ASCII TEXT EDITORS The Text Editor used on the host computer system must produce a source file that contains only standard printable ASCII text characters and no special control or formatting characters SET RS 232 UTILITY PROGRAM Some early versions of the 1720A Set RS 232 C Utility program do not implement the STALL option versions 1 x You may upgrade your software by purchasing the 1720A 200U software upgrade package which contains among other things the new version of the Set RS 232 C Utility program Contac
76. hand feature described in Section 4 Part 2 number 6 9 Language Reference ADDRESSES The following syntax diagrams apply to statements that require an address or an address range to be specified address ad tl Oa Vo ee 5 6 10 Language Reference GENERAL INFORMATION Statement Format Follow these guidelines when constructing statements Each 9010A statement must be on a separate line Continuation lines are not allowed A statement may begin in any column Blanks and tabs are ignored except when they occur in DPY or AUX statements Blank lines are ignored Adjacent keywords symbolic names and numbers must be separated by at least one blank Program Comments The rules for using comments are as follows Comments start with an exclamation point and they extend to the end of the line A comment can be on the same line as a 9010A statement or it can be on a separate line If a comment extends over several lines each line must begin with an exclamation point A comment cannot be placed in the middle of a9010A statement Language Reference General Information File Inclusion The form of the INCLUDE statement is 6 12 We gt a CD The compiler replaces the INCLUDE statement with the contents of the specified file The effect is equivalent to manually typing the contents of the included file in the source file at that point The following rules apply The filename
77. here are more than 32 characters in the AUX DPY string The compiler program will ignore all characters past the first 32 expected in INCLUDE statement Missing quote surrounding the filename to be included F 6 Error Messages FILE TRANSFER ERROR MESSAGES Address descriptors must precede program information You attempted to save address descriptors after saving programs Address descriptors previously saved In this file You attempted to save address descriptors more than once Cannot open filename An illegal file name was entered You attempted to open a file for writing on a write protected disk You attempted to open a file that does not exist You attempted to create a file on a full disk Cannot open temporary file There is not enough room to open a temporary file Data transmission error detected A checksum error was detected indicating that data transmission errors occurred This is possibly due to a bad connection between the 9010A and host computer or the time delay specified by the Setup parameter NEWLINE is not a large enough value Check the connections and try again or try a larger time delay value Illegal option An illegal option was used Enter a valid option Illegal program ordering You attempted to save a program with a number LOWER than a program already saved Incorrect data format for transfer You pressed the wrong keys on the 9010A Port setup parameters were set incorrectly
78. ide on the system default device Copy VERIFY DAT from the original diskette to the system default device File lt filename not found The file filename does not reside onthe system default device Ifthe file is needed copy it from the original diskette to the system default device File fllename error signature Is sig should be slg The indicated file has been corrupted or has been modified Check that the appropriate Copy command was used in systems where different commands are used for binary and ASCII data check for bad blocks on the disk or verify that the version number for the file is the same as specified in the VERIFY DAT file Illegal or missing signature for file fllename The VERIFY DAT file may have been altered Try using a new copy from the original diskette x files tested i bad signatures i missing files Provides a summary of the errors that occurred while running the VERIFY program F 9 F 10 Abbreviations Keyword 4 17 Address Space Information 4 8 Coding Shortcuts 4 16 Default Entries 4 18 Unary Operator Shorthand 4 18 Command Line Mode 5 8 Comments Program 4 7 Compiler Program 9LC How it works 1 5 Package 1 7 Using 5 6 Computer Systems Host 1 4 CP M Operating Systems 3 17 Data Files Pod 1 8 4 11 Default Entries 4 18 Default Setup Parameters Appendix D Disk Verification Program 1 7 Errors Syntax 5 11 Extensions Language 1 6 Fil
79. ine You probably did not include the appropriate pod data file in the source file You may have misspelled the name of the forcing line in an ENABLE statement The pod data file may have been modified to contain a FORCELN name more than six characters long F 4 Error Messages Missing checksum should be xxxx There were checksums in a binary program or the checksums were missing the delimiter characters or Missing label A label was used as the target of a GOTO but was not created through a LABEL statement Also check for misspelling of label names Mixed symbolic label names with hex label numbers Within a single program all of the labels must be symbolically named or all of the labels must be hexadecimal digits The two cannot be mixed Program not found A literally numbered program used as the target of an execute statement 1 EXECUTE PROGRAM 96 was not present in the source file s that was compiled Syntax error The indicated line contains a statement that is incorrectly formed It may have a misspelled word it may be incomplete it may be missing a keyword or a keyword or hexadecimal constant may have been used as a symbolic name Note that the spelling that the 9010A uses on its display is not strictly compatible with the compiled language Example 9010A Display SET TRAP BAD PWR SUPPLY YES 9LC Syntax TRAP BAD POWER SUPPLY YES Refer to the appropriate syntax diagram to verify correct s
80. ing Interactive Mode If you run the compiler in the interactive mode it prompts you for the names of the source and hex files The compiler asks you whether you want a listing file produced If you answer yes the compiler asks for the name of the listing file and the specific listing file options desired runthe compiler in the interactive mode simply enter the command device 9LC RETURN NOTE The use of device in the examples in this section refers to an optional device name specification that may be required for files that are not on a system default device RETURN indicates the key that is pressed to terminate the command line After you have entered the filename command 9LC the compiler responds by displaying its version number and copyright notice The compiler then asks for the name of the source file You now enter the name of the source file for example deviceJDEMO S RETURN Next you are prompted for the name of the hex file to be created by the compiler Enter the name of the hex file followed by RETURN If you simply press RETURN the compiler generates a hex file with the same name as the source file but with a H extension appended to the root of the source file name In this example the hex file name becomes DEMO H on the same device as DEMO S RETURN The compiler then asks you whether you want a listing of the source program You should respond by entering Y yes or N no For this exampl
81. ing Listing File Options contain more information regarding these options The following examples illustrate the use of the command line mode The command 9LC L device JDEMO S RETURN produces exactly the same results as the sequence of options described above under the heading Interactive Mode To compile the source file DEMO S and produce a hex file named DEMO H but not produce a listing file use the following command 9LC device JDEMO S RETURN To produce a listing file with include files expanded use the following command 9LC I device JDEMO S RETURN 5 9 Using the Compiler Compiling Listing File Options The compiler provides a number of different listing file options These options are described below 5 10 I Expand Include Files If the source file contains an INCLUDE statement such as INCLUDE 6802 POD the listing file normally just copies this statement However if the I option is specified then the listing file also shows the contents of the file 6802 POD S Replace Symbolic Names If the source file contains symbolic names for registers programs or labels they are normally copied to the listing file as they appear in the source file However if the S option is specified then the symbolic names are replaced by the actual program number register number or label number EXAMPLE lines from source file EXECUTE DELAY INC ERRCNT normal listing file EXECUTE DELAY INC ERRC
82. m Name and Version Number i e XFER ver 1 0 8080 POD ver 1 2 etc Host Operating System include Version Number Host Computer System i e PC Yescription of problem How can problem be reproduced Attach listing or separate sheet of paper if appropriate Were you able to work around the problem If so how Return completed form to John Fiuke Mfg Inc Digital Service Products M S 267D 9LC Product Manager P O Box C9090 Everett WA 98206 CHANGE ERRATA INFORMATION ISSUE NO 1 12 84 This change errata contains information necessary to ensure the accuracy of the following manual Enter the corrections in the manual if either one of the following conditions exist 1 The revision letter stamped on the indicated PCB is equal to or higher than that given with each change 2 No revision letter is indicated at the beginning of the change errata MANUAL Title 9010A Language Compiler Print Date December 1983 Rev Date C E PAGE EFFECTIVITY Page No Print Date 12 84 12 84 12 84 12 84 12 84 12 84 Ee 9010A LC ERRATA 1 On page 3 1 under Fluke 1720A Instrument Controller System Dependencies CHANGE Test Editor TO Text Editor On page 3 6 change the second sentence in Step 3 to read SET a 1720A system program is included on the 1720A System Disk for this purpose On page 3 11 change the second
83. ment You can only assign symbolic names to these registers locally Cannot open file lt fllename An illegal file name was entered You attempted to open a file for writing on a write protected disk You attempted to open a file that does not exist You attempted to create a file on a full disk An Include file cannot be opened because it would result in more files being opened concurrently than your system allows Checksum error should be xx A checksum error was encountered Duplicate label A label was used more than once Error Messages Duplicate program An attempt was made to compile a source file with two programs with the same number or same name Error In hex line There was a missing character in a binary program Illegal address An address with more than eight hexadecimal digits past the 32 bit limit was specified Illegal bitmask A bitmask equal to 0 or with more than eight hexadecimal digits was specified Illegal bltnumber A bitnumber was specified as hexadecimal rather than decimal or the bitnumber was out of range for the statement i e in ATOG or DTOG statement bitnumber gt 31 will cause this error in DTOG CTL bitnumber 27 will cause this error Consult the appropriate page in Section 6 Language Reference for the statement inerror to determine the bitnumber limits Illegal label number A hexadecimal label number a single digit is out of the range 0 9 or A F For example
84. ment cannot be placed in the middle of a 9010A statement EXAMPLE This example demonstrates the use of comments PROGRAM 0 Main program DPY THIS IS AN EXAMPLE DPY statements can have comments EXECUTE PROGRAM 10 Execute the delay routine DPY OF A VALID 9010A PROGRAM PROGRAM 10 Delay routine REG1 40 Initialize REG1 with delay count 0 LABEL 0 DEC REG1 Count down to zero IF REG1 gt 0 GOTO 0 4 7 Writing Programs General Program Format 9010A Programs The 9010A Language allows programs to be specified in the same form that would be produced by the 9010 AUX I F PROGM keys By connecting a printer to the auxiliary interface of the 9010A you can obtain formatted listings of your 9010A programs These listings can serve as examples of acceptable syntax Address Space Information The 9010A Language allows address space information to be specified in the same form that would be produced by the 9010A AUX I F LEARN keys The following rules apply to address space information The address space information must appear at the beginning of the source file preceding all 9010A programs i e before the first PROGRAM statement Up to 100 address descriptors may be specified EXAMPLE This is an example of a source file containing UUT memory map information ADDRESS SPACE INFORMATION RAM 3 000 ROM 0000 1FFF SIG 0295 ROM 2000 3FFF SIG C262 PROGRAM 0 RAM SHORT ROM TEST
85. must be the name of an existing file If the host operating system is case sensitive regarding filenames then the filename must be properly capitalized A source file may include a file which in turn includes another file INCLUDE statements must be on a line by themselves but can occur anywhere in the source file INCL UDE statements may even appear as a statement in a 9010A program The programmer is responsible for ensuring that the contents of the indicated file can legally be inserted at that point in the source file A standard use of the INCLUDE statement is to include a pod data file SOURCE FILE SYNTAX The following pages contain reference information on source file syntax For more explanation about a specific topic refer to Section 4 Writing Programs Source File Syntax contains the following syntax diagrams SOURCE FILE SETUP ADDRESS SPACE ADDRESS DESCRIPTOR GLOBAL DECLARATION SYMBOLIC REGISTER NAME DECLARATION 9010A PROGRAM PROGRAM BODY LOCAL DECLARATION BINARY PROGRAM INCLUDE DIRECTIVE 6 13 6 14 SOURCE FILE source file 9010A a program p global declaration Function This syntax diagram defines the overall structure of the source file The appropriate pod data file must be included if your programs have any pod dependencies e At this time the pod data file must be one of the following more files will be added as new interface pods are implemented 1802 POD 808
86. n excellent tool for interactive troubleshooting and many users may want to take advantage of its power by writing extensive test programs While the 9010A itself is very convenient for entering relatively short programs it may be advantageous to create and maintain large elaborate or complex programs using a host computer s editing and file management facilities The 9010A Language Compiler allows 9010A programs to be developed conveniently on a host computer system and then transferred to the 9010A for execution Introduction THE HOST COMPUTER SYSTEM The illustration shows the 9010A connected by an RS 232 C serial interface to a host computer system Fluke currently supports the 9010A Language Compiler on the following computer systems Fluke 1720A and 1722A Instrument Controllers Most Z80 CP M systems with 8 inch disk drives Kaypro II IBM Personal Computers PC and XT Registered Trademarks Z 80 Zilog CP M Digital Research Inc Kaypro Kaypro Corp International Business Machines 1 4 Introduction HOW THE COMPILER WORKS The 9010A is able to read and write test programs viaits auxiliary RS 232 C interface The entire contents of the 9010A program memory including setup parameters and address space descriptors are transferred through the serial interface in a special hex data format The 9010A Language Compiler takes advantage of this ability of the 9010A to read programs in hex format
87. nd Appendix D Pod Specific Setup Parameters 6 53 6 54 STALL UNSTALL Syntax hex number Function Allows the programmer to specify the Stall and Unstall characters X ON and X OFF to which the 9010A responds when it is sending data through the AUX I F Setup parameter limits for Stall and Unstall are 0 FF Any ASCII character may be selected for the Stall and Unstall characters The characters are specified with their hexadecimal ASCII values The characters used are those that are required by your remote device The 9010A s default values are as follows STALL 13 CTRL S UNSTALL 11 CTRL Q Example STALL 13 UNSTALL 11 See Also LINESIZE NEWLINE 6 55 6 56 TIMEOUT Syntax TIMEOUT _ decimal number Function Represents a count of how long the 9010A waits before timing out on an interface pod operation Setup parameter limits for TIMEOUT are 0 60000 The 9010A s default value is 200 Example TIMEOUT 200 6 57 6 58 Syntax ACTIVE INTERRUPT pe DATA ERROR Function Allows the operator to individually enable or disable traps on UUT system errors If YES is selected the UUT system error is reported to the operator as it occurs IF is selected the UUT system error is not reported to the operator as it occurs Any error types not explicitly specified are set to the 9010A default values The 9010A s default values are as follows
88. ne Mode An alternative way of running the compiler is to specify all the desired options directly on the command line If any options are specified on the command line then the prompting described above is completely bypassed To run the compiler in the command line mode you enter acommand in the following format device 9LC listoptions H hexfile L listfile srcfile RETURN 5 8 In the above notation items within brackets are optional Srcfile is the name of the source file to be processed by the compiler It may require an optional device name specification The H option is used to override the default hex file name H extension Hexfile is the desired name of the hex file produced by the compiler The L option is used to override the default listing file name L extension Listfile is the desired name of the listing file produced by the compiler The L option without a listing file name can be used to produce a listing file in the case where no listing options are specified The listing file is generated with the L extension The listoptions allow you to specify the form of the listing file The listing file options and their functions are I Expand Include Files S Replace Symbolic Names D Replace Default Entries Expand Keyword Abbreviations Using the Compiler Compiling Specifying any of the options I S D or A causes a listing file to be produced The paragraphs following the next head
89. nguage Section 6 Register Names Predefined 4 29 Appendix B Register Names Symbolic 4 28 Setup Information 4 9 Setup Keywords Appendix A Setup Parameters Default Appendix D Shortcuts Coding 4 16 Shorthand Operator Unary 4 18 Source Files Preparing 5 4 Source Format 5 14 Space Information Address 4 8 Statements Section 6 Symbolic Labels 4 26 Names 4 22 Program Names 4 27 Register Names 4 28 Syntax Diagrams Notation 6 4 Symbols 6 5 Syntax Errors 5 11 Appendix Transferring Programs 5 12 Unary Operator Shorthand 4 18 Use with the 9005A 1 8 Using the Compiler 5 6 Writing Programs Section 4 XFER File Transfer Program 1 7 9LC Compiler Program 5 6 9005A Using with the 1 8 9010A Pod Interaction 4 12 9010A Programs 4 8 9010A Language Compiler Software Error Report Form We would like to know how the 9010A Language Compiler meets your expectations and whether you ncountered any shortcomings including missing features you consider important cases where the program does something unexpected and bugs of all kinds This information will help us to inprove the product We suggest that you retain this sheet as an original and use a photocopy for each report Date Name of User Co Name Dept Street City Mail Stop Phone No Model Number i e 9010A 920 etc from diskette label Software Version Number from diskette label Progra
90. ntax error Example INC REG7 INC ERRCNT is a symbolic register name See Also REG 6 111 6 112 WALK Syntax WALK adar 5 7 REG F REG EJ Function Rotates a programmer specified bit pattern across data lines by performing a series of write operations at a programmer specified address The process continues until the data bits are rotated through every possible position Example WALK 34B0 7F See Also ATOG DTOG RAMP READ WRITE 6 113 6 114 WRITE Syntax esa Function Writes programmer specified data to a programmer specified location in the UUT microprocessor system WRITE CTL causes the 9010A to write control lines to the programmer specified logic levels Ifan expression is used with the CTL form it must have a binary value from 0 to 11111111 The binary string corresponds to the eight possible UUT control lines The 9010A forces control lines represented by a high and forces control lines represented by a0 low Refer to the pod instruction manuals or the label on the interface pod itself to identify which control lines are user writable for a specific pod Example WRITE 713B 2F WR CTL 11000100 See Also ATOG DTOG RAMP READ WALK 6 115 6 116 APPENDICES CONTENTS Av Keywords a6 A 1 B Predefined Register Names B 1 C Optional Keywords and Keyword Abbreviations D Default Setup Par
91. nuing to Part 2 you may wish to copy this program using your host computer and transfer it to your 9010A as an exercise Section 5 Using the Compiler shows how to run the compiler and transfer the generated hex files to the 9010A Once you feel comfortable using the compiler at this level you should proceed with Part 2 which introduces some extended features that simplify the task of writing larger test programs This program tests the U52 flip flop on the output side of the 8255 PIA on the NEC TK 80A single board computer INCLUDE 8080 POD SETUP INFORMATION POD 8080 TRAP ACTIVE FORCE LINE NO TRAP ACTIVE INTERRUPT YES ADDRESS SPACE INFORMATION RAM 3 8C00 8FFF ROM 0000 07FF SIG F77C 100F8 100FA BITS FF PROGRAM 0 WRITE 100FB 80 0 LABEL O REG2 A REG8 1A09 EXECUTE PROGRAM 3 EXECUTE PROGRAM 1 REG8 1 GOTO 1 DPY TESTING U52 READ PROBE Note this address space information is not actually used by the program but the descriptors will be loaded into the 9010A Main program Configure PIA for output Set up entry Set up 10 stimulus loops Store 052 pin9 for prompt Prompt for probe placement Detect probe placement Branch on open node Display Testing U52 Clear probe data register Writing Programs General Program Format 4 14 2 LABEL 2 WRITE 100FA 1 DTOG 100F9 80 BIT 7 WRITE 100FA 0 DTOG 3 100F9 80 BIT 7 DEC
92. oduce a listing file containing a modified copy of the source file The listing file can be requested in several optional formats that make the processing performed by the compiler more visible to the test programmer File Transfer Program The compiler package contains a utility program that is used to transfer 9010A programs between the host system and the 9010A The primary purpose of the file transfer program is to transfer hex files produced by the compiler to the 9010A for execution but it can also be used to transfer programs from the 9010A to the host system Introduction 9010A Language Compiler Package Pod Data Files Some of the Setup commands of the 9010A Language refer to information that is specific to particular 9010A interface pods Pod specific information includes the enableable forcing lines bus test address and RUN UUT address The 9010A Language Compiler package contains a pod data file for each interface pod currently available from Fluke The pod data files provide the information required by the compiler to process the pod specific Setup commands By simply creating new pod data files the compiler can be updated to accommodate new pods which are developed in the future USE WITH THE 9005A 1 8 Hex files that are produced by the 9010A Language Compiler are compatible with the 9005A as well as the 9010A However programs that are transferred from the host system to a 9005A cannot be edited on the 0
93. operating system that runs ona wide variety of host computers What You Need The following equipment is needed in order to use the compiler package with a host computer running the CP M operating system 1 9005 or 9010A Micro System Troubleshooter with Option 9010A 001 RS 232 Interface 2 CP M compatible Z80 based host computer system with a At least one eight inch IBM 3740 format disk drive We recommend using two disk drives b Standard CP M Operating System software version 2 2 c An RS 232 C interface 3 An RS 232 C Interface Cable suitable for connecting your host computer system to the 9010A For example use a Fluke Y1709 RS 232 C Interface Cable to connect a Kaypro II Personal Computer to a 9010 4 Fluke 9010A 921 the version of the 9010A Language Compiler package for CP M on eight inch disks or 9010A 922 the version for the Kaypro II Personal Computer with CP M on a 5 1 4 inch disk 3 17 Getting Started CP M Operating Systems Backing Up the Program Diskette The 9010A Language Compiler package consists of this manual and a write protected program diskette containing the compiler itself and various other programs and data files Before using the compiler you should make a copy of the write protected program diskette This copy is used for normal day to day operations while the original program diskette should be kept ina safe place as a backup so that the working copy can be restored if it is e
94. owed by a hexadecimal digit or symbolic register name it transmits the low order byte contained in the designated register This provides a way for the programmer to send the full range of ASCII characters including characters not usually allowed inan AUX string to the AUX I F Eight data bits are sent if the RS 232 interface is configured to transfer eight bits When is the last character in an AUX I F step it prevents the NEWLINE termination sequence from being sent at the end of the line NOTE In order to cause one of the special symbols or to be sent to the RS 232 interface in the case where the symbol is followed by a hexadecimal digit or symbolic register name the symbol must appear twice in the specification EXAMPLE STATEMENT AUX 1 AUX 9591 AUX X TEXT SENT contents of REG 1 6 69 6 70 BUS TEST Syntax BUS Function Tests for proper function of the UUT control lines data lines and address lines When Bus Test is performed testing of data lines occurs at the address specified in the Bus Test setup parameter Example BUS TEST BUS See Also AUTO TEST IO TEST RAM TEST ROM TEST and BUS TEST in Setup Parameters part of this section 6 71 6 72 Syntax Function DPY iS Displays the string on the 9010A Text to be displayed is separated from the DPY keyword by a single space hyphen or tab Any spaces beyond the single separating character are treated a
95. pelling and syntax Too many labels More than 16 labels were used in one program Too many symbolic names You used more than 100 local symbolic names register label names or more than 200 global symbolic names program names and register names F 5 Error Messages Undefined symbolic name A symbolic register name was used before that register was declared in an ASSIGN statement or the register name was misspelled or a symbolically named program used as the target of an Execute statement 1 EXECUTE PROGRAM MISSING was not present in the source file s that was compiled USAGE Qlc Isda h hexfile lisfile srcfile You have tried to use the compiler program incorrectly 1 6 an illegal option was specified you did not put a filename after the h flag etc The usage line above shows the correct format for using the compiler Warning Illegal character A character outside of the DPY AUX character set has been used For example you have attempted to use parenthesis or brackets in a DPY AUX string Valid characters are described on the AUX and DPY pages in Section 6 Language Reference Warning Incorrect byte count The byte count listed on the program statement is incorrect The program has probably been edited Warning Invalid separator character A character other than a tab space or dash was used to separate a DPY AUX string from the keyword Warning string too long discarding xxxx T
96. pod data file See Also Default Setup Parameters Appendix D Setup Parameter Limits Appendix E Pod Data Files Section 4 Part 1 6 18 ADDRESS SPACE Syntax ADORESS SPACE INFORMATION E address descriptor Function Forms the UUT memory map identifies address blocks of RAM ROM and I O 9 All address descriptors must be declared at the beginning of the source file preceding all programs Up to 100 address descriptors can be specified in the source file Example ADDRESS SPACE INFORMATION RAM 5000 50FF ROM 0000 0FFF SIG 0D47 ROM 3000 4FFF SIG 2B60 ROM 3 7000 70FF SIG 08AA ROM SIG 4409 I O 1A00 1A01 BITS 7F 6 19 6 20 ADDRESS DESCRIPTOR hex number hex number Function Formsthe UUT memory map identifies address block of RAM ROM and I O In a 9010A program statement if a RAM ROM or I O test is specified but the address range to be tested is not specified the 9010A performs the specified test over all blocks of the appropriate memory type described by the address descriptors Parameters and limits are as follows PARAMETER LIMIT signature ROM 0 FFFF bit mask I O Example RAM 5000 50FF ROM 0000 0FFF SIG 0D47 ROM 3000 4FFF SIG 2B60 ROM 7000 70FF SIG 08AA ROM SIG 4409 I O 1A00 1A01 BITS 7F See Also LEARN RAM TEST ROM TEST IO TEST in 9010A Program Statements part of this
97. r 3 Fluke Y1705 RS 232 C Null Modem Cable and Y1707 RS 232 C Interface Cable one 4 Fluke 9010A 920 9010A Language Compiler 1720A 1722A Version Backing Up the Program Diskette The 9010A Language Compiler package consists of this manual and a write protected program diskette containing the compiler itself and various other programs and data files Before using the compiler you should make a copy of the program diskette This copy should be used for normal day to day operations while the original program diskette should be kept in a safe place as a backup so that the working copy can be restored if it is ever damaged Complete instructions on how to copy diskettes can be found in the 1722A System Manual 3 9 Getting Started 1722A Instrument Controller Verifying the Working Diskette Once you have created a working copy of the program diskette you should verify the integrity of its files by running VERIFY one of the programs included in the compiler package To run the VERIFY program type VERIFY RETURN in response to the 1722 FDOS prompt The VERIFY program checks the contents of the 1722A System Device SY0 to verify the integrity of the compiler package files It calculates a checksum for each of the files and compares it to the checksum contained in the VERIFY DAT file VERIFY DAT is an ASCII file that contains a list of filenames and checksums for each of the files in the compiler package Results from
98. rd computer INCLUDE 8080 POD SETUP Equivalent to SETUP INFORMATION POD 8080 TRAP ACTIVE FORCE LINE NO in SETUP statements is optional TRAP ACTIVE INTERRUPT YES ADDRESS SPACE RAM 8C00 8FFF omitted ROM 0000 07FF SIG F77C Ca 1 0 100F8 100FA BITS FF PROGRAM 0 WR 100FB 80 WRITE abbreviated to WR 0 REG2 A REG8 1A09 3 Same as EXECUTE PROGRAM 3 EX 1 REG8 1 GOTO 1 DPY TESTING U52 PROBE 2 WR 100FA 1 Short form of LABEL statement DTOG 100F9 80 BIT 7 WR 100FA 0 DTOG 100F9 80 BIT 7 DEC REG2 IF REG2 gt 0 GOTO 2 EX 2 REG8 A GOTO 3 DPY U52 TOGGLING IMPROPERLY _ is optional in DPY statement a GOTO 4 4 20 Writing Programs Coding Shortcuts 1 DPY WAS PROBE PLACE 21 IF REG1 0 GOTOO DPY 52 OPEN GOTO 4 3 DPY U52 TEST PASSED INCLUDE PROBE1 S Code for PROGRAM 1 is inserted here INCLUDE PROBE2 S PROGRAM 2 INCLUDE PROMPT S PROGRAM 3 4 21 Writing Programs PART 3 SYMBOLIC NAMES Introduction The 9010A Language allows programs labels and registers to be referred to by symbolic names For example the statement EXECUTE PROGRAM 5 could be replaced by something more meaningful such as EXECUTE PROGRAM DELAY Symbolic names can contribute greatly to the readability of programs allowing the programs to be self documenting to a large degree The following rules apply to symbolic names e Symbolic names must begin with
99. re any programs If you attempt to save setup information or address descriptors after programs the XFER program will print an error message At the end of the entire file transfer process the new source file in this case DEMO1 S exists on the host system You can use the R option to return to the file transfer options menu The source file created by the file transfer utility can be modified using a text editor on the host system For example you may want to add comments or change the program numbers to symbolic names The modified source file can be compiled and the resulting hex file can be transferred back to the 9010A 5 15 Using the Compiler Transferring Programs Hex Format 5 16 Hex format files are not generally modified on the host system and they cannot be processed by the 9010A Language Compiler The only reason for transferring files in hex format is to store the programs so that they can be loaded back into the 9010A at a later time To select the hex format enter H RETURN in response to the file transfer option menu XFER prompts you for the name of the hex file to be created For example you could enter RETURN You are then instructed to press the AUX I Fand WRITE keys on the 9010A When the transfer is complete the 9010A displays the message AUX SENDING COMPLETE and the file transfer utility returns to the file transfer option menu Section 6 Language Reference
100. rrect Pod Data file INCLUDE podname POD This statement must appear before the setup information in the source file EXAMPLE INCLUDE 8086 POD 4 9 Writing Programs General Program Format 4 10 The INCLUDE statement is described in Part 2 of thissection Pod data files are described below A POD statement should be placed in the setup section ifany ofthe programs depend upon pod unique features EXAMPLE INCLUDE 8086 POD SETUP INFORMATION POD 8086 TRAP ACTIVE FORCE LINE NO TRAP ACTIVE INTERRUPT YES Writing Programs General Program Format Pod Data Files The 9010A Language Compiler program diskette contains a collection of files with names like 8086 POD 68000 POD etc These files contain pod specific definitions for enableable forcing lines bus test address BUSADR and RUN UUT address UUTADR If you want to specify any of the pod specific setup parameters you should merge the appropriate pod data file into your source file by using an INCLUDE statement The INCLUDE statement must appear before the SETUP INFORMATION section Pod specific forcing lines are defined in the pod data file The pods equate each of the forcing lines to a bit in an enable mask For example the definitions for an 8086 pod are shown below Each of the enableable forcing lines must be defined as the appropriate bit in the enable mask FORCELN READY 0 READY is bit 0 in the enable mask FORCEL
101. rs The best way to learn the 9010A Language is to start by reading through Part of this section and then skip directly to Section 5 Using the Compiler You should use the compiler to compile the example programs provided in Part 1 and then try writing some simple programs of your own Once you feel comfortable with the concepts covered in Part 1 youcan return at any time to this section and proceed with the more advanced concepts covered in the remaining parts The compiler can be used productively at any of the three levels 4 3 Writing Programs PART 1 GENERAL PROGRAM FORMAT Introduction The 9010A Language Compiler allows you to create source files identical to those that the 9010A AUX I F functions send via the RS 232 C auxiliary interface These files can contain the entire contents of the 9010A memory not only 9010A programs but also any available address space and setup information In source files for the 9010A Language Compiler address space information setup information and programs are described in separate blocks These blocks are identified with compiler keywords such as SETUP INFORMATION This section provides information about using the various blocks and shows some sample source files In the 9010A language program statements use an expanded syntax to take advantage of the flexibility of the host system text editor and to provide enhanced readability Program lines may contain comments and symbolic name
102. s 4 17 Unary Operator Shorthand 4 18 Default Entries ceed shies dae e aaa 4 18 saints bide se bis ceca ote ee 4 19 Sample Program 4 20 Part 3 Symbolic Names 4 22 Introduction joie Sate ciel dele ee 4 22 Symbolic Program Names 4 24 Symbolic Labels cece cece cece reece eee eece 4 26 Symbolic Register 65 4 28 Predefined Register Names 4 29 Sample Program 4 30 4 1 4 2 Writing Programs INTRODUCTION This section provides the information you need to write programs for the 9010A Language Compiler The section is divided into three parts Each part is self contained and describes increasingly more advanced features of the 9010A Language The three parts cover the following topics PART I GENERAL PROGRAM Describes how to write simple FORMAT programs using the standard features of the 9010 Language PART 2 CODING SHORTCUTS Introduces some extended features of the 9010A Language which reduce the amount of typing required to enter programs PART 3 SYMBOLIC NAME Allows programs to be made more readable and easier to maintain by using mnemonic names for programs labels and registe
103. s More information about source files and program lines is found throughout this section Section 6 Language Reference contains detailed information on the syntax and usage of each 9010A program statement The following is an example of a short source file containing two valid 9010A programs and no address space or setup information PROGRAM 0 DPY THIS IS AN EXAMPLE EXECUTE PROGRAM 10 DPY OF A VALID 9010A PROGRAM PROGRAM 10 REG1 40 0 LABEL 0 DEC REG1 IF REG1 gt 0 GOTO 0 Writing Programs General Program Format Important Detalls When writing programs for the 9010A Language Compiler on your computer you will find that it is necessary to pay attention to some details that you could ignore when entering programs using the 9010A keyboard These important rules are Each 9010A statement must be on a separate line Continuation lines are not allowed A statement may begin in any column Spaces and tabs are ignored except when they occur in DPY or AUX statements Blank lines are ignored Adjacent keywords symbolic names described in Part 3 of this section and numbers must be separated by at least one space EXAMPLES VALID INVALID READ PROBE READPROBE DTOG 3 100F9 80 BIT 7 DTOG 100F9 80 BIT7 Uppercase and lowercase characters can be used interchangeably EXAMPLE The following program statements are all equivalent WRITE 100FA 1 write 100fa 1 Write 100FA 1 Writing
104. s part of the display message resulting in leading blanks The DPY string can contain a maximum of 32 characters Spaces at the end ofa DPY string are ignored If trailing blanks are desired the appropriate number of underscores should be appended to the DPY string Characters allowed in the DPY string are limited to those available on the 9010A The valid characters are A Z 0 9 1 lt gt space underscores will be converted to spaces The functions of the special DPY characters are shown on the next page Symbolic register names can be used with these special DPY symbols The symbolic register names arecounted as one character in the DPY string A symbolic register name cannot be immediately followed by a hexadecimal character 0 9 A F A separating space is required 6 73 DPY Example DPY test 3 complete pass DPY trailing blank_ See Also AUX CHARACTER 6 74 Functions of DPY Characters ACTION CAUSED Causes the 9010A to beep when DPY is executed This symbol does not appear on the display when DPY is executed When is followed by a hexadecimal or symbolic register name it causes the contents of the designated register to be displayed in hexadecimal on the display The same as for the symbol except that the contents are displayed in decimal When is followed by a hexadecimal digit or symbolic register name it suspends program ex
105. simply press the RETURN key RETURN Using the Compiler Transferring Programs You are then asked to enter the name of the hex file to be transferred To transfer DEMO H the file produced by compiling DEMOS in the previous examples enter deviceJDEMO H RETURN XFER then instructs you to prepare the 9010A for reading by pressing the AUX I F READ and YES keys on the 9010A As soon as you have pressed the YES key the host system starts transferring the hex file to the 9010A NOTE Pressing the AUX I F and READ keys causes the 9010A to clear its program memory and reset all the setup parameters to their default values Any programs currently in the 9010A memory are lost When the file transfer is complete the 9010A displays the message AUX RECEIVING COMPLETE and the host system again displays the file transfer options menu To exit from XFER and return to the host operating system enter Q RETURN The test programs can now be executed on the 9010A just like any other 9010A programs Once the transfer is complete the 9010A may be disconnected from the host system If you have followed the example above to compile DEMO S and transfer DEMO H to the 9010A you can execute the program on the 9010A by pressing the following keys EXECUTE 0 ENTER If your source file contains symbolic program names you must determine which actual program numbers were assigned by the compiler to the symbolic program names For this
106. sory program is included on the program diskette and a copy of the Editor User Manual is included with the compiler package Disk Space After using the Editor or Compiler programs it may be advantageous to pack the disk contents using the P option in the 1720A File Utility program to provide as much free disk space as possible Refer to the 1720A File Utility User Manual if you need help with packing the disk The message Read write past physical end of file means that there was not enough contiguous disk space to create the output files Delete any unnecessary files pack the disk and try again Compiler Organization 3 8 The Compiler program is constructed of overlayed program segments some of which must be loaded during program execution Therefore if the Compiler program is being used from a floppy disk the disk must remain in the disk drive while the program is running Do not remove the disk until the program is finished If the overlays are not available when needed the fatal error message Unable to load overlay will be displayed Getting Started PR FLUKE 1722A INSTRUMENT CONTROLLER Introduction The following information applies to the 1722A version of the 9010A Language Compiler What You Need The following equipment is needed in order to use the compiler package l Fluke 9005A or 9010A Micro System Troubleshooter with Option 9010A 001 RS 232 C Interface 2 Fluke 1722A Instrument Controlle
107. t DA E blew eit eee ah 5 5 Interactive Mode cc cece cece cece eee eens 5 6 Command Line Mode 5 8 Listing File Options 5 10 SyntaX Errors ates ooo aes 5 11 Transferring Programs 5 12 Transferring Programs to the 9010A 5 12 Transferring Programs from the 9010A 5 14 Source Format Gob enni 5 14 Hex Format io Sa eis ed onl Bal tLe Oe 5 16 5 1 5 2 Using the Compiler INTRODUCTION This section provides the information needed to use the 9010A Language Compiler 9LC and the File Transfer Utility program XFER The following topics are covered in this section Preparing the Source File Compiling e Transferring Programs Using the Compiler PREPARING THE SOURCE FILE 5 4 The first step in using the compiler is to create a source file containing the desired 9010A programs The source file may use all the language features introduced in Section 4 Writing Programs For detailed information on specific statements see Section 6 Language Reference To edit and modify the source files you should use the text editor that you normally use on your host computer system By convention the names of source files are usually given a filename extension of S but this is not required by the compiler PIA S is an example of a typic
108. t a Fluke Technical Service Center for information REQUIRED SPACES In the description of terms to be used in expressions shown with a syntax diagram on page 6 9 if more than one operator is specified each operator must be separated from the rest by a space A space must also be inserted between REG and the following hex register number POD DATA FILES New interface pods are continually being developed by Fluke If a data file is not on the disk for your pod you may use the simple procedure shown below to create one also refer to the Instruction Manual for you pod l Using the editor create a new file named lt podname gt POD lt podname gt is the name of your new pod such as 80186 2 Copy the following lines into the file lt podname gt Pod data file FORCELN lt name gt lt n gt busadr lt address gt uutadr lt address gt lt name gt is the name of an enableable forcing line lt n gt is the bit in the enable mask that corresponds to that forcing line Use a 12 84 3 9010A LC Separate line for each enableable forcing line You must define all of the pod s available forcing lines The 80186 Pod for example has two enableable forcing lines EXTRDY and HOLD so you would insert FORCELN extrdy 0 FORCELN hold 1 lt address gt is the hex address to be used for either BUS TEST busadr or RUN UUT uutadr For example busadr uutadr 00000 FFFFO To specify the B
109. t appear twice in the specification EXAMPLE STATEMENT DPY 1 DPY 31 DPY X TEXT DISPLAYED contents of 1 X 6 75 6 76 Function Toggles a programmer specified data bit from one binary logicstate to another by performing two write operations at a programmer specified address The DTOG CTL function toggles a programmer specified control line from one binary logic state to another Ifthe DTOG CTL form is used and the expression immediately following the equal sign is specified explicitly the expression must be a binary value from 0 to 11111111 9 If the address not the DTOG CTL form is specified then the following bit number expression after BIT must have a decimal value in the range 0 n 1 where n equals the number of bits in the microprocessor data bus Inthe DTOG CTL form if an expression is used to specify the bit number it must have a decimal value in the range 0 7 Refer to the pod instruction manuals or the label on the interface pod to identify which control lines are user writable for a specific pod Example DTOG REGF FF BIT REG3 DTOG CTL 01011111 BIT 5 See Also ATOG RAMP READ WALK WRITE 6 77 6 78 EXECUTE Syntax dec Function Executes one program from within another program in a subroutine like fashion Program numbers are limited to the range 0 99 A program may call a program which in turn calls ano
110. t can be used asa time saving checklist Using the Compiler TRANSFERRING PROGRAMS Once you have successfully compiled your programs you are ready to transfer the generated hex file to the 9010A through the RS 232 C serial interface XFER the File Transfer Utility program is provided on the program diskette for this purpose Before running XFER the 9010A must be connected to the serial port of the host system as described in Section 3 Getting Started To run XFER simply enter the command device XFER RETURN After you have entered the command XFER the program responds by displaying its version number and copyright notice followed by a main menu of file transfer options T Transfer hex file from host to 9010A S Transfer source files from 9010A to host H Transfer hex files from 9010A to host C Configure host system Q Quit Whenever this menu is displayed you can return to the host operating system by entering Q RETURN You can also use the Q command to return to this main menu when prompted for a filename in any of the other options in this menu You should select the C option if you want to change the default setting for the RS 232 C serial port Refer to Section 3 Getting Started for further information on configuring the serial port Transferring Programs to the 9010A 5 12 To transfer a file from the host system to the 9010A you should select the T option Since this is the default option you may
111. the VERIFY program are printed in tabular form as each file is checked Missing files or checksum errors that could indicate either corrupted files or incorrect version numbers are reported If such problems occur recopy the diskette and run the VERIFY program again If problems persist and youare unable torunany of the programs contact a Fluke Technical Service Center Hooking Up the System The 1722A must be connected to the 9010A whenever you want to transfer the hex files produced by the compiler to the 9010A for execution 1 Use an RS 232 C interface cable and an RS 232 C null modem cable to connect the auxiliary interface of the 9010A to the serial port on the 1722A 2 Set the RS 232 C auxiliary interface parameters on the rear panel of the 9010A Suggested settings are 9600 baud switch setting 7 Parity even Data bits 8 Stop bits Parity on Getting Started 1722A Instrument Controller The 9010A Setup parameter NEWLINE must be set to 00000D0A the 9010A default value for transferring files Set the parameters of the serial port on the 1722A to correspond to those of the 9010A The Set Utility program SET a 1722A system program is included on the program diskette for this purpose Refer to the 1722A System Manual for a complete description of how to use the SET utility NOTE The STALL option must be enabled on the 1722A if any files are to be transferred from the 9010A to the 1722A This option is not r
112. the language EXAMPLES STATEMENT ABBREVIATED FORM EXECUTE PROGRAM 5 WRITE 100FF 25 3 LABEL 3 SYNC ADDRESS EXECUTE 5 or EX 5 WRITE 100FF 25 or WR 00 25 3 SYNCA or 3 SYNC A Writing Programs Coding Shortcuts Unary Operator Shorthand For multiple applications of a unary operator INC DEC CPL SHL or SHR you may specify the unary operator followed by a decimal number indicating how many times it is to be applied EXAMPLE statement REG1 REGO SHR SHR SHR SHR SHR SHR SHR AND 7F be abbreviated to REG1 REGO SHR 7 AND Default Entrles When programs are created through the 9010A keyboard many of the entries in a program step can be defaulted to the appropriate dedicated register by pressing the ENTER key For example to create the statement READ REGF you need only press the READ and ENTER keys on the 9010A The read address automatically defaults to REGF Similarly if the WRITE and ENTER keys are pressed onthe 9010A the write address automatically defaults to REGF and the data to be written defaults to REGE The 9010A Language provides a similar default capability You can use an asterisk to indicate that an entry should default to a dedicated register The syntax diagrams in Section 6 Language Reference indicate which entries can be defaulted in this way EXAMPLES STATEMENT DEFAULT FORM READ REGF READ WRITE REGF REGE WRITE 4 18
113. ther program Programs may be called up to ten levels of nesting If multiple levels of programs are called a program may not call any program from a previous level A program may not call itself Symbolic program names can be used in this statement The compiler issues a warning message if you attempt to execute a program that is not contained in the files being compiled Example EXECUTE PROGRAM 5 EX 5 EXECUTE DELAY See Also PROGRAM 6 79 6 80 GOTO Syntax cD Pe Function Allows the programmer to construct GOTO unconditional branch steps which redirect program execution to a label in the program Symbolic label names can be used in this statement e Within a single program symbolic names cannot be mixed with hexadecimal label numbers 0 9 A F 9 More than one GOTO step may redirect program execution to the same label The label to which program execution is redirected may appear anywhere in the program Example GOTO 3 See Also LABEL IF 6 81 6 82 IF amp Function Creates conditional branch steps Symbolic label names can be used in this statement Within a single program symbolic labels cannot be mixed with hexadecimal label numbers 0 9 More than one IF step may redirect program execution to the same label The label to which program execution is redirected may appear anywhere in the program Example IF REG3 AND 7F gt REG4 GOTO 1 See
114. ver damaged Verifying the Working Diskette 3 18 Once you have created a working copy of the program diskette you should verify the integrity of its files by running VERIFY one of the programs included in the compiler package To run the VERIFY program type VERIFY RETURN in response to the CP M system prompt The VERIFY program checks the contents of the copy to verify the integrity of the compiler package files It calculates a checksum for each of the files and compares it to the checksum contained in the VERIFY DAT file VERIFY DAT is an ASCII file that contains a list of filenames and checksums for each of the files in the compiler package Results from the VERIFY program are printed in tabular form as each file is checked Missing files or checksum errors that could indicate either corrupted files or incorrect version numbers are reported If such problems occur recopy the diskette and run the VERIFY program again If problems persist and youare unable to run any of the programs contact a Fluke Technical Service Center fay Getting Started CP M Operating Systems Hooking Up the System The host computer must be connected to the 9010A whenever you want to transfer the hex files produced by the compiler to the 9010A for execution l Use an RS 232 interface cable to connect the auxiliary interface of the 9010A to a serial port on the host computer Set the RS 232 auxiliary interface parameters onthe rear
115. verview of the 9010A Language and describes how to create 9010A source files Describes how to use the compiler and the file transfer program Provides detailed information on the 9010A Language syntax in a quick reference format Provides other information about the 9010A Language How to Use This Manual SUGGESTED USE The sections in this manual appear in the order in which they are intended to be read by a first time user of the 9010A Language Compiler Section 1 Introduction provides an overview of the features of the 9010A Language Compiler If you are a first time user of the compiler the introduction gives you an idea of what to expect This section How to Use this Manual provides guidance in using the manual so that you can quickly and correctly begin to use the 9010A Language Compiler Section 3 Getting Started provides you with the information you need to get your new compiler running Before attempting to use the compiler it is essential that you read this section thoroughly so that you can avoid problems Getting Started shows you how to set up your host computer system and how to connect it to the 9010A Section 4 Writing Programs uses explanations and examples to introduce you to the 9010A Language and demonstrates how to create 9010A program source files Everyone should read this section at least once When you become more familiar with the 9010A Language you will rely less on Section 4 and more on Se
116. vidual tests Example AUTO TEST AUTO See Also BUS TEST IO TEST RAM TEST ROM TEST 6 65 6 66 Function AUX Allows for sending and receiving data between the 9010A and other devices using the RS 232 Interface Option The string parameter represents the text to be sent The text is separated from the AUX keyword by a single space hyphen or tab Any spaces beyond the single separating character are treated as part of the display message resulting in leading blanks The AUX string can contain a maximum of 32 characters Spaces at the end of an AUX string are ignored If trailing blanks are desired the appropriate number of underscores should be appended to the AUX string Characters allowed in the AUX string are limited to those available on the 9010A The valid characters are A Z 0 9 lt gt space underscores will be converted to spaces The functions of the special AUX I F characters are shown on the next two pages Symbolic register names can be used with these special AUX characters Symbolic register names are counted as one character in the AUX string 6 67 AUX A symbolic register name cannot be immediately followed by a hexadecimal character 0 9 A F A separating space is required Example AUX ROM SIGNATURE IS ROMSIG1 ROMSIG is a symbolic register name The String to be sent is ROM SIGNATURE IS followed by the hexadecimal contents o
117. w be displayed E Save the entire file Save the setup information Save the address descriptors Save all programs 99 Save the specified program Return to the main menu S A P 0 R Using the Compiler Transferring Programs If you choose to save the entire file then setup information address descriptors and all programs will be saved If you choose to save the setup information or the entire file XFER then prompts forthe name of a pod data file since the 9010A Language Compiler requires that a pod data file be included before any pod dependent setup information For the present example enter device Z80 POD RETURN In this case XFER inserts a statement of the form INCLUDE Z80 POD immediately before the SETUP INFORMATION statement in the source file on the host system If for some reason you do not want to specify a pod data file simply enter RETURN when prompted for the name of a pod data file No INCLUDE statement will be inserted into the source file If you choose to save the address descriptors and none exist a warning message will be displayed You have the option of saving individual programs or all of the 9010A programs in a single operation If you attempt to save a program that does not exist a warning message will be issued NOTE The compiler requires setup and address space information to appear before any programs Therefore setup or address space information should be saved befo
118. ways optional used in LABEL statements Optional only in EXECUTE PROGRAM xx commands None always optional used in Setup and Address Descriptor sections Optional only in READ PROBE command None always optional used in program statements TWO EQUIVALENT AND ACCEPTED STATEMENTS AUTO TEST AUTO WRITE 100FF 25 WRITE 100FF 25 DPY TEST MESSAGE DPY TEST MESSAGE POD 8080 POD 8080 3 LABEL 3 3 EXECUTE PROGRAM 35 EXECUTE 35 SETUP INFORMATION SETUP READ PROBE PROBE PROGRAM 10 524 BYTES PROGRAM 10 C 1 Keyword Abbreviations C 2 KEYWORD ABBREVIATIONS me KEYWORD ABBREVIATION SYNC ADDRESS SYNC A SYNC DATA SYNC D SYNC FREE RUN READ WRITE EXECUTE Ba N Appendix D Default Setup Parameters The information in the following table applies only to these pods 1802 6502 6800 68000 6802 6809 6809E 8041 8048 8080 8085 8086 8086MX 8088 8088MX 9900 Z80 Setup Parameters Common to All Pods Listed Above PARAMETER DEFAULT VALUE TRAP BAD POWER SUPPLY TRAP ILLEGAL ADDRESS TRAP ACTIVE INTERRUPT NO TRAP ACTIVE FORCE LINE YES TRAP CONTROL ERROR YES TRAP ADDRESS ERROR YES TRAP DATA ERROR YES EXERCISE ERRORS YES BEEP ON ERR TRANSITION YES STALL 13 UNSTALL 11 NEWLINE LINESIZE 79 BUS TEST 0000 RUN UUT 0000 3 a pod name is not specified in the setup parameter section of the source file then the default address for BUS

Fluke 9010 Compiler

Contents

Download Pdf Manuals

Related Search

Related Contents