DRTIO port - satman firmware #136
No reviewers
Labels
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: M-Labs/artiq-zynq#136
Loading…
Reference in New Issue
No description provided.
Delete Branch "mwojcik/artiq-zynq:drtio_satman"
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?
This is a part of few pull requests for DRTIO functionality. They have been broken up to allow easier code review overall. They're identical in contents to drtio_port branch.
This PR includes satman firmware ported from mainline ARTIQ, stripped down because most of the peripherals are currently not available on Zynq.
Any feedback and suggestions are welcome.
@ -0,0 +34,4 @@
pub const RAW_DDMTD_N: i32 = 1 << RAW_DDMTD_N_SHIFT;
pub const DDMTD_DITHER_BITS: i32 = 1;
pub const DDMTD_N_SHIFT: i32 = RAW_DDMTD_N_SHIFT + DDMTD_DITHER_BITS;
pub const DDMTD_N: i32 = 1 << DDMTD_N_SHIFT;
Remove this entire file, we don't support Sayma stuff on Zynq.
@ -0,0 +83,4 @@
. += 0x100;
__irq_stack0_start = .;
} > SDRAM
}
Can this file be shared with runtime?
Turns out it can, it's pulled from runtime now.
@ -0,0 +52,4 @@
. += 0x10000;
_fstack = . - 4;
} > main_ram
}
Can this file be shared with runtime?
@ -0,0 +311,4 @@
&drtioaux::Packet::SpiReadReply { succeeded: false, data: 0 })
}
drtioaux::Packet::JdacBasicRequest { destination: _destination, dacno: _dacno,
Remove
You can also remove
Packet::Jdac*
fromdrtioaux
.Is Jdac stuff then unsupported on all platforms? I imagine that it could be forwarded to a mainline artiq-based satellite that does have ad9154. Or is mixing satellites not supported?
Not supported.
@ -0,0 +10,4 @@
let out = &PathBuf::from(env::var_os("OUT_DIR").unwrap());
File::create(out.join("link.x"))
.unwrap()
.write_all(include_bytes!("../runtime/link.x"))
These files do not belong specifically to the runtime. Put them in their own folder?
libbuild_zynq
seems a proper candidate with shared build code, maybe? Or alinker
folder, with just the linker script inside?libbuild_zynq
would be ok I think.