Flashing a newly built ZoomFloppy

[Luca]

HI all,

  just wanted to give a heads up as I haven't found this info explained around nor a clear indication of a how-to if you are in this case scenario (please bare with me and check the end): if you just built a Flashfloppy from scratch like me and you need to flash the xum1541-ZOOMFLOPPY-v08.hex file first time (so Atmel32U2 in DFU mode) and are under Windows 10/11 you will need first to have the Atmel32U2 DFU driver installed. This can be done using the well known ZADIG utility (https://zadig.akeo.ie/). However to allow the xum1541cfg.exe utility to correctly detect the Atmel32U2 in DFU mode you need to install the libusb-win32 driver with ZADIG, not the default WinUSB one else the xum1541 DFU device detection will fail as it relies on this model. Once you have installed the libusb-32 driver you can run the "xum1541cfg.exe update xum1541-ZOOMFLOPPY-v08.hex" from shell/command line and it will detect and flash the Atmel after which the device will disconnect/reconnect and will be detected as "xum1541 floppy adapter (ZOOMFLOPPY)" (and the activity LED should turn off).

   At this point Windows 10, after having pointed the new device to the opencbm-ZoomFloppy-2.0-i386\windrv drivers folder, will still fail to load the drivers as they are not digitally signed. Again use ZADIG and repeat the above process selecting the libusb-32 driver and let ZADIG do it's work. After this is complete you should have a functional zoomfloppy device. To check after having donwnloaded the latest OpenCBM build from Soucreforge (https://sourceforge.net/projects/opencbm/files/opencbm/) which at this time is 0.4.99.104 and unpacked it, you first need to install the necessary files which can be done through the install.cmd script (or manually if you know your way around). Then you can run "cbmctrl detect" command from the opencbm subdirectory (under program files if you installed it there). If all is good you shouldn't get any errors and the Zoomfloppy activity LED should flash.

P.S. it's a but cumbersome and might be confusing to get around the sourceforge and github repos (and some other referenced sites with outdated links) as they are both maintained but not apparently synched (sourceforge appears to have more recent binaries after some further checking). Pity there isn't a clear reference website with the latest links, how tos and case scenarious. I put together what I could by reading here and there and trying to work around the information also based on my experience so this might not be the best way to set a "virgin" Zoomfloppy but it's the only way I found to get mine working. I later found the latest sourceforge repo had an updated installation for Windows x64 versions and the INFer utility which should get around the above ZADIG workaround (I haven't tried it as I had resolved the thing as explained abouve). If the above isn't the best way please follow up on this to update anyone who reads this list.

Reference sites (in order of relevance):

https://sourceforge.net/projects/opencbm/files/opencbm/

https://github.com/go4retro/ZoomFloppy

http://root.org/~nate/c64/xum1541/

https://www.youtube.com/watch?v=rdAzAIPkbf4&t=346s

Cheers

[Spiro Trikaliotis]

Hello,

* On Sat, May 10, 2025 at 12:54:30PM -0700 Luca wrote:

> (so Atmel32U2 in DFU mode) and are under Windows 10/11 you will need first to
> have the Atmel32U2 DFU driver installed. This can be done using the well known
> ZADIG utility (https://zadig.akeo.ie/).

[...]

>    At this point Windows 10, after having pointed the new device to the
> opencbm-ZoomFloppy-2.0-i386\windrv drivers folder, will still fail to load the
> drivers as they are not digitally signed. Again use ZADIG and repeat the above
> process selecting the libusb-32 driver and let ZADIG do it's work.

As I already told you at
https://www.forum64.de/index.php?thread/155050-zoomfloppy-aufgebaut-aber-wie-den-atmega-flashen/&postID=2275310#post2275310,
this is not correct.

Just install the OpenCBM package (v0.4.99.104 or newer), and the driver
for the DFU mode as well as the ZF mode will be installed *and*
digitally signed!

You do not need to use ZADIG on your own!

> After this
> is complete you should have a functional zoomfloppy device. To check after
> having donwnloaded the latest OpenCBM build from Soucreforge (https://
> sourceforge.net/projects/opencbm/files/opencbm/) which at this time is
> 0.4.99.104 and unpacked it, you first need to install the necessary files which
> can be done through the install.cmd script (or manually if you know your way
> around). Then you can run "cbmctrl detect" command from the opencbm
> subdirectory (under program files if you installed it there). If all is good
> you shouldn't get any errors and the Zoomfloppy activity LED should flash.

If you had read the official documentation and not relied on some dudes
that gave you advice, you would have know this and would not need to
find it out.

> P.S. it's a but cumbersome and might be confusing to get around the sourceforge
> and github repos (and some other referenced sites with outdated links) as they
> are both maintained but not apparently synched (sourceforge appears to have
> more recent binaries after some further checking).

Sourceforge is used *only* for the binaries.

Where are the outdated links? It would help if you mention which links
are wrong, so they can be fixed.

> Pity there isn't a clear
> reference website with the latest links, how tos and case scenarious.

There isn't one?

https://spiro.trikaliotis.net/opencbm which also has a link to the manual: https://opencbm.trikaliotis.net/

> I put
> together what I could by reading here and there and trying to work around the
> information also based on my experience

[...]

Yes, and you also ignored my advice more than once.

> If the above isn't the best way please follow up on this to update
> anyone who reads this list.

I have just done this.

Regards,
Spiro

--
Spiro R. Trikaliotis
https://spiro.trikaliotis.net/

[Luca]

    HI Spiro,

   thanks for the follow up. However I don't know what you mean by "I already told you at" at that german forum (I'm italian) - it's the first time I see this - maybe you mixed me with someone else?

   Regarding the links, I merely used google to search what I could, so I posted the relevant links at the bottom of my post - I have not got hits for your https://spiro.trikaliotis.net/opencbm at all in the search, glad that you pointed this out. Maybe as your sourceforge and git repos have a higher index hit you could add this link there too for a back reference to your site for others.

   Anyhow thanks for your feedback and work.

   Luke

[Spiro Trikaliotis]

Hello Luca,

* On Sat, May 10, 2025 at 02:29:28PM -0700 Luca wrote:

>    thanks for the follow up. However I don't know what you mean by "I already
> told you at" at that german forum (I'm italian) - it's the first time I see
> this - maybe you mixed me with someone else?

I am sorry. I was under the impression that you were the one with whom I
communicated on that forum. You had exactly the same topic, the same
issues and the same solutions like the one there.

I told him what to do, but he counted more on others than me. That's why
I reacted so harsh.

I will try to keep more calm in the future. I did not want to answer so
harsh, and I think time will help me not to do it again.

Again, I am sorry for my response.


You came here to share some insights, and I reacted this way. That's not
how it should be!

>    Regarding the links, I merely used google to search what I could, so I
> posted the relevant links at the bottom of my post - I have not got hits for
> your https://spiro.trikaliotis.net/opencbm at all in the search, glad that you
> pointed this out. Maybe as your sourceforge and git repos have a higher index
> hit you could add this link there too for a back reference to your site for
> others.

I will have a look how this can be done.

Best regards,