Use this hub to turn a device requirement into a development and verification plan. The guides address engineering decisions behind custom firmware, Linux systems and connected products: what must be specified, how an implementation can fail, and what evidence is needed before handover. Choose the area closest to your current project stage rather than starting with a particular tool.
Choose a starting point
For a new MCU product, start with requirements and firmware reliability. For a custom Linux board, start with board bring-up and the boot path, then build a reproducible system image. For an existing product that needs connectivity, define network or Bluetooth behavior and failure recovery before adding a user interface. Delivery planning applies across all of these paths.
MCU & RTOS Firmware
Firmware requirements, peripheral integration, task coordination, fault diagnosis and verification for microcontroller products. Start from the actual hardware and acceptance conditions before choosing an implementation.
- MCU Firmware Outsourcing: What to Put in the Acceptance Requirements
- Intermittent RTOS Crashes: Logging, Core Dumps and a Reproducible Test
- Reviewing AI-Assisted MCU Drivers: Registers, Timing and Failure Paths
Linux BSP & Board Bring-up
Board-level Linux integration, U-Boot, device trees, kernel drivers and peripheral bring-up. Separate power and hardware checks from software adaptation, and define a recoverable boot path.
- Custom Linux Board Bring-Up: From Power Rails to the Application
- U-Boot Port Acceptance: Boot Media, Environment and Recovery
- Replacing a Wi-Fi Module: Linux Driver and Device-Tree Validation
- Reviewing AI-Assisted Device-Tree Changes: From Boot Logs to Real Peripherals
Buildroot & Root Filesystems
Reproducible system builds, custom packages, root filesystem layouts, startup services and persistent data. Buildroot is a build and integration tool; it is not a runtime layer between the kernel and applications.
- Reproducible Buildroot Delivery: From a Booting Image to a Release Kit
- Read-only Rootfs: Preserve Configuration, Logs and Update State Safely
- Reviewing AI-Assisted Buildroot Packages: Dependencies, Cross-Compilation and Clean Builds
Device Networking & Provisioning
Ethernet addressing, DHCP roles, Wi-Fi provisioning and recovery when a connection fails. Define user-visible states and diagnostic evidence as well as the successful connection path.
- Embedded Linux DHCP Client and Server Requirements
- Wi-Fi AP Provisioning Recovery: Design and Acceptance Tests
Bluetooth & BLE Development
Classic Bluetooth SPP, BLE GATT services and clients, notifications and reconnection. Radio roles and GATT client/server roles are separate design choices; define the application data contract explicitly.
- BLE GATT Design for UUIDs Data Formats Notifications and Version Compatibility
- Multi Sensor BLE Gateway Capacity and Reconnection Testing
- Reviewing AI-Assisted BLE Services and Clients: Bytes, Notifications and Reconnection
Industrial Protocols & Gateways
Serial and industrial data integration, gateway protocols and application-level buffering. Evaluate data ordering, duplicates and recovery independently of whether a network connection has been restored.
Qt, LVGL & Device Applications
Display, touch and device application integration with Qt or LVGL. Evaluate hardware resources, interaction requirements and maintenance responsibilities before selecting a GUI stack.
This area is included in the framework. Dedicated articles will be added when their technical scope and supporting material are ready. Related verification and delivery considerations also appear throughout the current guides.
Product Engineering & Delivery
Update and recovery design, production programming, diagnostics and project handover. Define deliverables, ownership, acceptance evidence and support boundaries in the project scope.
- MCU Firmware Outsourcing: What to Put in the Acceptance Requirements
- Reproducible Buildroot Delivery: From a Booting Image to a Release Kit
- Read-only Rootfs: Preserve Configuration, Logs and Update State Safely
- Industrial Gateway Offline Replay: Capacity, Order and Duplicates
Explore the AI-assisted engineering workflows
How to use the guides
These articles provide design guidance, illustrative workflows and acceptance checklists. Examples are not customer test reports, and a published checklist does not establish that a particular board meets it. Verify the stated software versions, hardware assumptions and interfaces against your own product. Keep logs and test conditions with the results so that another engineer can reproduce the conclusion.
Preparing a project discussion
Prepare the processor or module, current software stack, required interfaces, existing fault symptoms, and the intended development stage. Identify available schematics, source code and test access, and clarify what may be shared. These inputs help define development scope and acceptance work; they do not replace a project-specific assessment.