sinara-hw
/
assembly
5
3
Fork 6
Code Issues 5 Pull Requests Packages Projects Releases Activity

mirny: add build and flashing instructions #17

Merged
esavkin merged 1 commits from mwojcik/assembly:mirny-improvements into master 2024-08-17 17:37:24 +08:00
Conversation 1 Commits 1 Files Changed 2 +11 -3
mwojcik commented 2024-06-03 15:59:16 +08:00
Collaborator
Copy Link

It's not easy to figure out how to build this at all - so I'm writing this down before I forget.

I'm leveraging ARTIQ flake for building Mirny here. Yeah it's an overkill, but it's simpler than building an environment from scratch.

It's not easy to figure out how to build this at all - so I'm writing this down before I forget. I'm leveraging ARTIQ flake for building Mirny here. Yeah it's an overkill, but it's simpler than building an environment from scratch.
👍 1
morgan reviewed 2024-06-03 17:15:17 +08:00
src/hw/mirny_almazny.md Outdated
@ -18,0 +20,4 @@
Once you get your hands on the firmware, you will need to work around few shortcomings of Nix, mainly not being able to run dynamically linked executables.
You will need:
- Xilinx ISE installed on your system,
morgan commented 2024-06-03 17:10:31 +08:00
Member
Copy Link

add an install path example like "/opt/Xilinx", since by default Xilinx installer use "/tools/Xilinx" iirc

add an install path example like "/opt/Xilinx", since by default Xilinx installer use "/tools/Xilinx" iirc
morgan marked this conversation as resolved
src/hw/mirny_almazny.md Outdated
@ -18,0 +23,4 @@
- Xilinx ISE installed on your system,
- an environment with Migen.
One way to do it is to create an FHS environment, like ARTIQ does for Vivado, within ARTIQ (to leverage Migen already being there), by adding these lines:
morgan commented 2024-06-03 17:13:00 +08:00
Member
Copy Link

There are no mention of the file we need to add the lines to, you can add it here e.g. "adding these line to flake.nix" or after the code block

There are no mention of the file we need to add the lines to, you can add it here e.g. "adding these line to flake.nix" or after the code block
morgan marked this conversation as resolved
mwojcik force-pushed mirny-improvements from 3744c29952 to 440f687bac 2024-06-04 16:25:53 +08:00 Compare
esavkin commented 2024-06-04 16:49:31 +08:00
Collaborator
Copy Link

Since QUARTIQ refuses to add the binary distribution for some reason, would be nice to add it here, so there will be no need to do these flake.nix edits for those, who just needs to update the firmware (who may appear to be far from development).

Since QUARTIQ [refuses](https://github.com/quartiq/mirny/issues/6) to add the binary distribution for some reason, would be nice to add it here, so there will be no need to do these flake.nix edits for those, who just needs to update the firmware (who may appear to be far from development).
esavkin reviewed 2024-06-05 10:16:10 +08:00
src/hw/mirny_almazny.md Outdated
@ -18,0 +19,4 @@
Here is [Mirny 0.3.1 firmware](../extra/mirny/mirny-0.3.1.zip). It contains a single ``.jed`` file that can be flashed following [flashing instructions](#flashing).
## Building firmware (optional)
esavkin commented 2024-06-05 10:16:00 +08:00
Collaborator
Copy Link

Feels like it should be H3 instead of H2

Feels like it should be H3 instead of H2
sb10q commented 2024-06-05 10:58:24 +08:00
Owner
Copy Link

Just add the release to hydra like the others https://nixbld.m-labs.hk/eval/6728

Just add the release to hydra like the others https://nixbld.m-labs.hk/eval/6728
src/hw/mirny_almazny.md
@ -18,0 +25,4 @@
Once you get your hands on the firmware source code, you will need to work around few shortcomings of Nix, mainly not being able to run dynamically linked executables.
You will need:
esavkin commented 2024-06-05 10:15:23 +08:00
Collaborator
Copy Link

This better be in Getting the firmware

This better be in `Getting the firmware`
mwojcik commented 2024-06-05 10:27:44 +08:00
Author
Collaborator
Copy Link

There's some overlap (ISE) but not all (no Migen, but xc3sprog). So I just repeated that.

There's some overlap (ISE) but not all (no Migen, but xc3sprog). So I just repeated that.
mwojcik force-pushed mirny-improvements from caede1555e to 6bdd0b61ac 2024-06-05 10:27:03 +08:00 Compare
esavkin merged commit 6bdd0b61ac into master 2024-06-05 10:35:31 +08:00
mwojcik deleted branch mirny-improvements 2024-06-05 11:31:04 +08:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
4 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: sinara-hw/assembly#17
No description provided.
Delete Branch "mwojcik/assembly:mirny-improvements"

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?