easylogger-integrationlisted

# EasyLogger Integration ## Overview Use this skill to integrate EasyLogger without making logs distort the system being debugged. Confirm output backend, timestamp source, concurrency, buffer policy, and log level before relying on logs as evidence. ## When To Use Use this skill when: - The user wants to add or debug EasyLogger in MCU, RTOS, or bare-metal firmware. - Logs are missing, truncated, blocking, out of order, too slow, too verbose, or not timestamped correctly. - The task involves `elog_port`, UART output, flash/file logging, filters, colors, async output, or runtime log levels. Do not use this skill when the issue is raw UART capture quality. Use `embedded-serial-log-debug` first. ## First Questions Ask for: - Target MCU/RTOS/compiler and EasyLogger version or source. - Output backend: UART, RTT, semihosting, file, flash, network, shell, or custom. - Whether logs can block, allocate memory, or run in interrupt context. - Timestamp source and desired format. - Current `elog_cfg` and port functions if available. - Symptom and sample log output. ## Integration Checklist 1. Bring up one output path. Prove a minimal blocking UART/RTT output works before enabling async, flash, or network logging. 1. Implement port functions deliberately. Output, lock/unlock, time, and optional color handling must match the target environment. 1. Set log levels and filters. Avoid enabling verbose logs globally on timing-sensitive firmware. 1. Decide concurrency pol