2.8" QD Disk Emulation

[Jeff]

EDIT : HxCFEUSB.UPD removed.

The attached version should improve the long blank write support.

Try it with the previous post to_write_and_read2.zip images and post back the files.
(and ignore the previous firmware, the attached one replace it).

[AMSynths]

Latest fw...
we will get there!

EDIT : DSKA0000.zip removed.

[AMSynths]

Latest fw...
Save to each file...verify error each time

We will get there!

[Jeff]

Latest fw...
Save to each file...verify error each time

We will get there!

EDIT : I just notice that i have mix-up the firmware UPD file name in the 2 lasts fw updates -> Have you though to remove the old UPD file on the usb stick before updating ? (You should currently have the v3.4.4.6a version code. To see it, remove the stick, press both buttons, choose 'F')

- Are you able to read some of these disk images with a load attempt ?

- Is the Roland still does 2 write attempt ? (a trace with the Write gate + the ready signal @2S / div may help)

- Does the "verify error" message appears right after the write, or is there 2/3 seconds delay ?


fyi all disks images are valid : the tracks are ok and the CRCs are valid... :

valid.png (19.05 KiB) Viewed 6535 times

Can take some new traces ? :

I need these following screens with the Write gate and the write data line :
-> at the first Write gate rising edge (edge centered on the screen @ ~20uS/div)
-> at a "glitch" Write gate falling edge (edge on the left on the screen @ ~100uS/div) (the whole glitch should fit the screen)
-> at a "glitch" Write gate falling edge (edge centered on the screen @ ~20uS/div)
-> at a "glitch" Write gate rising edge (edge centered on the screen @ ~20uS/div)
-> at the last Write gate falling edge (edge centered on the screen @ ~20uS/div)

What i want to check is the write data pulses spacing under the write gate glitches and at the write start and end.

And something we have never checked : Is the RST signal used during the write/read ?

(I want to avoid to have to decompile the S10/S220 ROM ...
And btw no way to find the QD controller datasheet used in the Roland machines... Have you it?)

[AMSynths]

Hi,
I overwrite the old fw before loading. Its 3.4.4.6
0004 and 0005 load ok rest are Illegal QD
Verify Error is displayed at the end of the read back in

I will do some traces tomorrow
I cant find the QD controller datasheet either
I have disassembled the S10 OS for a display change in the code, its look structured but I havent looked for how the I/O works

[Jeff]

A good news : I just got the confirmation that the v3.4.4.6 is working perfectly with the Akai S612 / MD280.

[AMSynths]

That is good news...now the traces

[AMSynths]

traaces

[AMSynths]

traces

[AMSynths]

Its the verify read back that's failing here.
First activity is the Check QD, then the Write and then the read verify -which fails at the end

[Jeff]

Its the verify read back that's failing here.
First activity is the Check QD, then the Write and then the read verify -which fails at the end

Thanks !
The oscilloscope sampling rate is too low to be able to decode the write data line. Could you increase it at 5MSa/s when you are at 100uS/20uS per div ?
Anyway the write gate glitches duration appears to match to the blank recorded in the .QD files, so i think that this part is working properly in the current firmware.

Is the the Motor On line always during the write/verify cycle ?

I am now unsure what cause this "verify error" while you can read back the disk right after.
Btw why the Roland QD drive appears to have a 4.5s ready window while the MO5 and Akai QD drives have a 5.4s window ? I though that Roland and Akai machines shared the same QD drive ? Maybe the issue is just related to some ready window/read duration timing miss-configuration.
What is the Roland QD drive whole read/turn duration and ready window duration (at the millisecond level) ?

[Jeff]

Can you write to this ? :

EDIT : DSKA0003_Akai_formatted.QD.zip removed.

Do you get a "verify error" and could you read back the image after ?

[Jeff]

The HxC Gotek firmware have been tested on a MD-280 / Akai 612 : This works "out-the-box".

I have added the Akai QD format to the HxC QuickDisk toolkit software :

https://github.com/jfdelnero/HXCFE_QuickDisk_Toolkit

You can currently convert your Akai QD disk image to wav. I can easily add the wav->Quickdisk image converter too if you are interested by this feature.

[AMSynths]

Hi
I used the Akai QD.

Read fails with Illegal QD
I can write to it but Verify Error as usual
I can read the sample bank ok

Yes please add the Wav to QD feature, very useful!

Any thoughts on next steps ? I will measure the read duration and ready window.
We know the data is correct and can be read, so it must be how the verify read is working, somehow chopping some data out maybe.

[AMSynths]

something is wrong...the traces show 3 reads on Save. 3rd read is after the Verify Error.
Also cant Load from any banks now..