AT32F435 fw 3.36 hangs on specific directory

[lyzanxia]

I think I am obviously doing something wrong...
But when I flash 3.36 on my AT32F435 gotek, it works fine until next reboot (and the image_a file is getting created).
The oled garbles and I see the drive light flicker, but nothing gets read. If I delete image_a, everything works again until next reboot.
Flashing back to 3.35 fixes everything.

Strapped the MOR jumper, but do not know which one the MCU jumper is?
(Put interface amiga and drive delay 500)..

[keirf]

IMAGE_A gets created whenever a new disk image is selected on the Gotek.

You might have to give more details. I did a quick full flash to 3.35, and then updated to 3.36, and selected a few image files on my USB stick. No problems.

So what were your steps? What is your FF.CFG? Etc etc

[lyzanxia]

I did some more troubleshooting. If I change interface from shugart to amiga in ff.cfg I experience these problems.
Tried different USB sticks. Have attached the ff.cfg. If needed I can make a video of the problem.

Steps where upgrade from 3.34 to 3.36, changed interface shugart to amiga (had motor delay 500 already, since I had MOR already strapped). On first power on/off of the Amiga after flash, display show flashfloppy+ 3.36 and thereafter garbage on screen and gotek green light flickers a few times.

Sorry I misread "MCU jumper" as in : "Requires AT32F435 "MCU and MOR jumper strap".. :)

FF.txt

[keirf]

Interesting. This is just while running the Gotek as DF0 in Amiga Workbench? What Kickstart version?

[lyzanxia]

Yes, it is the only drive in the amiga (df0).
Just powering up, gives a garbled oled display and gotek drive light flickers a few times and then kicks up the kickstart screen.
Here is a (bad) video of the display after powering up, first time it shows the directory (91 is the year of megademo dir), I then reset again and it show garbage..

kickstart is 1.3, rev6a motherboard.

gotek.mp4

[keirf]

Oooook. So, no high-density (1760kB) ADF images here? We're just talking 880kB images, and as soon as you select an image at Kickstart screen, badness happens? Like, you can't even boot an image using 3.36, at all?

[keirf]

And jumpers at S0 and MOR only? Nothing at JC for example?

[keirf]

I am running 3.36 on an AT32F435 Gotek with jumpers at MOR and S0. I am running with your FF.CFG. And I have a couple of bootable 880kB (double density) ADF images: one in the root, and one in a folder called 91.

I am running as DF0 on an A500 running KS1.3.

I can reset the Amiga and select images, over and over, and it works okay for me.

Can you think of any differences in your setup? For example, do you have a particular USB stick setup? Deep folder hierarchy?

I will also add that resetting the Amiga should not directly affect the Gotek. The Gotek doesn't get reset by Amiga reset. In fact the Amiga reset line is not physically connected to the Gotek.

[lyzanxia]

Yay :-) .. thanks for thinking with me.

[keirf]

Ok it was a straightforward nasty bug introduced in v3.36. Any read-only file would provoke it when interface=amiga. Thanks for helping to track it down!

[keirf]

Could you try the firmware linked here: https://github.com/keirf/flashfloppy/suites/8835715192/artifacts/402639062

It has some other fixes too. You have to be logged into GitHub for the link to work.

Thanks!

[keirf]

Should now be fixed in v3.37. Please test.

[lyzanxia]

Yes, works perfect now. It's fixed. Thanks!