bk7252-cam

Use when testing a hardware hypothesis on the real BK7252 chip — register behaviour, peripheral interaction, driver correctness. Triggers on "test this on chip", "verify on hardware", "check what this register does", "probe this peripheral", "let me see on real hardware", or any task requiring autonomous write→build→flash→capture→iterate in src/tests/probe/.

Use when asked to commit a named JetBrains IDE changelist or stage files from a specific changelist. Reads .idea/workspace.xml to find which files belong to that changelist.

Use when generating a new MMIO register header for a BK7252 driver from vendor SDK source, or when explicitly asked to refactor an existing header in this project to the canonical style. Triggers on phrases like "generate a register header for <block>", "translate this SDK fragment into a register header", "make a register header from this", "bring `soc/<block>.h` to canon", "rewrite this SDK fragment to canon". Also use when the user pastes a Beken SDK fragment that contains `_POSI` / `_MASK` macros, `(1UL << N)` constants, and a base-address `#define` — that's the input shape.

Use when reading or navigating Beken SDK source code for the BK7252 project — resolving CFG_SOC_NAME preprocessor guards, identifying which SDK branches apply to this chip, finding register definitions, or understanding SDK encoding conventions. Triggers on: pasted SDK fragments with #if CFG_SOC_NAME guards, questions about which chip variant a code block applies to, "which branch should I use", "does this apply to our chip", "where is X defined in the SDK", or any task that requires interpreting beken_freertos_sdk source before porting or translating it.

Use when an implementation attempt has failed and you want to preserve knowledge before stopping work. Triggers on: "implementation failed", "park this branch", "dead end", "stop this direction".

Write hardware-block reference documentation for chips where the vendor datasheet is missing, incomplete, or wrong - the kind of document the vendor should have written but didn't. Use whenever the user wants to document a peripheral, security block, DMA controller, sensor interface, or any other on-chip hardware unit. Triggers on phrases like "write documentation for this hardware block", "document the registers", "make a hardware reference", "describe how this peripheral works", "reverse-engineered documentation", "turn my notes into a hardware doc", or when the user shares register-level details about a chip and asks for them to be written up. Use this even if the user just says "write a README for the X block" - the right output is a hardware reference, not a project README.