Adds an option to write a btsnoop compatible log file containing BLE
traffic. A new file is created after each boot if BLE is activated and
the `ble_log_enable` option is set in `card10.cfg`. The last 10 logs are
kept via log rotation.

It's 44 years since the release of vi and sadly lots of editors still
don't care about trimming off trailing spaces ...

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

Kai authored 4 years ago and rahix committed 4 years ago

Original work from @sistason in MR !121, rebased
on latest master.

Commit 1ea42e8e
Author: Kai <sistason@sistason.de>
Date:   Mon Aug 19 21:58:11 2019 +0200

    Adds Docker for firmware-building

    This commit adds a Dockerfile to build a docker
    container to build the firmware with.  It also
    updates the documentation on how to do that.

Changelog:

    - packaging: upgrade development status to beta
    - build: remove FIXME about VERSION
    - test: cover additional macro cases
    - parser: simplify macro arguments extraction
    - Re-use the looked up cursor of a token.
    - test: cover cases of functions with no parameters
    - parser: fix documentation of non prototyped functions
    - doc: add example with preprocessor

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

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

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

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

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

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

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>

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.

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

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>

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

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

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

Philip Stewart authored 5 years ago and rahix committed 5 years ago

Fix two bugs in the display/gfx module:

1. The animation of the simple_menu used in the main menu had the issue
   that there is a black line visible at the top.  This is due the
   gfx_puts method ignoring lines, where the top pixel of the string is
   above the top of the screen.  As gfx_puts uses gfx_setpixel which in
   turn ignores pixels outside of the screen, remove the check in
   gfx_puts.
2. X and Y coordinates were cast to unsigned-ints before being given to
   the gfx-library which means calls like circ(0, -10, 30) would be draw
   at coordinates like [0,65526].  Fix this by changing the data-type of
   all coordinates to signed-integers.

Also remove the x and y ranges from the documentation of the individual
python functions and instead add a general documentation about the
screen and it's size/coordinate system.

Serge Bazanski authored 5 years ago and dx committed 5 years ago

We update the documentaiton and CI tooling to remove references to the jailbreak firmware.

We also slightly update the docs to mention USB mode in a separate page, for unification purposes.

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

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

Astro authored 5 years ago and rahix committed 5 years ago

Partial merge of !303

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

joe landa authored 5 years ago and rahix committed 5 years ago

Update overview.rst for easier understanding/usage of the Pycardium
debugger and console.  For people like me who had no idea how to use it
before.

Manual merge for !219

Michael Huebler authored 5 years ago and rahix committed 5 years ago

Update how-to-build.rst - Added another hint for macOS, for the common
problem that strip fails on mpy-cross with "malformed object (unknown
load command 9)"

Manual merge for !173