Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
RusPiRo bare metal system development kit crate
This is the packaged crate combining different RusPiRo crates into one library. The library can be configured with feature gates
and allowes a more convinient usage pattern for the dependencies in your
Cargo.toml file. See the details and usage patterns
To use the crate just add the following dependency to your
Cargo.toml file. The components of the system development kit could be configured using feature gates. The available features are listed in the table below.
[dependencies] ruspiro-sdk = "0.2"
The always usable crates are:
||yes||Forwarded to the dependend crates to enable Raspberry Pi3 specific compilation, e.g. provide the proper base address for MMIO register.|
The following sections give some guidance how the
ruspiro-sdk might be utilized. Each scenario provides an example
that could be found in the sub-folders mentioned in the respective chapter. Those examples should build just fine and could
be used as starting point for your own projects.
Scenario 1: Minimal with built-in boot
This scenario is the proposed entry point in using the RusPiRo SDK the first time. In this scenario the
will be used with the set of default features only.
Find the whole crate structure here: Scenario-1
Scenario 1: Advanced! Minimal without built-in boot
This advanced scenario is intended for those who either already have their own boot assembly or do want to write their own one.
Additionally some other core requirements to successfully build a binary when not using the
ruspiro-boot need to be fulfilled:
provide a panic handler and a eh_personality function.
provide unwind stubs:
when using the
ruspiro-allocatorin this scenario the linker need to provide the two symbols:
indicating the physical memory address space of the heap.
Scenario 2: Using Uart/Console with built-in boot
This might be the most typical scenario to start with as it provides the functions to successfully initialize the Uart to be used as console output channel which makes "debugging" on the real hardware a bit easier. Find the whole crate structure here: Scenario-2