Mirrors_Framework/nuttx
1
0
Fork 0
mirror of https://github.com/apache/nuttx.git synced 2026-06-05 15:58:59 +08:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Fix some typos. Also minor update to stm32f7/nucleo-144/README.txt and stm32l4/nucleo-l496zg/README.txt board documentation.

Browse Source
This commit is contained in:
Juha Niskanen
2019-09-05 08:10:42 -06:00
committed by Gregory Nutt
parent 0b64e79736
commit 822bb06967
37 changed files with 67 additions and 140 deletions
Download Patch File Download Diff File Expand all files Collapse all files
boards/arm/kinetis/twr-k60n512/README.txt
+1 -1
View File
@@ -491,4 +491,4 @@ Where <subdir> is one of the following:
CONFIG_SCHED_WORKQUEUE=y : Enable the NuttX workqueue
CONFIG_NSH_ARCHINIT=y : Provide NSH initializeation logic
CONFIG_NSH_ARCHINIT=y : Provide NSH initialization logic
boards/arm/kinetis/twr-k64f120m/README.txt
+1 -1
View File
@@ -597,7 +597,7 @@ Where <subdir> is one of the following:
CONFIG_SCHED_WORKQUEUE=y : Enable the NuttX workqueue
CONFIG_NSH_ARCHINIT=y : Provide NSH initializeation logic
CONFIG_NSH_ARCHINIT=y : Provide NSH initialization logic
netnsh:
------
boards/arm/lpc17xx_40xx/lpcxpresso-lpc1768/README.txt
+1 -1
View File
@@ -347,7 +347,7 @@ LEDs
- The LED is not illuminated until the LPCXpresso completes initialization.
If the LED is stuck in the OFF state, this means that the LPCXpresso did not
complete initializeation.
complete initialization.
- Each time the OS enters an interrupt (or a signal) it will turn the LED OFF and
restores its previous stated upon return from the interrupt (or signal).
boards/arm/lpc17xx_40xx/zkit-arm-1769/README.txt
+1 -1
View File
@@ -156,7 +156,7 @@ LEDs
- The LED is not illuminated until the ZKit-ARM completes initialization.
If the LED is stuck in the OFF state, this means that the ZKit-ARM did not
complete initializeation.
complete initialization.
- Each time the OS enters an interrupt (or a signal) it will turn the LED OFF and
restores its previous stated upon return from the interrupt (or signal).
boards/arm/stm32/mikroe-stm32f4/src/stm32_pm.c
+3 -19
View File
@@ -48,22 +48,6 @@
#ifdef CONFIG_PM
/****************************************************************************
* Pre-processor Definitions
****************************************************************************/
/****************************************************************************
* Private Data
****************************************************************************/
/****************************************************************************
* Public Data
****************************************************************************/
/****************************************************************************
* Private Functions
****************************************************************************/
/****************************************************************************
* Public Functions
****************************************************************************/
@@ -73,8 +57,8 @@
*
* Description:
* This function is called by MCU-specific logic at power-on reset in
* order to provide one-time initialization the power management subystem.
* This function must be called *very* early in the initializeation sequence
* order to provide one-time initialization the power management subsystem.
* This function must be called *very* early in the initialization sequence
* *before* any other device drivers are initialized (since they may
* attempt to register with the power management subsystem).
*
@@ -82,7 +66,7 @@
* None.
*
* Returned Value:
* None.
* None.
*
****************************************************************************/
boards/arm/stm32/olimex-stm32-p407/scripts/memory.ld
+2 -2
View File
@@ -72,12 +72,12 @@
*
* Both of these alignment limitations could be reduced by using multiple
* regions to map the FLASH/SDRAM range or perhaps with some clever use of
* subregions or with mutliple MPU regions per memory region.
* subregions or with multiple MPU regions per memory region.
*
* NOTE: The MPU is used in a mode where mappings are not required for
* kernel addresses and, hence, there are not alignment issues for those
* case. Only the user address spaces suffer from alignment requirements.
* However, in order to exploit this fact, we would staill need to change
* However, in order to exploit this fact, we would still need to change
* the ordering of memory regions in SRAM.
*
* A detailed memory map for the 112KB SRAM region is as follows:
boards/arm/stm32/omnibusf4/src/stm32_pm.c
+3 -19
View File
@@ -49,22 +49,6 @@
#ifdef CONFIG_PM
/****************************************************************************
* Pre-processor Definitions
****************************************************************************/
/****************************************************************************
* Private Data
****************************************************************************/
/****************************************************************************
* Public Data
****************************************************************************/
/****************************************************************************
* Private Functions
****************************************************************************/
/****************************************************************************
* Public Functions
****************************************************************************/
@@ -74,8 +58,8 @@
*
* Description:
* This function is called by MCU-specific logic at power-on reset in
* order to provide one-time initialization the power management subystem.
* This function must be called *very* early in the initializeation sequence
* order to provide one-time initialization the power management subsystem.
* This function must be called *very* early in the initialization sequence
* *before* any other device drivers are initialized (since they may
* attempt to register with the power management subsystem).
*
@@ -83,7 +67,7 @@
* None.
*
* Returned Value:
* None.
* None.
*
****************************************************************************/
boards/arm/stm32/stm3210e-eval/src/stm32_pm.c
+3 -19
View File
@@ -48,22 +48,6 @@
#ifdef CONFIG_PM
/****************************************************************************
* Pre-processor Definitions
****************************************************************************/
/****************************************************************************
* Private Data
****************************************************************************/
/****************************************************************************
* Public Data
****************************************************************************/
/****************************************************************************
* Private Functions
****************************************************************************/
/****************************************************************************
* Public Functions
****************************************************************************/
@@ -73,8 +57,8 @@
*
* Description:
* This function is called by MCU-specific logic at power-on reset in
* order to provide one-time initialization the power management subystem.
* This function must be called *very* early in the initializeation sequence
* order to provide one-time initialization the power management subsystem.
* This function must be called *very* early in the initialization sequence
* *before* any other device drivers are initialized (since they may
* attempt to register with the power management subsystem).
*
@@ -82,7 +66,7 @@
* None.
*
* Returned Value:
* None.
* None.
*
****************************************************************************/
boards/arm/stm32/stm32f4discovery/src/stm32_pm.c
+2 -18
View File
@@ -49,22 +49,6 @@
#ifdef CONFIG_PM
/****************************************************************************
* Pre-processor Definitions
****************************************************************************/
/****************************************************************************
* Private Data
****************************************************************************/
/****************************************************************************
* Public Data
****************************************************************************/
/****************************************************************************
* Private Functions
****************************************************************************/
/****************************************************************************
* Public Functions
****************************************************************************/
@@ -74,8 +58,8 @@
*
* Description:
* This function is called by MCU-specific logic at power-on reset in
* order to provide one-time initialization the power management subystem.
* This function must be called *very* early in the initializeation sequence
* order to provide one-time initialization the power management subsystem.
* This function must be called *very* early in the initialization sequence
* *before* any other device drivers are initialized (since they may
* attempt to register with the power management subsystem).
*
boards/arm/stm32/stm32ldiscovery/README.txt
+3 -3
View File
@@ -41,10 +41,10 @@ Status
* The following subsystem have header files, drivers and have been
exercised: PWR, RCC, GPIO, SYSCFG, LCD, USART.
* The following subsystenms have header files and ported drivers, but are
* The following subsystems have header files and ported drivers, but are
untested: DMA
* The following subystems have counterparts with other STM32 parts, but
* The following subsystems have counterparts with other STM32 parts, but
have not been ported or verified: ADC, DAC, TIM2-15, TIM9-11, RTC,
IWDG, WWDG, I2C, SPI, DBG. These may be close to functional depending
upon how close the IP is on the STM32L15X.
@@ -57,7 +57,7 @@ Status
* The STM32L15X does support USB, however, USB is not available on the
STM32L-Discovery board.
* These subystems are available on other STM32L15x/16x parts, but not on
* These subsystems are available on other STM32L15x/16x parts, but not on
the part used in the STM32L-Discovery board: CRC, AES, FSMC, SDIO
GPIO Pin Usage
boards/arm/stm32f7/nucleo-144/Kconfig
+2 -2
View File
@@ -38,13 +38,13 @@ choice
Advantage: Use the ST-Link as a console. No Extra wiring
needed.
Disdvantage: Not the best choice for initial bring up.
Disadvantage: Not the best choice for initial bring up.
ARDUINO Connector:
Advantage: You have a shield so it is easy.
Disdvantage: You loose the use of the
Disadvantage: You loose the use of the
other functions on PC6, PC7
STM32F7
boards/arm/stm32f7/nucleo-144/README.txt
+10 -5
View File
@@ -45,17 +45,22 @@ LQFP144 package. Variants include
STM32F767ZIT6 NUCLEO-F767ZI
STM32L496ZGT6 NUCLEO-L496ZG
STM32L496ZGT6P NUCLEO-L496ZG-P
STM32L4A6ZGT6 NUCLEO-L4A6ZG
STM32L4R5ZIT6 NUCLEO-L4R5ZI
STM32L4R5ZIT6P NUCLEO-L4R5ZI-P
------------- ------------------
This directory is intended to support all Nucleo-144 variants since the
boards are identical, differing only in the installed part. This common
This directory is intended to support all STM32F7 Nucleo-144 variants since
the boards are identical, differing only in the installed part. This common
board design provides uniformity in the documentation from ST and should
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 boards/nucleo-l496zg
common information in the documentation.
The NUCLEO-L496ZG and NUCLEO-L496ZG-P boards are not supported by this
directory, but by boards/arm/stm32l4/nucleo-l496zg. Any other STM32L4
Nucleo-144 boards are also not supported by this directory.
Please read the User Manual UM1727: Getting started with STM32 Nucleo board
software development tools and take note of the Powering options for the
boards/arm/stm32l4/nucleo-l496zg/README.txt
+1 -1
View File
@@ -36,7 +36,7 @@ LQFP144 package. Variants with a STM32L4 MCU include:
------------- ------------------
This directory supports only the STM32L4 variants of Nucleo-144. For others,
see boards/arm/stm32l4/nucleo-l496zg configuration.
see boards/arm/stm32f7/nucleo-144 configuration.
Please read the User Manual UM2179: Getting started with STM32 Nucleo board
software development tools and take note of the Powering options for the