Mirrors_Framework/nuttx
1
0
Fork 0
mirror of https://github.com/apache/nuttx.git synced 2026-02-05 19:56:43 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Docs: Update links to old website and wiki

Browse Source 
Signed-off-by: Brennan Ashton <bashton@brennanashton.com>
This commit is contained in:
Brennan Ashton
2020-08-30 13:12:57 -07:00
committed by Matias N
parent 3ddb3dc00e
commit 4cb193d530
36 changed files with 210 additions and 231 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
Documentation/components/nsh/nsh.rst
View File

@@ -1,4 +1,5 @@
.. include:: /substitutions.rst
.. _nsh:
********
Overview

14
Documentation/components/nxwidgets.rst
View File

@@ -43,17 +43,11 @@ Note: Many of the fundamental classed in NxWidgets derive from the
Antony Dzeryn's "Woopsi" project: http://woopsi.org/ which also has a
BSD style license. See the COPYING file for details.
NXWidgets DOxygen Documentation
NXWidgets Doxygen Documentation
===============================
Release notes, DOxygen documentation, as well as downloads for the
latest NxWidgets releases are available online:
**NxWidgets-1.19**:
`Documentation <http://nuttx.org/nxwidgets_v1_19/html/index.html>`__,
`Release
notes <http://sourceforge.net/projects/nuttx/files/NxWidgets/NxWidgets-1.19/>`__,
and
`Downloads <http://sourceforge.net/projects/nuttx/files/NxWidgets/NxWidgets-1.19/>`__
.. todo::
NXWidgets supports building HTML documentation via Doxygen. We should
integrate this into the Sphinx documentation build.
Thanks go to Jose Pablo Carballo for contributing this!

43
Documentation/introduction/detailed_support.rst
View File

