mwojcik
1 Followers · 0 Following
  • Joined on 2021-07-22
Repositories
9
 Projects Packages Code Public Activity Starred Repositories
Loading Heatmap…

mwojcik created pull request sinara-hw/assembly#6

describe building legacy firmware

2023-10-25 12:30:46 +08:00

mwojcik created branch legacy-build in sinara-hw/assembly

2023-10-25 12:29:59 +08:00

mwojcik pushed to legacy-build at sinara-hw/assembly

2023-10-25 12:29:59 +08:00

mwojcik deleted branch simplify_build_instructions from mwojcik/assembly

2023-10-25 12:23:47 +08:00

mwojcik deleted branch urukul-troubleshoot-improv from mwojcik/assembly

2023-10-25 12:23:45 +08:00

mwojcik commented on pull request M-Labs/artiq-zynq#274

master: fix kasli-soc demo compilation warning

Yes, I was actually thinking about that too.

2023-10-25 10:16:21 +08:00

mwojcik commented on pull request M-Labs/artiq-zynq#274

master: fix kasli-soc demo compilation warning

Does ``io_expander`` even make sense if there's no ``virtual_leds``? On standalone Kasli-SoCs that means the task isn't actually doing anything at the moment.

2023-10-24 14:44:34 +08:00

mwojcik commented on pull request M-Labs/artiq-zynq#273

release-7: fix zc706 master and standalone compilation warning

Maybe just move it and task::spawn of io_expander_service to the block with io expander settings?

2023-10-24 13:19:45 +08:00

mwojcik commented on issue M-Labs/zynq-rs#105

MIO reset_gpio collisions

A quick study of the Zynq7000 TRM in the topic of MIO, GPIO, etc. confirms that the reset is indeed not necessary. Two things to note: An example on programming a MIO pin: https://docs.xilinx.…

2023-10-20 16:46:08 +08:00

mwojcik created pull request M-Labs/zynq-rs#106

remove gpio reset

2023-10-18 17:37:18 +08:00

mwojcik created branch no_reset in mwojcik/zynq-rs

2023-10-18 17:33:57 +08:00

mwojcik pushed to no_reset at mwojcik/zynq-rs

2023-10-18 17:33:57 +08:00

mwojcik commented on issue M-Labs/zynq-rs#105

MIO reset_gpio collisions

Actually, it's even simpler than that. SD code was an inspiration. Seems like ``reset_gpio`` is not necessary. I can boot normally and connect with DRTIO.

2023-10-18 17:33:52 +08:00

mwojcik opened issue M-Labs/zynq-rs#105

MIO reset_gpio collisions

2023-10-18 16:38:02 +08:00

mwojcik commented on pull request M-Labs/artiq-zynq#271

Add grabber module to release-7

``sys_clk_freq`` is the one that should be used, as grabber clock is based off the system clock domain ([deserializer_7series.py#L22](https://github.com/m-labs/artiq/blob/release-7/artiq/gateware/g…

2023-10-18 14:58:00 +08:00

mwojcik pushed to subkernel_composite at mwojcik/artiq-zynq

2023-10-18 12:04:02 +08:00

mwojcik created pull request M-Labs/artiq-zynq#272

subkernel: separate tags and data

2023-10-18 11:58:02 +08:00

mwojcik created branch subkernel_composite in mwojcik/artiq-zynq

2023-10-18 11:56:43 +08:00

mwojcik pushed to subkernel_composite at mwojcik/artiq-zynq

2023-10-18 11:56:43 +08:00

mwojcik commented on pull request M-Labs/artiq-zynq#270

Add grabber module

and use clk_freq here, since you just defined it :)

2023-10-16 13:36:31 +08:00