mirror of
https://github.com/apache/nuttx.git
synced 2026-05-31 14:27:37 +08:00
Fix various typos assocated with LM4F
git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@5763 42af7a65-404d-4744-a932-0658087f49c3
This commit is contained in:
@@ -153,7 +153,7 @@
|
|||||||
|
|
||||||
#define ETHBUF ((struct uip_eth_hdr *)priv->ld_dev.d_buf)
|
#define ETHBUF ((struct uip_eth_hdr *)priv->ld_dev.d_buf)
|
||||||
|
|
||||||
#define LM32S_MAX_MDCCLK 2500000
|
#define LM_MAX_MDCCLK 2500000
|
||||||
|
|
||||||
/****************************************************************************
|
/****************************************************************************
|
||||||
* Private Types
|
* Private Types
|
||||||
@@ -1047,10 +1047,10 @@ static int lm_ifup(struct uip_driver_s *dev)
|
|||||||
* div = (SYSCLK_FREQUENCY / 2 / MDCCLK_FREQUENCY) - 1
|
* div = (SYSCLK_FREQUENCY / 2 / MDCCLK_FREQUENCY) - 1
|
||||||
*
|
*
|
||||||
* Where the maximum value for MDCCLK_FREQUENCY is 2,500,000. We will
|
* Where the maximum value for MDCCLK_FREQUENCY is 2,500,000. We will
|
||||||
* add 1 to assure the max LM32S_MAX_MDCCLK is not exceeded.
|
* add 1 to assure the max LM_MAX_MDCCLK is not exceeded.
|
||||||
*/
|
*/
|
||||||
|
|
||||||
div = SYSCLK_FREQUENCY / 2 / LM32S_MAX_MDCCLK;
|
div = SYSCLK_FREQUENCY / 2 / LM_MAX_MDCCLK;
|
||||||
lm_ethout(priv, LM_MAC_MDV_OFFSET, div);
|
lm_ethout(priv, LM_MAC_MDV_OFFSET, div);
|
||||||
nllvdbg("MDV: %08x\n", div);
|
nllvdbg("MDV: %08x\n", div);
|
||||||
|
|
||||||
|
|||||||
@@ -195,6 +195,9 @@ Using OpenOCD and GDB with an FT2232 JTAG emulator
|
|||||||
but that should have been added to your PATH variable when you sourced
|
but that should have been added to your PATH variable when you sourced
|
||||||
the setenv.sh script.
|
the setenv.sh script.
|
||||||
|
|
||||||
|
Note that OpenOCD needs to be run with administrator privileges in
|
||||||
|
some environments (sudo).
|
||||||
|
|
||||||
Connecting GDB
|
Connecting GDB
|
||||||
|
|
||||||
Once the OpenOCD daemon has been started, you can connect to it via
|
Once the OpenOCD daemon has been started, you can connect to it via
|
||||||
@@ -432,7 +435,7 @@ NXFLAT Toolchain
|
|||||||
|
|
||||||
LEDs
|
LEDs
|
||||||
^^^^
|
^^^^
|
||||||
The LM32F120 has a single RGB LED. If CONFIG_ARCH_LEDS is defined, then
|
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:
|
support for the LaunchPad LEDs will be included in the build. See:
|
||||||
|
|
||||||
- configs/lm4f120-launchpad/include/board.h - Defines LED constants, types and
|
- configs/lm4f120-launchpad/include/board.h - Defines LED constants, types and
|
||||||
|
|||||||
@@ -53,7 +53,7 @@
|
|||||||
* 32.768kHz connected to XOSC0/1 (pins 34/36)
|
* 32.768kHz connected to XOSC0/1 (pins 34/36)
|
||||||
*/
|
*/
|
||||||
|
|
||||||
#define SYSCON_RCC_XTAL SYSCON_RCC_XTAL16000KHZ /* On-board crystall is 16 MHz */
|
#define SYSCON_RCC_XTAL SYSCON_RCC_XTAL16000KHZ /* On-board crystal is 16 MHz */
|
||||||
#define XTAL_FREQUENCY 16000000
|
#define XTAL_FREQUENCY 16000000
|
||||||
|
|
||||||
/* Oscillator source is the main oscillator */
|
/* Oscillator source is the main oscillator */
|
||||||
@@ -89,8 +89,9 @@
|
|||||||
#define LM_RCC2_VALUE (SYSCON_RCC2_OSCSRC | SYSCON_RCC2_SYSDIV(LM_SYSDIV) | SYSCON_RCC2_DIV400)
|
#define LM_RCC2_VALUE (SYSCON_RCC2_OSCSRC | SYSCON_RCC2_SYSDIV(LM_SYSDIV) | SYSCON_RCC2_DIV400)
|
||||||
|
|
||||||
/* LED definitions ******************************************************************/
|
/* LED definitions ******************************************************************/
|
||||||
/* The LM32F120 has a single RGB LED. There is only one visible LED which will vary
|
/* The LM4F120 LaunchPad has a single RGB LED. There is only one visible LED which
|
||||||
* in color. But, from the standpoint of the firmware, this appears as three LEDs:
|
* will vary in color. But, from the standpoint of the firmware, this appears as
|
||||||
|
* three LEDs:
|
||||||
*
|
*
|
||||||
* BOARD_LED_R -- Connected to PF1
|
* BOARD_LED_R -- Connected to PF1
|
||||||
* BOARD_LED_G -- Connected to PF3
|
* BOARD_LED_G -- Connected to PF3
|
||||||
@@ -144,7 +145,7 @@
|
|||||||
#define LED_PANIC 4 /* ON OFF OFF (flashing 2Hz) */
|
#define LED_PANIC 4 /* ON OFF OFF (flashing 2Hz) */
|
||||||
|
|
||||||
/* LED definitions ******************************************************************/
|
/* LED definitions ******************************************************************/
|
||||||
/* The LM32F120 has a two buttons:
|
/* The LM4F120 LaunchPad has a two buttons:
|
||||||
*
|
*
|
||||||
* BOARD_SW1 -- Connected to PF4
|
* BOARD_SW1 -- Connected to PF4
|
||||||
* BOARD_SW2 -- Connected to PF0
|
* BOARD_SW2 -- Connected to PF0
|
||||||
|
|||||||
@@ -54,8 +54,9 @@
|
|||||||
/****************************************************************************
|
/****************************************************************************
|
||||||
* Definitions
|
* Definitions
|
||||||
****************************************************************************/
|
****************************************************************************/
|
||||||
/* The LM32F120 has a single RGB LED. There is only one visible LED which will vary
|
/* The LM4F120 LaunchPad has a single RGB LED. There is only one visible LED
|
||||||
* in color. But, from the standpoint of the firmware, this appears as three LEDs:
|
* which will vary in color. But, from the standpoint of the firmware, this
|
||||||
|
* appears as three LEDs:
|
||||||
*
|
*
|
||||||
* BOARD_LED_R -- Connected to PF1
|
* BOARD_LED_R -- Connected to PF1
|
||||||
* BOARD_LED_G -- Connected to PF3
|
* BOARD_LED_G -- Connected to PF3
|
||||||
|
|||||||
@@ -67,8 +67,9 @@
|
|||||||
#endif
|
#endif
|
||||||
|
|
||||||
/* LM4F LaunchPad *******************************************************************/
|
/* LM4F LaunchPad *******************************************************************/
|
||||||
/* The LM32F120 has a single RGB LED. There is only one visible LED which will vary
|
/* The LM4F120 LaunchPad has a single RGB LED. There is only one visible LED which
|
||||||
* in color. But, from the standpoint of the firmware, this appears as three LEDs:
|
* will vary in color. But, from the standpoint of the firmware, this appears as
|
||||||
|
* three LEDs:
|
||||||
*
|
*
|
||||||
* BOARD_LED_R -- Connected to PF1
|
* BOARD_LED_R -- Connected to PF1
|
||||||
* BOARD_LED_G -- Connected to PF3
|
* BOARD_LED_G -- Connected to PF3
|
||||||
@@ -113,7 +114,7 @@
|
|||||||
#define GPIO_LED_G (GPIO_FUNC_OUTPUT | GPIO_VALUE_ONE | GPIO_PORTF | GPIO_PIN_3)
|
#define GPIO_LED_G (GPIO_FUNC_OUTPUT | GPIO_VALUE_ONE | GPIO_PORTF | GPIO_PIN_3)
|
||||||
#define GPIO_LED_B (GPIO_FUNC_OUTPUT | GPIO_VALUE_ONE | GPIO_PORTF | GPIO_PIN_2)
|
#define GPIO_LED_B (GPIO_FUNC_OUTPUT | GPIO_VALUE_ONE | GPIO_PORTF | GPIO_PIN_2)
|
||||||
|
|
||||||
/* The LM32F120 has a two buttons:
|
/* The LM4F120 LaunchPad has a two buttons:
|
||||||
*
|
*
|
||||||
* BOARD_SW1 -- Connected to PF4
|
* BOARD_SW1 -- Connected to PF4
|
||||||
* BOARD_SW2 -- Connected to PF0
|
* BOARD_SW2 -- Connected to PF0
|
||||||
|
|||||||
Reference in New Issue
Block a user