Problems Flashing DivIDE with FatWare.
Hi.
I've recently purchased a DivIDE and it appears to be working fine, however the firmware on it is 0.12a and I am having trouble flashing it to a newer version.
I am using a ZX spectrum +2a with an original DivIDE purchased from www.lotharek.pl.
I have both Jumper A and Jumper E on since I have a +2a
I am using a 256MB GoodRam compact flash card and the CF interface and these came with the unit.
Using FATware 0.12 for ZX48 and ZX128/+2. I placed the bin file and tap file in the root of my CF card. I loaded the tap file and removed jumper E.
I pressed a key as got the message "System not flashed" and Installation complete. I then put Jumper E back.
Pressing the NMI button twice boots me into the new firmware, but it is only in memory and vanished when I power off.
Using FATware 0.14, I repeated the same process, except I placed the .bin file in the FATWare folder in the root.
I got the same error but this time, pressing the button twice did nothing.
I am a little confused with the placement of the .bin files and the tap files? Are both of these needed? If so, do I have them in the right place?
Jumper E seems to be functioning correctly for enabling / disabling the device, so that seems ok.
Is there a problem with my speccy because it is a +2a? I have tried it with a +3 with the same results, but I do not have any others to test with.
Could it be the CF adaptor? Do I need to install via a HD?
Any advice would be greatly appreciated
I've recently purchased a DivIDE and it appears to be working fine, however the firmware on it is 0.12a and I am having trouble flashing it to a newer version.
I am using a ZX spectrum +2a with an original DivIDE purchased from www.lotharek.pl.
I have both Jumper A and Jumper E on since I have a +2a
I am using a 256MB GoodRam compact flash card and the CF interface and these came with the unit.
Using FATware 0.12 for ZX48 and ZX128/+2. I placed the bin file and tap file in the root of my CF card. I loaded the tap file and removed jumper E.
I pressed a key as got the message "System not flashed" and Installation complete. I then put Jumper E back.
Pressing the NMI button twice boots me into the new firmware, but it is only in memory and vanished when I power off.
Using FATware 0.14, I repeated the same process, except I placed the .bin file in the FATWare folder in the root.
I got the same error but this time, pressing the button twice did nothing.
I am a little confused with the placement of the .bin files and the tap files? Are both of these needed? If so, do I have them in the right place?
Jumper E seems to be functioning correctly for enabling / disabling the device, so that seems ok.
Is there a problem with my speccy because it is a +2a? I have tried it with a +3 with the same results, but I do not have any others to test with.
Could it be the CF adaptor? Do I need to install via a HD?
Any advice would be greatly appreciated
Post edited by Kirby2000 on
Comments
I don't know details about flashing from fatware 0.14, but if you need upgrade or reflash system then you must place in root directory on master disc file "flash.bin" with new system image. (before and during flashing must be left jumper open)
Or use classic way: load installation TAP file to ZX, open jumper and reflash system, close jumper.
Or load installation TAP file from PC(soundcard output) or from real tape recorder/MP3 player.
If you need best comfort with boot menu (firmware selector) please flash last version of ESXDOS and place my FIRMWARE SELECTOR to your master IDE disc:
http://velesoft.speccy.cz/zx/divide/systems/esxdos/esxdos073out-firmware-selector02.zip
(ZIP contain ESXFLASH.TAP with flash utility for divide eeprom)
With this menu is possible select different systems or switch DivIDE to true allram mode with system BS-DOS309 or modified ZX48 rom with RS232 support ( ZX tape operations < > RS232 on PC )
EEPROM chip can use special write protection. This feature can protect flashed systems and before reflash eeprom must be used special utility for deactive protection:
EPROTECTOR - write protector for eeprom AT28C64B.
This utility use eeprom software write protect feature and work only with eeprom type 28C64B (with "B" !!!)
After press key "D" will eeprom protected and all system flasher utilities will ignored. Before rewriting eeprom you must load EPROTECTOR and press key "E" for enable writing + load any system flasher(intalator). After flash system to eeprom you can load EPROTECTOR and press key "D" for write protection.
http://velesoft.speccy.cz/zx/divide/software/eprotector-divide.zip
For +2A and +3 models with original rom chips can't be used FATWARE (128kB versions for 48 and 128/+2). This fatware need original 48/128/+2 rom and on +2A/+3 work incorrect. For +2A/+2B/+3 models please use only FATWARE 12 / 12a or 14. Other original systems work on all ZX models.
It was the EEPROM that was write protected. I can flash it now.
I flashed Fatware 0.14 OK and was able to load 128K tap files using the files on http://velesoft.speccy.cz/zx/divide/divide-fatware.htm.
Is FATware the best firmware to have? I'm looking to use a CF card and be able to write files from my PC onto it then use in my Spectrum. It would be nice to use TZX files
Depends what you want to do. If you just want to load TAP and z80 files, then FatWare is the way to go.
If you want the ability to load and save on the Divide interface (and you don't have the Divide Plus), then ESXDOS is what you want, since it also allows loading and saving.
Consult this thread for the latest version of ESXDOS. It also includes a nice filebrowser now, as well as the ability to save files on the Divide 57c interface...
http://www.worldofspectrum.org/forums/showthread.php?t=27864&highlight=esxdos
Please not use writing in ESXDOS. Actual version 0.7.3. contain small bug and can destroy FAT table. For reading is this system stable. Author will soon release new bug-fixed version with stable write support.
Damn... Their I was hoping the write support was going to be stable... Fingers crossed they get this fixed soon. Until then, I'm holding back from updating my Divide until a stable release comes along.
Thanks velesoft for the info :)
Yes. DUSKY (author of filebrowser for ESXDOS) detect this bug. If you use small clusters on dics then bug can destory FAT often. (for example each 16th/32th/.. writed file active this bug)
My FIRMWARE SELECTOR is only easy BASIC program with short machine code for install ZX ram to DivIDE ram. Basic after select system open TAP file with 4x CODE blocks and install all to divide ram (mapram mode).
If you select system from my FIRMWARE SELECTOR and need jump back to main menu then write in basic command OUT 227,128. This OUT active software reset of DivIDE memory + install ESXDOS + load menu with selector.
File AUTOEXEC.TAP in my ZIP archive contain basic line 3. If you remove REM command from begin of this basic line, then will active automatic delay after (re)start ZX. Wait abou 1 second to press any key (press key to start menu with selector) else load automatically FILEBROWSER for ESXDOS ( AUTOEXE2.TAP file ) ;-) You can replace AUTOEXE2.TAP with any other TAP file with your game...