@@ -110,7 +110,7 @@ Moxa NP51x0
A port to the Moxa NP51x0 series of 2-port advanced
RS-232/422/485 serial device servers was contributed by Anton D.
Kachalov in NuttX-7.11. This port includes a NuttShell (NSH)
Kachalov in NuttX-7.11. This port includes :ref:`NSH <nsh>`
configuration with support for the Faraday FTMAC100 Ethernet MAC Driver.
@@ -174,9 +174,9 @@ There are ports to two Atmel SAMA5D3 boards:
configurations that run out of internal SRAM and extended
configurations that run out of the on-board NOR FLASH:
- A barebones NuttShell (`NSH <NuttShell.html>`__) configuration
- A barebones NuttShell (:ref:`NSH <nsh>`) configuration
that can be used as the basis for further application development.
- A full-loaded NuttShell (`NSH <NuttShell.html>`__) configuration
- A full-loaded NuttShell (:ref:`NSH <nsh>`) configuration
that demonstrates all of the SAMA5D3x features.
The following support was added in Nuttx 6.30:
@@ -398,7 +398,7 @@ that features the NUC120LE3AN MCU.
**STATUS**. Initial support for the NUC120 was released in NuttX-6.26.
This initial support is very minimal: There is a NuttShell
(`NSH <NuttShell.html>`__) configuration that might be the basis for an
(:ref:`NSH <nsh>`) configuration that might be the basis for an
application development. As of this writing, more device drivers are
needed to make this a more complete port. Refer to the NuttX board
`README <https://bitbucket.org/nuttx/nuttx/src/master/boards/arm/nuc1xx/nutiny-nuc120/README.txt>`__
@@ -511,8 +511,7 @@ TI/Stellaris LM3S6432S2E
This port uses Serial-to-Ethernet Reference
Design Kit (`RDK-S2E <http://www.ti.com/tool/rdk-s2e>`__) and has
similar support as for the other Stellaris family members. A
configuration is available for the NuttShell (NSH) (see the `NSH User
Guide <http://www.nuttx.org/Documentation/NuttShell.html>`__). The NSH
configuration is available for the NuttShell (NSH) (see :ref:`NSH <nsh>`). The NSH
configuration including networking support with a Telnet NSH console.
This port was contributed by Mike Smith.
@@ -691,7 +690,7 @@ family was added in NuttX-7.21. Support for the Nucleo-L152RE was added
in NuttX-7.28.
That initial STM32L-Discovery support included a configuration using the
NuttShell (`NSH <NuttShell.html>`__) that might be the basis for an
NuttShell (:ref:`NSH <nsh>`) that might be the basis for an
application development. A driver for the on-board segment LCD is
included as well as an option to drive the segment LCD from an NSH
"built-in" command. Refer to the STM32L-Discovery board
@@ -970,7 +969,7 @@ Three configurations are available:
with the STM32F107 part.
#. The configuration that was used to verify the Nuttx `high-priority,
nested interrupt
feature <http://www.nuttx.org/doku.php?id=wiki:nxinternal:highperfints>`__.
feature <https://cwiki.apache.org/confluence/display/NUTTX/High+Performance%2C+Zero+Latency+Interrupts>`__.
**STATUS:** Networking and touchscreen support are well test. But, at
present, neither USB nor LCD functionality have been verified. Refer to
@@ -1103,8 +1102,7 @@ boards.
That initial, 5.6, basic release included *timer* interrupts and a
*serial console* and was verified using the NuttX OS test
(``apps/examples/ostest``). Configurations available include include
a verified NuttShell (NSH) configuration (see the `NSH User
Guide <http://www.nuttx.org/Documentation/NuttShell.html>`__). The
a verified NuttShell (NSH) configuration (see :ref:`NSH <nsh>`). The
NSH configuration supports the Nucleus2G's microSD slot and
additional configurations are available to exercise the USB serial
and USB mass storage devices. However, due to some technical reasons,
@@ -1145,8 +1143,7 @@ boards.
file for further information.
Verified configurations are now available for the NuttShell with
networking and microSD support(NSH, see the `NSH User
Guide <http://www.nuttx.org/Documentation/NuttShell.html>`__), for
networking and microSD support(NSH, see :ref:`NSH <nsh>`), for
the NuttX network test, for the
`THTTPD <http://acme.com/software/thttpd>`__ webserver, for USB
serial deive and USB storage devices examples, and for the USB host
@@ -1570,8 +1567,7 @@ further information about this board.
- **NuttX-6.12** The basic port is complete and first appeared in
NuttX-6.12. The initial port passes the NuttX OS test and includes a
validated configuration for the NuttShell (NSH, see the `NSH User
Guide <http://www.nuttx.org/Documentation/NuttShell.html>`__) as well
validated configuration for the NuttShell (NSH, see :ref:`NSH <nsh>`) as well
as several other configurations.
- **NuttX-6.13-6.16** Additional drivers and configurations were added
in NuttX 6.13-6.16. Drivers include an Ethernet driver, ADC driver,
@@ -2177,7 +2173,7 @@ was contributed in NuttX-8.1 by Nathan Hartman.
the EK-TM4C123GXL was also included in that release but was not fully
tested. This basic board support included a configuration for the
NuttShell
`NSH <http://www.nuttx.org/Documentation/NuttShell.html>`__).
:ref:`NSH <nsh>`).
- **NuttX-7.2**. The fully verified port to the EK-TM4C123GXL was
provided in NuttX-7.2.
- **NuttX-7.7**. An I2C driver was added in NuttX-7.7.
@@ -2195,7 +2191,7 @@ LaunchPad `(EK-TM4C1294XL) <http://www.ti.com/tool/ek-tm4c1294xl>`__.
- Support for the EK-TM4C1294XL was contributed by Frank Sautter and
was released in NuttX 7.9. This basic board support included a
configuration for the NuttShell
`NSH <http://www.nuttx.org/Documentation/NuttShell.html>`__) and a
:ref:`NSH <nsh>`) and a
configuration for testing IPv6. See drivers for the `TI Tiva
TM4C129X <#titm4c129x>`__.
- FLASH and EEPROM drivers from Shirshak Sengupta were included in
@@ -2220,7 +2216,7 @@ Development Kit `(DK-TM4C129X) <http://www.ti.com/tool/dk-tm4c129x>`__.
Other Tiva/Stellaris drivers should port to the TM4C129X without
major difficulty.
- This board supports included two configurations for the NuttShell
(`NSH <http://www.nuttx.org/Documentation/NuttShell.html>`__). Both
(:ref:`NSH <nsh>`). Both
are networked enabled: One configured to support IPv4 and one
configured to supported IPv6. Instructions are included in the board
`README <https://bitbucket.org/nuttx/nuttx/src/master/boards/arm/tiva/dk-tm4c129x/README.txt>`__
@@ -2255,7 +2251,7 @@ board. This board features the ATSAM4LC4C MCU running at 48MHz with
**STATUS:** As of this writing, the basic port is code complete and a
fully verified configuration exists for the NuttShell
`NSH <http://www.nuttx.org/Documentation/NuttShell.html>`__). The first
:ref:`NSH <nsh>`). The first
fully functional SAM4L Xplained Pro port was released in NuttX-6.28.
Support for the SAM4L Xplained modules was added in NuttX-6.29:
@@ -2317,8 +2313,7 @@ in part by Mitko.
**Atmel SAM4E-EK**. Board support was added for the SAM4E-EK development
board in NuttX 7.1. A fully functional NuttShell (NSH) configuration is
available (see the `NSH User
Guide <http://www.nuttx.org/Documentation/NuttShell.html>`__). That NSH
available (see :ref:`NSH <nsh>`). That NSH
configuration includes networking support and support for an AT25 Serial
FLASH file system.
@@ -2343,8 +2338,7 @@ in part by Mitko.
**Atmel SAM4E-EK**. Board support was added for the SAM4E-EK development
board in NuttX 7.1. A fully functional NuttShell (NSH) configuration is
available (see the `NSH User
Guide <http://www.nuttx.org/Documentation/NuttShell.html>`__). That NSH
available (see :ref:`NSH <nsh>`). That NSH
configuration includes networking support and support for an AT25 Serial
FLASH file system.
@@ -2491,7 +2485,7 @@ STM32 F7 Driver Status:
peripherals are very similar to some members of the STM32 F4 and
additional drivers can easily be ported the F7 as discussed in this
Wiki page: `Porting Drivers to the STM32
F7 <http://www.nuttx.org/doku.php?id=wiki:howtos:port-drivers_stm32f7>`__
F7 <https://cwiki.apache.org/confluence/display/NUTTX/Porting+Drivers+to+the+STM32+F7>`__
- **NuttX-7.17**. David Sidrane contributed PWR, RTC, BBSRAM, and
DBGMCU support. Lok Tep contribed SPI, I2c, ADC, SDMMC, and USB
@@ -2757,8 +2751,7 @@ basic RTOS port has solidified:
- The port successfully passes the NuttX OS test
(apps/examples/ostest).
- A NuttShell (NSH) configuration is in place (see the `NSH User
Guide <http://www.nuttx.org/Documentation/NuttShell.html>`__).
- A NuttShell (NSH) configuration is in place (see :ref:`NSH <nsh>`).
Testing of that configuration has been postponed (because it got
bumped by the Olimex LPC1766-STK port). Current Status: I think I
have a hardware problem with my serial port setup. There is a good

