readme.txt

DM642支持4个串口的驱动代码

#
#  Copyright 2003 by Texas Instruments Incorporated.
#  All rights reserved. Property of Texas Instruments Incorporated.
#  Restricted rights to use, duplicate or disclose this code are
#  granted through contract.
#  
#
# "@(#) DDK 1.10.00.23 07-02-03 (ddk-b12)"
TITLE
-----
UARTHW_EVMDM642 stress tests (uartttest)

USAGE
-----
This application tests the hardware UART on the EVMDM642 board by 
transfering data from the PC communication ports (using HyperTerminal) to the
DSP hardware via a serial cable. The application must link both a generic
driver and a specific driver library in order for it to function correctly. 
These libraries are called uarthw_evmdm642.l64 and uartmd.l64. They can be found
in the ddk/lib directory.

DOCUMENTATION
-------------
The documentation for this device driver can be found at:
        /ddk/docs/uart.pdf

DESCRIPTION
-----------
- uarttest test:
  --------------
  This example demonstrates how an application can use a hardware UART to
  transfer data from the a target(DSP) to a host(PC) via the GIO synchronous
  APIs.  Data inputed from the host is sent to the target and echo back onto 
  the host.

FILES
-----
- uarttest.pjt: project files to build the application uarttest.
- ../uartttest.c: implementation of uarttest.
- ../uartttest_params.c: UART driver parameter settings.
- ../uarttest.tci: tconf configuration file.  See notes below.
- uarttestcfg.tcf: tconf configuration file.  See notes below.
- tconflocal.tci: tconf configuration file.  See notes below.
- readme.txt: this file

NOTES
-----
- These examples are not delivered with any CDB configuration files.  This was
  done to avoid customer versioning problems, since CDB versions must be matched
  up with the DSP/BIOS product version.  Instead, these applications have been
  delivered with textual configuration files.  You can generate your CDB files
  by running the CCS tconf utility on the application's respective TCF file.
  Alternatively, you can generate all of the DDK CDB files at once from the
  makefile in the DDK's top level directory.  See the product release notes for
  more information on running this makefile.  See the DSP/BIOS TextConf User's
  Guide (SPRU007) for more information on the tconf utility.

- Files in the library are compiled with "no optimization switch" turned on,
  and the same is specified in the project (pjt) files. If you plan to use this
  module in a project release, you should rebuild the library with optimization
  turned on.

- Each of the applications has a custom linker command file as part of the
  its project.  This linker command file links in the command file that is
  generated by the DSP/BIOS Configuration Tool and also explicitely links in
  the driver libraries.

Known Problems At Release
-------------------------
- None.

Q&A
---
Q1: How to run the sample test?
Q2: Where can I find the documentation for the UART drivers?
Q2: Where can I find the documentation for writing IOM drivers?

---
Q1: How to run the sample test?
A1: Here are the steps to run the sample test:
    1) Connect a serial cable from the targets UART to the PCs 
       communication port (com port).
    2) Run HyperTerminal a select the proper Com port.
    3) Set the Bits per second to 115200, Data bits to 8, Parity to None, 
       Stop bits to 1, and Flow control to None.
    4) Open CCS and load .out file from the Debug directory within the DDK tree.
    5) Run the application. You should see "Hello World" on the HyperTeminal
       window.
    6) Input at least 12 characters from the keyboard and watch them get echo back.

Q2: Where can I find the documentation for the UART drivers?
A2: The literature number is SPRU822, DSP/BIOS Hardware and Software UART 
    Device Drivers.

Q2: Where can I find the documentation for writing IOM drivers?
A2: The literature number is SPRU616, DSP/BIOS Device Driver Developer's Guide.