2008-01-25 23:28:46 +01:00
|
|
|
README.txt
|
|
|
|
^^^^^^^^^^
|
|
|
|
|
2014-01-01 17:29:44 +01:00
|
|
|
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:
|
2014-01-01 19:40:18 +01:00
|
|
|
|
2014-01-01 17:29:44 +01:00
|
|
|
nuttx.hex, nuttx.map, nuttx.lod
|
2014-01-01 19:40:18 +01:00
|
|
|
|
2008-01-25 23:28:46 +01:00
|
|
|
to this directory as:
|
2014-01-01 19:40:18 +01:00
|
|
|
|
2014-01-01 17:29:44 +01:00
|
|
|
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.
|
2014-01-24 18:58:30 +01:00
|
|
|
|
|
|
|
STATUS
|
|
|
|
------
|
|
|
|
|
2020-02-22 19:31:14 +01:00
|
|
|
This example works fine when started from ZDS-II. But I have seen problems
|
2014-01-24 18:58:30 +01:00
|
|
|
when starting from a hardware reset.
|