nuttx

History

Xiang Xiao e1d3627bb1 sched/wdog: Change the default value of MAX_WDOGPARMS from 4 to 2 since the maximum number of argument pass to wd_start in the whole code base is 2 and change CONFIG_MAX_WDOGPARMS in some defconfig from 1 to 2 oherwise pthread_condclockwait will fail Signed-off-by: Xiang Xiao <xiaoxiang@xiaomi.com> Change-Id: Ib6cb28b8c0722058849e7be916e164513431d21c		2020-08-06 10:36:22 -06:00
..
defconfig	sched/wdog: Change the default value of MAX_WDOGPARMS from 4 to 2	2020-08-06 10:36:22 -06:00
ostest.zfpproj	Ensure all source code end with one and only one newline	2020-02-08 07:25:56 -06:00
README.txt	Run codespell -w against all files	2020-02-22 14:45:07 -06:00

README.txt

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 example works fine when started from ZDS-II.  But I have seen problems
when starting from a hardware reset.