Has anyone taken a look at the ARTIK 030 module from Samsung? It's a
Cortex-M4 based (SiLabs EFR32MG1 SoC) module with 256 kB flash and 32
kB SRAM, a cryto processor, and 802.15.4 radio.
In the US they're available from Digikey and Mouser for $7.30 in
single unit quantities; I'm not sure who distr
Hi!
I think I’m quite against `dist/tools/bootloader`. Most of the code there can
be built by itself, which is not the case of the bootloader… I was maybe
thinking about leave it there in the root or move it to sys/ as a module. The
module option seems to me a bit adequate since is an optional
Dear developers,
I have been working on the kw41zrf driver in PR #7107 [1]. However, I
can't get 6lowpan fragmented packets to transmit properly.
It seems the GNRC stack is trying to pass the next fragment to the
netdev driver before the first fragment has finished transmitting over
the air, result
Hi,
gut feeling says `dist/tools/bootloader` (maybe something more unique than
just bootloader?), since it isn't really part of the system and not really
an example, but a quite specific application. Then again, for the same
reasons I could argue to put it in the root folder, that IMHO should be
k
Hi everyone,
PR #7457 will introduce a bootloader application.
The question came up where to put it within the source tree?
Currently the PR puts it in the root folder (./bootloader).
Do we want that? Is there a better place?
Options:
examples/bootloader
dist/tools/bootloader
...
Kaspar
__