incubator-nuttx

History

Gregory Nutt d0254b1c79 Squashed commit of the following: libs/libc/stdio/lib_libvsprintf.c: Resolves the integer field width problem if Issue 35 for the cases of long and long long integer types. libs/libc/stdio/lib_libvsprintf.c: Resolves the integer field width problem if Issue 35 for the case of integer types. libs/libc/stdio: Remove CONFIG_NOPRINTF_FIELDWIDTH. That option does, indeed, make the printf family of functions much smaller. But it also adds a lot of complexity and makes the functions non-standard. Removing this might break some of the tinier platforms but it is the best thing to do for long term maintanance for for OpenGroup.org compliance.		2018-10-05 09:33:48 -06:00
..
.gitignore	…
README.txt	…
defconfig	Squashed commit of the following:	2018-10-05 09:33:48 -06:00
ostest.zfpproj	…

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