Hey Federico,
Yes, checking for NVMCTRL_RWW_EEPROM_SIZE seems to be a good
approach.
BTW. Be careful with using the term "revision". Where you mentioned A,
B and L, that is what Atmel calls "device variant" to denote functional
differences. There is also a die revision, which can be read from
Hi Nitin,
Am Mi., 30. Jan. 2019 um 09:25 Uhr schrieb Nitin Shivaraman <
nitin.shivara...@tum-create.edu.sg>:
> Hello,
>
>
>
> I’m working on implementing a custom clock synchronization protocol on
> Riot OS.
>
> I saw that the earlier branch having well-known protocols (FTSP, GTSP,
> etc)
Hi Christian,
thanks for the heads up! Looks interesting. We could indeed organize such
that some RIOTers (whom exactly is t.b.d) would attend to give a talk and
answer Q
Best,
Emmanuel
On Wed, Jan 30, 2019 at 9:35 AM chrysn wrote:
> Hi,
>
> there will be a conference event embedded systems
Hi,
there will be a conference event embedded systems and IoT development in
Rust in Berlin 2019-04-26 to -29 called oxidize[1]. I'm about to enter a
presentation on using RIOT as an operating system with Rust applications
built atop of it at its CFP.
Given the event, according to the CFP
Hello,
I'm working on implementing a custom clock synchronization protocol on Riot OS.
I saw that the earlier branch having well-known protocols (FTSP, GTSP, etc)
implementation was merged to RIOT OS main branch and removed. Is there a
separate branch in which these protocols are included now?
