Use cases and solution mapping - Qualcomm Dragonwing Documentation

Maps common MCU use cases to recommended sample applications and highlights key integration considerations Use this mapping to quickly identify a starting point for your use case, reuse validated flows, and choose the right progression from basic interface bring-up to optimized paths such as GPI and low-power operation. Table 4-1 Use case mapping

Use case	Problem statement	Recommended sample application	Key consideration
Always-on sensor monitoring	Keep a sensor or event source local to the MCU so the host wakes only when a threshold or policy decision is met.	Always-on monitoring	Use event qualification, debounce, and lightweight local processing before you escalate.
Peripheral offload	Move peripheral work to the MCU when you need local control, lower host wake frequency, or tighter event response	UART logging or I2C sensor read	Bring up one protocol at a time. Add GPI only after the basic path is stable.
Event-driven wake handling	Wake the MCU on a timer, GPIO event, UART receive activity, or another valid source and service the event locally.	GPIO interrupt and wake	Define wake qualification, interrupt polarity, and worker handoff early.
Low-power optimization	Reduce dynamic power while keeping wake and resume behavior predictable.	Low-power mode and wake-up	Validate the active protocol path before and after the transition
Autonomous mission mode	Keep repetitive policydriven work on the MCU without continuous host supervision.	Always-on monitoring	Make the host escalation rule explicit.