-
Notifications
You must be signed in to change notification settings - Fork 198
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Info: FF with 26-pin header Gotek Floppy #155
Comments
Do you know what RA, RB, RC (all 0R?) do or how they are connected into the Gotek schematic, and why you had to remove them? If I can document that I can add something to the "Gotek Compatibility" section of the wiki. |
Yes, all are assembled with 0R. With RA the drive ever shows 'Upd' on the display. The drive is mounted now, I can't measure the Rx->pin config. But I have a fast drawing on paper - maybe I can re-read it from there. From here we can know that RA is pulling down Pin 37 of the STM32 |
Added a link to this ticket to the wiki. |
Thanks for the info, I was able to get the SFR1M44-DU26 working on my LeCroy LC684 oscilloscope. I only removed the three resistors and left the EEPROM. |
Did it not work before? I have the SFR1M44-DU26 happily working in my TDS784D without any modifications. Just curious as to why you guys modded your disk emus. |
IMHO the original firmware of the SFR1M44-DU26 works better. With no USB device connected, it uses the internal flash memory as a virtual disk. Once you've connected a USB device (one large partition formatted to FAT32) and press the right button, it'll then read the first few files (up to 1.44 MB) from the USB and present those as the "disk". Pressing the button again will read the next few files and so on. And if you want to store files on USB, just press the left button and from that moment on, all files written to the "disk" will end up on the USB drive. No need to make multiple disk images or special partitions or anything. |
The Tektronix TDS3000 series have a 26pin flat wire, so to use the SFR1M44-DU26 is a logic step. The original FW offers only a non HD Disk - what was not accepted by (my) TDS, so to replace the FW to get a HD drive was the next logical step. |
@oldtrusty I see a lot of markings on your PCB, and also a TO92 Transistor - ... As i remember, at the end I didn't need such modifications. |
@mbirth do you have the original firmware or know of a link to it? |
@JoanMCD the markings were to help me identify the boot0, +3.3, Tx, Rx, and Gnd pin during programming of FF. The TO92 (2N2222A) is temporary and was to replace the 1P SOT23 (2N2222A), which I damaged when I was playing with the rear jumpers. It tells the uC that the disk is read-only, I believe. That's the constant error I was getting when it was damaged. When I replaced the error went away. How did you format your USB drive and did you have to load any of the .img files mentioned in the FF examples? |
@oldtrusty Sorry, no. Never fiddled with my Gotek and/or dumped the fw. |
Hi - fellow Flashfloppy user here with the SFR1M44-DU26. Mine was used with an IBM slimline floppy drive enclosure (formerly occupied by a TEAC FD05HF) to allow oldschool ThinkPads (560E) to work off disk images and whatnot. Mine has a revised logic board variant (SFRC2DA) that looks to be almost the same as the SFRC2D. Just to confirm with the postings of @JoanMCD - you do have to remove/disconnect resistors RA and RC for the device to get out of flash update mode. Once it's removed the device will work just fine. Retaining the RB+EEPROM (used by the original firmware to...I don't even know what it does as this Gotek variant does not behave like normal Goteks, so formatting your drive into multiple segments of 1.44MB in size is not going to work)...is purely up to you. I disconnected RB but kept the EEPROM alone on mine. Things to be aware of -
[Boot0] [3.3] [TX] [RX] [RST] The following pins on the output corresponds to the following pinout on the STM32F105 LQFP64 package, and with the colors noted on the diagram below.
5v - Pin1 (VBAT) Red There is an AMS1117 voltage regulator(SOT223 package) with 3 pins, denoted on the board as U4. Left is GND, middle is 3.3v, and right is 5v. On the SFRC2D/A the display connector is the following from left to right: [SDA] [SCL] [GND] [3.3V] Ground is denoted as Black, and 3.3v is denoted as Orange-Red. To program the SFRC2D/A with a USB-TTL serial adapter (preferably one that can do both 3.3/5v with the flick of a jumper), put a jumper between Boot0 and 3.3v, TX and TX to the correct pins, run VCC to the 5v pin (below J4), and ground to the GND pin (below RST), and follow the usual instructions. There are existing test points on the board that can be used to verify that the soldering has been done correctly. See the attached photo for an idea of where they are located. Test points for RX/TX is above the STM105, Boot0 is to the left of the STM32F105, SDA/SCL is to the right (SDA will require you to test continuity with pin 27 directly), and 5v is present in at least 4 locations + the right leg off U4. 3.3v is supposed to be on the rightmost pin of the display pinout and on the middle leg off U4. @keirf you might find this photo of the SFRC2DA useful: Hope this bit is useful for those trying to make this device do useful things - the SFR1M44-GU26 have practically no open documentation available whatsoever besides "buy this overpriced Gotek variant" and a poorly translated instruction manual of questionable applicability. @mbirth The default firmware is utterly useless crap if you plan to work with non-standard disk images, like the 1.72MB XDF images used by IBM's OS/2. For 1.44MB floppies it's not that difficult to grab a disk image template and have the FDC write/save it to a blank disk image, save it and then rename it on the USB stick later. @oldtrusty did your model come with the jumpers for the bottom headers? I noticed that on mine the JD/JE headers were jumped...not sure if this might impact your Oscilloscope reading the device. |
Hello. I am currently having some trouble with programming the SFRC2DA with the USB-TTL serial adapter. I followed the instructions given by @kkwannyc
I removed the three resistors (RB, RC, and RA), then I followed the wiring diagram. I attached a picture of how I wired the SFRC2DA to the USB-TTL serial adapter. I then proceeded to follow the video from Kris Cochrane that was linked in the wiki page. After opening the ST Flasher program I got the following error attached. I was wondering what else I could be missing. Thanks |
Just to add a success here: Tektronix TDS640A Initial programming was performed in DFU/USB mode (jump 3.3v/boot and tx/5v, connect to PC and use the ) since I couldn't find my USB to serial adapter, worked perfectly. The drive is a bit narrower than the original drive, so there is a small gap in the front panel. The drive seems slow, as it takes about 10 seconds to write 38KB, or around 30kbit/second, but I didn't think to time how long it took on an actual floppy drive. |
Check continuity with the test points/ pins I’ve given and see if there are some cold solders/bad contacts somewhere (it happens sometimes). Also, I think you need to unlock the device for write before it will work, but if the commands are downright being ignored it might be a communications issue (hence…continuity checks) |
I have a TDS640A and I am trying to do the exact same thing as you. I have Flash Floppy firmware on my SFRC2DA and removed RA, RB and RC. However when ever I try to plug in a thumb drive, it gives me error 34. I have a freshly formatted thumbdrive with just FF.CFG and IMG.CFG. When I plug it in it also creates the empty IMAGE_A.CFG file. What do you have on your thumbdrive? Do you have any jumpers installed? It might be because I don't have a working thumbdrive setup yet but also when I press the "Hard Copy" button on the scope, it tells me that the "File System Media is Missing". |
Another success story (TDS3032B) - just added a quick guide based on this thread and other sources: https://github.com/andrewpono/TDS3000-Series-Gotek-FlashFloppy |
Thanks, I also success With only RA removed, lecroy didn't seem to recognize the replacement, even if I changed discs (.img) with left and right buttons. |
Thanks to all for this informative thread, it really helped me. |
Another success on TDS3032. Some road blocks, but eventually all solved. Here are the brief procedures.
|
@kkwannyc I've pored through your writeup and tried to glean from your pics here and on VOGONS what your jumper setup might be... e.g., you have JE/JD/S1 jumped in your picture above but I can't tell from the pics on VOGONS because the Gotek is closed up. I'm trying like hell to get the same Artery DU26 working on my ThinkPad 560 AND 570. I'm getting a green LED during POST but "Operating System not found" on known, good images. Would you mind attaching your FF.CFG as well so perhaps we can tag this for (specifically) early ThinkPads with the 26-pin external connector? |
@hisink Thanks for the clear instructions. Is there a need to put back RA/RB/RC and any of the jumpers after reprogramming? |
They correspond to jumpers JA JB JC on normal Goteks. No need to reinstall those resistors. |
So, only S0 or S1 jumper should remain? I want to make a combo - this slim Gotek + slim floppy drive and put it into the normal 3.5 FDD drive's compartment of my Arabic MSX. I've already designed the board to connect 2 slim drives to a normal 34-pin FDD cable. |
I think so. If JC is actually correct you can get same effect with interface=ibmpc in FF.CFG. But I think shugart is probably correct. |
Thanks, I will test once I get my hands on the device. |
Removed 3 solder jumpers, 2 physical jumpers and flashed the device with FlashFloppy 3.34 firmware. Works like a charm in my Dual-Slim setup. Many thanks for your excellent work, @keirf!! |
I've created an article with links to the repositories. |
Hi everyone. A few years ago, I got an Agilent 54622A oscilloscope for about 100 USD, a real bargain and the truth is that it is an excellent measurement equipment, despite being just 100 MHz. I just want to share the methodology that I followed to be able to use a Gotek floppy emulator. Without having read this issue, I decided to buy the cheapest emulator of this brand (34 USD shipping included), it’s an SFR1M44-DU26 SFRC2D.B version. So, there is no need to buy an expensive type to perform this operation. Step 1. Download FlashFloppy version 3.29 (I think 3.3 could also be used). Step 2. Download the file Artery_ISP_Programmer_V1.5.46 or later and install the driver “Artery_DFU_DriverInstall.exe”. Artery_ISP_Programmer_V1.5.46.zip Step 3. Prepare the PCB for flashing according to the follow images:
Finally click close. You can unplug the USB cable from the computer. Now you can desolder the resistors RA, RB and RC and the USB cable in any case. The memory IC does not need to be preserved. I removed it so I could use it in some other project later on. Don't forget to remove Jumper Boot-3.3V. Finally, it is necessary to prepare you USB device. Give it a format FAT32 and then you need to copy the "1m44_fat12.img" file into the main directory of the USB that you just formatted. That’s it, your scope should be ready to save Images into your USB stick. The file storing time it’s slow but it’s definitely more convenient than to use a Floppy Disk. Cheers and enjoy your measurement! |
Hah, sorry - I really need to log into my personal Github more often. JD/JE/S1 are indeed jumped on the Gotek. I haven't actually used it in the past few months since the OLED display on my custom enclosure just kept dying, and I only use it on my ThinkPad 560E (I am not sure where the cable for my 240 went...) The Gotek (with an STM32) only have the following on its ff.cfg: interface = ibmpc |
Hi all, Just wanted to add my tuppence worth. I've got the SFRC20.B and have successfully re-flashed it and got it working with a Toshiba T1900C laptop - they are very fussy as they use a slightly odd Citizen floppy drive (which has an unobtainium drive belt) and uses RDY on pin 34. I did the following:
Relevant config in the FF.CFG:
And that was it, booted fine. I hope this helps somebody else! |
I don't suppose you have a copy of your ff.cfg? I'm trying to run mine on a ThinkPad 755C. The drive will boot images, but sometimes has trouble switching images. Also, ThinkPad diags and software setup think there's no floppy installed (but swapping in the Teac FD-05HG it came with shows up), but I can still read it most of the time. Problematic areas are writing images with IBM's loaddskf or equivalent, rawrite2 for Linux, and reading the root image and beyond on Linux. I was, however, able to install OS/2 2.1 from start to finish. |
I followed these instructions along with the standard FlashFloppy installation guide and it worked perfectly on a variant SFRC2DA board. Even the OLED screen remained functional. It was to restore a laptop from the 90's, an Epson Action Note 4SLC/33. Thank you! |
Hello everyone, I really need your help. Regarding this floppy drive simulator, can you provide photos of the back of the PCB to determine the direction of certain pins of the 26 pin connector. Thank you, may you all be happy in the long run! |
@bodong001 Will this help? |
Thank you Wierzbowsky ! My problem has been solved. It was caused by me forgetting to close the SO jumper. In addition, according to your prompt, I modified pin 2 of pin 34. Now the oscilloscope is working very happily! Thank you again! |
From pictures and the use of a meter I have created what should be a schematic for the above Artery version SFRC2D.B. Should be the same as the STM version as a couple of smoothing caps make no sense on the Artery but do on the STM105. Gotek.pdf |
@liveboxandy Thanks, I have linked to your repository from the FlashFloppy wiki. |
I sucessful use FF with an 26-pin header Gotek Floppy and use it in my Tektronix TDS3000 series (TDS3012B) Oscilloscope. The PB and the LEDs are at the same pins. I have to remove the resistors RA & RC (normaly 0R), and (not sure if it's nessesary) I also removed RB and the external EEPROM (8pin SOC). The PCB No. of the GOtek is SFRC2D. Model: Slim drive - SFR1M44-DU26 GOTEK.
Thx for the great project!
The text was updated successfully, but these errors were encountered: