mirror of
https://github.com/RIOT-OS/RIOT.git
synced 2024-12-29 04:50:03 +01:00
Mirror of https://github.com/RIOT-OS/RIOT
bff745236c
19817: compile_and_test_for_boards: Add no-compile flag r=benpicco a=MrKevinWeiss ### Contribution description Since we have a no-test flag that prevents executing tests, I think a no-compile flag is a nice compliment. Why? Well if I want to use this script for running multiple boards at the same time, RIOT is not so great handling parallel compile steps with conflicts on lockfiles happening, mostly due to packages. With this I can compile a list of boards sequentially, then flash and run tests in parallel, skipping the compile step. ### Testing procedure Run the following once to compile and clean: ``` ./dist/tools/compile_and_test_for_board/compile_and_test_for_board.py . native --applications tests/sys/shell --clean-after ``` Then try to run without the compile step and it should fail due to lack of the binary ``` ./dist/tools/compile_and_test_for_board/compile_and_test_for_board.py . native --applications tests/sys/shell --no-compile ``` ### Issues/PRs references 19826: ztimer/periodic: reinit remove from right clock and handle aquired ztimer r=benpicco a=kfessel ### Contribution description #19806 added some retinit handling for ztimer periodic removing the timer from the new clock This tries to detect if this is a reinit and remove the timer from the old clock this also removes the ztimer_acquire/_release handling by removing now calls in favour of set return value and now values that are allready in ztimer, that also has the potential to reduce the jitter of the periodic calls and bus-usage (for cpus that take their time to get "now") ### Testing procedure read run tests/sys/ztimer_periodic ### Issues/PRs references Fixes #19806 19841: boards/adafruit-itsybitsy-nrf52: Add configuration for DotStar LED r=benpicco a=jimporter 19842: cpu/stm32: fix ld script for SRAM4 r=benpicco a=gschorcht ### Contribution description This PR fixes the LD script for STM32. Since the CCM and SRAM4 length are defined as symbols with perifx `_`, the LD script didn't use them correctly. Instead of using `ccmram_length` and `sram4_length`, `_ccmram_length` and `_sram4_length` have to be used. Furthermore, the location counter for the SRAM has to be set to the beginning of SRAM4 to work. BTW, I don't understand why the `ccmram` region is defined. There is no section definition that would use it to place code or data with attribute `.ccmram.*` there. Without the fix in this PR, defined symbols in `tests/sys/malloc` for the `b-u585i-iot02a` board were: ```python 00000000 T _sheap2 <== wrong start position because of wrong location counter 28000000 T _eheap2 <== wrong end position because of `sram4_length` is 0. ``` Although the `tests/sys/malloc` crashes for `b-u585i-iot02a` at the end of the heap (known problem, see [here](https://github.com/RIOT-OS/RIOT/pull/17410#issuecomment-996556823)), it uses only the backup RAM before it crashes: ``` Allocated 512 Bytes at 0x200bf600, total 756072 Allocated 512 Bytes at 0x200bf818, total 756592 Allocated 512 Bytes at 0x200bfa30, total 757112 Allocated 512 Bytes at 0x200bfc48, total 757632 Allocated 512 Bytes at 0x40036408, total 758152 Allocated 512 Bytes at 0x40036610, total 758672 Allocated 512 Bytes at 0x40036818, total 759192 ``` With the fix in this PR, defined symbols in `tests/sys/malloc` for the `b-u585i-iot02a` board are: ```python 28000000 T _sheap2 <== correct start position 28004000 T _eheap2 <== correct end position ``` `tests/sys/malloc` also crashes for the `b-u585i-iot02a` at the end of the heap, but it uses also the SRAM4 before it crashes. ``` Allocated 512 Bytes at 0x200bf600, total 756072 Allocated 512 Bytes at 0x200bf818, total 756592 Allocated 512 Bytes at 0x200bfa30, total 757112 Allocated 512 Bytes at 0x200bfc48, total 757632 Allocated 512 Bytes at 0x40036408, total 758152 Allocated 512 Bytes at 0x40036610, total 758672 Allocated 512 Bytes at 0x40036818, total 759192 Allocated 512 Bytes at 0x28000008, total 759712 Allocated 512 Bytes at 0x28000210, total 760232 Allocated 512 Bytes at 0x28000418, total 760752 ... Allocated 512 Bytes at 0x280038e8, total 774272 Allocated 512 Bytes at 0x28003af0, total 774792 Allocated 512 Bytes at 0x28003cf8, total 775312 ``` ### Testing procedure 1. Flash `tests/sys/malloc` and use `MAX_MEM` limit to stop `malloc` before the crash: ``` CFLAGS='-DMAX_MEM=774800 -DCHUNK_SIZE=512 -DDEBUG_ASSERT_VERBOSE' \ BOARD=b-u585i-iot02a make -j8 -C tests/sys/malloc flash ``` Without the PR it crashes at the end of the backup RAM. With the PR it works. 2. Check `_sheap2` and `_eheap2` with ``` nm -s tests/sys/malloc/bin/b-u585i-iot02a/tests_malloc.elf | grep heap2 | sort ``` Without the PR it will be: ``` 00000000 T _sheap2 28000000 T _eheap2 ``` With the PR it should be: ``` 28000000 T _sheap2 28004000 T _eheap2 ``` ### Issues/PRs references Co-authored-by: MrKevinWeiss <weiss.kevin604@gmail.com> Co-authored-by: Karl Fessel <karl.fessel@ovgu.de> Co-authored-by: Jim Porter <jporterbugs@gmail.com> Co-authored-by: Gunar Schorcht <gunar@schorcht.net> |
||
|---|---|---|
| .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: