1. 21 May, 2020 2 commits
  2. 25 Nov, 2019 2 commits
  3. 03 Nov, 2019 2 commits
    • Rahix's avatar
      chore(api-lock): Port to new mutex API · 75278836
      Rahix authored
      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's avatarRahix <rahix@rahix.de>
      75278836
    • Rahix's avatar
      chore(lifecycle): Port to new mutex API · cc5f0e29
      Rahix authored
      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's avatarRahix <rahix@rahix.de>
      cc5f0e29
  4. 05 Oct, 2019 1 commit
  5. 28 Aug, 2019 1 commit
    • swym's avatar
      feat(epicardium): read card10.cfg · f1d63669
      swym authored
      Adds simple config parser along with config_ API that:
      
      - supports default values for options
      - allows typed querying of config values
      - types supported: boolean, integer, floating point and string
      
      unknown options are ignored and LOG_WARNed on the console
      f1d63669
  6. 22 Aug, 2019 2 commits
  7. 20 Aug, 2019 4 commits
  8. 19 Aug, 2019 1 commit
  9. 15 Aug, 2019 1 commit
    • Rahix's avatar
      feat(epicardium): Add core 1 lifecycle · b7c0b608
      Rahix authored
      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's avatarRahix <rahix@rahix.de>
      b7c0b608