One more time; Gotek hdx2001 .. Where am I failing here? Thanks! :-)

[KC9KEP]

Hello!

I appreciate the responses that everyone has given me .. but I wonder if I'm doing something proceduraly wrong here ..

I am now flummoxed, gobsmacked and perplexed :-(

Could someone who is familiar with the “Gotek hdx2001” please review my procedure and tell me
if my assumptions are correct? Thanks!

I had ordered a “bare-bones” GoTEK model from Amazon, with just two-push-buttons and LED front panel display.

1.) As the GoTEK is received, its boot loader needs to be re-flashed with a Windows machine. I used a USB to Serial adapter module. One must set-up the GoTEK jumpers as instructed in the “https://hxc2001.com/docs/gotek-floppy-emulator-hxc-firmware/” manual to flash the GoTEK boot-loader. (Lessons learned, set the module to 5V (not 3.3V) and use a SHORT USB cable to the REAR USB port of my Windows 11 machine). It uploads quite quickly, maybe 2 minutes or so. Then I remove the programming jumpers from the GoTEK.
2.) One is then instructed to install the *.upd firmware program. It's accomplished by loading the *.upd file onto a FAT32 formatted USB stick on my Windows machine. Insert the stick into the GoTEK, hold the two front-panel buttons in, power up the Gotek drive while holding the buttons for 2 seconds, and the *.upt firmware is loaded. No problem.

I've added an OLED display to the GOTEK as well.
Some one mentioned that GoTEK DRIVE-B is OFF by default. One can launch a MENU driven utility in the GoTEK by pressing the front panel buttons. I turned "ON" drive B.

I set the GoTEK jumper block for DRIVE-B.

I boot from my CP/M A: 5.25" drive and want to access the GoTEK which is conneced as my CP/M B: drive.

When I try to log the B: drive ">B: <return>" the GoTEK activity LED comes on as expected, but the system just hangs.

WHAT I AM TRYING TO DETERMINE IS THIS: Are all the required floppy drive settings contained within the *.upd file on the USB stick? (There is a custom firmware editor available for that file.) Is that the only file that needs to be on the USB stick in order for the GoTEK to operate?

Of course the OLED display tells me that I have no image files on the USB stick.

FWIW: My target computer is a legacy home-brew Z80 system with 64K ram, running CP/M 2.2

I'm really floundering here ..

Copious thanks!

 

[tradde]

I will be doing almost the same when I get my Gotek. But I know almost nothing about configuring them. But if the OLED says no files that seems suspicious.

 

[KC9KEP]

I will be doing almost the same when I get my Gotek. But I know almost nothing about configuring them. But if the OLED says no files that seems suspicious.

Well, the OLED says there are no files on the USB stick in GoTEK drive .. which I’d expect, because CP/M can’t access it

 

[tradde]

Wouldn't it show if files are there even without trying to access them via CP/M? I'd think it would show what was on the stick. That is its job right, to allow you to select files from the stick by turning the knob. Or images actually.

 

[KC9KEP]

Wouldn't it show if files are there even without trying to access them via CP/M? I'd think it would show what was on the stick. That is its job right, to allow you to select files from the stick by turning the knob. Or images actually.

The only file on the stick is the *.upd firmware. I do not know if this should be visible on the OLED display or not?

 

[cj7hawk]

Gotek will only show files and directories it recognizes.

It will show them even if a computer is not connected.

Common causes of isses:

1. Hooking 12v into the 5v line for the Gotek - Does your gotek get 12v on any pins? Amazingly the GOTEK usually survives and even operates, but the USB will die, and show zero files. Can be verified by putting the USB in a PC and checking if it's alive. Also, some machines swap 12v and 5v, and some even leave the colors in the same place and run 12v through the red and 5v through the yellow ! Be aware of this. (ESPECIALLY WITH 3" drives, where they usually swap the voltage pins )

2. Wrong file extension or bad file. I've found a LOT of Gotek files that simply aren't read... Don't know why. I assume the people who post them don't test them.

3. Wrong image on the Gotek. A lot of people just get the latest image without checking if it supports the files or the application. This caught me out and so I make a point of knowing that I'm using the correct image when reflashing the Gotek.

A gotek will power up and allow files to be selected even if the Gotek is not connected to anything other than power.

 

[twolazy]

