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

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

This commit introduces a lifecycle for core 1.  Based on the new loading
system, a few APIs are made available to control the payload running on
core 1.  These are:

1. From core 1 (Pycardium, L0dable):

    - `epic_exec(name)` API Call:  Request loading of a new payload by
      name.  If the file does not exist, the call will return with an
      error code.  Otherwise, control will go to the new payload.
    - `epic_exit(retcode)` API Call:  Return from payload
      unconditionally.  This call should be called whenever a payload is
      done or when it has hit an unrecoverable error.  On `epic_exit`,
      Epicardium will reset the core back into the menu.

2. From inside Epicardium:

    - `epic_exec(name)`: This is **not** the same as the API call, as it
      needs a different implementation underneath.  It will load a new
      payload and wait until this load actually completed (synchroneous).
    - `return_to_menu()`: Return core 1 to the menu script no matter
      what it is currently doing.  This call is asynchroneous and will
      return immediately after scheduling the lifecycle task.  This task
      will then take care of actually performing the load.

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

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

Also add a mutex around API calls in preparation for future changes.

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

This commit introduces a way to control core 1.  This is archieved by a
predefined API-Interrupt:  The reset interrupt.  When triggered, it will
bring the core back into its default state and wait for a new vector
address from Epicardium.  Once this vector address is transferred, it
will start the new payload.

This method only works as long as core 1 is responsive to the API
interrupts.  Cases where this might not be the case:

  - During times where core 1 has interrupts disabled
  - When in a higher priority exception handler
  - When core 1 has corrupted its IVT

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

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

Previously 0 was used but as 0 is also the ID of the reset interrupt,
this could lead to weird behaviors.

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

This allows pycardium to learn which script it should start once it
boots.  Arguments can only be read before any API calls are made.
Afterward they are lost.

To ensure they won't collide with anything during a core 1 restart,
they are offset by 0x20 from the start of the API buffer.

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

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

The vector table's alignment requirements depend on the number of
interrupts [1].  In our case, we have 0x6E(=110) interrupts and thus an
alignment requirement of 0x80(=128).

To satisfy this requirement, this commit moves the IVT to the beginning
of .text and enforces a 128 byte alignment.  Please note that the
headers which come before .text will push the IVT to 0x100 instead of
having it directly in the beginning at 0x00.

[1]: https://developer.arm.com/docs/dui0553/a/cortex-m4-peripherals/system-control-block/vector-table-offset-register



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

Closes #67

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

Mateusz Zalega authored 5 years ago and rahix committed 5 years ago

Signed-off-by: Mateusz Zalega <mateusz@appliedsourcery.com>

Mateusz Zalega authored 5 years ago and rahix committed 5 years ago

Signed-off-by: Mateusz Zalega <mateusz@appliedsourcery.com>

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

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

swym authored 5 years ago and rahix committed 5 years ago

Co-authored-by: Rahix <rahix@rahix.de>

This commit imports a few modules from micropython-lib.

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

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

This commit adds a script to embed the git-version of the firmware into
the bootloader, epicardium, and pycardium.  All three binaries will
display their version on startup.

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

Text was displayed one character further right than intended because the
offset was incremented before drawing.  This commit reverses the two
operations and thus restores proper display of text.

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

genofire authored 5 years ago and rahix committed 5 years ago

Closes !80

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

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

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

Mateusz Zalega authored 5 years ago and rahix committed 5 years ago

This commit substitutes the vendor gfx library with a completely
new implementation.  It also adds a text-buffer mode.

Signed-off-by: Mateusz Zalega <mateusz@appliedsourcery.com>

fleur authored 5 years ago and rahix committed 5 years ago

The new LED modules allow a much broader range of uses of the RGB LEDs.
It also includes smart powersaving and options to set all LEDs at once.