Files
tactility/TactilityKernel
Ken Van Hoeylandt 92ca046681 app-module events & callstack config, crash diagnostics (#630)
- Apps can specify task stack depth and preferred memory placement in their manifests.
- App identifiers are validated against length and character requirements.
- Crash diagnostics now show the crash cause, reason, fault address, call stack, and program-counter details, with logs saved for review.
- App closing is more consistent across built-in screens. There's now a dedicated function, and the old _emit() function is made private.
- Crash diagnostics no longer display a QR code without a call stack.
- Improved memory allocation for unrestricted requests.
2026-08-27 21:50:12 +02:00
..
2026-08-25 17:44:20 +02:00

TactilityKernel

TactilityKernel is the core component of the Tactility project, providing a hardware abstraction layer (HAL) and essential kernel services for embedded systems.

Features

  • Device and Driver Model: A flexible system for managing hardware devices and their corresponding drivers.
  • Peripheral Support: Standard interfaces for common peripherals:
    • GPIO (General Purpose Input/Output)
    • I2C (Inter-Integrated Circuit)
    • I2S (Inter-IC Sound)
    • SPI (Serial Peripheral Interface)
    • UART (Universal Asynchronous Receiver-Transmitter)
  • Concurrency Primitives: Built-in support for multi-threaded environments, including:
    • Threads and Dispatchers
    • Mutexes and Recursive Mutexes
    • Event Groups
    • Timers
  • Module System: Support for loadable modules that can export symbols and provide runtime-extensible functionality.
  • Device Tree Integration: Utilizes a devicetree-like system for hardware configuration and initialization.
  • Cross-Platform: Designed to run on both embedded platforms (such as ESP32) and desktop environments (Linux) for simulation and testing.