1. The page preview seems unusable anyway, as GitLab doesn't serve HTML
   pages (only allows to download them).
2. Rules seems broken and 'splits' pipelines:
   https://gitlab.com/gitlab-org/gitlab/-/issues/34756
   In return, 'only' is deprecated, but at least it works.

This also hopefully stops us from submitting random MR docs onto the
production pages.

We need to have the bmi270 component available, even though we don't
even link against it.

This moves the raw read/write access code from the recovery mode into
st3m, and gives us the ability to mount/unmount the FAT partition on
demand.

q3k authored 1 year ago and q3k committed 1 year ago

This should make it easier to run clang-check/clang-tidy locally.

Only ctx.arc has a 6th integer argument, integer truncation was applied to
all 6-argument methods.

Tested by doing the following in REPL:

    >>> import hardware
    >>> ctx = hardware.get_ctx()
    >>> ctx.rgb(1, 0, 0)
    <ctx_type>
    >>> ctx.rectangle(-120, -120, 240, 240)
    <ctx_type>
    >>> ctx.fill()
    <ctx_type>
    >>> hardware.display_update(ctx)

Fixes #25.

Whoops.

This allows us to os.listdir("/").

We seem to be wasting a lot of internal memory on random mallocs(),
preventing us from late-initializing bluetooth/BLE.

Fixes #13 . Maybe. We'll see with time.

I think a more complete approach would be to force all micropython
allocations to land in SPIRAM? Or maybe use some memory watermarking to
make the micropython allocator only use internal memory if there's
plenty of it available, enough to initialize BLE?

Fixes #12.

This is the first implementation of the Recovery Mode for the badge.

See README for information on how to use/flash it.

We attempt to share st3m with the recovery firmware, and thus must
eliminate two components that can't live in the recovery firmware:

1. The startup function, which contains references to all matters of
   subfunctionality we don't want (audio, micropython, etc)
2. The FS code, which contains references to the tarball extraction
   logic (which we don't want to embed into recovery mode either).

We don't pre-generate a FAT partition anymore.

Looks like we won't be using frozen Python modules, probably.