consolidate all write..file()
into config.py
and update zc706.py
to follow artiq repo
#260
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#260
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "morgan/artiq-zynq:zc_cfg_fix"
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?
Sumamary
write_csr_file()
,write_mem_file()
&write_rustc_cfg_file()
fromkasli_soc.py
andzc706.py
are moved toconfig.py
write_rustc_cfg_file()
to usecpu_interface.get_rust_cfg
zc706.py
now auto generatedhas_CRS_core
to its rustc_cfg filefollowing artiq repo, all
self.rustc_cfg
atzc706.py
are replaced withself.config
zc706 rustc-cfg file check
python src/gateware/zc706.py -c build/rustc-cfg -V <variant>
for zc706_nist_clock master, satellite & standalonekasli_soc rustc-cfg file check
python src/gateware/zc706.py -c build/rustc-cfg <variant>.json
for kasli_soc master, satellite & standalonecompilation check
nix build <variant> -L
for kasli_soc master, satellite, standalone and all built successfullynix build <variant> -L
for zc706_nist_clock, zc706_nist_clock_master, zc706_nist_clock_satellite and all built successfullyb41b931ce5
toaa2009d49e
Now I'm thinking that since
write_...
functions are shared between zc706 and kasli-soc, they could be just extracted into e.g.config.py
- but it's not a big deal if it isn't.Sounds good.
write..file()
intoconfig.py
4716d1a4c5write_rustc_cfg_file()
3807857423zc706.py: replace self.rustc_cfg and change write_rustc_cfg_file() to follow artiq repoto consolidate all `write..file()` into `config.py` and update `zc706.py` to follow artiq repomorgan referenced this pull request2023-10-26 13:05:45 +08:00