...otherwise ->int_id will not be reloaded in the while-loop at
api_interrupt_trigger(), causing it to loop indefinitely

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

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>

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>

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

0x31 - battery_current
0x32 - chargein_voltage
0x33 - chargein_current
0x34 - system_voltage
0x35 - thermistor_voltage

* battery_voltage (already existed)
* battery_current
* chargein_voltage
* chargein_current
* system_voltage
* thermistor_voltage

Only allow paired devices to use this Service.

Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>