MKROM(1)

🎀 mkrom — the ROM-stuffing bestie 🎀

okay so real talk, this is mkrom(1) from the manual pages, and it's literally the tool that writes individual files into a ROM image. that's the whole vibe. 💅

✨ SYNOPSIS ✨

mkrom OUTPUT LENGTH FILES...

three things, bestie: where it goes, how big it is, and what goes in it. periodt.

💖 DESCRIPTION 💖

so FILES is a list of pairs, right? and each pair is a filename and an offset, joined together with a colon. the offset is literally the position where that input file gets dropped inside the OUTPUT file. iykyk. 🫶

then LENGTH decides how big OUTPUT is gonna be — like, the whole final size, no cap. before any of your input files get copied in, the whole thing is filled with 0xFF octets. every single byte. it's giving blank canvas but make it hex. ✨

🌸 EXAMPLES 🌸

mkrom example.rom 0x4000 temp1.bin:0x0 temp2.bin:0x200

so this one creates a 16KiB large ROM image out of two input files — one placed at offset 0 and the other at offset 512. cute, right? two little files living their best lives in one ROM. 🦋

👑 AUTHORS 👑

maintained by Drew DeVault <sir@cmpwn.com>, who is assisted by other open source contributors. iconic behavior tbh. 💜

if you wanna know more about mkrom development, the link is right here: https://github.com/KnightOS/mkrom — go be nosy, it's encouraged. 🔥

okay final sign-off: this page is from the MKROM(1) manual, dated 01/01/1980 — yeah, the date is a whole mood, don't come for it 😭 — and it's the MKROM(1) source/version you're reading. slay, bye! 🌈💖