Sometimes during initialization, one `log_msg()` intercepts another one,
leading to a whole lot of weird issues in other modules (like I2C).  I
suspect this to be memory corruption of some kind.  The issues can be
fixed by performing serial prints in a critical section, thus ensuring
atomicity of prints.  Note that this does not mean log messages will not
interleave.

The CDC-ACM and BLE-Serial writes cannot be put into a critical section
and are thus a point where this code can still fail.  For now, however,
this fix ensures the race-conditions during startup, where USB and BLE
are not yet running, don't happen anymore.

Signed-off-by: Rahix <rahix@rahix.de>

See merge request !237

Relax lock requirements to prevent busy lock

See merge request !241

Signed-off-by: Rahix <rahix@rahix.de>

Signed-off-by: Rahix <rahix@rahix.de>

Signed-off-by: Rahix <rahix@rahix.de>

Signed-off-by: Rahix <rahix@rahix.de>

Signed-off-by: Rahix <rahix@rahix.de>

Signed-off-by: Rahix <rahix@rahix.de>

- hw-lock: Log task names and return address when lock is busy
- pmic: print strerror(errno)


See merge request !221

See merge request !200

fleur authored 5 years ago and rahix committed 5 years ago

Fixes #119

Signed-off-by: Rahix <rahix@rahix.de>

reserve api id block for max86150

See merge request !232

feat(ecg) add ecg application

See merge request !230

feat(max30001): Pycardium support

See merge request !226

MAX30001 support for epicardium

See merge request card10/firmware!225

fix(stream): Properly release locks

See merge request !224

Minor edit to the docstrings of personal_state. Colors for the camp and...

See merge request !228

doc(bhi160): Add BHI160 documentation

See merge request !231

Minor edit to the docstrings of personal_state. Colors for the camp and communication states are now correct