nuttx/configs/z16f2800100zcog/ostest
2016-03-30 17:53:19 -06:00
..
.gitignore Clone svn:ignore directory atributed to .gitignore files 2013-04-04 14:27:29 -06:00
defconfig Remove all references to CONFIG_SYSTEM_SDCARD 2016-03-30 17:53:19 -06:00
Make.defs Change use of mknulldeps.sh to mkwindeps.sh 2016-01-09 14:13:44 -06:00
ostest.linkcmd 16Z: Some early bring-up fixes 2014-01-22 13:46:42 -06:00
ostest.zfpproj Make sure that the Z16F build still builds and runs 2014-01-01 10:29:44 -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
------

This exemple works fine when started from ZDS-II.  But I have seen problems
when starting from a hardware reset.