crasbe
crasbe
> The `stdio_nimble_debug` module only enables the debug messages for the `stdio_nimble.c` module. Everything else is still sent to the normal `STDOUT`, which is redirected to the BLE interface. >...
> > [ ] Add mutex and two staged variable setting for `_status` to avoid race conditions. (Set a temporary `_status`, get mutex and check if global `_status` still has...
> There's one other thing to consider: The behavior of `stdio_nimble` without the callout and without ztimer is now blocking for `stdout`. This is typical behavior, but it has to...
I think the stack keeps on giving. Adding `ztimer_set` again caused the program to never call `_send_stdout` at all and it would crash without any further messages. I suspect that...
> I think the stack keeps on giving. Adding `ztimer_set` again caused the program to never call `_send_stdout` at all and it would crash without any further messages. I suspect...
The only other example I could find which requires increasing the `ISR_STACKSIZE` is openwsn: https://github.com/RIOT-OS/RIOT/blob/88f2e451ca9936a51804246e647e91e3959d6aa9/pkg/openwsn/Makefile.include#L62-L66 Ideally we would get away without increasing the ISR stack at all and I'm not...
I learned that `ps` requires `DEVELHELP = 1` in the Makefile to show the stack usage (I always wondered why it didn't do that in the `tests/sys/shell_ble` application). This might...
I decided to add a commit to replace the deprecated functions, as mentioned in #21234 too. Surprisingly it did not give a merge conflict in the rebase :D
It looks like this is turning into a bit of a rabbit hole again :melting_face: To test the different resolutions, I modified the `tests/periph/adc` test to sample once with every...
Interestingly, for the STM32L4, the behavior is different. I have a NUCLEO-L452RE here, and this is what the output looks like: ``` 2024-11-18 11:52:59,127 # ADC_LINE(0): 63 255 1023 4095...