Which cpu is the gotek using? There are 3 different cpu's now, and vendors not knowing what they are selling. I ordered what I thought was the STM CPU, but got one with an Artery CPU instead. I had similar problems trying to use serial to flash it, and gave up and got a male to male usb cable and flashed perfectly first try.

​

 

[Svenska]

Are all the required floppy drive settings contained within the *.upd file on the USB stick?

Maybe? The *.upd file contains the software running on the Gotek itself.
The image files may contain their format information, but the software also contains defaults for some formats.

Is that the only file that needs to be on the USB stick in order for the GoTEK to operate?

No. After the Gotek has been updated, this file is not needed at all. You only need image files to operate.
A disk drive without media isn't very useful, and the image files are the media.

Note that changing the image file can also change the floppy hardware type (i.e. if you insert a 5.25" DD disk, your drive becomes a 5.25" DD drive; if you insert a 3.5" HD disk, your drive becomes a 3.5" HD drive). This is why you need a correct image file to start with.

Of course the OLED display tells me that I have no image files on the USB stick.

You need to add some image files and select them. Otherwise, you only have an empty floppy drive of unspecified type.
I don't know if HxC can create image files itself, FlashFloppy can't.

FWIW: My target computer is a legacy home-brew Z80 system with 64K ram, running CP/M 2.2

You need to provide some rather detailed information about the floppy disk format for us to help.

 

[ldkraemer]

KC9KEP,
You need a few files on the USB to scroll through. You scroll through the list, select one that you
want to boot or use, then if booting you need to RESET the computer to read in the Directory from
the Floppy (or selected Image). Then, you should be able to access the files on A: or B:.

While I've not use a GOTEK with my KAYPRO, I do have a DOS Version that works on my
DESKTOP, so I know the process to properly access the files.

Any time you INSERT a DIFFERENT Floppy in a CP/M Computer, you need to do a HARD RESET,
or CNTL C to read in the new Floppy's Information. If you do not do this you will Clobber the
Floppy when you write the previous Floppy's directory information on the newly inserted floppy.

If you can image your Boot floppy with Teledisk, or Imagedisk I should be able to make you a *.hfe
file that should boot from the GOTEK.

Larry

 

[jafir]

I've never used the HXC firmware on gotek, I've only used their software for converting images. Is their gotek firmware better than flashfloppy in some way? What about their own hardware floppy emulators, are they better than the gotek stuff?

 

[tradde]

The only file on the stick is the *.upd firmware. I do not know if this should be visible on the OLED display or not?

Ok, I thought you had put some files on it. But it still should show up as the B: drive. But wouldn't it still need to have an image file on it to show up?

 

[KC9KEP]

KC9KEP,
You need a few files on the USB to scroll through. You scroll through the list, select one that you
want to boot or use, then if booting you need to RESET the computer to read in the Directory from
the Floppy (or selected Image). Then, you should be able to access the files on A: or B:.

While I've not use a GOTEK with my KAYPRO, I do have a DOS Version that works on my
DESKTOP, so I know the process to properly access the files.

Any time you INSERT a DIFFERENT Floppy in a CP/M Computer, you need to do a HARD RESET,
or CNTL C to read in the new Floppy's Information. If you do not do this you will Clobber the
Floppy when you write the previous Floppy's directory information on the newly inserted floppy.

If you can image your Boot floppy with Teledisk, or Imagedisk I should be able to make you a *.hfe
file that should boot from the GOTEK.

Larry

Larry,

I do have Dave Dunfield's Image Disk program. It creates *.IMD files. Is that what you could use to create an .hfe file? Can I attach a *.IMD file to a message to you on this forum? Should I use a boot floppy with system tracks AND files or just system tracks? Thanks!

 

[Svenska]

I do have Dave Dunfield's Image Disk program. It creates *.IMD files. Is that what you could use to create an .hfe file?

Yes.

Can I attach a *.IMD file to a message to you on this forum?

Yes.

Should I use a boot floppy with system tracks AND files or just system tracks?

You get a copy of that disk in HFE format. If you want an empty floppy, you attach an image of an empty floppy.
Or you can simply attach both - doing two files isn't really different from doing one.

 

[KC9KEP]

Yes.


Yes.


You get a copy of that disk in HFE format. If you want an empty floppy, you attach an image of an empty floppy.
Or you can simply attach both - doing two files isn't really different from doing one.

Great .. Let's see if this works. The file is "MBAS.IMD" that I have zipped.

 

[Svenska]

I have no idea if this file will work, but it's worth a try.

 

