- 14 Sep, 2019 1 commit
-
-
schneider authored
Also modifies the PMIC UI code to be more intuitive
-
- 31 Aug, 2019 1 commit
-
- 28 Aug, 2019 1 commit
-
- 24 Aug, 2019 1 commit
-
-
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.
-
- 23 Aug, 2019 1 commit
-
-
schneider authored
-
- 22 Aug, 2019 3 commits
-
-
Rahix authored
Related to #20. Signed-off-by:
Rahix <rahix@rahix.de>
-
-
- 20 Aug, 2019 3 commits
-
-
trilader authored
This includes a new RTOS task to animate the personal state LED independently of pycardium. While the animation is running pycardium can't control the personal state LED.
-
Rahix authored
Signed-off-by:
Rahix <rahix@rahix.de>
-
-
- 19 Aug, 2019 1 commit
-
-
trilader authored
-
- 17 Aug, 2019 1 commit
-
-
Rahix authored
Co-authored-by:
fleur <spacecarrot@fleurshax.net> Signed-off-by:
Rahix <rahix@rahix.de>
-
- 15 Aug, 2019 3 commits
-
-
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 <rahix@rahix.de>
-
Rahix authored
Signed-off-by:
Rahix <rahix@rahix.de>
-
Rahix authored
Also add a mutex around API calls in preparation for future changes. Signed-off-by:
Rahix <rahix@rahix.de>
-
- 09 Aug, 2019 1 commit
-
-
- 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
-
- 06 Aug, 2019 4 commits
-
-
Rahix authored
Signed-off-by:
Rahix <rahix@rahix.de>
-
- 02 Aug, 2019 1 commit
-
- 29 Jul, 2019 1 commit
-
- 22 Jul, 2019 1 commit
-
- 21 Jul, 2019 1 commit
-
-
Gerd authored
-
- 20 Jul, 2019 2 commits
-
-
Rahix authored
Signed-off-by:
Rahix <rahix@rahix.de>
-
Rahix authored
Closes #41 Signed-off-by:
Rahix <rahix@rahix.de>
-
- 16 Jul, 2019 1 commit
-
-
Rahix authored
Signed-off-by:
Rahix <rahix@rahix.de>
-
- 11 Jul, 2019 1 commit
-
-
Rahix authored
Signed-off-by:
Rahix <rahix@rahix.de>
-
- 08 Jul, 2019 1 commit
-
- 05 Jul, 2019 2 commits
-
-
Rahix authored
Signed-off-by:
Rahix <rahix@rahix.de>
-
Rahix authored
Signed-off-by:
Rahix <rahix@rahix.de>
-