Add ebaz4205 support #327
No reviewers
Labels
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: M-Labs/artiq-zynq#327
Loading…
Reference in New Issue
No description provided.
Delete Branch "newell/artiq-zynq: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 to
artiq-zynq
forEBAZ4205
.Testing:
Note:
artiq_coreanalyzer -p
shows the GPIO toggling but I have not been able to get it to view in the waveform viewer of the dashboard.@ -0,0 +87,4 @@
platform.add_extension(_ps)
platform.add_extension(_ddr)
## Uncomment if your EBAZ4205 doesn't have a PHY XTAL
This should be a commandline option (e.g.
--no-xtal
), rather than uncommentingYes, agreed. This board is known to come in different variants on the 2nd hand market and I don't feel like removing the xtal to test things as my board has the xtal populated. I will remove this commented out code and leave the commandline option for a possible future branch.
Fair enough, don't add anything that's not been tested either.
Add ebaz4205 supportto WIP: Add ebaz4205 supportWIP: Add ebaz4205 supportto Add ebaz4205 support@ -115,2 +121,4 @@
api!(i2c_write = i2c::write),
#[cfg(not(feature = "target_ebaz4205"))]
api!(i2c_read = i2c::read),
#[cfg(not(feature = "target_ebaz4205"))]
Might be simpler to either (1) add a dummy module with I2C functions that always return error/false, or (2) dedicate two I/O pins on the board to I2C since many use cases will want it anyway.
I am open to either option. Note that if I did go with (2), dedicating two I/O pins, I would need to update
zynq-rs
for this as well. What do you deem the better option?Another
zynq-rs
update is not a problem, but if it's too contrived, you may go with dummies for now and add I2C support later.@ -0,0 +211,4 @@
parser.add_argument(
"-g", default=None, help="build gateware into the specified directory"
)
parser.add_argument("--rtio_clk", default=100e6, help="RTIO Clock Frequency (Hz)")
125MHz would be a more sensible default.
And I think most other programs use - not _ in command line arguments.
Add ebaz4205 supportto WIP: Add ebaz4205 supportWIP: Add ebaz4205 supportto Add ebaz4205 support