4
Documentation/introduction/resources.rst
View File

@@ -9,9 +9,9 @@ Here's a list of Apache NuttX resources that you might find helpful:
* Apache NuttX
* `NuttX website <https://nuttx.apache.org>`_
* `Apache NuttX website <https://www.nuttx.org>`_
* `Apache NuttX website <https://apache.nuttx.org>`_
* `Apache NuttX online documentation <https://cwiki.apache.org/confluence/display/NUTTX/Nuttx>`_
* `Apache NuttX mailing list <https://nuttx.incubator.apache.org/community/>`_ – a very active mailing list, the place to get help with your application or any questions you have about NuttX.
* `Apache NuttX mailing list <https://nuttx.apache.org/community/>`_ – a very active mailing list, the place to get help with your application or any questions you have about NuttX.
* `Apache NuttX YouTube channel <https://www.youtube.com/channel/UC0QciIlcUnjJkL5yJJBmluw/videos>`_ – Alan Carvalho de Assis's YouTube channel on NuttX. It's a source of a lot of great practical information.
* `Apache NuttX Coding Standard <https://cwiki.apache.org/confluence/display/NUTTX/Coding+Standard>`_ — How code should look when you submit new files or modify existing ones.
* `Apache NuttX Code Contribution Guidlines <https://cwiki.apache.org/confluence/display/NUTTX/Code+Contribution+Workflow+--+Brennan+Ashton>`_ — The full workflow to follow for submitting code with all the details.

2
Documentation/reference/os/smp.rst
View File

@@ -22,7 +22,7 @@ bus or a crossbar."
For a technical description of the NuttX implementation of SMP,
see the NuttX `SMP Wiki
Page <http://www.nuttx.org/doku.php?id=wiki:nxinternal:smp>`__.
Page <https://cwiki.apache.org/confluence/display/NUTTX/SMP>`__.
.. c:function:: spinlock_t up_testset(volatile FAR spinlock_t *lock)

6
Documentation/reference/user/01_task_control.rst
View File

@@ -48,7 +48,7 @@ Non-standard task control interfaces inspired by VxWorks interfaces:
Non-standard extensions to VxWorks-like interfaces to support POSIX
`Cancellation
Points <http://www.nuttx.org/doku.php?id=wiki:nxinternal:cancellation-points>`__.
Points <https://cwiki.apache.org/confluence/display/NUTTX/Cancellation+Points>`__.
- :c:func:`task_setcancelstate`
- :c:func:`task_setcanceltype`
@@ -168,7 +168,7 @@ Functions
This function obeys the semantics of pthread cancellation: task deletion
is deferred if cancellation is disabled or if deferred cancellation is
supported (with `Cancellation
Points <http://www.nuttx.org/doku.php?id=wiki:nxinternal:cancellation-points>`__
Points <https://cwiki.apache.org/confluence/display/NUTTX/Cancellation+Points>`__
enabled).
:param pid: The task ID of the task to delete. An ID of zero signifies
@@ -297,7 +297,7 @@ Functions
.. c:function:: void task_testcancel(void)
Creates a `Cancellation
Point <http://www.nuttx.org/doku.php?id=wiki:nxinternal:cancellation-points>`__
Point <https://cwiki.apache.org/confluence/display/NUTTX/Cancellation+Points>`__
in the calling task. The ``task_testcancel()`` function has no effect if
cancellability is disabled.

2
Documentation/reference/user/05_counting_semaphore.rst
View File

