GitLab

Epicardium API for max86150 aligned with latest state of sensor
development on card10.
Authored-by: Jakob (XDjackieXD) Riepler <jakob.riepler@chaosfield.at>
Co-Authored-by: Arist <aristkojevnikov@gmail.com>

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

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

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

Unify unrecoverable errors to use panic() in all cases.  This will allow
further changes to panic() to work for all critical errors.
Signed-off-by: Rahix <rahix@rahix.de>

Mateusz Zalega authored Aug 11, 2019 and Rahix committed Oct 03, 2019

Signed-off-by: Mateusz Zalega <mateusz@appliedsourcery.com>

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

Also decrease the time needed to update the LEDs

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

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

swym authored Aug 28, 2019 and Rahix committed Aug 28, 2019

Adds simple config parser along with config_ API that:

- supports default values for options
- allows typed querying of config values
- types supported: boolean, integer, floating point and string

unknown options are ignored and LOG_WARNed on the console

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

danukeru authored Aug 24, 2019 and Rahix committed Aug 24, 2019

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>

Related to #20.
Signed-off-by: Rahix <rahix@rahix.de>

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

The lifecycle task needs higher priority than the API to ensure it can
win the `api_mutex`, even during a busy payload.

This commit is potentially a fix for #94.
Signed-off-by: Rahix <rahix@rahix.de>

This includes a new RTOS task to animate the personal state LED
independently of pycardium. While the animation is running pycardium
can't control the personal state LED.

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>

This commit introduces a lifecycle for core 1.  Based on the new loading
system, a few APIs are made available to control the payload running on
core 1.  These are:

1. From core 1 (Pycardium, L0dable):

    - `epic_exec(name)` API Call:  Request loading of a new payload by
      name.  If the file does not exist, the call will return with an
      error code.  Otherwise, control will go to the new payload.
    - `epic_exit(retcode)` API Call:  Return from payload
      unconditionally.  This call should be called whenever a payload is
      done or when it has hit an unrecoverable error.  On `epic_exit`,
      Epicardium will reset the core back into the menu.

2. From inside Epicardium:

    - `epic_exec(name)`: This is **not** the same as the API call, as it
      needs a different implementation underneath.  It will load a new
      payload and wait until this load actually completed (synchroneous).
    - `return_to_menu()`: Return core 1 to the menu script no matter
      what it is currently doing.  This call is asynchroneous and will
      return immediately after scheduling the lifecycle task.  This task
      will then take care of actually performing the load.
Signed-off-by: Rahix <rahix@rahix.de>

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

Also add a mutex around API calls in preparation for future changes.
Signed-off-by: Rahix <rahix@rahix.de>