summaryrefslogtreecommitdiff
path: root/nuttx/configs/16z/ostest/README.txt
diff options
context:
space:
mode:
Diffstat (limited to 'nuttx/configs/16z/ostest/README.txt')
-rw-r--r--nuttx/configs/16z/ostest/README.txt39
1 files changed, 0 insertions, 39 deletions
diff --git a/nuttx/configs/16z/ostest/README.txt b/nuttx/configs/16z/ostest/README.txt
deleted file mode 100644
index 1116dabc1..000000000
--- a/nuttx/configs/16z/ostest/README.txt
+++ /dev/null
@@ -1,39 +0,0 @@
-README.txt
-^^^^^^^^^^
-
-OSTEST Project
---------------
-
-ostest.zfpproj is a simple ZDS II - ZNEO 5.0.1 project that will allow you
- to use the ZDS-II debugger. Before using, copy the following files from
- the toplevel directory:
-
- nuttx.hex, nuttx.map, nuttx.lod
-
- to this directory as:
-
- ostest.hex, ostest.map, ostest.lod
-
-Loading and Executing Code
---------------------------
-
-1. Copy the files to this directory as described above
-2. Connect the ZiLOG XTools USB debugger.
-3. Install the USB driver from the ZDS-II device_drivers directory
-4. Start ZDS-II and load the ostest.zfpproj project
-5. In the debug tab, connect to the debugger
-6. In the debug tab, load code, reset, and go
-
-Hmmm... it appears that the code does not run if started by a hardware reset.
-It runs only when started via the debugger. What is up with that?
-
-Console Output
---------------
-
-OS test results will be provided on the serial console at 57600 8N1 baud.
-
-STATUS
-------
-
-1. This configuration does not run correctly. There is currently a problem
- with the SRAM accesses.