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

Fix some typos

Browse Source
This commit is contained in:
Gregory Nutt 2014-10-15 10:57:04 -06:00
parent 81f013ddb8
commit 0e3e2e3029
4 changed files with 39 additions and 37 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
Documentation/NuttX.html
View File

@ -399,7 +399,7 @@
<td><br></td> <td><br></td>
<td> <td>
<p> <p>
<li>Built-in, per-thread CPU load measurments.</li> <li>Built-in, per-thread CPU load measurements.</li>
</p> </p>
</tr> </tr>
@ -616,7 +616,7 @@
<td><br></td> <td><br></td>
<td> <td>
<p> <p>
<li>Cryptiographic subsystem</li> <li>Cryptographic subsystem</li>
</p> </p>
</td> </td>
</tr> </tr>
@ -1971,7 +1971,7 @@
<p> <p>
<b>Development Environments:</b> <b>Development Environments:</b>
1) Linux with native Linux GNU toolchain, 2) Cygwin/MSYS with Cygwin GNU toolchain, 3) Cygwin/MSYS with Windows native toolchain, or 4) Native Windows. 1) Linux with native Linux GNU toolchain, 2) Cygwin/MSYS with Cygwin GNU toolchain, 3) Cygwin/MSYS with Windows native toolchain, or 4) Native Windows.
All testing has been perfomed with the CodeSourcery toolchain (GCC version 4.7.3) in the Cygwin environment under Windows. All testing has been performed with the CodeSourcery toolchain (GCC version 4.7.3) in the Cygwin environment under Windows.
</p> </p>
</td> </td>
</tr> </tr>
@ -2482,7 +2482,7 @@ nsh>
The basic STM32 port was released in NuttX version 0.4.12. The basic port includes boot-up The basic STM32 port was released in NuttX version 0.4.12. The basic port includes boot-up
logic, interrupt driven serial console, and system timer interrupts. logic, interrupt driven serial console, and system timer interrupts.
The 0.4.13 release added support for SPI, serial FLASH, and USB device.; The 0.4.13 release added support for SPI, serial FLASH, and USB device.;
The 4.14 release added support for buttons and SDIO-based MMC/SD and verifed DMA support. The 4.14 release added support for buttons and SDIO-based MMC/SD and verified DMA support.
Verified configurations are available for the NuttShell (NSH) example, Verified configurations are available for the NuttShell (NSH) example,
the USB serial device class, and the USB mass storage device class example. the USB serial device class, and the USB mass storage device class example.
</p> </p>
@ -2766,7 +2766,7 @@ nsh>
The NSH configuration supports the Nucleus2G's microSD slot and additional configurations The NSH configuration supports the Nucleus2G's microSD slot and additional configurations
are available to exercise the USB serial and USB mass storage devices. are available to exercise the USB serial and USB mass storage devices.
However, due to some technical reasons, neither the SPI nor the USB device drivers are fully verified. However, due to some technical reasons, neither the SPI nor the USB device drivers are fully verified.
(Although they have since been verfiied on other platforms; this needs to be revisited on the Nucleus2G). (Although they have since been verified on other platforms; this needs to be revisited on the Nucleus2G).
</p> </p>
</li> </li>
<li> <li>
@ -2868,7 +2868,7 @@ nsh>
Initial Open1788 support appeared in NuttX-6.26 with the first verified configurations in NuttX-6.27. Initial Open1788 support appeared in NuttX-6.26 with the first verified configurations in NuttX-6.27.
In NuttX-6.27 there is a working basic port with OS verification, Nuttshell (<a href="http://www.nuttx.org/Documentation/NuttShell.html">NSH</a>) configurations, and a graphics test configuration. In NuttX-6.27 there is a working basic port with OS verification, Nuttshell (<a href="http://www.nuttx.org/Documentation/NuttShell.html">NSH</a>) configurations, and a graphics test configuration.
SDRAM and GPDMA are working. SDRAM and GPDMA are working.
The NSH configuration includes verfied support for a DMA-based SD card interface. The NSH configuration includes verified support for a DMA-based SD card interface.
The frame-buffer LCD driver is functional and uses the SDRAM for frame-buffer memory. The frame-buffer LCD driver is functional and uses the SDRAM for frame-buffer memory.
A touchscreen interface has been developed but there appears to be a hardware issue with the WaveShare implementation of the XPT2046 touchscreen controller. A touchscreen interface has been developed but there appears to be a hardware issue with the WaveShare implementation of the XPT2046 touchscreen controller.
Refer to the NuttX board <a href="http://sourceforge.net/p/nuttx/git/ci/master/tree/nuttx/configs/open1788/README.txt">README</a> file for further information. Refer to the NuttX board <a href="http://sourceforge.net/p/nuttx/git/ci/master/tree/nuttx/configs/open1788/README.txt">README</a> file for further information.
@ -2951,7 +2951,7 @@ nsh>
<p> <p>
<b>STATUS:</b> <b>STATUS:</b>
The basic port for the STM32F3-Discover was first released in NuttX-6.26. The basic port for the STM32F3-Discover was first released in NuttX-6.26.
Many of the drivers previously released for the STM32 F1, Value Line, and F2 and F4 may be usable on this plaform as well. Many of the drivers previously released for the STM32 F1, Value Line, and F2 and F4 may be usable on this platform as well.
New drivers will be required for ADC and I2C which are very different on this platform. New drivers will be required for ADC and I2C which are very different on this platform.
Refer to the NuttX board <a href="http://sourceforge.net/p/nuttx/git/ci/master/tree/nuttx/configs/stm32f3discovery/README.txt">README</a> file for further information. Refer to the NuttX board <a href="http://sourceforge.net/p/nuttx/git/ci/master/tree/nuttx/configs/stm32f3discovery/README.txt">README</a> file for further information.
</p> </p>
@ -3529,7 +3529,7 @@ Mem: 29232 5920 23312 23312
</p> </p>
<p> <p>
An SPI driver and a USB device driver exist for the AT90USB as well An SPI driver and a USB device driver exist for the AT90USB as well
as a USB mass storage configureation. However, this configuration is not as a USB mass storage configuration. However, this configuration is not
fully debugged as of the NuttX-6.5 release. fully debugged as of the NuttX-6.5 release.
Refer to the NuttX board <a href="http://sourceforge.net/p/nuttx/git/ci/master/tree/nuttx/configs/teensy/README.txt">README</a> file for further information. Refer to the NuttX board <a href="http://sourceforge.net/p/nuttx/git/ci/master/tree/nuttx/configs/teensy/README.txt">README</a> file for further information.
</p> </p>
@ -4321,7 +4321,7 @@ avr, m68k, m68hc11, m68hc12, m9s12, blackfin, m32c, h8, and SuperH ports.</block
dependencies are retained in files called <code>Make.deps</code> throughout the system. dependencies are retained in files called <code>Make.deps</code> throughout the system.
For compilers other than GCC, there is no support for making dependencies in this way. For compilers other than GCC, there is no support for making dependencies in this way.
For Windows native GCC compilers, the generated dependencies are windows paths and not For Windows native GCC compilers, the generated dependencies are windows paths and not
directly usable in the Cygwin make. By default, dependencies are surpressed for these directly usable in the Cygwin make. By default, dependencies are suppressed for these
compilers as well. compilers as well.
</li> </li>
<p><small> <p><small>
@ -4362,7 +4362,7 @@ avr, m68k, m68hc11, m68hc12, m9s12, blackfin, m32c, h8, and SuperH ports.</block
</ol> </ol>
<p> <p>
This capability first appeared in NuttX-6.24 and should still be considered a work in progress because: (1) it has not been verfied on all targets and tools, and (2) still lacks some of the creature-comforts of the more mature environments. This capability first appeared in NuttX-6.24 and should still be considered a work in progress because: (1) it has not been verfied on all targets and tools, and (2) still lacks some of the creature-comforts of the more mature environments.
The windows native build logic initiatiated if <code>CONFIG_WINDOWS_NATIVE=y</code> is defined in the NuttX configuration file: The windows native build logic initiated if <code>CONFIG_WINDOWS_NATIVE=y</code> is defined in the NuttX configuration file:
</p> </p>
<p> <p>
At present, this build environment also requires: At present, this build environment also requires:
@ -4385,7 +4385,7 @@ avr, m68k, m68hc11, m68hc12, m9s12, blackfin, m32c, h8, and SuperH ports.</block
<b>MinGW-GCC</b>. <b>MinGW-GCC</b>.
MinGW-GCC is used to compiler the C tools in the <code>nuttx/tools</code> directory that are neede by the build. MinGW-GCC is used to compiler the C tools in the <code>nuttx/tools</code> directory that are neede by the build.
MinGW-GCC can be downloaded from http://www.mingw.org/. MinGW-GCC can be downloaded from http://www.mingw.org/.
If you are using GNUWin32, then it is recommendedthe you not install the optional MSYS components as there may be conflicts. If you are using GNUWin32, then it is recommended that you not install the optional MSYS components as there may be conflicts.
</li> </li>
</td> </td>
</tr> </tr>

