mcuboot-integrationlisted

# MCUboot Integration ## Overview Use this skill to integrate MCUboot by proving the boot chain, flash map, image format, signing flow, and upgrade policy. Most failures come from slot geometry, trailer layout, or signing metadata mismatches rather than the application itself. ## When To Use Use this skill when: - The user wants to add MCUboot to Zephyr, Mynewt, NuttX, RIOT, Mbed OS, ESP-IDF, or a custom MCU platform. - The issue involves image validation, swap, overwrite-only upgrade, rollback, confirm flags, serial recovery, or signed images. - The project has dual slots, external flash, encrypted images, secure boot, or OTA requirements. Do not use this skill for application-level firmware transfer alone. Use `ota-update-integration` first if the bootloader is already fixed and the issue is delivery. For generic bootloader jump/handoff debugging, use `bootloader-debug`. ## First Questions Ask for: - MCU/SoC, SDK/RTOS, boot flow, and current bootloader ownership. - Flash layout: bootloader, primary slot, secondary slot, scratch, trailer, and external flash if used. - Upgrade mode: swap, overwrite-only, direct-XIP, RAM-load, or serial recovery. - Image signing method, key type, image version, and whether rollback prevention is needed. - Current symptom and boot log from the bootloader. ## Integration Checklist 1. Freeze the flash map. Slot sizes, erase block size, alignment, scratch size, and trailer offsets must match the target flash. 1. Build a minimal sign