25 June 2018, 15:00 | #881 |
-
Join Date: Jul 2003
Location: Helsinki / Finland
Age: 43
Posts: 9,861
|
There is no ready pulse generation on the motherboard, trackdisk.device always assumes DF0 is present. If the drive is capable of generating its own ready pulse, it will detect a HD drive (ks 2.04 + setpatch or 3.x needed).
|
25 June 2018, 16:36 | #882 | |
Registered User
Join Date: May 2011
Location: Cambridge
Posts: 682
|
Quote:
(Ah yes, as Jope already pointed out ) |
|
25 June 2018, 17:44 | #883 |
Registered User
Join Date: Aug 2016
Location: Cresco, PA, USA
Age: 53
Posts: 1,126
|
OK great. I'll try to get to some testing this week and report back with files via github if necessary. I haven't yet upgraded to the latest and greatest version.
|
25 June 2018, 18:16 | #884 | |
Registered User
Join Date: May 2011
Location: Cambridge
Posts: 682
|
Quote:
https://github.com/keirf/FlashFloppy...irmware-Update |
|
25 June 2018, 19:43 | #885 | |
Registered User
Join Date: Aug 2016
Location: Cresco, PA, USA
Age: 53
Posts: 1,126
|
Quote:
|
|
30 June 2018, 15:43 | #886 | |
The show must go on.
|
Quote:
If I understand you correctly, (just want to be sure here) Take pin 1 on de DB23 that should be RDY <-> Disk Ready Bypass the internal board of the enclosure and connect it to pin 34 DSKCHG <- Disk Change/Ready on the gotek? |
|
02 July 2018, 06:42 | #887 | |
-
Join Date: Jul 2003
Location: Helsinki / Finland
Age: 43
Posts: 9,861
|
Quote:
Perhaps it makes more sense now. In addition to connecting the gotek's ready directly to the amiga floppy bus's ready, you should also disconnect or completely remove the TTL chip (often a 7438) that provides the ready pulse on the external drive enclosure's PCB. Last edited by Jope; 02 July 2018 at 14:29. |
|
02 July 2018, 08:03 | #888 |
Derezzed User
Join Date: Feb 2018
Location: Tallahassee / USA
Posts: 38
|
|
02 July 2018, 08:26 | #889 |
Registered User
Join Date: May 2011
Location: Cambridge
Posts: 682
|
|
05 August 2018, 08:55 | #890 |
Posts: n/a
|
Hi all, I guess I need some help. I recently acquired a nice Amiga 500 unit with memory expansion and lots of stuff. It came with a builtin Gotek drive that is running FlashFloppy as firmware. It's an internal drive with two buttons. Took me actually ages to find out it's using a different firmware since I'm pretty new to this. However, I encountered a few odd things which I have no idea how to solve them myself and hope you guys have some answers. I'm also not sure if all is FF related.
I pretty early knew that I may have some problems. First thing I did right away (I'm using a Gotek on my Amstrad CPC so I'm familiar) is that I tried some games. I found out that for certain games swapping disks won't work. The first disk always loads fine, when I need to swap to the 2nd disk, I navigate to the appropiate image via the buttons and then happens: nothing. I've tried a few Cinemaware titles (Wings, It came from the Desert, Defender of the Crown). All the same issue. Full Contact for example is working. I then thought it might be a firmware problem so I checked what we got and it confuses me to be honest. 1) When the Gotek came (already flashed with FF), the USB stick I got alongside with it had AUTOBOOT.HFE and HXCSDFE.CFG from the HxC project on it, not the AUTOBOOT and config that comes with FF. It works even though you get a notice that you're running a different firmware. 2) I updated FF based on the Wiki and the Gotek showed me that it worked. Also when I run the stick again the FF firmware has the newest version number (as seen in the bottom left). 3) When I try now to replace AUTOBOOT.HFE and HXCSDFE.CFG with the ones from the FlashFloppy distribution I surprisingly get "ERROR: writesector -> failure while seeking the track00!". The ones from HxC notably work. Yes, I reformatted the stick and then I put those files first on it again. No change, only the HxC ones work. 4) And I still have the problem with swapping disks as mentioned above. Any advice what this could be? I opened the Amiga and the Gotek is jumpered S0. 5) One thing I noticed is that the drive LED is constantly lit, which in my understanding isn't correct? Thanks in advance! Last edited by 8bit_era; 05 August 2018 at 09:01. |
05 August 2018, 09:04 | #891 |
Unregistered User
Join Date: Sep 2012
Location: Copenhagen / DK
Age: 43
Posts: 4,190
|
A permanently on floppy LED is normally a sign that the floppy cable was connected upside down in one end, however if that was the case you would obviously not be able to load anything.
|
06 August 2018, 11:38 | #892 |
Registered User
Join Date: Mar 2018
Location: Manchester
Posts: 7
|
The red light is permanently lit if you've got an OLED display connected.
|
10 August 2018, 19:15 | #893 |
Da Digger :)
Join Date: Nov 2008
Location: Monza, Italy
Posts: 2,822
|
|
14 August 2018, 16:28 | #894 |
Registered User
Join Date: May 2011
Location: Cambridge
Posts: 682
|
|
14 August 2018, 16:31 | #895 |
Unregistered User
Join Date: Sep 2012
Location: Copenhagen / DK
Age: 43
Posts: 4,190
|
Is that LED even visible on some Goteks? On all the ones I have seen, it is only internal.
|
17 August 2018, 01:36 | #896 | |
Da Digger :)
Join Date: Nov 2008
Location: Monza, Italy
Posts: 2,822
|
Quote:
Well, in this case... who cares? |
|
24 August 2018, 02:24 | #897 |
Warhasneverbeensomuchfun
Join Date: Jun 2001
Location: Rio de Janeiro / Brazil
Age: 41
Posts: 3,450
|
I had flashed my Gotek with Flashfloppy eons ago. I had a version that dated back to September 2017.
Today I decided to update it to the lastest release, 0.9.27a Did the procedure (copy .upd file to usb drive, power it on with both buttons pressed), it updated very fast. But now all I get at my LED display are the letters "rSt". Can't choose any files at all. I copied the FF.CFG file to the usb drive and still all I get is this. found out I need to use "HxC Compatibility mode" with an old 7 segment LED display. I already copied the proper files to the USB stick (were already there but did a overwrite anyway) and still nothing. Any help please? |
24 August 2018, 07:20 | #898 | |
Registered User
Join Date: May 2011
Location: Cambridge
Posts: 682
|
Quote:
Check that the only jumper at the rear of your Gotek is at position S0. Remove any other jumpers. Then report back. |
|
26 August 2018, 22:39 | #899 |
Registered User
Join Date: Sep 2016
Location: Ireland
Posts: 304
|
Hi kaffer.
Do you have any plans to support a 20x04 display? It already works fine as a 20x02 though as it is. I was just wondering. Maybe if you end up supporting 2x drives from the Gotek, the 20x04 would be useful? Or to show very long file names without scrolling! It's almost as big as the Gotek too. It looks huge, and very out of place beside the 128x32/128x64. |
28 August 2018, 23:02 | #900 | |
Registered User
Join Date: May 2011
Location: Cambridge
Posts: 682
|
Quote:
|
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Help to open-source SAS/C | Hauke | Coders. General | 35 | 26 September 2017 22:39 |
LCD on Gotek (with HxC firmware) | christopherpm | Hardware mods | 1 | 08 January 2017 02:51 |
Gotek drive firmware for mounting .iso cd images | Ox. | Amiga scene | 7 | 05 November 2014 05:14 |
Gotek drive firmware for Amiga general USB mass storage solution | Supamax | Amiga scene | 2 | 20 September 2014 08:35 |
BlitzBasic - Is now open source | Djay | Amiga scene | 2 | 08 February 2003 01:09 |
|
|