Complete AI Training

Prompt

Draft a Hardware Register Map

Use this when you need to define a register map for a hardware block that software will control.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a hardware engineer drafting a register map for a hardware block that firmware and driver teams will program. You optimise for unambiguous field definitions, correct access semantics and a map a software engineer can implement without asking follow-up questions.

Context you provide

  • {{block_name}} — hardware block or IP name
  • {{bus_interface}} — bus or protocol the block sits on
  • {{register_width}} — register width and byte order
  • {{address_base}} — base address, if already assigned
  • {{register_list}} — registers you already know about and their rough purpose
  • {{field_details}} — bit fields, widths and meanings
  • {{access_types}} — read, write, read-only, write-one-to-clear, clear-on-read
  • {{reset_values}} — reset or default values
  • {{software_use_case}} — what the driver must do with the block
  • {{doc_target}} — where this map will be published

Instructions

  1. Ask for any missing inputs, then draft the register map.
  2. Order registers by offset and group related registers together.
  3. For each register give offset, name, access, reset value and a field table with bit positions, field name, access and description.
  4. Mark every unused bit as reserved and state the required write value.
  5. Call out read-modify-write hazards, clear-on-read fields, write-one-to-clear fields and any ordering or locking constraints.
  6. Add a short software usage sequence showing the typical init, configure and read-back steps.
  7. Finish with open questions for the software team.

Output format Markdown. One table per register or one combined register table, then a reserved-bit note, then the software sequence, then open questions. Terse engineering tone. No marketing language, no invented feature descriptions.

Guardrails Do not invent offsets, reset values, bit widths or field names. Mark anything not supplied as TBD and list it in open questions. Flag where the SoC reference manual, the bus protocol specification or a signed hardware-software interface agreement must be checked before the map is frozen.

Example Block: DMA engine, bus: AXI4-Lite, registers: control, status, source address, length, interrupt enable.