Robin Mueller
5d0f2837d1
Some checks failed
ci / Check build (pull_request) Has been cancelled
ci / Check formatting (pull_request) Has been cancelled
ci / Check Documentation Build (pull_request) Has been cancelled
ci / Clippy (pull_request) Has been cancelled
ci / Check build (push) Has been cancelled
ci / Check formatting (push) Has been cancelled
ci / Check Documentation Build (push) Has been cancelled
ci / Clippy (push) Has been cancelled
This PR introduces some major features while also changing the project structure to be more flexible for multiple platforms (e.g. host tooling). It also includes a lot of bugfixes, renamings for consistency purposes and dependency updates. Added features: 1. Pure Rust FSBL for the Zedboard. This first variant is simplistic. It is currently only capable of QSPI boot. It searches for a bitstream and ELF file inside the boot binary, flashes them and jumps to them. 2. QSPI flasher for the Zedboard. 3. DDR, QSPI, DEVC, private CPU timer and PLL configuration modules 3. Tooling to auto-generate board specific DDR and DDRIOB config parameters from the vendor provided ps7init.tcl file Changed project structure: 1. All target specific project are inside a dedicated workspace inside the `zynq` folder now. 2. All tool intended to be run on a host are inside a `tools` workspace 3. All other common projects are at the project root Major bugfixes: 1. SPI module: CPOL was not configured properly 2. Logger flush implementation was empty, implemented properly now.
32 lines
1.3 KiB
Rust
32 lines
1.3 KiB
Rust
//! This build script copies the `memory.x` file from the crate root into
|
|
//! a directory where the linker can always find it at build time.
|
|
//! For many projects this is optional, as the linker always searches the
|
|
//! project root directory -- wherever `Cargo.toml` is. However, if you
|
|
//! are using a workspace or have a more complicated build setup, this
|
|
//! build script becomes required. Additionally, by requesting that
|
|
//! Cargo re-run the build script whenever `memory.x` is changed,
|
|
//! updating `memory.x` ensures a rebuild of the application with the
|
|
//! new memory settings.
|
|
|
|
use std::env;
|
|
use std::fs::File;
|
|
use std::io::Write;
|
|
use std::path::PathBuf;
|
|
|
|
fn main() {
|
|
// Put `memory.x` in our output directory and ensure it's
|
|
// on the linker search path.
|
|
let out = &PathBuf::from(env::var_os("OUT_DIR").unwrap());
|
|
File::create(out.join("memory.x"))
|
|
.unwrap()
|
|
.write_all(include_bytes!("memory.x"))
|
|
.unwrap();
|
|
println!("cargo:rustc-link-search={}", out.display());
|
|
|
|
// By default, Cargo will re-run a build script whenever
|
|
// any file in the project changes. By specifying `memory.x`
|
|
// here, we ensure the build script is only re-run when
|
|
// `memory.x` is changed.
|
|
println!("cargo:rerun-if-changed=memory.x");
|
|
}
|