@@ -132,7 +132,7 @@ the case of pthread mutexes,
with ``PTHREAD_PRIO_NONE``.
This is discussed in much more detail on this `Wiki
page <http://www.nuttx.org/doku.php?id=wiki:howtos:signalling-semaphores>`__.
page <https://cwiki.apache.org/confluence/display/NUTTX/Signaling+Semaphores+and+Priority+Inheritance>`__.
**POSIX semaphore interfaces:**

4
Documentation/reference/user/08_pthread.rst
View File

@@ -448,7 +448,7 @@ No support for the following pthread interfaces is provided by NuttX:
When cancellability is deferred, all cancellations are held pending in
the target thread until the thread changes the cancellability type or a
`Cancellation
Point <http://www.nuttx.org/doku.php?id=wiki:nxinternal:cancellation-points>`__
Point <https://cwiki.apache.org/confluence/display/NUTTX/Cancellation+Points>`__
function such as ```pthread_testcancel()`` <#pthreadtestcancel>`__ is
entered.
@@ -528,7 +528,7 @@ No support for the following pthread interfaces is provided by NuttX:
.. c:function:: void pthread_testcancel(void);
The ``pthread_testcancel()`` function creates a `Cancellation
Point <http://www.nuttx.org/doku.php?id=wiki:nxinternal:cancellation-points>`__
Point <https://cwiki.apache.org/confluence/display/NUTTX/Cancellation+Points>`__
in the calling thread. The ``pthread_testcancel()`` function has no
effect if cancellability is disabled.

8
README.md
View File

