What it does for you
Gives product firmware one consistent foundation for EFL modules instead of letting each feature invent its own status codes, constants, configuration reporting, and lock boundary.
EFL foundation
Core
The shared base layer for portable EFL modules: status values, constants, configuration diagnostics, umbrella includes, and callback-backed lock handling.
Use whenMultiple EFL modules need one status and lock contract.
IncludesConstants, config reporting, umbrella headers, locks.
API count5 current callable services.
Best fitPortable firmware shared across RTOS and bare-metal targets.
What is in the repo
efl.h, efl_common.h, efl_constants.h, efl_configure.h, efl_lock.h, matching C files, and optional SafeCLib adapter sources.
Why you need it
Use it when you want the other EFL modules to share one portable contract for success/failure reporting, compile-time feature visibility, and product-owned synchronization.
Public API.
Small foundation calls that let every EFL module report build capability and share the same product-owned lock boundary.
EflConfigureGetBuildOptions(void)Returns compile-time feature flags. Example: a service screen can show whether SafeCLib adapter support or FileX stdio support was compiled into this firmware build.EFL_LockInit(lock, acquire, release, context)Binds your RTOS mutex, critical-section wrapper, or no-RTOS lock callback to an EFL lock object.EFL_LockIsConfigured(lock)Lets a module decide whether shared-state protection is active before using a lock path.EFL_LockAcquire(lock, timeoutMs)Requests the configured lock before touching shared state, such as a diagnostic buffer or module context used by more than one thread.EFL_LockRelease(lock)Releases the configured lock after the protected operation, using the same product-owned synchronization primitive.