Latest openocd version does not allow flashing (Windows, conda) #83

Closed
opened 2022-04-13 21:11:47 +08:00 by ThorstenGroh · 1 comment

I don't know whether this is the right place to file this issue, but I was directed to here.

As discussed in the forum 412-error-while-flashing-gateware-windows the latest version of openocd as hosted by m-labs (v0.10.0+git2 and v0.10.0+git1), where v0.10.0+git2 automatically installs via conda install -c m-labs openocd, does not allow flashing new gateware to the Kasli on Windows / conda. Running artiq_flash -V YOUR_VARIANT throws an invalid command name "xadc_report" error.

Explicitly installing an older version via conda install https://anaconda.org/m-labs/openocd/0.10.0/download/win-64/openocd-0.10.0-6.tar.bz2 solves the issue.

This is on a fresh conda installation under Windows 10 as described in the documentation (installing-via-conda-windows-linux).

More details can be found in the linked forum post.

I don't know whether this is the right place to file this issue, but I was directed to here. As discussed in the forum [412-error-while-flashing-gateware-windows](https://forum.m-labs.hk/d/412-error-while-flashing-gateware-windows) the latest version of openocd as hosted by m-labs (`v0.10.0+git2` and `v0.10.0+git1`), where `v0.10.0+git2` automatically installs via `conda install -c m-labs openocd`, does not allow flashing new gateware to the Kasli on Windows / conda. Running `artiq_flash -V YOUR_VARIANT` throws an `invalid command name "xadc_report"` error. Explicitly installing an older version via `conda install https://anaconda.org/m-labs/openocd/0.10.0/download/win-64/openocd-0.10.0-6.tar.bz2` solves the issue. This is on a fresh conda installation under Windows 10 as described in the documentation ([installing-via-conda-windows-linux](https://m-labs.hk/artiq/manual/installing.html#installing-via-conda-windows-linux)). More details can be found in the linked forum post.

I moved the older versions to an "obsolete" label, problem should not occur again.

I moved the older versions to an "obsolete" label, problem should not occur again.
sb10q closed this issue 2022-04-18 17:13:12 +08:00
Sign in to join this conversation.
No Label
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: M-Labs/nix-scripts#83
There is no content yet.