Proteus 8.9免安装版本、Proteus 8 Professional 8.9免安装版本

INSTRUCTIONS FOR ASM11 Copyright (c) 1998-1999 by Tony G. Papadimitriou, M.S. e-mail: tonyp@acm.org Hi 68HC11 enthusiasts, PLEASE TAKE THE TIME TO READ THE ENTIRE DOCUMENT (SPECIALLY IF THIS THE FIRST TIME YOU USE THIS PROGRAM). THIS WILL HELP YOU AVOID UNNECESSARY HEAD-SCRATCHING FOR WHAT'S ALREADY DOCUMENTED. This archive should contain the files listed in the file CRC To extract the files from this archive, you should open with the "Create Directories" option for whatever archiver you use, (eg., UNZIP -D ASM11_xx.ZIP) This README.TXT file is not intended to be an assembly language manual or tutorial. It assumes the user knows how to program in 68HC11 assembly or has the desire to learn and has relevant literature to consult. If you are not familiar with 68HC11 you should get a 68HC11 Assembly Language Reference, some of them are free, if you know where to look (hint: start with Motorola). If you are converting your source from some other assembler, please read the relevant section in this file. It will save you time. To most experienced 68HC11 users, a lot of the information in this document may seem obvious and unnecessary to be mentioned. I have to take into account that some potential users are new to 68HC11 and assembly language programming in general, so I've tried to make it a bit more comfortable for them. 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴 ABOUT THE SOURCE CODE EXAMPLE FILES INCLUDED (in the subdirectory SAMPLES) 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴 Several assembly language source files are included. All example programs are only meant to illustrate acceptable assembly language syntax for ASM11 more than to provide accurate working programs. These programs, although carefully reviewed, may contain errors, or not do exactly what they claim to do. They only provide examples for you to work with. I believe they are correct, but some bugs may exist in them so please take the time to verify their correctness yourself (ie., don't use them blindly). FRAME.ASM and the *.MOD file in the OS11 directory are a set of files that provide a framework for actual programs. All OS11 modules are fully functional and ready to use in your program. 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴 ABOUT THE EXTRA UTILITIES INCLUDED (in the subdirectory UTILS) 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴 M.EXE There is an extra utility included in this archive, M.EXE (a MORE type program). This is a utility for viewing text files. Type M on the command line by itself to get a comprehensive help screen. You may use this utility to view listings, source files, etc. It will adjust to any screen display, whether you're working at 40, 80, or 132 column widths. (In case you didn't know, most systems support wider than 80-column displays -- even under DOS, which for one thing makes it easy to view assembler listings in all their beauty without printing them out.) Another function of this utility is that it will act as a Unix-to-PC file converter. The assembler expects regular DOS text files and it will not correctly read files that aren't such, eg., files that do not end with CR/LF or simply a CR. Please note that assembling such files does not always produce errors or warnings because if, for example, there is a CTRL-Z (end-of-file) character, the assembler will stop reading the source file assuming its the end of it. Also, files having only LF as end-of-line marker will only have their first line processed, and in most cases this will not give any errors, since usually the first line is either a comment or some equate. This may give you the impression you source has assembled correctly when in reality, only a portion of it has and it simply happened not to produce errors. One way to quickly check for such problems is to look at the line number counter at the end of the assembly. If you still have problems, there may be nulls (ASCII 0) or other strange control characters left in the file. You could try clearing those away by loading the file into an ASCII editor, and re-saving it. Not all ASCII editors will do that, though. Yet another function of M.EXE is to de-tab a file, ie., expand its tabs. Although ASM11 can use the -Tn option or the $TABSIZE directive to control tab expansion of the source file, you may wish to convert someone else's source to a no-tabs text if you don't normally save your sources in tabbed form. You set the -Xn option to whatever tab size the original is using, then redirect the output to the new file, eg., M -X10 TABBED.ASM >UNTABBED.ASM will create the file UNTABBED.ASM by expanding possible tabs inside TABBED.ASM and using a tab size of 10. What tab size to use is not easy to tell. Normally, most editors use a default value of 8, but they also allow changing this value to any number. Before converting, try viewing the file with different -Xn settings until you see instruction, operands, and comments align properly (although that's not always the case). Note, however, that M.EXE wraps lines at the width of the current video mode, so if run from an 80-column display, everything beyond column 80 will be placed on a new line. This may require some further editing to bring wrapped lines back up to the line they belong. You can limit the wrapped line problems by running M from a 132-column display. TERM.EXE One other extra utility included is TERM.EXE (a very basic terminal program). Type TERM -? to get a comprehensive help screen. Set the options (such as COM port, BAUD, etc.) that apply to your setup, then save them with the -W option inside the TERM.EXE file so it will remember them. TERM is not only meant for use with evaluation boards (actually it was written for remotely controlling a DOS PC using DOORWAY), but this is the reason for being included here. Once configured, typing TERM brings up a screen that let's you talk to an EVBU, EVM, EVS, or custom SCI-enabled 68HC11 system. You can use the PgUp key on your keyboard to give the filename of an S19 file to upload to your system. If the -E option is on, PgUp does not require having typed the "LOAD T" command beforehand. If the -E option is off, you must type LOAD T in advance. Although not tested with every system, it should work on all evaluation boards that accept the BUFFALO command LOAD T to load an S19 file. It has been tested on an EVBU and an EVS. You may exit the terminal mode by pressing the SysRq key (usually CTRL-PrintScreen, laptops may require a different sequence). There are some reports that when the -E option is enabled the upload won't work. This is very likely a problem with delayed responses from the LOAD T to the beginning of the upload (I'll look into it, not so easy to fix when I can't reproduce the problem in my system). Play with the -Ln option using different delay values, you should be able to make it work eventually. If you keep having problems like this, turn off the -E switch and manually type the LOAD T command before commencing the upload. It should work at speeds upto 9600; you may encounter problems at higher speeds as the MCU itself (running at 2MHz) isn't ready to read another line and gets out of sync. This will also depend to a certain extent on the length of your S19 records (longer ones are more likely to cause errors) and the coding of the loader itself. SB2ASM11.EXE This utility is a "quick and *very* dirty" program to make SBasic produced assembler programs ASM11 compatible. It d