Files
LithosAnanake/boards
rajamesandClaude Opus 5.5 9772ee8b68 fix(repl): the bring-up build's prompt waits for a line instead of answering itself without end
Built with EMERGENCY_CONSOLE_ENABLED=1 and booted with no identity logged
in, the prompt printed "ok>  ok" without end, 1.4 million times in 200
seconds (logs/20261013-210442).  sk_console_readline() gave up at once
whenever no identity was present.  The production build answers that by
going silent until a login; the bring-up build, which needs no login,
took it as an empty line and asked again.  The give-up is now the
production build's only.

Found rehearsing boards/BRINGUP.md; it predates the console change of
c9519173 (the image built from the commit before that did the same).

The riscv64 bring-up build, no thumbdrive, three lines typed
(logs/20261013-235129): one prompt that waits, and 3, 56 and 81.
Acceptance of the production build, one QEMU at a time: amd64
(-235255), aarch64 (-235411), riscv64 (-235620) to the zuse prompt, no
unknown word, hash 0x08873e0f44b7cb2a on all three.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-13 23:57:29 -04:00
..

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
SER5 ser5/ amd64 UEFI firmware, removable-media path 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 SER5 image has been booted in QEMU (q35 + OVMF, from its own disk) through POST. The Pi 5 native path (raspi/README.md) and the JH7110 peripherals have still only been checked by compiling.