Drop baud to 57600
git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@3092 42af7a65-404d-4744-a932-0658087f49c3
This commit is contained in:
parent
6cd75d7e18
commit
458a61aac4
@ -97,15 +97,31 @@ Olimex LPC1766-STK development board
|
|||||||
--------------
|
--------------
|
||||||
|
|
||||||
The LPC1766-STK board has two serial connectors. One, RS232_0, connects to
|
The LPC1766-STK board has two serial connectors. One, RS232_0, connects to
|
||||||
the LPC1766 USART0. This is the DB-9 connector next to the power connector.
|
the LPC1766 UART0. This is the DB-9 connector next to the power connector.
|
||||||
The other RS232_1, connect to the LPC1766 USART1. This is he DB-9 connector
|
The other RS232_1, connect to the LPC1766 UART1. This is he DB-9 connector
|
||||||
next to the Ethernet connector.
|
next to the Ethernet connector.
|
||||||
|
|
||||||
Simple USART1 is the more flexible USART and since the needs for a serial
|
Simple UART1 is the more flexible UART and since the needs for a serial
|
||||||
console are minimal, the more minimal USART0/RS232_0 is used for the NuttX
|
console are minimal, the more minimal UART0/RS232_0 is used for the NuttX
|
||||||
system console. Of course, this can be changed by editting the NuttX
|
system console. Of course, this can be changed by editting the NuttX
|
||||||
configuration file as discussed below.
|
configuration file as discussed below.
|
||||||
|
|
||||||
|
The serial console is configured as follows (57600 8N1):
|
||||||
|
|
||||||
|
BAUD: 57600
|
||||||
|
Number of Bits: 8
|
||||||
|
Parity: None
|
||||||
|
Stop bits: 1
|
||||||
|
|
||||||
|
You will need to connect a monitor program (Hyperterminal, Tera Term,
|
||||||
|
minicom, whatever) to UART0/RS232_0 and configure the serial port as
|
||||||
|
shown above.
|
||||||
|
|
||||||
|
NOTE: The ostest example works fine at 115200, but the other configurations
|
||||||
|
have problems at that rate (probably because they use the interrupt driven
|
||||||
|
serial driver). Other LPC17xx boards with the same clocking will run at
|
||||||
|
115200.
|
||||||
|
|
||||||
Development Environment
|
Development Environment
|
||||||
^^^^^^^^^^^^^^^^^^^^^^^
|
^^^^^^^^^^^^^^^^^^^^^^^
|
||||||
|
|
||||||
@ -448,11 +464,17 @@ Using OpenOCD and GDB with an FT2232 JTAG emulator
|
|||||||
(gdb) symbol-file nuttx
|
(gdb) symbol-file nuttx
|
||||||
(gdb) load nuttx
|
(gdb) load nuttx
|
||||||
|
|
||||||
OpenOCD will support several special 'monitor' commands:
|
OpenOCD will support several special 'monitor' commands. These
|
||||||
|
GDB commands will send comments to the OpenOCD monitor. Here
|
||||||
|
are a couple that you will need to use:
|
||||||
|
|
||||||
(gdb) monitor reset
|
(gdb) monitor reset
|
||||||
(gdb) monitor halt
|
(gdb) monitor halt
|
||||||
|
|
||||||
|
The MCU must be halted prior to loading code. Reset will restart
|
||||||
|
the processor after loading code. The 'monitor' command can be
|
||||||
|
abbreviated as just 'mon'.
|
||||||
|
|
||||||
Olimex LPC1766-STK Configuration Options
|
Olimex LPC1766-STK Configuration Options
|
||||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||||
|
|
||||||
|
@ -161,10 +161,10 @@ CONFIG_UART1_RXBUFSIZE=256
|
|||||||
CONFIG_UART2_RXBUFSIZE=256
|
CONFIG_UART2_RXBUFSIZE=256
|
||||||
CONFIG_UART3_RXBUFSIZE=256
|
CONFIG_UART3_RXBUFSIZE=256
|
||||||
|
|
||||||
CONFIG_UART0_BAUD=115200
|
CONFIG_UART0_BAUD=57600
|
||||||
CONFIG_UART2_BAUD=115200
|
CONFIG_UART2_BAUD=57600
|
||||||
CONFIG_UART3_BAUD=115200
|
CONFIG_UART3_BAUD=57600
|
||||||
CONFIG_UART1_BAUD=115200
|
CONFIG_UART1_BAUD=57600
|
||||||
|
|
||||||
CONFIG_UART0_BITS=8
|
CONFIG_UART0_BITS=8
|
||||||
CONFIG_UART1_BITS=8
|
CONFIG_UART1_BITS=8
|
||||||
|
@ -161,10 +161,10 @@ CONFIG_UART1_RXBUFSIZE=256
|
|||||||
CONFIG_UART2_RXBUFSIZE=256
|
CONFIG_UART2_RXBUFSIZE=256
|
||||||
CONFIG_UART3_RXBUFSIZE=256
|
CONFIG_UART3_RXBUFSIZE=256
|
||||||
|
|
||||||
CONFIG_UART0_BAUD=115200
|
CONFIG_UART0_BAUD=57600
|
||||||
CONFIG_UART2_BAUD=115200
|
CONFIG_UART2_BAUD=57600
|
||||||
CONFIG_UART3_BAUD=115200
|
CONFIG_UART3_BAUD=57600
|
||||||
CONFIG_UART1_BAUD=115200
|
CONFIG_UART1_BAUD=57600
|
||||||
|
|
||||||
CONFIG_UART0_BITS=8
|
CONFIG_UART0_BITS=8
|
||||||
CONFIG_UART1_BITS=8
|
CONFIG_UART1_BITS=8
|
||||||
|
@ -161,10 +161,10 @@ CONFIG_UART1_RXBUFSIZE=256
|
|||||||
CONFIG_UART2_RXBUFSIZE=256
|
CONFIG_UART2_RXBUFSIZE=256
|
||||||
CONFIG_UART3_RXBUFSIZE=256
|
CONFIG_UART3_RXBUFSIZE=256
|
||||||
|
|
||||||
CONFIG_UART0_BAUD=115200
|
CONFIG_UART0_BAUD=57600
|
||||||
CONFIG_UART2_BAUD=115200
|
CONFIG_UART2_BAUD=57600
|
||||||
CONFIG_UART3_BAUD=115200
|
CONFIG_UART3_BAUD=57600
|
||||||
CONFIG_UART1_BAUD=115200
|
CONFIG_UART1_BAUD=57600
|
||||||
|
|
||||||
CONFIG_UART0_BITS=8
|
CONFIG_UART0_BITS=8
|
||||||
CONFIG_UART1_BITS=8
|
CONFIG_UART1_BITS=8
|
||||||
|
@ -161,10 +161,10 @@ CONFIG_UART1_RXBUFSIZE=256
|
|||||||
CONFIG_UART2_RXBUFSIZE=256
|
CONFIG_UART2_RXBUFSIZE=256
|
||||||
CONFIG_UART3_RXBUFSIZE=256
|
CONFIG_UART3_RXBUFSIZE=256
|
||||||
|
|
||||||
CONFIG_UART0_BAUD=115200
|
CONFIG_UART0_BAUD=57600
|
||||||
CONFIG_UART2_BAUD=115200
|
CONFIG_UART2_BAUD=57600
|
||||||
CONFIG_UART3_BAUD=115200
|
CONFIG_UART3_BAUD=57600
|
||||||
CONFIG_UART1_BAUD=115200
|
CONFIG_UART1_BAUD=57600
|
||||||
|
|
||||||
CONFIG_UART0_BITS=8
|
CONFIG_UART0_BITS=8
|
||||||
CONFIG_UART1_BITS=8
|
CONFIG_UART1_BITS=8
|
||||||
|
Loading…
Reference in New Issue
Block a user