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>

Hauke Mehrtens authored 5 years ago and rahix committed 5 years ago

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

danukeru authored 5 years ago and rahix committed 5 years ago

Previously, race-conditions between multiple serial writes could lead to
memory corruption and weird artifacts like I2C getting stuck.  This
patch introduces a write-streambuffer which queues all messages.

Co-authored-by: Rahix <rahix@rahix.de>
Signed-off-by: danukeru <danukeru@foulab.org>

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

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

swym authored 5 years ago and rahix committed 5 years ago

usb/epc_usb
====
Contains device-independent USB implementation, services MAXUSB stack
and is given the actual USB descriptors & callbacks on initialization.
Handles USB events and configures/deconfigures the device accordingly
during the USB setup procedure.

usb/mass_storage & cdcacm
====
Contain device-specific implementations, service MAXUSB's device class
APIs for cdcacm and mass storage.
Here, mass storage is independent of the underlying storage device.

modules/usb
====
Public apic_usb API, configuration and storage device management.
Defines the actual USB device descriptors and services the upc_usb API.

If we want to add SD card functionality, this would be the place to add
it.

...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