configs/stm32f103-minimum: Fix a few typos.
This commit is contained in:
parent
3a95464153
commit
c8b567db61
@ -53,7 +53,7 @@ STM32F103C8T6 Minimum System Development Boards:
|
||||
Good things about the blue board:
|
||||
|
||||
- Four soldered anchor point on the USB connector. What you can't tell
|
||||
from this picture is that there is a notch in the pcb board and the USB
|
||||
from this picture is that there is a notch in the PCB board and the USB
|
||||
connector sits down inside it some. This provides some lateral stability
|
||||
that takes some of the stress off the solder points.
|
||||
- It has nice clear readable silkscreen printing.
|
||||
@ -123,7 +123,7 @@ LEDs
|
||||
enabled.
|
||||
|
||||
If enabled the LED is simply turned on when the board boots
|
||||
succesfully, and is blinking on panic / assertion failed.
|
||||
successfully, and is blinking on panic / assertion failed.
|
||||
|
||||
UARTs
|
||||
=====
|
||||
@ -282,7 +282,7 @@ Nintendo Wii Nunchuck:
|
||||
Quadrature Encoder:
|
||||
===================
|
||||
|
||||
The nsh configuration has been used to test the Quadrture Encoder
|
||||
The nsh configuration has been used to test the Quadrature Encoder
|
||||
(QEncoder, QE) with the following modifications to the configuration
|
||||
file:
|
||||
|
||||
@ -443,7 +443,7 @@ Nokia 5110 LCD Display support:
|
||||
Device Drivers --->
|
||||
LCD Driver Support --->
|
||||
[*] Graphic LCD Driver Support --->
|
||||
[*] Nokia 5110 LCD Display (Philips PCD8544)
|
||||
[*] Nokia 5110 LCD Display (Phillips PCD8544)
|
||||
(1) Number of PCD8544 Devices
|
||||
(84) PCD8544 X Resolution
|
||||
(48) PCD8544 Y Resolution
|
||||
@ -561,7 +561,7 @@ STM32F103 Minimum - specific Configuration Options
|
||||
CONFIG_ARCH_BOARD - Identifies the configs subdirectory and
|
||||
hence, the board that supports the particular chip or SoC.
|
||||
|
||||
CONFIG_ARCH_BOARD=stm32f103-minium
|
||||
CONFIG_ARCH_BOARD=stm32f103-minimum
|
||||
|
||||
CONFIG_ARCH_BOARD_name - For use in C code
|
||||
|
||||
@ -593,7 +593,7 @@ STM32F103 Minimum - specific Configuration Options
|
||||
|
||||
CONFIG_ARCH_CALIBRATION - Enables some build in instrumentation that
|
||||
cause a 100 second delay during boot-up. This 100 second delay
|
||||
serves no purpose other than it allows you to calibratre
|
||||
serves no purpose other than it allows you to calibrate
|
||||
CONFIG_ARCH_LOOPSPERMSEC. You simply use a stop watch to measure
|
||||
the 100 second delay then adjust CONFIG_ARCH_LOOPSPERMSEC until
|
||||
the delay actually is 100 seconds.
|
||||
@ -770,7 +770,7 @@ Configurations
|
||||
4. Enabling USB monitor SYSLOG output. If tracing is enabled, the USB
|
||||
device will save encoded trace output in in-memory buffer; if the
|
||||
USB monitor is enabled, that trace buffer will be periodically
|
||||
emptied and dumped to the system loggin device (UART2 in this
|
||||
emptied and dumped to the system logging device (UART2 in this
|
||||
configuraion):
|
||||
|
||||
CONFIG_USBDEV_TRACE=y : Enable USB trace feature
|
||||
|
@ -34,8 +34,8 @@
|
||||
*
|
||||
************************************************************************************/
|
||||
|
||||
#ifndef __CONFIGS_STM32F103_MINIMUM_BOARD_H
|
||||
#define __CONFIGS_STM32F103_MINIMUM_BOARD_H
|
||||
#ifndef __CONFIGS_STM32F103_MINIMUM_INCLUDE_BOARD_H
|
||||
#define __CONFIGS_STM32F103_MINIMUM_INCLUDE_BOARD_H
|
||||
|
||||
/************************************************************************************
|
||||
* Included Files
|
||||
@ -56,7 +56,7 @@
|
||||
|
||||
#define STM32_BOARD_XTAL 8000000ul
|
||||
|
||||
/* PLL source is HSE/1, PLL multipler is 9: PLL frequency is 8MHz (XTAL) x 9 = 72MHz */
|
||||
/* PLL source is HSE/1, PLL multiplier is 9: PLL frequency is 8MHz (XTAL) x 9 = 72MHz */
|
||||
|
||||
#define STM32_CFGR_PLLSRC RCC_CFGR_PLLSRC
|
||||
#define STM32_CFGR_PLLXTPRE 0
|
||||
@ -194,4 +194,4 @@
|
||||
#define RGBLED_BPWMTIMER 4
|
||||
#define RGBLED_BPWMCHANNEL 4
|
||||
|
||||
#endif /* __CONFIGS_STM32F103_MINIMUM_BOARD_H */
|
||||
#endif /* __CONFIGS_STM32F103_MINIMUM_INCLUDE_BOARD_H */
|
||||
|
@ -1,7 +1,7 @@
|
||||
/****************************************************************************
|
||||
* configs/stm32f103-minimum/scripts/ld.script
|
||||
*
|
||||
* Copyright (C) 2016 Gregory Nutt. All rights reserved.
|
||||
* Copyright (C) 2016, 2018 Gregory Nutt. All rights reserved.
|
||||
* Author: Gregory Nutt <gnutt@nuttx.org>
|
||||
* Laurent Latil <laurent@latil.nom.fr>
|
||||
*
|
||||
@ -39,6 +39,11 @@
|
||||
* FLASH memory is aliased to address 0x0000:0000 where the code expects to
|
||||
* begin execution by jumping to the entry point in the 0x0800:0000 address
|
||||
* range.
|
||||
*
|
||||
* NOTE: While the STM32F103C8T6 states that the part has 64Kb of FLASH,
|
||||
* all parts that I have seen do, in fact, have 128Kb of FLASH. That
|
||||
* additional 64Kb of FLASH can be utilized by simply change the LENGTH
|
||||
* of the flash region from 64K to 128K.
|
||||
*/
|
||||
|
||||
MEMORY
|
||||
|
@ -66,7 +66,7 @@
|
||||
* arg - The boardctl() argument is passed to the board_app_initialize()
|
||||
* implementation without modification. The argument has no
|
||||
* meaning to NuttX; the meaning of the argument is a contract
|
||||
* between the board-specific initalization logic and the
|
||||
* between the board-specific initialization logic and the
|
||||
* matching application logic. The value cold be such things as a
|
||||
* mode enumeration value, a set of DIP switch switch settings, a
|
||||
* pointer to configuration data read from a file or serial FLASH,
|
||||
|
@ -135,7 +135,7 @@ int stm32_at24_automount(int minor)
|
||||
return ret;
|
||||
}
|
||||
#endif
|
||||
/* Now we are initializeed */
|
||||
/* Now we are initialized */
|
||||
|
||||
initialized = true;
|
||||
}
|
||||
|
@ -80,10 +80,10 @@ static const uint32_t g_buttons[NUM_BUTTONS] =
|
||||
* Name: board_button_initialize
|
||||
*
|
||||
* Description:
|
||||
* board_button_initialize() must be called to initialize button resources. After
|
||||
* that, board_buttons() may be called to collect the current state of all
|
||||
* buttons or board_button_irq() may be called to register button interrupt
|
||||
* handlers.
|
||||
* board_button_initialize() must be called to initialize button resources.
|
||||
* After that, board_buttons() may be called to collect the current state
|
||||
* of all buttons or board_button_irq() may be called to register button
|
||||
* interrupt handlers.
|
||||
*
|
||||
****************************************************************************/
|
||||
|
||||
|
@ -112,7 +112,7 @@
|
||||
#define MAX_IRQBUTTON BUTTON_USER2
|
||||
#define NUM_IRQBUTTONS (BUTTON_USER1 - BUTTON_USER2 + 1)
|
||||
|
||||
/* ZERO CROSS pin definiton */
|
||||
/* ZERO CROSS pin definition */
|
||||
|
||||
#define GPIO_ZEROCROSS (GPIO_INPUT|GPIO_CNF_INFLOAT|GPIO_PORTA|GPIO_PIN0)
|
||||
|
||||
@ -214,7 +214,7 @@
|
||||
* CONFIG_LIB_BOARDCTL=y:
|
||||
* If CONFIG_NSH_ARCHINITIALIZE=y:
|
||||
* Called from the NSH library (or other application)
|
||||
* Otherse, assumed to be called from some other application.
|
||||
* Otherwise, assumed to be called from some other application.
|
||||
*
|
||||
* Otherwise CONFIG_BOARD_INITIALIZE=y:
|
||||
* Called from board_initialize().
|
||||
|
Loading…
Reference in New Issue
Block a user