1. 26 Aug, 2019 1 commit
  2. 25 Aug, 2019 1 commit
  3. 24 Aug, 2019 2 commits
    • swym's avatar
      feat(epicardium): Add ESB module · 9b0fd54f
      swym authored and Rahix's avatar Rahix committed
      usb/epc_usb
      ====
      Contains device-independent USB implementation, services MAXUSB stack
      and is given the actual USB descriptors & callbacks on initialization.
      Handles USB events and configures/deconfigures the device accordingly
      during the USB setup procedure.
      
      usb/mass_storage & cdcacm
      ====
      Contain device-specific implementations, service MAXUSB's device class
      APIs for cdcacm and mass storage.
      Here, mass storage is independent of the underlying storage device.
      
      modules/usb
      ====
      Public apic_usb API, configuration and storage device management.
      Defines the actual USB device descriptors and services the upc_usb API.
      
      If we want to add SD card functionality, this would be the place to add
      it.
      9b0fd54f
    • Rahix's avatar
      chore: Fix docs · f2f3f050
      Rahix authored
      
      Signed-off-by: Rahix's avatarRahix <rahix@rahix.de>
      f2f3f050
  4. 23 Aug, 2019 5 commits
  5. 22 Aug, 2019 17 commits
  6. 21 Aug, 2019 1 commit
  7. 20 Aug, 2019 6 commits
  8. 19 Aug, 2019 1 commit
  9. 17 Aug, 2019 1 commit
  10. 16 Aug, 2019 3 commits
  11. 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
  12. 12 Aug, 2019 1 commit
    • fleur's avatar
      feat: Add proper LED module · e87cdd45
      fleur authored and Rahix's avatar Rahix committed
      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.
      e87cdd45