sergiotarxz/nuttx-apps
sergiotarxz/nuttx-apps
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

apps/README.txt: Fix typos.

Browse Source
This commit is contained in:
Nathan Hartman 2019-08-02 12:36:22 -06:00 committed by Gregory Nutt
parent bf9a5180cd
commit da4c2461a6
2 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.txt
View File

@ -153,7 +153,7 @@ Q: Has anyone come up with a tidy way to build NuttX with board-
A: Here are three:
1) There is a make target called 'make export'. It will build
NuttX, then bundle all of the header files, libaries, startup
NuttX, then bundle all of the header files, libraries, startup
objects, and other build components into a .zip file. You
can can move that .zip file into any build environment you
want. You even build NuttX under a DOS CMD window.
@ -176,14 +176,14 @@ A: Here are three:
3) If you like the random collection of stuff in the apps/ directory
but just want to expand the existing components with your own,
external sub-directory then there is an easy way to that too:
You just create a sympolic link in the apps/ directory that
You just create a symbolic link in the apps/ directory that
redirects to your application sub-directory.
In order to be incorporated into the build, the directory that
you link under the apps/ directory should contain (1) a Makefile
that supports the clean and distclean targets (see other Makefiles
for examples), and (2) a tiny Make.defs file that simply adds the
custon build directories to the variable CONFIGURED_APPS like:
custom build directories to the variable CONFIGURED_APPS like:
CONFIGURED_APPS += my_directory1 my_directory2

16
modbus/README.txt
View File

@ -19,15 +19,15 @@ system. The mapping between freemodbus-v1.5.0 and the nuttx directories
is shown below:
--------------------------- ----------------------------------------------
freemodbus-v1.5.0 Nuttx
freemodbus-v1.5.0 NuttX
--------------------------- ----------------------------------------------
All top level .txt files Not included
demo/ Not included. This directory contains demo
and porting code for a variety of platforms.
The NuttX demo was ported from the LINUX
demo in this director and can be found at
demo in this directory and can be found at
apps/examples/modbus.
doc/ Note included. This directory contains Doxygen
doc/ Not included. This directory contains Doxygen
support files.
modbus/ Included in its entirety in various locations:
ascii apps/modbus/ascii
@ -36,7 +36,7 @@ is shown below:
mb.c apps/modbus/mb.c
rtu apps/modbus/rtu
tcp apps/modbus/tcp
tools/ Note included. This directory contain Doxygen
tools/ Not included. This directory contains Doxygen
tools.
--------------------------- ----------------------------------------------
@ -75,13 +75,13 @@ The NuttX-named configuration options that are available include:
vMBPortSerialDelay with the argument CONFIG_MB_ASCII_TIMEOUT_WAIT_BEFORE_SEND_MS
to allow for a delay before the serial transmitter is enabled. This is
required because some targets are so fast that there is no time between
receiving and transmitting the frame. If the master is to slow with
enabling its receiver then he will not receive the response correctly.
receiving and transmitting the frame. If the master is too slow with
enabling its receiver then it will not receive the response correctly.
CONFIG_MB_FUNC_HANDLERS_MAX - Maximum number of Modbus functions codes the
protocol stack should support. The maximum number of supported Modbus
functions must be greater than the sum of all enabled functions in this
file and custom function handlers. If set to small adding more functions
will fail.
file and custom function handlers. If set too small, adding more
functions will fail.
CONFIG_MB_FUNC_OTHER_REP_SLAVEID_BUF - Number of bytes which should be
allocated for the Report Slave ID command. This number limits the
maximum size of the additional segment in the report slave id function.