1. 05 Sep, 2019 1 commit
  2. 28 Aug, 2019 2 commits
  3. 27 Aug, 2019 1 commit
  4. 24 Aug, 2019 3 commits
  5. 23 Aug, 2019 1 commit
  6. 22 Aug, 2019 4 commits
  7. 21 Aug, 2019 7 commits
  8. 20 Aug, 2019 8 commits
  9. 19 Aug, 2019 1 commit
  10. 15 Aug, 2019 5 commits
    • 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
    • Rahix's avatar
      feat(epicardium): Add module for hardware init · be09c127
      Rahix authored
      
      Signed-off-by: Rahix's avatarRahix <rahix@rahix.de>
      be09c127
    • Rahix's avatar
      chore(epicardium): Move dispatcher into own module · 5f794074
      Rahix authored
      
      
      Also add a mutex around API calls in preparation for future changes.
      Signed-off-by: Rahix's avatarRahix <rahix@rahix.de>
      5f794074
    • Rahix's avatar
      feat(epicardium): Implement basic core 1 lifecycle · 3b9393fe
      Rahix authored
      
      
      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's avatarRahix <rahix@rahix.de>
      3b9393fe
    • Rahix's avatar
      feat(epicardium): Add switch for core 1 debugging · 32144f97
      Rahix authored
      
      Signed-off-by: Rahix's avatarRahix <rahix@rahix.de>
      32144f97
  11. 14 Aug, 2019 2 commits
  12. 12 Aug, 2019 1 commit
  13. 09 Aug, 2019 1 commit
    • swym's avatar
      feat(fatfs): Implement global FLASH lock · 6d1686e0
      swym authored
      - 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
      6d1686e0
  14. 06 Aug, 2019 3 commits