@@ -963,7 +963,7 @@ This make target will bring up NuttX configuration menus.
**WARNING**: Never do `make menuconfig` on a configuration that has
not been converted to use the kconfig-frontends tools! This will
damage your configuration (see
<http://www.nuttx.org/doku.php?id=wiki:howtos:convertconfig>).
<https://cwiki.apache.org/confluence/display/NUTTX/Converting+Legacy+Configurations+to+Use+kconfig-mconf>).
How do we tell a new configuration from an old one? See "Incompatibilities
with Older Configurations" below.
@@ -1278,7 +1278,7 @@ configuration will probably not be functional.
> Q: How can I convert a older, manual configuration into a new,
> kconfig-frontends toolchain.
>
> A: Refer to <http://www.nuttx.org/doku.php?id=wiki:howtos:convertconfig>
> A: Refer to <https://cwiki.apache.org/confluence/display/NUTTX/Converting+Legacy+Configurations+to+Use+kconfig-mconf>
**WARNING**
@@ -1304,7 +1304,7 @@ file, regenerating the `.config` and making it usable for NuttX builds.
Never do `make oldconfig` (OR `make menuconfig`) on a configuration that
has not been converted to use the kconfig-frontends tools! This will
damage your configuration (see
<http://www.nuttx.org/doku.php?id=wiki:howtos:convertconfig>).
<https://cwiki.apache.org/confluence/display/NUTTX/Converting+Legacy+Configurations+to+Use+kconfig-mconf>).
## NuttX Configuration Tool under DOS
@@ -1876,7 +1876,7 @@ into your Web browser:
Documentation/index.html
NuttX documentation is also available online at <http://www.nuttx.org>.
NuttX documentation is also available online at <https://apache.nuttx.org>.
Below is a guide to the available README files in the NuttX source tree:

260
ReleaseNotes
View File

File diff suppressed because it is too large Load Diff

8
TODO
View File

@@ -77,7 +77,7 @@ o Task/Scheduler (sched/)
Title: ON-DEMAND PAGING INCOMPLETE
Description: On-demand paging has recently been incorporated into the RTOS.
The design of this feature is described here:
http://www.nuttx.org/NuttXDemandPaging.html.
https://nuttx.apache.org/docs/latest/components/paging.html.
As of this writing, the basic feature implementation is
complete and much of the logic has been verified. The test
harness for the feature exists only for the NXP LPC3131 (see
@@ -862,7 +862,7 @@ o pthreads (sched/pthreads libs/libc/pthread)
Excerpted from my post in a Linked-In discussion:
"I started to implement this HLS/"PCP" semaphore in an RTOS that I
work with (http://www.nuttx.org) and I discovered after doing the
work with (https://apache.nuttx.org) and I discovered after doing the
analysis and basic code framework that a complete solution for the
case of a counting semaphore is still quite complex -- essentially
as complex as is priority inheritance.
@@ -1195,7 +1195,7 @@ o C++ Support
processes).]
NuttX does not have processes, but it does have "task groups".
See http://www.nuttx.org/doku.php?id=wiki:nxinternal:tasksnthreads.
See https://cwiki.apache.org/confluence/display/NUTTX/Tasks+vs.+Threads+FAQ.
A task group is the task plus all of the pthreads created by
the task via pthread_create(). Resources like FILE streams
are shared within a task group. Task groups are like a poor
@@ -2504,7 +2504,7 @@ o Linux/Cygwin simulation (arch/sim)
Priority: Low, unless there is a need for developing a higher fidelity simulation
I have been thinking about how to implement simulated interrupts in
the simulation. I think a solution would work like this:
http://www.nuttx.org/doku.php?id=wiki:nxinternal:simulator
https://cwiki.apache.org/confluence/display/NUTTX/NuttX+Simulation
Title: ROUND-ROBIN SCHEDULING IN THE SIMULATOR
Description: Since the simulation is not pre-emptible, you can't use round-robin

3
arch/Kconfig
View File

@@ -537,7 +537,8 @@ menuconfig PAGING
depends on ARCH_USE_MMU && !ARCH_ROMPGTABLE
---help---
If set =y in your configation file, this setting will enable the on-demand
paging feature as described in http://www.nuttx.org/NuttXDemandPaging.html.
paging feature as described in
https://nuttx.apache.org/docs/latest/components/paging.html.
if PAGING

2
arch/arm/src/armv7-m/Kconfig
View File

@@ -58,7 +58,7 @@ config ARMV7M_USEBASEPRI
Though, these hardfaults are properly handled by the RTOS, the
hardfaults can confuse some debuggers. With the BASEPRI
register, these hardfaults, will be avoided. For more details see
http://www.nuttx.org/doku.php?id=wiki:nxinternal:svcall
https://cwiki.apache.org/confluence/display/NUTTX/ARMv7-M+Hardfaults%2C+SVCALL%2C+and+Debuggers
WARNING: If CONFIG_ARCH_HIPRI_INTERRUPT is selected, then you
MUST select CONFIG_ARMV7M_USEBASEPRI. The Kconfig dependencies

2
arch/arm/src/armv8-m/Kconfig
View File

@@ -57,7 +57,7 @@ config ARMV8M_USEBASEPRI
Though, these hardfaults are properly handled by the RTOS, the
hardfaults can confuse some debuggers. With the BASEPRI
register, these hardfaults, will be avoided. For more details see
http://www.nuttx.org/doku.php?id=wiki:nxinternal:svcall
https://cwiki.apache.org/confluence/display/NUTTX/ARMv7-M+Hardfaults%2C+SVCALL%2C+and+Debuggers
WARNING: If CONFIG_ARCH_HIPRI_INTERRUPT is selected, then you
MUST select CONFIG_ARMV8M_USEBASEPRI. The Kconfig dependencies

2
arch/arm/src/kinetis/kinetis_lowputc.c
View File

@@ -692,7 +692,7 @@ void kinetis_uartconfigure(uintptr_t uart_base, uint32_t baud,
* The fractional divider, BRFA, is a 5 bit fractional value that is
* logically added to the SBR:
*
* UART baud rate = clock / (16 <EFBFBD> (SBR + BRFD))
* UART baud rate = clock / (16 * (SBR + BRFD))
*
* The BRFA the remainder. This will be a non-negative value since the SBR
* was calculated by truncation.

4
arch/arm/src/lpc17xx_40xx/hardware/lpc17_40_i2s.h
View File

@@ -114,8 +114,8 @@
#define I2S_DAI_WSHALFPER_SHIFT (6) /* Bits 6-14: Word select half period minus 1 */
#define I2S_DAI_WSHALFPER_MASK (0x01ff << I2S_DAI_WSHALFPER_SHIFT)
/* Bits 15-31: Reserved */
/* Transmit FIFO: 8 <EFBFBD> 32-bit transmit FIFO */
/* Receive FIFO: 8 <EFBFBD> 32-bit receive FIFO */
/* Transmit FIFO: 8 - 32-bit transmit FIFO */
/* Receive FIFO: 8 - 32-bit receive FIFO */
/* Status Feedback Register */

2
arch/arm/src/lpc43xx/lpc43_serial.c
View File

@@ -812,7 +812,7 @@ static int up_interrupt(int irq, void *context, void *arg)
* RS-485/EIA-485 Auto Address Detection (AAD) mode -- NOT supported
*
* In this mode, the receiver will compare any address byte received
* (parity = <EFBFBD>1<EFBFBD>) to the 8-bit value programmed into the RS485ADRMATCH
* (parity = 1) to the 8-bit value programmed into the RS485ADRMATCH
* register. When a matching address character is detected it will be
* pushed onto the RXFIFO along with the parity bit, and the receiver
* will be automatically enabled.

24
boards/README.txt
View File

@@ -160,10 +160,6 @@ any time using that tool or, more appropriately, the wrapper script at
nuttx/tools/mkconfigvars.sh. That script will generate the file
nuttx/Documentation/NuttXConfigVariables.html.
The version of NuttXConfigVariables.html for the last released version of
NuttX can also be found online at:
http://nuttx.org/Documentation/NuttXConfigVariables.html.
Supported Boards
^^^^^^^^^^^^^^^^
@@ -228,8 +224,8 @@ boards/hc/m9s12/demo9s12ne64
is code complete but has not yet been verified.
boards/arm/tiva/dk-tm4c129x
This is the port of NuttX to the Tiva® DK-TM4C129x Connected Development Kit. The
Tiva® DK-TM4C129x features the TM4C129XNCZAD MCU.
This is the port of NuttX to the Tiva DK-TM4C129x Connected Development Kit. The
Tiva DK-TM4C129x features the TM4C129XNCZAD MCU.
boards/arm/lpc31xx/ea3131
Embedded Artists EA3131 Development board. This board is based on the
@@ -338,8 +334,8 @@ boards/arm/tiva/lm3s8962-ek
boards/arm/tiva/lm4f120-launchpad
This is the port of NuttX to the Stellaris LM4F120 LaunchPad. The
Stellaris® LM4F120 LaunchPad Evaluation Board is a low-cost evaluation
platform for ARM® Cortex™-M4F-based microcontrollers from Texas
Stellaris LM4F120 LaunchPad Evaluation Board is a low-cost evaluation
platform for ARM Cortex-M4F-based microcontrollers from Texas
Instruments.
boards/arm/lpc17xx_40xx/lpcxpresso-lpc1768
@@ -826,15 +822,15 @@ boards/arm/kl/teensy-lc
based bootloader.
boards/arm/tiva/tm4c123g-launchpad
This is the port of NuttX to the Tiva® TM4C123G LaunchPad. The
Tiva® TM4C123G LaunchPad Evaluation Board is a low-cost evaluation
platform for ARM® Cortex™-M4F-based microcontrollers from Texas
This is the port of NuttX to the Tiva TM4C123G LaunchPad. The
Tiva TM4C123G LaunchPad Evaluation Board is a low-cost evaluation
platform for ARM Cortex-M4F-based microcontrollers from Texas
Instruments.
boards/arm/tiva/tm4c1294-launchpad
This is the port of NuttX to the Tiva® TM4C1294 LaunchPad. The
Tiva® TM4C123G LaunchPad Evaluation Board is a low-cost evaluation
platform for ARM® Cortex™-M4F-based microcontrollers from Texas
This is the port of NuttX to the Tiva TM4C1294 LaunchPad. The
Tiva TM4C123G LaunchPad Evaluation Board is a low-cost evaluation
platform for ARM Cortex-M4F-based microcontrollers from Texas
Instruments.
boards/arm/tmx570/tms570ls31x-usb-kit

1
boards/arm/cxd56xx/spresense/configs/rndis/defconfig
View File

@@ -100,7 +100,6 @@ CONFIG_NSH_DISABLE_TELNETD=y
CONFIG_NSH_FILE_APPS=y
CONFIG_NSH_READLINE=y
CONFIG_NSH_TELNETD_CLIENTSTACKSIZE=3072
CONFIG_NSH_WGET_USERAGENT="NuttX/7.2x.x (; http://www.nuttx.org/)"
CONFIG_NXPLAYER_HTTP_STREAMING_SUPPORT=y
CONFIG_NXPLAYER_MAINTHREAD_STACKSIZE=3072
CONFIG_PATH_INITIAL="/mnt/sd0/bin"

1
boards/arm/cxd56xx/spresense/configs/wifi/defconfig
View File

@@ -103,7 +103,6 @@ CONFIG_NSH_DISABLE_IFUPDOWN=y
CONFIG_NSH_DISABLE_NSLOOKUP=y
CONFIG_NSH_FILE_APPS=y
CONFIG_NSH_READLINE=y
CONFIG_NSH_WGET_USERAGENT="NuttX/7.2x.x (; http://www.nuttx.org/)"
CONFIG_NXPLAYER_HTTP_STREAMING_SUPPORT=y
CONFIG_NXPLAYER_MAINTHREAD_STACKSIZE=3072
CONFIG_PATH_INITIAL="/mnt/sd0/bin"

1
boards/arm/lc823450/lc823450-xgevk/configs/bt/defconfig
View File

@@ -124,7 +124,6 @@ CONFIG_NSH_FILEIOSIZE=512
CONFIG_NSH_LINELEN=128
CONFIG_NSH_MAXARGUMENTS=10
CONFIG_NSH_READLINE=y
CONFIG_NSH_WGET_USERAGENT="NuttX/7.2x.x (; http://www.nuttx.org/)"
CONFIG_NX=y
CONFIG_NXFONT_MONO5X8=y
CONFIG_NXPLAYER_DEFAULT_MEDIADIR="/mnt/sd1"

1
boards/arm/lc823450/lc823450-xgevk/configs/krndis/defconfig
View File

@@ -128,7 +128,6 @@ CONFIG_NSH_FILE_APPS=y
CONFIG_NSH_LINELEN=128
CONFIG_NSH_MAXARGUMENTS=10
CONFIG_NSH_READLINE=y
CONFIG_NSH_WGET_USERAGENT="NuttX/7.2x.x (; http://www.nuttx.org/)"
CONFIG_NUTTX_USERSPACE=0x05020000
CONFIG_NX=y
CONFIG_NXFONT_MONO5X8=y

1
boards/arm/lc823450/lc823450-xgevk/configs/rndis/defconfig
View File

@@ -129,7 +129,6 @@ CONFIG_NSH_LINELEN=128
CONFIG_NSH_MAXARGUMENTS=10
CONFIG_NSH_READLINE=y
CONFIG_NSH_TELNETD_CLIENTSTACKSIZE=3072
CONFIG_NSH_WGET_USERAGENT="NuttX/7.2x.x (; http://www.nuttx.org/)"
CONFIG_NX=y
CONFIG_NXFONT_MONO5X8=y
CONFIG_NXPLAYER_DEFAULT_MEDIADIR="/mnt/sd1"

10
boards/arm/lpc17xx_40xx/olimex-lpc1766stk/README.txt
View File

@@ -135,11 +135,11 @@ Olimex LPC1766-STK development board
LDS176 controller but it is 100% compatible with the Philips PCF8833).
So how do you tell which controller you have? Some message boards have
suggested that the LCD display be disassembled and the controller chip
measured with a digital caliper – well that’s getting a bit extreme.
measured with a digital caliper well that's getting a bit extreme.
"Here’s what I know. The Olimex boards have both display controllers
possible; if the LCD has a GE-12 sticker on it, it’s a Philips PCF8833.
If it has a GE-8 sticker, it’s an Epson controller. The older Sparkfun
"Here's what I know. The Olimex boards have both display controllers
possible; if the LCD has a GE-12 sticker on it, it's a Philips PCF8833.
If it has a GE-8 sticker, it's an Epson controller. The older Sparkfun
6100 displays were Epson, their web site indicates that the newer ones
are an Epson clone. Sparkfun software examples sometimes refer to the
Philips controller so the whole issue has become a bit murky. The
@@ -927,7 +927,7 @@ Configuration Sub-Directories
2015-06-02. Do to issues introduced by recent versions of GCC, NXFLAT
is not often usable.
See http://www.nuttx.org/doku.php?id=wiki:vfs:nxflat#toolchain_compatibility_problem
See https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=139630111
usbserial:
This configuration directory exercises the USB serial class

1
boards/arm/lpc17xx_40xx/u-blox-c027/configs/nsh/defconfig
View File

@@ -88,7 +88,6 @@ CONFIG_NSH_LINELEN=64
CONFIG_NSH_READLINE=y
CONFIG_NSH_STRERROR=y
CONFIG_NSH_TELNET_LOGIN=y
CONFIG_NSH_WGET_USERAGENT="NuttX/7.xx.x (; http://www.nuttx.org/)"
CONFIG_PREALLOC_TIMERS=4
CONFIG_RAM_SIZE=32768
CONFIG_RAM_START=0x10000000

2
boards/arm/lpc31xx/ea3131/README.txt
View File

@@ -584,7 +584,7 @@ Configuration Sub-Directories
pgnsh
This is the same configuration as nsh, but with On-Demand
paging enabled. See http://www.nuttx.org/Documentation/NuttXDemandPaging.html.
paging enabled. See https://nuttx.apache.org/docs/latest/components/paging.html.
This configuration is an experiment for the purposes of test
and debug. At present, this does not produce functioning,
usable system

2
boards/arm/sam34/flipnclick-sam3x/README.txt
View File

@@ -441,8 +441,6 @@ Loading Code
https://www.olimex.com/Products/ARM/JTAG/ARM-JTAG-20-10/ . I have been
loading code and debugging with no problems using JTAG.
You can find photos my setup here: http://www.nuttx.org/doku.php?id=wiki:howtos:flipnclick-sam3x
Flip&Click SAM3X-specific Configuration Options
===============================================

2
boards/arm/sama5/sama5d2-xult/README.txt
View File

@@ -817,7 +817,7 @@ Configurations
4. This configuration supports logging of debug output to a circular
buffer in RAM. This feature is discussed fully in this Wiki page:
http://nuttx.org/doku.php?id=wiki:howtos:syslog . Relevant
https://cwiki.apache.org/confluence/display/NUTTX/SYSLOG . Relevant
configuration settings are summarized below:
File System:

2
boards/arm/sama5/sama5d2-xult/include/board_498mhz.h
View File

@@ -97,7 +97,7 @@
#define BOARD_ADC_PRESCAL (7)
#define BOARD_TSD_STARTUP (40) /* 40 nanoseconds */
#define BOARD_TSD_TRACKTIM (2000) /* Min 1<EFBFBD>s at 8MHz */
#define BOARD_TSD_TRACKTIM (2000) /* Min 1us at 8MHz */
#define BOARD_TSD_DEBOUNCE (10000000) /* 10 milliseconds (units nanoseconds) */
/* Resulting frequencies */

2
boards/arm/sama5/sama5d2-xult/src/sam_ethernet.c
View File

@@ -166,7 +166,7 @@ void weak_function sam_netinitialize(void)
* (MICREL KSZ9021/31) operating at 10/100/1000 Mbps.
* The board supports RGMII interface mode.
* The Ethernet interface consists of 4 pairs of low voltage differential
* pair signals designated from GRX<EFBFBD> and GTx<EFBFBD> plus control signals for
* pair signals designated from GRX and GTx plus control signals for
* link activity indicators. These signals can be used to connect to a
* 10/100/1000 BaseT RJ45 connector integrated on the main board.
*

10
boards/arm/sama5/sama5d4-ek/README.txt
View File

@@ -3032,9 +3032,9 @@ TM7000 LCD/Touchscreen
- 7 inch LCD at 800x480 18-bit RGB resolution and white backlight
- Projected Capacitive Multi-Touch Controller based on the Atmel
MXT768E maXTouch™ IC
- 4 Capacitive “Navigation” Keys available via an Atmel AT42QT1070
QTouch™ Button Sensor IC
MXT768E maXTouch IC
- 4 Capacitive Navigation Keys available via an Atmel AT42QT1070
QTouch Button Sensor IC
- 200 bytes of non-volatile serial EEPROM
NOTE: It appears that my TM7000 differs slightly from the version
@@ -3873,7 +3873,7 @@ Configurations
task_create() as it is used in the ELF test, but the code
seems to survive it. See:
http://www.nuttx.org/doku.php?id=wiki:nxinternal:memconfigs#task_create
https://cwiki.apache.org/confluence/display/NUTTX/Memory+Configurations
2014-8-29: System call interface verified.
2014-9-16: Reverified after fixing changes for the knsh configuration
@@ -4243,7 +4243,7 @@ Configurations
4. This configuration supports logging of debug output to a circular
buffer in RAM. This feature is discussed fully in this Wiki page:
http://nuttx.org/doku.php?id=wiki:howtos:syslog . Relevant
https://cwiki.apache.org/confluence/display/NUTTX/SYSLOG . Relevant
configuration settings are summarized below:
Device Drivers:

2
boards/arm/samv7/samv71-xult/README.txt
View File

@@ -1873,7 +1873,7 @@ Configuration sub-directories
6. This configuration supports logging of debug output to a circular
buffer in RAM. This feature is discussed fully in this Wiki page:
http://nuttx.org/doku.php?id=wiki:howtos:syslog . Relevant
https://cwiki.apache.org/confluence/display/NUTTX/SYSLOG . Relevant
configuration settings are summarized below:
Device Drivers:

2
boards/arm/stm32/clicker2-stm32/README.txt
View File

@@ -401,7 +401,7 @@ Configurations
4. This configuration does NOT have USART3 output enabled. This
configuration supports logging of debug output to a circular
buffer in RAM. This feature is discussed fully in this Wiki page:
http://nuttx.org/doku.php?id=wiki:howtos:syslog . Relevant
https://cwiki.apache.org/confluence/display/NUTTX/SYSLOG . Relevant
configuration settings are summarized below:
Device Drivers:

6
boards/arm/stm32/stm32f4discovery/README.txt
View File

@@ -1760,7 +1760,7 @@ Configuration Sub-directories
not be possible.
b) Develop a strategy to manage CCM memory and DMA memory. Look
at this discussion on the NuttX Wiki:
http://www.nuttx.org/doku.php?id=wiki:howtos:stm32-ccm-alloc
https://cwiki.apache.org/confluence/display/NUTTX/STM32+CCM+Allocator
To put the CCM memory back into the heap you would need to change
the following in the NuttX configuration:
@@ -2142,8 +2142,8 @@ Configuration Sub-directories
There are some issues with the presentation... some tuning of the
configuration could fix that. Lower resolution displays are also more
subject to the "fat, flat line bug" that I need to fix someday. See
http://www.nuttx.org/doku.php?id=wiki:graphics:nxgraphics for a description
of the fat, flat line bug.
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=139629474
for a description of the fat, flat line bug.
pm:
--

2
boards/arm/stm32f7/stm32f746g-disco/README.txt
View File

@@ -140,7 +140,7 @@ Porting STM32 F4 Drivers
and, as a result, we need to exercise much more care to maintain cache
coherency. There is a Wiki page discussing the issues of porting
drivers from the stm32/ to the stm32f7/ directories here:
http://www.nuttx.org/doku.php?id=wiki:howtos:port-drivers_stm32f7
https://cwiki.apache.org/confluence/display/NUTTX/Porting+Drivers+to+the+STM32+F7
FPU
===

2
boards/z16/z16f/z16f2800100zcog/README.txt
View File

@@ -186,7 +186,7 @@ nsh
---
nsh:
This configuration directory will built the NuttShell (NSH). See
the NSH user manual in the documents directory (or online at nuttx.org).
the NSH user manual in the documents directory (or online at apache.nuttx.org).
See also the README.txt file in the nsh sub-directory for information
about using ZDS-II.