I've found out, that it currently doesn't work on my STE, where I have HD/DD mod.
When I insert a valid image, it always says 'Data corrupted' on the STE, it's like when I remove a sticker from my HD/DD window on the real floppy. I need to investigate on that one. On my STFM it works fine (no HD/DD mod there).
There has been also reported some issue that when the new CE_DD driver is loaded, people seem to have trouble accessing drive A:, even if it's the real drive - the new CE_DD might be blocking floppy access or something.
I've created a tool for testing the floppy access, and for that I would suggest updating your device - the test is on the config drive (2016-01-03).
How to test it:1.A)
Decide if you want also sector data validation, for that you need TEST floppy image. In that test the testing app it will seek to a floppy sector, and also check if the data contain the right marker. To insert that TEST floppy image, open the browser, point it to IP of your CE device (e.g. 192.168.0.100), click 'Floppy' and there you should press 'Insert FLOPPY TEST image'.1.B)
If you want to test the floppy interface without data validation, just insert any floppy image into slot #1 and activate that slot.2)
have the floppy cable connected to your CE device. 3)
Turn on the CE device, wait, turn on ST(e). From config drive run the 'CE_TSTFD.PRG' app, and use option R/N/S for TEST floppy image (option A above), or use options A/D/E for any image (option B from above). To terminate the test, just press 'q' or 'c' key during the test.
It should look something like this when running:
You should have all '*' if everything is perfect, some 'L' might appear and it shouldn't be that bad (it means ST read that sector with a retry, not on the first time), and if you see '!' or 'D', than it's not very good. If you won't insert TEST floppy image but you will use tests for TEST floppy image, you will get lots of 'D's, but that's not an actual error - just use a different test.
You might use this on different machines to see if it behaves differently. You might even use this under STEEM / HATARI, run the sequential test ('E') with the problematic floppy image, and at the end of sequential test it will display a checksum word. You can run the same test with the same floppy image with CE and real ST, and see if the sequential test will show the same checksum word as in emulator. If not, this might be caused by:A)
bad data reading, but if you get all '*' in the sequential test, it might not be this case, but instead...B)
bad floppy image reading / decoding in Main App (on Raspberry) - there might be an error in decoding the floppy image, or...C)
some special image geometry - I'm mostly testing this whole with 2 sides / 80 tracks / 9 sectors per track, so a different geometry might result in some issues, but I'm not sure about this one D)
image geometry would be handled fine, but there's some other issue with sector numbering / sector padding / sector order or something like that...
So... If you want, you can try that and see what you will get... And then tell us.