0dce63b242
19689: cpu/sam0_eth: disable PHY when MAC is sleeping r=maribu a=benpicco 19700: pkg/openthread: Fix Kconfig and broken example r=maribu a=MrKevinWeiss ### Contribution description There were some improvements that could be make to the kconfig modeling of the `pkg/openthread` after looking a bit closer. The bigger problem is the hash check on nightlies require reproducible builds, however, even with make, the builds are not reproducible. So, for now, I just rename the `app.config.test` to `skip.app.config.test` to prevent murdock from trying to do a hash check but still letting it be useable. ### Testing procedure Green murdock, all modules match `examples/openthread` - Rename `skip.app.config.test` to `app.config.test` - Run the following ``` ./dist/tools/compile_test/compile_like_murdock.py -j 8 -a examples/openthread/ -b all -m ``` <details> ``` examples/openthread/ cc2538dk PASS examples/openthread/ frdm-kw41z PASS examples/openthread/ iotlab-a8-m3 PASS examples/openthread/ iotlab-m3 PASS examples/openthread/ nrf52840-mdk PASS examples/openthread/ nrf52840dk PASS examples/openthread/ omote PASS examples/openthread/ openlabs-kw41z-mini PASS examples/openthread/ openlabs-kw41z-mini-256kib PASS examples/openthread/ openmote-cc2538 PASS examples/openthread/ phynode-kw41z PASS examples/openthread/ reel PASS examples/openthread/ remote-reva PASS examples/openthread/ remote-revb PASS examples/openthread/ samr21-xpro PASS examples/openthread/ usb-kw41z PASS ``` </details> ### Issues/PRs references Fixes an aspect of broken master 19701: sys/usb/Kconfig: Fix default PID r=maribu a=MrKevinWeiss ### Contribution description Seems like I just didn't have the correct `USB_PID` defined in the `usb-codes.inc.mk`. It should be 0x7D01 not 0x7001. It only shows up in nightlies since the hash would mismatch. ### Testing procedure Simulated nightly testing with: ``` ./dist/tools/compile_test/compile_like_murdock.py -j 8 -a tests/pkg/tinyusb_cdc_acm_stdio/ tests/pkg/tinyusb_cdc_msc/ tests/pkg/tinyusb_cdc_msc/ tests/sys/fido2_ctap/ tests/sys/usbus_board_reset/ tests/sys/usbus_msc/ -b arduino-zero samd21-xpro nucleo-f767zi -v ``` <details> ``` tests/pkg/tinyusb_cdc_acm_stdio/ arduino-zero PASS ctests/pkg/tinyusb_cdc_acm_stdio/ nucleo-f767zi PASS tests/pkg/tinyusb_cdc_acm_stdio/ samd21-xpro PASS tests/pkg/tinyusb_cdc_msc/ arduino-zero PASS tests/pkg/tinyusb_cdc_msc/ nucleo-f767zi PASS tests/pkg/tinyusb_cdc_msc/ samd21-xpro PASS tests/pkg/tinyusb_cdc_msc/ arduino-zero PASS tests/pkg/tinyusb_cdc_msc/ nucleo-f767zi PASS tests/pkg/tinyusb_cdc_msc/ samd21-xpro PASS tests/sys/fido2_ctap/ arduino-zero PASS tests/sys/fido2_ctap/ samd21-xpro PASS tests/sys/usbus_board_reset/ arduino-zero PASS tests/sys/usbus_board_reset/ nucleo-f767zi PASS tests/sys/usbus_board_reset/ samd21-xpro PASS tests/sys/usbus_msc/ arduino-zero PASS tests/sys/usbus_msc/ nucleo-f767zi PASS tests/sys/usbus_msc/ samd21-xpro PASS ``` ### Issues/PRs references Broken master in nightlies. Co-authored-by: Benjamin Valentin <benjamin.valentin@ml-pa.com> Co-authored-by: MrKevinWeiss <weiss.kevin604@gmail.com>
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: