Releases: LinuxJedi/68000_Relocator_FLASH_Kickstart
Version 1.8
Versions
Item versions in bold have changed in this project version.
Item | Version |
---|---|
GUI | v1.8 |
CLI | v3.5 |
Firmware | v3.4 |
Notable changes
The behaviour of the jumper on the board has now changed. Firmware version 3.4 onwards requires that the board was built using 2x 39ST040 chips (all mine are). The jumper now sets the default ROM on first boot, either motherboard (jumper off) or ROM1 (jumper on).
Changelog
Firmware
- Jumper now determines which ROM will boot first (off for Motherboard). Firmware now only works with two-ROMs
- Fix issue where held reset on first boot switches ROM (PiStorm boot)
GUI
- If autoconfig failed then disable ROM flashing with appropriate message
Version 1.7a
Versions
This is a re-release of 1.7 as 1.7 had the wrong Firmware file.
Item versions in bold have changed in this project version.
Item | Version |
---|---|
GUI | v1.7 |
CLI | v3.5 |
Firmware | v3.03 |
Board | rev 3 |
Notable changes
In some Amiga hardware configurations it was possible for ROM2 to hit a reboot loop. This is now fixed.
Changelog
Firmware
- Fixed reboot loop on ROM2 in some scenarios
CLI
- Ported 256K ROM fixes from GUI
GUI
- Don't double-flash the 256K ROMs if the first flash fails
- Make erase-before-flash more human
- Remove error message that asked if you erased, since it is automatic
Version 1.7
Versions
Item versions in bold have changed in this project version.
Item | Version |
---|---|
GUI | v1.7 |
CLI | v3.5 |
Firmware | v3.03 |
Board | rev 3 |
Notable changes
In some Amiga hardware configurations it was possible for ROM2 to hit a reboot loop. This is now fixed.
Changelog
Firmware
- Fixed reboot loop on ROM2 in some scenarios
CLI
- Ported 256K ROM fixes from GUI
GUI
- Don't double-flash the 256K ROMs if the first flash fails
- Make erase-before-flash more human
- Remove error message that asked if you erased, since it is automatic
Version 1.6
GUI - v1.6
CLI - v3.4
Firmware - v3.02
Board - rev 3
Changelog:
- Fixed issue where GUI was not flashing 256K ROMs correctly
- Fixed versioning in firmware
- Potentially allowed flash to work outside of the 8MB ZII memory area (needs further testing)
Version 1.5
GUI - v1.5
CLI - v3.4
Firmware - v3.01
Board - rev 3
Notable changes:
- You no longer need to erase the entire device before flashing a new ROM using the GUI. The "Load File" button will warn you that it is going to erase an individual ROM and then will do so before you select a file.
Changelog:
- Firmware Verilog a little easier to read and has version information in the Autoconfig
- CLI tool shows the firmware version number in information
- GUI tool shows the firmware version number in the "About"
- Fixed the sector erase code in the ROM JEDEC interface
- Individual ROM erase functionality added
- GUI tool will erase a ROM before flashing automatically (with prompting)
Version 1.4
GUI - v1.4
CLI - v3.3
Board - rev 3
- Fix VBCC maths issue when calculating ROM2 position for reading
- Fix fussy paths issue for WB1.3
Version 1.3
GUI - v1.3
CLI - v3.2
Board - rev 3
- First proper release of new GUI
- Improved KS 1.3 compatibility
- Switched compiling back to VBCC
- Scripts to create ADF and LHA
- Significant reduction in memory requirements to flash
- Simplified board design a little