nuttx/configs/16z/ostest
2014-01-24 11:58:30 -06:00
..
.gitignore configs/16z: Add support for 16z board 2014-01-22 11:50:37 -06:00
defconfig configs/16z: Add support for 16z board 2014-01-22 11:50:37 -06:00
Make.defs configs/16z: Add support for 16z board 2014-01-22 11:50:37 -06:00
ostest.linkcmd 16z: Fix option bits; adjust system clock frequency 2014-01-23 12:06:57 -06:00
ostest.zfpproj configs/16z: Add support for 16z board 2014-01-22 11:50:37 -06:00
README.txt Add a patch to work around the bug in the ZDS-II 5.0.1 toolchain 2014-01-24 11:58:30 -06:00
setenv.sh Add a patch to work around the bug in the ZDS-II 5.0.1 toolchain 2014-01-24 11:58:30 -06:00

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.