ebaz4205 support #116
Loading…
Reference in New Issue
No description provided.
Delete Branch "newell/zynq-rs:ebaz4205"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Add support for EBAZ4205 board.
@ -156,4 +165,0 @@
#[cfg(any(feature = "target_coraz7", feature = "target_kasli_soc"))]
let data1_config = slcr::DdriobConfig::zeroed()
.pullup_en(true);
#[cfg(feature = "target_redpitaya")]
Why was this removed and Red Pitaya dumped together even though it had a different configuration?
Nevermind, I see it's an oversight and duplicated code. 👍
@ -15,0 +13,4 @@
ArmPll = 0b010,
DdrPll = 0b011,
// Ethernet controller 0 EMIO clock
EMIO = 0b100,
Emio
rather thanEMIO
for consistent style.18b569d9aa
tof2eebf44e9
Did you manage to get
experiments
orszl
running on it?Yes,
szl
builds and runs fine. The main thing to be aware of is that to use Ethernet you need to load the gateware since it is via EMIO. I have rust-ebaz4205 where I built a simple blinky led firmware and also tested the Ethernet.For
experiments
it works up to the point that it tries to use Ethernet and panics since you need to load the gateware to be able to communicate with the PHY.@ -7,7 +7,7 @@
outputs = { self, nixpkgs, mozilla-overlay }:
let
pkgs = import nixpkgs { system = "x86_64-linux"; overlays = [ (import mozilla-overlay) crosspkgs-overlay ]; };
Could you clean up the diff and remove all these whitespace changes?
That one must have been by accident.
Are you also wanting the trailing whitespace changes to be reverted? The trailing ones were from my VS Code extension (rust-analyzer) formatting. In the event you don't mind those changes I could do that in a follow up PR to partition the diff better.
Ideally we should just run nixfmt/rustfmt and get rid of all of them in one go, should be in separate PR and individual unrelated diffs should be clean though.
Including trailing whitespaces.
Since one of the main uses of szl is netboot, the Ethernet behavior is rather annoying. Maybe load minimal gateware (could hopefully be built with the open tools like openxc7)? Hopefully with bitstream "compression" it won't overflow the OCM. This is somewhat complicated and best addressed later, though.
Yeah, this one of the pains I had because I wasn't able to use artiq_netboot (etc.) to netboot and was having to swap my SD card back and forth (I could have probably used openocd for all the steps and will investigate that more later).
ebaz4205 supportto WIP: ebaz4205 supportWIP: ebaz4205 supportto ebaz4205 supportDoes it mean that the openocd/JTAG has some issues, or have you not tried it yet?
No, I was able to use openocd via JTAG without issue (tested with szl). What I was referring to is that when I was testing my firmware I was using my SD card via mkbootimage but it would have probably been easier if I had just loaded szl, bitstream, and the firmware all via openocd rather than doing it via my SD card each time. I just hadn't taken the time to write a script to do all three.
ebaz4205 supportto WIP: ebaz4205 supportWIP: ebaz4205 supportto ebaz4205 support