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	Remove the configs/ directory	2015-06-29 13:12:29 -06:00
defconfig	Squashed commit of the following:	2018-10-05 09:33:48 -06:00
nsh.zfpproj	Remove the configs/ directory	2015-06-29 13:12:29 -06:00
README.txt	Remove the configs/ directory	2015-06-29 13:12:29 -06:00

README.txt

README.txt
==========

Contents
--------

  o NSH Project
  o Loading and Executing Code
  o Console Output
  o STATUS

NSH Project
-----------

nsh.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:

    nsh.hex, nsh.map, nsh.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 nsh.zfpproj project
5. In the debug tab, connect to the debugger
6. In the debug tab, load code, reset, and go

Console Output
--------------

Interaction with NSH is via the serial console at 57600 8N1 baud.

STATUS
------

1. Note that you must apply the ZNEO patch if you are using ZDS-II 5.0.1.
   See the README.txt file in the parent directory for more information.
   This configuration does run correctly with the path applied.

2. I bet that this code, like ostest, will not run if started by a hardware
   reset.  It may only run when started via the debugger.