How do I flash `boot.bin` instead of `<afws_directory>`?

Ddtsevas · 3 Feb

artiq_coremgmt [-D IP_address] -s <destination_number> flash <afws_directory>

That's great, but I compiled boot.bin myself. How do I flash it? By passing the absolute path of its local directory in place of <afws_directory>?

Ddtsevas · 3 Feb

I went into the directory that contains my boot.bin and ran

artiq_coremgmt -D 192.168.1.30 -s 1 flash .

Here is the error log:

Traceback (most recent call last):
  File "/home/dimitry/.pyenv/versions/artiq-py311/bin/artiq_coremgmt", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/opt/m1/workspace/artiq-original-untouched/artiq/frontend/artiq_coremgmt.py", line 196, in main
    mgmt.flash(bins)
  File "/opt/m1/workspace/artiq-original-untouched/artiq/coredevice/comm_mgmt.py", line 221, in flash
    self._read_expect(Reply.RebootImminent)
  File "/opt/m1/workspace/artiq-original-untouched/artiq/coredevice/comm_mgmt.py", line 121, in _read_expect
    raise IOError("Incorrect reply from device: {} (expected {})".
OSError: Incorrect reply from device: Reply.Error (expected Reply.RebootImminent)

Version info:

3x Kasli SoC v1.1.1: two satellites connected to one master in default topology.
artiq-zynq commit a0281e498927d5c8467dd18f28aa497cb75150fd from 23 December 2024 running on all three Kasli SoCs.
artiq commit d4bd4e587958a3ea249a7d4759d2ddf144d51a85 from 31 January 2025 running on host computer.

Ddtsevas · 3 Feb

Ok, I turned this into https://github.com/m-labs/artiq/issues/2667 because I think it's an actual Artiq bug and not a problem with <afws_directory> vs. a self-made local directory.