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 change allows cleaner loading of payloads and is a preparation for
the proper implementation/use of hardware_reset().

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

The bootloader will have initialized the display in all cases so we
don't need to repeat the same init code all over again.

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>

allow API signatures to contain the names "buffer" and "size"

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

When no `menu.py` is found, Epicardium will create one with the contents
of `preload/menu.py`.

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

Delaying BLE startup by a bit seems to resolve the lockup issue we
observed.  This might need further attention in the future.

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

Without resetting the FPU we get spurious failures in Pycardium.  These
manifest in many different forms, ranging from HardFaults and triggered
assertions to "syntax errors" in loaded scripts while said script does
not contain any.

These failures stem from the FPU still containing state from the last
loaded payload and thus sometimes corrupting stack locations where the
previous payload had floating point state.

Closes #72.

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

Co-authored-by: fleur <spacecarrot@fleurshax.net>
Signed-off-by: Rahix <rahix@rahix.de>

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

This adds BLE a characteristic which allows to set the current time. The
time is set in milliseconds since 1.1.1970 as 64 bit value.

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

This allows to set the current time in milliseconds.

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