Skip to content

A simple program that links your executables created using the rust bootloader_api crate with the actual bootloader.

Notifications You must be signed in to change notification settings

mysteriouslyseeing/bootloader_linker

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

13 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

bootloader-linker

A simple program that links your executables created using the bootloader_api crate with the actual bootloader crate into a disk image. Also capable of running disk images using qemu.

bootloader_linker -V
bootloader_linker 0.1.6 using bootloader 0.11.6

Installation

Installation can be done directly via cargo. You will need a nightly compiler with the llvm-tools-preview and rust-src components:

rustup component add llvm-tools-preview
rustup component add rust-src
cargo install bootloader_linker

Usage

bootloader_linker -h
A simple program that links your executables created using bootloader_api with the actual bootloader.

Usage: bootloader_linker [OPTIONS] <COMMAND> <INPUT_FILE> [EXTRA_ARGS]...

Arguments:
  <COMMAND>        [possible values: build, run, build-run]
  <INPUT_FILE>     The binary/.img file to operate on
  [EXTRA_ARGS]...  Extra args to pass to qemu

Options:
  -u, --uefi
          Sets the loader to use uefi instead of bios
  -o, --out-dir <OUT_DIR>
          The directory to put output files in. Ignored if not building a disk image [default: ./]
  -q, --qemu-path <QEMU_PATH>
          The name of the qemu executable. Ignored if not running a disk image [default: qemu-system-x86_64]
  -m, --mount-file <FILES_TO_MOUNT>
          Extra files to mount to the FAT filesystem
  -H, --min_height <MINIMUM_FRAMEBUFFER_HEIGHT>
          Specifies the minimum frame buffer height desired. If it is not possible, the bootloader will fall back to a smaller format
  -W, --min_width <MINIMUM_FRAMEBUFFER_WIDTH>
          Specifies the minimum frame buffer width desired. If it is not possible, the bootloader will fall back to a smaller format
  -l, --log-level <LOG_LEVEL>
          The minimum level of logging to still display [default: trace] [possible values: off, trace, debug, info, warn, error]
  -f, --frame_logging
          Whether the bootloader should print log messages to the framebuffer during boot
  -s, --serial_logging
          Whether the bootloader should print log messages to the serial port during boot
  -a, --args <ARGS>
          Extra args to pass to qemu. You can also put them after -- at the end of the command
  -h, --help
          Print help (see more with '--help')
  -V, --version
          Print version

Please note that in order to run the disk image you need to have qemu installed. If the executable is not in PATH, you can specify it with --qemu-path

Examples

bootloader_linker build-run test_binary -o ./target -- -serial stdio
// Bootloader booting info...
Hello world!

The test binary used to create this output is in the repo and was built from source code that looks like this for the x86_64-unknown-none target:

#![no_std]
#![no_main]

use core::panic::PanicInfo;

use bootloader_api::entry_point;

entry_point!(main);

fn main(_info: &'static mut bootloader_api::BootInfo) -> ! {
    qemu_print::qemu_print!("Hello world!");
    loop {}
}

#[panic_handler]
fn panic(_info: &PanicInfo) -> ! {
    loop {}
}

qemu_print crate

There are also short-hands for the three subcommands:

  • build can be shortened to b
  • run can be shortened to r
  • build-run can be shortened to br

Advanced use

Use with cargo run

bootloader-linker is suitable for use with cargo run. Add these lines to your .cargo/config.toml:

[target.'cfg(target_os = "none")']
runner = ["bootloader_linker", "br", "-o", "./target", "-u"]

Now, cargo run will invoke bootloader_linker instead of trying to run the executable directly.

If you want to pass extra args to qemu, you cannot use the normal notation with --, as cargo will place the extra arguments before the binary. So, for example,

runner = ["bootloader_linker", "br", "--", "-serial", "stdio"]

would result in the command

bootloader_linker br -- -serial stdio [BINARY]

which does not work.

If you want to pass in extra args, you will have to use the -a argument to pass them in one at a time:

bootloader_linker br -a"-serial" -a"stdio" [BINARY]

So therefore, your runner field should look like this:

runner = ["bootloader_linker", "br", "-o", "./target", "-u", "-a'-serial'", "-a'stdio'"]

You can remove the quotes too if your extra argument does not contain spaces:

runner = ["bootloader_linker", "br", "-o", "./target", "-u", "-a-serial", "-astdio"]

Mounting extra files

If you need other files mounted to the .img filesystem, specify them with --mount-file (or -m):

bootloader_linker br [BINARY] --mount-file [FILE] -u -o ./target

If you need multiple files mounted, include the argument multiple times:

bootloader_linker br [BINARY] --mount-file [FILE_A] --mount-file [FILE_B] -u -o ./target

Reporting bugs

This command-line utility has not been tested extensively. If you have any issues, report them in an issue on the github repo.

About

A simple program that links your executables created using the rust bootloader_api crate with the actual bootloader.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages