Bare-metal target for any cpu in the ARMv4T architecture family, supporting
ARM/Thumb code interworking (aka
t32), with ARM code as the default code
In particular this supports the Gameboy Advance (GBA), but there's nothing GBA specific with this target, so any ARMv4T device should work fine.
The target is cross-compiled, and uses static linking.
This target doesn't provide a linker script, you'll need to bring your own
according to the specific device you want to target. Pass
-Clink-arg=-Tyour_script.ld as a rustc argument to make the linker use
your_script.ld during linking.
Because it is Tier 3, rust does not yet ship pre-compiled artifacts for this target.
Just use the
build-std nightly cargo feature to build the
core library. You
can pass this as a command line argument to cargo, or your
file might include the following lines:
[unstable] build-std = ["core"]
core should work as expected, with the following notes:
- the target is "soft float", so
f64operations are emulated in software.
- integer division is also emulated in software.
- the target is old enough that it doesn't have atomic instructions.
Rust programs are output as ELF files.
For running on hardware, you'll generally need to extract the "raw" program code
out of the ELF and into a file of its own. The
objcopy program provided as
part of the GNU Binutils can do this:
arm-none-eabi-objcopy --output-target binary [in_file] [out_file]
This is a cross-compiled target that you will need to emulate during testing.
Because this is a device-agnostic target, and the exact emulator that you'll need depends on the specific device you want to run your code on.
For example, when programming for the Gameboy Advance, the
mgba-test-runner program could be used to make a
normal set of rust tests be run within the