Files

T

Claude 4742cf8b3b boards(BRINGUP): the SER5 bench steps for the plug-and-play stick and the real Zuse (#92 , Task 5 step 6) [skip ci]

First boot (genesis, growth, the time to the prompt), the second boot, MINT-ZUSE onto a second stick, the system stick alone (the fixed screen), both sticks at power-on -- each rehearsed first in QEMU by the qemu_session.py mode named. 3.2's 'boots headless' corrected: the stick's first boot now mints its Zuse.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GE3SDvQn5EoxdGufk84zz2

2026-11-10 07:05:11 +00:00

milkv

chore(license): an SPDX header on every source file that had none (LicenseRef-Starship-1.0) [skip ci]

2026-11-10 04:12:49 +00:00

chore(license): an SPDX header on every source file that had none (LicenseRef-Starship-1.0) [skip ci]

2026-11-10 04:12:49 +00:00

raspi

chore(license): an SPDX header on every source file that had none (LicenseRef-Starship-1.0) [skip ci]

2026-11-10 04:12:49 +00:00

zynq7020

chore(license): an SPDX header on every source file that had none (LicenseRef-Starship-1.0) [skip ci]

2026-11-10 04:12:49 +00:00

BRINGUP.md

boards(BRINGUP): the SER5 bench steps for the plug-and-play stick and the real Zuse (#92 , Task 5 step 6) [skip ci]

2026-11-10 07:05:11 +00:00

README.md

boards: the amd64 target is PC -- a generic x86-64 UEFI PC, not the SER5

2026-10-14 17:22:32 -04:00

README.md

boards/

One directory per physical target. make boot_image TARGET=<NAME> (repo root) maps the name to a directory here, reads its board.mk, and builds the single file that goes on that board's boot medium into build/boards/<board>/.

TARGET	Directory	ISA	Boot path	Image
`PC`	`pc/`	amd64	UEFI firmware, removable-media path -- any x86-64 PC	GPT + FAT32 ESP: `EFI/BOOT/BOOTX64.EFI`
`RASPI`	`raspi/`	aarch64	Pi 5 EEPROM firmware, native	MBR + FAT32: `config.txt`, `kernel_2712.img`, `bcm2712-rpi-5-b.dtb`
`MILKV`	`milkv/`	riscv64	SPI-flash U-Boot + OpenSBI, `bootefi`	GPT + FAT32 ESP: `EFI/BOOT/BOOTRISCV64.EFI`
`ZYNQ7020`	`zynq7020/`	armv7	BootROM, `BOOT.BIN`, U-Boot	not yet: needs `kernel/src/arch/armv7`

board.mk sets:

BOARD_DESC: one-line description (make boards)
BOARD_ARCH: kernel ISA (kernel/src/arch/<arch>)
BOARD_BOOT: image recipe in kernel/Makefile (uefi-esp, rpi-native, ...)
BOARD_IMAGE: output file name

Disk images are assembled by scripts/mkdiskimage.sh, which needs no root access and no loop devices. KERNEL_ARGS="..." is written as starforth.cfg (UEFI boards) or cmdline.txt (Pi 5, where the firmware copies it into /chosen/bootargs). BOOT_IMAGE_SIZE_MIB sets the image size; the default is 128.

Hardware status: none of these images has been booted on real silicon from this build. The PC image has been booted in QEMU (q35 + OVMF, from its own disk) through POST. (PC was named SER5 until 2026-10-14, after the first PC on the bench; the image was never specific to it.) The Pi 5 native path (raspi/README.md) and the JH7110 peripherals have still only been checked by compiling.