Using the Serial Port The core file supports the serial port installed on the TI TMS320C54x DSP. The serial port on the EVM is connected with a cable to COM2 on the PC. Before jumping to your code, the core file initializes the EVM's serial port to 38,400 bits per second (bps) with no parity, eight data bits, and one stop bit (but it may be necessary to restart the DSP completely if the serial port does not work.) It then accepts characters received from the PC by the UART (Universal Asynchronous Receiver/Transmitter) and buffers them in memory until your code retrieves them. It also can accept a block of bytes to transmit and send them to the UART in sequence. Two macros are used to control the serial port: READSER and WRITSER. Both accept one parameter. READSER n reads up to n characters from the serial input buffer (the data coming from the PC) and places them in memory starting at *AR3. (AR3 is left pointing one past the last memory location written.) The actual number of characters read is left in AR1. If AR1 is zero, then no characters were available in the input buffer. WRITSER n adds n characters starting at *AR3 to the serial output buffer; in other words, it queues them to be sent to the PC. AR3 is left pointing one location after the last memory location read. Note that READSER and WRITSER modify registers AR0, AR1, AR2, AR3, and BK, as well as the flag TC. Be sure you restore these registers after calling READSER and WRITSER if you need them later in your code. Note also that the core file allows up to 126 characters to be stored in the input and output buffers. Neither the DSP hardware nor the core file protect against serial-buffer overflows, so you must be careful not to allow the input and output buffers to overflow. (The length of the buffers can be changed by editing ser_rxlen and ser_txlen values in core.asm.) The buffers are 127 characters long; however, the code cannot distinguish between a completely-full and completely-empty buffer. Therefore, only 126 characters can be stored in the buffers. It is easy to check if the input or output buffers in memory are empty. The input buffer can be checked by comparing the values stored in the memory locations srx_head and srx_tail; if both memory locations hold the same value, the input buffer is empty. Likewise, the output buffer can be checked by comparing the values stored in memory locations stx_head and stx_tail. The number of characters in the buffer can be computed by subtracting the head pointer from the tail pointer; add the length of the buffer (normally 127) if the resulting distance is negative. The following example shows the minimal amount of code necessary to echo received data back through the serial port. It is available as ser_echo.asm.

Line 8 sets AR3 to point to the location hold so that READSER will store serial data there. On Line 9,


	READSER 1

reads one serial byte into hold; the byte is placed in the low-order bits of the word, and the high-order bits are zeroed. If a byte was read, AR1 will be set to 1. AR1 is checked in Line 12; Line 13 branches back to the top if no byte was read. Otherwise, AR3 is reset to hold (since READSER moved it), then on Line 16, WRITSER sends the word received. Finally, Line 18 branches back to the start to receive another character.

Using MATLAB to Control the DSP MATLAB allows you to create a visual interface with standard graphical user-interface (GUI) controls such as sliders, checkboxes, and radio buttons to call MATLAB scripts. The following scripts can be used to create a sample interface: ser_set.m: Initializes the serial port and user interface wrt_slid.m: Called when sliders are moved to send new data

Creating a MATLAB user interface The following code (ser_set.m) initializes the serial port COM2, then creates a minimal user interface consisting of three sliders.

Line 4 of this code uses the Windows mode command to set up serial port COM2 (which is connected to the DSP) to match the serial port settings on the DSP evaluation board: 38,400 bps, no parity, eight data bits, and one stop bit. Line 7 then creates a new MATLAB figure for the controls; this prevents the controls from being overlaid on any graph you may have already created. Lines 12 through the end create the three sliders for the user interface. Several parameters are used to specify the behavior of each slider. The first parameter, Fig, tells the slider to create itself in the window we created in Line 7. The rest of the parameters are property/value pairs: units normal tells MATLAB to use positioning relative to the window boundaries. pos Tells MATLAB where to place the control. style Tells MATLAB what type of control to place. slider creates a slider control. value Tells MATLAB the default value for the control. max Tells MATLAB the maximum value for the control. min Tells MATLAB the minimum value for the control. callback Tells MATLAB what script to call when the control is manipulated. wrt_slid.m is a MATLAB file that reads the values of the sliders and sends them to the DSP via the serial port.

User-interface callback function Every time a slider is moved, the file wrt_slid.m is called:

Line 4 of wrt_slid.m opens COM2 for writing. (It has already been initialized by ser_set.m.) Then Line 7 reads the value of the first slider using MATLAB's get function to retrieve the value property. The value is then rounded off to create an integer, and the integer is sent as an 8-bit quantity to the DSP in Line 8. (The number that is sent at this step will appear when the serial port is read with READSER in your code.) Then the other two sliders are sent in the same way. Line 17 sends 0xFF (255) to the DSP, which can be used to indicate that the three previously-transmitted values represent a complete set of data points. Your code can check for the value 255 to detect and correct synchronization errors. Line 20 closes the serial port. Note that MATLAB buffers the data being transmitted, and data is often not sent until the serial port is closed. Make sure you close the port after writing a data block to the serial port.