- Aug 25, 2019
-
- Aug 24, 2019
-
-
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.
-
rahix authored
Signed-off-by:
Rahix <rahix@rahix.de>
-
- Aug 23, 2019
- Aug 22, 2019
-
-
schneider authored
-
Manuel Kasten authored
-
Hinerk authored
-
swym authored
-
Hinerk authored
-
swym authored
-
Stefan Haun authored
0x31 - battery_current 0x32 - chargein_voltage 0x33 - chargein_current 0x34 - system_voltage 0x35 - thermistor_voltage
-
rahix authored
Related to #20. Signed-off-by:
Rahix <rahix@rahix.de>
-
- Aug 21, 2019
-
-
Signed-off-by:
Rahix <rahix@rahix.de>
-
- Aug 20, 2019
-
-
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.
-
trilader authored
-
-
rahix authored
Signed-off-by:
Rahix <rahix@rahix.de>
-
rahix authored
Signed-off-by:
Rahix <rahix@rahix.de>
-
- Aug 19, 2019
-
-
trilader authored
-
- Aug 17, 2019
-
-
rahix authored
Co-authored-by:
fleur <spacecarrot@fleurshax.net> Signed-off-by:
Rahix <rahix@rahix.de>
-
- Aug 16, 2019
-
-
Hauke Mehrtens authored
This allows to set the current time in milliseconds. Signed-off-by:
Hauke Mehrtens <hauke@hauke-m.de>
-
rahix authored
Signed-off-by:
Rahix <rahix@rahix.de>
-
- Aug 15, 2019
-
-
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>
-
- Aug 12, 2019
-
- Aug 04, 2019
-
-
rahix authored
Signed-off-by:
Rahix <rahix@rahix.de>
-