3
Kconfig
View File

@ -753,7 +753,7 @@ menu "Audio Support"
source audio/Kconfig source audio/Kconfig
endmenu endmenu
menu "Binary Formats" menu "Binary Loader"
source binfmt/Kconfig source binfmt/Kconfig
endmenu endmenu
@ -765,4 +765,3 @@ endmenu
menu "Application Configuration" menu "Application Configuration"
source "$APPSDIR/Kconfig" source "$APPSDIR/Kconfig"
endmenu endmenu

10
README.txt
View File

@ -285,7 +285,7 @@ Refreshing Configurations
If you configuration is out of date, you will be prompted to resolve the If you configuration is out of date, you will be prompted to resolve the
issues detected by the configuration tool. Doing this can save you a lot issues detected by the configuration tool. Doing this can save you a lot
of problems done the road due to a bad configuration. The NuttX of problems done the road due to a bad configuration. The NuttX
onfiguration is discussed in the following paragraph. configuration is discussed in the following paragraph.
NuttX Configuration Tool NuttX Configuration Tool
------------------------ ------------------------
@ -499,7 +499,7 @@ NuttX Buildroot Toolchain
NOTE: For Cortex-M3/4, there are OABI and EABI versions of the buildroot NOTE: For Cortex-M3/4, there are OABI and EABI versions of the buildroot
toolchains. If you are using the older OABI toolchain the prefix for toolchains. If you are using the older OABI toolchain the prefix for
the tools will be arm-nuttx-elf-; for the EABI toolchin the prefix will the tools will be arm-nuttx-elf-; for the EABI toolchain the prefix will
be arm-nuttx-eabi-. If you are using the older OABI toolchain with be arm-nuttx-eabi-. If you are using the older OABI toolchain with
an ARM Cortex-M3/4, you will need to set CONFIG_ARMV7M_OABI_TOOLCHAIN an ARM Cortex-M3/4, you will need to set CONFIG_ARMV7M_OABI_TOOLCHAIN
in the .config file in order to pick the right tool prefix. in the .config file in order to pick the right tool prefix.
@ -857,14 +857,14 @@ General Pre-built Toolchain Issues
you will get the stdio.h from the incompatible, foreign C library and you will get the stdio.h from the incompatible, foreign C library and
not the nuttx stdio.h (at nuttx/include/stdio.h) that you wanted. not the nuttx stdio.h (at nuttx/include/stdio.h) that you wanted.
This can cause really confusion in the buildds and you must always be This can cause really confusion in the builds and you must always be
sure the -nostdinc is included in the CFLAGS. That will assure that sure the -nostdinc is included in the CFLAGS. That will assure that
you take the include files only from you take the include files only from
5. Libraries. What was said above header files applies to libraries. 5. Libraries. What was said above header files applies to libraries.
You do not want to include code from the libraries of any foreign You do not want to include code from the libraries of any foreign
C libraries built into your toolchain. If this happens you will get C libraries built into your toolchain. If this happens you will get
perplexing errors about undefined sysmbols. To avoid these errors, perplexing errors about undefined symbols. To avoid these errors,
you will need to add -nostdlib to your CFLAGS flags to assure that you will need to add -nostdlib to your CFLAGS flags to assure that
you only take code from the NuttX libraries. you only take code from the NuttX libraries.
@ -889,7 +889,7 @@ General Pre-built Toolchain Issues
of this in the misc/buildroot/configs directory. However, it of this in the misc/buildroot/configs directory. However, it
is possible that there could be interoperability issues with is possible that there could be interoperability issues with
your toolchain since they will be using different versions of your toolchain since they will be using different versions of
binutials and possibly different ABIs. binutils and possibly different ABIs.
DOCUMENTATION DOCUMENTATION
^^^^^^^^^^^^^ ^^^^^^^^^^^^^

