Select Git revision
Forked from
card10 / firmware
Source project has a limited visibility.
-
rahix authored
In the current firmware, different locking mechanisms a littered around the code-base. Among them are bare FreeRTOS mutexes and the hw-locks. The callers for these often specify timeouts but don't make much effort in A) picking robust values for the timeout and B) recovering gracefully from a timeout happening. Most of the time, we return -EBUSY to _Python code_. This is really really bad API design. The firmware needs to have enough integrity to ensure these situations can't ever occur. To combat this, add a new locking primitive: The `struct mutex`. The intention is to replace all other locking and synchronization APIs with this one. This will provide one central place to debug any sort of locking issues. The `struct mutex` API is based on a few assumptions about locking. Those are detailed in `Documentation/epicardium/mutex.rst`, which is part of this commit. The most important one is: Locking can **never** fail. By requiring this to be true, we eliminate the need for drivers to contain (often incorrect) logic for dealing with locking fails. This should drastically improve the stability of the firmware in regards to lock-related bugs. This commit does not introduce any functional changes yet. Signed-off-by:
Rahix <rahix@rahix.de>
rahix authoredIn the current firmware, different locking mechanisms a littered around the code-base. Among them are bare FreeRTOS mutexes and the hw-locks. The callers for these often specify timeouts but don't make much effort in A) picking robust values for the timeout and B) recovering gracefully from a timeout happening. Most of the time, we return -EBUSY to _Python code_. This is really really bad API design. The firmware needs to have enough integrity to ensure these situations can't ever occur. To combat this, add a new locking primitive: The `struct mutex`. The intention is to replace all other locking and synchronization APIs with this one. This will provide one central place to debug any sort of locking issues. The `struct mutex` API is based on a few assumptions about locking. Those are detailed in `Documentation/epicardium/mutex.rst`, which is part of this commit. The most important one is: Locking can **never** fail. By requiring this to be true, we eliminate the need for drivers to contain (often incorrect) logic for dealing with locking fails. This should drastically improve the stability of the firmware in regards to lock-related bugs. This commit does not introduce any functional changes yet. Signed-off-by:
Rahix <rahix@rahix.de>
main.c 1.91 KiB
#include "modules/modules.h"
#include "modules/log.h"
#include "modules/filesystem.h"
#include "card10-version.h"
#include "FreeRTOS.h"
#include "task.h"
#include <stdlib.h>
#include <string.h>
int main(void)
{
LOG_INFO("startup", "Epicardium startup ...");
LOG_INFO("startup", "Version " CARD10_VERSION);
LOG_INFO("startup", "Initializing hardware ...");
hardware_early_init();
LOG_INFO("startup", "Initializing tasks ...");
/* Serial */
if (xTaskCreate(
vSerialTask,
(const char *)"Serial",
configMINIMAL_STACK_SIZE,
NULL,
tskIDLE_PRIORITY + 1,
NULL) != pdPASS) {
LOG_CRIT("startup", "Failed to create %s task!", "Serial");
abort();
}
/* PMIC */
if (xTaskCreate(
vPmicTask,
(const char *)"PMIC",
configMINIMAL_STACK_SIZE,
NULL,
tskIDLE_PRIORITY + 4,
NULL) != pdPASS) {
LOG_CRIT("startup", "Failed to create %s task!", "PMIC");
abort();
}
/* API */
if (xTaskCreate(
vApiDispatcher,
(const char *)"API Dispatcher",
configMINIMAL_STACK_SIZE * 16,
NULL,
tskIDLE_PRIORITY + 2,
&dispatcher_task_id) != pdPASS) {
LOG_CRIT(
"startup",
"Failed to create %s task!",
"API Dispatcher"
);
abort();
}
/* BLE */
if (ble_shall_start()) {
if (xTaskCreate(
vBleTask,
(const char *)"BLE",
configMINIMAL_STACK_SIZE * 10,
NULL,
tskIDLE_PRIORITY + 1,
NULL) != pdPASS) {
LOG_CRIT("startup", "Failed to create %s task!", "BLE");
abort();
}
}
/* Lifecycle */
if (xTaskCreate(
vLifecycleTask,
(const char *)"Lifecycle",
configMINIMAL_STACK_SIZE * 4,
NULL,
tskIDLE_PRIORITY + 1,
NULL) != pdPASS) {
LOG_CRIT("startup", "Failed to create %s task!", "Lifecycle");
abort();
}
LOG_INFO("startup", "Starting FreeRTOS ...");
vTaskStartScheduler();
LOG_CRIT("startup", "FreeRTOS did not start due to unknown error!");
abort();
}