Skip to main content
skill CX Codex

baremetal-startup — Claude Code skill: what it does, how to install

baremetal-startup is a Claude Code skill that guides coding agents through Cortex-M and RISC-V initialization from reset to main().

MIT 394 installs ★ 298 updated 2026-06-27

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add mohitmishra786/low-level-dev-skills --skill baremetal-startup -a claude-code
Open on GitHub

What baremetal-startup does

The skill provides step-by-step guidance for writing minimal startup.s, entry.S, and crt0 routines. It covers vector table definitions, setting up the initial stack pointer via _estack, copying .data from flash to RAM, and zeroing the .bss section before calling main().

It also details linker symbol integration and vector table relocation with SCB->VTOR. Without proper address alignment required by ARM specifications, setting VTOR after a bootloader jump will break interrupt handlers.

The reference addresses typical boot crashes: immediate HardFault from invalid stack pointers, corrupted global variables, calling C++ static constructors prior to clock configuration, and missing while(1) or WFI loops if main() terminates.

What it helps with

  • write a minimal Cortex-M startup.s or Reset_Handler
  • configure .data copying and .bss clearing before entering main()
  • relocate the vector table using SCB->VTOR after a bootloader jump
  • fix boot-time HardFault exceptions and stack pointer errors

Example prompts for the agent

  • /baremetal-startup My STM32 never reaches main — what should Reset_Handler do?
  • /baremetal-startup How do I relocate the vector table after bootloader jump?
  • /baremetal-startup Generate a minimal RISC-V assembly entry point clearing bss

How to install baremetal-startup

1Skills CLI (Vercel)

npx skills add mohitmishra786/low-level-dev-skills --skill baremetal-startup -a claude-code

2Manually: put the files in place

~/.claude/skills/baremetal-startup/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/baremetal-startup/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about baremetal-startup

How do I install baremetal-startup in Claude Code?

Run npx skills add mohitmishra786/low-level-dev-skills --skill baremetal-startup -a claude-code in your terminal.

What does the baremetal-startup skill do?

It instructs agents on bare-metal MCU initialization from hardware reset to main(), covering vector tables, memory sections, and runtime bring-up.

Why does firmware hit a HardFault before reaching main?

This typically happens when vector zero contains an invalid stack pointer address pointing outside valid RAM.

Source text

SKILL.md · MIT
---
name: baremetal-startup
description: Bare-metal startup skill for reset-to-main bring-up. Use when writing startup code, vector tables, .data/.bss init, stack setup, or crt0 for Cortex-M/RISC-V. Activates on queries about reset vector, VTOR, startup.s, bss init, or bare-metal entry point.
---

# Bare-Metal Startup

## Purpose

Guide agents through bare-metal startup from reset to `main()`: reset and exception vectors, `.data`/`.bss` initialization, stack and heap setup, C runtime integration with linker scripts, and common Cortex-M and RISC-V bring-up bugs.

## When to Use

- Firmware hangs before reaching `main()`
- Porting to a new MCU without vendor HAL
- Writing custom `startup.s` or `Reset_Handler`
- Integrating with `skills/embedded/linker-scripts`
- Debugging uninitialized globals or stack overflows at boot

## Workflow

### 1. Boot sequence mental model

```
Power-on / reset
├── CPU loads SP from vector[0]
├── CPU branches to Reset_Handler from vector[1]
├── Reset_Handler: init clocks (optional), copy .data, zero .bss
├── Configure stack pointer (if not already from vector)
├── Call SystemInit() / platform_init()
└── Call main() — must not return (loop or WFI)
```

### 2. Cortex-M vector table

On Cortex-M, the vector table starts at address 0 or a relocatable base (VTOR):

| Index | Entry |
|-------|-------|
| 0 | Initial stack pointer (`_estack`) |
| 1 | `Reset_Handler` |
| 2 | `NMI_Handler` |
| 3 | `HardFault_Handler` |
| 4+ | IRQ handlers per NVIC |

```asm
/* startup.s — minimal Cortex-M */
.syntax unified
.thumb

.section .isr_vector,"a",%progbits
.global g_pfnVectors
g_pfnVectors:
    .word _estack
    .word Reset_Handler
    .word NMI_Handler
    .word HardFault_Handler
    /* ... device IRQ vectors from vendor CMSIS ... */

.section .text.Reset_Handler
.thumb_func
.global Reset_Handler
Reset_Handler:
    ldr r0, =_sidata    /* .data load address (LMA) */
    ldr r1, =_sdata     /* .data VMA start */
    ldr r2, =_edata
    b LoopCopyDataInit
CopyDataInit:
    ldr r3, [r0], #4
    str r3, [r1], #4
LoopCopyDataInit:
    cmp r1, r2
    blt CopyDataInit
    ldr r2, =_sbss
    ldr r4, =_ebss
    movs r3, #0
    b LoopFillZerobss
FillZerobss:
    str r3, [r2], #4
LoopFillZerobss:
    cmp r2, r4
    blt FillZerobss
    bl SystemInit
    bl main
    b .
```

