Implement the hal functions necessary for utime.ticks_ms() and
utime.ticks_us().  This enables much more accurate measurements of time
taken in Pycardium (useful for profiling).

Please note that the tick counter will reset whenever a new app is
loaded.

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

Add a short delay after opening USB-Mode to prevent immediate exit which
happened when pressing the select-button for a very short time.

Also exit the menu-app after exiting USB-Mode to force a reload and thus
immediately display changes in the apps/ folder.

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

Fix the display backlight staying off while the pmic task prints its
messages (power-off/sleep & battery critial).

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

fgross authored 5 years ago and rahix committed 5 years ago

The framebuf module provides a framebuffer implementation running purely
in MicroPython which will increase drawing performance by a lot.  A
follow-up change will be necessary to connect this framebuffer
implementation to the display API.

This commit is implements a part of MR !211.

Closes #177

See merge request card10/firmware!324

Rewrite the delay implementation to be more accurate and properly handle
incoming MicroPython interrupts (See issue #177).

For this, the delay is split into two functions:

- systick_delay_precise(): Delay with microsecond accuracy for delays
      less than 1 ms.
- systick_delay_sleep(): Sleep for a potentially very long time, using
      WFI to put the CPU to sleep.  Whenever the CPU wakes up, this
      function will poll the MicroPython scheduler so it can execute
      pending interrupts.

Ontop, this implementation allows for a future, fast, tick-based
monotonic time implementation (e.g. mp_hal_ticks_ms).

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

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

Enable the input() builtin which allows reading from the serial console.

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

Add an option to use the top right and bottom right buttons to move
in the menu.  The option would ideally be added to the card10.cfg.

Related: #178

See merge request card10/firmware!330

See merge request card10/firmware!355

Rewrite image-convert script to more easily change the version splash
screen.

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

Closes #53 and #188

See merge request card10/firmware!354

See merge request card10/firmware!353

RFC: Proper Mutexes

See merge request card10/firmware!345

Allow calling buttons.read() without an argument.  This is equivalent to
a mask with all bits set (that is, buttons.read(255)).  Additionally,
add a check that the mask is within the limits (< 256).

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

For convenience, allow calling os.listdir() without any argument.
This is equivalent to calling os.listdir("").

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

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

Using a bare FreeRTOS mutex is deprecated.  Replace it with the new
`struct mutex`.  This should increase stability of the module.  In the
process of switching, also remove the `EPIC_FAT_STATIC_SEMAPHORE` define
as it is no longer needed with the new mutex API.

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

Using a bare FreeRTOS mutex is deprecated.  Replace it with the new
`struct mutex`.  This should increase stability.

Additionally, fix a bug in `lifecycle.c:do_load()` where the function
would return without unlocking the API mutex if `hardware_reset()`
returns an error.

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

Using a bare FreeRTOS mutex is deprecated.  Replace it with the new
`struct mutex`.  This should increase stability of the module.

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

Using a bare FreeRTOS mutex is deprecated.  Replace it with the new
`struct mutex`.  This should increase stability of the module.

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

In the current firmware, different locking mechanisms a littered around
the code-base.  Among them are bare FreeRTOS mutexes and the hw-locks.
The callers for these often specify timeouts but don't make much effort
in A) picking robust values for the timeout and B) recovering gracefully
from a timeout happening.  Most of the time, we return -EBUSY to _Python
code_.  This is really really bad API design.  The firmware needs to
have enough integrity to ensure these situations can't ever occur.

To combat this, add a new locking primitive: The `struct mutex`.  The
intention is to replace all other locking and synchronization APIs with
this one.  This will provide one central place to debug any sort of
locking issues.

The `struct mutex` API is based on a few assumptions about locking.
Those are detailed in `Documentation/epicardium/mutex.rst`, which is
part of this commit.  The most important one is:

    Locking can **never** fail.

By requiring this to be true, we eliminate the need for drivers to
contain (often incorrect) logic for dealing with locking fails.  This
should drastically improve the stability of the firmware in regards to
lock-related bugs.

This commit does not introduce any functional changes yet.

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

See merge request card10/firmware!333

electrodes unfiltered

See merge request card10/firmware!347

Makes the `color` module page a lot more colorful!

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!346

Add a menu entry that opens USB storage.  Pressing any button will
return to the menu and disable USB storage again.

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

Add a mechanism for "favorite apps" which are shown at the top of the
app-list no matter what.

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