On Thu, Sep 3, 2020 at 7:38 PM Gregory Nutt wrote:
> 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)
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
Some IP blocks need to be disabled to modify some registers.
David
On Thu, Sep 3, 2020, 3:45 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 u
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
Hi Xiang,
can you confirm that arch_timer.c assumes that the timer resets itself? (as if
using STM32 autoreload?)
It doesn't call TIMER_STOP() on the underlying timer on timer_cancel(). In
fact, it simply sets a maximum timeout.
I understand this is because you also need the timer to be running t
Yes, it's better to auto select SCHED_TICKLESS_LIMIT_MAX_SLEEP under config
TIMER_ARCH/ALARM_ARCH.
> -Original Message-
> From: Matias N.
> Sent: Friday, September 4, 2020 12:09 AM
> To: dev@nuttx.apache.org
> Subject: Re: max sleep and tickless with no alarm
>
> Actually, I see this in
Actually, I see this in arch_timer.c/arch_alarm.c:
# ifndef CONFIG_SCHED_TICKLESS_LIMIT_MAX_SLEEP
#error CONFIG_SCHED_TICKLESS_LIMIT_MAX_SLEEP must be set to use
CONFIG_SCHED_TICKLESS
# endif
So I think this is somehow being enforced but it is in a really awkward place.
I will open an iss
Hi,
thanks, I will select TIMER_ARCH from Kconfig for this arch for now. I can
create an issue later.
I will also try to document these three drivers and link them from the
discussion about tickless support.
Best,
Matias
