Perhaps:
Bit 10PCE: Parity control enableThis bit selects the hardware parity
control (generation and detection). When the parity control is enabled,
the computedparity is inserted at the MSB position (9th bit if M=1; 8th
bit if M=0) and the parity is checked on the received data. This bit is
set and cleared by software. Once it is set, PCE is active after the
current byte (in reception and in transmission).0: Parity control
disabled1: Parity control enabled/*This bitfield can only be writte*//*n
when the USART is disabled (U*//*E=0).*/
Bit 9PS: Parity selectionThis bit selects the odd or even parity when
theparity generation/detection is enabled (PCE bit set). It is set and
cleared by software.The parity is selected after the current byte.0:
Even parity1: Odd parityT/*his bitfield can only be writte*//*n when the
USART is disabled (U*//*E=0)*/
On 9/3/2020 4:44 PM, Nathan Hartman wrote:
I ran into a strange issue with serial init for STM32. If the UART is
already enabled/configured, our configuration does not seem to apply.
I discovered this because I used a bootloader to flash and run NuttX
on the arm/stm32/b-g474e-dpow1 board. The bootloader configs the UART
for 115200 baud 8E1.
This is how nsh looks if I type 'help' command:
nsh> [hp
hp usag hp [v] [md>]
d s mv s unam
[ p mb m sp umun
mp as mkd pn su uns
basnam dnam hp mkd pd s usp
bak dd hdump mh m m d
a h k mun md u
nsh> [
This is because Even Parity (and possibly other stale config) is still
in effect from the bootloader.
When I flash and run NuttX without the bootloader, the nsh prompt
works correctly with 115200 baud 8N1.
Has anyone seen this before?
