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

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>

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>

swym authored 5 years ago and rahix committed 5 years ago

- Implement de-initialization
- Wrap filesystem operations in semaphore
- Introduce EpicFileSystem object and move epic_file_FOO(...)
  imlementations into efs_FOO(EpicFileSystem*, ...) functions.
- epic_file_FOO(...) functions are now wrappers around the _fs_
  functions, but lock and unlock the global filesystem object before &
  after calls.  This way, all efs_ functions can assume that the
  necessary lock has been acquired.
- libff: don't use FF_FS_REENTRANT, our own FS lock is enough

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

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

Closes #41

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

swym authored 5 years ago and rahix committed 5 years ago

Closes !20

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

glue functions for handling the locking are implement as weak symbols in
libff13 itself and overriden to use FreeRTOS's semaphores in epicardium

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

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

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

Gerd authored 5 years ago and rahix committed 5 years ago

Closes !13

Hopefully fixes #5.

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 commit changes the tickless idle behaviour.  Instead of keeping
interrupts off during sleep, they are enabled because preemption somehow
prevents them from triggering with WFE.  This might have unintended
sideeffects and needs further verification.

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