Файл: Microcontrollers in Practice (Mitescu M., 2005).pdf

Note that before launching the actual write command, the program disables all interrupts. The reason for this is that an interrupt occurring between the execution of steps 4 and 5 would delay the moment when EEWE is set beyond the limit of four cycles after EEMWE is set. Writing EEWE in step 5 would find EEWME cleared by hardware, and the whole write operation would fail.

9

HC11 Development Board

9.1 In this Chapter

This chapter contains the description of a simple development board based on the microcontroller 68HC11F1, and related software utilities, intended to allow the user to write and test software applications for this microcontroller.

9.2 Description of the Hardware Module

A development system for the study of a microcontroller comprises a hardware module and a set of software utilities (cross-assembler, compiler, etc). Along with the data sheets and application notes from the manufacturer, this allows the user to reach a clear understanding of the resources and capabilities of that specific microcontroller, and to write and test software applications for it.

The module presented here is one of the simplest possible. It is built around the Motorola 68HC11F1 microcontroller, operating with an external EEPROM memory AT28C256, easily reprogrammable around 10 000 times. Test programs can be written directly to AT28C256 using a standard commercial EPROM programmer.

The 68HC11F1 microcontroller does not have internal program memory – it is designed to work with external ROM in expanded mode. For this purpose, the microcontroller can provide up to four chip select signals for external memory or other I/O devices. The way these signals activate, their polarity and relative priority are software controlled. The schematic of the hardware module is presented in Fig. 9.1.

There are very few external components, besides the microcontroller. The program memory is connected directly to the address and data buses, and the chip select signal CSPROG is provided by the microcontroller, without the need of an external address decoder.

The external clock circuit is implemented using the crystal Q1 (8 MHz typical), the capacitors C5 and C6 (15–22 pF) and the resistor R1 (1–10 M). This type of oscillator circuit is typical of all HC11 family members.

The RESET circuit comprises the transistor T1 along with resistors R2, R3, R4, capacitor C9 and connector JP1. At power-up, the capacitor C8 starts charging through R2, feeding current to the base of T1. This saturates the transistor for a time interval comparable to R2×C9, generating an active LOW pulse on the RESET line of the microcontroller. A similar process occurs when the terminals of JP1 are short-circuited, providing a means for manual reset of the module.

The IC2 circuit (MAX232) along with capacitors C1, C2, C3, and C4 implement the typical RS232 interface presented in Chap. 3.

The control signals MODA, MODB and the external interrupts IRQ and XIRQ are pulled up to Vcc using four 10 K resistors. The rest of the I/O lines of the microcontroller are brought to three header-type connectors SV1, SV2, SV3.

The module is powered from a DC or ac adapter, able to deliver 9–12 V at 250 mA. The input voltage is applied through the bridge rectifier B1 to the voltage regulator IC4 (7805) that generates the +5 V supply voltage.

9.3 Assembling and Testing the Module

All the projects described in this section come with detailed schematics and printed circuit board drawings available on the accompanying CD. The PCB drawings are created with Eagle 4.11 from CadSoft. A freeware version of this software is available for free download from Cadsoft, so that the user can view, edit, and print all the schematics and the PCB drawings of the projects described in this book.

The major advantage of this CAD software is that it is very easy to learn, and the freeware version, despite some limitations, still allows the user to design pretty complex microcontroller based circuits.

Most companies manufacturing custom printed circuit boards accept drawings created with Eagle 4.11, and the cost per square decimeter of printed circuit board is reasonable. However, in this particular case, the circuit is so simple that it can be easily realized on a prototyping board using the wire wrap technique. It is recommended to use appropriate IC sockets for all ICs, except IC4.

Refer to Fig. 9.2 for a possible component layout of the PCB. Once you have the module assembled, follow this test sequence:

1.Apply power to the module, without having the ICs inserted in the sockets.

2.Check the +5 V voltage on every socket.

3.Check the RESET circuit by measuring the voltage in the collector of T1. When a short-circuit is applied to the terminals of JP1, the voltage on this point drops near 0 V, while without short-circuit it stays near the Vcc value.

4.Insert the ICs into the sockets and apply power to the module. With an oscilloscope check the E clock on pin 4 of the microcontroller. If you don’t have an oscilloscope, use a voltmeter to measure the RESET signal on the collector of T1. If the oscillator fails to operate, the clock monitor circuit of the microcontroller will force this line to logic zero.

For ALL the projects described in this book, the RS232 interface is connected to a header-type connector. The adapter cable between the header connector and the NULL MODEM cable is presented in Fig. 9.3, and the NULL MODEM CABLE is shown in Fig. 9.4.

