Board safety

Each board has its own safety level. Start with setup-full when device support is available.

Level	What it checks	Best for
no-setup	No memory-map checks or board identity proof. Uses raw access.	Experts who accept responsibility for addresses and destructive actions.
setup-lite	Limits guarded operations to regions and capabilities you confirm from the datasheet. Trusts your board selection.	A smaller, manually reviewed setup.
setup-full	Uses verified device support, a derived memory map, and live identity checks. Blocks raw access.	Work that needs stronger server checks.

Guarded operations check the configured limits before acting. Raw operations bypass those checks. Lite setup still allows raw access; the agent must tell you when it uses it.

Choose a level

Tell the agent which level to use:

Set up my sensor board using setup-full.

For lite or full setup, supply the exact MCU and official datasheet PDF. Lite asks you to confirm memory regions and permissions. Full resolves device support and checks the connected hardware. The identity result may prove the exact device or only a compatible core; the agent should report which.

New boards begin at no-setup. You can ask to move to lite or full later. Returning a configured board to raw access requires the downgrade skill.

What the checks cover

• Guarded reads and writes stay within allowed memory regions.
• Flashing checks the image, destination, and sectors it will erase.
• Application and bootloader flashing have separate permissions.
• Mass erase requires a supported recovery method and your explicit authorization after a data-loss explanation.

Full setup does not enable every operation. Flashing needs a defined application area; bootloader access and recovery need separate support. A generic debug connection may allow inspection without allowing flash programming.

These checks do not prove that firmware or register writes will behave correctly. Test the result.

After reconnecting

Saved setup remains, but full boards need fresh live validation. Plans and permissions are temporary; a server restart also clears manual approvals. Ask the agent to show the current safety level and available operations.

If setup fails, follow the reported fix. It does not automatically authorize raw access. See Board families for device requirements.