41
TODO
View File

@ -133,13 +133,13 @@ o Task/Scheduler (sched/)
Title: execv() AND vfork() Title: execv() AND vfork()
Description: There is a problem when vfork() calls execv() (or execl()) to Description: There is a problem when vfork() calls execv() (or execl()) to
start a new appliction: When the parent thread calls vfork() start a new application: When the parent thread calls vfork()
it receives and gets the pid of the vforked task, and *not* it receives and gets the pid of the vforked task, and *not*
the pid of the desired execv'ed application. the pid of the desired execv'ed application.
The same tasking arrangement is used by the standard function The same tasking arrangement is used by the standard function
posix_spawn(). However, posix_spawn uses the non-standard, internal posix_spawn(). However, posix_spawn uses the non-standard, internal
NuttX interface task_reparent() to replace the childs parent task NuttX interface task_reparent() to replace the child's parent task
with the caller of posix_spawn(). That cannot be done with vfork() with the caller of posix_spawn(). That cannot be done with vfork()
because we don't know what vfork() is going to do. because we don't know what vfork() is going to do.
@ -311,7 +311,7 @@ o pthreads (sched/)
would have to know the priority of every semaphore held by would have to know the priority of every semaphore held by
every thread. every thread.
"Providing the HLS capability on a simple phread mutex would not "Providing the HLS capability on a simple pthread mutex would not
be such quite such a complex job if you allow only one mutex per be such quite such a complex job if you allow only one mutex per
thread. However, the more general case seems almost as complex thread. However, the more general case seems almost as complex
as priority inheritance. I decided that the implementation does as priority inheritance. I decided that the implementation does
@ -390,7 +390,7 @@ o Kernel/Protected Build
Description: There are a few syscalls that operate very often in user space. Description: There are a few syscalls that operate very often in user space.
Since syscalls are (relatively) time consuming this could be Since syscalls are (relatively) time consuming this could be
a performance issue. Here is some numbers that I collected a performance issue. Here is some numbers that I collected
in an application that was doing mostly printf outout: in an application that was doing mostly printf output:
sem_post - 18% of syscalls sem_post - 18% of syscalls
sem_wait - 18% of syscalls sem_wait - 18% of syscalls
@ -490,7 +490,7 @@ o C++ Support
this will provide the model for all solutions. Basically, if this will provide the model for all solutions. Basically, if
CONFIG_HAVE_CXXINITIALIZE=y is defined in the configuration, then CONFIG_HAVE_CXXINITIALIZE=y is defined in the configuration, then
board-specific code must provide the interface up_cxxinitialize(). board-specific code must provide the interface up_cxxinitialize().
up_cxxinitialize() is called from aplication logic to initialize up_cxxinitialize() is called from application logic to initialize
all static class instances. This TODO item probably has to stay all static class instances. This TODO item probably has to stay
open because this solution is only available on STM32 F4. open because this solution is only available on STM32 F4.
Status: Open Status: Open
@ -580,8 +580,8 @@ o C++ Support
uClibc++ and NuttX would need some extensions. I am thinking uClibc++ and NuttX would need some extensions. I am thinking
along the lines of the following: along the lines of the following:
1) There is a per-task group storage are withing the RTOS (see 1) There is a per-task group storage are within the RTOS (see
include/nuttx/sched.h). If we add some new, nonstandard APIs include/nuttx/sched.h). If we add some new, non-standard APIs
then uClibc++ could get access to per-task group storage (in then uClibc++ could get access to per-task group storage (in
the spirit of pthread_getspecific() which gives you access to the spirit of pthread_getspecific() which gives you access to
per-thread storage). per-thread storage).
@ -1032,7 +1032,7 @@ o Libraries (libc/)
time error, and some, such as sdcc, do. AFAIK, C implementations time error, and some, such as sdcc, do. AFAIK, C implementations
are not even required to support infinity. In C99 the macro isinf() are not even required to support infinity. In C99 the macro isinf()
could replace the first use of division by zero. Unfortunately, the could replace the first use of division by zero. Unfortunately, the
macro INFINITY from math.h probably can't replce the second division macro INFINITY from math.h probably can't replace the second division
by zero, since it will result in a compile-time diagnostic, if the by zero, since it will result in a compile-time diagnostic, if the
implementation does not support infinity." implementation does not support infinity."
Status: Open Status: Open
@ -1106,7 +1106,7 @@ o File system / Generic drivers (fs/, drivers/)
Title: POLLHUP SUPPORT Title: POLLHUP SUPPORT
Description: All drivers that support the poll method should also report Description: All drivers that support the poll method should also report
POLLHUP event when the driver is closedd. POLLHUP event when the driver is closed.
Status: Open Status: Open
Priority: Medium-Low Priority: Medium-Low
@ -1128,7 +1128,7 @@ o File system / Generic drivers (fs/, drivers/)
On an array of file structures and the other an array of On an array of file structures and the other an array of
socket structures. There really should be one array that socket structures. There really should be one array that
is a union of file and socket descriptors. Then socket and is a union of file and socket descriptors. Then socket and
file decriptors could lie in the same range. file descriptors could lie in the same range.
Status: Open Status: Open
Priority: Low Priority: Low
@ -1294,7 +1294,7 @@ o Linux/Cywgin simulation (arch/sim)
Title: SIMULATOR HAS NO INTERRUPTS (NON-PREMPTIBLE) Title: SIMULATOR HAS NO INTERRUPTS (NON-PREMPTIBLE)
Description: The current simulator implementation is has no interrupts and, hence, Description: The current simulator implementation is has no interrupts and, hence,
is non-preemptible. Also, without simulated interrutps, there can is non-preemptible. Also, without simulated interrupt, there can
be no high-fidelity simulated device drivers. be no high-fidelity simulated device drivers.
Currently, all timing and serial input is simulated in the IDLE loop: Currently, all timing and serial input is simulated in the IDLE loop:
@ -1581,6 +1581,8 @@ o ARM/LPC31xx (arch/arm/src/lpc31xx/)
o ARM/LPC43x (arch/arm/src/lpc43xx/) o ARM/LPC43x (arch/arm/src/lpc43xx/)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
See comments in configs/lpc4330-xplorer/README.txt
o ARM/STR71x (arch/arm/src/str71x/) o ARM/STR71x (arch/arm/src/str71x/)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@ -1706,7 +1708,7 @@ o AVR (arch/avr)
into the more abundant FLASH memory, but this would require modification into the more abundant FLASH memory, but this would require modification
to the printf logic to access the strings from program memory. to the printf logic to access the strings from program memory.
Status: Open Status: Open
Priority: Low. The AVR is probably not the architecuture that you want to use Priority: Low. The AVR is probably not the architecture that you want to use
for extensive string operations. for extensive string operations.
Title: SPI AND USB DRIVERS UNTESTED Title: SPI AND USB DRIVERS UNTESTED
@ -1774,7 +1776,7 @@ o MIPS/PIC32(arch/mips)
Title: PIC32 USB MASS STORAGE DEVICE FAILS TO RE-CONNECT Title: PIC32 USB MASS STORAGE DEVICE FAILS TO RE-CONNECT
Description: Found using configuration configs/pic32mx7mmb/nsh. Description: Found using configuration configs/pic32mx7mmb/nsh.
In this configuratin, the NSH 'msconn' command will connect the In this configuration, the NSH 'msconn' command will connect the
mass storage device to the host; the 'msdis' command will mass storage device to the host; the 'msdis' command will
disconnect the device. The first 'msconn' works perfectly. disconnect the device. The first 'msconn' works perfectly.
However, when attempting to re-connect, the second 'msconn' However, when attempting to re-connect, the second 'msconn'
@ -1863,7 +1865,7 @@ o Renesas M16C/26 (arch/sh/src/m16c)
Priority: Low Priority: Low
Title: UNIMPLEMENTED M16C DRIVERS Title: UNIMPLEMENTED M16C DRIVERS
Description: Should implement SPI, I2C, Virual EEPROM, FLASH, RTC drivers Description: Should implement SPI, I2C, Virtual EEPROM, FLASH, RTC drivers
Status: Open Status: Open
Priority: Medium Priority: Medium
@ -1874,7 +1876,7 @@ o z80/z8/ez80/z180 (arch/z80)
Description: The SDCC version the same problems with integer overflow during Description: The SDCC version the same problems with integer overflow during
compilation for certain 8-bit platform. At typical cause is code like compilation for certain 8-bit platform. At typical cause is code like
usleep(500*1000) which exceeds the range of a 16-bit integer. usleep(500*1000) which exceeds the range of a 16-bit integer.
Status: These have probably been fixed but have not yet been verified on thes Status: These have probably been fixed but have not yet been verified on these
affected platforms. affected platforms.
Priority: Low for now Priority: Low for now
@ -1935,7 +1937,7 @@ o z80/z8/ez80/z180 (arch/z80)
rule removes .asm files. This works because there are no .asm rule removes .asm files. This works because there are no .asm
files except in sub-directories that are provided from 'make clean' -- files except in sub-directories that are provided from 'make clean' --
except for XTRS: It has a .asm file in its src/ directory that except for XTRS: It has a .asm file in its src/ directory that
gets removed every time clean is performd. gets removed every time clean is performed.
Status: Open Status: Open
Priority: High if you happen to be working with XTRS. Priority: High if you happen to be working with XTRS.
@ -2100,6 +2102,7 @@ o mc68hc1x (arch/hc)
Priority: Medium/Low Priority: Medium/Low
o Network Utilities (apps/netutils/) o Network Utilities (apps/netutils/)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Title: PPP PORT Title: PPP PORT
Description: Port PPP support from http://contiki.cvs.sourceforge.net/contiki/contiki-2.x/backyard/core/net/ppp/ Description: Port PPP support from http://contiki.cvs.sourceforge.net/contiki/contiki-2.x/backyard/core/net/ppp/
@ -2115,7 +2118,7 @@ o Network Utilities (apps/netutils/)
Title: THE ARP ISSUES AGAIN Title: THE ARP ISSUES AGAIN
Description: The first GET received by THTTPD is not responded to. Refreshing the page Description: The first GET received by THTTPD is not responded to. Refreshing the page
from the browser solves the problem and THTTPD works fine after thatg. I from the browser solves the problem and THTTPD works fine after that. I
believe that this is the duplicate of another bug: "Outgoing believe that this is the duplicate of another bug: "Outgoing
[uIP] packets are dropped and overwritten by ARP packets if the [uIP] packets are dropped and overwritten by ARP packets if the
destination IP has not been mapped to a MAC." destination IP has not been mapped to a MAC."
@ -2154,7 +2157,7 @@ o System libraries apps/system (apps/system)
Title: READLINE IMPLEMENTATION Title: READLINE IMPLEMENTATION
Description: readline implementation does not use C-buffered I/O, but rather Description: readline implementation does not use C-buffered I/O, but rather
talks to serial driver directly via read(). It includes VT-100 talks to serial driver directly via read(). It includes VT-100
specific editting commands. A more generic readline() should be specific editing commands. A more generic readline() should be
implemented using termios' tcsetattr() to put the serial driver implemented using termios' tcsetattr() to put the serial driver
into a "raw" mode. into a "raw" mode.
Status: Open Status: Open
@ -2185,7 +2188,7 @@ o Other Applications & Tests (apps/examples/)
leveraged for more general purposes, it would be a problem. leveraged for more general purposes, it would be a problem.
Update: see examples/nxtext for some improved font cache handling. Update: see examples/nxtext for some improved font cache handling.
Status: Open Status: Open
Priority: Low. This is not really a problem becauses examples/nx works Priority: Low. This is not really a problem because examples/nx works
fine with its bogus font caching. fine with its bogus font caching.
Title: EXAMPLES/NXTEXT ARTIFACTS Title: EXAMPLES/NXTEXT ARTIFACTS