9.4 Description of the Software Components

The freeware cross-assembler offered by Motorola for the HC11 family, called AS11.EXE, is extremely simple and has many weak points. Among them, the most important are:

•It does not allow the INCLUDE directive, thus forcing the user to write all the source code in a single file. This can be extremely inconvenient. For example, the source code for the free monitor offered by Motorola (BUFFALO) has over 5000 lines of code. Obviously, it is virtually impossible to debug such a program, if anything goes wrong. On the other hand, if the assembler accepts INCLUDE, the source code can be organized in smaller, reusable, blocks of code, placed in distinct files, according to some user selected criteria, e.g. TIMER.ASM, SCI.ASM, OUTPUT.ASM, etc. All these software modules are invoked by a main module, using the INCLUDE directive.

•It does not allow macro definitions, thus severely limiting the freedom of the user to customize his/her programming environment.

For these reasons, we chose to use a different freeware cross-assembler, called ASHC11, created by Peter Gargano. Besides INCLUDE and macro definitions, this cross-assembler has many additional features. See Appendix B2 for details on how to download this free software.

Getting Started

Step 1. Installing the Cross-Assembler

ASHC11 is a DOS application and does not require any special installation procedure. To install it, create a folder on the hard drive with the name C:\ASHC11, and unzip the downloaded archive to this folder. Then create a DOS window, having the working directory in C:\ASHC11.

To do this, in Windows™ 9.x, press the right button of the mouse on the desktop, and, from the list of options presented, choose New, then Shortcut. In the space reserved to define the command line associated to the new shortcut, type “Command.com”, then press the Next button, and Finish.

The effect of this operation is that a new shortcut appears on the desktop, named “MS-DOS™ Prompt”. To complete the job, specify the working directory for this

120 9 HC11 Development Board

shortcut. To do this, select the new shortcut, then press the right button of the mouse and choose the option Properties, and then Program.

In the field labeled Working, type C:\ASHC11, and then press OK. Double clicking on the new shortcut opens a DOS window, where applications can be launched from the command line by simply typing their names, followed by [ENTER].

To simplify the use of the assembler, we created a batch file, called LASM.BAT, with the following contents:

ashc11 %1.asm -LIST=%1.lst bincvt %1.s19 -OV

The first line invokes the assembler, and instructs it to create a list file, having the same name as the source file, and the extension .LST. The default extension for the source file is assumed to be .ASM.

The second line calls a conversion utility BINCVT, provided by the author of ASHC11 in the same archive with the assembler. BINCVT creates a binary file having the same name as the source, and the extension .BIN. This can be useful, since some EPROM programmers do not properly handle the S19 output files generated by the assembler.

The batch file must be invoked by specifying the name of the source file, without extension, like in the example below:

LASM STEP1

This causes the file STEP1.ASM to be open and assembled. The following files are created in this process:

•STEP1.S19 – this contains the actual executable code in Motorola S19 format.

•STEP1.BIN – contains the executable code in plain binary format.

•STEP1.LST – this is the list file.

The list file is a text file, containing detailed information on the source file, as well as on the result of the assembly process – the output code, and the address where this will be placed in the memory map. The list file also explains the variable definitions, and gives a short description of the errors that might occur during assembly.

ASHC11, like all MS-DOS™ based programs, admits only short file names in the format “8.3”, i.e. maximum eight characters for the file name, and maximum three characters for the extension. If you are using a Windows™ based text editor to create your source files, like Notepad, make sure you observe this rule when you save your files on disk.

If you are not familiar with MS-DOS™ programs, consult Appendix A15 for the description of a software utility that allow invoking the assembler from a Windows™ application. This utility also contains a text editor for creating and editing the assembler source files.

Step 2. Defining the Memory Sections for the Program

Consider the following simple source file: (STEP1.ASM)

TITLE Defining origins for DATA and CODE sections

Though very simple, this code fragment contains some fundamental elements, to be considered in any program, written for any microcontroller. It shows how to define the starting address of the two main memory segments: the CODE segment (or section), where the executable code is placed, and the DATA segment, normally a RAM zone, reserved for variables. This is done with the ORG (Origin) directive.

The assembler associates a pointer to each predefined memory section (DATA, CODE). The ORG directive initializes the pointer of the current section to the value specified as a parameter to ORG.

Symbolic parameters for ORG are allowed, like in this example:

RESET EQU $8000

CODE

ORG RESET

The assembler automatically increments the pointer associated with the section, after each operation that reserves space in that section. In the example below, three variables are defined:

DATA

ORG $100

VAR1 DS 1

BUF1 DS 10

VAR2 DS 1