Replies: 45 comments
-
I just copied and pasted those IMG.CFG entries into my IMG.CFG and created empty 256256-byte and 1025024-byte IMG files. They loaded up fine; no Error 31 here. |
Beta Was this translation helpful? Give feedback.
-
May there be something wrong in the FF.CFG file? |
Beta Was this translation helpful? Give feedback.
-
Still it doesn't work here.
Any hints? |
Beta Was this translation helpful? Give feedback.
-
Only place IMG.CFG and the IMG files themselves on your stick. Reset flash by holding both buttons a few seconds after power on with no stick inserted. |
Beta Was this translation helpful? Give feedback.
-
Further, basic question, but are you certain your IMG files are exactly 256256 bytes and 10251024 bytes? |
Beta Was this translation helpful? Give feedback.
-
OK, so here we go with only these two files: (no FF.CFG file)
I used a BASCOM image file. Inserting stick -> E31 The write indicator on the 3digit 7segment led display (right digit, topmost line) flashes during write operations. Before this test, using the FF.CFG(*) file, writing to images (1,44MB, 1,2MB, 720KB) worked. Should I run some tests with the logging firmware? If so, which tests? Christian (*) I used this FF.CFG file:
|
Beta Was this translation helpful? Give feedback.
-
Try putting FF.CFG back and see what happens? |
Beta Was this translation helpful? Give feedback.
-
Hmmm ok it must have something to do with |
Beta Was this translation helpful? Give feedback.
-
Can you please try the automated build artifact linked here: https://github.com/keirf/FlashFloppy/actions/runs/452833031 The bug was that IMG.CFG is not parsed in indexed mode. Actually it was deliberate / by design but I have no idea why I did that!! |
Beta Was this translation helpful? Give feedback.
-
I flashed the new build. Now all defined image types read correct. :) |
Beta Was this translation helpful? Give feedback.
-
You have two different FF.CFGs listed above. They differ in settings for |
Beta Was this translation helpful? Give feedback.
-
Otherwise the tiny 128-byte sectors may be slow to write back on your USB drive. I ought to batch them but I don't, currently. You may have better luck with a different USB drive. Also |
Beta Was this translation helpful? Give feedback.
-
OK, so I changed these three lines in FF.CFG:
Also, I moved to a faster USB drive (about 18MB/sec). May this also be a issue with FM vs. MFM? |
Beta Was this translation helpful? Give feedback.
-
Do the default FF.CFG options work with other image types? Those would be:
Please use these options if they generally work with your host system, and see if they then work with SSSD too. If not, it is worth gathering a FFLOG.TXT file using alt/logfile firmware, to log what happens when you try to write to a SSSD image. |
Beta Was this translation helpful? Give feedback.
-
With these options I get a 'delayed write error'. |
Beta Was this translation helpful? Give feedback.
-
That's good news. :) |
Beta Was this translation helpful? Give feedback.
-
There is another thing that looks odd to me: |
Beta Was this translation helpful? Give feedback.
-
The data certainly is written by the host and not conjured up by FlashFloppy. If writes are generally working, and your IMG file originally is blank (say all zeroes), then you can be very sure that the formatting data is coming from CP/M. So the question is: Why 3F in this case? :) |
Beta Was this translation helpful? Give feedback.
-
You could also look in FFLOG.TXT after a format operation and confirm you see no weird warnings (eg CRC errors) and just normal write logging. |
Beta Was this translation helpful? Give feedback.
-
The logfile looks good to me. So what is different from a normal write during formatting? The used FDC chip should be a Mitsubishi M5W1793-02P, which should be compatible to the WD1793. FFLOG.TXT:
|
Beta Was this translation helpful? Give feedback.
-
Another try with activated WPCom... I think that's how it looks when things go wrong:
|
Beta Was this translation helpful? Give feedback.
-
I think it depends on the FDC but there is either a Format Track or Write Track command. Either way the host has control over the sector data, it's not prescribed by the FDC. |
Beta Was this translation helpful? Give feedback.
-
WPCom = write precompensation? Doesn't seem to be liked :) Of course FlashFloppy does not need any precomp. |
Beta Was this translation helpful? Give feedback.
-
Of course not. :) |
Beta Was this translation helpful? Give feedback.
-
Made another try with a Siemens SAB1793-02P FDC Chip. |
Beta Was this translation helpful? Give feedback.
-
I may have to explicitly handle precomp in that case. It is used quite generally including on 3.5/5.25 micro-diskette systems and I've had no problems before. Either the precomp here is very extreme, or we've still got the bitrate a bit wrong, and precomp puts us "over the edge" for correct decoding. |
Beta Was this translation helpful? Give feedback.
-
Is it feasible for you to get scope or logic analyser traces of WDATA when precomp is enabled? On a scope just a few bit times could suffice. |
Beta Was this translation helpful? Give feedback.
-
By the way -- although FDC controls when precomp is applied, on these earlier systems the actual time shifting is not integrated into the FDC. So it is no surprise that switching the FDC chip had no effect. |
Beta Was this translation helpful? Give feedback.
-
I could use LA and scope, but I don't think this is worth it. |
Beta Was this translation helpful? Give feedback.
-
Issues now fixed in official release v3.23 |
Beta Was this translation helpful? Give feedback.
-
Hi all,
yesterday I flashed a Gotek with the latest Flashfloppy F/W, v3.22.
It works fine with usual 3,5" und 5,25" formats on my MFA running CP/M 2.2.
But 2 of the 3 8" formats I would like to use alwas give me error 31.
Even the standard 8" SS/SD format, which I copied 1:1 from the CompuPro example results in error 31.
I created empty files with the corrected file size to start with, which worked for the other formats.
These are the non working formats in my IMG.CFG:
These are the working ones:
This is my FF.CFG:
The only thing, that seems to be common to the affected formats is, that the sector size differs from 512 bytes.
Christian
Beta Was this translation helpful? Give feedback.
All reactions