```c
/* Linker symbols — declared extern in startup */
extern uint32_t _estack, _sidata, _sdata, _edata, _sbss, _ebss;
```

### 3. VTOR relocation (Cortex-M)

```c
#include "core_cm4.h"  /* CMSIS */

void relocate_vector_table(uint32_t base) {
    SCB->VTOR = base & 0xFFFFFF80U;  /* must be aligned per ARM ref manual */
    __DSB();
    __ISB();
}
```

Bootloader jumping to app often requires setting VTOR to the application's vector table address (e.g., `0x08020000` on STM32 flash).

### 4. RISC-V startup (overview)

```asm
/* entry.S — simplified */
.section .text.entry
.global _start
_start:
    la sp, _stack_top
    la t0, _bss_start
    la t1, _bss_end
clear_bss:
    beq t0, t1, bss_done
    sw zero, 0(t0)
    addi t0, t0, 4
    j clear_bss
bss_done:
    call main
    j .
```

Trap vector: `mtvec` for M-mode; see `skills/platform/riscv-privileged`.

### 5. crt0 responsibilities

| Task | Who does it |
|------|-------------|
| Copy `.data` LMA→VMA | `Reset_Handler` / crt0 |
| Zero `.bss` | `Reset_Handler` |
| Init stack | Vector[0] or explicit `sp` |
| Heap (`_sbrk`) | Optional; libc or custom |
| C++ constructors | `__libc_init_array()` if using full libc |
| FPU enable | `SystemInit` on Cortex-M4F/M7 |

### 6. Linker script integration

```ld
_estack = ORIGIN(RAM) + LENGTH(RAM);
_sidata = LOADADDR(.data);
```

Cross-link `skills/embedded/linker-scripts` for MEMORY/SECTIONS layout.

### 7. Agent usage examples

```
/baremetal-startup My STM32 never reaches main — what should Reset_Handler do?
/baremetal-startup How do I relocate the vector table after bootloader jump?
```

## Common Problems

| Symptom | Cause | Fix |
|---------|-------|-----|
| HardFault immediately | Stack pointer invalid | Set `_estack` to valid RAM top |
| Globals wrong at boot | `.data` not copied | Copy LMA→VMA in Reset_Handler |
| BSS non-zero | `.bss` not zeroed | Add bss clear loop |
| IRQs don't fire | VTOR points to wrong table | `SCB->VTOR = app_vector_addr` |
| `main` returns into garbage | No loop after main | `while(1)` or `WFI` loop |
| C++ static init crash | Constructors before clocks | Call `SystemInit` first |

## Related Skills

- `skills/embedded/linker-scripts` — `_estack`, LMA/VMA, section placement
- `skills/baremetal/interrupts-and-exceptions-baremetal` — vector table IRQ entries
- `skills/baremetal/bootloaders-embedded` — VTOR relocation on app jump
- `skills/embedded/openocd-jtag` — halt at `Reset_Handler` with GDB
- `skills/low-level-programming/assembly-arm` — Thumb-2 syntax
- `skills/platform/riscv-privileged` — RISC-V trap setup

© mohitmishra786 · MIT · mohitmishra786/low-level-dev-skills

Similar skills

All skills for Programming languages →

From the same set140

The whole set →
low-power-embedded low-power-embedded — a skill for configuring MCU low-power modes: sleep, stop, standby, peripheral clock gating, and wake-up sources. Activates on questions about WFI, STOP mode, STM32 PWR, nRF sleep, or reducing firmware power draw. CX Codex +1 397installs bootloaders-embedded bootloaders-embedded is a skill for Cortex-M bootloader development. It covers image validation, safe handoff to an app, vector table relocation, and updates over UART or USB DFU. CX Codex +1 395installs kernel-debugging This Claude Code skill guides Linux kernel debugging with tracing, debuggers, and crash-dump analysis. It activates for questions about kgdb, kdb, ftrace, kprobes, dyndbg, kdump, or dmesg levels. CX Codex +1 395installs qemu-kvm qemu-kvm walks the agent through QEMU VMs with KVM acceleration: flags, virtio devices, VFIO passthrough and booting custom kernels. CX Codex +1 395installs mmio-and-bit-manipulation mmio-and-bit-manipulation — a skill for safe peripheral memory access: volatile semantics, read-modify-write patterns, bit masks, and alignment. Essential when writing bare-metal drivers without a HAL. CX Codex +1 392installs dma-baremetal dma-baremetal is a Claude Code skill that assists with register-level DMA setup for bare-metal microcontrollers, moving UART, SPI, or ADC data away from the CPU. CX Codex +1 392installs bus-drivers-i2c-spi bus-drivers-i2c-spi walks an agent through Linux client drivers for I2C and SPI sensors and PMICs: registration, regmap, device tree binding. CX Codex +1 392installs uart-serial-baremetal uart-serial-baremetal configures bare-metal UART and USART drivers for serial debug consoles, baud calculation, and interrupt I/O. CX Codex +1 391installs

Project sponsors

Companies that keep this analytics open