EEL4744 – Summary of Lab Tips Mauricio J. Vacas EEL4744 Spring 2008 TA May 23, 2008 Contents Introduction .................................................................................................................................................. 3 Lab 2 – UF 68HC12 Board Construction & Software Tools ...........................................................................4 Lab 3 – Assembly Programming & Elementary Wiring ................................................................................. 5 Lab 4 – Elementary Programming & Adding a Keypad .................................................................................7 Lab 5 – Software Switch Debounce & CPLD Programming...........................................................................9 Lab 6 – Microprocessor Port & Memory Expansion ................................................................................... 11 Lab 7 – LCD Display & Real Time Interrupt (Stop Watch) ........................................................................... 13 Lab 8 – Asynchronous Serial I/O: Interfacing to an External UART and using the Internal UART .............. 16 Lab 9 – A/D & D/A Conversion.................................................................................................................... 21 Extra Stuff – How to debug your non‐working board.................................................................................23 Introduction This document summarizes a set of tips I created for each lab while I was TA for Microprocessor Applications. The purpose is to supplement the lab documents and clarify any confusion as to the tasks and goals for each lab. Each lab is based on the labs taught in the Spring of 2008 by Dr. Tao Li, although the work is very similar to my own expe rience when I took the class. The end goal is to guide students to not only understand how to do the labs, but see how the labs connect with one another and see the big picture of using microprocessors and their interactions with components. I try to not just regurgitate the information on the lab documents, but expand on it and provide references for more information on the subject. At the end of the document, I provide a set of tips on how to debug boards that don’t work. I hope these set of tips are useful in providing clarity and understanding to students as they progress through this fascinating field. ‐Mauricio J. Vacas Lab 2 – UF 68HC12 Board Construction & Software Tools The main purpose of this lab is for you guys to finish your boards and boot them so you can run programs on it. In order to do this, you guys should have the following programs installed on your laptops: a) MiniIDE ‐ http://www.mgtek.com/miniide/ b) Quartus ‐ http://www.altera.com/products/software/products/quartus2/qts‐index.html c) HC12 Simulator ‐ http://hcs12text.com/freesim.html Because of this you should bring your laptop to this and every lab in the semester. I'm sure by now everyone's already run through the Board Construction Manual. In order to get more information and start understanding your boards better, I recommend reading through the Board Manual. It will answer a great deal of questions regarding the purpose of jumpers on the board as well as a handy reference when making connections to the headers. I recommend printing it out as it will be heavily used throughout the semester. The other reference material which will not be used as much this week, but will be used heavily throughout the semester is the Programming Reference Manual. This manual provides all of the assembly instructions the microprocess or supports and how to use them. Therefore, it is very useful for assembly language programming. You can order a hardcopy of this manual by going to http://www2.hibbertgroup.com/freescale/main?action=hibbertgroup.client.freescale.ui.inventory.InventorySearchController Writing under description: 68HC12 Under Type of Item, select Reference Manual Click search The item number is CPU12RM and its description is: HCS12 AND M68HC12 CPU12 REFERENCE MANUAL. Just add it to the cart and checkout. Lab 3 – Assembly Programming & Elementary Wiring This section serves to clarify any ambiguities in the lab 3 document as well as to provide guidance on how to accomplish the tasks for this lab. As the lab purpose states, lab 3 is used to introduce students into the basics of assembly language programming and wire wrapping of components. Part I. • For the dummy vector, different TA's might approach this differently, but you can assume that the TA might give you this vector as an assembly program to compile and download into the board. • Remember that using EQU to define a constant is different than a label used to mark an address. In other words: o CONST EQU $01, is not the same as o ORG $9000 LABEL ABA o The value of CONST is $01, whereas the value of LABEL is $9000 o Regardless, you can also store an address label as a constant:  LABEL EQU $9000 • The breakdown of the address labels/constants are as follows; the following values will be provided in the lab, but for testing students can assume their own values: o score_addr: starting address of dummy vector containing values 0‐100 o score_vector_len: length of vector, number of elements in vector o grade_addr: starting address of vector containing letter grades determined from the numeric values in the dummy vector o You should store all of these values as constants in your program, so that when the actual values are given in lab you can modify them easily. Part II. • All wire wrapping is done in the large unused area of the board. Instead of putting the components (LEDs, R‐packs) directly on the holes, you should put them on the sockets with large pins for easier wire wrapping. • You do not need to solder all of the pins of the sockets on the board, just the corners is sufficient to keep the socket in place. • For the resistor, you can use the 330 Ohm DIP RPACK(should look different than the other chips and have two rows of pins, 8 on each side) included in your kit. To determine which ones they are, use a multimeter to test the resistance between the two sides of the RPACK. • To write "1s" to DDRT, you can use the memory modify (mm) command on the console you get when you boot up the