Problems after flashing kasli with Zotino and clock

raffi

Hello.

We are running a Kasli 2.0 with some urukuls and a zotino. Long story short, we just moved from a 7.x.beta version to 6.0 and reflashed Kasli. Anytime we try to initialize our zotino now, we get the ValueError: DAC CONTROL read back mismatch. I see where this comes from, but my EE knowledge is limited and I cannot understand what is causing the exception and why.

In addition our experiments are now all scheduled for exactly 4 months from now and we are unsure why. (To have an experiment execute we must change the computer's clock to July 29.)

All of our code had been working properly before this, so we are pretty confident in the code. Below is the error message.

Any suggestions on what to check or how to proceed would be greatly appreciated.

Cheers!
Raffi

INFO:worker(7410,control_zotino.py):print:Initializing DAC ERROR:worker(7410,control_zotino.py):root:Terminating with exception (ValueError: DAC CONTROL readback mismatch) Core Device Traceback (most recent call last): File "/home/srlab/artiq/artiq-master/repository/manual-control/control_zotino.py", line 149, in __modinit__ (RA=+0x5d4) self.zotino.init() File "<artiq>/coredevice/ad53xx.py", line -1, in ... artiq.coredevice.ad53xx.AD53xx.init<artiq.coredevice.zotino.Zotino>(...) (RA=+0xb4c) <unknown> File "<artiq>/coredevice/ad53xx.py", line 191, column 17, in ... artiq.coredevice.ad53xx.AD53xx.init<artiq.coredevice.zotino.Zotino>(...) raise ValueError("DAC CONTROL readback mismatch") ^ ValueError(0): DAC CONTROL readback mismatch Traceback (most recent call last): File "/home/srlab/nix_json/artiq/artiq/master/worker_impl.py", line 300, in main exp_inst.run() File "/home/srlab/artiq/artiq-master/repository/manual-control/control_zotino.py", line 104, in run self.call_init() File "/home/srlab/nix_json/artiq/artiq/language/core.py", line 54, in run_on_core return getattr(self, arg).run(run_on_core, ((self,) + k_args), k_kwargs) File "/home/srlab/nix_json/artiq/artiq/coredevice/core.py", line 137, in run self.comm.serve(embedding_map, symbolizer, demangler) File "/home/srlab/nix_json/artiq/artiq/coredevice/comm_kernel.py", line 644, in serve self._serve_exception(embedding_map, symbolizer, demangler) File "/home/srlab/nix_json/artiq/artiq/coredevice/comm_kernel.py", line 636, in _serve_exception raise python_exn ValueError: DAC CONTROL readback mismatch

sb10q

raffi In addition our experiments are now all scheduled for exactly 4 months from now and we are unsure why. (To have an experiment execute we must change the computer's clock to July 29.)

I assume you are using the dashboard. Maybe you selected the "schedule at..." option by mistake? What happens when you submit via the artiq_client command-line tool?

sb10q

Which system is it and how did you build the gateware and device db?

raffi

sb10q We are using a Zotino V1.1 with a Kasli 2.0. I generated the gateware and device db using python -m artiq.gateware.targets.kasli_generic sr_kasli2.json and python -m artiq.frontend.artiq_ddb_template sr_kasli2.json -o device_db.py respectively. Below is our json file, I have used it and these commands successfully before.

{ "target": "kasli", "variant": "strontium", "hw_rev": "v2.0", "ext_ref_frequency": 100e6, "base": "standalone", "core_addr": "192.168.1.50",
"peripherals": [ { "type": "dio", "ports": [0], "bank_direction_low": "input", "bank_direction_high": "output" }, { "type": "urukul", "ports": [1, 2], "dds": "ad9910", "clk_sel": 1, "refclk": 100e6, "pll_vco": 5, "pll_n": 40 }, { "type": "urukul", "ports": [3, 4], "dds": "ad9910", "clk_sel": 1, "refclk": 100e6, "pll_vco": 5, "pll_n": 40 }, { "type": "urukul", "ports": [5, 6], "dds": "ad9910", "clk_sel": 1, "refclk": 100e6, "pll_vco": 5, "pll_n": 40 },
{ "type": "zotino", "hw_rev": "v1.1", "ports": [9] } ] }

Apologies if the indentation/presentation is off - copied weirdly.

Thank you for assisting with the scheduling; I cannot believe I missed a simple the schedule at option.

rjo

The most common problem is a mismatch between system description and bitstream (old bitstream or a fresh one from the same json in both cases?), or between system description and device database (old device database or generated freshly from the same json in both cases?) or between host software and bitstream (both times matching the gateware version?).

raffi

We weren't getting mismatch errors before. Today, I rebuilt and flashed, being very careful of versions, however we are now getting a mismatch between software and gateware. But, when viewing GtkTerm on startup, it says that the versions do match. I have attached a screenshot so you can see what I mean. We are also confused on why GtkTerm says the versions are 6.7609.2f808880 and the dashboard says 6.7665.83af3b75 and 6.unknown. Any guidance would be greatly appreciated. Thanks!