Tactility/TactilityKernel
Ken Van Hoeylandt 79d3dd4fdb
Improvements for apps, filesystems, terminal and shell (#659)
app-module

- Apps now have support for:
  - environment variables (inherit from parent app)
  - current workdir
  - window size (when running in terminal)
- Add type aliases like `AppId` and `PackageId`
- Remove data duplication between ledger and app instance records: create `AppManifestSet`
- `AppManifest` usage safety improved: pass by value where needed, or use `AppId` instead of a manifest.

Terminal and shell

- Moved shell commands into coreutils-module as proper apps.
- Refine stack size for terminal and shell because apps now run with their own task and stack (including in-memory apps)

Platform

- Fix for listing root dir on ESP32: wrap posix directory functions and wire in file systems.
- Moved all platform-specific file system init code to platform subprojects

Other

- Fix for screenshot capture (issue with paths)
- Fixes for coreutils app correctness
- Memory optimizations (use more PSRAM where possible) in various locations such as app-module, shell and terminal.
- `ls` and `help` commands now use terminal width and show columns of data by default
- Created fs helpers at `TactilityKernel/include/tactility/filesystem/fs.h` (partially ported from `ShellFs`)
2026-09-25 08:29:27 +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.