3469fce248
19335: ipv6/nib: 6LBR should not send RS on their downstream interface r=fabian18 a=fabian18 19581: cpu/samd5x: enable FDPLL1 at 200MHz r=benpicco a=dylad ### Contribution description This PR allows to use the second FDPLL (the first one is used to generated the 120MHz frequency used by the core and some peripherals). The second FDPLL is setup to run at 200MHz which is the maximum allowed by this MCU. In fact, I reused the existing function which setup FDPLL0 so it can be used in a generic way for both PLL (since they are the same IP). I change the way the computation offset (left shift by 5) is done because 200MHz << 5 wouldn't fit inside an `uint32_t` and I wanted to avoid using an `uint64_t` here Two additional commits are present for a small cleanup and a fix. This is currently unused in our codebase, so it shouldn't impact this platform too much as the `ONDEMAND` bit is set. the FDPLL will not be running out of the box. But `@gschorcht` might need it pretty soon. ### Testing procedure This PR can be tested on a `same54-xpro` and an oscilloscope using the following the patch: ``` From 76490845ec72387b24116bdd364a61365c186aa1 Mon Sep 17 00:00:00 2001 From: Dylan Laduranty <dylan.laduranty@mesotic.com> Date: Thu, 11 May 2023 17:42:16 +0200 Subject: [PATCH] removeme! for debug purpose Signed-off-by: Dylan Laduranty <dylan.laduranty@mesotic.com> --- cpu/samd5x/cpu.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/cpu/samd5x/cpu.c b/cpu/samd5x/cpu.c index f778991a5b..2866c8c9e5 100644 --- a/cpu/samd5x/cpu.c +++ b/cpu/samd5x/cpu.c `@@` -220,7 +220,7 `@@` static void fdpll_init(uint8_t idx, uint32_t f_cpu) } static void gclk_connect(uint8_t id, uint8_t src, uint32_t flags) { - GCLK->GENCTRL[id].reg = GCLK_GENCTRL_SRC(src) | GCLK_GENCTRL_GENEN | flags | GCLK_GENCTRL_IDC; + GCLK->GENCTRL[id].reg = GCLK_GENCTRL_SRC(src) | GCLK_GENCTRL_GENEN | flags | GCLK_GENCTRL_OE | GCLK_GENCTRL_IDC; while (GCLK->SYNCBUSY.reg & GCLK_SYNCBUSY_GENCTRL(id)) {} } `@@` -384,6 +384,12 `@@` void cpu_init(void) dma_init(); #endif + sam0_gclk_enable(SAM0_GCLK_200MHZ); + /* output both FDPLL (GCLK0 and GCLK4) to gpios */ + gpio_init_mux(GPIO_PIN(PB, 14), GPIO_MUX_M); + gpio_init_mux(GPIO_PIN(PB, 10), GPIO_MUX_M); + /* PB14 -> EXT2 PB10 -> QSPI SCK */ + /* initialize stdio prior to periph_init() to allow use of DEBUG() there */ early_init(); -- 2.35.3 ``` It will output both FDPLLs to PB14 and PB10. Their frequency can then be measured using an oscilloscope. ### Issues/PRs references None. 19612: pkg/ndn-riot: drop unmaintained pkg r=benpicco a=maribu ### Contribution description Upstream [1] has seen no activity since 2018, so it safe to assume this is dead. It is reasonable to assume that any users - if there ever were any - have moved on. Fixes https://github.com/RIOT-OS/RIOT/issues/15638 [1]: https://github.com/named-data-iot/ndn-riot 19643: examples/suit_update: some test fixes r=aabadie a=kaspar030 19655: net/ipv6: make use of clz in ipv6_addr_match_prefix() r=benpicco a=benpicco Co-authored-by: Fabian Hüßler <fabian.huessler@st.ovgu.de> Co-authored-by: Dylan Laduranty <dylan.laduranty@mesotic.com> Co-authored-by: Marian Buschsieweke <marian.buschsieweke@ovgu.de> Co-authored-by: Kaspar Schleiser <kaspar@schleiser.de> Co-authored-by: Benjamin Valentin <benjamin.valentin@ml-pa.com> |
||
---|---|---|
.cargo | ||
.github | ||
.vscode | ||
boards | ||
bootloaders | ||
core | ||
cpu | ||
dist | ||
doc | ||
drivers | ||
examples | ||
fuzzing | ||
kconfigs | ||
makefiles | ||
pkg | ||
sys | ||
tests | ||
.bandit | ||
.gitattributes | ||
.gitignore | ||
.mailmap | ||
.murdock | ||
.murdock.yml | ||
bors.toml | ||
CITATION.cff | ||
CODE_OF_CONDUCT.md | ||
CODEOWNERS | ||
CODING_CONVENTIONS_C++.md | ||
CODING_CONVENTIONS.md | ||
CONTRIBUTING.md | ||
doc.txt | ||
Kconfig | ||
LICENSE | ||
LOSTANDFOUND.md | ||
MAINTAINING.md | ||
Makefile | ||
Makefile.base | ||
Makefile.dep | ||
Makefile.features | ||
Makefile.include | ||
README.md | ||
release-notes.txt | ||
SECURITY.md | ||
SUBSYSTEMS.md | ||
uncrustify-riot.cfg | ||
Vagrantfile |
The friendly Operating System for IoT!
RIOT is a real-time multi-threading operating system that supports a range of devices that are typically found in the Internet of Things (IoT): 8-bit, 16-bit and 32-bit microcontrollers.
RIOT is based on the following design principles: energy-efficiency, real-time capabilities, small memory footprint, modularity, and uniform API access, independent of the underlying hardware (this API offers partial POSIX compliance).
RIOT is developed by an international open source community which is independent of specific vendors (e.g. similarly to the Linux community). RIOT is licensed with LGPLv2.1, a copyleft license which fosters indirect business models around the free open-source software platform provided by RIOT, e.g. it is possible to link closed-source code with the LGPL code.
FEATURES
RIOT provides features including, but not limited to:
- a preemptive, tickless scheduler with priorities
- flexible memory management
- high resolution, long-term timers
- MTD abstraction layer
- File System integration
- support 200+ boards based on AVR, MSP430, ESP8266, ESP32, RISC-V, ARM7 and ARM Cortex-M
- the native port allows to run RIOT as-is on Linux and BSD. Multiple instances of RIOT running on a single machine can also be interconnected via a simple virtual Ethernet bridge or via a simulated IEEE 802.15.4 network (ZEP)
- IPv6
- 6LoWPAN (RFC4944, RFC6282, and RFC6775)
- UDP
- RPL (storing mode, P2P mode)
- CoAP
- OTA updates via SUIT
- MQTT
- USB (device mode)
- Display / Touchscreen support
- CCN-Lite
- LoRaWAN
- UWB
- Bluetooth (BLE) via NimBLE
GETTING RIOT
The most convenient way to get RIOT is to clone it via Git
$ git clone https://github.com/RIOT-OS/RIOT
this will ensure that you get all the newest features and bug fixes with the caveat of an ever changing work environment.
If you prefer things more stable, you can download the source code of one of our quarter annual releases via Github as ZIP file or tarball. You can also checkout a release in a cloned Git repository using
$ git pull --tags
$ git checkout <YYYY.MM>
For more details on our release cycle, check our documentation.
GETTING STARTED
- You want to start the RIOT? Just follow our quickstart guide or try this tutorial. For specific toolchain installation, follow instructions in the getting started page.
- The RIOT API itself can be built from the code using doxygen. The latest version of the documentation is uploaded daily to doc.riot-os.org.
FORUM
Do you have a question, want to discuss a new feature, or just want to present your latest project using RIOT? Come over to our forum and post to your hearts content.
CONTRIBUTE
To contribute something to RIOT, please refer to our contributing document.
MAILING LISTS
- RIOT commits: commits@riot-os.org
- Github notifications: notifications@riot-os.org
LICENSE
- Most of the code developed by the RIOT community is licensed under the GNU Lesser General Public License (LGPL) version 2.1 as published by the Free Software Foundation.
- Some external sources, especially files developed by SICS are published under a separate license.
All code files contain licensing information.
For more information, see the RIOT website: