cmsis-dsp-integration

CMSIS-DSP Integration

Overview

Use this skill to integrate CMSIS-DSP by matching the target core, FPU/DSP extensions, data type, scaling, and buffer alignment. DSP bugs often come from numeric format and build flags rather than function calls.

When To Use

Use this skill when:

• The user wants CMSIS-DSP or ARM math functions on Cortex-M or Cortex-A/R targets.
• The task involves FFT, FIR/IIR filters, matrix math, statistics, PID, Q15/Q31/f32, or optimized vector operations.
• Results are wrong, saturated, NaN, too slow, or differ from desktop reference output.

Do not use this skill for TinyML inference runtime integration. Use tinymaix-integration or ML-specific skills instead.

First Questions

Ask for:

• MCU/core, FPU/DSP extension, compiler, and build flags.
• CMSIS-DSP version and how it is included.
• Function family and data type: f32, f16, q7, q15, q31, or mixed.
• Input range, expected output, reference data, and buffer sizes.
• Whether performance, code size, or accuracy is the primary goal.

Integration Checklist

1. Match core flags. Compiler options must match FPU, ABI, and DSP extensions.

2. Choose numeric format deliberately. Fixed-point Q formats need scaling, saturation, and headroom analysis.

3. Validate buffers. FFT/filter/state buffers must be sized and aligned as required.

4. Compare with golden vectors. Use known input/output before live sensor data.

5. Measure performance on target. Desktop estimates do not prove MCU timing.

Common Failures

• FPU ABI mismatch between objects.
• Q15/Q31 overflow from missing scaling.
• FFT length or bit-reversal config wrong.
• Filter state buffer too small.
• Cache/DMA buffer incoherency around ADC/audio data.
• Reference output uses different normalization.

Verification

Before claiming CMSIS-DSP works:

• State core, build flags, data type, function, and buffer sizes.
• Confirm golden-vector output within tolerance.
• Confirm no saturation/NaN unless expected.
• Report runtime cycles/time if performance is in scope.