On Sat, Nov 12, 2022 at 9:28 AM Gregory Nutt wrote:
> There was also IAR/uVision IDE support in the repository for STM32. All
> of the IAR/uVision helper tools are still present (I think), but the IAR
> board support was removed
> https://bitbucket.org/patacongo/obsoleted/src/60ec01456d8b09f5b81
I have pretty much ironed out all the issues with the SAMA5 touchscreen (TSD)
and ADC drivers, making sure they actually work correctly for the D2 variant
and look like they should work for the D3 and D4 variants, and fixed bugs along
the way. I will do a PR in due course but still have one high
On 11/12/2022 9:05 AM, Brennan Ashton wrote:
I can probably help revive my past effort to run some native builds in CI
to at least prevent it from getting fully broken. One of the blockers last
time, was just how slow it was and the limited number of Windows workers.
Did we ever really have a n
I can probably help revive my past effort to run some native builds in CI
to at least prevent it from getting fully broken. One of the blockers last
time, was just how slow it was and the limited number of Windows workers.
Let's see what we can do.
--Brennan
On Sat, Nov 12, 2022, 5:43 AM fft wr
Hi Petro,
Maybe instead of creating an override you can create a capability like
exists for SDIO on NuttX.
It could be used to control features/characteristics unique for some
PWM controllers.
Buf of course it will need some override/sync flag because some
applications will prefer to wait up to
Hello David,
Thanks for your reply. I fully understand that. In my case I have the half
bridge schema of four pins and PWM frequency is very low. In case I need to
do immediate stop I need to stop pulse generation and short pin to the
ground. It is more because the overall half bridge solution is
