Start a RIOT #2

OlegHahm · 2013-02-28T17:39:40Z

No description provided.

OlegHahm · 2013-02-28T17:40:59Z

RIOT started!

Native board doxygen integration

add system calls to the shell (to implement a reboot command)

Pca10000 3

# This is the 1st commit message: Support for radio chip MRF24J40 - Work In Progress # This is the commit message #2: added new files to project

Siehe RIOT-OS#2

Fix FCS packet length problem

shell: remove feature guards from sc_rtc

…_allocator Fix printf %zu and 0x%p

pkg/openthread: fix bit alignment error of uart driver

# This is the 1st commit message: core: Made thread state an enum - Introduced enum type `thread_state_t` to replace preprocessor macros - Moved thread states to `sched.h` for two reasons: a) Because of the interdependencies of `sched.h` and `thread.h` keeping it in `thread.h` would result in ugly code. b) Theses thread states are defined from the schedulers point of view, so it actually makes senses to have it defined there # The commit message RIOT-OS#2 will be skipped: # fixup! core: Made thread state an enum

sys: make uart_stdio RX optional (attempt #2)

The evtimer_msg test is expanded to also delete entries. Furthermore the messages that are printed should now show numbers that are very close (if not equal). Something like this: At 740 ms received msg 0: "RIOT-OS#2 supposed to be 740" At 1081 ms received msg 1: "#0 supposed to be 1081" At 1581 ms received msg 2: "#1 supposed to be 1581" At 4035 ms received msg 3: "RIOT-OS#3 supposed to be 4035" The function evtimer_print is also called to show the intermediate status of evtimer entries.

The evtimer_msg test is expanded to also delete entries. Furthermore the messages that are printed should now show numbers that are very close (if not equal). Something like this: At 740 ms received msg 0: "#2 supposed to be 740" At 1081 ms received msg 1: "#0 supposed to be 1081" At 1581 ms received msg 2: "#1 supposed to be 1581" At 4035 ms received msg 3: "#3 supposed to be 4035" The function evtimer_print is also called to show the intermediate status of evtimer entries.

The test randomly fails on `native` due to timers being not accurate but it cannot be otherwise. So better disable it than raising fake errors. main(): This is RIOT! (Version: buildtest) Testing generic evtimer This should list 2 items ev RIOT-OS#1 offset=1000 ev RIOT-OS#2 offset=500 This should list 4 items ev RIOT-OS#1 offset=659 ev RIOT-OS#2 offset=341 ev RIOT-OS#3 offset=500 ev RIOT-OS#4 offset=2454 Are the reception times of all 4 msgs close to the supposed values? At 662 ms received msg 0: "RIOT-OS#2 supposed to be 659" At 1009 ms received msg 1: "#0 supposed to be 1000" At 1511 ms received msg 2: "RIOT-OS#1 supposed to be 1500" Traceback (most recent call last): File "/tmp/dwq.0.3125418833043728/ef3af88c4b3615788b164464a437df5c/tests/evtimer_msg/tests/01-run.py", line 33, in <module> sys.exit(run(testfunc)) File "/tmp/dwq.0.3125418833043728/ef3af88c4b3615788b164464a437df5c/dist/pythonlibs/testrunner/__init__.py", line 29, in run testfunc(child) File "/tmp/dwq.0.3125418833043728/ef3af88c4b3615788b164464a437df5c/tests/evtimer_msg/tests/01-run.py", line 26, in testfunc assert(actual in range(expected - ACCEPTED_ERROR, expected + ACCEPTED_ERROR)) AssertionError

The ENTROPY test always fails on this board main(): This is RIOT! (Version: buildtest) mbedtls test SHA-224 test RIOT-OS#1: passed SHA-224 test RIOT-OS#2: passed SHA-224 test RIOT-OS#3: passed SHA-256 test RIOT-OS#1: passed SHA-256 test RIOT-OS#2: passed SHA-256 test RIOT-OS#3: passed ENTROPY test: failed

fix compile errors

add microcoap example application

19270: drivers/at24cxxx: implement _mtd_at24cxxx_read_page r=benpicco a=HendrikVE ### Contribution description The function `read_page` was missing which lead to (from a user perspective) undefined behavior on the MTD layer. ### Testing procedure Any application using MTD in conjunction with a board with an at24cxxx. 19271: core/xfa: disable asan on llvm r=benpicco a=Teufelchen1 ### Contribution description Hi! 🦎 When using llvm and address sanitation, the XFA trip the sanitizer. This PR attempts to fix this by adding the `no_sanitize` attribute to the XFA macros. Sadly, this attribute is not known by gnu, a guard is hence needed. I'm open for alternatives as I dislike this solution but it is the best I could come up with. ### Testing procedure Before this patch: Go to `examples/gnrc_minimal` and run `TOOLCHAIN=llvm make all-asan` and then `make term`. You should see an error similar to this: ``` ==3374719==ERROR: AddressSanitizer: global-buffer-overflow on address 0x080774e0 at pc 0x0804af5e bp 0x0808eb88 sp 0x0808eb78 READ of size 4 at 0x080774e0 thread T0 #0 0x804af5d in _auto_init_module /RIOT/sys/auto_init/auto_init.c:40 #1 0x804af5d in auto_init /RIOT/sys/auto_init/auto_init.c:339 #2 0x804b375 in main_trampoline /RIOT/core/lib/init.c:56 #3 0xf76bc7b8 in makecontext (/lib32/libc.so.6+0x4a7b8) ... ``` After applying this PR, the example can be build and run with llvm or gcc, with or without asan. Co-authored-by: Hendrik van Essen <hendrik.vanessen@ml-pa.com> Co-authored-by: Teufelchen1 <bennet.blischke@haw-hamburg.de>

18392: drivers/servo: reimplement with high level interface r=benpicco a=maribu ### Contribution description The previous servo driver didn't provide any benefit over using PWM directly, as users controlled the servo in terms of PWM duty cycles. This changes the interface to provide a high level interface that abstracts the gory PWM details. In addition, a SAUL layer and auto-initialization is provided. ### Testing procedure The test application provides access to the servo driver via the `saul` shell command. ``` > saul 2022-08-02 22:12:31,826 # saul 2022-08-02 22:12:31,827 # ID Class Name 2022-08-02 22:12:31,830 # #0 ACT_SWITCH LD1(green) 2022-08-02 22:12:31,832 # #1 ACT_SWITCH LD2(blue) 2022-08-02 22:12:31,834 # #2 ACT_SWITCH LD3(red) 2022-08-02 22:12:31,837 # #3 SENSE_BTN B1(User button) 2022-08-02 22:12:31,838 # #4 ACT_SERVO servo > saul write 4 0 2022-08-02 22:12:41,443 # saul write 4 0 2022-08-02 22:12:41,445 # Writing to device #4 - servo 2022-08-02 22:12:41,447 # Data: 0 2022-08-02 22:12:41,450 # [servo] setting 0 to 2949 (0 / 255) 2022-08-02 22:12:41,453 # data successfully written to device #4 > saul write 4 256 2022-08-02 22:12:45,343 # saul write 4 256 2022-08-02 22:12:45,346 # Writing to device #4 - servo 2022-08-02 22:12:45,347 # Data: 256 2022-08-02 22:12:45,351 # [servo] setting 0 to 6865 (255 / 255) 2022-08-02 22:12:45,354 # data successfully written to device #4 ``` Each write resulted in the MG90S servo that I connected to move to the corresponding position. ### Issues/PRs references 19292: sys/phydat: Fix unit confusion r=benpicco a=maribu ### Contribution description Previously, `UNIT_G` was used for g-force with the correct symbol `g`, `UNIT_GR` for gram (as in kilogram) with the incorrect symbol `G` (which would be correct for Gauss), and `UNIT_GS` for Gauss with symbol `Gs` (which is an alternative correct symbol). To avoid confusion between G-Force, Gauss, and Gram the units have been renamed to `UNIT_G_FORCE`, `UNIT_GRAM`, and `UNIT_GAUSS`. In addition, gram now uses the correct symbol `g`; which sadly is the same as for g-force. But usually there is enough context to tell them apart. ### Testing procedure Green CI ### Issues/PRs references None 19294: sys/shell: don't include suit command by default r=benpicco a=benpicco 19295: gcoap: Finish the gcoap_get_resource_list_tl -> gcoap_get_resource_list renaming r=benpicco a=chrysn ### Contribution description In #16688, an argument was added to the `gcoap_get_resource_list` function by creating a new function `gcoap_get_resource_list_tl` with a deprecation and roll-over plan. This plan has not been acted on so far. This PR shortens the original plan by just adding the argument to `gcoap_get_resource_list` and removing `gcoap_get_resource_list_tl` in a single go. The rationale for this deviation is that while it's a public API, its only two practical consumers are the (built-in) well-known/core implementation, and the (built-in) CoRE Resource Directory (cord) endpoint. Moreover, a further change to this API (switching over to `coap_block_slicer_t`) is expected to happen within this release cycle, which would take something like 4 total releases to get through otherwise, which is unrealistic for an API that there are no known external users of. A second commit clean up ToDo items (in the changed function's documentation) that referred to a IETF draft that has long been abandoned by the CoRE WG. ### Testing procedure Plain inspection and CI passing should suffice. ### AOB There is a second analogous pair left over from #16688, `gcoap_req_send` / `gcoap_req_send_tl`. As that *is* expected to be used widely, I prefer not to mix these two concerns, and get the present one through without unnecessary hold-up. Co-authored-by: Marian Buschsieweke <marian.buschsieweke@ovgu.de> Co-authored-by: Benjamin Valentin <benjamin.valentin@bht-berlin.de> Co-authored-by: chrysn <chrysn@fsfe.org>

18392: drivers/servo: reimplement with high level interface r=benpicco a=maribu ### Contribution description The previous servo driver didn't provide any benefit over using PWM directly, as users controlled the servo in terms of PWM duty cycles. This changes the interface to provide a high level interface that abstracts the gory PWM details. In addition, a SAUL layer and auto-initialization is provided. ### Testing procedure The test application provides access to the servo driver via the `saul` shell command. ``` > saul 2022-08-02 22:12:31,826 # saul 2022-08-02 22:12:31,827 # ID Class Name 2022-08-02 22:12:31,830 # #0 ACT_SWITCH LD1(green) 2022-08-02 22:12:31,832 # #1 ACT_SWITCH LD2(blue) 2022-08-02 22:12:31,834 # #2 ACT_SWITCH LD3(red) 2022-08-02 22:12:31,837 # #3 SENSE_BTN B1(User button) 2022-08-02 22:12:31,838 # #4 ACT_SERVO servo > saul write 4 0 2022-08-02 22:12:41,443 # saul write 4 0 2022-08-02 22:12:41,445 # Writing to device #4 - servo 2022-08-02 22:12:41,447 # Data: 0 2022-08-02 22:12:41,450 # [servo] setting 0 to 2949 (0 / 255) 2022-08-02 22:12:41,453 # data successfully written to device #4 > saul write 4 256 2022-08-02 22:12:45,343 # saul write 4 256 2022-08-02 22:12:45,346 # Writing to device #4 - servo 2022-08-02 22:12:45,347 # Data: 256 2022-08-02 22:12:45,351 # [servo] setting 0 to 6865 (255 / 255) 2022-08-02 22:12:45,354 # data successfully written to device #4 ``` Each write resulted in the MG90S servo that I connected to move to the corresponding position. ### Issues/PRs references 19292: sys/phydat: Fix unit confusion r=benpicco a=maribu ### Contribution description Previously, `UNIT_G` was used for g-force with the correct symbol `g`, `UNIT_GR` for gram (as in kilogram) with the incorrect symbol `G` (which would be correct for Gauss), and `UNIT_GS` for Gauss with symbol `Gs` (which is an alternative correct symbol). To avoid confusion between G-Force, Gauss, and Gram the units have been renamed to `UNIT_G_FORCE`, `UNIT_GRAM`, and `UNIT_GAUSS`. In addition, gram now uses the correct symbol `g`; which sadly is the same as for g-force. But usually there is enough context to tell them apart. ### Testing procedure Green CI ### Issues/PRs references None Co-authored-by: Marian Buschsieweke <marian.buschsieweke@ovgu.de>

18392: drivers/servo: reimplement with high level interface r=benpicco a=maribu ### Contribution description The previous servo driver didn't provide any benefit over using PWM directly, as users controlled the servo in terms of PWM duty cycles. This changes the interface to provide a high level interface that abstracts the gory PWM details. In addition, a SAUL layer and auto-initialization is provided. ### Testing procedure The test application provides access to the servo driver via the `saul` shell command. ``` > saul 2022-08-02 22:12:31,826 # saul 2022-08-02 22:12:31,827 # ID Class Name 2022-08-02 22:12:31,830 # #0 ACT_SWITCH LD1(green) 2022-08-02 22:12:31,832 # #1 ACT_SWITCH LD2(blue) 2022-08-02 22:12:31,834 # #2 ACT_SWITCH LD3(red) 2022-08-02 22:12:31,837 # #3 SENSE_BTN B1(User button) 2022-08-02 22:12:31,838 # #4 ACT_SERVO servo > saul write 4 0 2022-08-02 22:12:41,443 # saul write 4 0 2022-08-02 22:12:41,445 # Writing to device #4 - servo 2022-08-02 22:12:41,447 # Data: 0 2022-08-02 22:12:41,450 # [servo] setting 0 to 2949 (0 / 255) 2022-08-02 22:12:41,453 # data successfully written to device #4 > saul write 4 256 2022-08-02 22:12:45,343 # saul write 4 256 2022-08-02 22:12:45,346 # Writing to device #4 - servo 2022-08-02 22:12:45,347 # Data: 256 2022-08-02 22:12:45,351 # [servo] setting 0 to 6865 (255 / 255) 2022-08-02 22:12:45,354 # data successfully written to device #4 ``` Each write resulted in the MG90S servo that I connected to move to the corresponding position. ### Issues/PRs references Co-authored-by: Marian Buschsieweke <marian.buschsieweke@ovgu.de>

cpu/native: introduce periph_i2c_mock

ghost assigned OlegHahm Feb 28, 2013

OlegHahm closed this as completed Feb 28, 2013

mehlis mentioned this issue Aug 13, 2013

segfault in vtimer update shortterm #132

Closed

benpicco mentioned this issue Oct 26, 2013

native uart0 crashes when no real terminal is attached #270

Closed

OlegHahm referenced this issue in OlegHahm/RIOT Nov 6, 2013

Merge pull request #2 from LudwigOrtmann/master

6f8650a

Native board doxygen integration

haukepetersen mentioned this issue Jan 15, 2014

Thread-local memory #506

Closed

rousselk added a commit that referenced this issue Feb 17, 2014

Merge pull request #2 from LudwigOrtmann/shell_syscalls

3753f38

add system calls to the shell (to implement a reboot command)

haukepetersen referenced this issue in haukepetersen/RIOT Jul 30, 2014

Merge pull request #2 from haukepetersen/pca10000_3

f77a8fe

Pca10000 3

maxencechotard mentioned this issue Dec 10, 2014

samr21 : RPL_UDP: always falling into "isr_hard_fault" #2173

Closed

PeterKietzmann mentioned this issue Jul 9, 2015

ng_nativenet crashes when hammered #3222

Closed

OlegHahm mentioned this issue Jul 10, 2015

netdev2_tap: crashes when hammered #3341

Closed

mali added a commit to mali/RIOT that referenced this issue May 19, 2016

boards/arduino-uno : fix flash programmer RIOT-OS#2

a6ae250

bergzand referenced this issue in bergzand/RIOT Dec 31, 2016

# This is a combination of 2 commits.

2ff56de

# This is the 1st commit message: Support for radio chip MRF24J40 - Work In Progress # This is the commit message #2: added new files to project

nmeum added a commit to nmeum/RIOT that referenced this issue May 1, 2017

Mehr buildsystem fixes 🚑🚑🚑

c8f1f22

Siehe RIOT-OS#2

riot-ci pushed a commit to riot-ci/RIOT that referenced this issue May 26, 2017

Merge pull request RIOT-OS#2 from biboc/openthread-FCS-FIX

6c5b99a

Fix FCS packet length problem

roberthartung added a commit to roberthartung/RIOT that referenced this issue Jun 29, 2017

gitlab ci: PORT test RIOT-OS#2

1f3db03

riot-ci pushed a commit to riot-ci/RIOT that referenced this issue Jul 19, 2017

Merge pull request RIOT-OS#2 from smlng/fix/export_features

412d9d2

shell: remove feature guards from sc_rtc

roberthartung added a commit to roberthartung/RIOT that referenced this issue Jul 24, 2017

gitlab ci: PORT test RIOT-OS#2

8834829

travisgriggs mentioned this issue Sep 21, 2017

samd21:uart TXC test backwards #7617

Closed

kaspar030 mentioned this issue Jan 11, 2018

net: Introduce iolists #8351

Merged

22 tasks

riot-ci pushed a commit to riot-ci/RIOT that referenced this issue Apr 6, 2018

Merge pull request RIOT-OS#2 from cladmi/pr/7651/Generic_memory_block…

22fe85a

…_allocator Fix printf %zu and 0x%p

riot-ci pushed a commit to riot-ci/RIOT that referenced this issue May 1, 2018

Merge pull request RIOT-OS#2 from Hyungsin/openthread-ftd-mtd-ncp

aa7948e

pkg/openthread: fix bit alignment error of uart driver

Mario0x1 mentioned this issue May 7, 2018

EFM32 (sltb001a) is missing FEATURES_PROVIDED=cpp #9093

Closed

nunux13 mentioned this issue May 19, 2018

__libc_init_array () trigger HARD FAULT HANDLER on SAML21E18B arm core bug #9155

Closed

riot-ci pushed a commit to riot-ci/RIOT that referenced this issue Jun 20, 2018

squash: reflect comments RIOT-OS#2

1b0efd6

riot-ci pushed a commit to riot-ci/RIOT that referenced this issue Jul 4, 2018

address @gebart's comments RIOT-OS#2

b63725c

riot-ci pushed a commit to riot-ci/RIOT that referenced this issue Jul 4, 2018

address @gebart's comments RIOT-OS#2

6640e24

VilleHiltunen pushed a commit to VilleHiltunen/RIOT that referenced this issue Jul 19, 2018

Speculative whitespace fix RIOT-OS#2

e821619

kaspar030 added a commit that referenced this issue May 9, 2019

Merge pull request #11310 from OTAkeys/make_uart_stdio_rx_optional

a9f1a85

sys: make uart_stdio RX optional (attempt #2)

This was referenced Jul 16, 2019

pkg/semtech_loramac: fix memcpy to uninitialized pointer #11847

Merged

pkg/semtech_loramac: fix memcpy to uninitialized pointer [backport 2019.07] #11848

Merged

fjmolinas mentioned this issue Nov 25, 2019

doc: document how to handle multiple cpu_models in a directory #12407

Open

benpicco mentioned this issue Aug 4, 2021

gnrc_ipv6_simple_subnets: auto-configuration for nested subnets on a simple tree topology #16536

Merged

CW-75 pushed a commit to CW-75/RIOT that referenced this issue Jul 1, 2022

Merge pull request RIOT-OS#2 from Mesh4all/fix/compilation_errors

aab1247

fix compile errors

chrysn pushed a commit to chrysn-pull-requests/RIOT that referenced this issue Sep 16, 2022

Merge pull request RIOT-OS#2 from Lotterleben/microcoap_example

efb0740

add microcoap example application

hugueslarrive added a commit to hugueslarrive/RIOT that referenced this issue Jun 20, 2023

cpu/atmega_common: checking features instead of CPU RIOT-OS#2

6d39173

hugueslarrive added a commit to hugueslarrive/RIOT that referenced this issue Jun 20, 2023

fixup! cpu/atmega_common: checking features instead of CPU RIOT-OS#2

c3b5344

mrdeep1 added a commit to mrdeep1/RIOT that referenced this issue Sep 8, 2023

Test fix for Murdock build RIOT-OS#2

80520e0

riot-ci mentioned this issue Sep 8, 2023

pkg/libcoap: Add in libcoap CoAP library support #19889

Open

gdoffe added a commit to cogip/RIOT that referenced this issue Feb 23, 2024

Merge pull request RIOT-OS#2 from cogip/native_i2c_mock

a9ed4e5

cpu/native: introduce periph_i2c_mock

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Start a RIOT #2

Start a RIOT #2

OlegHahm commented Feb 28, 2013

OlegHahm commented Feb 28, 2013

Start a RIOT #2

Start a RIOT #2

Comments

OlegHahm commented Feb 28, 2013

OlegHahm commented Feb 28, 2013