Core runtime helpers
Shared EFL constants, status handling, configuration reporting, bounded strings, deterministic memory and buffer helpers, plus math/conversion utilities.
Reusable C firmware modules, ThreadX-centered integrations, embedded services, and bench tools from Endeavor product work. Built for teams that need useful infrastructure without starting from zero.
Embedded teams keep rebuilding the same practical pieces: byte streams, logging, file transfer, boot/update handoff, diagnostics, network services, and test fixture glue. EFL is where we make those pieces easier to find, evaluate, reuse, and support.
The goal is not a giant framework. It is a practical library of small, understandable modules that can move into real products without forcing a team to restart its architecture.
The first EFL packages are reusable C modules, ThreadX-centered integrations, network services, production diagnostics, hardware-facing adapters, and bench tools that have come out of product work.
Some pieces are simple drop-in helpers. Others are larger product bridges such as pimaX, smbX, consoleX, and printX, where the value is in the boundary, documentation, test harnesses, and integration path around the firmware.
Shared EFL constants, status handling, configuration reporting, bounded strings, deterministic memory and buffer helpers, plus math/conversion utilities.
Category-based logging, measurement evidence, watchdog boundaries, LED indicators, and support hooks for manufacturing and field service.
Portable boundaries for bootloader handoff, image confirmation, file access, OTA policy, timestamps, JSON payloads, and bounded upload/download workflows.
Portable protocol and adapter work for CAN, NMEA 2000, J1939, ISO TP, UART, RS-485, Modbus RTU, HTTP, I2C, and SPI-backed device integration.
AT-command cellular foundations, CMUX/PPP boundaries, Quectel-oriented modem work, and BG95 USB/PPP runtime pieces.
ThreadX-centered bridges and product services for USB media transfer, embedded file sharing, remote GUIX display/control, and low-memory print/report workflows.
Developer-facing tools for command consoles, bench automation, relay control, MCP integrations, GUIX Studio workflows, and soon RTT-driven AI validation.
Core, Strings, Utilities, Log, LED, Boot, File, Memory, Measurement, OTA, Security, Time, Watchdog, and Xfer already have useful module boundaries or implementations, though several are still limited by examples, platform ports, or hardening work.
CANStack, Cell, UART, RS-485, Modbus, HTTP, I2C, and SPI are active development areas. Some have host tests and strong foundations; others are planned adapter and protocol work that should be evaluated before product use.
Portable USBX/FileX MTP bridge module extracted from a working ThreadX/Synergy demo, intended for products that need controlled media/device file transfer.
Native SMB2/SMB3 client work for embedded products that need Windows or Samba share access without a BSD socket shim or heap-heavy desktop stack.
Small VNC-compatible firmware/server and PC viewer approach for GUIX products that need remote screen view, touch injection, and hard-key control.
Embedded print client for direct Ethernet and USB host printers, designed for streaming jobs without a full spooler, renderer, or page framebuffer.
Command/menu foundation for embedded service ports, local diagnostics, manufacturing commands, and module diagnostic integration.
ESP32 relay-board firmware, SCPI/TCP bench tools, hardware references, and automation helpers for repeatable validation and fixture control.
Local MCP packages for Azure DevOps, JouleScope bench measurement, SmartPlug control, and Relay Board automation.
Branded GUIX Studio package with headless export and render hooks so multi-developer teams and AI editing loops can inspect GUIX projects without hand-opening every screen.
Planned tooling around SEGGER RTT evidence, firmware interaction, and AI-assisted embedded validation workflows.
All first-pass prices are set to $0 while we finish packaging, licensing, and checkout rules.
The catalog now has explicit pricing and access states. Today everything is public at $0. Later, individual rows can move to paid checkout, evaluation access, or supported-license access without changing the module pages.
EFL access
EFL is early. If one of these modules maps to a product need, start the conversation and we can talk through status, licensing, fit, and support.