[KC9KEP]

Thank you greatly, Sir ..

OK, I've placed the .hfe file on my USB stick. When I boot up the system, I momentarily see "HxC Floppy Emu v5.2.1.2a".

Shortly after I see; "MBAS.HFE Choose a file" (Not sure how to "choose a file" .. I tried pushing buttons, but I don't think I accomplished anything :-(

When I boot from Drive A, I see; "MBAS.HFE T:000/040 S:0" but this changes from "T:000/040 S:0" to "T:000/040 S:1" and back to "T:000/040 S:0" as drive A boots.

When I try to access drive B:, it says: RA T:000/040 S:0" and hangs.

Does any of this make any sense? Not sure where to look next .. Maybe some error codes deciphering exist somewhere?

But thanks again .. at least the GoTEK can see a file on the USB stick ..

 

[mark0x01]

I have the USB one with just the 7seg display, and it took a while to figure it out.
I don't use optional Drive B - a second emulated drive, I just set the jumper to S0 to make it the first floppy, as I'm booting from it.
I use index mode firmware, and have the HXCSDEF.CFG file and name the files DSKAxxxx (0000-9999).
There must be a suitable file on usb and selected for it to see a drive, and the file must have the format that is correct for the computer even if it is an blank floppy.

 

[GeoffB17]

The results you show could well be correct.

The idea of an image is that the image file appears to the computer exactly as a real disk would do, and function exactly as a real disk would do.

The Gotek firmware/software should know which image format you're using (.hfe here) and provide all the required translations to allow the above.

If the system is going to A:, and is hoping to boot, then I'd expect this it would be looking for track 0 and expecting to find boot code which it could load and then run. As the disk image is empty of valid data, this will fail. But it seems to be trying.

You mention B: as well, is this using the sort of 'swap' process that many computers had so that you could use the single drive as A: or B:? You would not normally be booting from B:. BUT, if you HAVE booted then the system may well try to 'log' onto B: and look for a directory, but this would usually be a little further into the disk?

By the way, as far as I can tell, the IMD system can do nothing with the .hfe image. the IMD software may well be able to read your original floppy, and create an IMD image (you can but try), but that's it (unless there's a MUCH later version of the system that the one that I've used).

Sorry to report that my old PC passed all the DD tests, but seemed to fail the test for SD. Well, that's my interpretation of the results.
Not sure if the result for READ was different to WRITE, maybe you need to WRITE ONLY?

The SAM system can I believe convert an .hfe image into various other things, but seems NOT to be able to create an .hfe image. The software re the HxC emulator CAN do this though. I do have some .hfe image files, maybe could use the emulator on one of those to empty the image? BUT, the images I have will not be the correct format internally for your computer??

Geoff

 

[ldkraemer]

IMDA shows your IMD file as a 40 track Image, with 2 Heads and written at 300 kbps.

IMageDisk Analyzer 1.18 / Mar 12 2012
IMD 1.18: 28/03/2019 17:48:01

MBASIC

Required cylinders: 40
Required heads : 2
Data rate : 300kbps
Est. maximum track: 6475 bytes

Possible drives/options to write MBAS.IMD :

5.25" QD 80-track
Double-step: ON
300 kbps -> 250 kbps

5.25" HD 80-track
Double-step: ON

3.5" DD 80-track NOTE: *1
Double-step: OFF
300 kbps -> 250 kbps

3.5" HD 80-track NOTE: *1
Double-step: OFF
300 kbps -> 250 kbps

*1 40 track image will use only first 1/2 of 80-track drive.

And IMDU shows the following:

IMageDisk Utility 1.18 / Mar 07 2012
IMD 1.18: 28/03/2019 17:48:01

MBASIC

Assuming 1:1 for Binary output
0/0 300 kbps SD 16x128 = 2048 = 0x0800
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
D D D D D D D D D D D D D D D D
HD: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0/1 D D D D D D D D D D D D D D D D
1/0 300 kbps DD 30x128 = 3840 = 0x0F00 * 78 Tracks
14 27 10 23 6 19 2 15 28 11 24 7 20 3 16 29 12 25 8 21 4 17 30 13 26 9 22 5 18 1
D DFFD DFFD D D D DFFD DFFD D D D DFFD DFFD DFFD D DFFD DFFD DFFD D D
HD: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
1/1 DE5DE5DE5DE5DE5DE5D DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5D
2/0 D D D D00D D DE5D D D D00D D00D D D D D D D00D D D D D D D00D D00DE5
HD: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
2/1 D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D
3/0 D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D
HD: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
3/1 D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D
4/0 D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D
HD: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
4/1 D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D
5/0 DE5D D D D D D D D D D D D D D D D D D D D D D DE5D D D D D D
HD: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
5/1 D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D
6/0 DE5D D D D D D DE5D D D D D D DE5D D D D D D DE5D DE5D D D D DE5D
HD: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
6/1 D D D D D DE5D D D D D D DE5D D D D D D D D D D D D D D D DE5D
7/0 D DE5D D D D D D DE5D DE5D D D D DE5D DE5D DE5D D DE5D DE5D DE5D D D
HD: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
7/1 DE5D DE5DE5DE5DE5DE5DE5D DE5DE5DE5DE5DE5DE5D DE5D DE5DE5DE5DE5D DE5D D DE5DE5DE5DE5
8/0 D DE5D DE5D DE5D D DE5D DE5D DE5D D DE5D DE5D DE5D D DE5D DE5D DE5D DE5D
HD: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
8/1 DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5
..
..
..
..
..
..
33/0 DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5
HD: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
33/1 DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5
34/0 DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5
HD: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
34/1 DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5
35/0 DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5
HD: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
35/1 DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5
36/0 DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5
HD: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
36/1 DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5
37/0 DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5
HD: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
37/1 DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5
38/0 DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5
HD: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
38/1 DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5
39/0 DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5
HD: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
39/1 DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5DE5
80 tracks(40/40), 2372 sectors (1992 Compressed)

Why are you writing at 300 kbps?

With the directory at 0x1F00 = 7936 Decimal
00001F00 00 4D 42 41 53 49 43 20 20 43 4F 4D 01 00 00 3E .MBASIC COM...>
00001F10 02 03 04 05 06 07 08 09 0A 0B 0C 0D 00 00 00 00 ................
00001F20 00 50 49 50 20 20 20 20 20 43 4F 4D 00 00 00 3A .PIP COM...:
00001F30 0E 0F 10 11 00 00 00 00 00 00 00 00 00 00 00 00 ................
00001F40 00 55 54 49 4C 49 54 59 20 42 41 53 00 00 00 1D .UTILITY BAS....
00001F50 12 13 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00001F60 00 55 54 49 4C 31 20 20 20 42 41 53 00 00 00 1D .UTIL1 BAS....
00001F70 14 15 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00001F80 E5 63 6C 65 61 72 20 20 20 42 41 53 00 00 00 01 .clear BAS....
00001F90 16 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00001FA0 00 43 4C 45 41 52 20 20 20 42 41 53 00 00 00 01 .CLEAR BAS....
00001FB0 17 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00001FC0 00 55 54 49 4C 32 20 20 20 42 41 53 00 00 00 17 .UTIL2 BAS....
00001FD0 18 19 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00001FE0 E5 E5 E5 E5 E5 E5 E5 E5 E5 E5 E5 E5 E5 E5 E5 E5 ................

cpmtools gives the directory listing as:

larry@debian:~/IMD-118$ cpmls -f sup5 -D MBAS.RAW
     Name    Bytes   Recs  Attr     update             create
------------ ------ ------ ---- -----------------  -----------------
CLEAR   .BAS     1K      1    
MBASIC  .COM    24K    190    
PIP     .COM     8K     58    
UTIL1   .BAS     4K     29    
UTIL2   .BAS     3K     23    
UTILITY .BAS     4K     29    
    6 Files occupying      1K,     297K Free.
larry@debian:~/IMD-118$

Is this really a DS/DD 5.25" Floppy that should be written at 250 kbps?


Larry

 

[KC9KEP]

Larry ..

I CANT BELIEVE IT! yes! This is a major screw-up!
I didn’t even know this was possible to write at 300kbps on a 360K drive ..
I rewrote the formatter and BIOS that was intended for an 8” drive (back in 1985 or so) to work on 5” media.
It seemed to work, so I never researched it.
I’m using a Western Digital 1793 and 1MHz clock oscillator.
There must be a setting somewhere that is controlling data rate in the formatting program?
I’ll have to locate my source code and figure out how I assembled it and look for some 1793 command that did this .. maybe my BIOS in junk too.
I used this sys thru college to write reports, etc.
Now that I think about it, it makes sense that IMD could only read my floppies on a 1.2M drive while double stepping ..