v1.2.2 release

This patch release contains a change to the CP version of a314.device that makes it possible to write a configuration file to DEVS:a314.config. See Software/README.md#configuration-file for more details.

See the v1.0 release for the A314-500/-600 firmware.

v1.2.1 release

This patch release contains a change to the FE version of a314.device such that both the 0x040000 and the 0xC40000 addresses are probed to find the A314-1000 hardware. In an A314-1000 with a Rejuvenator the front expansion memory is moved from 0x040000 to 0xC40000.

See the previous release for the A314-500/-600 firmware.

v1.2 release

The a314-amiga.zip archive contains the A314 software for the Amiga side, for all variants of A314.

The release also contains the firmware for the A314-500 and A314-600 boards.

There are three Programmable Object Files (.pof):

a314-500.pof - The normal firmware for A500 and A500+. In an A500 you need to disconnected RAS0 using the JMP3 jumper that exists on 1.2 boards (https://github.com/niklasekstrom/a314/wiki/Jumpers-on-PCB-1.1).
a314-500-ras0-disconnected.pof - On a Beta-2 board there is no JMP3 jumper, so if you want to use a Beta-2 board in an A500 you need to use this firmware that has RAS0 permanently disconnected.
a314-600.pof - For use with the A600 version of A314.

A314 files with compiled firmware

A snapshot of the A314 files, with compiled firmware.

There are three Programmable Object Files (.pof):

• a314-500.pof - The normal firmware for A500 and A500+. In an A500 you need to disconnected RAS0 using the JMP3 jumper that exists on 1.2 boards (https://github.com/niklasekstrom/a314/wiki/Jumpers-on-PCB-1.1).
• a314-500-ras0-disconnected.pof - On a Beta-2 board there is no JMP3 jumper, so if you want to use a Beta-2 board in an A500 you need to use this firmware that has RAS0 permanently disconnected.
• a314-600.pof - For use with the A600 version of A314.

FPGA configuration for autodetect branch

This POF (Programmer Object File) was compiled from the autodetect branch, and the corresponding software in the autodetect branch should be used.