diff --git a/src/extra/mirny/mirny_0.2.4_legacy_almazny.zip b/src/extra/mirny/mirny_0.2.4_legacy_almazny.zip
new file mode 100644
index 0000000..fda9a20
Binary files /dev/null and b/src/extra/mirny/mirny_0.2.4_legacy_almazny.zip differ
diff --git a/src/hw/mirny_almazny.md b/src/hw/mirny_almazny.md
index 471c965..acfca36 100644
--- a/src/hw/mirny_almazny.md
+++ b/src/hw/mirny_almazny.md
@@ -17,7 +17,9 @@
 
 ## Getting the firmware
 
-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).
+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). This firmware supports Almazny v1.2+.
+
+If you are using a legacy Almazny (v1.0-1.1), due to different signals routed, you need to flash the older [0.2.4 firmware with Almazny support](../extra/mirny/mirny_0.2.4_legacy_almazny.zip).
 
 ### Building firmware (optional)
 
@@ -150,4 +152,6 @@ You should also see differences in various modes, but that may require disabling
 
 ~~Mirnies often fail `ValueError: MUXOUT not high`, in that case restart the tests or reboot the board(s).~~ - fixed in [9569cfb](https://github.com/m-labs/artiq/commit/9569cfb26329c0acdc1705d3256d2506b7bccce5)
 
+For Almazny v1.0 and 1.1 support, CPLD firmware 0.2.4 (linked above) must be flashed onto Mirny.
+
 For Almazny v1.2+ support, CPLD firmware 0.3.1+ (with fixes) must be flashed onto Mirny.
\ No newline at end of file