Commit dbeec980 ("fix(pycardium): Fix delay implementation") enables
the systick on core 1 but on loading a new app, it is not reset which
makes some l0dables crash.  Fix this by always resetting (disabling) the
SysTick in the core1_reset() stub.

Fixes: dbeec980 ("fix(pycardium): Fix delay implementation")
Reported-by: Beastie <fischervincent98@gmail.com>
Signed-off-by: Rahix <rahix@rahix.de>

See merge request card10/firmware!364

If an app directory is missing metadata.json or if metadata.json is
invalid/cannot be parsed correctly, don't just print an error, also add
a menu entry based on what we'd hope to be correct information.  This is
obviously best effort only and there is no guarantee that it will work.

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

Closes #181

See merge request card10/firmware!366

The first epic_ws2812_write() call will set the first pixel to 0x008000
(bright green).  This is caused by the GPIO line being pulled down on
mode-setting (epic_gpio_set_pin_mode).  Wait before writing the values
to reset the bus and thus properly set the pixels to the correct colors
on first write.

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

Closes #133

See merge request card10/firmware!365

The orientation sensor uses a different axis mapping than the other
sensors.  Document this.

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

Don't open all 4 virtual sensors all time time; only open the one which
is actually displayed.  This prevents the storm of queue-full message on
the serial terminal.

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

If initialization fails, bhi160 API calls should not infinitely block
waiting for it to complete; they should fail immediately with an error
stating that something went wrong.

Add a flag that indicates the driver to not accept API requests because
initialization was not finished properly.

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

As discussed in issue card10/firmware#133, the BHI160 changes its
interrupt behavior during initialization.  In commit 2f56ff36
("fix(bhi160): Call bhy_mapping_matrix_set twice for the first time")
a quick workaround for this issue was added.  Replace this hack with
a proper fix by reconfiguring the interrupt on the host side according
to the specification.

(Finally) fixes card10/firmware#133.

Fixes: 2f56ff36 ("fix(bhi160): Call bhy_mapping_matrix_set twice for the first time")
Link: https://git.card10.badge.events.ccc.de/card10/firmware/issues/133#note_5894


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

Port the bhi160 mutex and hwlock usage in bhi.c to the new mutex API.
This will hopefully increase system stability.

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

Closes #189

See merge request card10/firmware!363

The call to MAX77650_getDebounceStatusnEN0() in epic_buttons_read()
performs transactions on the I2C bus but is not guarded by locking the
I2C hwlock.  This leads to strange issues like USB mode deadlocking when
writing large files.

Widen the hwlock I2C section to encompass the MAX77650_getDebounceStatusnEN0()
call as well.  This fixes card10/firmware#189.

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

Port the buttons module to the new hardware lock API which can no longer
fail.

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

Move hw-locks to new mutex API in multiple steps to keep diffs readable.  The
users of hw-locks are **not** ported to the new-semantics; this needs to be
done as a follow up.  One patch is included, porting the MAX30001 driver in
commit 6da4644e ("chore(max30001): Port to new mutex and hw-lock APIs").

See merge request card10/firmware!356

Using a FreeRTOS mutex directly is deprecated.  Replace it with a
`struct mutex`.  Similarly, the deprecated `hwlock_acquire_timeout()`
is replaced with `hwlock_acquire()`.

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

Re-add a `hwlock_acquire()` method, but this time without a timeout
parameter.  From a functional point of view, this is just a wrapper
around `mutex_lock()`.

Additionally, add `hwlock_acquire_nonblock()` which behaves like
`mutex_trylock()`.

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

Rename hwlock_acquire() to hwlock_acquire_timeout() in preparation for
future changes to the hw-lock API.  Change all uses of the hw-lock API
to reflect this change.

This commit does not introduce any functional changes, except getting
rid of the timeout usage warnings.  This change is no-op, because the
hwlock_acquire() implementation already replaces any non-zero timeout
value with portMAX_DELAY.

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

With the switch to the new mutex API, hwlock_release() cannot fail under
any circumstances.  To emphasize this, make it return void instead of
int (Previously it just always returned 0).

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

Reimplement the hw-lock module to use the new mutex API.  This slightly
changes the semantics of locking a hw-lock as the new mutex API does not
allow timeouts.  When a hwlock_acquire() with a (non-infinite) timeout
is attempted, a warning is printed to the serial console.

Additionally, instead of returning -EINVAL on use of a non-existent
hardware lock, the new implementation triggers a firmware panic.

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

The poor-profiler scripts allow profiling card10 (to some degree).

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>

See merge request card10/firmware!337

fuchsi* authored 5 years ago and rahix committed 5 years ago

fix performance problems with pulse logging (caching time string and approximating timestamp via samplecount)

See merge request card10/firmware!361

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

Closes #192

See merge request card10/firmware!360