I think we should do it like in other BLE implementations for NRF52
(SoftDevice, Zephyr) and use a combination of RTC and TIMER peripherals.
There are quite a few places in the BLE protocol where we need to count
the time in various ranges from seconds to mili-seconds.
It is not possible t
Hi,
I'm working on a BLE Link Layer for NuttX, which sits between HCI layer and
low-level radio-layer. I'm starting with BLE scanning and I need to set a timer
to periodically execute the radio reception to listen for advertisements. I'm
trying to see which interface should this layer use: onesh
Could we put the compilers in a private repository or web server? Maybe
Apache has solved this problem before.
-adam
On Thu, Jul 16, 2020 at 12:21 PM Pavel Ionut <
pavel.ionut.catalin...@gmail.com> wrote:
> Also, regarding the CI stuff.
>
> Seems like Microchip has the official compiler(s) downl
Also, regarding the CI stuff.
Seems like Microchip has the official compiler(s) download links under a
(login) wall.
What would be the approach in this case (so that the compilers could be
downloaded by the CI scripts)?
There are various binaries scattered across the internet, but I guess the
offi
Hello,
I created a PR for the build issue.
Will have a go at the CI stuff.
Regards.
On Thu, Jul 16, 2020 at 5:48 PM Xiang Xiao
wrote:
>
>
> > -Original Message-
> > From: Pavel Ionut
> > Sent: Wednesday, July 15, 2020 6:48 PM
> > To: dev@nuttx.apache.org
> > Subject: [nuttx][avr] Issu
I like the idea of doing a ReStructured Text build in CI. I'd help convert
READMEs and other docs to RST. And I'd be willing to contribute the RST
docs I have already as a starting place if people are interested. They are
already Apache 2.0 Licensed.
-adam
On Thu, Jul 16, 2020 at 6:45 AM Matias N
> -Original Message-
> From: Pavel Ionut
> Sent: Wednesday, July 15, 2020 6:48 PM
> To: dev@nuttx.apache.org
> Subject: [nuttx][avr] Issues while building avr (atmega) board example.
>
> Hello,
>
> Basically I'm trying to build the moteino-mega board example and I found some
> issues
Documenting boards using the README's in each subdirectory (by converting them
to Markdown and having them rendered somewhere) is indeed to most direct
approach. Although I would say it is an intermediate solution.
I think having an explicit repo holding documentation written in something more
