- There is a good example of how to do this in the NSH simulation configuration at configs/sim/nsh. The ROMFS support files are provided at configs/sim/include and the README.txt file at the location provides detailed information about creating and modifying the ROMFS file system.
+ There is a good example of how to do this in the NSH simulation configuration at boards/sim/nsh. The ROMFS support files are provided at boards/sim/include and the README.txt file at the location provides detailed information about creating and modifying the ROMFS file system.
diff --git a/Documentation/NuttX.html b/Documentation/NuttX.html
index 417c28c3a6..738a32fe2e 100644
--- a/Documentation/NuttX.html
+++ b/Documentation/NuttX.html
@@ -1874,7 +1874,7 @@
STATUS:
Does not support interrupts but is otherwise fully functional.
- Refer to the NuttX README file for further information.
+ Refer to the NuttX README file for further information.
@@ -1899,7 +1899,7 @@
STATUS:
This port is complete, verified, and included in the initial NuttX release.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -1926,7 +1926,7 @@
timer interrupts, serial console, USB driver, and SPI-based MMC/SD card
support. A verified NuttShell (NSH)
configuration is also available.
- Refer to the NuttX board README files for the mcu123.com and for the ZPA213X/4XPA boards for further information.
+ Refer to the NuttX board README files for the mcu123.com and for the ZPA213X/4XPA boards for further information.
Development Environments:
@@ -1961,7 +1961,7 @@
The port is complete and verified.
As of NuttX 5.3, the port included only basic timer interrupts and serial console support.
In NuttX 7.1, Lizhuoyi contributed additional I2C and SPI drivers.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
Development Environments: (Same as for the NXP LPC214x).
@@ -1994,7 +1994,7 @@
SD cards).
An SPI-based ENC28J60 Ethernet driver for add-on hardware is available and
but has not been fully verified on the Olimex board (due to issues powering the ENC28J60 add-on board).
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
Development Environments:
@@ -2026,7 +2026,7 @@
STATUS:
This port has stalled due to development tool issues.
Coding is complete on the basic port (timer, serial console, SPI).
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
NOTE: This port has been obsoleted.
@@ -2059,7 +2059,7 @@
The basic port (timer interrupts, serial ports, network, framebuffer, etc.) is complete.
All implemented features have been verified with the exception of the USB device-side
driver; that implementation is complete but untested.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -2095,7 +2095,7 @@
However, as of this writing, I have not had the opportunity to verify this new feature.
- Refer to the Embedded Artists EA3131 board README file for further information.
+ Refer to the Embedded Artists EA3131 board README file for further information.
@@ -2111,7 +2111,7 @@
NOTE: That driver should work on the EA3131 as well. However, the EA3131 uses a PCA9532 PWM part to controller the port power so the it would not quite be a simple drop-in.
- Refer to the Olimex LPC-H3131 board README file for further information.
+ Refer to the Olimex LPC-H3131 board README file for further information.
@@ -2139,7 +2139,7 @@
At this point, verification of the EA3152 port has been overcome by events and
may never happen.
However, the port is available for anyone who may want to use it.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -2176,7 +2176,7 @@
Raspberry Pi Zero.
This support was provided for the Raspberry Pi Zero which is based on the BCM2835.
Basic logic is in place but the port is incomplete and completely untested as of the NuttX-7.23 released.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
Obsoleted:: Support for the Raspberry Pi Zero was never completed.
@@ -2355,7 +2355,7 @@
NuttX-7.4 added support for the on-board WM8904 CODEC chip and for Tickless operation.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -2376,7 +2376,7 @@
The SAMA5D3 Xplained board does not have NOR FLASH and, as a consequence NuttX must boot into SDRAM with the help of U-Boot.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -2407,7 +2407,7 @@
The TM7000 LCDC with the maXTouch multi-touch controller are also fully support in a special NxWM configuration for that larger display.
Support for a graphics media player is included (although there were issues with the WM8904 audio CODEC on my board).
An SRAM bootloader was also included.
- Refer to the NuttX board README file for current status.
+ Refer to the NuttX board README file for current status.
@@ -2450,7 +2450,7 @@
This port was developed on the v1 board, but the others may be compatible:
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
STATUS.
@@ -2496,7 +2496,7 @@
- Refer to the Beaglebone Black board README file for further, up-to-date information.
+ Refer to the Beaglebone Black board README file for further, up-to-date information.
@@ -2521,7 +2521,7 @@
Sabre-6Quad.
This is a port to the NXP/Freescale Sabre-6Quad board.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
STATUS:
@@ -2531,7 +2531,7 @@
Basic support of NuttX running in SMP mode on the i.MX6Q was also accomplished in NuttX-7.16.
- However, there are still known issues with SMP support on this platform as described in the README file for the board.
+ However, there are still known issues with SMP support on this platform as described in the README file for the board.
@@ -2555,14 +2555,14 @@
STATUS.
My porting efforts were stalled due to tool-related issues.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
However, my understanding is that other people have successfully completed the port and submitted changes to the NuttX repository.
Toolchain:
The TMS570 is a big-endian ARM platform and requires a big-endian ARM toolchain.
All testing has been performed using a big-endian NuttX buildroot toolchain.
- Instructions for building this toolchain are included in the board README file.
+ Instructions for building this toolchain are included in the board README file.
@@ -2579,7 +2579,7 @@
STATUS.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
Toolchain:
@@ -2609,7 +2609,7 @@
This initial support is very minimal:
There is a NuttShell (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 file for further information.
+ Refer to the NuttX board README file for further information.
Memory Usage.
@@ -2673,7 +2673,7 @@ nsh>
As of NuttX-6.28 more device driver development would be needed to make this a complete port, particularly to support USB OTG.
A TSI and a SPI driver were added in NuttX-6.29.
Alan contributed a PWM driver in NuttX-6.32.
- Refer to the Freedom KL25Z board README file for further information.
+ Refer to the Freedom KL25Z board README file for further information.
@@ -2687,7 +2687,7 @@ nsh>
STATUS.
This is the work of Michael Hope.
Verified, initial support for the Teensy-LC first appeared in NuttX-7.10.
- Refer to the Teensy-LC board README file for further information.
+ Refer to the Teensy-LC board README file for further information.
@@ -2711,7 +2711,7 @@ nsh>
This work was contributed in NuttX 7.8 by Derek B. Noonburg.
The board support is very similar to the Freedom-KL25Z.
It was decided to support this a a separate board, however, due to some small board-level differences.
- Refer to the Freedom KL26Z board README file for further information.
+ Refer to the Freedom KL26Z board README file for further information.
@@ -2734,7 +2734,7 @@ nsh>
The initial SAMD20 Xplained Pro release (NuttX 7.1) included a functional NuttShell (NSH) configuration.
An SPI driver was also included to support the OLED1 and I/O1 modules.
That SPI driver, however, was not completely verified due to higher priority tasks that came up (I hope to get back to this later).
- Refer to the SAMD20 Explained Pro board README file for further information.
+ Refer to the SAMD20 Explained Pro board README file for further information.
The fully verified SPI driver appeared in the NuttX-7.22 release.
@@ -2760,7 +2760,7 @@ nsh>
Initial support for the SAML21 Xplained Pro was release in the NuttX 7.10.
This initial support included a basic configuration for the NuttShell (NSH)
(see the NSH User Guide).
- Refer to the SAML21 Explained Pro board README file for further information.
+ Refer to the SAML21 Explained Pro board README file for further information.
The fully verified SPI driver appeared in the NuttX-7.22 release along with an I2C and USB device driver.
@@ -2785,7 +2785,7 @@ nsh>
STATUS:
The first released version was provided in NuttX 7.10.
- Refer to the board README.txt file for further information.
+ Refer to the board README.txt file for further information.
Obsoleted:
@@ -2833,7 +2833,7 @@ nsh>
STATUS:
This port was was released in NuttX 6.14.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -2857,7 +2857,7 @@ nsh>
The current port includes timer, serial console, Ethernet, SSI, and microSD support.
There are working configurations to run the NuttShell
(NSH), the NuttX networking test, and the uIP web server.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -2897,7 +2897,7 @@ nsh>
NOTE: As it is configured now, you MUST have a network connected.
Otherwise, the NSH prompt will not come up because the Ethernet
driver is waiting for the network to come up.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -2923,7 +2923,7 @@ nsh>
STATUS:
This port was released in NuttX 5.10.
Features are the same as with the Eagle-100 LM3S6918 described above.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -2953,7 +2953,7 @@ nsh>
Header file support was contributed by Tiago Maluta for this part.
Jose Pablo Rojas V. is used those header file changes to port NuttX to the TI/Stellaris EKK-LM3S9B96.
That port was available in the NuttX-6.20 release.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -3010,7 +3010,7 @@ nsh>
DMA and USART-based SPI supported are included, but not fully tested.
- Refer to the EFM32 Gecko Starter Kit README.txt file for further information.
+ Refer to the EFM32 Gecko Starter Kit README.txt file for further information.
@@ -3034,7 +3034,7 @@ nsh>
The board suppport is complete but untested because of tool-related issues. An OpenOCD compatible, SWD debugger would be required to make further progress in testing.
- Refer to the Olimex EFM32G880F120-STK README.txt for further information.
+ Refer to the Olimex EFM32G880F120-STK README.txt for further information.
@@ -3144,7 +3144,7 @@ nsh>
That initial STM32L-Discovery support included a configuration using the NuttShell (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 README file for further information.
+ Refer to the STM32L-Discovery board README file for further information.
Memory Usage.
@@ -3297,7 +3297,7 @@ nsh>
STM32VL-Discovery.
In NuttX-6.33, support for the STMicro STM32VL-Discovery board was contributed by Alan Carvalho de Assis.
The STM32VL-Discovery board features an STM32F100RB MCU.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -3354,7 +3354,7 @@ nsh>
The basic STM32F103C8 port was released in NuttX version 6.28.
This work was contributed by Laurent Latil.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -3379,21 +3379,21 @@ nsh>
STM3210E-EVAL.
A port for the STMicro STM3210E-EVAL development board that
features the STM32F103ZET6 MCU.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
HY-Mini STM32v board.
This board is based on the STM32F103VCT chip. Port contributed by Laurent Latil.
- Refer to the NuttX board README file.
+ Refer to the NuttX board README file.
The M3 Wildfire development board (STM32F103VET6), version 2.
See http://firestm32.taobao.com (the current board is version 3).
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -3401,7 +3401,7 @@ nsh>
LeafLab's Maple and Maple Mini boards.
These boards are based on the STM32F103RBT6 chip for the standard version and on the STM32F103CBT6 for the mini version.
See the LeafLabs web site for hardware information;
- see the NuttX board README file for further information about the NuttX port.
+ see the NuttX board README file for further information about the NuttX port.
@@ -3539,7 +3539,7 @@ nsh>
(1) Basic Cortex-M3 port,
(2) Ethernet,
(3) On-board LEDs.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -3566,7 +3566,7 @@ nsh>
STATUS:
Networking and touchscreen support are well test.
But, at present, neither USB nor LCD functionality have been verified.
- Refer to the Viewtool STM32F103/F107 README file for further information.
+ Refer to the Viewtool STM32F103/F107 README file for further information.
@@ -3601,7 +3601,7 @@ nsh>
STATUS:
- In addition to the above-mention WiFI support, the Photon board support includes buttons, LEDS, IWDG, USB OTG HS, and procfs support. Configurations available for nsh, usbnsh, and wlan configurations. See the Photon README file for additional information.
+ In addition to the above-mention WiFI support, the Photon board support includes buttons, LEDS, IWDG, USB OTG HS, and procfs support. Configurations available for nsh, usbnsh, and wlan configurations. See the Photon README file for additional information.
@@ -3631,7 +3631,7 @@ nsh>
STATUS:
The peripherals of the STM32 F2 family are compatible with the STM32 F4 family.
See discussion of the STM3240G-EVAL board below for further information.
- Refer also to the NuttX board README file for further information.
+ Refer also to the NuttX board README file for further information.
Support for both the IAR and uVision GCC IDEs added for the STM3220G-EVAL board in NuttX 7.16.
@@ -3669,7 +3669,7 @@ nsh>
Subsequent NuttX releases will extend this port and add support for the SDIO-based SD cards and
USB device.
- Refer to the NuttX board README file for further information about this port.
+ Refer to the NuttX board README file for further information about this port.
@@ -3708,7 +3708,7 @@ nsh>
STATUS:
As of this writing, the basic Arduino Due port is code complete and a fully verified configuration exists for the NuttShell NSH).
The first fully functional Arduino Due port was released in NuttX-6.29.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
Support for the Flip&Click SAM3X was added in NuttX-7.24.
@@ -3783,7 +3783,7 @@ nsh>
-
The first functional release for the NXP LPC1768/Nucleus2G occured with NuttX 5.7 with
Some additional enhancements through NuttX-5.9.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -3801,7 +3801,7 @@ nsh>
Support for the Nucleus2G board was terminated on 2016-04-12.
There has not been any activity with the commercial board in a few years and it no longer appears to be available from the 2g-eng.com website.
Since the board is commercial and no longer publically available, it no longer qualifies for inclusion in the open source repositories.
- A snapshot of the code is still available in the Obsoleted repository and can easily be reconstitued if needed.
+ A snapshot of the code is still available in the Obsoleted repository and can easily be reconstitued if needed.
-
@@ -3809,7 +3809,7 @@ nsh>
-
Support for the mbed board was contributed by Dave Marples and released in NuttX-5.11.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -3833,7 +3833,7 @@ nsh>
The NuttX-5.17 released added support for low-speed USB devices, interrupt endpoints, and a USB host HID keyboard class driver.
-
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -3852,7 +3852,7 @@ nsh>
An fully verified board configuration is included in NuttX-6.2.
The Code Red toolchain is supported under either Linux or Windows.
Verified configurations include DHCPD, the NuttShell (NSH), NuttX graphis (NX), THTTPD, and USB mass storage device.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
-
@@ -3863,7 +3863,7 @@ nsh>
The initial release was included NuttX-6.26.
The Nuttx Buildroot toolchain is used by default.
Verifed configurations include the "Hello, World!" example application and a THTTPD demonstration.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
-
@@ -3871,7 +3871,7 @@ nsh>
This board configuration was contributed and made available in NuttX-6.20.
As contributed board support, I am unsure of what all has been verfied and what has not.
- See the Microment website Lincoln60 board and the NuttX board README file for further information about the Lincoln board.
+ See the Microment website Lincoln60 board and the NuttX board README file for further information about the Lincoln board.
-
@@ -3879,7 +3879,7 @@ nsh>
This board configuration was contributed by Vladimir Komendantskiy and made available in NuttX-7.15.
This is a variant of the LPCXpresso LPC1768 board support with special provisions for the U-Blox Model Evaluation board.
- See the NuttX board README file for further information about this port.
+ See the NuttX board README file for further information about this port.
-
@@ -3927,7 +3927,7 @@ nsh>
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.
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 README file for further information.
+ Refer to the NuttX board README file for further information.
NuttX-7.29
@@ -3952,7 +3952,7 @@ nsh>
Further information about the LC823450XGEVK is available on from the the ON Semiconductor website as are LC823450 related technical documents.
- Refer to the NuttX board README file for details of the NuttX port.
+ Refer to the NuttX board README file for details of the NuttX port.
This port is intended to test LC823450 features including SMP. Supported peripherals include UART, TIMER, RTC, GPIO, DMA, I2C, SPI, LCD, eMMC, and USB device.
@@ -3992,7 +3992,7 @@ nsh>
README File.
- Refer to the MAX32660-EVSYS README file for further information.
+ Refer to the MAX32660-EVSYS README file for further information.
@@ -4016,7 +4016,7 @@ nsh>
This initial porting effort uses the Infineon XMC4500 Relax v1 board as described on the manufacturer's website.
- The current status of the board is available in the board README file
+ The current status of the board is available in the board README file
@@ -4053,7 +4053,7 @@ nsh>
STATUS:
- Refer to the generic NRF52 board README file for further information.
+ Refer to the generic NRF52 board README file for further information.
@@ -4075,7 +4075,7 @@ nsh>
STATUS:
- Refer to the Teensy-3.1 board README file for further information.
+ Refer to the Teensy-3.1 board README file for further information.
@@ -4097,7 +4097,7 @@ nsh>
STATUS:
- Refer to the Freedom-K28F board README file for further information.
+ Refer to the Freedom-K28F board README file for further information.
@@ -4126,7 +4126,7 @@ nsh>
(2) bring up the NuttShell NSH, (3) develop support for the SDHC-based SD card,
(4) develop support for USB host and device, and (2) develop an LCD driver.
NOTE: Some of these remaining tasks are shared with the K60 work described below.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -4151,7 +4151,7 @@ nsh>
An additional, validated configuration exists for the NuttShell (NSH, see the
NSH User Guide).
This basic TWR-K60N512 first appeared in NuttX-6.8.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -4172,7 +4172,7 @@ nsh>
Support for the Kinetis K64 family and specifically for the NXP/Freescale Freedom K64F board was added in NuttX 7.17.
Initial release includes two NSH configurations with support for on-board LEDs, buttons, and Ethernet with the on-board KSZ8081 PHY.
SDHC supported has been integrated, but not verified.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
MK64FN1M0VMD12.
@@ -4182,7 +4182,7 @@ nsh>
NXP/Freescale Kinetis TWR-K64F120M.
Support for the Freescale Kinetis TWR-K64F120M was contributed in NuttX-7.20 by Maciej Skrzypek. Refer to the Freescale web site for further information about this board.
The board may be complemented by TWR-SER which includes (among other things), an RS232 and Ethernet connections.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -4221,7 +4221,7 @@ nsh>
NXP/FreeScale Kinetis K66.
Support for the Kinetis K64 family and specifically for the NXP/Freescale Freedom K66F board was contributed by David Sidrane in NuttX 7.20.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -4301,7 +4301,7 @@ nsh>
Support for the Nucleo-F302R8 board was added by raiden00pl in NuttX-7.27.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -4327,7 +4327,7 @@ nsh>
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 platform as well.
New drivers will be required for ADC and I2C which are very different on this platform.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -4335,12 +4335,12 @@ nsh>
STMicro ST Nucleo F303RE board.
The basic port for the Nucleo F303RE was contributed by Paul Alexander Patience and first released in NuttX-7.12.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
STMicro ST Nucleo F303ZE board.
Support for the Nucleo-F303ZE board was added by Mateusz Szafoni in NuttX-7.27.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -4412,7 +4412,7 @@ nsh>
Architecture support (only) for STMicro STM32F401xB and STM32F401xC pars was added.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -4500,7 +4500,7 @@ nsh>
- Refer to the STM3240G-EVAL board README file for further information.
+ Refer to the STM3240G-EVAL board README file for further information.
STMicro STM32F4-Discovery.
@@ -4529,7 +4529,7 @@ nsh>
STATUS:
The basic port for the STM32F4-Discovery was contributed by Mike Smith and was first released in NuttX-6.14.
All drivers listed for the STM3240G-EVAL are usable on this platform as well.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -4546,7 +4546,7 @@ nsh>
Battery connect and batter charger circuit.
- See the Mikroelektronika website for more information about this board and the NuttX board README file for further information about the NuttX port.
+ See the Mikroelektronika website for more information about this board and the NuttX board README file for further information about the NuttX port.
@@ -4558,30 +4558,30 @@ nsh>
Olimex STM32 H405.
Support for the Olimex STM32 H405 development board was contributed by Martin Lederhilger and appeared in NuttX-7.3.
- See the NuttX board README file for further information about the NuttX port.
+ See the NuttX board README file for further information about the NuttX port.
Olimex STM32 H407.
Support for the Olimex STM32 H407 development board was contributed by Neil Hancock and appeared in NuttX-7.14.
- See the NuttX board README file for further information about the NuttX port.
+ See the NuttX board README file for further information about the NuttX port.
Olimex STM32 E407.
Support for the Olimex STM32 E407 development board was contributed by Mateusz Szafoni and appeared in NuttX-7.17.
Networking configurations were added in NuttX-7.18.
- See the NuttX board README file for further information about the NuttX port.
+ See the NuttX board README file for further information about the NuttX port.
Olimex STM32 P407.
Support for the Olimex STM32 P407 development board appeared in NuttX-7.19.
- See the NuttX board README file for further information about the NuttX port.
+ See the NuttX board README file for further information about the NuttX port.
MikroElektronika Clicker2 for STM32.
This is yet another board supported by NuttX that uses the same STM32F407VGT6 MCU as does the STM32F4-Discovery board.
This board has been used primarily with the MRF24J40 Click board for the development of IEEE 802.15.4 MAC and 6LoWPAN support.
- See the Mikroelektronika website for more information about this board and the NuttX board README file for further information about the NuttX port.
+ See the Mikroelektronika website for more information about this board and the NuttX board README file for further information about the NuttX port.
@@ -4699,7 +4699,7 @@ nsh>
- Refer to the STM32F429I-Discovery board README file for further information.
+ Refer to the STM32F429I-Discovery board README file for further information.
@@ -4764,7 +4764,7 @@ nsh>
-
B-L475E-IOT01A Discovery Kit.
- Board support for the STMicro B-L475E-IOT01A board from ST Micro was contributed by Simon Piriou in NuttX-7.22. See the STMicro website and the board README file for further information.
+ Board support for the STMicro B-L475E-IOT01A board from ST Micro was contributed by Simon Piriou in NuttX-7.22. See the STMicro website and the board README file for further information.
This board STMicro is powered by STM32L475VG Cortex-M4 and targets IoT nodes with a choice of connectivity options including WiFi, Bluetooth LE, NFC, and sub-GHZ RF at 868 or 915 MHz, as well as a long list of various environmental sensors.
@@ -4806,13 +4806,13 @@ nsh>
-
Nucleo-L476RG.
- Board support for the STMicro NucleoL476RG board from ST Micro was contributed by Sebastien Lorquet in NuttX-7.15. See the STMicro website and the board README file for further information.
+ Board support for the STMicro NucleoL476RG board from ST Micro was contributed by Sebastien Lorquet in NuttX-7.15. See the STMicro website and the board README file for further information.
-
STM32L476VG Discovery.
- Board support for the STMicro STM32L476VG Discovery board from ST Micro was contributed by Dave in NuttX-7.15. See the STMicro website and the board README file for further information.
+ Board support for the STMicro STM32L476VG Discovery board from ST Micro was contributed by Dave in NuttX-7.15. See the STMicro website and the board README file for further information.
-
@@ -4820,7 +4820,7 @@ nsh>
STM32L476 MDK.
Very basic support for NuttX on the Motorola Moto Z MDK was contributed by Jim Wylder in NuttX 7.18.
A simple NSH configuration is available for the STM32L476 chip.
- See the Moto Mods Development Kit and the board README file for further information.
+ See the Moto Mods Development Kit and the board README file for further information.
@@ -4908,13 +4908,13 @@ nsh>
Nucleo-L432KC.
- Board support for the STMicro Nucleo-L432KC board from ST Micro was contributed by JSebastien Lorquet in NuttX-7.21. See the STMicro website and the board README file for further information.
+ Board support for the STMicro Nucleo-L432KC board from ST Micro was contributed by JSebastien Lorquet in NuttX-7.21. See the STMicro website and the board README file for further information.
Nucleo-L452RE.
- Board support for the STMicro Nucleo-L452RE board from ST Micro was contributed by Juha Niskanen in NuttX-7.21. See the STMicro website and the board README file for further information.
+ Board support for the STMicro Nucleo-L452RE board from ST Micro was contributed by Juha Niskanen in NuttX-7.21. See the STMicro website and the board README file for further information.
@@ -4939,7 +4939,7 @@ nsh>
Nucleo-L496ZG.
- Board support for the STMicro Nucleo-L496ZG board from ST Micro was contributed by Juha Niskanen in NuttX-7.21. See the STMicro website and the board README file for further information.
+ Board support for the STMicro Nucleo-L496ZG board from ST Micro was contributed by Juha Niskanen in NuttX-7.21. See the STMicro website and the board README file for further information.
See also the status above for the STM32 L476 most of which also applies to this part.
@@ -4964,7 +4964,7 @@ nsh>
STM32L4R9I-Discovery.
Board support for the STMicro STM32L4R9I-Discovery board from ST Micro was contributed by Juha Niskanen in NuttX-7.26.
That development board uses the STM32L4R9AI part.
- See the STMicro website and the board README file for further information.
+ See the STMicro website and the board README file for further information.
See also the status above for the opther STM32 L4 parts, most of which also applies to this part.
@@ -5028,7 +5028,7 @@ nsh>
- Refer to the EK-TM4C1294XL board README file for more detailed information about this port.
+ Refer to the EK-TM4C1294XL board README file for more detailed information about this port.
@@ -5305,14 +5305,14 @@ nsh>
This board supports included two configurations for the NuttShell (NSH).
Both are networked enabled: One configured to support IPv4 and one configured to supported IPv6.
- Instructions are included in the board README file for configuring both IPv4 and IPv6 simultaneously.
+ Instructions are included in the board README file for configuring both IPv4 and IPv6 simultaneously.
Tiva PWM and Quadrature Encoder drivers were contributed to NuttX in 7.18 by Young.
- Refer to the DK-TM4C129X board README file for more detailed information about this port.
+ Refer to the DK-TM4C129X board README file for more detailed information about this port.
@@ -5343,7 +5343,7 @@ nsh>
The basic port is nearly code complete but unverified in NuttX-7.28; The NSH configuration was fully functional in NuttX-7.29.
This effort is stalled on further radio development.
The plan was to integrate the IEEE 802.15.4 radio provided by the co-resident Cortex-M0. The Cortex-M0 interface, however, is not available with an open license that would permit redistribution.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -5379,7 +5379,7 @@ nsh>
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
Memory Usage.
@@ -5437,7 +5437,7 @@ Mem: 29232 5920 23312 23312
Support for the SAM4CMP-DB board was contributed to NuttX by Masayuki Ishikawa in NuttX-7.19.
The SAM4CM is a dual-CPU part and SMP was included for the ARMv7-M and SAM3/4 families.
The SAM4CMP-DB board support includes an NSH configuration that operates in an SMP configuration.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -5467,7 +5467,7 @@ Mem: 29232 5920 23312 23312
A DMA-base SPI driver is supported and has been verified with the AT25 Serial FLASH.
Touchscreen and LCD support was added in NuttX-7.3, but has not been fully integrated as of this writing.
The SAM4E-EK should be compatible with most of the other SAM3/4 drivers (like HSMCI, DMAC, etc.) but those have not be verified on the SAM4E-EK as of this writing.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -5496,7 +5496,7 @@ Mem: 29232 5920 23312 23312
Support for the on-board 1MB SRAM was added in NuttX-6.29.
An RTT driver was Bob Doiron in NuttX-7.3.
Bob also added an high resolution RTC emulation using the RTT for the sub-second counter.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -5511,7 +5511,7 @@ Mem: 29232 5920 23312 23312
As of this writing, the basic port is code complete and a fully verified configuration exists for the NuttShell NSH).
The first fully functional SAM4S Xplained Pro port was released in NuttX-7.2.
This supported also added HSMCI, RTC, and watchdog and verified support for USB device.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -5544,7 +5544,7 @@ Mem: 29232 5920 23312 23312
A new Ethernet MAC driver has been developed and is functional in the NSH configuration.
A DMA-base SPI driver is supported and has been verified with the AT25 Serial FLASH.
The SAM4E-EK should be compatible with most of the other SAM3/4 drivers (like HSMCI, DMAC, etc.) but those have not be verified on the SAM4E-EK as of this writing.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -5630,7 +5630,7 @@ Mem: 29232 5920 23312 23312
RSWDT driver.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -5648,7 +5648,7 @@ Mem: 29232 5920 23312 23312
This port uses Atmel SAM E70 Xplained Evaluation Kit (ATSAME70-XPLD).
This board is essentially a lower cost version of the SAMV71-XULT board featuring the ATSAME70Q21 Cortex-M7 microcontroller.
See the Atmel SAMV71 for supported features.
- Also refer to the NuttX board README file for further information.
+ Also refer to the NuttX board README file for further information.
@@ -5674,7 +5674,7 @@ Mem: 29232 5920 23312 23312
Because of the similarity in peripherals, several drivers were brought in from the SAML21 port.
Most have not been verified as of the NuttX-7.26 release.
These unverfied drivers include: SPI, I2C, DMA, USB.
- Also refer to the NuttX board README file for further information about the current state of the port.
+ Also refer to the NuttX board README file for further information about the current state of the port.
@@ -5696,7 +5696,7 @@ Mem: 29232 5920 23312 23312
Nucleo F722ZE.
This is a member of the common board support for the common Nucleo-144 boards, this one featuring the STM32F722ZE.
This port was also provided by Bob Feretich in NuttX-7.23.
- See the board README.txt file for further information.
+ See the board README.txt file for further information.
STATUS:
@@ -5735,7 +5735,7 @@ Mem: 29232 5920 23312 23312
STATUS:
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -5807,7 +5807,7 @@ Mem: 29232 5920 23312 23312
Nucleo-F767ZI.
This is a member of the Nucleo-144 board family.
Support for this board was also contributed by David Sidrane in NuttX-7.17.
- See the board README.txt file for further information.
+ See the board README.txt file for further information.
@@ -5834,7 +5834,7 @@ Mem: 29232 5920 23312 23312
Refer to the http://www.st.com website for further information about this board (search keyword: stm32f769i-disco).
- See also the board README.txt file for further information.
+ See also the board README.txt file for further information.
@@ -5862,7 +5862,7 @@ Mem: 29232 5920 23312 23312
Nucleo-H743ZI.
This is a member of the Nucleo-144 board family.
Support for this board was also added NuttX-7.26.
- See the board README.txt file for further information.
+ See the board README.txt file for further information.
The basic NSH configuration is fully, thanks to the bring-up efforts of Mateusz Szafoni.
@@ -5911,11 +5911,11 @@ Mem: 29232 5920 23312 23312
The basic IMXRT1050-EVK port is complete and verified configurations are available.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
The basic IMXRT1060-EVK port was complete but un-verified as of NuttX-7.27 but has been fully verified since NuttX-7.27
- Refer to the NuttX board README file for more current status information.
+ Refer to the NuttX board README file for more current status information.
Architecture-only support for the IMXRT1020 family was contributed in NuttX-7.30 by Dave Marples.
@@ -5996,14 +5996,14 @@ Mem: 29232 5920 23312 23312
STATUS:
Work on this port has stalled due to toolchain issues. Complete, but untested code for this port appears in the NuttX 6.5 release.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
LowPowerLab MoteinoMEGA.
This port of NuttX to the MoteinoMEGA from LowPowerLab.
The MoteinoMEGA is based on an Atmel ATMega1284P.
- See the LowPowerlab website and the board README file for further information.
+ See the LowPowerlab website and the board README file for further information.
@@ -6020,7 +6020,7 @@ Mem: 29232 5920 23312 23312
STATUS:
The basic port was released in NuttX-7.14 including a simple "Hello, World!" and OS test configurations.
Extensive effort was made to the use the special capabilities of the Atmel Studio AVR compiler to retain strings in FLASH memory and so keep the SRAM memory usage to a minimum.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -6050,7 +6050,7 @@ Mem: 29232 5920 23312 23312
The basic port was released in NuttX-6.5. This basic port consists only of
a "Hello, World!!" example that demonstrates initialization of the OS,
creation of a simple task, and serial console output.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -6072,7 +6072,7 @@ Mem: 29232 5920 23312 23312
An SPI driver and a USB device driver exist for the AT90USB as well
as a USB mass storage configuration. However, this configuration is not
fully debugged as of the NuttX-6.5 release.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -6165,7 +6165,7 @@ Mem: 29232 5920 23312 23312
The basic, port was be released in NuttX-5.13.
A complete port will include drivers for additional AVR32 UC3 devices -- like SPI and USB --- and will be available in a later release,
time permitting.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -6242,7 +6242,7 @@ Mem: 29232 5920 23312 23312
However, testing has not yet begun due to issues with BDMs, Code Warrior, and
the paging in the build process.
Progress is slow, but I hope to see a fully verified MC9S12NE64 port in the near future.
- Refer to the NuttX board README files for DEMO9S12NE64 and for the NE64 /PoE Badge for further information.
+ Refer to the NuttX board README files for DEMO9S12NE64 and for the NE64 /PoE Badge for further information.
@@ -6269,7 +6269,7 @@ Mem: 29232 5920 23312 23312
The port is reported to be functional on the Bifferboard as well.
In NuttX 7.1, Lizhuoyi contributed additional keyboard and VGA drivers.
This is a great, stable starting point for anyone interest in fleshing out the x86 port!
- Refer to the NuttX README file for further information.
+ Refer to the NuttX README file for further information.
@@ -6300,7 +6300,7 @@ Mem: 29232 5920 23312 23312
The PGA117, however, is not yet fully integrated to support ADC sampling.
See the NSH User Guide for further information about NSH.
The first verified port to the Mirtoo module was available with the NuttX 6.20 release.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -6334,7 +6334,7 @@ Mem: 29232 5920 23312 23312
An untested USB device-side driver is available in the source tree.
A more complete port would include support of the USB OTG port and of the LCD display on this board.
Those drivers are not yet available as of this writing.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -6350,7 +6350,7 @@ Mem: 29232 5920 23312 23312
STATUS:
The basic port is code complete and fully verified in NuttX 6.13.
Available configurations include the NuttShell (NSH - see the NSH User Guide).
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
UBW32 Board from Sparkfun
This is the port to the Sparkfun UBW32 board.
@@ -6363,7 +6363,7 @@ Mem: 29232 5920 23312 23312
The basic port is code complete and fully verified in NuttX 6.18.
Available configurations include the NuttShell (NSH - see the NSH User Guide).
USB has not yet been fully tested but on first pass appears to be functional.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -6394,7 +6394,7 @@ Mem: 29232 5920 23312 23312
A verified configuration is available for the NuttShel (NSH) appeared in NuttX-6.16.
Board support includes a verified USB (device-side) driver.
Also included are a a verified Ethernet driver, a partially verified USB device controller driver, and an unverifed SPI driver.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
Mikroelektronika PIC32MX7 Mulitmedia Board (MMB).
A port has been completed for the Mikroelektronika PIC32MX7 Multimedia Board (MMB).
@@ -6417,7 +6417,7 @@ Mem: 29232 5920 23312 23312
However, additional verification and tuning of this driver is required.
Further display/touchscreen verification would require C++ support (for NxWidgets and NxWM).
Since I there is no PIC32 C++ is the free version of the MPLAB C32 toolchain, further graphics development is stalled.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -6506,7 +6506,7 @@ Mem: 29232 5920 23312 23312
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -6551,7 +6551,7 @@ Mem: 29232 5920 23312 23312
(which has very limit SH-1 support to begin with), or perhaps with the CMON debugger.
At any rate, I have exhausted all of the energy that I am willing to put into this cool
old processor for the time being.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -6588,7 +6588,7 @@ BFD_ASSERT (*plt_offset != (bfd_vma) -1);
No workaround is known at this time. This is a show stopper for M16C.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -6645,7 +6645,7 @@ BFD_ASSERT (*plt_offset != (bfd_vma) -1);
There is little yet in the way of device driver support.
Outstanding issues include missing clock configuration logic, missing partition tables to support correct configuration from FLASH, and some serial driver pin configuration issues.
The configuration is usable despite these limitations.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -6671,7 +6671,7 @@ BFD_ASSERT (*plt_offset != (bfd_vma) -1);
The initial release of support for the z16f was made available in NuttX version 0.3.7.
A working NuttShell (NSH) configuration as added in NuttX-6.33 (although a patch is required to work around an issue with a ZDS-II 5.0.1 tool problem).
An ESPI driver was added in NuttX-7.2.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -6707,7 +6707,7 @@ BFD_ASSERT (*plt_offset != (bfd_vma) -1);
The first integrated version was released in NuttX version 0.4.2 (with important early bugfixes
in 0.4.3 and 0.4.4).
As of this writing, that port provides basic board support with a serial console, SPI, and eZ80F91 EMAC driver.
- Refer to the NuttX board README files for the ez80f0910200kitg and ez80f910200zcofile for further information.
+ Refer to the NuttX board README files for the ez80f0910200kitg and ez80f910200zcofile for further information.
NuttX-7.31:
@@ -6753,7 +6753,7 @@ BFD_ASSERT (*plt_offset != (bfd_vma) -1);
STATUS:
This release has been verified only on the ZiLOG ZDS-II Z8Encore! chip simulation
as of nuttx-0.3.9.
- Refer to the NuttX board README files for the z8encore000zco and for thez8f64200100kit for further information.
+ Refer to the NuttX board README files for the z8encore000zco and for thez8f64200100kit for further information.
@@ -6782,7 +6782,7 @@ BFD_ASSERT (*plt_offset != (bfd_vma) -1);
Most of the NuttX is in port for both the Z80182 and for the P112 board.
Boards from Kickstarter project will not be available, however, until the third quarter of 2013.
So it will be some time before this port is verified on hardware.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -6807,7 +6807,7 @@ BFD_ASSERT (*plt_offset != (bfd_vma) -1);
STATUS:
This port is complete and stable to the extent that it can be tested
using an instruction set simulator.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
@@ -6831,7 +6831,7 @@ BFD_ASSERT (*plt_offset != (bfd_vma) -1);
STATUS:
Basically the same as for the Z80 instruction set simulator.
This port was contributed by Jacques Pelletier.
- Refer to the NuttX board README file for further information.
+ Refer to the NuttX board README file for further information.
NOTE:
diff --git a/Documentation/NuttXNxFlat.html b/Documentation/NuttXNxFlat.html
index 4e44e45fce..3167f06a0c 100644
--- a/Documentation/NuttXNxFlat.html
+++ b/Documentation/NuttXNxFlat.html
@@ -331,7 +331,7 @@
cd
<some-dir>/buildroot
-
- Copy a configuration file into the top buildroot directory:
cp configs/abc-defconfig-x.y.z .config
.
+ Copy a configuration file into the top buildroot directory: cp boards/abc-defconfig-x.y.z .config
.
-
Enable building of the NXFLAT tools by
make menuconfig
.
diff --git a/Documentation/NuttxPortingGuide.html b/Documentation/NuttxPortingGuide.html
index d2c7b292d8..9211fdbccd 100644
--- a/Documentation/NuttxPortingGuide.html
+++ b/Documentation/NuttxPortingGuide.html
@@ -30,7 +30,7 @@
2.3 nuttx/binfmt/
2.4 nuttx/audio/
- 2.5 nuttx/configs/
+ 2.5 nuttx/boards/
2.5.1 Subdirectory Structure
2.5.2 Summary of Files
@@ -260,7 +260,7 @@
into the build.
- See also arch/README.txt
and configs/README.txt
.
+ See also arch/README.txt
and boards/README.txt
.
@@ -526,11 +526,11 @@
These board-specific configuration files can be found in the
- configs/
<board-name>/
sub-directories and are discussed
+ boards/
<board-name>/
sub-directories and are discussed
in a paragraph below.
- The directory configs/stm32f4disovery/
, as an example, holds board-specific logic for the STM32F4 Discovery board and is selected via the CONFIG_ARCH_BOARD="stm32f4discovery"
configuration setting.
+ The directory boards/stm32f4disovery/
, as an example, holds board-specific logic for the STM32F4 Discovery board and is selected via the CONFIG_ARCH_BOARD="stm32f4discovery"
configuration setting.
@@ -793,7 +793,7 @@
- The configs/
subdirectory contains configuration data for each board.
+ The boards/
subdirectory contains configuration data for each board.
These board-specific configurations plus the architecture-specific configurations in
the arch/
subdirectory complete define a customized port of NuttX.
@@ -801,7 +801,7 @@
The configs directory contains board specific configuration files. Each board must
- provide a subdirectory <board-name> under configs/
with the following characteristics:
+ provide a subdirectory <board-name> under boards/
with the following characteristics:
<board-name>
@@ -850,7 +850,7 @@
- The configs/
<board-name>/
sub-directory holds all of the
+ The boards/
<board-name>/
sub-directory holds all of the
files that are necessary to configure NuttX for the particular board.
A board may have various different configurations using the common source files.
Each board configuration is described by two files: Make.defs
and defconfig
.
@@ -920,7 +920,7 @@
- All of the specific boards supported by NuttX are identified in the README.txt file.
+ All of the specific boards supported by NuttX are identified in the README.txt file.
@@ -928,14 +928,14 @@
Now, how do you hook this board into the configuration system so that you can select with make menuconfig
?
- You will need modify the file configs/Kconfig
.
+ You will need modify the file boards/Kconfig
.
Let's look at the STM32F4-Discovery configuration in the Kconfig
file and see how we would add a new board directory to the configuration.
- For this configuration let's say that you new board resides in the directory configs/myboard
;
+ For this configuration let's say that you new board resides in the directory boards/myboard
;
It uses an MCU selected with CONFIG_ARCH_CHIP_MYMCU
; and you want the board to be selected with CONFIG_ARCH_BOARD_MYBOARD
.
- Then here is how you can clone the STM32F4-Discovery configuration in configs/Kconfig
to support your new board configuration.
+ Then here is how you can clone the STM32F4-Discovery configuration in boards/Kconfig
to support your new board configuration.
- In configs/Kconfig
for the stm32f4-discovery, you will see a configuration definition like this:
+ In boards/Kconfig
for the stm32f4-discovery, you will see a configuration definition like this:
config ARCH_BOARD_STM32F4_DISCOVERY
@@ -966,7 +966,7 @@ config ARCH_BOARD_MYBOARD
based on the MYMCU processor.
- Later in the configs/Kconfig
file, you will see a long, long string configuration with lots of defaults like this:
+ Later in the boards/Kconfig
file, you will see a long, long string configuration with lots of defaults like this:
config ARCH_BOARD
@@ -980,7 +980,7 @@ config ARCH_BOARD
This logic will assign string value to a configuration variable called CONFIG_ARCH_BOARD
that will name the directory where the board-specific files reside.
- In our case, these files reside in configs/myboard
and we add the following to the long list of defaults (again in alphabetical order):
+ In our case, these files reside in boards/myboard
and we add the following to the long list of defaults (again in alphabetical order):
default "myboard" if ARCH_BOARD_MYBOARD
@@ -989,15 +989,15 @@ config ARCH_BOARD
Now the build system knows where to find your board configuration!
- And finally, add something like this near the bottom of configs/myboard
:
+ And finally, add something like this near the bottom of boards/myboard
:
if ARCH_BOARD_MYBOARD
-source "configs/myboard/Kconfig"
+source "boards/myboard/Kconfig"
endif
- This includes additional, board-specific configuration variable definitions in configs/myboard/Kconfig
.
+ This includes additional, board-specific configuration variable definitions in boards/myboard/Kconfig
.
@@ -1555,13 +1555,13 @@ tools/
This could be done manually as follows:
- - Copy
configs/
<board-name>/[
<config-dir>/]Make.defs
to ${TOPDIR}/Make.defs
, -
-
- Copy
configs/
<board-name>/[
<config-dir>/]defconfig
to ${TOPDIR}/.config
+ - Copy
boards/
<board-name>/[
<config-dir>/]Make.defs
to ${TOPDIR}/Make.defs
, -
+
- Copy
boards/
<board-name>/[
<config-dir>/]defconfig
to ${TOPDIR}/.config
Where <board-name> is the name of one of the sub-directories of the
- NuttX configs/
directory.
+ NuttX boards/
directory.
This sub-directory name corresponds to one of the supported boards
identified above.
<config-dir> is the optional, specific configuration directory for the board.
@@ -1705,8 +1705,8 @@ The specific environmental definitions are unique for each board but should incl
- Auto-generating the file
${TOPDIR}/.version
with version 0.0 if one does not exist.
- Auto-generating the file
include/nuttx/version.h
using the ${TOPDIR}/.version
file.
- Creating a link to
${TOPDIR}/arch/
<arch-name>/include
at ${TOPDIR}/include/arch
.
- - Creating a link to
${TOPDIR}/configs/
<board-name>/include
at ${TOPDIR}/include/arch/board
.
- - Creating a link to
${TOPDIR}/configs/
<board-name>/src
at ${TOPDIR}/arch/
<arch-name>/src/board
+ - Creating a link to
${TOPDIR}/boards/
<board-name>/include
at ${TOPDIR}/include/arch/board
.
+ - Creating a link to
${TOPDIR}/boards/
<board-name>/src
at ${TOPDIR}/arch/
<arch-name>/src/board
- Creating a link to
${APPDIR}/include
at ${TOPDIR}/include/apps
- Creating make dependencies.
@@ -1762,7 +1762,7 @@ The specific environmental definitions are unique for each board but should incl
Board-Specific Interfaces.
Any interface which is unique to a board should be prefixed with the board name, for example
stm32f4discovery_
.
Sometimes the board name is too long so stm32_
would be okay too.
- These should be prototyped in configs/<board>/src/<board>.h
and should not be used outside of that directory since board-specific definitions have no meaning outside of the board directory.
+ These should be prototyped in boards/<board>/src/<board>.h
and should not be used outside of that directory since board-specific definitions have no meaning outside of the board directory.
-
@@ -1787,7 +1787,7 @@ The specific environmental definitions are unique for each board but should incl
Keeping in the spirit of the layered architecture, these publicly visible header files must not export platform-specific definitions; Only platform-specific realizations of standardized declarations should be visible.
Those standardized declarations should appear in common header files such as those provided by include/nuttx/arch.h
and include/nuttx/board.h
.
Similarly, these publicly visible header file must not include files that reside in the inaccessible platform-specific source directories.
- For example, the board-specific configs/<board>/include/board.h
header file must never include microcontroller-specific header files that reside in arch/<arch>/src/<mcu>
.
+ For example, the board-specific boards/<board>/include/board.h
header file must never include microcontroller-specific header files that reside in arch/<arch>/src/<mcu>
.
That practice will cause inclusion failures when the publicly visible file is included in common logic outside of the platform-specific source directories.
@@ -5204,7 +5204,7 @@ void iob_dump(FAR const char *msg, FAR struct iob_s *iob, unsigned int len,
The controller-specific, "upper half" touchscreen drivers reside in the directory drivers/input
.
- "Lower Half" Drivers.
- Platform-specific touchscreen drivers reside in either: (1) The
arch/
<architecture>/src/
<hardware> directory for the processor architectures that have build in touchscreen controllers or (2) the configs/
<board>/src/
directory for boards that use an external touchscreen controller chip.
+ Platform-specific touchscreen drivers reside in either: (1) The arch/
<architecture>/src/
<hardware> directory for the processor architectures that have build in touchscreen controllers or (2) the boards/
<board>/src/
directory for boards that use an external touchscreen controller chip.
@@ -6074,7 +6074,7 @@ int kbd_decode(FAR struct lib_instream_s *stream, FAR struct kbd_getstate_s *sta
-
Examples:
- drivers/lcd/p14201.c
, configs/sam3u-ek/src/up_lcd.c.
+ drivers/lcd/p14201.c
, boards/sam3u-ek/src/up_lcd.c.
See also the usage of the LCD driver in the graphics/
directory.
@@ -6366,7 +6366,7 @@ int kbd_decode(FAR struct lib_instream_s *stream, FAR struct kbd_getstate_s *sta
Examples:
- The function nsh_waiter()
in the file configs/olimex-lpc1766stk/src/lpc17_40_appinit.c
.
+ The function nsh_waiter()
in the file boards/olimex-lpc1766stk/src/lpc17_40_appinit.c
.
-
diff --git a/Documentation/README.html b/Documentation/README.html
index 18f537a309..8f12ce61bf 100644
--- a/Documentation/README.html
+++ b/Documentation/README.html
@@ -58,327 +58,327 @@ nuttx/
| `- README.txt
|- audio/
| `- README.txt
- |- configs/
+ |- boards/
| |- amber/
- | | `- README.txt
+ | | `- README.txt
| |- arduino-mega2560/
- | | `- README.txt
+ | | `- README.txt
| |- arduino-due/
- | | `- README.txt
+ | | `- README.txt
| |- avr32dev1/
- | | `- README.txt
+ | | `- README.txt
| |- axoloti/
- | | `- README.txt
+ | | `- README.txt
| |- b-l475e-iot01a/
- | | `- README.txt
+ | | `- README.txt
| |- bambino-200e/
- | | `- README.txt
+ | | `- README.txt
| |- c5471evm/
- | | `- README.txt
+ | | `- README.txt
| |- clicker2-stm32/
- | | `- README.txt
+ | | `- README.txt
| |- cloudctrl/
- | | `- README.txt
+ | | `- README.txt
| |- demo9s12ne64/
- | | `- README.txt
+ | | `- README.txt
| |- dk-tm4c129x/
- | | `- README.txt
+ | | `- README.txt
| |- ea3131/
- | | `- README.txt
+ | | `- README.txt
| |- ea3152/
- | | `- README.txt
+ | | `- README.txt
| |- eagle100/
- | | `- README.txt
+ | | `- README.txt
| |- efm32-g8xx-stk/
- | | `- README.txt
+ | | `- README.txt
| |- efm32gg-stk3700/
- | | `- README.txt
+ | | `- README.txt
| |- ekk-lm3s9b96/
- | | `- README.txt
+ | | `- README.txt
| |- ez80f910200kitg/
- | | |- ostest/README.txt
- | | `- README.txt
+ | | |- ostest/README.txt
+ | | `- README.txt
| |- ez80f910200zco/
- | | |- dhcpd/README.txt
- | | |- httpd/README.txt
- | | |- nettest/README.txt
- | | |- nsh/README.txt
- | | |- ostest/README.txt
- | | |- poll/README.txt
- | | `- README.txt
+ | | |- dhcpd/README.txt
+ | | |- httpd/README.txt
+ | | |- nettest/README.txt
+ | | |- nsh/README.txt
+ | | |- ostest/README.txt
+ | | |- poll/README.txt
+ | | `- README.txt
| |- fire-stm32v2/
- | | `- README.txt
+ | | `- README.txt
| |- flipnclick-pic32mz/
- | | `- README.txt
+ | | `- README.txt
| |- flipnclick-sam3x/
- | | `- README.txt
+ | | `- README.txt
| |- freedom-k28f/
- | | `- README.txt
+ | | `- README.txt
| |- freedom-k64f/
- | | `- README.txt
+ | | `- README.txt
| |- freedom-k66f/
- | | `- README.txt
+ | | `- README.txt
| |- freedom-kl25z/
- | | `- README.txt
+ | | `- README.txt
| |- freedom-kl26z/
- | | `- README.txt
+ | | `- README.txt
| |- gapuino/
- | | `- README.txt
+ | | `- README.txt
| |- hymini-stm32v/
- | | |- RIDE/README.txt
- | | `- README.txt
+ | | |- RIDE/README.txt
+ | | `- README.txt
| |- imxrt1050-evk/
- | | `- README.txt
+ | | `- README.txt
| |- kwikstik-k40/
- | | `- README.txt
+ | | `- README.txt
| |- launchxl-cc1310/
- | | `- README.txt
+ | | `- README.txt
| |- launchxl-cc1312r1/
- | | `- README.txt
+ | | `- README.txt
| |- launchxl-tms57004/
- | | `- README.txt
+ | | `- README.txt
| |- lincoln60/
- | | `- README.txt
+ | | `- README.txt
| |- lm3s6432-s2e/
- | | `- README.txt
+ | | `- README.txt
| |- lm3s6965-ek/
- | | `- README.txt
+ | | `- README.txt
| |- lm3s8962-ek/
- | | `- README.txt
+ | | `- README.txt
| |- lpc4330-xplorer/
- | | `- README.txt
+ | | `- README.txt
| |- lpc4337-ws/
- | | `- README.txt
+ | | `- README.txt
| |- lpc4357-evb/
- | | `- README.txt
+ | | `- README.txt
| |- lpc4370-link2/
- | | `- README.txt
+ | | `- README.txt
| |- lpcxpresso-lpc1768/
- | | `- README.txt
+ | | `- README.txt
| |- lpcxpresso-lpc54628/
- | | `- README.txt
+ | | `- README.txt
| |- makerlisp/
- | | |- nsh/README.txt
- | | `- README.txt\
+ | | |- nsh/README.txt
+ | | `- README.txt\
| |- maple/
- | | `- README.txt\
+ | | `- README.txt\
| |- max32660-evsys/
- | | `- README.txt
+ | | `- README.txt
| |- mbed/
- | | `- README.txt
+ | | `- README.txt
| |- mcb1700/
- | | `- README.txt
+ | | `- README.txt
| |- mcu123-lpc214x/
- | | `- README.txt
+ | | `- README.txt
| |- metro-m4/
- | | `- README.txt
+ | | `- README.txt
| |- micropendous3/
- | | `- README.txt
+ | | `- README.txt
| |- mikroe-stm32f4/
- | | `- README.txt
+ | | `- README.txt
| |- mirtoo/
- | | `- README.txt
+ | | `- README.txt
| |- misoc/
- | | `- README.txt
+ | | `- README.txt
| |- moteino-mega/
- | | `- README.txt
+ | | `- README.txt
| |- ne64badge/
- | | `- README.txt
+ | | `- README.txt
| |- nrf52-generic/
- | | `- README.txt
+ | | `- README.txt
| |- ntosd-dm320/
- | | |- doc/README.txt
- | | `- README.txt
+ | | |- doc/README.txt
+ | | `- README.txt
| |- nucleo-144/
- | | `- README.txt
+ | | `- README.txt
| | `- README.txt
| |- nucleo-f072rb/
- | | `- README.txt
+ | | `- README.txt
| |- nucleo-f091rc/
- | | `- README.txt
+ | | `- README.txt
| |- nucleo-f303re/
- | | `- README.txt
+ | | `- README.txt
| |- nucleo-f334r8/
- | | `- README.txt
+ | | `- README.txt
| |- nucleo-f4x1re/
- | | `- README.txt
+ | | `- README.txt
| |- nucleo-f410rb/
- | | `- README.txt
+ | | `- README.txt
| |- nucleo-f446re/
- | | `- README.txt
+ | | `- README.txt
| |- nucleo-l432kc/
- | | `- README.txt
+ | | `- README.txt
| |- nucleo-l452re/
- | | `- README.txt
+ | | `- README.txt
| |- nucleo-l476rg/
- | | `- README.txt
+ | | `- README.txt
| |- nucleo-l496zg/
- | | `- README.txt
+ | | `- README.txt
| |- nutiny-nuc120/
- | | `- README.txt
+ | | `- README.txt
| |- olimex-efm32g880f129-stk/
- | | `- README.txt
+ | | `- README.txt
| |- olimex-lpc1766stk/
- | | `- README.txt
+ | | `- README.txt
| |- olimex-lpc2378/
- | | `- README.txt
+ | | `- README.txt
| |- olimex-lpc-h3131/
- | | `- README.txt
+ | | `- README.txt
| |- olimex-stm32-h405/
- | | `- README.txt
+ | | `- README.txt
| |- olimex-stm32-h407/
- | | `- README.txt
+ | | `- README.txt
| |- olimex-stm32-p107/
- | | `- README.txt
+ | | `- README.txt
| |- olimex-stm32-p207/
- | | `- README.txt
+ | | `- README.txt
| |- olimex-stm32-p407/
- | | `- README.txt
+ | | `- README.txt
| |- olimex-strp711/
- | | `- README.txt
+ | | `- README.txt
| |- omnibusf4/
- | | `- README.txt
+ | | `- README.txt
| |- open1788/
- | | `- README.txt
+ | | `- README.txt
| |- p112/
- | | `- README.txt
+ | | `- README.txt
| |- pcduino-a10/
- | | `- README.txt
+ | | `- README.txt
| |- photon/
- | | `- README.txt
+ | | `- README.txt
| |- pic32mx-starterkit/
- | | `- README.txt
+ | | `- README.txt
| |- pic32mx7mmb/
- | | `- README.txt
+ | | `- README.txt
| |- pic32mz-starterkit/
- | | `- README.txt
+ | | `- README.txt
| |- pnev5180b/
- | | `- README.txt
+ | | `- README.txt
| |- qemu-i486/
- | | `- README.txt
+ | | `- README.txt
| |- sabre-6quad/
- | | `- README.txt
+ | | `- README.txt
| |- sama5d2-xult/
- | | `- README.txt
+ | | `- README.txt
| |- sama5d3x-ek/
- | | `- README.txt
+ | | `- README.txt
| |- sama5d3-xplained/
- | | `- README.txt
+ | | `- README.txt
| |- sama5d4-ek/
- | | `- README.txt
+ | | `- README.txt
| |- samd20-xplained/
- | | `- README.txt
+ | | `- README.txt
| |- samd21-xplained/
- | | `- README.txt
+ | | `- README.txt
| |- saml21-xplained/
- | | `- README.txt
+ | | `- README.txt
| |- sam3u-ek/
- | | `- README.txt
+ | | `- README.txt
| |- sam4cmp-db
- | | `- README.txt
+ | | `- README.txt
| |- sam4e-ek/
- | | `- README.txt
+ | | `- README.txt
| |- sam4l-xplained/
- | | `- README.txt
+ | | `- README.txt
| |- sam4s-xplained/
- | | `- README.txt
+ | | `- README.txt
| |- sam4s-xplained-pro/
- | | `- README.txt
+ | | `- README.txt
| |- same70-xplained/
- | | `- README.txt
+ | | `- README.txt
| |- samv71-xult/
- | | `- README.txt
+ | | `- README.txt
| |- shenzhou/
- | | `- README.txt
+ | | `- README.txt
| |- sim/
- | | |- include/README.txt
- | | `- README.txt
+ | | |- include/README.txt
+ | | `- README.txt
| |- skp16c26/
- | | `- README.txt
+ | | `- README.txt
| |- spresense/
- | | `- README.txt
+ | | `- README.txt
| |- stm3210e-eval/
- | | |- RIDE/README.txt
- | | `- README.txt
+ | | |- RIDE/README.txt
+ | | `- README.txt
| |- stm3220g-eval/
- | | `- README.txt
+ | | `- README.txt
| |- stm3240g-eval/
- | | `- README.txt
+ | | `- README.txt
| |- stm32_tiny/
- | | `- README.txt
+ | | `- README.txt
| |- stm32f103-minumum/
- | | `- README.txt
+ | | `- README.txt
| |- stm32f3discovery/
- | | `- README.txt
+ | | `- README.txt
| |- stm32f4discovery/
- | | `- README.txt
+ | | `- README.txt
| |- stm32f411e-disco/
- | | `- README.txt
+ | | `- README.txt
| |- stm32f429i-disco/
- | | |- fb/README.txt<
- | | `- README.txt
+ | | |- fb/README.txt<
+ | | `- README.txt
| |- stm32f746g-disco/
- | | |- fb/README.txt<
- | | |- nxdemo/README.txt<
- | | |- nxterm/README.txt<
- | | `- README.txt
+ | | |- fb/README.txt<
+ | | |- nxdemo/README.txt<
+ | | |- nxterm/README.txt<
+ | | `- README.txt
| |- stm32f769i-disco/
- | | `- README.txt
+ | | `- README.txt
| |- stm32l476-mdk/
- | | `- README.txt
+ | | `- README.txt
| |- stm32l476vg-disco/
- | | `- README.txt
+ | | `- README.txt
| |- stm32l4r9ai-disco/
- | | `- README.txt
+ | | `- README.txt
| |- stm32ldiscovery/
- | | `- README.txt
+ | | `- README.txt
| |- stm32vldiscovery/
- | | `- README.txt
+ | | `- README.txt
| |- sure-pic32mx/
- | | `- README.txt
+ | | `- README.txt
| |- teensy-2.0/
- | | `- README.txt
+ | | `- README.txt
| |- teensy-3.1/
- | | `- README.txt
+ | | `- README.txt
| |- teensy-lc/
- | | `- README.txt
+ | | `- README.txt
| |- tm4c123g-launchpad/
- | | `- README.txt
+ | | `- README.txt
| |- tm4c1294-launchpad/
- | | `- README.txt
+ | | `- README.txt
| |- tms570ls31x-usb-kit/
- | | `- README.txt
+ | | `- README.txt
| |- twr-k60n512/
- | | `- README.txt
+ | | `- README.txt
| |- twr-k64f120m/
- | | `- README.txt
+ | | `- README.txt
| |- "u-blox-c027/
- | | `- README.txt
+ | | `- README.txt
| |- ubw32/
- | | `- README.txt
+ | | `- README.txt
| |- us7032evb1/
- | | `- README.txt
+ | | `- README.txt
| |- viewtool-stm32f107/
- | | `- README.txt
+ | | `- README.txt
| |- xmc4500-relax/
- | | `- README.txt
+ | | `- README.txt
| |- z16f2800100zcog/
- | | |- ostest/README.txt
- | | |- pashello/README.txt
- | | `- README.txt
+ | | |- ostest/README.txt
+ | | |- pashello/README.txt
+ | | `- README.txt
| |- z80sim/
- | | `- README.txt
+ | | `- README.txt
| |- z8encore000zco/
- | | |- ostest/README.txt
- | | `- README.txt
+ | | |- ostest/README.txt
+ | | `- README.txt
| |- z8f64200100kit/
- | | |- ostest/README.txt
- | | `- README.txt
+ | | |- ostest/README.txt
+ | | `- README.txt
| |- zkit-arm-1769/
- | | `- README.txt
+ | | `- README.txt
| |- zp214xpa/
- | | `- README.txt
- | `- README.txt
+ | | `- README.txt
+ | `- README.txt
|- drivers/
| |- eeprom/
| | `- README.txt
diff --git a/README.txt b/README.txt
index 1391538b2b..d03f1dc383 100644
--- a/README.txt
+++ b/README.txt
@@ -679,7 +679,7 @@ Instantiating "Canned" Configurations
"Canned" NuttX configuration files are retained in:
- configs//
+ boards//
Where is the name of your development board and
is the name of the sub-directory containing a specific configuration for
@@ -706,8 +706,8 @@ Instantiating "Canned" Configurations
General information about configuring NuttX can be found in:
- {TOPDIR}/configs/README.txt
- {TOPDIR}/configs//README.txt
+ {TOPDIR}/boards/README.txt
+ {TOPDIR}/boards//README.txt
The Hidden Configuration Scripts:
@@ -720,9 +720,9 @@ Instantiating "Canned" Configurations
Configuring NuttX requires only copying two files from the
to the directory where you installed NuttX (TOPDIR):
- Copy configs///Make.def to{TOPDIR}/Make.defs
+ Copy boards///Make.def to{TOPDIR}/Make.defs
OR
- Copy configs//scripts/Make.def to{TOPDIR}/Make.defs
+ Copy boards//scripts/Make.def to{TOPDIR}/Make.defs
Make.defs describes the rules needed by your tool chain to compile
and link code. You may need to modify this file to match the
@@ -731,7 +731,7 @@ Instantiating "Canned" Configurations
it may use a common Make.defs file for the board in the scripts/
directory. The first takes precedence.
- Copy configs///defconfig to{TOPDIR}/.config
+ Copy boards///defconfig to{TOPDIR}/.config
The defconfig file holds the actual build configuration. This
file is included by all other make files to determine what is
@@ -1221,7 +1221,7 @@ Cross-Development Toolchains
In order to build NuttX for your board, you will have to obtain a cross-
compiler to generate code for your target CPU. For each board,
- configuration, there is a README.txt file (at configs//README.txt).
+ configuration, there is a README.txt file (at boards//README.txt).
That README file contains suggestions and information about appropriate
tools and development environments for use with your board.
@@ -1234,11 +1234,11 @@ NuttX Buildroot Toolchain
For many configurations, a DIY set of tools is available for NuttX. These
tools can be downloaded from the NuttX Bitbucket.org file repository. After
unpacking the buildroot tarball, you can find instructions for building
- the tools in the buildroot/configs/README.txt file.
+ the tools in the buildroot/boards/README.txt file.
Check the README.txt file in the configuration directory for your board
to see if you can use the buildroot toolchain with your board (this
- README.txt file is located in configs//README.txt).
+ README.txt file is located in boards//README.txt).
This toolchain is available for both the Linux and Cygwin development
environments.
@@ -1312,7 +1312,7 @@ Building
make
At least one configuration (eagle100) requires additional command line
- arguments on the make command. Read{TOPDIR}/configs//README.txt
+ arguments on the make command. Read{TOPDIR}/boards//README.txt
to see if that applies to your target.
Re-building
@@ -1754,7 +1754,7 @@ nuttx/
|- binfmt/
| `-libpcode/
| `-README.txt
- |- configs/
+ |- boards/
| |- amber/
| | `- README.txt
| |- arduino-mega2560/
diff --git a/TODO b/TODO
index 34b3a15671..3a75faa6b1 100644
--- a/TODO
+++ b/TODO
@@ -4,7 +4,7 @@ NuttX TODO List (Last updated July 1, 2019)
This file summarizes known NuttX bugs, limitations, inconsistencies with
standards, things that could be improved, and ideas for enhancements. This
TODO list does not include issues associated with individual board ports. See
-also the individual README.txt files in the configs/ sub-directories for
+also the individual README.txt files in the boards/ sub-directories for
issues related to each board port.
nuttx/:
@@ -81,7 +81,7 @@ o Task/Scheduler (sched/)
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
- configs/ea3131/pgnsh and locked directories). There are
+ boards/ea3131/pgnsh and locked directories). There are
some limitations of this testing so I still cannot say that
the feature is fully functional.
Status: Open. This has been put on the shelf for some time.
@@ -283,7 +283,7 @@ o Task/Scheduler (sched/)
and sched_setaffinity(),
2018-09-15: This change has been completed for the case of
open() used within the OS. There are places under libs/ and
- configs/ that have not been converted. I also note cases
+ boards/ that have not been converted. I also note cases
where fopen() is called under libs/libc/netdb/.
Status: Open
@@ -987,7 +987,7 @@ o Kernel/Protected Build
by simply reading this variable.
"This one would be easy: Just a change to include/nuttx/userspace.h,
- configs/*/kernel/up_userspace.c, libs/libc/,
+ boards/*/kernel/up_userspace.c, libs/libc/,
sched/sched_addreadytorun.c, and sched/sched_removereadytorun.c.
That would eliminate 59% of the syscalls."
@@ -1788,7 +1788,7 @@ o USB (drivers/usbdev, drivers/usbhost)
Title: USB CDC/ACM HOST CLASS DRIVER
Description: A CDC/ACM host class driver has been added. This has been
testing by running the USB CDC/ACM host on an Olimex
- LPC1766STK and using the configs/stm3210e-eval/usbserial
+ LPC1766STK and using the boards/stm3210e-eval/usbserial
configuration (using the CDC/ACM device side driver). There
are several unresolved issues that prevent the host driver
from being usable:
@@ -2230,7 +2230,7 @@ o File system / Generic drivers (fs/, drivers/)
file being read is smaller than number bytes written to the
file. That test does write small files continuously until
file system is full and even the the error is rare. The
- configs/sim/spiffs test can used to demonstrate the error.
+ boards/sim/spiffs test can used to demonstrate the error.
Status: Open
Priority: Medium. It is certain a file system failure, but I think that
the exposure in real world uses cases is very small.
diff --git a/arch/README.txt b/arch/README.txt
index 551dd2d5f4..7aececc72b 100644
--- a/arch/README.txt
+++ b/arch/README.txt
@@ -32,7 +32,7 @@ o Board specific files. In order to be usable, the chip must be
peripheral LEDs, external peripherals (such as network, USB, etc.).
These board-specific configuration files can be found in the
- configs// sub-directories.
+ boards// sub-directories.
This README will address the processor architecture specific files
that are contained in the arch// directory. The file
diff --git a/arch/arm/src/am335x/am335x_lcdc.c b/arch/arm/src/am335x/am335x_lcdc.c
index aebca6d358..9b16913168 100644
--- a/arch/arm/src/am335x/am335x_lcdc.c
+++ b/arch/arm/src/am335x/am335x_lcdc.c
@@ -514,7 +514,7 @@ static int am335x_lcdc_enableclk(void)
* 1b. The framebuffer character driver is initialized and calls
* up_fbinitialize().
* 2. The function up_fbinitialize() must reside in board specific logic
- * under configs/. It must create the instance of struct
+ * under boards/. It must create the instance of struct
* am335x_panel_info_s and call this function with that instance.
*
* For a directly connected LCD, either (1) the struct am335x_panel_info_s
diff --git a/arch/arm/src/am335x/am335x_lcdc.h b/arch/arm/src/am335x/am335x_lcdc.h
index 79e63943f3..9d156ad6c8 100644
--- a/arch/arm/src/am335x/am335x_lcdc.h
+++ b/arch/arm/src/am335x/am335x_lcdc.h
@@ -196,7 +196,7 @@ struct am335x_panel_info_s
* 1b. The framebuffer character driver is initialized and calls
* up_fbinitialize().
* 2. The function up_fbinitialize() must reside in board specific logic
- * under configs/. It must create the instance of struct
+ * under boards/. It must create the instance of struct
* am335x_panel_info_s and call this function with that instance.
*
* For a directly connected LCD, either (1) the struct am335x_panel_info_s
diff --git a/arch/arm/src/dm320/dm320_memorymap.h b/arch/arm/src/dm320/dm320_memorymap.h
index a5db596361..f5e3a9bcd3 100644
--- a/arch/arm/src/dm320/dm320_memorymap.h
+++ b/arch/arm/src/dm320/dm320_memorymap.h
@@ -60,7 +60,7 @@
* NOTE:
* 1. Most DM320 memory sections can be programmed to lie at different locations in
* the memory map. Therefore, much of the DM320 physical memory map is really
- * board-specific and, as such, really belongs in the configs//include/board.h
+ * board-specific and, as such, really belongs in the boards//include/board.h
* file rather than here.
*
* To handle all cases, this file defines a "default" physical memory map, but
diff --git a/arch/arm/src/stm32/stm32_eth.c b/arch/arm/src/stm32/stm32_eth.c
index 974ebcf11b..5b1b956f19 100644
--- a/arch/arm/src/stm32/stm32_eth.c
+++ b/arch/arm/src/stm32/stm32_eth.c
@@ -84,7 +84,7 @@
* Pre-processor Definitions
****************************************************************************/
/* Configuration ************************************************************/
-/* See configs/stm3240g-eval/README.txt for an explanation of the configuration
+/* See boards/stm3240g-eval/README.txt for an explanation of the configuration
* settings.
*/
diff --git a/arch/arm/src/stm32f7/stm32_ethernet.c b/arch/arm/src/stm32f7/stm32_ethernet.c
index e80ae02af2..3f69169b43 100644
--- a/arch/arm/src/stm32f7/stm32_ethernet.c
+++ b/arch/arm/src/stm32f7/stm32_ethernet.c
@@ -90,7 +90,7 @@
#define MEMORY_SYNC() do { ARM_DSB(); ARM_ISB(); } while (0)
/* Configuration ************************************************************/
-/* See configs/stm3240g-eval/README.txt for an explanation of the configuration
+/* See boards/stm3240g-eval/README.txt for an explanation of the configuration
* settings.
*/
diff --git a/arch/arm/src/stm32h7/stm32_ethernet.c b/arch/arm/src/stm32h7/stm32_ethernet.c
index bfbe655022..f6e44f89e5 100644
--- a/arch/arm/src/stm32h7/stm32_ethernet.c
+++ b/arch/arm/src/stm32h7/stm32_ethernet.c
@@ -92,7 +92,7 @@
/* Configuration ************************************************************/
-/* See configs/stm3240g-eval/README.txt for an explanation of the
+/* See boards/stm3240g-eval/README.txt for an explanation of the
* configuration settings.
*/
diff --git a/arch/avr/src/at32uc3/at32uc3.h b/arch/avr/src/at32uc3/at32uc3.h
index 4fc12171ed..f1610550e9 100644
--- a/arch/avr/src/at32uc3/at32uc3.h
+++ b/arch/avr/src/at32uc3/at32uc3.h
@@ -223,7 +223,7 @@ void up_consoleinit(void);
*
* Description:
* This function must be provided by the board-specific logic in the
- * directory configs//src.
+ * directory boards//src.
*
****************************************************************************/
diff --git a/arch/avr/src/at90usb/at90usb.h b/arch/avr/src/at90usb/at90usb.h
index 2f2fc208e7..fd0c198612 100644
--- a/arch/avr/src/at90usb/at90usb.h
+++ b/arch/avr/src/at90usb/at90usb.h
@@ -128,7 +128,7 @@ void up_consoleinit(void);
*
* Description:
* This function must be provided by the board-specific logic in the
- * directory configs//src/.
+ * directory boards//src/.
*
****************************************************************************/
diff --git a/arch/avr/src/atmega/atmega.h b/arch/avr/src/atmega/atmega.h
index 621e6f335e..7acebb6196 100644
--- a/arch/avr/src/atmega/atmega.h
+++ b/arch/avr/src/atmega/atmega.h
@@ -130,7 +130,7 @@ void up_consoleinit(void);
*
* Description:
* This function must be provided by the board-specific logic in the
- * directory configs//src.
+ * directory boards//src.
*
****************************************************************************/
diff --git a/arch/mips/src/pic32mx/pic32mx.h b/arch/mips/src/pic32mx/pic32mx.h
index e76f02c871..3610a26fa7 100644
--- a/arch/mips/src/pic32mx/pic32mx.h
+++ b/arch/mips/src/pic32mx/pic32mx.h
@@ -234,7 +234,7 @@ void pic32mx_uartconfigure(uintptr_t uart_base, uint32_t baudrate,
*
* Description:
* This function must be provided by the board-specific logic in the directory
- * configs//pic32_boot.c.
+ * boards//pic32_boot.c.
*
************************************************************************************/
diff --git a/arch/mips/src/pic32mz/pic32mz-lowinit.h b/arch/mips/src/pic32mz/pic32mz-lowinit.h
index 369ef9ebb8..6fdc6db85e 100644
--- a/arch/mips/src/pic32mz/pic32mz-lowinit.h
+++ b/arch/mips/src/pic32mz/pic32mz-lowinit.h
@@ -87,7 +87,7 @@ void pic32mz_lowinit(void);
*
* Description:
* This function must be provided by the board-specific logic in the directory
- * /configs//pic32mz_boot.c.
+ * /boards//pic32mz_boot.c.
*
************************************************************************************/
diff --git a/arch/renesas/include/README.txt b/arch/renesas/include/README.txt
index c07708aeca..4a96130c63 100644
--- a/arch/renesas/include/README.txt
+++ b/arch/renesas/include/README.txt
@@ -1,5 +1,5 @@
This directory contains header files common to all SH architectures.
Sub-directories within this directory contain header files unique to
specific SH chip architectures. At configuration time, additional directories
-will be linked here: 'build' will be a link to the configs/*/include
+will be linked here: 'build' will be a link to the boards/*/include
directory; 'chip' will be a link to the SH chip sub-directory.
diff --git a/arch/renesas/src/README.txt b/arch/renesas/src/README.txt
index 77c3cdeca8..342fc13a1f 100644
--- a/arch/renesas/src/README.txt
+++ b/arch/renesas/src/README.txt
@@ -3,5 +3,5 @@ architectures. The 'common' subdirectory contains source files shared by
all Renesas architectures; Source files unique to a specific Renesas chip
architecture are contained in a subdirectory named after the chip. At
configuration time, additional directories will be linked here: 'board'
-will be a link to the configs/*/src directory; 'chip' will be a link to
+will be a link to the boards/*/src directory; 'chip' will be a link to
the SH chip sub-directory.
diff --git a/arch/x86/src/common/up_internal.h b/arch/x86/src/common/up_internal.h
index 32690eddfe..9906a91f93 100644
--- a/arch/x86/src/common/up_internal.h
+++ b/arch/x86/src/common/up_internal.h
@@ -166,7 +166,7 @@ extern uint32_t _ebss; /* End+1 of .bss */
*
* Description:
* This function must be provided by the board-specific logic in the
- * directory configs//src/.
+ * directory boards//src/.
*
****************************************************************************/
diff --git a/arch/z80/src/z180/README.txt b/arch/z80/src/z180/README.txt
index b088470b6a..7c551c86ca 100644
--- a/arch/z80/src/z180/README.txt
+++ b/arch/z80/src/z180/README.txt
@@ -16,19 +16,19 @@ z180_rom.asm
Some architectures may have ROM located at address zero. In this case, a
special version of the "head" logic must be used. This special "head"
file is probably board-specific and, hence, belongs in the board-specific
- configs//src directory. This file may, however, be used as
+ boards//src directory. This file may, however, be used as
a model for such a board-specific file.
z180_rom.S is enabled by specifying CONFIG_LINKER_ROM_AT_0000 in the
configuration file.
- A board specific version in the configs//src directory can be
+ A board specific version in the boards//src directory can be
used by:
1. Define CONFIG_ARCH_HAVEHEAD
2. Add the board-specific head file, say .asm, to
- configs//src
- 3. Add a file called Make.defs in the configs//src directory
+ boards//src
+ 3. Add a file called Make.defs in the boards//src directory
containing the line: HEAD_ASRC = .asm
Make.defs
diff --git a/arch/z80/src/z80/README.txt b/arch/z80/src/z80/README.txt
index f5ad20a4c1..81ca426c9d 100644
--- a/arch/z80/src/z80/README.txt
+++ b/arch/z80/src/z80/README.txt
@@ -16,19 +16,19 @@ z80_rom.asm
Some architectures may have ROM located at address zero. In this case, a
special version of the "head" logic must be used. This special "head"
file is probably board-specific and, hence, belongs in the board-specific
- configs//src directory. This file may, however, be used as
+ boards//src directory. This file may, however, be used as
a model for such a board-specific file.
z80_rom.S is enabled by specifying CONFIG_LINKER_ROM_AT_0000 in the
configuration file.
- A board specific version in the configs//src directory can be
+ A board specific version in the boards//src directory can be
used by:
1. Define CONFIG_ARCH_HAVEHEAD
2. Add the board-specific head file, say .asm, to
- configs//src
- 3. Add a file called Make.defs in the configs//src directory
+ boards//src
+ 3. Add a file called Make.defs in the boards//src directory
containing the line: HEAD_ASRC = .asm
Make.defs
diff --git a/boards/README.txt b/boards/README.txt
index aa3bd35250..0edebef95c 100644
--- a/boards/README.txt
+++ b/boards/README.txt
@@ -47,11 +47,11 @@ o Board specific files. In order to be usable, the chip must be
peripheral LEDs, external peripherals (such as network, USB, etc.).
These board-specific configuration files can be found in the
- configs// sub-directories and are discussed in this
+ boards// sub-directories and are discussed in this
README. Additional configuration information may be available in
- board-specific configs//README.txt files.
+ board-specific boards//README.txt files.
-The configs/ subdirectory contains configuration data for each board. These
+The boards/ subdirectory contains configuration data for each board. These
board-specific configurations plus the architecture-specific configurations in
the arch/ subdirectory completely define a customized port of NuttX.
@@ -59,7 +59,7 @@ Directory Structure
^^^^^^^^^^^^^^^^^^^
The configs directory contains board specific configuration logic. Each
-board must provide a subdirectory under configs/ with the
+board must provide a subdirectory under boards/ with the
following characteristics:
@@ -166,16 +166,16 @@ http://nuttx.org/Documentation/NuttXConfigVariables.html.
Supported Boards
^^^^^^^^^^^^^^^^
-configs/amber
+boards/amber
This is placeholder for the SoC Robotics Amber Web Server that is based
on the Atmel AVR ATMega128 MCU. There is not much there yet and what is
there is untested due to tool-related issues.
-configs/arduino-due
+boards/arduino-due
This sub-directory holds board support for the Arduino DUE board featuring
the Atmel ATSAM3X8E MCU running at 84 MHz.
-configs/avr32dev1
+boards/avr32dev1
This is a port of NuttX to the Atmel AVR32DEV1 board. That board is
based on the Atmel AT32UC3B0256 MCU and uses a specially patched
version of the GNU toolchain: The patches provide support for the
@@ -183,17 +183,17 @@ configs/avr32dev1
Atmel website. STATUS: This port is functional but very basic. There
are configurations for NSH and the OS test.
-configs/axoloti
+boards/axoloti
Support for the Axoloti synthesizer board based on the STMicro
STM32F427IGH6 MCU. See: http://www.axoloti.com/
-configs/b-l072z-lrwan1
+boards/b-l072z-lrwan1
STMicro STM32L0 Discovery kit with LoRa/SigFox based on STM32L072CZ MCU.
-configs/bambino-200e
+boards/bambino-200e
Micromint Bambino board. This board is based on the LPC4330FBD144.
-configs/c5471evm
+boards/c5471evm
This is a port to the Spectrum Digital C5471 evaluation board. The
TMS320C5471 is a dual core processor from TI with an ARM7TDMI general
purpose processor and a c54 DSP. It is also known as TMS320DA180 or just DA180.
@@ -209,51 +209,51 @@ configs launchxl_cc1312r1
Port to the TI SimpleLink CC1312R1 LaunchPad Evaluation Kit (LAUNCHXL-CC1312R1)
featuring the SimpleLinkCC1312R1 chip.
-configs/clicker2-stm32
+boards/clicker2-stm32
Mikroe Clicker2 STM32 board based on the STMicro STM32F407VGT6 MCU.
-configs/cloudctrl
+boards/cloudctrl
Darcy's CloudController board. This is a small network relay development
board. Based on the Shenzhou IV development board design. It is based on
the STM32F107VC MCU.
-configs/demo9s12ne64
+boards/demo9s12ne64
NXP/FreeScale DMO9S12NE64 board based on the MC9S12NE64 hcs12 cpu. This
port uses the m9s12x GCC toolchain. STATUS: (Still) under development; it
is code complete but has not yet been verified.
-configs/dk-tm4c129x
+boards/dk-tm4c129x
This is the port of NuttX to the Tiva® DK-TM4C129x Connected Development Kit. The
Tiva® DK-TM4C129x features the TM4C129XNCZAD MCU.
-configs/ea3131
+boards/ea3131
Embedded Artists EA3131 Development board. This board is based on the
an NXP LPC3131 MCU. This OS is built with the arm-nuttx-elf toolchain*.
STATUS: This port is complete and mature.
-configs/ea3152
+boards/ea3152
Embedded Artists EA3152 Development board. This board is based on the
an NXP LPC3152 MCU. This OS is built with the arm-nuttx-elf toolchain*.
STATUS: This port is has not be exercised well, but since it is
a simple derivative of the ea3131, it should be fully functional.
-configs/eagle100
+boards/eagle100
Micromint Eagle-100 Development board. This board is based on the
an ARM Cortex-M3 MCU, the Luminary LM3S6918. This OS is built with the
arm-nuttx-elf toolchain*. STATUS: This port is complete and mature.
-configs/efm32-g8xx-stk
+boards/efm32-g8xx-stk
The port of NuttX to the EFM32 Gecko Starter Kit (EFM32-G8XX-STK).
-configs/efm32gg-stk3700
+boards/efm32gg-stk3700
The port of NuttX to the EFM32 Giant Gecko Starter Kit
(EFM32GG-STK3700).
-configs/ekk-lm3s9b96
+boards/ekk-lm3s9b96
TI/Stellaris EKK-LM3S9B96 board. This board is based on the
an EKK-LM3S9B96 which is a Cortex-M3.
-configs/esp-core
+boards/esp-core
The ESP32 is a dual-core system from Expressif with two Harvard
architecture Xtensa LX6 CPUs. All embedded memory, external memory and
nd peripherals are located on the data bus and/or the instruction bus of
@@ -261,179 +261,179 @@ configs/esp-core
CPUs is symmetric, meaning they use the same addresses to access the same
memory.
-configs/ez80f0910200kitg
+boards/ez80f0910200kitg
ez80Acclaim! Microcontroller. This port use the Zilog ez80f0910200kitg
development kit, eZ80F091 part, and the Zilog ZDS-II Windows command line
tools. The development environment is Cygwin under WinXP.
-configs/ez80f0910200zco
+boards/ez80f0910200zco
ez80Acclaim! Microcontroller. This port use the Zilog ez80f0910200zco
development kit, eZ80F091 part, and the Zilog ZDS-II Windows command line
tools. The development environment is Cygwin under WinXP.
-configs/fire-stm32v2
+boards/fire-stm32v2
A configuration for the M3 Wildfire STM32 board. This board is based on the
STM32F103VET6 chip. See http://firestm32.taobao.com . Version 2 and 3 of
the boards are supported but only version 2 has been tested.
-configs/flipnclick-pic32mz
+boards/flipnclick-pic32mz
Board support for the Mikroe Flip&Click PIC32MZ board. This board is an
chipKit Arduino-compatible board (but can also be used with the Mikroe
bootloader). It has with four Mikroe Click bus interfaces in addition to
standard Arduino connectors. This board features the Microchip
PIC32MZ2048EFH100 MCU running at 200 MHz (252Mhz capable).
-configs/flipnclick-sam3x
+boards/flipnclick-sam3x
Board support for the Mikroe Flip&Click STM32X board. This board is an
Arduino-Due work-alike with four Mikroe Click bus interfaces. Like the
Arduino DUE, this board features the Atmel ATSAM3X8E MCU running at 84
MHz.
-configs/freedom-k28f
+boards/freedom-k28f
This port uses the NXP/FreeScale FREEDOM-K28F development board. This
board uses the Kinetis K28F MK28FN2M0VMI15 Cortex-M4 MCU.
-configs/freedom-k64f
+boards/freedom-k64f
This port uses the NXP/FreeScale FREEDOM-K64F development board. This board
uses the Kinetis K64 MK64FN1M0VLL12 Cortex-M4 MCU.
-configs/freedom-kl25z
-configs/freedom-kl26z
+boards/freedom-kl25z
+boards/freedom-kl26z
These configurations are for the NXP/FreeScale Freedom KL25Z and very similar
KL26Z board. The Freedom-KL25Z features the K25Z120LE3AN chip; the
Freedom-KL26Z has the K26Z128VLH4 chip. These are separate configurations
because of minor differences in the on-board logic. Both include a
built-in SDA debugger.
-configs/hymini-stm32v
+boards/hymini-stm32v
A configuration for the HY-Mini STM32v board. This board is based on the
STM32F103VCT chip.
-configs/kwikstik-k40.
+boards/kwikstik-k40.
Kinetis K40 Cortex-M4 MCU. This port uses the NXP/FreeScale KwikStik-K40
development board.
-configs/launchxl-tms57004
+boards/launchxl-tms57004
TI Hercules TMS570LS04x/03x LaunchPad Evaluation Kit (LAUNCHXL-TMS57004)
featuring the Hercules TMS570LS0432PZ chip.
-configs/lincoln60
+boards/lincoln60
NuttX port to the Micromint Lincoln 60 board.
-configs/lm3s6432-s2e
+boards/lm3s6432-s2e
Stellaris RDK-S2E Reference Design Kit and the MDL-S2E Ethernet to
Serial module.
-configs/lm3s6965-ek
+boards/lm3s6965-ek
Stellaris LM3S6965 Evaluation Kit. This board is based on the
an ARM Cortex-M3 MCU, the Luminary/TI LM3S6965. This OS is built with the
arm-nuttx-elf toolchain*. STATUS: This port is complete and mature.
-configs/lm3s8962-ek
+boards/lm3s8962-ek
Stellaris LMS38962 Evaluation Kit.
-configs/lm4f120-launchpad
+boards/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
Instruments.
-configs/lpcxpresso-lpc1768
+boards/lpcxpresso-lpc1768
Embedded Artists base board with NXP LPCExpresso LPC1768. This board
is based on the NXP LPC1768. The Code Red toolchain is used by default.
STATUS: Under development.
-configs/lpcxpresso-lpc54628
+boards/lpcxpresso-lpc54628
NXP LPCExpresso LPC54628. This board is based on the NXP LPC54628.
-configs/lpc4330-xplorer
+boards/lpc4330-xplorer
NuttX port to the LPC4330-Xplorer board from NGX Technologies featuring
the NXP LPC4330FET100 MCU
-configs/lpc4337-ws
+boards/lpc4337-ws
NuttX port to the WaveShare LPC4337-ws board featuring the NXP LPC4337JBD144
MCU.
-configs/lpc4357-evb
+boards/lpc4357-evb
NuttX port to the LPC4357-EVB board from Embest featuring the NXP
LPC4357FET256 MCU. Based on the LPC4300 Xplorer port and provided by
Toby Duckworth.
-configs/lpc4370-link2
+boards/lpc4370-link2
NuttX port to the NXP LPC4370-Link2 development board featuring the NXP
LPC4370FET100 MCU. Based on the LPC4300 Xplorer port and provided by
Lok Tep.
-configs/makerlisp
+boards/makerlisp
This port use the MakerLips machine based on an eZ80F091 ez80Acclaim!
Microcontroller, and the Zilog ZDS-II Windows command line tools. The
development environment is Cygwin under Windows. A Windows native
development environment is available but has not been verified.
-configs/maple
+boards/maple
NuttX support for the LeafLab's Maple and Maple Mini boards. These boards
are based on the STM32F103RBT6 chip for the standard version and on the
STM32F103CBT6 for the mini version (See http://leaflabs.com/docs/hardware/maple.html)
-configs/max32660-evsys
+boards/max32660-evsys
The configurations in this directory support the Maxim Integrated
MAX32660-EVSYS board.
-configs/mbed
+boards/mbed
The configurations in this directory support the mbed board (http://mbed.org)
that features the NXP LPC1768 microcontroller. This OS is also built
with the arm-nuttx-elf toolchain*. STATUS: Contributed.
-configs/mcb1700
+boards/mcb1700
Board support for the Keil MCB1700
-configs/metro-m4
+boards/metro-m4
Th configurations in this directory are part of the port of NuttX to the
Adafruit Metro M4. The Metro M4 uses a Arduino form factor and and pinout.
It's powered with an ATSAMD51J19
-configs/mikroe-stm32f4
+boards/mikroe-stm32f4
This is the port of NuttX to the MikroElektronika Mikromedia for STM32F4
development board. Contributed by Ken Petit.
-configs/misoc
+boards/misoc
This directory holds the port to NuttX running on a Qemu LM32 system.
You can find the Qemu setup at https://bitbucket.org/key2/qemu
-configs/mcu123-lpc214x
+boards/mcu123-lpc214x
This port is for the NXP LPC2148 as provided on the mcu123.com
lpc214x development board. This OS is also built with the arm-nuttx-elf
toolchain*. The port supports serial, timer0, spi, and usb.
-configs/micropendous3
+boards/micropendous3
This is a port to the Opendous Micropendous 3 board. This board may
be populated with either an AVR AT90USB646, 647, 1286, or 1287 MCU.
Support is configured for the AT90USB647.
-configs/mirtoo
+boards/mirtoo
This is the port to the DTX1-4000L "Mirtoo" module. This module uses MicroChip
PIC32MX250F128D. See http://www.dimitech.com/ for further information.
-configs/moteino-mega
+boards/moteino-mega
This is placeholder for the LowPowerLab MoteinoMEGA that is based
on the Atmel AVR ATMega1284P MCU. There is not much there yet and what is
there is untested due to tool-related issues.
-configs/moxa
+boards/moxa
Moxa NP51x0 series of 2-port advanced RS-232/422/485 serial device servers.
-configs/ne64badge
+boards/ne64badge
Future Electronics Group NE64 /PoE Badge board based on the
MC9S12NE64 hcs12 cpu. This port uses the m9s12x GCC toolchain.
STATUS: Under development. The port is code-complete but has
not yet been fully tested.
-configs/nrf52-generic
+boards/nrf52-generic
NuttX port to the a generic NRF52. Support is in place for the NRF
PCA10040 board from Nordic Semiconductor or for the Adafruit NRF52
feather, both featuring the NRF52832 MCU.
-configs/ntosd-dm320
+boards/ntosd-dm320
This port uses the Neuros OSD v1.0 Dev Board with a GNU arm-nuttx-elf
toolchain*: see
@@ -448,7 +448,7 @@ configs/ntosd-dm320
STATUS: This port is code complete, verified, and included in the
NuttX 0.2.1 release.
-configs/nucleo-144
+boards/nucleo-144
STMicro Nucleo-144 development board family. Included support for (1) the
Nucleo-F767ZG board featuring the STM32F746ZGT6U MCU. The STM32F746ZGT6U
is a 216MHz Cortex-M7 operation with 1024Kb Flash memory and 320Kb SRAM.
@@ -456,92 +456,92 @@ configs/nucleo-144
STM32F767ZIT6 is a 216MHz Cortex-M7 operation with 2048Kb Flash memory
and 512Kb SRAM.
-configs/nucleo-f072rb
+boards/nucleo-f072rb
STMicro Nucleo F072RB board based on the STMicro STM32F072RBT6 MCU.
-configs/nucleo-f4x1re
+boards/nucleo-f4x1re
STMicro ST Nucleo F401RE and F411RE boards. See
http://mbed.org/platforms/ST-Nucleo-F401RE and
http://developer.mbed.org/platforms/ST-Nucleo-F411RE for more
information about these boards.
-configs/nucleo-f410rb
+boards/nucleo-f410rb
NuttX configuration for the STMicro NucleoF410RB board from ST Micro.
This board features the STM32F410RB 100MHz Cortex-M4 with 128 KB Flash
and 32 KB SRAM.
-configs/nucleo-f303re
+boards/nucleo-f303re
STMicro ST Nucleo F303RE board. Contributed by Paul Alexander Patience.
-configs/nucleo-l073rz
+boards/nucleo-l073rz
STMicro STM32L0 Discovery kit with LoRa/SigFox based on STM32L072CZ MCU.
-configs/nutiny-nuc120
+boards/nutiny-nuc120
This is the port of NuttX to the NuvoTon NuTiny-SDK-NUC120 board. This
board has the NUC120LE3AN chip with a built-in NuLink debugger.
-configs/olimex-efm32g880f128-stk
+boards/olimex-efm32g880f128-stk
This is the port of NuttX to the Olimex EFM32G880F128-STK development
board.
-configs/olimex-lpc1766stk
+boards/olimex-lpc1766stk
This port uses the Olimex LPC1766-STK board and a GNU GCC toolchain* under
Linux or Cygwin. STATUS: Complete and mature.
-configs/olimex-lpc2378
+boards/olimex-lpc2378
This port uses the Olimex-lpc2378 board and a GNU arm-nuttx-elf toolchain* under
Linux or Cygwin. STATUS: ostest and NSH configurations available.
This port for the NXP LPC2378 was contributed by Rommel Marcelo.
-configs/olimex-stm32-h405
+boards/olimex-stm32-h405
This port uses the Olimex STM32 H405 board and a GNU arm-nuttx-elf
toolchain* under Linux or Cygwin. See the http://www.olimex.com for
further information. This board features the STMicro STM32F405RGT6 MCU.
Contributed by Martin Lederhilger.
-configs/olimex-stm32-h407
+boards/olimex-stm32-h407
This port uses the Olimex STM32 H407 board and a GNU arm-nuttx-elf
toolchain* under Linux or Cygwin. See the http://www.olimex.com for
further information. This board features the STMicro STM32F407ZGT6 (144
pins). Contributed by Neil Hancock.
-configs/olimex-stm32-e407
+boards/olimex-stm32-e407
Olimex STM32 E407 board based on the STMicro STM32F407ZGT6 (144pins).
Contributed by Mateusz Szafoni.
-configs/olimex-stm32-p107
+boards/olimex-stm32-p107
This port uses the Olimex STM32-P107 board (STM32F107VC) and a GNU arm-nuttx-elf
toolchain* under Linux or Cygwin. See the https://www.olimex.com/dev/stm32-p107.html
for further information. Contributed by Max Holtzberg.
-configs/olimex-stm32-p207
+boards/olimex-stm32-p207
This port uses the Olimex STM32-P207 board (STM32F207ZE) and a GNU arm-nuttx-elf
toolchain under Linux or Cygwin. See the https://www.olimex.com/dev/stm32-p207.html
for further information. Contributed by Martin Lederhilger.
-configs/olimex-stm32-p407
+boards/olimex-stm32-p407
This port uses the Olimex STM32-P407 board (STM32F407ZG) and a GNU arm-nuttx-elf
toolchain under Linux or Cygwin. See the https://www.olimex.com/dev/stm32-p407.html
for further information.
-configs/olimexino-stm32
+boards/olimexino-stm32
This port uses the Olimexino STM32 board (STM32F103RBT6) and a GNU arm-nuttx-elf
toolchain* under Linux or Cygwin. See the http://www.olimex.com for further\
information. Contributed by David Sidrane.
-configs/olimex-strp711
+boards/olimex-strp711
This port uses the Olimex STR-P711 board and a GNU arm-nuttx-elf toolchain* under
Linux or Cygwin. See the http://www.olimex.com/dev/str-p711.html" for
further information. STATUS: Configurations for the basic OS test and NSH
are complete and verified.
-configs/omnibusf4
+boards/omnibusf4
Flight controllers compatible with the OMINBUSF4 Betaflight target
-configs/or1k
+boards/or1k
Generic OpenRISC board.
-configs/pcduino-a10
+boards/pcduino-a10
This directory contains the port of NuttX to the pcDuino v1 board
See http://www.pcduino.com/ for information about pcDuino Lite, v1,
and v2. These boards are based around the Allwinner A10 Cortex-A8 CPU.
@@ -549,7 +549,7 @@ configs/pcduino-a10
differences are cosmetic. This port was developed on the v1 board, but
the others may be compatible.
-configs/p112
+boards/p112
The P112 is notable because it was the first of the hobbyist single board
computers to reach the production stage. The P112 hobbyist computers
were relatively widespread and inspired other hobbyist centered home brew
@@ -576,22 +576,22 @@ configs/p112
Dave Brooks was successfully funded through Kickstarter for and another
run of P112 boards in November of 2012.
-configs/photon
+boards/photon
A configuration for the Photon Wifi board from Particle Devices
(https://www.particle.io). This board features the STM32F205RGY6 MCU from
STMicro.
-configs/pic32mx-starterkit
+boards/pic32mx-starterkit
This directory contains the port of NuttX to the Microchip PIC32 Ethernet
Starter Kit (DM320004) with the Multimedia Expansion Board (MEB, DM320005).
See www.microchip.com for further information.
-configs/pic32mx7mmb
+boards/pic32mx7mmb
This directory will (eventually) contain the port of NuttX to the
Mikroelektronika PIC32MX7 Multimedia Board (MMB). See
http://www.mikroe.com/ for further information.
-configs/pic32mz-starterkit
+boards/pic32mz-starterkit
This directory contains the port of NuttX to the Microchip PIC32MZ
Embedded Connectivity (EC) Starter Kit. There are two configurations of
the starter kit:
@@ -603,26 +603,26 @@ configs/pic32mz-starterkit
See www.microchip.com for further information.
-configs/pnev5180b
+boards/pnev5180b
NXP Semiconductors' PN5180 NFC Frontend Development Kit. This board is
based on the NXP LPC1769 MCU.
-configs/qemu-i486
+boards/qemu-i486
Port of NuttX to QEMU in i486 mode. This port will also run on real i486
hardwared (Google the Bifferboard).
-configs/nr5m100-nexys4
+boards/nr5m100-nexys4
Port of NuttX to RISC-V platform on IQ-Analog NR5M100 RISC-V FPGA platform.
-configs/sabre-6quad
+boards/sabre-6quad
This directory holds a port of NuttX to the NXP/Freescale Sabre board
featuring the iMX 6Quad CPU.
-configs/sama5d2-xult
+boards/sama5d2-xult
This is the port of NuttX to the Atmel SAMA5D2-Xplained Ultra development
board. This board features the Atmel SAMA5D27. See http://www.atmel.com.
-configs/sama5d3x-ek
+boards/sama5d3x-ek
This is the port of NuttX to the Atmel SAMA5D3x-EK development boards
(where x=1,3,4, or 5). These boards feature the Atmel SAMA5D3
microprocessors. Four different SAMA5D3x-EK kits are available
@@ -637,146 +637,146 @@ configs/sama5d3x-ek
are supported by NuttX with a simple reconfiguration of the processor
type.
-configs/sama5d3-xplained
+boards/sama5d3-xplained
This is the port of NuttX to the Atmel SAMA5D3x-Xplained development board.
This board features the Atmel SAMA5D36. See
http://www.atmel.com/devices/sama5d36.aspx.
-configs/sama5d4-ek
+boards/sama5d4-ek
This is the port of NuttX to the Atmel SAMA5D4-EK development board.
This board features the Atmel SAMA5D44. See http://www.atmel.com.
-configs/samd20-xplained
+boards/samd20-xplained
The port of NuttX to the Atmel SAMD20-Xplained Pro development board. This
board features the ATSAMD20J18A MCU (Cortex-M0+ with 256KB of FLASH and
32KB of SRAM).
-configs/samd21-xplained
+boards/samd21-xplained
The port of NuttX to the Atmel SAMD21-Xplained Pro development board. This
board features the ATSAMD21J18A MCU (Cortex-M0+ with 256KB of FLASH and
32KB of SRAM).
-configs/sam3u-ek
+boards/sam3u-ek
The port of NuttX to the Atmel SAM3U-EK development board.
-configs/sam4cmp-db
+boards/sam4cmp-db
The port of NuttX to the Atmel SAM4CMP-DB development board.
-configs/sam4e-ek
+boards/sam4e-ek
The port of NuttX to the Atmel SAM4E-EK development board. This board
features the SAM4E16 MCU running at up to 120MHz.
-configs/sam4l-xplained
+boards/sam4l-xplained
The port of NuttX to the Atmel SAM4L-Xplained development board.
-configs/sam4s-xplained
+boards/sam4s-xplained
The port of NuttX to the Atmel SAM4S-Xplained development board.
-configs/sam4s-xplained-pro
+boards/sam4s-xplained-pro
The port of NuttX to the Atmel SAM4S-Xplained Pro development board.
-configs/same70-xplained
+boards/same70-xplained
The port of NuttX to the Atmel SAME70 Xplained evaluation board.
-configs/samv71-xult
+boards/samv71-xult
The port of NuttX to the Atmel SAMV71 Xplained Ultra evaluation board.
-configs/sim
+boards/sim
A user-mode port of NuttX to the x86 Linux platform is available.
The purpose of this port is primarily to support OS feature development.
This port does not support interrupts or a real timer (and hence no
round robin scheduler) Otherwise, it is complete.
-configs/shenzhou
+boards/shenzhou
This is the port of NuttX to the Shenzhou development board from
www.armjishu.com. This board features the STMicro STM32F107VCT MCU.
-configs/skp16c26
+boards/skp16c26
Renesas M16C processor on the Renesas SKP16C26 StarterKit. This port
uses the GNU m32c toolchain. STATUS: The port is complete but untested
due to issues with compiler internal errors.
-configs/stm3210e-eval
+boards/stm3210e-eval
STMicro STM3210E-EVAL development board based on the STMicro STM32F103ZET6
microcontroller (ARM Cortex-M3). This port uses the GNU Cortex-M3
toolchain.
-configs/stm3220g-eval
+boards/stm3220g-eval
STMicro STM3220G-EVAL development board based on the STMicro STM32F407IG
microcontroller (ARM Cortex-M3).
-configs/stm3240g-eval
+boards/stm3240g-eval
STMicro STM3240G-EVAL development board based on the STMicro STM32F103ZET6
microcontroller (ARM Cortex-M4 with FPU). This port uses a GNU Cortex-M4
toolchain (such as CodeSourcery).
-configs/stm32butterfly2
+boards/stm32butterfly2
Kamami stm32butterfly2 development board with optional ETH phy. See
https://kamami.pl/zestawy-uruchomieniowe-stm32/178507-stm32butterfly2.html
-configs/stm32f051-discovery
+boards/stm32f051-discovery
STMicro STM32F051-Discovery board based on the STMicro ARCH_CHIP_STM32F051R8
MCU.
-configs/stm32f072-discovery
+boards/stm32f072-discovery
STMicro STM32F072-Discovery board based on the STMicro ARCH_CHIP_STM32F072RB
MCU.
-configs/stm32f103-minimum
+boards/stm32f103-minimum
Generic STM32F103C8T6 Minimum ARM Development Board.
-configs/stm32f4discovery
+boards/stm32f4discovery
STMicro STM32F4-Discovery board based on the STMIcro STM32F407VGT6 MCU.
-configs/stm32f411e-disco
+boards/stm32f411e-disco
This is a minimal configuration that supports low-level test of the
STMicro STM32F411E-Discovery Board.
-configs/stm32f429i-disco
+boards/stm32f429i-disco
STMicro STM32F429I-Discovery board based on the STMicro STM32F429ZIT6 MCU.
-configs/stm32f746g-disco
+boards/stm32f746g-disco
STMicro STM32F746G-DISCO development board featuring the STM32F746NGH6
MCU. The STM32F746NGH6 is a 216MHz Cortex-M7 operation with 1024Kb Flash
memory and 300Kb SRAM.
-configs/stm32f746g-ws
+boards/stm32f746g-ws
Waveshare STM32F746 development board featuring the STM32F746IG MCU.
-configs/stm32l476-mdk
+boards/stm32l476-mdk
Motorola Mods Development Board (MDK) features STM32L476ME MCU.
The STM32L476ME is a Cortex-M4 optimised for low-power operation
at up to 80MHz operation with 1024Kb Flash memory and 96+32Kb SRAM.
-configs/stm32f769i-disco
+boards/stm32f769i-disco
NuttX configurations for the STMicro STM32F769I-DISCO development board
featuring the STM32F769NIH6 MCU. The STM32F769NIH6 is a 216MHz Cortex-M7
operating with 2048K Flash memory and 512Kb SRAM.
-configs/stm32l476vg-disco
+boards/stm32l476vg-disco
STMicro STM32L476VG_DISCO development board featuring the STM32L476VG
MCU. The STM32L476VG is a Cortex-M4 optimised for low-power operation
at up to 80MHz operation with 1024Kb Flash memory and 96+32Kb SRAM.
-configs/stm32ldiscovery
+boards/stm32ldiscovery
STMicro STM32L-Discovery board based on the STMicro STM32L152RB MCU.
-configs/stm32vldiscovery
+boards/stm32vldiscovery
STMicro STM32VL-Discovery board based on the STMicro STM32F100RB MCU.
-configs/sure-pic32mx
+boards/sure-pic32mx
The "Advanced USB Storage Demo Board," Model DB-DP11215, from Sure
Electronics (http://www.sureelectronics.net/). This board features
the MicroChip PIC32MX440F512H. See also
http://www.sureelectronics.net/goods.php?id=1168 for further
information about the Sure DB-DP11215 board.
-configs/teensy-2.0
+boards/teensy-2.0
This is the port of NuttX to the PJRC Teensy++ 2.0 board. This board is
developed by http://pjrc.com/teensy/. The Teensy++ 2.0 is based
on an Atmel AT90USB1286 MCU.
-configs/teensy-3.x
+boards/teensy-3.x
This is the port of NuttX to the Teensy-3.1 from PJRC
(https://www.pjrc.com/). The Teensy-3.1 features the Freescale
MK30DX256VLH7 chip (now NXP). The MK30DX256VLH7 is a 64-pin Cortex-M4
@@ -791,36 +791,36 @@ configs/teensy-3.x
Teensy-3.0). the primary difference is that the Teensy 3.0 has a
MK30DX128VLH5 with slightly less capability.
-configs/teensy-lc
+boards/teensy-lc
This is the port of nuttx for the Teensy LC board. The Teensy LC
is a DIP style breakout board for the MKL25Z64 and comes with a USB
based bootloader.
-configs/tm4c123g-launchpad
+boards/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
Instruments.
-configs/tm4c1294-launchpad
+boards/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
Instruments.
-configs/tms570ls31x-usb-kit
+boards/tms570ls31x-usb-kit
TI Hercules TMS570LS31xx Evaluation Kit (TMDS570ls31xx USB Kit)
featuring the Hercules TMS570LS3137ZWT chip.
-configs/twr-k60n512
+boards/twr-k60n512
Kinetis K60 Cortex-M4 MCU. This port uses the FreeScale TWR-K60N512
development board.
-configs/twr-k64f120m
+boards/twr-k64f120m
Kinetis K64 Cortex-M4 MCU. This port uses the FreeScale TWR-K64F120M
development board.
-configs/ubw32
+boards/ubw32
This is the port to the Sparkfun UBW32 board. This port uses the original v2.4
board which is based on the MicroChip PIC32MX460F512L. See
@@ -828,11 +828,11 @@ configs/ubw32
with this board http://www.sparkfun.com/products/9713. See also
http://www.schmalzhaus.com/UBW32/.
-configs/us7032evb1
+boards/us7032evb1
This is a port of the Hitachi SH-1 on the Hitachi SH-1/US7032EVB1 board.
STATUS: Work has just began on this port.
-configs/viewtool-stm32f107
+boards/viewtool-stm32f107
NuttX configurations for the ViewTool STM32F103/F107 V1.2 board. This
board may be fitted with either: (1) STM32F107VCT6 or (2) STM32F103VCT6.
See http://www.viewtool.com/ for further information.
@@ -840,32 +840,32 @@ configs/viewtool-stm32f107
config/xmc4500-relax
Infineon XMC4000 Relax Lite v1
-configs/z16f2800100zcog
+boards/z16f2800100zcog
z16f Microcontroller. This port use the Zilog z16f2800100zcog
development kit and the Zilog ZDS-II Windows command line tools. The
development environment is Cygwin under WinXP.
-configs/z80sim
+boards/z80sim
z80 Microcontroller. This port uses a Z80 instruction set simulator
called z80sim. This port also uses the SDCC toolchain
(http://sdcc.sourceforge.net/") (verified with version 2.6.0).
-configs/z8encore000zco
+boards/z8encore000zco
z8Encore! Microcontroller. This port use the Zilog z8encore000zco
development kit, Z8F6403 part, and the Zilog ZDS-II Windows command line
tools. The development environment is Cygwin under WinXP.
-configs/z8f64200100kit
+boards/z8f64200100kit
z8Encore! Microcontroller. This port use the Zilog z8f64200100kit
development kit, Z8F6423 part, and the Zilog ZDS-II Windows command line
tools. The development environment is Cygwin under WinXP.
-configs/zp214xpa
+boards/zp214xpa
This port is for the NXP LPC2148 as provided on the The0.net
ZPA213X/4XPA development board. Includes support for the
UG-2864AMBAG01 OLED also from The0.net
-configs/zkit-arm-1769
+boards/zkit-arm-1769
Zilogic System's ARM development Kit, ZKIT-ARM-1769. This board is based
on the NXP LPC1769. The Nuttx Buildroot toolchain is used by default.
@@ -874,8 +874,8 @@ Configuring NuttX
Configuring NuttX requires only copying
- configs///Make.def to ${TOPDIR}/Make.defs
- configs///defconfig to ${TOPDIR}/.config
+ boards///Make.def to ${TOPDIR}/Make.defs
+ boards///defconfig to ${TOPDIR}/.config
tools/configure.sh
There is a script that automates these steps. The following steps will
diff --git a/boards/amber/README.txt b/boards/amber/README.txt
index 164a1e254a..50a23cac48 100644
--- a/boards/amber/README.txt
+++ b/boards/amber/README.txt
@@ -289,7 +289,7 @@ NuttX buildroot Toolchain
4. cd /buildroot
- 5. cp configs/avr-defconfig-4.5.2 .config
+ 5. cp boards/avr-defconfig-4.5.2 .config
6. make oldconfig
@@ -298,7 +298,7 @@ NuttX buildroot Toolchain
8. Make sure that the PATH variable includes the path to the newly built
binaries.
- See the file configs/README.txt in the buildroot source tree. That has more
+ See the file boards/README.txt in the buildroot source tree. That has more
detailed PLUS some special instructions that you will need to follow if you
are building a toolchain for Cygwin under Windows.
@@ -388,7 +388,7 @@ Amber Web Server Configuration Options
CONFIG_ARCH_CHIP_ATMEGA128=y
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=amber
diff --git a/boards/amber/scripts/amber.ld b/boards/amber/scripts/amber.ld
index c7639e964d..354bfe6636 100644
--- a/boards/amber/scripts/amber.ld
+++ b/boards/amber/scripts/amber.ld
@@ -1,5 +1,5 @@
/**************************************************************************************
- * configs/amber/scripts/amber.ld
+ * boards/amber/scripts/amber.ld
*
* Copyright (C) 2011, 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/arduino-due/README.txt b/boards/arduino-due/README.txt
index 35b68618b6..9209746ab2 100644
--- a/boards/arduino-due/README.txt
+++ b/boards/arduino-due/README.txt
@@ -561,7 +561,7 @@ Arduino DUE-specific Configuration Options
CONFIG_ARCH_CHIP_SAM3X
CONFIG_ARCH_CHIP_ATSAM3X8E
- CONFIG_ARCH_BOARD - Identifies the configs/ subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=arduino-due (for the Arduino Due development board)
diff --git a/boards/arduino-due/scripts/arduino-due.ld b/boards/arduino-due/scripts/arduino-due.ld
index 4b10d82146..fab973da79 100644
--- a/boards/arduino-due/scripts/arduino-due.ld
+++ b/boards/arduino-due/scripts/arduino-due.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/arduino-due/scripts/arduino-due.ld
+ * boards/arduino-due/scripts/arduino-due.ld
*
* Copyright (C) 2013, 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/arduino-mega2560/scripts/flash.ld b/boards/arduino-mega2560/scripts/flash.ld
index a678b45465..4f087d31d1 100644
--- a/boards/arduino-mega2560/scripts/flash.ld
+++ b/boards/arduino-mega2560/scripts/flash.ld
@@ -1,5 +1,5 @@
/*******************************************************************************
- * configs/arduino-mega2560/scripts/flash.ld
+ * boards/arduino-mega2560/scripts/flash.ld
*
* Copyright (C) 2015 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/avr32dev1/README.txt b/boards/avr32dev1/README.txt
index 647de6f7ba..f96a534274 100644
--- a/boards/avr32dev1/README.txt
+++ b/boards/avr32dev1/README.txt
@@ -34,7 +34,7 @@ The only GPIO pin usage is for LEDs (2) and Buttons (2):
PIN 24 PB2 KEY1
PIN 25 PB3 KEY2
-(See configs/avr32dev1/src/avr32dev1.h). And also for
+(See boards/avr32dev1/src/avr32dev1.h). And also for
crystals (4), JTAG (1), and USB (1):
PIN 30 PA11 XIN32
@@ -83,7 +83,7 @@ RS-232 drivers or connectors on board. I use an off-board MAX232
module that I got on eBay (search for MAX232 if you want to find
one). I connect the MAX232 board as follows:
-In configs/avr32dev/include/board.h:
+In boards/avr32dev/include/board.h:
#define PINMUX_USART1_RXD PINMUX_USART1_RXD_1
#define PINMUX_USART1_TXD PINMUX_USART1_TXD_1
@@ -352,7 +352,7 @@ AVR32DEV1 Configuration Options
CONFIG_ARCH_CHIP_AT32UC3B0256
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=avr32dev1 (for the AV32DEV1 board)
diff --git a/boards/avr32dev1/scripts/avr32dev1.ld b/boards/avr32dev1/scripts/avr32dev1.ld
index 94d87a9fbf..ceb5e1cf64 100644
--- a/boards/avr32dev1/scripts/avr32dev1.ld
+++ b/boards/avr32dev1/scripts/avr32dev1.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/avr32dev1/scripts/avr32dev1.ld
+ * boards/avr32dev1/scripts/avr32dev1.ld
*
* Copyright (C) 2010, 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/axoloti/scripts/gnu-elf.ld b/boards/axoloti/scripts/gnu-elf.ld
index 45590f51b3..764b03fde8 100644
--- a/boards/axoloti/scripts/gnu-elf.ld
+++ b/boards/axoloti/scripts/gnu-elf.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/axoloti/scripts/gnu-elf.ld
+ * boards/axoloti/scripts/gnu-elf.ld
*
* Copyright (C) 2012 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/axoloti/scripts/kernel-space.ld b/boards/axoloti/scripts/kernel-space.ld
index 68287ec766..cb2e46daf2 100644
--- a/boards/axoloti/scripts/kernel-space.ld
+++ b/boards/axoloti/scripts/kernel-space.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/axoloti/scripts/kernel-space.ld
+ * boards/axoloti/scripts/kernel-space.ld
*
* Copyright (C) 2013 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/axoloti/scripts/ld.script b/boards/axoloti/scripts/ld.script
index 135aaf128c..66626cbd5c 100644
--- a/boards/axoloti/scripts/ld.script
+++ b/boards/axoloti/scripts/ld.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/axoloti/scripts/ld.script
+ * boards/axoloti/scripts/ld.script
*
* Copyright (C) 2019 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/axoloti/scripts/memory.ld b/boards/axoloti/scripts/memory.ld
index 109a893f97..7a9a268b08 100644
--- a/boards/axoloti/scripts/memory.ld
+++ b/boards/axoloti/scripts/memory.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/axoloti/scripts/memory.ld
+ * boards/axoloti/scripts/memory.ld
*
* Copyright (C) 2013 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
@@ -48,7 +48,7 @@
* For MPU support, the kernel-mode NuttX section is assumed to be 128Kb of
* FLASH and 4Kb of SRAM. That is an excessive amount for the kernel which
* should fit into 64KB and, of course, can be optimized as needed (See
- * also configs/axoloti/scripts/kernel-space.ld). Allowing the
+ * also boards/axoloti/scripts/kernel-space.ld). Allowing the
* additional does permit addition debug instrumentation to be added to the
* kernel space without overflowing the partition.
*
diff --git a/boards/axoloti/scripts/user-space.ld b/boards/axoloti/scripts/user-space.ld
index 0197a91896..d0c03487ce 100644
--- a/boards/axoloti/scripts/user-space.ld
+++ b/boards/axoloti/scripts/user-space.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/axoloti/scripts/user-space.ld
+ * boards/axoloti/scripts/user-space.ld
*
* Copyright (C) 2013 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/b-l072z-lrwan1/scripts/ld.script b/boards/b-l072z-lrwan1/scripts/ld.script
index c65394ecf6..dc2518110f 100644
--- a/boards/b-l072z-lrwan1/scripts/ld.script
+++ b/boards/b-l072z-lrwan1/scripts/ld.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/b-l072z-lrwan1/scripts/ld.script
+ * boards/b-l072z-lrwan1/scripts/ld.script
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Authors: Gregory Nutt
diff --git a/boards/b-l475e-iot01a/scripts/flash.ld b/boards/b-l475e-iot01a/scripts/flash.ld
index 1812d08126..44bdc44f33 100644
--- a/boards/b-l475e-iot01a/scripts/flash.ld
+++ b/boards/b-l475e-iot01a/scripts/flash.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/b-l475e-iot01a/scripts/flash.ld
+ * boards/b-l475e-iot01a/scripts/flash.ld
*
* Copyright (C) 2017 Gregory Nutt. All rights reserved.
*
diff --git a/boards/bambino-200e/README.txt b/boards/bambino-200e/README.txt
index 7855135611..b172bdbbfe 100644
--- a/boards/bambino-200e/README.txt
+++ b/boards/bambino-200e/README.txt
@@ -126,7 +126,7 @@ the following lines in each Make.defs file:
Configuration Changes
---------------------
-Below are all of the configuration changes that I had to make to configs/stm3240g-eval/nsh2
+Below are all of the configuration changes that I had to make to boards/stm3240g-eval/nsh2
in order to successfully build NuttX using the Atollic toolchain WITH FPU support:
-CONFIG_ARCH_FPU=n : Enable FPU support
@@ -173,7 +173,7 @@ Bambino-200e Configuration Options
CONFIG_ARCH_CHIP_LPC4330=y
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=bambino-200e (for the Bambino-200e board)
diff --git a/boards/bambino-200e/knsh/defconfig b/boards/bambino-200e/knsh/defconfig
index f5119ecdd0..789ce212c9 100644
--- a/boards/bambino-200e/knsh/defconfig
+++ b/boards/bambino-200e/knsh/defconfig
@@ -38,7 +38,7 @@ CONFIG_NSH_FILEIOSIZE=512
CONFIG_NSH_LINELEN=64
CONFIG_NSH_READLINE=y
CONFIG_NUTTX_USERSPACE=0x14040000
-CONFIG_PASS1_BUILDIR="configs/bambino-200e/kernel"
+CONFIG_PASS1_BUILDIR="boards/bambino-200e/kernel"
CONFIG_PREALLOC_MQ_MSGS=4
CONFIG_PREALLOC_TIMERS=4
CONFIG_PREALLOC_WDOGS=4
diff --git a/boards/bambino-200e/scripts/memory.ld b/boards/bambino-200e/scripts/memory.ld
index 3beb58402b..c5af303f0f 100644
--- a/boards/bambino-200e/scripts/memory.ld
+++ b/boards/bambino-200e/scripts/memory.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/stm32f4discovery/scripts/memory.ld
+ * boards/stm32f4discovery/scripts/memory.ld
*
* Copyright (C) 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
@@ -47,7 +47,7 @@
* For MPU support, the kernel-mode NuttX section is assumed to be 128Kb of
* FLASH and 4Kb of SRAM. That is an excessive amount for the kernel which
* should fit into 64KB and, of course, can be optimized as needed (See
- * also configs/stm32f4discovery/scripts/kernel-space.ld). Allowing the
+ * also boards/stm32f4discovery/scripts/kernel-space.ld). Allowing the
* additional does permit addition debug instrumentation to be added to the
* kernel space without overflowing the partition.
*
diff --git a/boards/bambino-200e/scripts/ramconfig.ld b/boards/bambino-200e/scripts/ramconfig.ld
index 0f7d0228db..fcdb16834f 100644
--- a/boards/bambino-200e/scripts/ramconfig.ld
+++ b/boards/bambino-200e/scripts/ramconfig.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/bambino-200e/scripts/ramconfig.ld
+ * boards/bambino-200e/scripts/ramconfig.ld
*
* Copyright (C) 2016 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/bambino-200e/scripts/spificonfig.ld b/boards/bambino-200e/scripts/spificonfig.ld
index e1f744eb0b..6f516cf5be 100644
--- a/boards/bambino-200e/scripts/spificonfig.ld
+++ b/boards/bambino-200e/scripts/spificonfig.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/bambino-200e/scripts/spificonfig.ld
+ * boards/bambino-200e/scripts/spificonfig.ld
*
* Copyright (C) 2012 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/bambino-200e/scripts/user-space.ld b/boards/bambino-200e/scripts/user-space.ld
index 3f98a40edf..147070f3d6 100644
--- a/boards/bambino-200e/scripts/user-space.ld
+++ b/boards/bambino-200e/scripts/user-space.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/stm32f4discovery/scripts/user-space.ld
+ * boards/stm32f4discovery/scripts/user-space.ld
*
* Copyright (C) 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/beaglebone-black/scripts/sdram.ld b/boards/beaglebone-black/scripts/sdram.ld
index cba0e6a09b..995e4e210d 100644
--- a/boards/beaglebone-black/scripts/sdram.ld
+++ b/boards/beaglebone-black/scripts/sdram.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/beaglebone-black/scripts/sdram.ld
+ * boards/beaglebone-black/scripts/sdram.ld
*
* Copyright (C) 2018 Petro Karashchenko. All rights reserved.
* Author: Petro Karashchenko
diff --git a/boards/c5471evm/README.txt b/boards/c5471evm/README.txt
index 6e4047bbef..a8ea362900 100644
--- a/boards/c5471evm/README.txt
+++ b/boards/c5471evm/README.txt
@@ -21,7 +21,7 @@ Toolchain
4. cd /buildroot
- 5. cp configs/arm-defconfig .config
+ 5. cp boards/arm-defconfig .config
6. make oldconfig
@@ -63,7 +63,7 @@ ARM/C5471-specific Configuration Options
CONFIG_ARCH_CHIP_C5471
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=c5471evm (for the Spectrum Digital C5471 EVM)
diff --git a/boards/c5471evm/scripts/ld.script b/boards/c5471evm/scripts/ld.script
index 193241d91d..d9f060947f 100644
--- a/boards/c5471evm/scripts/ld.script
+++ b/boards/c5471evm/scripts/ld.script
@@ -1,5 +1,5 @@
/************************************************************
- * configs/c5471evm/scripts/ld.script
+ * boards/c5471evm/scripts/ld.script
*
* Copyright (C) 2007, 2011-2012, 2014 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/clicker2-stm32/README.txt b/boards/clicker2-stm32/README.txt
index 3d5b5648e5..c294914eba 100644
--- a/boards/clicker2-stm32/README.txt
+++ b/boards/clicker2-stm32/README.txt
@@ -75,7 +75,7 @@ Using JTAG
The Clicker2 comes with the mikroBootloader installed. That bootloader
has not been used and is possibly incompatible with the Clicker2-STM32
- linker script at configs/clicker2-stm32/scripts/flash.ld. Often code must
+ linker script at boards/clicker2-stm32/scripts/flash.ld. Often code must
be built to execute at an offset in to FLASH when a bootloader is used.
Certainly that is the case for the ST-Micro DFU bootloader but I am not
aware of the requirements for use with the mikroBootloader.
diff --git a/boards/clicker2-stm32/knsh/defconfig b/boards/clicker2-stm32/knsh/defconfig
index 6ecbefb78d..9e1f7f3bb0 100644
--- a/boards/clicker2-stm32/knsh/defconfig
+++ b/boards/clicker2-stm32/knsh/defconfig
@@ -39,7 +39,7 @@ CONFIG_NSH_FILEIOSIZE=512
CONFIG_NSH_LINELEN=64
CONFIG_NSH_READLINE=y
CONFIG_NUTTX_USERSPACE=0x08020000
-CONFIG_PASS1_BUILDIR="configs/clicker2-stm32/kernel"
+CONFIG_PASS1_BUILDIR="boards/clicker2-stm32/kernel"
CONFIG_PREALLOC_MQ_MSGS=4
CONFIG_PREALLOC_TIMERS=4
CONFIG_PREALLOC_WDOGS=8
diff --git a/boards/clicker2-stm32/scripts/flash.ld b/boards/clicker2-stm32/scripts/flash.ld
index 59331788d0..c3b11db486 100644
--- a/boards/clicker2-stm32/scripts/flash.ld
+++ b/boards/clicker2-stm32/scripts/flash.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/clicker2-stm32/scripts/flash.ld
+ * boards/clicker2-stm32/scripts/flash.ld
*
* Copyright (C) 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/clicker2-stm32/scripts/gnu-elf.ld b/boards/clicker2-stm32/scripts/gnu-elf.ld
index d10b5aaf89..fad585583c 100644
--- a/boards/clicker2-stm32/scripts/gnu-elf.ld
+++ b/boards/clicker2-stm32/scripts/gnu-elf.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/clicker2-stm32/scripts/gnu-elf.ld
+ * boards/clicker2-stm32/scripts/gnu-elf.ld
*
* Copyright (C) 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/clicker2-stm32/scripts/kernel-space.ld b/boards/clicker2-stm32/scripts/kernel-space.ld
index 7ae056b8dc..a394f4a5eb 100644
--- a/boards/clicker2-stm32/scripts/kernel-space.ld
+++ b/boards/clicker2-stm32/scripts/kernel-space.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/clicker2-stm32/scripts/kernel-space.ld
+ * boards/clicker2-stm32/scripts/kernel-space.ld
*
* Copyright (C) 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/clicker2-stm32/scripts/memory.ld b/boards/clicker2-stm32/scripts/memory.ld
index 99b2a1c585..a3c0d547c4 100644
--- a/boards/clicker2-stm32/scripts/memory.ld
+++ b/boards/clicker2-stm32/scripts/memory.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/clicker2-stm32/scripts/memory.ld
+ * boards/clicker2-stm32/scripts/memory.ld
*
* Copyright (C) 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
@@ -47,7 +47,7 @@
* For MPU support, the kernel-mode NuttX section is assumed to be 128Kb of
* FLASH and 4Kb of SRAM. That is an excessive amount for the kernel which
* should fit into 64KB and, of course, can be optimized as needed (See
- * also configs/clicker2-stm32/scripts/kernel-space.ld). Allowing the
+ * also boards/clicker2-stm32/scripts/kernel-space.ld). Allowing the
* additional does permit addition debug instrumentation to be added to the
* kernel space without overflowing the partition.
*
diff --git a/boards/clicker2-stm32/scripts/user-space.ld b/boards/clicker2-stm32/scripts/user-space.ld
index b7e9f0f8f8..50fb158ac8 100644
--- a/boards/clicker2-stm32/scripts/user-space.ld
+++ b/boards/clicker2-stm32/scripts/user-space.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/clicker2-stm32/scripts/user-space.ld
+ * boards/clicker2-stm32/scripts/user-space.ld
*
* Copyright (C) 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/cloudctrl/README.txt b/boards/cloudctrl/README.txt
index 1fba253e11..1417a6e619 100644
--- a/boards/cloudctrl/README.txt
+++ b/boards/cloudctrl/README.txt
@@ -221,7 +221,7 @@ Cloudctrl-specific Configuration Options
CONFIG_ARCH_BOARD_STM32_CUSTOM_CLOCKCONFIG=n
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=shenzhou (for the Cloudctrl development board)
@@ -498,7 +498,7 @@ Where is one of the following:
ADC_IN8 (PB0) CON5 CN14 Pin2
ADC_IN9 (PB1) CON5 CN14 Pin1
- The signal selection is hard-coded in configs/shenzhou/src/up_adc.c: The
+ The signal selection is hard-coded in boards/shenzhou/src/up_adc.c: The
potentiometer input (only) is selected.
These selections will enable sampling the potentiometer input at 100Hz using
diff --git a/boards/cloudctrl/scripts/cloudctrl-dfu.ld b/boards/cloudctrl/scripts/cloudctrl-dfu.ld
index 13f666cd47..571fc4b255 100644
--- a/boards/cloudctrl/scripts/cloudctrl-dfu.ld
+++ b/boards/cloudctrl/scripts/cloudctrl-dfu.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/cloudctrl/scripts/cloudctrl-dfu.ld
+ * boards/cloudctrl/scripts/cloudctrl-dfu.ld
*
* Copyright (C) 2012 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/cloudctrl/scripts/cloudctrl.ld b/boards/cloudctrl/scripts/cloudctrl.ld
index 5ed650a3be..a076882129 100644
--- a/boards/cloudctrl/scripts/cloudctrl.ld
+++ b/boards/cloudctrl/scripts/cloudctrl.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/cloudctrl/scripts/cloudctrl.ld
+ * boards/cloudctrl/scripts/cloudctrl.ld
*
* Copyright (C) 2012 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/demo9s12ne64/README.txt b/boards/demo9s12ne64/README.txt
index 25c59f3f95..76be2562cf 100644
--- a/boards/demo9s12ne64/README.txt
+++ b/boards/demo9s12ne64/README.txt
@@ -131,7 +131,7 @@ NuttX Buildroot Toolchain
4. cd /buildroot
- 5. cp configs/m9s12x-defconfig-3.3.6 .config
+ 5. cp boards/m9s12x-defconfig-3.3.6 .config
6. make oldconfig
@@ -145,7 +145,7 @@ NuttX Buildroot Toolchain
8. Make sure that the PATH variable includes the path to the newly built
binaries.
- See the file configs/README.txt in the buildroot source tree. That has more
+ See the file boards/README.txt in the buildroot source tree. That has more
detailed PLUS some special instructions that you will need to follow if you are
building a Cortex-M3 toolchain for Cygwin under Windows.
@@ -276,7 +276,7 @@ HCS12/DEMO9S12NEC64-specific Configuration Options
CONFIG_ARCH_CHIP_MCS92S12NEC64
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=demo9s12nec64
diff --git a/boards/demo9s12ne64/scripts/demo9s12ne64-banked.ld b/boards/demo9s12ne64/scripts/demo9s12ne64-banked.ld
index f073537185..2c42493d89 100644
--- a/boards/demo9s12ne64/scripts/demo9s12ne64-banked.ld
+++ b/boards/demo9s12ne64/scripts/demo9s12ne64-banked.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/demo9s12ne64/ostest/demo9s12ne64-banked.ld
+ * boards/demo9s12ne64/ostest/demo9s12ne64-banked.ld
*
* Copyright (C) 2009, 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/demo9s12ne64/scripts/demo9s12ne64-unbanked.ld b/boards/demo9s12ne64/scripts/demo9s12ne64-unbanked.ld
index 09479e0134..bc507652fb 100644
--- a/boards/demo9s12ne64/scripts/demo9s12ne64-unbanked.ld
+++ b/boards/demo9s12ne64/scripts/demo9s12ne64-unbanked.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/demo9s12ne64/ostest/demo9s12ne64-banked.ld
+ * boards/demo9s12ne64/ostest/demo9s12ne64-banked.ld
*
* Copyright (C) 2009, 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/dk-tm4c129x/README.txt b/boards/dk-tm4c129x/README.txt
index 827c7d2c56..b757749dcb 100644
--- a/boards/dk-tm4c129x/README.txt
+++ b/boards/dk-tm4c129x/README.txt
@@ -40,7 +40,7 @@ Using OpenOCD and GDB with ICDI
Building OpenOCD under Cygwin:
- Refer to configs/olimex-lpc1766stk/README.txt
+ Refer to boards/olimex-lpc1766stk/README.txt
Installing OpenOCD in Linux:
@@ -56,7 +56,7 @@ Using OpenOCD and GDB with ICDI
I have been using the on-board In-Circuit Debug Interface (ICDI) interface.
OpenOCD requires a configuration file. I keep the one I used last here:
- configs/dk-tm4c129x/tools/dk-tm4c129x.cfg
+ boards/dk-tm4c129x/tools/dk-tm4c129x.cfg
However, the "correct" configuration script to use with OpenOCD may
change as the features of OpenOCD evolve. So you should at least
@@ -74,7 +74,7 @@ Using OpenOCD and GDB with ICDI
- Possibly the value of OPENOCD_PATH and TARGET_PATH
- It assumes that the correct script to use is the one at
- configs/dk-tm4c129x/tools/dk-tm4c129x.cfg
+ boards/dk-tm4c129x/tools/dk-tm4c129x.cfg
Starting OpenOCD
@@ -84,7 +84,7 @@ Using OpenOCD and GDB with ICDI
oocd.sh $PWD
Assuming that you have included the path to the oocd.sh script,
- configs/dk-tm4c129x/tools, in PATH variable.
+ boards/dk-tm4c129x/tools, in PATH variable.
Note that OpenOCD needs to be run with administrator privileges in
some environments (sudo).
@@ -513,7 +513,7 @@ Temperature Sensor
More complex temperature sensor operations are also available. See the IOCTL
commands enumerated in include/nuttx/sensors/lm75.h. Also read the descriptions
of the tiva_tmp100_initialize() and tiva_tmp100_attach() interfaces in the
- arch/board/board.h file (sames as configs/dk-tm4c129x/include/board.h).
+ arch/board/board.h file (sames as boards/dk-tm4c129x/include/board.h).
NSH Command Line Application
----------------------------
@@ -562,7 +562,7 @@ DK-TM4129X Configuration Options
CONFIG_ARCH_CHIP_TM4C129XNC
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=dk-tm4c129x (for the DK-TM4129X)
diff --git a/boards/dk-tm4c129x/scripts/ld.script b/boards/dk-tm4c129x/scripts/ld.script
index 6b5f5179ea..8b8ce1fbee 100644
--- a/boards/dk-tm4c129x/scripts/ld.script
+++ b/boards/dk-tm4c129x/scripts/ld.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/dk-tm4c129x/scripts/ld.script
+ * boards/dk-tm4c129x/scripts/ld.script
*
* Copyright (C) 2014 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/ea3131/README.txt b/boards/ea3131/README.txt
index b76473740a..e85ffb20c8 100644
--- a/boards/ea3131/README.txt
+++ b/boards/ea3131/README.txt
@@ -160,7 +160,7 @@ NuttX buildroot Toolchain
4. cd /buildroot
- 5. cp configs/arm926t-defconfig-4.2.4 .config
+ 5. cp boards/arm926t-defconfig-4.2.4 .config
6. make oldconfig
@@ -169,7 +169,7 @@ NuttX buildroot Toolchain
8. Make sure that the PATH variable includes the path to the newly built
binaries.
- See the file configs/README.txt in the buildroot source tree. That has more
+ See the file boards/README.txt in the buildroot source tree. That has more
detailed PLUS some special instructions that you will need to follow if you are
building a Cortex-M3 toolchain for Cygwin under Windows.
@@ -195,11 +195,11 @@ Image Format
it!
To work around both of these issues, I have created a small program under
- configs/ea3131/tools to add the header. This program can be built under
+ boards/ea3131/tools to add the header. This program can be built under
either Linux or Cygwin (and probably other tool environments as well). That
tool can be built as follows:
- - cd configs/ea3131/tools
+ - cd boards/ea3131/tools
- make
Then, to build the NuttX binary ready to load with the bootloader, just
@@ -216,10 +216,10 @@ Image Format
to mklpc.sh in the final step.
2. You can instruct Symantec to ignore the errors and it will stop quarantining
the NXP program.
- 3. The CRC32 logic in configs/ea3131/tools doesn't seem to work. As a result,
+ 3. The CRC32 logic in boards/ea3131/tools doesn't seem to work. As a result,
the CRC is currently disabled in the header:
- RCS file: /cvsroot/nuttx/nuttx/configs/ea3131/tools/lpchdr.c,v
+ RCS file: /cvsroot/nuttx/nuttx/boards/ea3131/tools/lpchdr.c,v
retrieving revision 1.2
diff -r1.2 lpchdr.c
264c264
@@ -262,7 +262,7 @@ Using OpenOCD and GDB
Then you should be able to start the OpenOCD daemon like:
- configs/ea3131/tools/oocd.sh $PWD
+ boards/ea3131/tools/oocd.sh $PWD
Where it is assumed that you are executing oocd.sh from the top level
directory where NuttX is installed.
@@ -383,16 +383,16 @@ On-Demand Paging
This example uses a two-pass build. The top-level Makefile recognizes the
configuration option CONFIG_BUILD_2PASS and will execute the Makefile in
- configs/ea3131/locked/Makefile to build the first pass object, locked.r.
+ boards/ea3131/locked/Makefile to build the first pass object, locked.r.
This first pass object contains all of the code that must be in the locked
text region. The Makefile in arch/arm/src/Makefile then includes this 1st
- pass in build, positioning it as controlled by configs/ea3131/scripts/pg-ld.script.
+ pass in build, positioning it as controlled by boards/ea3131/scripts/pg-ld.script.
Finishing the Example:
----------------------
This example is incomplete in that it does not have any media to reload the
- page text region from: The file configs/ea3131/src/up_fillpage.c is only
+ page text region from: The file boards/ea3131/src/up_fillpage.c is only
a stub. That logic to actually reload the page from some storage medium
(among other things) would have to be implemented in order to complete this
example. At present, the example works correctly up to the point where
@@ -438,7 +438,7 @@ On-Demand Paging
Alternative:
------------
- I have implemented an alternative within configs/ea3131/src/up_fillpage.c
+ I have implemented an alternative within boards/ea3131/src/up_fillpage.c
which is probably only useful for testing. Here is the usage module
for this alternative
@@ -495,7 +495,7 @@ ARM/EA3131-specific Configuration Options
CONFIG_ARCH_CHIP_LPC3131
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=ea3131
diff --git a/boards/ea3131/locked/ld-locked.script b/boards/ea3131/locked/ld-locked.script
index 334c328c07..a44cdc7ba0 100644
--- a/boards/ea3131/locked/ld-locked.script
+++ b/boards/ea3131/locked/ld-locked.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/ea3131/locked/ld-locked.script
+ * boards/ea3131/locked/ld-locked.script
*
* Copyright (C) 2010 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/ea3131/pgnsh/defconfig b/boards/ea3131/pgnsh/defconfig
index d7d53913ba..e2b222b32a 100644
--- a/boards/ea3131/pgnsh/defconfig
+++ b/boards/ea3131/pgnsh/defconfig
@@ -41,7 +41,7 @@ CONFIG_PAGING_NPPAGED=96
CONFIG_PAGING_NVPAGED=384
CONFIG_PAGING_PAGESIZE=1024
CONFIG_PAGING_STACKSIZE=2048
-CONFIG_PASS1_BUILDIR="configs/ea3131/locked"
+CONFIG_PASS1_BUILDIR="boards/ea3131/locked"
CONFIG_PASS1_OBJECT="locked.r"
CONFIG_PREALLOC_MQ_MSGS=4
CONFIG_PREALLOC_TIMERS=4
diff --git a/boards/ea3131/scripts/ld.script b/boards/ea3131/scripts/ld.script
index 18c4a316ab..4785687cf3 100644
--- a/boards/ea3131/scripts/ld.script
+++ b/boards/ea3131/scripts/ld.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/ea3131/scripts/ld.script
+ * boards/ea3131/scripts/ld.script
*
* Copyright (C) 2010-2012 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/ea3131/scripts/pg-ld.script b/boards/ea3131/scripts/pg-ld.script
index d7c1f1d4d1..888c965395 100644
--- a/boards/ea3131/scripts/pg-ld.script
+++ b/boards/ea3131/scripts/pg-ld.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/ea3131/scripts/pg-ld.script
+ * boards/ea3131/scripts/pg-ld.script
*
* Copyright (C) 2010, 2012 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/ea3152/README.txt b/boards/ea3152/README.txt
index f663f2fdea..33c1b3c1af 100644
--- a/boards/ea3152/README.txt
+++ b/boards/ea3152/README.txt
@@ -159,7 +159,7 @@ NuttX buildroot Toolchain
4. cd /buildroot
- 5. cp configs/arm926t-defconfig-4.2.4 .config
+ 5. cp boards/arm926t-defconfig-4.2.4 .config
6. make oldconfig
@@ -168,7 +168,7 @@ NuttX buildroot Toolchain
8. Make sure that the PATH variable includes the path to the newly built
binaries.
- See the file configs/README.txt in the buildroot source tree. That has more
+ See the file boards/README.txt in the buildroot source tree. That has more
detailed PLUS some special instructions that you will need to follow if you are
building a Cortex-M3 toolchain for Cygwin under Windows.
@@ -194,11 +194,11 @@ Image Format
it!
To work around both of these issues, I have created a small program under
- configs/ea3152/tools to add the header. This program can be built under
+ boards/ea3152/tools to add the header. This program can be built under
either Linux or Cygwin (and probably other tool environments as well). That
tool can be built as follows:
- - cd configs/ea3152/tools
+ - cd boards/ea3152/tools
- make
Then, to build the NuttX binary ready to load with the bootloader, just
@@ -215,10 +215,10 @@ Image Format
to mklpc.sh in the final step.
2. You can instruct Symantec to ignore the errors and it will stop quarantining
the NXP program.
- 3. The CRC32 logic in configs/ea3152/tools doesn't seem to work. As a result,
+ 3. The CRC32 logic in boards/ea3152/tools doesn't seem to work. As a result,
the CRC is currently disabled in the header:
- RCS file: /cvsroot/nuttx/nuttx/configs/ea3152/tools/lpchdr.c,v
+ RCS file: /cvsroot/nuttx/nuttx/boards/ea3152/tools/lpchdr.c,v
retrieving revision 1.2
diff -r1.2 lpchdr.c
264c264
@@ -261,7 +261,7 @@ Using OpenOCD and GDB
Then you should be able to start the OpenOCD daemon like:
- configs/ea3152/tools/oocd.sh $PWD
+ boards/ea3152/tools/oocd.sh $PWD
Where it is assumed that you are executing oocd.sh from the top level
directory where NuttX is installed.
@@ -301,7 +301,7 @@ ARM/EA3152-specific Configuration Options
CONFIG_ARCH_CHIP_LPC3152
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=ea3152
diff --git a/boards/ea3152/scripts/ea3152.ld b/boards/ea3152/scripts/ea3152.ld
index f6d01c92ad..4775ee26fa 100644
--- a/boards/ea3152/scripts/ea3152.ld
+++ b/boards/ea3152/scripts/ea3152.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/ea3152/scripts/ea3152.ld
+ * boards/ea3152/scripts/ea3152.ld
*
* Copyright (C) 2011-2012, 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/eagle100/README.txt b/boards/eagle100/README.txt
index c6f38c49d2..65ea1c3827 100644
--- a/boards/eagle100/README.txt
+++ b/boards/eagle100/README.txt
@@ -91,7 +91,7 @@ Eagle100-specific Configuration Options
CONFIG_ARCH_CHIP_LM3S6918
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=eagle100 (for the MicroMint Eagle-100 development board)
diff --git a/boards/eagle100/scripts/ld.script b/boards/eagle100/scripts/ld.script
index 3dcc209b73..6f72c4b7d6 100644
--- a/boards/eagle100/scripts/ld.script
+++ b/boards/eagle100/scripts/ld.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/eagle100/scripts/ld.script
+ * boards/eagle100/scripts/ld.script
*
* Copyright (C) 2009, 2011-2012 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/efm32-g8xx-stk/scripts/efm32-g8xx-stk.ld b/boards/efm32-g8xx-stk/scripts/efm32-g8xx-stk.ld
index d199bd1e64..4caa3ef9ce 100644
--- a/boards/efm32-g8xx-stk/scripts/efm32-g8xx-stk.ld
+++ b/boards/efm32-g8xx-stk/scripts/efm32-g8xx-stk.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/efm32-g8xx-stk/scripts/efm32-g8xx-stk.ld
+ * boards/efm32-g8xx-stk/scripts/efm32-g8xx-stk.ld
*
* Copyright (C) 2012, 2014, 2017 Gregory Nutt. All rights reserved.
*
diff --git a/boards/efm32gg-stk3700/scripts/ld.script b/boards/efm32gg-stk3700/scripts/ld.script
index 07769aaa87..819258d203 100644
--- a/boards/efm32gg-stk3700/scripts/ld.script
+++ b/boards/efm32gg-stk3700/scripts/ld.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/efm32gg-stk3700/scripts/ld.script
+ * boards/efm32gg-stk3700/scripts/ld.script
*
* Copyright (C) 2014 Gregory Nutt. All rights reserved.
*
diff --git a/boards/ekk-lm3s9b96/README.txt b/boards/ekk-lm3s9b96/README.txt
index af873ceaa2..1ef16dd975 100644
--- a/boards/ekk-lm3s9b96/README.txt
+++ b/boards/ekk-lm3s9b96/README.txt
@@ -98,7 +98,7 @@ Stellaris EKK-LM3S9B96 Evaluation Kit Configuration Options
CONFIG_ARCH_CHIP_LM3S9B96
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=ekk-lm3s9b96 (for the Stellaris EKK-LM3S9b96 Evaluation Kit)
diff --git a/boards/ekk-lm3s9b96/scripts/ekk-lm3s9b96.ld b/boards/ekk-lm3s9b96/scripts/ekk-lm3s9b96.ld
index 40978b93ad..b9095e0fad 100644
--- a/boards/ekk-lm3s9b96/scripts/ekk-lm3s9b96.ld
+++ b/boards/ekk-lm3s9b96/scripts/ekk-lm3s9b96.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/ekk-lm3s9b96/ostest/ekk-lm3s9b96.ld
+ * boards/ekk-lm3s9b96/ostest/ekk-lm3s9b96.ld
*
* Copyright (C) 2012, 2017 Gregory Nutt. All rights reserved.
* Authors: Gregory Nutt
diff --git a/boards/esp32-core/README.txt b/boards/esp32-core/README.txt
index 63895c0226..9a0799229c 100644
--- a/boards/esp32-core/README.txt
+++ b/boards/esp32-core/README.txt
@@ -277,7 +277,7 @@ OpenOCD for the ESP32
to reflect the physical JTAG adapter connected.
NOTE: A copy of this OpenOCD configuration file available in the NuttX
- source tree at nuttx/configs/esp32-core/scripts/esp32.cfg . It has these
+ source tree at nuttx/boards/esp32-core/scripts/esp32.cfg . It has these
modifications:
- The referenced "set ESP32_RTOS none" line has been uncommented
@@ -533,7 +533,7 @@ OpenOCD for the ESP32
I did the initial bring-up using the IRAM configuration and OpenOCD. Here
is a synopsis of my debug steps:
- configs/esp32-core/nsh with
+ boards/esp32-core/nsh with
CONFIG_DEBUG_ASSERTIONS=y
CONFIG_DEBUG_FEATURES=y
@@ -549,7 +549,7 @@ OpenOCD for the ESP32
Start OpenOCD:
cd ../openocde-esp32
- cp ../nuttx/configs/esp32-core/scripts/esp32.cfg .
+ cp ../nuttx/boards/esp32-core/scripts/esp32.cfg .
sudo ./src/openocd -s ./tcl/ -f tcl/interface/ftdi/olimex-arm-usb-ocd.cfg -f ./esp32.cfg
Start GDB and load code:
@@ -648,7 +648,7 @@ NOTES:
to provide that logic -- hopefully that is coming. As a
consequence, whatever clock setup was left when NuttX started is
used. For the case of execution out of IRAM with GDB, the
- settings in configs/esp32-core/include/board.h work. To check
+ settings in boards/esp32-core/include/board.h work. To check
the timing, I use a stop watch and:
nsh> sleep 60
diff --git a/boards/esp32-core/scripts/esp32.template b/boards/esp32-core/scripts/esp32.template
index 871171ddde..b7394b9870 100644
--- a/boards/esp32-core/scripts/esp32.template
+++ b/boards/esp32-core/scripts/esp32.template
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/elf32-core/scripts/esp32.template
+ * boards/elf32-core/scripts/esp32.template
* ESP32 Linker Script Memory Layout
*
* This file describes the memory layout (memory blocks) as virtual
diff --git a/boards/esp32-core/scripts/esp32_flash.ld b/boards/esp32-core/scripts/esp32_flash.ld
index e11f2f954a..2292636f63 100644
--- a/boards/esp32-core/scripts/esp32_flash.ld
+++ b/boards/esp32-core/scripts/esp32_flash.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/elf32-core/scripts/esp32_flash.ld
+ * boards/elf32-core/scripts/esp32_flash.ld
****************************************************************************/
/* Default entry point: */
diff --git a/boards/esp32-core/scripts/esp32_iram.ld b/boards/esp32-core/scripts/esp32_iram.ld
index 2df0a5355a..c83316ffdf 100644
--- a/boards/esp32-core/scripts/esp32_iram.ld
+++ b/boards/esp32-core/scripts/esp32_iram.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/elf32-core/scripts/esp32_iram.ld
+ * boards/elf32-core/scripts/esp32_iram.ld
****************************************************************************/
/* Default entry point: */
diff --git a/boards/esp32-core/scripts/esp32_peripherals.ld b/boards/esp32-core/scripts/esp32_peripherals.ld
index cabfe4aaa4..9595be2a9d 100644
--- a/boards/esp32-core/scripts/esp32_peripherals.ld
+++ b/boards/esp32-core/scripts/esp32_peripherals.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/elf32-core/scripts/esp32_peripherals.ld
+ * boards/elf32-core/scripts/esp32_peripherals.ld
****************************************************************************/
PROVIDE ( UART0 = 0x3ff40000 );
diff --git a/boards/esp32-core/scripts/esp32_rom.ld b/boards/esp32-core/scripts/esp32_rom.ld
index b7181d8896..8d318cc19f 100644
--- a/boards/esp32-core/scripts/esp32_rom.ld
+++ b/boards/esp32-core/scripts/esp32_rom.ld
@@ -1163,7 +1163,7 @@ PROVIDE ( r_lld_pdu_tx_prog = 0x4004b120 );
PROVIDE ( r_lld_pdu_tx_push = 0x4004b080 );
PROVIDE ( r_lld_ral_renew_req = 0x4004a73c );
/****************************************************************************
- * configs/elf32-core/scripts/esp32_rom.ld
+ * boards/elf32-core/scripts/esp32_rom.ld
****************************************************************************/
PROVIDE ( r_lld_scan_start = 0x40048ee0 );
diff --git a/boards/ez80f910200kitg/README.txt b/boards/ez80f910200kitg/README.txt
index fa66ca392d..1b1be5d890 100644
--- a/boards/ez80f910200kitg/README.txt
+++ b/boards/ez80f910200kitg/README.txt
@@ -71,7 +71,7 @@ Other Versions
If you use any version of ZDS-II other than 5.1.1, 5.2.1, or 5.3.0 or
if you install ZDS-II at any location other than the default location,
you will have to modify three files: (1) arch/arm/z80/src/ez80/Kconfig,
- (2) configs/ez80f910200kitg/scripts/Make.defs and, perhaps, (3)
+ (2) boards/ez80f910200kitg/scripts/Make.defs and, perhaps, (3)
arch/z80/src/ez80/Toolchain.defs.
Configuration Subdirectories
diff --git a/boards/ez80f910200kitg/scripts/ez80f910200kitg.linkcmd b/boards/ez80f910200kitg/scripts/ez80f910200kitg.linkcmd
index 66c90c79b4..7c4fb4ad01 100644
--- a/boards/ez80f910200kitg/scripts/ez80f910200kitg.linkcmd
+++ b/boards/ez80f910200kitg/scripts/ez80f910200kitg.linkcmd
@@ -1,5 +1,5 @@
/****************************************************************************/
-/* configs/ez80f910200kitg/scripts/ez80f910200kitg.linkcmd */
+/* boards/ez80f910200kitg/scripts/ez80f910200kitg.linkcmd */
/* */
/* Copyright (C) 2008 Gregory Nutt. All rights reserved. */
/* Author: Gregory Nutt */
diff --git a/boards/ez80f910200zco/README.txt b/boards/ez80f910200zco/README.txt
index bcc3faa3f7..300bdb2125 100644
--- a/boards/ez80f910200zco/README.txt
+++ b/boards/ez80f910200zco/README.txt
@@ -71,7 +71,7 @@ Other Versions
If you use any version of ZDS-II other than 5.1.1, 5.2.1, or 5.3.0 or
if you install ZDS-II at any location other than the default location,
you will have to modify three files: (1) arch/arm/z80/src/ez80/Kconfig,
- (2) configs/ez80f910200zco/scripts/Make.defs and, perhaps, (3)
+ (2) boards/ez80f910200zco/scripts/Make.defs and, perhaps, (3)
arch/z80/src/ez80/Toolchain.defs.
Configurations
diff --git a/boards/ez80f910200zco/scripts/ez80f910200zco.linkcmd b/boards/ez80f910200zco/scripts/ez80f910200zco.linkcmd
index a21988bfef..3ca7d83692 100644
--- a/boards/ez80f910200zco/scripts/ez80f910200zco.linkcmd
+++ b/boards/ez80f910200zco/scripts/ez80f910200zco.linkcmd
@@ -1,5 +1,5 @@
/****************************************************************************/
-/* configs/ez80f910200zco/scripts/ez80f910200zco.linkcmd */
+/* boards/ez80f910200zco/scripts/ez80f910200zco.linkcmd */
/* */
/* Copyright (C) 2009, 2017 Gregory Nutt. All rights reserved. */
/* Author: Gregory Nutt */
diff --git a/boards/fire-stm32v2/README.txt b/boards/fire-stm32v2/README.txt
index 490d25c95c..ad6e09d964 100644
--- a/boards/fire-stm32v2/README.txt
+++ b/boards/fire-stm32v2/README.txt
@@ -228,13 +228,13 @@ OpenOCD
=======
I have also used OpenOCD with the M3 Wildfire. In this case, I used
-the Olimex USB ARM OCD. See the script in configs/fire-stm32v2/tools/oocd.sh
+the Olimex USB ARM OCD. See the script in boards/fire-stm32v2/tools/oocd.sh
for more information. Using the script:
1) Start the OpenOCD GDB server
cd
- configs/fire-stm32v2/tools/oocd.sh $PWD
+ boards/fire-stm32v2/tools/oocd.sh $PWD
2) Load Nuttx
@@ -333,7 +333,7 @@ M3 Wildfire-specific Configuration Options
CONFIG_ARCH_BOARD_STM32_CUSTOM_CLOCKCONFIG=n
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=fire-stm32v2 (for the M3 Wildfire development board)
diff --git a/boards/fire-stm32v2/scripts/fire-stm32v2-dfu.ld b/boards/fire-stm32v2/scripts/fire-stm32v2-dfu.ld
index 74fc27362a..2dddc127c0 100644
--- a/boards/fire-stm32v2/scripts/fire-stm32v2-dfu.ld
+++ b/boards/fire-stm32v2/scripts/fire-stm32v2-dfu.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/fire-stm32v2/scripts/fire-stm32v2-dfu.ld
+ * boards/fire-stm32v2/scripts/fire-stm32v2-dfu.ld
*
* Copyright (C) 2012, 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/fire-stm32v2/scripts/fire-stm32v2.ld b/boards/fire-stm32v2/scripts/fire-stm32v2.ld
index a9eeab42f4..476ada9acc 100644
--- a/boards/fire-stm32v2/scripts/fire-stm32v2.ld
+++ b/boards/fire-stm32v2/scripts/fire-stm32v2.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/fire-stm32v2/scripts/fire-stm32v2.ld
+ * boards/fire-stm32v2/scripts/fire-stm32v2.ld
*
* Copyright (C) 2012, 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/flipnclick-pic32mz/README.txt b/boards/flipnclick-pic32mz/README.txt
index 5707bd1569..64a128da30 100644
--- a/boards/flipnclick-pic32mz/README.txt
+++ b/boards/flipnclick-pic32mz/README.txt
@@ -1,4 +1,4 @@
-configs/flipnclick-pic32mz README
+boards/flipnclick-pic32mz README
===============================
This README file discusses the port of NuttX to the Mikroe Flip&Click
diff --git a/boards/flipnclick-pic32mz/scripts/c32-debug.ld b/boards/flipnclick-pic32mz/scripts/c32-debug.ld
index a9f9518bd1..e4c94d1b6a 100644
--- a/boards/flipnclick-pic32mz/scripts/c32-debug.ld
+++ b/boards/flipnclick-pic32mz/scripts/c32-debug.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/flipnclick-pic32mz/nsh/c32-debug.ld
+ * boards/flipnclick-pic32mz/nsh/c32-debug.ld
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/flipnclick-pic32mz/scripts/mips-debug.ld b/boards/flipnclick-pic32mz/scripts/mips-debug.ld
index 5dc217f656..0cea856d2f 100644
--- a/boards/flipnclick-pic32mz/scripts/mips-debug.ld
+++ b/boards/flipnclick-pic32mz/scripts/mips-debug.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/flipnclick-pic32mz/nsh/mips-debug.ld
+ * boards/flipnclick-pic32mz/nsh/mips-debug.ld
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/flipnclick-pic32mz/scripts/pinguino-debug.ld b/boards/flipnclick-pic32mz/scripts/pinguino-debug.ld
index 1fae589e67..5fb8eba050 100644
--- a/boards/flipnclick-pic32mz/scripts/pinguino-debug.ld
+++ b/boards/flipnclick-pic32mz/scripts/pinguino-debug.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/flipnclick-pic32mz/nsh/mips-debug.ld
+ * boards/flipnclick-pic32mz/nsh/mips-debug.ld
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/flipnclick-pic32mz/scripts/xc32-debug.ld b/boards/flipnclick-pic32mz/scripts/xc32-debug.ld
index bbec260d52..25e08a6dbf 100644
--- a/boards/flipnclick-pic32mz/scripts/xc32-debug.ld
+++ b/boards/flipnclick-pic32mz/scripts/xc32-debug.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/flipnclick-pic32mz/nsh/mips-debug.ld
+ * boards/flipnclick-pic32mz/nsh/mips-debug.ld
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/flipnclick-sam3x/README.txt b/boards/flipnclick-sam3x/README.txt
index c4d154ae45..2d4afaf2dd 100644
--- a/boards/flipnclick-sam3x/README.txt
+++ b/boards/flipnclick-sam3x/README.txt
@@ -470,7 +470,7 @@ Flip&Click SAM3X-specific Configuration Options
CONFIG_ARCH_CHIP_SAM3X
CONFIG_ARCH_CHIP_ATSAM3X8E
- CONFIG_ARCH_BOARD - Identifies the configs/ subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=flipnclick-sam3x (for the Flip&Click SAM3X development board)
diff --git a/boards/flipnclick-sam3x/scripts/flash.ld b/boards/flipnclick-sam3x/scripts/flash.ld
index 2fe517ea3c..2d80c6e441 100644
--- a/boards/flipnclick-sam3x/scripts/flash.ld
+++ b/boards/flipnclick-sam3x/scripts/flash.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/flipnclick-sam3x/scripts/flash.ld
+ * boards/flipnclick-sam3x/scripts/flash.ld
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/freedom-k28f/scripts/flash.ld b/boards/freedom-k28f/scripts/flash.ld
index 18aa54cd35..b083892722 100644
--- a/boards/freedom-k28f/scripts/flash.ld
+++ b/boards/freedom-k28f/scripts/flash.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/freedom-k28f/scripts/flash.ld
+ * boards/freedom-k28f/scripts/flash.ld
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/freedom-k64f/README.txt b/boards/freedom-k64f/README.txt
index fdd5387d5b..657b65729e 100644
--- a/boards/freedom-k64f/README.txt
+++ b/boards/freedom-k64f/README.txt
@@ -673,7 +673,7 @@ Freedom K64F Configuration Options
CONFIG_ARCH_CHIP_MK64FN1M0VLL12
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD="freedom-k64f" (for the Freedom K64F development board)
diff --git a/boards/freedom-k64f/scripts/flash.ld b/boards/freedom-k64f/scripts/flash.ld
index 34b1e5b92a..d58489b2a4 100644
--- a/boards/freedom-k64f/scripts/flash.ld
+++ b/boards/freedom-k64f/scripts/flash.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/freedom-k64f/scripts/flash.ld
+ * boards/freedom-k64f/scripts/flash.ld
*
* Copyright (C) 2016 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/freedom-k66f/README.txt b/boards/freedom-k66f/README.txt
index f024c73b7c..7135f79877 100644
--- a/boards/freedom-k66f/README.txt
+++ b/boards/freedom-k66f/README.txt
@@ -676,7 +676,7 @@ Freedom K66F Configuration Options
CONFIG_ARCH_CHIP_MK66FN2M0VMD18
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD="freedom-K66F" (for the Freedom K66F development board)
diff --git a/boards/freedom-k66f/scripts/flash.ld b/boards/freedom-k66f/scripts/flash.ld
index 1d998d6847..fc7f8df1cb 100644
--- a/boards/freedom-k66f/scripts/flash.ld
+++ b/boards/freedom-k66f/scripts/flash.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/freedom-k66f/scripts/flash.ld
+ * boards/freedom-k66f/scripts/flash.ld
*
* Copyright (C) 2016-2017 Gregory Nutt. All rights reserved.
* Authors: Gregory Nutt
diff --git a/boards/freedom-kl25z/README.txt b/boards/freedom-kl25z/README.txt
index b84868e117..92e9c01cc0 100644
--- a/boards/freedom-kl25z/README.txt
+++ b/boards/freedom-kl25z/README.txt
@@ -54,7 +54,7 @@ NuttX Buildroot Toolchain
4. cd /buildroot
- 5. cp configs/cortexm0-eabi-defconfig-4.6.3 .config
+ 5. cp boards/cortexm0-eabi-defconfig-4.6.3 .config
6. make oldconfig
@@ -63,7 +63,7 @@ NuttX Buildroot Toolchain
8. Make sure that the PATH variable includes the path to the newly built
binaries.
- See the file configs/README.txt in the buildroot source tree. That has more
+ See the file boards/README.txt in the buildroot source tree. That has more
details PLUS some special instructions that you will need to follow if you are
building a Cortex-M0 toolchain for Cygwin under Windows.
@@ -172,7 +172,7 @@ Freedom KL25Z-specific Configuration Options
CONFIG_ARCH_CHIP_MKL25Z128=y
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=freedom-kl25z (for the Freescale FRDM-KL25Z development board)
diff --git a/boards/freedom-kl25z/scripts/freedom-kl25z.ld b/boards/freedom-kl25z/scripts/freedom-kl25z.ld
index e57a2f0496..5e51861c0d 100644
--- a/boards/freedom-kl25z/scripts/freedom-kl25z.ld
+++ b/boards/freedom-kl25z/scripts/freedom-kl25z.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/kwikstik-k40/scripts/freedom-kl25z.ld
+ * boards/kwikstik-k40/scripts/freedom-kl25z.ld
*
* Copyright (C) 2013, 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/freedom-kl26z/README.txt b/boards/freedom-kl26z/README.txt
index 2d3119af64..d9bcdeec4f 100644
--- a/boards/freedom-kl26z/README.txt
+++ b/boards/freedom-kl26z/README.txt
@@ -54,7 +54,7 @@ NuttX Buildroot Toolchain
4. cd /buildroot
- 5. cp configs/cortexm0-eabi-defconfig-4.6.3 .config
+ 5. cp boards/cortexm0-eabi-defconfig-4.6.3 .config
6. make oldconfig
@@ -63,7 +63,7 @@ NuttX Buildroot Toolchain
8. Make sure that the PATH variable includes the path to the newly built
binaries.
- See the file configs/README.txt in the buildroot source tree. That has more
+ See the file boards/README.txt in the buildroot source tree. That has more
details PLUS some special instructions that you will need to follow if you are
building a Cortex-M0 toolchain for Cygwin under Windows.
@@ -150,7 +150,7 @@ Freedom KL26Z-specific Configuration Options
CONFIG_ARCH_CHIP_MKL26Z128=y
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=freedom-kl26z (for the Freescale FRDM-KL26Z development board)
diff --git a/boards/freedom-kl26z/scripts/freedom-kl26z.ld b/boards/freedom-kl26z/scripts/freedom-kl26z.ld
index 2ba35c9b44..a0a5b42501 100644
--- a/boards/freedom-kl26z/scripts/freedom-kl26z.ld
+++ b/boards/freedom-kl26z/scripts/freedom-kl26z.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/freedom-kl26z/scripts/freedom-kl26z.ld
+ * boards/freedom-kl26z/scripts/freedom-kl26z.ld
*
* Copyright (C) 2015, 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/gapuino/scripts/ld.script b/boards/gapuino/scripts/ld.script
index ef6d22810c..17d8097a42 100644
--- a/boards/gapuino/scripts/ld.script
+++ b/boards/gapuino/scripts/ld.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/gapduino/scripts/ld.script
+ * boards/gapduino/scripts/ld.script
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Author: hhuysqt <1020988872@qq.com>
diff --git a/boards/hymini-stm32v/README.txt b/boards/hymini-stm32v/README.txt
index 7b7fa26030..97a6501b4a 100644
--- a/boards/hymini-stm32v/README.txt
+++ b/boards/hymini-stm32v/README.txt
@@ -124,7 +124,7 @@ HY-Mini specific Configuration Options
CONFIG_ARCH_BOARD_STM32_CUSTOM_CLOCKCONFIG=n
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=hymini-stm32v (for the HY-Mini development board)
diff --git a/boards/hymini-stm32v/scripts/ld.script b/boards/hymini-stm32v/scripts/ld.script
index 546c06bc1c..bf9d42d4b1 100644
--- a/boards/hymini-stm32v/scripts/ld.script
+++ b/boards/hymini-stm32v/scripts/ld.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/hymini-stm32v/scripts/ld.script
+ * boards/hymini-stm32v/scripts/ld.script
*
* Copyright (C) 2011-2012 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/imxrt1050-evk/README.txt b/boards/imxrt1050-evk/README.txt
index 02aedfd196..13628e4b0b 100644
--- a/boards/imxrt1050-evk/README.txt
+++ b/boards/imxrt1050-evk/README.txt
@@ -203,7 +203,7 @@ Configuration sub-directories
debugger or FLASH utility, then you may need to combine the two hex
files into a single .hex file. Here is how you can do that.
- a. The 'configs/samv71-xult/knsh/defconfigtail' of the nuttx.hex file should look something like this
+ a. The 'boards/samv71-xult/knsh/defconfigtail' of the nuttx.hex file should look something like this
(with my comments added beginning with #):
$ tail nuttx.hex
diff --git a/boards/imxrt1050-evk/knsh/defconfig b/boards/imxrt1050-evk/knsh/defconfig
index c1e75b69b1..b586acb0b0 100644
--- a/boards/imxrt1050-evk/knsh/defconfig
+++ b/boards/imxrt1050-evk/knsh/defconfig
@@ -35,7 +35,7 @@ CONFIG_NSH_FILEIOSIZE=512
CONFIG_NSH_LINELEN=64
CONFIG_NSH_READLINE=y
CONFIG_NUTTX_USERSPACE=0x60200000
-CONFIG_PASS1_BUILDIR="configs/imxrt1050-evk/kernel"
+CONFIG_PASS1_BUILDIR="boards/imxrt1050-evk/kernel"
CONFIG_PREALLOC_MQ_MSGS=4
CONFIG_PREALLOC_WDOGS=16
CONFIG_RAM_SIZE=524288
diff --git a/boards/imxrt1050-evk/scripts/flash-ocram.ld b/boards/imxrt1050-evk/scripts/flash-ocram.ld
index 0d37117d02..4b99138e63 100644
--- a/boards/imxrt1050-evk/scripts/flash-ocram.ld
+++ b/boards/imxrt1050-evk/scripts/flash-ocram.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/imxrt1050-evk/scripts/flash-ocram.ld
+ * boards/imxrt1050-evk/scripts/flash-ocram.ld
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Author: Ivan Ucherdzhiev
diff --git a/boards/imxrt1050-evk/scripts/kernel-space.ld b/boards/imxrt1050-evk/scripts/kernel-space.ld
index 4f73d3ab5a..0ed21c9b85 100644
--- a/boards/imxrt1050-evk/scripts/kernel-space.ld
+++ b/boards/imxrt1050-evk/scripts/kernel-space.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/simxrt1050-evk/scripts/kernel-space.ld
+ * boards/simxrt1050-evk/scripts/kernel-space.ld
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/imxrt1050-evk/scripts/memory.ld b/boards/imxrt1050-evk/scripts/memory.ld
index 59cccb2187..63d477948a 100644
--- a/boards/imxrt1050-evk/scripts/memory.ld
+++ b/boards/imxrt1050-evk/scripts/memory.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/imxrt1050-evk/scripts/memory.ld
+ * boards/imxrt1050-evk/scripts/memory.ld
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/imxrt1050-evk/scripts/user-space.ld b/boards/imxrt1050-evk/scripts/user-space.ld
index 0e7563263b..68ca37519d 100644
--- a/boards/imxrt1050-evk/scripts/user-space.ld
+++ b/boards/imxrt1050-evk/scripts/user-space.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/simxrt1050-evk/scripts/user-space.ld
+ * boards/simxrt1050-evk/scripts/user-space.ld
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/imxrt1060-evk/README.txt b/boards/imxrt1060-evk/README.txt
index 956d865587..37ac3f8b6f 100644
--- a/boards/imxrt1060-evk/README.txt
+++ b/boards/imxrt1060-evk/README.txt
@@ -221,7 +221,7 @@ Configuration sub-directories
debugger or FLASH utility, then you may need to combine the two hex
files into a single .hex file. Here is how you can do that.
- a. The 'configs/samv71-xult/knsh/defconfigtail' of the nuttx.hex file should look something like this
+ a. The 'boards/samv71-xult/knsh/defconfigtail' of the nuttx.hex file should look something like this
(with my comments added beginning with #):
$ tail nuttx.hex
diff --git a/boards/imxrt1060-evk/knsh/defconfig b/boards/imxrt1060-evk/knsh/defconfig
index b32ab9c70c..f4c381317d 100644
--- a/boards/imxrt1060-evk/knsh/defconfig
+++ b/boards/imxrt1060-evk/knsh/defconfig
@@ -35,7 +35,7 @@ CONFIG_NSH_FILEIOSIZE=512
CONFIG_NSH_LINELEN=64
CONFIG_NSH_READLINE=y
CONFIG_NUTTX_USERSPACE=0x60200000
-CONFIG_PASS1_BUILDIR="configs/imxrt1060-evk/kernel"
+CONFIG_PASS1_BUILDIR="boards/imxrt1060-evk/kernel"
CONFIG_PREALLOC_MQ_MSGS=4
CONFIG_PREALLOC_WDOGS=16
CONFIG_RAM_SIZE=1048576
diff --git a/boards/imxrt1060-evk/scripts/flash-ocram.ld b/boards/imxrt1060-evk/scripts/flash-ocram.ld
index f8224ef0a1..0bfbaf4eec 100644
--- a/boards/imxrt1060-evk/scripts/flash-ocram.ld
+++ b/boards/imxrt1060-evk/scripts/flash-ocram.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/imxrt1060-evk/scripts/flash-ocram.ld
+ * boards/imxrt1060-evk/scripts/flash-ocram.ld
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Authors: Ivan Ucherdzhiev
diff --git a/boards/imxrt1060-evk/scripts/kernel-space.ld b/boards/imxrt1060-evk/scripts/kernel-space.ld
index a65b159e89..dee7b7f4f7 100644
--- a/boards/imxrt1060-evk/scripts/kernel-space.ld
+++ b/boards/imxrt1060-evk/scripts/kernel-space.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/imxrt1060-evk/scripts/kernel-space.ld
+ * boards/imxrt1060-evk/scripts/kernel-space.ld
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Authors: Gregory Nutt
diff --git a/boards/imxrt1060-evk/scripts/memory.ld b/boards/imxrt1060-evk/scripts/memory.ld
index 0ad3e028b6..d14a2b1cf6 100644
--- a/boards/imxrt1060-evk/scripts/memory.ld
+++ b/boards/imxrt1060-evk/scripts/memory.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/imxrt1060-evk/scripts/memory.ld
+ * boards/imxrt1060-evk/scripts/memory.ld
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Authors: Gregory Nutt
diff --git a/boards/imxrt1060-evk/scripts/user-space.ld b/boards/imxrt1060-evk/scripts/user-space.ld
index 77a2bc2b40..af70749e21 100644
--- a/boards/imxrt1060-evk/scripts/user-space.ld
+++ b/boards/imxrt1060-evk/scripts/user-space.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/simxrt1060-evk/scripts/user-space.ld
+ * boards/simxrt1060-evk/scripts/user-space.ld
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Authors: Gregory Nutt
diff --git a/boards/kwikstik-k40/README.txt b/boards/kwikstik-k40/README.txt
index 0370db7ab2..28f313ad1e 100644
--- a/boards/kwikstik-k40/README.txt
+++ b/boards/kwikstik-k40/README.txt
@@ -169,7 +169,7 @@ KwikStik-K40-specific Configuration Options
CONFIG_ARCH_CHIP_MK40X256VLQ100
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=kwikstik-k40 (for the KwikStik-K40 development board)
diff --git a/boards/kwikstik-k40/scripts/kwikstik-k40.ld b/boards/kwikstik-k40/scripts/kwikstik-k40.ld
index 17f0753075..49af4ed113 100644
--- a/boards/kwikstik-k40/scripts/kwikstik-k40.ld
+++ b/boards/kwikstik-k40/scripts/kwikstik-k40.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/kwikstik-k40/scripts/kwikstik-k40.ld
+ * boards/kwikstik-k40/scripts/kwikstik-k40.ld
*
* Copyright (C) 2011, 2015, 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/launchxl-cc1310/scripts/flash.ld b/boards/launchxl-cc1310/scripts/flash.ld
index ca4aeaf1f9..b7600fdf49 100644
--- a/boards/launchxl-cc1310/scripts/flash.ld
+++ b/boards/launchxl-cc1310/scripts/flash.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/launchxl-cc1310/scripts/flash.ld
+ * boards/launchxl-cc1310/scripts/flash.ld
*
* Copyright (C) 2019 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/launchxl-cc1312r1/scripts/flash.ld b/boards/launchxl-cc1312r1/scripts/flash.ld
index 7e2a533281..ed090e031d 100644
--- a/boards/launchxl-cc1312r1/scripts/flash.ld
+++ b/boards/launchxl-cc1312r1/scripts/flash.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/launchxl-cc1312r1/scripts/flash.ld
+ * boards/launchxl-cc1312r1/scripts/flash.ld
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/launchxl-cc1312r1/scripts/sram.ld b/boards/launchxl-cc1312r1/scripts/sram.ld
index 88dec4273d..8ab46ed4b6 100644
--- a/boards/launchxl-cc1312r1/scripts/sram.ld
+++ b/boards/launchxl-cc1312r1/scripts/sram.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/launchxl-cc1312r1/scripts/sram.ld
+ * boards/launchxl-cc1312r1/scripts/sram.ld
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/launchxl-tms57004/README.txt b/boards/launchxl-tms57004/README.txt
index 86057e31cc..63e9f42746 100644
--- a/boards/launchxl-tms57004/README.txt
+++ b/boards/launchxl-tms57004/README.txt
@@ -64,7 +64,7 @@ Toolchain
this:
cd buildroot/
- cp configs/cortexr4-armeb-eabi-4.8.3-defconfig .config
+ cp boards/cortexr4-armeb-eabi-4.8.3-defconfig .config
make oldconfig
make
diff --git a/boards/launchxl-tms57004/scripts/flash-sram.ld b/boards/launchxl-tms57004/scripts/flash-sram.ld
index 810a2b9b5d..4f5a605c0d 100644
--- a/boards/launchxl-tms57004/scripts/flash-sram.ld
+++ b/boards/launchxl-tms57004/scripts/flash-sram.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/launchxl-tms5700/scripts/flash-sram.ld
+ * boards/launchxl-tms5700/scripts/flash-sram.ld
*
* Copyright (C) 2015 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/lc823450-xgevk/knsh/defconfig b/boards/lc823450-xgevk/knsh/defconfig
index 640639dcf8..048659d529 100644
--- a/boards/lc823450-xgevk/knsh/defconfig
+++ b/boards/lc823450-xgevk/knsh/defconfig
@@ -85,7 +85,7 @@ CONFIG_NUTTX_USERSPACE=0x05020000
CONFIG_NX=y
CONFIG_NXFONT_MONO5X8=y
CONFIG_NX_BLOCKING=y
-CONFIG_PASS1_BUILDIR="configs/lc823450-xgevk/kernel"
+CONFIG_PASS1_BUILDIR="boards/lc823450-xgevk/kernel"
CONFIG_PIPES=y
CONFIG_POSIX_SPAWN_PROXY_STACKSIZE=2048
CONFIG_PREALLOC_MQ_MSGS=4
diff --git a/boards/lc823450-xgevk/kostest/defconfig b/boards/lc823450-xgevk/kostest/defconfig
index d49aa84791..86dcdf625d 100644
--- a/boards/lc823450-xgevk/kostest/defconfig
+++ b/boards/lc823450-xgevk/kostest/defconfig
@@ -27,7 +27,7 @@ CONFIG_MAX_WDOGPARMS=2
CONFIG_NFILE_DESCRIPTORS=8
CONFIG_NFILE_STREAMS=8
CONFIG_NUTTX_USERSPACE=0x05020000
-CONFIG_PASS1_BUILDIR="configs/lc823450-xgevk/kernel"
+CONFIG_PASS1_BUILDIR="boards/lc823450-xgevk/kernel"
CONFIG_PREALLOC_MQ_MSGS=4
CONFIG_PREALLOC_TIMERS=4
CONFIG_PREALLOC_WDOGS=8
diff --git a/boards/lc823450-xgevk/krndis/defconfig b/boards/lc823450-xgevk/krndis/defconfig
index 9ac74ce6c4..2af06bf0e6 100644
--- a/boards/lc823450-xgevk/krndis/defconfig
+++ b/boards/lc823450-xgevk/krndis/defconfig
@@ -138,7 +138,7 @@ CONFIG_NXFONT_MONO5X8=y
CONFIG_NXPLAYER_DEFAULT_MEDIADIR="/mnt/sd1"
CONFIG_NXPLAYER_HTTP_STREAMING_SUPPORT=y
CONFIG_NX_BLOCKING=y
-CONFIG_PASS1_BUILDIR="configs/lc823450-xgevk/kernel"
+CONFIG_PASS1_BUILDIR="boards/lc823450-xgevk/kernel"
CONFIG_PATH_INITIAL="/mnt/sd0/bin"
CONFIG_PIPES=y
CONFIG_POSIX_SPAWN_PROXY_STACKSIZE=2048
diff --git a/boards/lc823450-xgevk/scripts/gnu-elf.ld b/boards/lc823450-xgevk/scripts/gnu-elf.ld
index cac851893c..8c01213d98 100644
--- a/boards/lc823450-xgevk/scripts/gnu-elf.ld
+++ b/boards/lc823450-xgevk/scripts/gnu-elf.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/lc823450-xgevk/scripts/gnu-elf.ld
+ * boards/lc823450-xgevk/scripts/gnu-elf.ld
*
* Copyright 2017 Sony Video & Sound Products Inc.
* Author: Masayuki Ishikawa
diff --git a/boards/lc823450-xgevk/scripts/ld-ipl2.script b/boards/lc823450-xgevk/scripts/ld-ipl2.script
index a018913469..d01fe91d72 100644
--- a/boards/lc823450-xgevk/scripts/ld-ipl2.script
+++ b/boards/lc823450-xgevk/scripts/ld-ipl2.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/lc823450-xgevk/scripts/ld-ipl2.script
+ * boards/lc823450-xgevk/scripts/ld-ipl2.script
*
* Copyright 2017 Sony Video & Sound Products Inc.
* Author: Masayuki Ishikawa
diff --git a/boards/lc823450-xgevk/scripts/ld-spif-boot.script b/boards/lc823450-xgevk/scripts/ld-spif-boot.script
index 4631d8bd14..1decf0c1a5 100644
--- a/boards/lc823450-xgevk/scripts/ld-spif-boot.script
+++ b/boards/lc823450-xgevk/scripts/ld-spif-boot.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/lc823450-xgevk/scripts/ld-spif-boot.script
+ * boards/lc823450-xgevk/scripts/ld-spif-boot.script
*
* Copyright 2019 Sony Video & Sound Products Inc.
* Author: Masayuki Ishikawa
diff --git a/boards/lc823450-xgevk/scripts/ld.script b/boards/lc823450-xgevk/scripts/ld.script
index 2876760330..84e7a7d779 100644
--- a/boards/lc823450-xgevk/scripts/ld.script
+++ b/boards/lc823450-xgevk/scripts/ld.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/lc823450-xgevk/scripts/ld.script
+ * boards/lc823450-xgevk/scripts/ld.script
*
* Copyright 2017 Sony Video & Sound Products Inc.
* Author: Masayuki Ishikawa
diff --git a/boards/lc823450-xgevk/scripts/memory.ld b/boards/lc823450-xgevk/scripts/memory.ld
index 12c54aa3b0..629216bd5d 100644
--- a/boards/lc823450-xgevk/scripts/memory.ld
+++ b/boards/lc823450-xgevk/scripts/memory.ld
@@ -1,10 +1,10 @@
/****************************************************************************
- * configs/lc823450-xgevk/scripts/memory.ld
+ * boards/lc823450-xgevk/scripts/memory.ld
*
* Copyright 2018 Sony Video & Sound Products Inc.
* Author: Masayuki Ishikawa
*
- * Based on configs/stm32f4discovery/scripts/memory.ld
+ * Based on boards/stm32f4discovery/scripts/memory.ld
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
diff --git a/boards/lc823450-xgevk/scripts/user-space.ld b/boards/lc823450-xgevk/scripts/user-space.ld
index b51eb8a826..f018d2fec6 100644
--- a/boards/lc823450-xgevk/scripts/user-space.ld
+++ b/boards/lc823450-xgevk/scripts/user-space.ld
@@ -1,10 +1,10 @@
/****************************************************************************
- * configs/lc823450-xgevk/scripts/user-space.ld
+ * boards/lc823450-xgevk/scripts/user-space.ld
*
* Copyright 2018 Sony Video & Sound Products Inc.
* Author: Masayuki Ishikawa
*
- * Based on configs/stm32f4discovery/scripts/user-space.ld
+ * Based on boards/stm32f4discovery/scripts/user-space.ld
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
diff --git a/boards/lincoln60/README.txt b/boards/lincoln60/README.txt
index 5b1a258923..d008450ec8 100644
--- a/boards/lincoln60/README.txt
+++ b/boards/lincoln60/README.txt
@@ -72,7 +72,7 @@ Lincoln 60 Configuration Options
CONFIG_ARCH_CHIP_LPC1768=y
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=lincoln60 (for the Lincoln 60 board)
diff --git a/boards/lincoln60/scripts/ld.script b/boards/lincoln60/scripts/ld.script
index fe4307b52a..78fd09d276 100644
--- a/boards/lincoln60/scripts/ld.script
+++ b/boards/lincoln60/scripts/ld.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/lincoln60/scripts/ld.script
+ * boards/lincoln60/scripts/ld.script
*
* Copyright (C) 2012 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/lm3s6432-s2e/README.txt b/boards/lm3s6432-s2e/README.txt
index cee7eac36b..81dc598cc1 100644
--- a/boards/lm3s6432-s2e/README.txt
+++ b/boards/lm3s6432-s2e/README.txt
@@ -94,7 +94,7 @@ Stellaris MDL-S2E Reference Design Configuration Options
CONFIG_ARCH_CHIP_LM3S6432
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=lm3s6432-s2e (for the Stellaris MDL-S2E Reference Design)
diff --git a/boards/lm3s6432-s2e/scripts/lm3s6432-s2e.ld b/boards/lm3s6432-s2e/scripts/lm3s6432-s2e.ld
index aaf7b4ed04..4b5435d2a8 100644
--- a/boards/lm3s6432-s2e/scripts/lm3s6432-s2e.ld
+++ b/boards/lm3s6432-s2e/scripts/lm3s6432-s2e.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/lm3s6432-s2e/scripts/lm3s6432-s2e.ld
+ * boards/lm3s6432-s2e/scripts/lm3s6432-s2e.ld
*
* Copyright (C) 2010, 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/lm3s6965-ek/README.txt b/boards/lm3s6965-ek/README.txt
index 86ef7d61a2..ef648e972d 100644
--- a/boards/lm3s6965-ek/README.txt
+++ b/boards/lm3s6965-ek/README.txt
@@ -103,7 +103,7 @@ Using OpenOCD and GDB with an FT2232 JTAG emulator
Building OpenOCD under Cygwin:
- Refer to configs/olimex-lpc1766stk/README.txt
+ Refer to boards/olimex-lpc1766stk/README.txt
Installing OpenOCD in Linux:
@@ -114,7 +114,7 @@ Using OpenOCD and GDB with an FT2232 JTAG emulator
I have been using the on-board FT2232 JTAG/SWD/SWO interface. OpenOCD
requires a configuration file. I keep the one I used last here:
- configs/lm3s6965-ek/tools/lm3s6965-ek.cfg
+ boards/lm3s6965-ek/tools/lm3s6965-ek.cfg
However, the "correct" configuration script to use with OpenOCD may
change as the features of OpenOCD evolve. So you should at least
@@ -132,13 +132,13 @@ Using OpenOCD and GDB with an FT2232 JTAG emulator
- Possibly the value of OPENOCD_PATH and TARGET_PATH
- It assumes that the correct script to use is the one at
- configs/lm3s6965-ek/tools/lm3s6965-ek.cfg
+ boards/lm3s6965-ek/tools/lm3s6965-ek.cfg
Starting OpenOCD
Then you should be able to start the OpenOCD daemon like:
- configs/lm3s6965-ek/tools/oocd.sh $PWD
+ boards/lm3s6965-ek/tools/oocd.sh $PWD
Connecting GDB
@@ -241,7 +241,7 @@ Stellaris LM3S6965 Evaluation Kit Configuration Options
CONFIG_ARCH_CHIP_LM3S6965
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=lm3s6965-ek (for the Stellaris LM3S6965 Evaluation Kit)
diff --git a/boards/lm3s6965-ek/scripts/ld.script b/boards/lm3s6965-ek/scripts/ld.script
index ee9a22ad54..2355298cd2 100644
--- a/boards/lm3s6965-ek/scripts/ld.script
+++ b/boards/lm3s6965-ek/scripts/ld.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/lm3s6965-ek/scripts/ld.script
+ * boards/lm3s6965-ek/scripts/ld.script
*
* Copyright (C) 2010 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/lm3s8962-ek/README.txt b/boards/lm3s8962-ek/README.txt
index 101d56c3a1..0e14387f8f 100644
--- a/boards/lm3s8962-ek/README.txt
+++ b/boards/lm3s8962-ek/README.txt
@@ -161,7 +161,7 @@ Stellaris LM3S8962 Evaluation Kit Configuration Options
CONFIG_ARCH_CHIP_LM3S8962
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=lm3s8962-ek (for the Stellaris LM3S8962 Evaluation Kit)
diff --git a/boards/lm3s8962-ek/scripts/ld.script b/boards/lm3s8962-ek/scripts/ld.script
index 16840d040e..5cb78871b3 100644
--- a/boards/lm3s8962-ek/scripts/ld.script
+++ b/boards/lm3s8962-ek/scripts/ld.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/lm3s8962-ek/scripts/ld.script
+ * boards/lm3s8962-ek/scripts/ld.script
*
* Copyright (C) 2010 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/lm4f120-launchpad/README.txt b/boards/lm4f120-launchpad/README.txt
index 235296c5c5..323639c731 100644
--- a/boards/lm4f120-launchpad/README.txt
+++ b/boards/lm4f120-launchpad/README.txt
@@ -131,7 +131,7 @@ Using OpenOCD and GDB with an FT2232 JTAG emulator
Building OpenOCD under Cygwin:
- Refer to configs/olimex-lpc1766stk/README.txt
+ Refer to boards/olimex-lpc1766stk/README.txt
Installing OpenOCD in Linux:
@@ -159,7 +159,7 @@ Using OpenOCD and GDB with an FT2232 JTAG emulator
I have been using the on-board In-Circuit Debug Interface (ICDI) interface.
OpenOCD requires a configuration file. I keep the one I used last here:
- configs/lm4f120-launchpad/tools/lm4f120-launchpad.cfg
+ boards/lm4f120-launchpad/tools/lm4f120-launchpad.cfg
However, the "correct" configuration script to use with OpenOCD may
change as the features of OpenOCD evolve. So you should at least
@@ -177,7 +177,7 @@ Using OpenOCD and GDB with an FT2232 JTAG emulator
- Possibly the value of OPENOCD_PATH and TARGET_PATH
- It assumes that the correct script to use is the one at
- configs/lm4f120-launchpad/tools/lm4f120-launchpad.cfg
+ boards/lm4f120-launchpad/tools/lm4f120-launchpad.cfg
Starting OpenOCD
@@ -186,7 +186,7 @@ Using OpenOCD and GDB with an FT2232 JTAG emulator
oocd.sh $PWD
- provided that you have the path to the oocd.sh script, configs/lm4f120-launchpad/tools,
+ provided that you have the path to the oocd.sh script, boards/lm4f120-launchpad/tools,
added to your PATH variable.
Note that OpenOCD needs to be run with administrator privileges in
@@ -234,12 +234,12 @@ LEDs
The LM4F120 has a single RGB LED. If CONFIG_ARCH_LEDS is defined, then
support for the LaunchPad LEDs will be included in the build. See:
- - configs/lm4f120-launchpad/include/board.h - Defines LED constants, types and
+ - boards/lm4f120-launchpad/include/board.h - Defines LED constants, types and
prototypes the LED interface functions.
- - configs/lm4f120-launchpad/src/lm4f120-launchpad.h - GPIO settings for the LEDs.
+ - boards/lm4f120-launchpad/src/lm4f120-launchpad.h - GPIO settings for the LEDs.
- - configs/lm4f120-launchpad/src/up_leds.c - LED control logic.
+ - boards/lm4f120-launchpad/src/up_leds.c - LED control logic.
OFF:
- OFF means that the OS is still initializing. Initialization is very fast so
@@ -370,7 +370,7 @@ LM4F120 LaunchPad Configuration Options
CONFIG_ARCH_CHIP_LM4F120
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=lm4f120-launchpad (for the LM4F120 LaunchPad)
diff --git a/boards/lm4f120-launchpad/scripts/lm4f120-launchpad.ld b/boards/lm4f120-launchpad/scripts/lm4f120-launchpad.ld
index a7e3828f89..d3c290b7dd 100644
--- a/boards/lm4f120-launchpad/scripts/lm4f120-launchpad.ld
+++ b/boards/lm4f120-launchpad/scripts/lm4f120-launchpad.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/lm4f120-launchpad/scripts/lm4f120-launchpad.ld
+ * boards/lm4f120-launchpad/scripts/lm4f120-launchpad.ld
*
* Copyright (C) 2013, 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/lpc4088-devkit/README.txt b/boards/lpc4088-devkit/README.txt
index 06381f95f0..f2cf0c3f09 100644
--- a/boards/lpc4088-devkit/README.txt
+++ b/boards/lpc4088-devkit/README.txt
@@ -97,7 +97,7 @@ Using OpenOCD with the Olimex ARM-USB-OCD
Building OpenOCD under Cygwin:
- Refer to configs/olimex-lpc1766stk/README.txt
+ Refer to boards/olimex-lpc1766stk/README.txt
Installing OpenOCD in Ubuntu Linux:
@@ -108,7 +108,7 @@ Using OpenOCD with the Olimex ARM-USB-OCD
I have been using the Olimex ARM-USB-OCD debugger. OpenOCD
requires a configuration file. I keep the one I used last here:
- configs/lpc4088-devkit/tools/lpc4088-devkit.cfg
+ boards/lpc4088-devkit/tools/lpc4088-devkit.cfg
However, the "correct" configuration script to use with OpenOCD may
change as the features of OpenOCD evolve. So you should at least
@@ -136,7 +136,7 @@ Using OpenOCD with the Olimex ARM-USB-OCD
installations. They could be most anywhwere if you are using a
windows version of OpenOCD.
- configs/lpc4088-devkit/tools/lpc4088-devkit.cfg
+ boards/lpc4088-devkit/tools/lpc4088-devkit.cfg
This is simply openocd-usb.cfg, lpc40xx.cfg, and lpc1xxx.cfg
concatenated into one file for convenience. Don't use it
unless you have to.
@@ -147,20 +147,20 @@ Using OpenOCD with the Olimex ARM-USB-OCD
- Possibly the value of OPENOCD_PATH and TARGET_PATH
- It assumes that the correct script to use is the one at
- configs/lpc4088-devkit/tools/lpc4088-devkit.cfg
+ boards/lpc4088-devkit/tools/lpc4088-devkit.cfg
Starting OpenOCD
Then you should be able to start the OpenOCD daemon as follows. This
assumes that you have already CD'ed to the NuttX build directory and
- that you have set the full path to the configs/lpc4088-devkit/tools in your
+ that you have set the full path to the boards/lpc4088-devkit/tools in your
PATH environment variable:
oocd.sh $PWD
or, if the PATH variable is not so configured:
- configs/lpc4088-devkit/tools/oocd.sh $PWD
+ boards/lpc4088-devkit/tools/oocd.sh $PWD
Connecting GDB
diff --git a/boards/lpc4088-devkit/knsh/defconfig b/boards/lpc4088-devkit/knsh/defconfig
index 4c2cf1991b..b84ffe77de 100644
--- a/boards/lpc4088-devkit/knsh/defconfig
+++ b/boards/lpc4088-devkit/knsh/defconfig
@@ -45,7 +45,7 @@ CONFIG_NSH_DISABLE_MKRD=y
CONFIG_NSH_FILEIOSIZE=512
CONFIG_NSH_READLINE=y
CONFIG_NUTTX_USERSPACE=0x00040000
-CONFIG_PASS1_BUILDIR="configs/lpc4088-devkit/kernel"
+CONFIG_PASS1_BUILDIR="boards/lpc4088-devkit/kernel"
CONFIG_PIPES=y
CONFIG_PREALLOC_MQ_MSGS=4
CONFIG_PREALLOC_TIMERS=4
diff --git a/boards/lpc4088-devkit/scripts/kernel-space.ld b/boards/lpc4088-devkit/scripts/kernel-space.ld
index 46a66376a7..5f3099ee88 100644
--- a/boards/lpc4088-devkit/scripts/kernel-space.ld
+++ b/boards/lpc4088-devkit/scripts/kernel-space.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/lpc4088-devkit/scripts/kernel-space.ld
+ * boards/lpc4088-devkit/scripts/kernel-space.ld
*
* Copyright (C) 2013 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/lpc4088-devkit/scripts/ld.script b/boards/lpc4088-devkit/scripts/ld.script
index e1b1f6dcce..bb60bad656 100644
--- a/boards/lpc4088-devkit/scripts/ld.script
+++ b/boards/lpc4088-devkit/scripts/ld.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/lpc4088-devkit/scripts/ld.script
+ * boards/lpc4088-devkit/scripts/ld.script
*
* Copyright (C) 2013 Gregory Nutt. All rights reserved.
* Author: Rommel Marcelo
diff --git a/boards/lpc4088-devkit/scripts/memory.ld b/boards/lpc4088-devkit/scripts/memory.ld
index 654f51641a..da6fbb7dec 100644
--- a/boards/lpc4088-devkit/scripts/memory.ld
+++ b/boards/lpc4088-devkit/scripts/memory.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/lpc4088-devkit/scripts/memory.ld
+ * boards/lpc4088-devkit/scripts/memory.ld
*
* Copyright (C) 2013 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
@@ -41,7 +41,7 @@
*
* For MPU support, the kernel-mode NuttX section is assumed to be 256KB of
* FLASH and 4KB of SRAM. That, of course, can be optimized as needed (See
- * also configs/lpc4088-devkit/scripts/kernel-space.ld); 256KB is probably much
+ * also boards/lpc4088-devkit/scripts/kernel-space.ld); 256KB is probably much
* more than is needed by the RTOS! That size is selected only because it
* is available due to alignment issues for the user space FLASH memory.
*
diff --git a/boards/lpc4088-devkit/scripts/user-space.ld b/boards/lpc4088-devkit/scripts/user-space.ld
index c4daf2c62a..1a174d8a9d 100644
--- a/boards/lpc4088-devkit/scripts/user-space.ld
+++ b/boards/lpc4088-devkit/scripts/user-space.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/lpc4088-devkit/scripts/user-space.ld
+ * boards/lpc4088-devkit/scripts/user-space.ld
*
* Copyright (C) 2013, 2015 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/lpc4088-quickstart/README.txt b/boards/lpc4088-quickstart/README.txt
index 0f6a88fa44..0fb495912e 100644
--- a/boards/lpc4088-quickstart/README.txt
+++ b/boards/lpc4088-quickstart/README.txt
@@ -82,7 +82,7 @@ Using OpenOCD with the Olimex ARM-USB-OCD
Building OpenOCD under Cygwin:
- Refer to configs/olimex-lpc1766stk/README.txt
+ Refer to boards/olimex-lpc1766stk/README.txt
Installing OpenOCD in Ubuntu Linux:
@@ -93,7 +93,7 @@ Using OpenOCD with the Olimex ARM-USB-OCD
I have been using the Olimex ARM-USB-OCD debugger. OpenOCD
requires a configuration file. I keep the one I used last here:
- configs/lpc4088-quickstart/tools/lpc4088-quickstart.cfg
+ boards/lpc4088-quickstart/tools/lpc4088-quickstart.cfg
However, the "correct" configuration script to use with OpenOCD may
change as the features of OpenOCD evolve. So you should at least
@@ -121,7 +121,7 @@ Using OpenOCD with the Olimex ARM-USB-OCD
installations. They could be most anywhwere if you are using a
windows version of OpenOCD.
- configs/lpc4088-quickstart/tools/lpc4088-quickstart.cfg
+ boards/lpc4088-quickstart/tools/lpc4088-quickstart.cfg
This is simply openocd-usb.cfg, lpc40xx.cfg, and lpc1xxx.cfg
concatenated into one file for convenience. Don't use it
unless you have to.
@@ -132,20 +132,20 @@ Using OpenOCD with the Olimex ARM-USB-OCD
- Possibly the value of OPENOCD_PATH and TARGET_PATH
- It assumes that the correct script to use is the one at
- configs/lpc4088-quickstart/tools/lpc4088-quickstart.cfg
+ boards/lpc4088-quickstart/tools/lpc4088-quickstart.cfg
Starting OpenOCD
Then you should be able to start the OpenOCD daemon as follows. This
assumes that you have already CD'ed to the NuttX build directory and
- that you have set the full path to the configs/lpc4088-quickstart/tools
+ that you have set the full path to the boards/lpc4088-quickstart/tools
in your PATH environment variable:
oocd.sh $PWD
or, if the PATH variable is not so configured:
- configs/lpc4088-quickstart/tools/oocd.sh $PWD
+ boards/lpc4088-quickstart/tools/oocd.sh $PWD
Connecting GDB
diff --git a/boards/lpc4088-quickstart/knsh/defconfig b/boards/lpc4088-quickstart/knsh/defconfig
index 440ceb4281..62d0063ca4 100644
--- a/boards/lpc4088-quickstart/knsh/defconfig
+++ b/boards/lpc4088-quickstart/knsh/defconfig
@@ -42,7 +42,7 @@ CONFIG_NSH_DISABLE_MKRD=y
CONFIG_NSH_FILEIOSIZE=512
CONFIG_NSH_READLINE=y
CONFIG_NUTTX_USERSPACE=0x00040000
-CONFIG_PASS1_BUILDIR="configs/lpc4088-quickstart/kernel"
+CONFIG_PASS1_BUILDIR="boards/lpc4088-quickstart/kernel"
CONFIG_PIPES=y
CONFIG_PREALLOC_MQ_MSGS=4
CONFIG_PREALLOC_TIMERS=4
diff --git a/boards/lpc4088-quickstart/scripts/kernel-space.ld b/boards/lpc4088-quickstart/scripts/kernel-space.ld
index c27292d066..ebc0677159 100644
--- a/boards/lpc4088-quickstart/scripts/kernel-space.ld
+++ b/boards/lpc4088-quickstart/scripts/kernel-space.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/lpc4088-quickstart/scripts/kernel-space.ld
+ * boards/lpc4088-quickstart/scripts/kernel-space.ld
*
* Copyright (C) 2013 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/lpc4088-quickstart/scripts/ld.script b/boards/lpc4088-quickstart/scripts/ld.script
index 223d097474..6364ef9f0d 100644
--- a/boards/lpc4088-quickstart/scripts/ld.script
+++ b/boards/lpc4088-quickstart/scripts/ld.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/lpc4088-quickstart/scripts/ld.script
+ * boards/lpc4088-quickstart/scripts/ld.script
*
* Copyright (C) 2013 Gregory Nutt. All rights reserved.
* Author: Rommel Marcelo
diff --git a/boards/lpc4088-quickstart/scripts/memory.ld b/boards/lpc4088-quickstart/scripts/memory.ld
index 6cf5900b02..c4dd383a3f 100644
--- a/boards/lpc4088-quickstart/scripts/memory.ld
+++ b/boards/lpc4088-quickstart/scripts/memory.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/lpc4088-quickstart/scripts/memory.ld
+ * boards/lpc4088-quickstart/scripts/memory.ld
*
* Copyright (C) 2013 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
@@ -41,7 +41,7 @@
*
* For MPU support, the kernel-mode NuttX section is assumed to be 256KB of
* FLASH and 4KB of SRAM. That, of course, can be optimized as needed (See
- * also configs/lpc4088-quickstart/scripts/kernel-space.ld); 256KB is probably much
+ * also boards/lpc4088-quickstart/scripts/kernel-space.ld); 256KB is probably much
* more than is needed by the RTOS! That size is selected only because it
* is available due to alignment issues for the user space FLASH memory.
*
diff --git a/boards/lpc4088-quickstart/scripts/user-space.ld b/boards/lpc4088-quickstart/scripts/user-space.ld
index 36551857a2..73822135b8 100644
--- a/boards/lpc4088-quickstart/scripts/user-space.ld
+++ b/boards/lpc4088-quickstart/scripts/user-space.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/lpc4088-quickstart/scripts/user-space.ld
+ * boards/lpc4088-quickstart/scripts/user-space.ld
*
* Copyright (C) 2013, 2015 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/lpc4330-xplorer/README.txt b/boards/lpc4330-xplorer/README.txt
index a1f3affafe..509e6f999d 100644
--- a/boards/lpc4330-xplorer/README.txt
+++ b/boards/lpc4330-xplorer/README.txt
@@ -269,7 +269,7 @@ Code Red IDE/Tools
The LPC18xx/LPC43xx debug driver can also be used to program the LPC43xx
flash directly from the command line. The script flash.sh that may be
- found in the configs/lpc4330-xplorer/scripts directory can do that with
+ found in the boards/lpc4330-xplorer/scripts directory can do that with
a single command line command.
Executing from SPIFI
@@ -378,7 +378,7 @@ the following lines in each Make.defs file:
Configuration Changes
---------------------
-Below are all of the configuration changes that I had to make to configs/stm3240g-eval/nsh2
+Below are all of the configuration changes that I had to make to boards/stm3240g-eval/nsh2
in order to successfully build NuttX using the Atollic toolchain WITH FPU support:
-CONFIG_ARCH_FPU=n : Enable FPU support
@@ -425,7 +425,7 @@ LPC4330-Xplorer Configuration Options
CONFIG_ARCH_CHIP_LPC4330=y
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=lpc4330-xplorer (for the LPC4330-Xplorer board)
diff --git a/boards/lpc4330-xplorer/scripts/ramconfig.ld b/boards/lpc4330-xplorer/scripts/ramconfig.ld
index d956120203..df2c83afb4 100644
--- a/boards/lpc4330-xplorer/scripts/ramconfig.ld
+++ b/boards/lpc4330-xplorer/scripts/ramconfig.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/lpc4330-xplorer/scripts/ramconfig.ld
+ * boards/lpc4330-xplorer/scripts/ramconfig.ld
*
* Copyright (C) 2012 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/lpc4330-xplorer/scripts/spificonfig.ld b/boards/lpc4330-xplorer/scripts/spificonfig.ld
index 8ed668beec..289e7e0c29 100644
--- a/boards/lpc4330-xplorer/scripts/spificonfig.ld
+++ b/boards/lpc4330-xplorer/scripts/spificonfig.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/lpc4330-xplorer/scripts/spificonfig.ld
+ * boards/lpc4330-xplorer/scripts/spificonfig.ld
*
* Copyright (C) 2012 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/lpc4337-ws/README.txt b/boards/lpc4337-ws/README.txt
index fce06d278b..82a53d6839 100644
--- a/boards/lpc4337-ws/README.txt
+++ b/boards/lpc4337-ws/README.txt
@@ -265,7 +265,7 @@ Code Red IDE/Tools
The LPC18xx/LPC43xx debug driver can also be used to program the LPC43xx
flash directly from the command line. The script flash.sh that may be
- found in the configs/LPC4337-ws/scripts directory can do that with
+ found in the boards/LPC4337-ws/scripts directory can do that with
a single command line command.
Executing from SPIFI
@@ -417,7 +417,7 @@ the following lines in each Make.defs file:
Configuration Changes
---------------------
-Below are all of the configuration changes that I had to make to configs/stm3240g-eval/nsh2
+Below are all of the configuration changes that I had to make to boards/stm3240g-eval/nsh2
in order to successfully build NuttX using the Atollic toolchain WITH FPU support:
-CONFIG_ARCH_FPU=n : Enable FPU support
@@ -464,7 +464,7 @@ LPC4337-ws Configuration Options
CONFIG_ARCH_CHIP_LPC4337=y
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=LPC4337-ws (for the LPC4337-ws board)
diff --git a/boards/lpc4337-ws/scripts/flashaconfig.ld b/boards/lpc4337-ws/scripts/flashaconfig.ld
index e08c459bb8..1ebc32372a 100644
--- a/boards/lpc4337-ws/scripts/flashaconfig.ld
+++ b/boards/lpc4337-ws/scripts/flashaconfig.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/lpc4337-ws/scripts/flashconfig.ld
+ * boards/lpc4337-ws/scripts/flashconfig.ld
*
* Copyright (C) 2016 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/lpc4337-ws/scripts/ramconfig.ld b/boards/lpc4337-ws/scripts/ramconfig.ld
index 95580daa5b..1b714cf052 100644
--- a/boards/lpc4337-ws/scripts/ramconfig.ld
+++ b/boards/lpc4337-ws/scripts/ramconfig.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/lpc4337-ws/scripts/ramconfig.ld
+ * boards/lpc4337-ws/scripts/ramconfig.ld
*
* Copyright (C) 2016 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/lpc4357-evb/README.txt b/boards/lpc4357-evb/README.txt
index 9cfe19d003..5c046f357b 100644
--- a/boards/lpc4357-evb/README.txt
+++ b/boards/lpc4357-evb/README.txt
@@ -262,7 +262,7 @@ Code Red IDE/Tools
The LPC18xx/LPC43xx debug driver can also be used to program the LPC43xx
flash directly from the command line. The script flash.sh that may be
- found in the configs/lpc4357-evb/scripts directory can do that with
+ found in the boards/lpc4357-evb/scripts directory can do that with
a single command line command.
Executing from SPIFI
@@ -414,7 +414,7 @@ the following lines in each Make.defs file:
Configuration Changes
---------------------
-Below are all of the configuration changes that I had to make to configs/stm3240g-eval/nsh2
+Below are all of the configuration changes that I had to make to boards/stm3240g-eval/nsh2
in order to successfully build NuttX using the Atollic toolchain WITH FPU support:
-CONFIG_ARCH_FPU=n : Enable FPU support
@@ -461,7 +461,7 @@ LPC4357-EVB Configuration Options
CONFIG_ARCH_CHIP_LPC4357=y
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=lpc4357-evb (for the LPC4357-EVB board)
diff --git a/boards/lpc4357-evb/scripts/flashaconfig.ld b/boards/lpc4357-evb/scripts/flashaconfig.ld
index 962401af1e..2a28599ff1 100644
--- a/boards/lpc4357-evb/scripts/flashaconfig.ld
+++ b/boards/lpc4357-evb/scripts/flashaconfig.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/lpc4357-evb/scripts/flashconfig.ld
+ * boards/lpc4357-evb/scripts/flashconfig.ld
*
* Copyright (C) 2014 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/lpc4357-evb/scripts/ramconfig.ld b/boards/lpc4357-evb/scripts/ramconfig.ld
index 90c1a4e247..96dff999fc 100644
--- a/boards/lpc4357-evb/scripts/ramconfig.ld
+++ b/boards/lpc4357-evb/scripts/ramconfig.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/lpc4357-evb/scripts/ramconfig.ld
+ * boards/lpc4357-evb/scripts/ramconfig.ld
*
* Copyright (C) 2014 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/lpc4357-evb/scripts/spificonfig.ld b/boards/lpc4357-evb/scripts/spificonfig.ld
index f23adf5097..c0d82fee4e 100644
--- a/boards/lpc4357-evb/scripts/spificonfig.ld
+++ b/boards/lpc4357-evb/scripts/spificonfig.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/lpc4357-evb/scripts/spificonfig.ld
+ * boards/lpc4357-evb/scripts/spificonfig.ld
*
* Copyright (C) 2014 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/lpc4370-link2/README.txt b/boards/lpc4370-link2/README.txt
index 321ad4294a..fdcf89ac0a 100644
--- a/boards/lpc4370-link2/README.txt
+++ b/boards/lpc4370-link2/README.txt
@@ -265,7 +265,7 @@ Code Red IDE/Tools
The LPC18xx/LPC43xx debug driver can also be used to program the LPC43xx
flash directly from the command line. The script flash.sh that may be
- found in the configs/LPC4370-Link2/scripts directory can do that with
+ found in the boards/LPC4370-Link2/scripts directory can do that with
a single command line command.
Executing from SPIFI
@@ -417,7 +417,7 @@ the following lines in each Make.defs file:
Configuration Changes
---------------------
-Below are all of the configuration changes that I had to make to configs/stm3240g-eval/nsh2
+Below are all of the configuration changes that I had to make to boards/stm3240g-eval/nsh2
in order to successfully build NuttX using the Atollic toolchain WITH FPU support:
-CONFIG_ARCH_FPU=n : Enable FPU support
@@ -464,7 +464,7 @@ LPC4370-Link2 Configuration Options
CONFIG_ARCH_CHIP_LPC4370=y
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=LPC4370-Link2 (for the LPC4370-Link2 board)
diff --git a/boards/lpc4370-link2/scripts/ramconfig.ld b/boards/lpc4370-link2/scripts/ramconfig.ld
index 4449dc1195..f2def59b72 100644
--- a/boards/lpc4370-link2/scripts/ramconfig.ld
+++ b/boards/lpc4370-link2/scripts/ramconfig.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/lpc4370-link2/scripts/ramconfig.ld
+ * boards/lpc4370-link2/scripts/ramconfig.ld
*
* Copyright (C) 2012 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/lpc4370-link2/scripts/spificonfig.ld b/boards/lpc4370-link2/scripts/spificonfig.ld
index d0f420c0e8..9de91e0864 100644
--- a/boards/lpc4370-link2/scripts/spificonfig.ld
+++ b/boards/lpc4370-link2/scripts/spificonfig.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/lpc4370-link2/scripts/spificonfig.ld
+ * boards/lpc4370-link2/scripts/spificonfig.ld
*
* Copyright (C) 2012 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/lpcxpresso-lpc1768/README.txt b/boards/lpcxpresso-lpc1768/README.txt
index 648735519e..c43a5b3eda 100644
--- a/boards/lpcxpresso-lpc1768/README.txt
+++ b/boards/lpcxpresso-lpc1768/README.txt
@@ -323,7 +323,7 @@ Code Red IDE
--------------
All of the above steps are automated in the bash script flash.sh that can
- be found in the configs/lpcxpresso/tools directory.
+ be found in the boards/lpcxpresso/tools directory.
LEDs
^^^^
@@ -331,12 +331,12 @@ LEDs
If CONFIG_ARCH_LEDS is defined, then support for the LPCXpresso LEDs will be
included in the build. See:
- - configs/lpcxpresso-lpc1768/include/board.h - Defines LED constants, types and
+ - boards/lpcxpresso-lpc1768/include/board.h - Defines LED constants, types and
prototypes the LED interface functions.
- - configs/lpcxpresso-lpc1768/src/lpcxpresso-lpc1768.h - GPIO settings for the LEDs.
+ - boards/lpcxpresso-lpc1768/src/lpcxpresso-lpc1768.h - GPIO settings for the LEDs.
- - configs/lpcxpresso-lpc1768/src/up_leds.c - LED control logic.
+ - boards/lpcxpresso-lpc1768/src/up_leds.c - LED control logic.
The LPCXpresso LPC1768 has a single LEDs (there are more on the Embedded Artists
base board, but those are not controlled by NuttX). Usage this single LED by NuttX
@@ -390,7 +390,7 @@ LPCXpresso Configuration Options
CONFIG_ARCH_CHIP_LPC1768=y
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=lpcxpresso-lpc1768
diff --git a/boards/lpcxpresso-lpc1768/scripts/ld.script b/boards/lpcxpresso-lpc1768/scripts/ld.script
index b2b8bcf425..70ac0df335 100644
--- a/boards/lpcxpresso-lpc1768/scripts/ld.script
+++ b/boards/lpcxpresso-lpc1768/scripts/ld.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/lpcxpresso-lpc1768/scripts/ld.script
+ * boards/lpcxpresso-lpc1768/scripts/ld.script
*
* Copyright (C) 2011-2012 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/lpcxpresso-lpc54628/scripts/flash.ld b/boards/lpcxpresso-lpc54628/scripts/flash.ld
index 42a0396af8..5a71b338dc 100644
--- a/boards/lpcxpresso-lpc54628/scripts/flash.ld
+++ b/boards/lpcxpresso-lpc54628/scripts/flash.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/lpcxpresso-lpc54628/scripts/flash.ld
+ * boards/lpcxpresso-lpc54628/scripts/flash.ld
*
* Copyright (C) 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/makerlisp/README.txt b/boards/makerlisp/README.txt
index a80490c213..b983985673 100644
--- a/boards/makerlisp/README.txt
+++ b/boards/makerlisp/README.txt
@@ -46,7 +46,7 @@ Other Versions
If you use any version of ZDS-II other than 5.3.0 or if you install ZDS-II
at any location other than the default location, you will have to modify
three files: (1) arch/arm/z80/src/ez80/Kconfig, (2)
- configs/makerlisp/scripts/Make.defs and, perhaps, (3)
+ boards/makerlisp/scripts/Make.defs and, perhaps, (3)
arch/z80/src/ez80/Toolchain.defs.
Serial Console
@@ -434,7 +434,7 @@ Configuration Subdirectories
the application's reset vector resides at address 0x040000 in external
SRAM.
- The boot loader source is located at configs/makerlisp/src/sd_main.c.
+ The boot loader source is located at boards/makerlisp/src/sd_main.c.
STATUS:
2019-06-26: Configuration added. Not yet verified.
diff --git a/boards/makerlisp/nsh_flash/README.txt b/boards/makerlisp/nsh_flash/README.txt
index 5b47610afc..f5a2587e1c 100644
--- a/boards/makerlisp/nsh_flash/README.txt
+++ b/boards/makerlisp/nsh_flash/README.txt
@@ -8,6 +8,6 @@ nsh.zfpproj is a simple project that will allow you to use the Smart Flash
due to RAM configuration in the project. Use ZDS-II instead as is described
in the upper README.txt file
nsh_flash.ztgt is the target file that accompanies the project files. This
- one is identical to configs/scripts/makerlisp_ram.ztgt.
+ one is identical to boards/scripts/makerlisp_ram.ztgt.
nsh_ram.ztgt is the target file that accompanies the project files. This
- one is identical to configs/scripts/makerlisp_flash.ztgt.
+ one is identical to boards/scripts/makerlisp_flash.ztgt.
diff --git a/boards/makerlisp/nsh_ram/README.txt b/boards/makerlisp/nsh_ram/README.txt
index 5b47610afc..f5a2587e1c 100644
--- a/boards/makerlisp/nsh_ram/README.txt
+++ b/boards/makerlisp/nsh_ram/README.txt
@@ -8,6 +8,6 @@ nsh.zfpproj is a simple project that will allow you to use the Smart Flash
due to RAM configuration in the project. Use ZDS-II instead as is described
in the upper README.txt file
nsh_flash.ztgt is the target file that accompanies the project files. This
- one is identical to configs/scripts/makerlisp_ram.ztgt.
+ one is identical to boards/scripts/makerlisp_ram.ztgt.
nsh_ram.ztgt is the target file that accompanies the project files. This
- one is identical to configs/scripts/makerlisp_flash.ztgt.
+ one is identical to boards/scripts/makerlisp_flash.ztgt.
diff --git a/boards/makerlisp/scripts/makerlisp_copytoram.linkcmd b/boards/makerlisp/scripts/makerlisp_copytoram.linkcmd
index e678ad0c90..f15b30b9df 100644
--- a/boards/makerlisp/scripts/makerlisp_copytoram.linkcmd
+++ b/boards/makerlisp/scripts/makerlisp_copytoram.linkcmd
@@ -1,5 +1,5 @@
/****************************************************************************/
-/* configs/makerlisp/scripts/makerlisp_copytoram.linkcmd */
+/* boards/makerlisp/scripts/makerlisp_copytoram.linkcmd */
/* For configurations booting from flash but otherwise running out of RAM */
/* */
/* Copyright (C) 2019 Gregory Nutt. All rights reserved. */
diff --git a/boards/makerlisp/scripts/makerlisp_flash.linkcmd b/boards/makerlisp/scripts/makerlisp_flash.linkcmd
index 47fec0eb74..4746235487 100644
--- a/boards/makerlisp/scripts/makerlisp_flash.linkcmd
+++ b/boards/makerlisp/scripts/makerlisp_flash.linkcmd
@@ -1,5 +1,5 @@
/****************************************************************************/
-/* configs/makerlisp/scripts/makerlisp_flash.linkcmd */
+/* boards/makerlisp/scripts/makerlisp_flash.linkcmd */
/* For configurations running entirely out of FLASH */
/* */
/* Copyright (C) 2019 Gregory Nutt. All rights reserved. */
diff --git a/boards/makerlisp/scripts/makerlisp_ram.linkcmd b/boards/makerlisp/scripts/makerlisp_ram.linkcmd
index d7e92ac199..cb80083cfc 100644
--- a/boards/makerlisp/scripts/makerlisp_ram.linkcmd
+++ b/boards/makerlisp/scripts/makerlisp_ram.linkcmd
@@ -1,5 +1,5 @@
/****************************************************************************/
-/* configs/makerlisp/scripts/makerlisp_ram.linkcmd */
+/* boards/makerlisp/scripts/makerlisp_ram.linkcmd */
/* For configurations running entirely out of RAM with nothing in FLASH */
/* */
/* Copyright (C) 2019 Gregory Nutt. All rights reserved. */
diff --git a/boards/makerlisp/sdboot/README.txt b/boards/makerlisp/sdboot/README.txt
index 75ef350f0f..48ce60a1ea 100644
--- a/boards/makerlisp/sdboot/README.txt
+++ b/boards/makerlisp/sdboot/README.txt
@@ -8,6 +8,6 @@ sdboot.zfpproj is a simple project that will allow you to use the Smart Flash
due to RAM configuration in the project. Use ZDS-II instead as is described
in the upper README.txt file
sdboot_flash.ztgt is the target file that accompanies the project files. This
- one is identical to configs/scripts/makerlisp_ram.ztgt.
+ one is identical to boards/scripts/makerlisp_ram.ztgt.
sdboot_ram.ztgt is the target file that accompanies the project files. This
- one is identical to configs/scripts/makerlisp_flash.ztgt.
+ one is identical to boards/scripts/makerlisp_flash.ztgt.
diff --git a/boards/maple/scripts/ld.script b/boards/maple/scripts/ld.script
index 036d44e113..e5055de2f4 100644
--- a/boards/maple/scripts/ld.script
+++ b/boards/maple/scripts/ld.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/maple/scripts/ld.script
+ * boards/maple/scripts/ld.script
*
* Copyright (C) 2013 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/maple/scripts/ld.script.dfu b/boards/maple/scripts/ld.script.dfu
index 47d2111d2d..84df059dbd 100644
--- a/boards/maple/scripts/ld.script.dfu
+++ b/boards/maple/scripts/ld.script.dfu
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/maple/scripts/ld.script.dfu
+ * boards/maple/scripts/ld.script.dfu
*
* Copyright (C) 2013 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/max32660-evsys/scripts/flash.ld b/boards/max32660-evsys/scripts/flash.ld
index dc3c5a84c5..1a2254e271 100644
--- a/boards/max32660-evsys/scripts/flash.ld
+++ b/boards/max32660-evsys/scripts/flash.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/max32660-evsys/scripts/flash.ld
+ * boards/max32660-evsys/scripts/flash.ld
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/max32660-evsys/scripts/sram.ld b/boards/max32660-evsys/scripts/sram.ld
index 679ae6a68c..e99313c028 100644
--- a/boards/max32660-evsys/scripts/sram.ld
+++ b/boards/max32660-evsys/scripts/sram.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/max32660-evsys/scripts/sram.ld
+ * boards/max32660-evsys/scripts/sram.ld
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/mbed/README.txt b/boards/mbed/README.txt
index 79d2c9b44f..27f16dceea 100644
--- a/boards/mbed/README.txt
+++ b/boards/mbed/README.txt
@@ -35,7 +35,7 @@ mbed Configuration Options
CONFIG_ARCH_CHIP_LPC1768=y
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=mbed (for the mbed.org board)
diff --git a/boards/mbed/scripts/ld.script b/boards/mbed/scripts/ld.script
index ddd3bc20cb..644fbbd8bd 100644
--- a/boards/mbed/scripts/ld.script
+++ b/boards/mbed/scripts/ld.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/mbed/scripts/ld.script
+ * boards/mbed/scripts/ld.script
*
* Copyright (C) 2010 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/mcb1700/README.txt b/boards/mcb1700/README.txt
index 25f747ceb5..1685fabdd3 100644
--- a/boards/mcb1700/README.txt
+++ b/boards/mcb1700/README.txt
@@ -36,7 +36,7 @@ mcb1700 Configuration Options
CONFIG_ARCH_CHIP_LPC1768=y
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=mcb1700 (for the mcb1700.org board)
diff --git a/boards/mcb1700/scripts/ld.script b/boards/mcb1700/scripts/ld.script
index 4e43d9dda7..4112866b2e 100644
--- a/boards/mcb1700/scripts/ld.script
+++ b/boards/mcb1700/scripts/ld.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/mcb1700/scripts/ld.script
+ * boards/mcb1700/scripts/ld.script
*
* Copyright (C) 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/mcu123-lpc214x/README.txt b/boards/mcu123-lpc214x/README.txt
index df3471d0ee..7461fb66e4 100644
--- a/boards/mcu123-lpc214x/README.txt
+++ b/boards/mcu123-lpc214x/README.txt
@@ -99,7 +99,7 @@ NuttX buildroot Toolchain
4. cd /buildroot
- 5. cp configs/arm7tdmi-defconfig-4.3.3 .config
+ 5. cp boards/arm7tdmi-defconfig-4.3.3 .config
6. make oldconfig
@@ -108,7 +108,7 @@ NuttX buildroot Toolchain
8. Make sure that the PATH variable includes the path to the newly built
binaries.
- See the file configs/README.txt in the buildroot source tree. That has more
+ See the file boards/README.txt in the buildroot source tree. That has more
detailed PLUS some special instructions that you will need to follow if you are
building a Cortex-M3 toolchain for Cygwin under Windows.
@@ -225,7 +225,7 @@ ARM/LPC214X-specific Configuration Options
CONFIG_ARCH_CHIP_LPC214X
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=mcu123-lpc214x
diff --git a/boards/mcu123-lpc214x/scripts/ld.script b/boards/mcu123-lpc214x/scripts/ld.script
index 7102110e75..d7a9cae2e3 100644
--- a/boards/mcu123-lpc214x/scripts/ld.script
+++ b/boards/mcu123-lpc214x/scripts/ld.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/mcu123-lpc214x/scripts/ld.script
+ * boards/mcu123-lpc214x/scripts/ld.script
*
* Copyright (C) 2008-2009, 2012 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/metro-m4/README.txt b/boards/metro-m4/README.txt
index de2c564a77..6432791dee 100644
--- a/boards/metro-m4/README.txt
+++ b/boards/metro-m4/README.txt
@@ -186,9 +186,9 @@ Unlocking FLASH
into NVM. See https://en.m.wikipedia.org/wiki/SREC_(file_format) for a
description of the Motorola SREC format.
- I wrote a small program at configs/metro-m4-scripts/nvm.c that will
+ I wrote a small program at boards/metro-m4-scripts/nvm.c that will
generate this Motorola SREC file with the correct checksum. The file at
- configs/metro-m4-scripts/nvm.c is the output of that program.
+ boards/metro-m4-scripts/nvm.c is the output of that program.
J-Link>mem8 804000,10
00804000 = 39 92 9A F6 80 FF EC AE FF FF FF FF FF FF FF FF
diff --git a/boards/metro-m4/scripts/flash.ld b/boards/metro-m4/scripts/flash.ld
index a162f40be2..e68f785076 100644
--- a/boards/metro-m4/scripts/flash.ld
+++ b/boards/metro-m4/scripts/flash.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/metro-m4/scripts/flash.ld
+ * boards/metro-m4/scripts/flash.ld
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/metro-m4/scripts/sram.ld b/boards/metro-m4/scripts/sram.ld
index 46bbbe4c57..fb8b779233 100644
--- a/boards/metro-m4/scripts/sram.ld
+++ b/boards/metro-m4/scripts/sram.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/metro-m4/scripts/sram.ld
+ * boards/metro-m4/scripts/sram.ld
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/micropendous3/README.txt b/boards/micropendous3/README.txt
index f224f7428a..26cbbd616c 100644
--- a/boards/micropendous3/README.txt
+++ b/boards/micropendous3/README.txt
@@ -302,7 +302,7 @@ NuttX buildroot Toolchain
4. cd /buildroot
- 5. cp configs/avr-defconfig-4.5.2 .config
+ 5. cp boards/avr-defconfig-4.5.2 .config
6. make oldconfig
@@ -311,7 +311,7 @@ NuttX buildroot Toolchain
8. Make sure that the PATH variable includes the path to the newly built
binaries.
- See the file configs/README.txt in the buildroot source tree. That has more
+ See the file boards/README.txt in the buildroot source tree. That has more
detailed PLUS some special instructions that you will need to follow if you
are building a toolchain for Cygwin under Windows.
@@ -406,7 +406,7 @@ Micropendous3 Configuration Options
Depending on which Micropendous3 version you have.
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=micropendous3
diff --git a/boards/micropendous3/scripts/micropendous3.ld b/boards/micropendous3/scripts/micropendous3.ld
index 6f5e5fe208..247d1e64c4 100644
--- a/boards/micropendous3/scripts/micropendous3.ld
+++ b/boards/micropendous3/scripts/micropendous3.ld
@@ -1,5 +1,5 @@
/**************************************************************************************
- * configs/micropendous3/scripts/micropendous3.ld
+ * boards/micropendous3/scripts/micropendous3.ld
*
* Copyright (C) 2011, 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/mikroe-stm32f4/README.txt b/boards/mikroe-stm32f4/README.txt
index bb27a81191..1f29a76188 100644
--- a/boards/mikroe-stm32f4/README.txt
+++ b/boards/mikroe-stm32f4/README.txt
@@ -184,7 +184,7 @@ the following lines in each Make.defs file:
Configuration Changes
---------------------
-Below are all of the configuration changes that I had to make to configs/stm3240g-eval/nsh2
+Below are all of the configuration changes that I had to make to boards/stm3240g-eval/nsh2
in order to successfully build NuttX using the Atollic toolchain WITH FPU support:
-CONFIG_ARCH_FPU=n : Enable FPU support
@@ -236,7 +236,7 @@ Mikroe-STM32F4-specific Configuration Options
CONFIG_ARCH_BOARD_STM32_CUSTOM_CLOCKCONFIG=n
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=Mikroe-STM32F4 (for the Mikroe-STM32F4 development board)
diff --git a/boards/mikroe-stm32f4/kostest/defconfig b/boards/mikroe-stm32f4/kostest/defconfig
index 0e46c516ba..f2a3fb03c0 100644
--- a/boards/mikroe-stm32f4/kostest/defconfig
+++ b/boards/mikroe-stm32f4/kostest/defconfig
@@ -55,7 +55,7 @@ CONFIG_NSH_LINELEN=64
CONFIG_NSH_READLINE=y
CONFIG_NSH_STRERROR=y
CONFIG_NUTTX_USERSPACE=0x08020000
-CONFIG_PASS1_BUILDIR="configs/mikroe-stm32f4/kernel"
+CONFIG_PASS1_BUILDIR="boards/mikroe-stm32f4/kernel"
CONFIG_PREALLOC_MQ_MSGS=4
CONFIG_PREALLOC_TIMERS=4
CONFIG_PREALLOC_WDOGS=8
diff --git a/boards/mikroe-stm32f4/scripts/gnu-elf.ld b/boards/mikroe-stm32f4/scripts/gnu-elf.ld
index 52064241f6..68f62d0b30 100644
--- a/boards/mikroe-stm32f4/scripts/gnu-elf.ld
+++ b/boards/mikroe-stm32f4/scripts/gnu-elf.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/mikroe-stm32f4/scripts/gnu-elf.ld
+ * boards/mikroe-stm32f4/scripts/gnu-elf.ld
*
* Copyright (C) 2012-2013 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/mikroe-stm32f4/scripts/kernel-space.ld b/boards/mikroe-stm32f4/scripts/kernel-space.ld
index 383bbe5f29..39b3402701 100644
--- a/boards/mikroe-stm32f4/scripts/kernel-space.ld
+++ b/boards/mikroe-stm32f4/scripts/kernel-space.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/mikroe-stm32f4/scripts/kernel-space.ld
+ * boards/mikroe-stm32f4/scripts/kernel-space.ld
*
* Copyright (C) 2013 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/mikroe-stm32f4/scripts/ld.script b/boards/mikroe-stm32f4/scripts/ld.script
index 0b4bd07457..396629f4c2 100644
--- a/boards/mikroe-stm32f4/scripts/ld.script
+++ b/boards/mikroe-stm32f4/scripts/ld.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/mikroe-stm32f4/scripts/ld.script
+ * boards/mikroe-stm32f4/scripts/ld.script
*
* Copyright (C) 2011-2013 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/mikroe-stm32f4/scripts/memory.ld b/boards/mikroe-stm32f4/scripts/memory.ld
index f81320551a..19d3c11b4d 100644
--- a/boards/mikroe-stm32f4/scripts/memory.ld
+++ b/boards/mikroe-stm32f4/scripts/memory.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/stm32f4discovery/scripts/memory.ld
+ * boards/stm32f4discovery/scripts/memory.ld
*
* Copyright (C) 2013 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
@@ -47,7 +47,7 @@
* For MPU support, the kernel-mode NuttX section is assumed to be 128Kb of
* FLASH and 4Kb of SRAM. That is an excessive amount for the kernel which
* should fit into 64KB and, of course, can be optimized as needed (See
- * also configs/stm32f4discovery/scripts/kernel-space.ld). Allowing the
+ * also boards/stm32f4discovery/scripts/kernel-space.ld). Allowing the
* additional does permit addition debug instrumentation to be added to the
* kernel space without overflowing the partition.
*
diff --git a/boards/mikroe-stm32f4/scripts/user-space.ld b/boards/mikroe-stm32f4/scripts/user-space.ld
index ffb106d8d0..8c0fb7b95a 100644
--- a/boards/mikroe-stm32f4/scripts/user-space.ld
+++ b/boards/mikroe-stm32f4/scripts/user-space.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/mikroe-stm32f4/scripts/user-space.ld
+ * boards/mikroe-stm32f4/scripts/user-space.ld
*
* Copyright (C) 2013, 2015 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/mirtoo/README.txt b/boards/mirtoo/README.txt
index f018d4ab6c..97ca5b9574 100644
--- a/boards/mirtoo/README.txt
+++ b/boards/mirtoo/README.txt
@@ -1,4 +1,4 @@
-configs/mirtoo README
+boards/mirtoo README
=====================
This README file discusses the port of NuttX to the DTX1-4000L "Mirtoo" module.
@@ -574,7 +574,7 @@ Analog Input
CONFIG_ADC_PGA11X=y : Enable support for the PGA117
When CONFIG_PIC32MX_ADC=y is defined, the Mirtoo boot up logic will
- automatically configure pin 18 (AN0) as an analog input (see configs/mirtoo/src/up_adc.c).
+ automatically configure pin 18 (AN0) as an analog input (see boards/mirtoo/src/up_adc.c).
To initializee and use the PGA117, you to add logic something like the
following in your application code:
@@ -618,7 +618,7 @@ Analog Input
return -EIO;
}
- The above logic may belong in configs/mirtoo/src/up_adc.c?
+ The above logic may belong in boards/mirtoo/src/up_adc.c?
There is still one missing piece to complete the analog support on the
Mirtoo. This is the ADC driver that collects analog data and provides
@@ -629,14 +629,14 @@ Analog Input
the ADC interfaces defined in include/nuttx/analog/adc.h and must
be built when CONFIG_PIC32MX_ADC is defined.
- (2) configs/mirtoo/up_adc.c. Add Mirtoo logic that initializes and
+ (2) boards/mirtoo/up_adc.c. Add Mirtoo logic that initializes and
registers the ADC driver.
A complete ADC driver will be a considerable amount of work to support
all of the ADC features (such as timer driven sampling). If all you want
to do is a simple analog conversion, then in lieu of a real ADC driver,
you can use simple in-line logic such as you can see in the PIC32MX7 MMB
- touchscreen driver at configs/pic32mx7mmb/src/up_touchscreen.c
+ touchscreen driver at boards/pic32mx7mmb/src/up_touchscreen.c
PIC32MX Configuration Options
=============================
@@ -665,7 +665,7 @@ PIC32MX Configuration Options
CONFIG_ARCH_CHIP_PIC32MX250F128D=y
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=mirtoo
diff --git a/boards/mirtoo/scripts/c32-debug.ld b/boards/mirtoo/scripts/c32-debug.ld
index 161c5b81ea..b3f4dccf92 100644
--- a/boards/mirtoo/scripts/c32-debug.ld
+++ b/boards/mirtoo/scripts/c32-debug.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/mirtoo/scripts/c32-debug.ld
+ * boards/mirtoo/scripts/c32-debug.ld
*
* Copyright (C) 2012 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/mirtoo/scripts/c32-release.ld b/boards/mirtoo/scripts/c32-release.ld
index e34a3b8e12..03b38810be 100644
--- a/boards/mirtoo/scripts/c32-release.ld
+++ b/boards/mirtoo/scripts/c32-release.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/mirtoo/scripts/c32-release.ld
+ * boards/mirtoo/scripts/c32-release.ld
*
* Copyright (C) 2012 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/mirtoo/scripts/mips-elf-debug.ld b/boards/mirtoo/scripts/mips-elf-debug.ld
index 990bc154b6..931822c62a 100644
--- a/boards/mirtoo/scripts/mips-elf-debug.ld
+++ b/boards/mirtoo/scripts/mips-elf-debug.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/mirtoo/scripts/mips-elf-debug.ld
+ * boards/mirtoo/scripts/mips-elf-debug.ld
*
* Copyright (C) 2012 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/mirtoo/scripts/mips-elf-release.ld b/boards/mirtoo/scripts/mips-elf-release.ld
index 2c3ee892fc..05468374b9 100644
--- a/boards/mirtoo/scripts/mips-elf-release.ld
+++ b/boards/mirtoo/scripts/mips-elf-release.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/mirtoo/scripts/mips-elf-release.ld
+ * boards/mirtoo/scripts/mips-elf-release.ld
*
* Copyright (C) 2012 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/mirtoo/scripts/xc32-debug.ld b/boards/mirtoo/scripts/xc32-debug.ld
index 3c5cc949df..04dbb24d42 100644
--- a/boards/mirtoo/scripts/xc32-debug.ld
+++ b/boards/mirtoo/scripts/xc32-debug.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/mirtoo/scripts/xc32-debug.ld
+ * boards/mirtoo/scripts/xc32-debug.ld
*
* Copyright (C) 2012 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/mirtoo/scripts/xc32-release.ld b/boards/mirtoo/scripts/xc32-release.ld
index b6b24cc718..e88b31cf9a 100644
--- a/boards/mirtoo/scripts/xc32-release.ld
+++ b/boards/mirtoo/scripts/xc32-release.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/mirtoo/scripts/xc32-release.ld
+ * boards/mirtoo/scripts/xc32-release.ld
*
* Copyright (C) 2012 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/misoc/README.txt b/boards/misoc/README.txt
index e2aadb9173..c1d0848457 100644
--- a/boards/misoc/README.txt
+++ b/boards/misoc/README.txt
@@ -50,7 +50,7 @@ Buildroot Toolchain
Make sure that he PATH variable includes the path to the newly built
binaries.
- See the file configs/README.txt in the buildroot source tree. That has more
+ See the file boards/README.txt in the buildroot source tree. That has more
detailed PLUS some special instructions that you will need to follow if you
are building a LM32 toolchain for Cygwin under Windows. Also included in
that README file is a FAQ of frequent build issues that their work-arounds.
@@ -60,19 +60,19 @@ Buildroot Toolchain
CONFIG_LM3S_TOOLCHAIN_BUILDROOT=y
-configs/misoc/include/generated
+boards/misoc/include/generated
===============================
In order to build this configuration, you must provide the
- configs/misoc/include/generated directory. It contains the generated
+ boards/misoc/include/generated directory. It contains the generated
Misoc files and may be a symbolic link. The base configurtion will NOT
build without this directory!
- There is a sample generated directory at configs/misoc/include/generated-sample.
+ There is a sample generated directory at boards/misoc/include/generated-sample.
If you want to do a test build without generating the architecture, then
you can simply link this sample directory like:
- $ ln -s configs/misoc/include/generated-sample configs/misoc/include/generated
+ $ ln -s boards/misoc/include/generated-sample boards/misoc/include/generated
That should permit a test build.
diff --git a/boards/misoc/scripts/lm32.ld b/boards/misoc/scripts/lm32.ld
index 32b7f44e2c..ba6bc31ba8 100644
--- a/boards/misoc/scripts/lm32.ld
+++ b/boards/misoc/scripts/lm32.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/misoc/hello/script/ld.script
+ * boards/misoc/hello/script/ld.script
*
* Copyright (C) 2016 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/misoc/scripts/minerva.ld b/boards/misoc/scripts/minerva.ld
index 0c9089b7f3..c3da040192 100644
--- a/boards/misoc/scripts/minerva.ld
+++ b/boards/misoc/scripts/minerva.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/misoc/scripts/ld.script
+ * boards/misoc/scripts/ld.script
*
* Copyright (C) 2019 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/moteino-mega/README.txt b/boards/moteino-mega/README.txt
index 09ac7efd09..2a6888ddd0 100644
--- a/boards/moteino-mega/README.txt
+++ b/boards/moteino-mega/README.txt
@@ -151,7 +151,7 @@ MoteinoMEGA Configuration Options
CONFIG_ARCH_CHIP_ATMEGA1284P=y
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=moteino-mega
diff --git a/boards/moteino-mega/scripts/ld.script b/boards/moteino-mega/scripts/ld.script
index 202da17f24..ab1225bef8 100644
--- a/boards/moteino-mega/scripts/ld.script
+++ b/boards/moteino-mega/scripts/ld.script
@@ -1,5 +1,5 @@
/**************************************************************************************
- * configs/moteino-mega/scripts/ld.script
+ * boards/moteino-mega/scripts/ld.script
*
* Copyright (C) 2015 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/moxa/scripts/moxa.ld b/boards/moxa/scripts/moxa.ld
index 7d5d49a2a0..a1cc951583 100644
--- a/boards/moxa/scripts/moxa.ld
+++ b/boards/moxa/scripts/moxa.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/moxa/scripts/moxa.ld
+ * boards/moxa/scripts/moxa.ld
*
* Copyright (C) 2013, 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/ne64badge/README.txt b/boards/ne64badge/README.txt
index be257e12f3..7b2f45ff5e 100644
--- a/boards/ne64badge/README.txt
+++ b/boards/ne64badge/README.txt
@@ -238,7 +238,7 @@ NuttX Buildroot Toolchain
4. cd /buildroot
- 5. cp configs/m9s12x-defconfig-3.3.6 .config
+ 5. cp boards/m9s12x-defconfig-3.3.6 .config
6. make oldconfig
@@ -252,7 +252,7 @@ NuttX Buildroot Toolchain
8. Make sure that the PATH variable includes the path to the newly built
binaries.
- See the file configs/README.txt in the buildroot source tree. That has more
+ See the file boards/README.txt in the buildroot source tree. That has more
detailed PLUS some special instructions that you will need to follow if you are
building a Cortex-M3 toolchain for Cygwin under Windows.
@@ -383,7 +383,7 @@ HCS12/NE64BADGE-specific Configuration Options
CONFIG_ARCH_CHIP_MCS92S12NEC64
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=ne64badge
diff --git a/boards/ne64badge/scripts/ne64badge-banked.ld b/boards/ne64badge/scripts/ne64badge-banked.ld
index 8a86ba95b8..5a73a641a2 100644
--- a/boards/ne64badge/scripts/ne64badge-banked.ld
+++ b/boards/ne64badge/scripts/ne64badge-banked.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/ne64badge/ostest/ne64badge-banked.ld
+ * boards/ne64badge/ostest/ne64badge-banked.ld
*
* Copyright (C) 2011m, 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/ne64badge/scripts/ne64badge-nonbanked.ld b/boards/ne64badge/scripts/ne64badge-nonbanked.ld
index 5bf5a1a492..5c6b8bab0f 100644
--- a/boards/ne64badge/scripts/ne64badge-nonbanked.ld
+++ b/boards/ne64badge/scripts/ne64badge-nonbanked.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/ne64badge/ostest/ne64badge-nonbanked.ld
+ * boards/ne64badge/ostest/ne64badge-nonbanked.ld
*
* Copyright (C) 2011, 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/nr5m100-nexys4/README.txt b/boards/nr5m100-nexys4/README.txt
index 7f9b5e4456..b88fa15618 100644
--- a/boards/nr5m100-nexys4/README.txt
+++ b/boards/nr5m100-nexys4/README.txt
@@ -148,7 +148,7 @@ Debugger
./configure --enable-jlink --enable-maintainer-mode --enable-ftdi --prefix=~/riscv CFLAGS=-g
The configuration scripts for openocd and nr5m100-nexys4 have been provided in the
- nuttx/configs/nr5m100-nexys4/scripts directory. They are configured to use a J-LINK JTAG
+ nuttx/boards/nr5m100-nexys4/scripts directory. They are configured to use a J-LINK JTAG
probe and to search for the IQ-Analog (the company I work for) IDCODE and part number for
the FPGA board (7a10 for Artix xc7a100 part on the Digilent Nexys4 board). With FPGA
source directly from the nr5m100 github site (to be provided), this ID will match the
diff --git a/boards/nr5m100-nexys4/scripts/ld.script b/boards/nr5m100-nexys4/scripts/ld.script
index 4aeb414c10..2c82bb79a5 100644
--- a/boards/nr5m100-nexys4/scripts/ld.script
+++ b/boards/nr5m100-nexys4/scripts/ld.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/nr5m100-nexys4/scripts/ld.script
+ * boards/nr5m100-nexys4/scripts/ld.script
*
* Copyright (C) 2011-2013 Gregory Nutt. All rights reserved.
* Copyright (C) 2016 Ken Pettit.
diff --git a/boards/nr5m100-nexys4/scripts/nr5m1xx.cfg b/boards/nr5m100-nexys4/scripts/nr5m1xx.cfg
index 9cff1d5aa8..0fe77f55d0 100644
--- a/boards/nr5m100-nexys4/scripts/nr5m1xx.cfg
+++ b/boards/nr5m100-nexys4/scripts/nr5m1xx.cfg
@@ -1,5 +1,5 @@
############################################################################
-# configs/nr5m100-nexys4/scripts/nr5m1xx.cfg
+# boards/nr5m100-nexys4/scripts/nr5m1xx.cfg
#
# Copyright (C) 2016 Ken Pettit. All rights reserved.
# Author: Ken Pettit
diff --git a/boards/nr5m100-nexys4/scripts/openocd.cfg b/boards/nr5m100-nexys4/scripts/openocd.cfg
index b3818fb9ea..57af6e507a 100644
--- a/boards/nr5m100-nexys4/scripts/openocd.cfg
+++ b/boards/nr5m100-nexys4/scripts/openocd.cfg
@@ -1,5 +1,5 @@
############################################################################
-# configs/nr5m100-nexys4/scripts/openocd.cfg
+# boards/nr5m100-nexys4/scripts/openocd.cfg
#
# Copyright (C) 2016 Ken Pettit. All rights reserved.
# Author: Ken Pettit
diff --git a/boards/nrf52-generic/scripts/flash_config.ld b/boards/nrf52-generic/scripts/flash_config.ld
index 1dbf47b89d..a79056254c 100644
--- a/boards/nrf52-generic/scripts/flash_config.ld
+++ b/boards/nrf52-generic/scripts/flash_config.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/nrf52-generic/scripts/flash_config.ld
+ * boards/nrf52-generic/scripts/flash_config.ld
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Author: Janne Rosberg
diff --git a/boards/ntosd-dm320/README.txt b/boards/ntosd-dm320/README.txt
index aaafc3a065..359171919b 100644
--- a/boards/ntosd-dm320/README.txt
+++ b/boards/ntosd-dm320/README.txt
@@ -174,8 +174,8 @@ NuttX buildroot Toolchain
4. cd /buildroot
- 5. cp configs/arm-defconfig .config OR
- cp configs/arm926t_defconfig-4.2.4 .config
+ 5. cp boards/arm-defconfig .config OR
+ cp boards/arm926t_defconfig-4.2.4 .config
6. make oldconfig
@@ -208,7 +208,7 @@ ARM/DM320-specific Configuration Options
CONFIG_ARCH_CHIP_DM320
- CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
+ CONFIG_ARCH_BOARD - Identifies the boards/ subdirectory and
hence, the board that supports the particular chip or SoC.
CONFIG_ARCH_BOARD=ntosd-dm320
@@ -324,7 +324,7 @@ Configuration Options
^^^^^^^^^^^^^^^^^^^^^
In additional to the common configuration options listed in the
-file configs/README.txt, there are other configuration options
+file boards/README.txt, there are other configuration options
specific to the DM320:
CONFIG_ARCH - identifies the arch subdirectory and, hence, the
@@ -334,7 +334,7 @@ specific to the DM320:
in.
CONFIG_ARCH_CHIP - Identifies the arch/*/chip subdirectory
CONFIG_ARCH_CHIP_name - For use in C code
- CONFIG_ARCH_BOARD - identifies the configs subdirectory and, hence,
+ CONFIG_ARCH_BOARD - identifies the boards/ subdirectory and, hence,
the board that supports the particular chip or SoC.
CONFIG_ENDIAN_BIG - define if big endian (default is little endian)
CONFIG_ARCH_BOARD_name - for use in C code
diff --git a/boards/ntosd-dm320/doc/README.txt b/boards/ntosd-dm320/doc/README.txt
index e3c24ea4a6..3f8f4fa517 100644
--- a/boards/ntosd-dm320/doc/README.txt
+++ b/boards/ntosd-dm320/doc/README.txt
@@ -43,7 +43,7 @@ General instructions.
5. Build the toolchain:
cd /buildroot
- cp configs/c5471-defconfig .config
+ cp boards/c5471-defconfig .config
make oldconfig
make
diff --git a/boards/ntosd-dm320/scripts/sdram.ld b/boards/ntosd-dm320/scripts/sdram.ld
index b7b8380bf9..1c6bf5249d 100644
--- a/boards/ntosd-dm320/scripts/sdram.ld
+++ b/boards/ntosd-dm320/scripts/sdram.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/ntosd-dm320/scripts/sdram.ld
+ * boards/ntosd-dm320/scripts/sdram.ld
*
* Copyright (C) 2007, 2008, 2011, 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/nucleo-144/README.txt b/boards/nucleo-144/README.txt
index ab492526fc..ee29095997 100644
--- a/boards/nucleo-144/README.txt
+++ b/boards/nucleo-144/README.txt
@@ -55,7 +55,7 @@ allow us to quickly change configurations by just cloning a configuration
and changing the CPU choice and board initialization. Unfortunately for
the developer, the CPU specific information must be extracted from the
common information in the documentation. The exception are the STM32L496ZG
-boards, which are supported by configs/nucleo-l496zg
+boards, which are supported by boards/nucleo-l496zg
Please read the User Manual UM1727: Getting started with STM32 Nucleo board
software development tools and take note of the Powering options for the
diff --git a/boards/nucleo-144/scripts/f722-flash.ld b/boards/nucleo-144/scripts/f722-flash.ld
index a297331523..1a1cb33856 100644
--- a/boards/nucleo-144/scripts/f722-flash.ld
+++ b/boards/nucleo-144/scripts/f722-flash.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/nucleo-144/scripts/f722-flash.ld
+ * boards/nucleo-144/scripts/f722-flash.ld
*
* Copyright (C) 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
@@ -33,7 +33,7 @@
* POSSIBILITY OF SUCH DAMAGE.
*
* Change Log:
- * bf20171114 Created from configs/nucleo-144/scripts/f746-flash.ld
+ * bf20171114 Created from boards/nucleo-144/scripts/f746-flash.ld
****************************************************************************/
/* The STM32F722ZE has 512 KiB of main FLASH memory. This FLASH memory
diff --git a/boards/nucleo-144/scripts/f746-flash.ld b/boards/nucleo-144/scripts/f746-flash.ld
index 025a2a1090..f7a25850f4 100644
--- a/boards/nucleo-144/scripts/f746-flash.ld
+++ b/boards/nucleo-144/scripts/f746-flash.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/nucleo-144/scripts/f746-flash.ld
+ * boards/nucleo-144/scripts/f746-flash.ld
*
* Copyright (C) 2016 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/nucleo-144/scripts/f767-flash.ld b/boards/nucleo-144/scripts/f767-flash.ld
index 1f72ca2634..12f8e525e5 100644
--- a/boards/nucleo-144/scripts/f767-flash.ld
+++ b/boards/nucleo-144/scripts/f767-flash.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/nucleo-144/scripts/f767-flash.ld
+ * boards/nucleo-144/scripts/f767-flash.ld
*
* Copyright (C) 2016 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/nucleo-144/scripts/kernel-space.ld b/boards/nucleo-144/scripts/kernel-space.ld
index 166d4f0bbc..7ecc15c01d 100644
--- a/boards/nucleo-144/scripts/kernel-space.ld
+++ b/boards/nucleo-144/scripts/kernel-space.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/nucleo-144/scripts/kernel-space.ld
+ * boards/nucleo-144/scripts/kernel-space.ld
*
* Copyright (C) 2016 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/nucleo-144/scripts/memory.ld b/boards/nucleo-144/scripts/memory.ld
index 2f5eecad41..a7909e7ebb 100644
--- a/boards/nucleo-144/scripts/memory.ld
+++ b/boards/nucleo-144/scripts/memory.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/nucleo-144/scripts/memory.ld
+ * boards/nucleo-144/scripts/memory.ld
*
* Copyright (C) 2016 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
@@ -67,7 +67,7 @@
* For MPU support, the kernel-mode NuttX section is assumed to be 128Kb of
* FLASH and 4Kb of SRAM. That is an excessive amount for the kernel which
* should fit into 64KB and, of course, can be optimized as needed (See
- * also configs/stm32f746g-disco/scripts/kernel-space.ld). Allowing the
+ * also boards/stm32f746g-disco/scripts/kernel-space.ld). Allowing the
* additional does permit addition debug instrumentation to be added to the
* kernel space without overflowing the partition.
*
diff --git a/boards/nucleo-144/scripts/user-space.ld b/boards/nucleo-144/scripts/user-space.ld
index 871d8e055f..cf3f5ba721 100644
--- a/boards/nucleo-144/scripts/user-space.ld
+++ b/boards/nucleo-144/scripts/user-space.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/nucleo-144/scripts/user-space.ld
+ * boards/nucleo-144/scripts/user-space.ld
*
* Copyright (C) 2016 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/nucleo-f072rb/scripts/flash.ld b/boards/nucleo-f072rb/scripts/flash.ld
index 6c880d9d27..87477a08ed 100644
--- a/boards/nucleo-f072rb/scripts/flash.ld
+++ b/boards/nucleo-f072rb/scripts/flash.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/nucleo-f072rb/scripts/flash.ld
+ * boards/nucleo-f072rb/scripts/flash.ld
*
* Copyright (C) 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/nucleo-f091rc/scripts/flash.ld b/boards/nucleo-f091rc/scripts/flash.ld
index 35bd797b0f..edbe7e728b 100644
--- a/boards/nucleo-f091rc/scripts/flash.ld
+++ b/boards/nucleo-f091rc/scripts/flash.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/nucleo-f091rc/scripts/flash.ld
+ * boards/nucleo-f091rc/scripts/flash.ld
*
* Copyright (C) 2017 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/nucleo-f103rb/scripts/ld.script b/boards/nucleo-f103rb/scripts/ld.script
index 77a50d820c..18aa73a572 100644
--- a/boards/nucleo-f103rb/scripts/ld.script
+++ b/boards/nucleo-f103rb/scripts/ld.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/nucleo-f103rb/scripts/ld.script
+ * boards/nucleo-f103rb/scripts/ld.script
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Authors: Gregory Nutt
diff --git a/boards/nucleo-f207zg/scripts/ld.script b/boards/nucleo-f207zg/scripts/ld.script
index 089988311a..afa653d52a 100644
--- a/boards/nucleo-f207zg/scripts/ld.script
+++ b/boards/nucleo-f207zg/scripts/ld.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/nucleo-f207zg/scripts/ld.script
+ * boards/nucleo-f207zg/scripts/ld.script
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Authors: Gregory Nutt
diff --git a/boards/nucleo-f302r8/scripts/ld.script b/boards/nucleo-f302r8/scripts/ld.script
index f1084c121b..2aa7f0548a 100644
--- a/boards/nucleo-f302r8/scripts/ld.script
+++ b/boards/nucleo-f302r8/scripts/ld.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/nucleo-f302r8/scripts/ld.script
+ * boards/nucleo-f302r8/scripts/ld.script
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Authors: Gregory Nutt
diff --git a/boards/nucleo-f303re/scripts/ld.script b/boards/nucleo-f303re/scripts/ld.script
index ba3152136a..7de0cc6ecf 100644
--- a/boards/nucleo-f303re/scripts/ld.script
+++ b/boards/nucleo-f303re/scripts/ld.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/nucleo-f303re/scripts/ld.script
+ * boards/nucleo-f303re/scripts/ld.script
*
* Copyright (C) 2013 Gregory Nutt. All rights reserved.
* Copyright (C) 2015 Omni Hoverboards Inc. All rights reserved.
diff --git a/boards/nucleo-f303ze/scripts/ld.script b/boards/nucleo-f303ze/scripts/ld.script
index 35e41a6860..19ade1b1e7 100644
--- a/boards/nucleo-f303ze/scripts/ld.script
+++ b/boards/nucleo-f303ze/scripts/ld.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/nucleo-f303ze/scripts/ld.script
+ * boards/nucleo-f303ze/scripts/ld.script
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Authors: Gregory Nutt
diff --git a/boards/nucleo-f334r8/scripts/ld.script b/boards/nucleo-f334r8/scripts/ld.script
index 00656794e3..4206ced2d5 100644
--- a/boards/nucleo-f334r8/scripts/ld.script
+++ b/boards/nucleo-f334r8/scripts/ld.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/nucleo-f334r8/scripts/ld.script
+ * boards/nucleo-f334r8/scripts/ld.script
*
* Copyright (C) 2017 Gregory Nutt. All rights reserved.
* Authors: Gregory Nutt
diff --git a/boards/nucleo-f410rb/scripts/f410rb.ld b/boards/nucleo-f410rb/scripts/f410rb.ld
index f24c7cf9cf..d941312b44 100644
--- a/boards/nucleo-f410rb/scripts/f410rb.ld
+++ b/boards/nucleo-f410rb/scripts/f410rb.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/nucleo-f410rb/scripts/f410rb.ld
+ * boards/nucleo-f410rb/scripts/f410rb.ld
*
* Copyright (C) 2017 Gwenhael Goavec-Merou. All rights reserved.
* Author: Gwenhael Goavec-Merou
diff --git a/boards/nucleo-f446re/README.txt b/boards/nucleo-f446re/README.txt
index 97994f3133..508db2f112 100644
--- a/boards/nucleo-f446re/README.txt
+++ b/boards/nucleo-f446re/README.txt
@@ -249,7 +249,7 @@ NuttX EABI "buildroot" Toolchain
4. cd /buildroot
- 5. cp configs/cortexm3-eabi-defconfig-4.6.3 .config
+ 5. cp boards/cortexm3-eabi-defconfig-4.6.3 .config
6. make oldconfig
@@ -258,7 +258,7 @@ NuttX EABI "buildroot" Toolchain
8. Make sure that the PATH variable includes the path to the newly built
binaries.
- See the file configs/README.txt in the buildroot source tree. That has more
+ See the file boards/README.txt in the buildroot source tree. That has more
details PLUS some special instructions that you will need to follow if you are
building a Cortex-M3 toolchain for Cygwin under Windows.
@@ -290,7 +290,7 @@ NXFLAT Toolchain
4. cd /buildroot
- 5. cp configs/cortexm3-defconfig-nxflat .config
+ 5. cp boards/cortexm3-defconfig-nxflat .config
6. make oldconfig
diff --git a/boards/nucleo-f446re/scripts/f446re.ld b/boards/nucleo-f446re/scripts/f446re.ld
index 16d18a722f..ee7755cfe7 100644
--- a/boards/nucleo-f446re/scripts/f446re.ld
+++ b/boards/nucleo-f446re/scripts/f446re.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/nucleo-f4x1re/scripts/f411re.ld
+ * boards/nucleo-f4x1re/scripts/f411re.ld
*
* Copyright (C) 2014 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/nucleo-f4x1re/README.txt b/boards/nucleo-f4x1re/README.txt
index f7283c909d..6993616d42 100644
--- a/boards/nucleo-f4x1re/README.txt
+++ b/boards/nucleo-f4x1re/README.txt
@@ -274,7 +274,7 @@ NuttX EABI "buildroot" Toolchain
4. cd /buildroot
- 5. cp configs/cortexm3-eabi-defconfig-4.6.3 .config
+ 5. cp boards/cortexm3-eabi-defconfig-4.6.3 .config
6. make oldconfig
@@ -283,7 +283,7 @@ NuttX EABI "buildroot" Toolchain
8. Make sure that the PATH variable includes the path to the newly built
binaries.
- See the file configs/README.txt in the buildroot source tree. That has more
+ See the file boards/README.txt in the buildroot source tree. That has more
details PLUS some special instructions that you will need to follow if you are
building a Cortex-M3 toolchain for Cygwin under Windows.
@@ -315,7 +315,7 @@ NXFLAT Toolchain
4. cd /buildroot
- 5. cp configs/cortexm3-defconfig-nxflat .config
+ 5. cp boards/cortexm3-defconfig-nxflat .config
6. make oldconfig
diff --git a/boards/nucleo-f4x1re/scripts/f401re.ld b/boards/nucleo-f4x1re/scripts/f401re.ld
index ace460afd6..c65c586f48 100644
--- a/boards/nucleo-f4x1re/scripts/f401re.ld
+++ b/boards/nucleo-f4x1re/scripts/f401re.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/nucleo-f4x1re/scripts/f401re.ld
+ * boards/nucleo-f4x1re/scripts/f401re.ld
*
* Copyright (C) 2014 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/nucleo-f4x1re/scripts/f411re.ld b/boards/nucleo-f4x1re/scripts/f411re.ld
index 16d18a722f..ee7755cfe7 100644
--- a/boards/nucleo-f4x1re/scripts/f411re.ld
+++ b/boards/nucleo-f4x1re/scripts/f411re.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/nucleo-f4x1re/scripts/f411re.ld
+ * boards/nucleo-f4x1re/scripts/f411re.ld
*
* Copyright (C) 2014 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/nucleo-g071rb/scripts/ld.script b/boards/nucleo-g071rb/scripts/ld.script
index 9572c27ed4..91f9538e24 100644
--- a/boards/nucleo-g071rb/scripts/ld.script
+++ b/boards/nucleo-g071rb/scripts/ld.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/nucleo-g071rb/scripts/ld.script
+ * boards/nucleo-g071rb/scripts/ld.script
*
* Copyright (C) 2019 Gregory Nutt. All rights reserved.
* Authors: Gregory Nutt
diff --git a/boards/nucleo-h743zi/scripts/flash.ld b/boards/nucleo-h743zi/scripts/flash.ld
index c470de4680..fd2b785179 100644
--- a/boards/nucleo-h743zi/scripts/flash.ld
+++ b/boards/nucleo-h743zi/scripts/flash.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/nucleo-h743zi/scripts/flash.ld
+ * boards/nucleo-h743zi/scripts/flash.ld
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/nucleo-h743zi/scripts/kernel.space.ld b/boards/nucleo-h743zi/scripts/kernel.space.ld
index f0fc0ef8a0..e6e7ad9118 100644
--- a/boards/nucleo-h743zi/scripts/kernel.space.ld
+++ b/boards/nucleo-h743zi/scripts/kernel.space.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/nucleo-h743zi/scripts/kernel-space.ld
+ * boards/nucleo-h743zi/scripts/kernel-space.ld
*
* Copyright (C) 2019 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/nucleo-h743zi/scripts/memory.ld b/boards/nucleo-h743zi/scripts/memory.ld
index cff0fcb64c..52a8a4d129 100644
--- a/boards/nucleo-h743zi/scripts/memory.ld
+++ b/boards/nucleo-h743zi/scripts/memory.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/nucleo-h743zi/scripts/memory.ld
+ * boards/nucleo-h743zi/scripts/memory.ld
*
* Copyright (C) 2019 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/nucleo-h743zi/scripts/user-space.ld b/boards/nucleo-h743zi/scripts/user-space.ld
index e65c3e3806..e165aa6b45 100644
--- a/boards/nucleo-h743zi/scripts/user-space.ld
+++ b/boards/nucleo-h743zi/scripts/user-space.ld
@@ -1,5 +1,5 @@
/****************************************************************************
-* configs/nucleo-h743zi/scripts/user-space.ld
+* boards/nucleo-h743zi/scripts/user-space.ld
*
* Copyright (C) 2019 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/nucleo-l073rz/scripts/ld.script b/boards/nucleo-l073rz/scripts/ld.script
index be88db993f..18ee4cd80c 100644
--- a/boards/nucleo-l073rz/scripts/ld.script
+++ b/boards/nucleo-l073rz/scripts/ld.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/nucleo-l073rz/scripts/ld.script
+ * boards/nucleo-l073rz/scripts/ld.script
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Authors: Gregory Nutt
diff --git a/boards/nucleo-l152re/scripts/ld.script b/boards/nucleo-l152re/scripts/ld.script
index 392ebf1ce1..0731bed439 100644
--- a/boards/nucleo-l152re/scripts/ld.script
+++ b/boards/nucleo-l152re/scripts/ld.script
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/nucleo-l152re/scripts/ld.script
+ * boards/nucleo-l152re/scripts/ld.script
*
* Copyright (C) 2018 Gregory Nutt. All rights reserved.
* Authors: Gregory Nutt
diff --git a/boards/nucleo-l432kc/README.txt b/boards/nucleo-l432kc/README.txt
index a0f45940a8..94a202e241 100644
--- a/boards/nucleo-l432kc/README.txt
+++ b/boards/nucleo-l432kc/README.txt
@@ -242,7 +242,7 @@ NuttX EABI "buildroot" Toolchain
4. cd /buildroot
- 5. cp configs/cortexm3-eabi-defconfig-4.6.3 .config
+ 5. cp boards/cortexm3-eabi-defconfig-4.6.3 .config
6. make oldconfig
@@ -251,7 +251,7 @@ NuttX EABI "buildroot" Toolchain
8. Make sure that the PATH variable includes the path to the newly built
binaries.
- See the file configs/README.txt in the buildroot source tree. That has more
+ See the file boards/README.txt in the buildroot source tree. That has more
details PLUS some special instructions that you will need to follow if you are
building a Cortex-M3 toolchain for Cygwin under Windows.
@@ -283,7 +283,7 @@ NXFLAT Toolchain
4. cd /buildroot
- 5. cp configs/cortexm3-defconfig-nxflat .config
+ 5. cp boards/cortexm3-defconfig-nxflat .config
6. make oldconfig
diff --git a/boards/nucleo-l432kc/scripts/l432kc.ld b/boards/nucleo-l432kc/scripts/l432kc.ld
index 9fb057cc10..f93412d8ba 100644
--- a/boards/nucleo-l432kc/scripts/l432kc.ld
+++ b/boards/nucleo-l432kc/scripts/l432kc.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/nucleo-l432kc/scripts/l432kc.ld
+ * boards/nucleo-l432kc/scripts/l432kc.ld
*
* Copyright (C) 2014 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/nucleo-l452re/scripts/l452re-flash.ld b/boards/nucleo-l452re/scripts/l452re-flash.ld
index 362a34d600..7c1c74fdd3 100644
--- a/boards/nucleo-l452re/scripts/l452re-flash.ld
+++ b/boards/nucleo-l452re/scripts/l452re-flash.ld
@@ -1,5 +1,5 @@
/****************************************************************************
- * configs/nucleo-l452re/scripts/l452re-flash.ld
+ * boards/nucleo-l452re/scripts/l452re-flash.ld
*
* Copyright (C) 2014 Gregory Nutt. All rights reserved.
* Author: Gregory Nutt
diff --git a/boards/nucleo-l476rg/README.txt b/boards/nucleo-l476rg/README.txt
index 2057ba9578..a4310dc11d 100644
--- a/boards/nucleo-l476rg/README.txt
+++ b/boards/nucleo-l476rg/README.txt
@@ -255,7 +255,7 @@ NuttX EABI "buildroot" Toolchain
4. cd /buildroot
- 5. cp configs/cortexm3-eabi-defconfig-4.6.3 .config
+ 5. cp boards/cortexm3-eabi-defconfig-4.6.3 .config
6. make oldconfig
@@ -264,7 +264,7 @@ NuttX EABI "buildroot" Toolchain
8. Make sure that the PATH variable includes the path to the newly built
binaries.
- See the file configs/README.txt in the buildroot source tree. That has more
+ See the file boards/README.txt in the buildroot source tree. That has more
details PLUS some special instructions that you will need to follow if you are
building a Cortex-M3 toolchain for Cygwin under Windows.
@@ -296,7 +296,7 @@ NXFLAT Toolchain
4. cd