fix(interrupts): Add the callbacks to the list of root pointers

See merge request !374

fix(ble): write new mac if files does not exist

See merge request card10/firmware!373

Fix LED mutex stuff

See merge request card10/firmware!369

leds_update_power() internally accesses the I2C bus so calls to this
function need to be inside an I2C lock section.

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

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

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

FS locking and FD counting

See merge request !370

Display a message on system panic

See merge request card10/firmware!362

See merge request !368

Instead of an ugly hack where spaces are used to pad the entries
background colors, properly draw a rectangle and the text above
it.  No visual change.

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

The query-arg is not needed, remove it.

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

Currently, panics will silently reboot if the user doesn't happen to
look at the serial console when it happens.  To give a bit more
feedback, display @msgctl's faultsplash and the panic messages as well.

Co-authored-by: Mateusz Zalega <mateusz@appliedsourcery.com>
Signed-off-by: Rahix <rahix@rahix.de>

See merge request card10/firmware!367

Originally, commit 1a3dfad3 ("fix(bhi160): Fix interrupt behavior
during initialization") was supposed to fix the BHI160 axis-mapping
issue (see card10/firmware#133) but apparently on some devices it still
needs the original hack to work.  Revert the removal of the axis-mapping
hack from commit 2f56ff36 ("fix(bhi160): Call bhy_mapping_matrix_set
twice for the first time").

Fixes: 1a3dfad3 ("fix(bhi160): Fix interrupt behavior during initialization")
Link: https://git.card10.badge.events.ccc.de/card10/firmware/issues/133


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

The mac Adress was printed in the wrong order, BLE stroes the MAC
address in LSB first mode, different from Ethernet which uses MSB first
mode.

Fixes: aece2960 ("feat(ble): Add some log messages")
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>

Instead of setting these values to 0, use the same settings as used in
lib/sdk/Libraries/BTLE/stack/ble-host/sources/stack/cfg/cfg_stack.c from
the Cordio SDK instead of 0.

In my small test these value sare not use in the normal pairing process,
so I think this is not fixing any problem.

Fixes: 4107bd22 ("hack(ble): Temporarily silence a warning")
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>

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

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

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>