Raphael Lehmann

Another addition: This driver thould use the [`SpiDevice`](https://docs.modm.io/develop/api/nucleo-f429zi/classmodm_1_1SpiDevice.html) abstraction and should make use of `void attachConfigurationHandler(Spi::ConfigurationHandler handler)`! @kikass13: We need this, because we have multiple MCP2515 and one ADIS16470 connected...

I think it would actually make sense to force all SPI drivers to always set all "relevant" SPI options, everything else doesn't work consistently and leads to strange behavior, especially...

> Then defining the modes is mandatory. Many modm drivers using Mode0 can't be used in a shared bus configuration because they assume the default mode 0. Currently almost all...

@nesos I would like to complete and merge your pull request, if you don't mind? I've already [rebased your branch](https://github.com/rleh/modm/tree/feature/hifive1) and [fixed the most conflicts](https://github.com/rleh/modm/commit/df377ca15e0b1a409522fbc76dea986f2f11cc73). Clock and Timers still have...

II have also experienced the same problem, could be reproduced even without VSCode with GDB in tui mode. (For example, I wasn't able to set breakpoints in the whole main.cpp...

This are the debug compile flags used by modm: https://github.com/modm-io/modm/blob/develop/tools/build_script_generator/common.py#L224-L225 and (in debug mode) https://github.com/modm-io/modm/blob/develop/tools/build_script_generator/common.py#L243-L246

Which flags does the STM32 Cube project use (by default)?

There is the (very) old unmerged #324 that at least partially fixes the issue.

> `FAIL: ltc2984_test:25 : true == false` > `FAIL: ltc2984_test:26 : true == false` Fix: ```diff - TEST_ASSERT_TRUE(modm::ltc2984::Data(0x01

https://github.com/modm-io/modm/blob/9abe7151a2bdd80b954cb9919712448f2782fb19/src/modm/driver/temperature/ltc2984.hpp#L78-L83 Fix: (?) ```diff - return (this->data & 0x800000) ? -(((~ret) + 1) & 0xffffff) : ret; + return (this->data & 0x800000ul) ? -(((~ret) + 1) & 0xfffffful) : ret;...