0.4.99.98 Possible Issue

[RETRO Innovations]

Windows 10, 64 bit. opencbm 0.4.99.98. Zadiq install, zoomfloppy works
fine in usage.

But, when I do xum1541cfg, to program new units, I get:

>xum1541cfg
Success. xum1541 now in bootloader mode.
Run your firmware update program now.
USB request for XUM1541 close failed, continuing: libusb0-dll:err
[control_msg] sending control message failed, win error: A device
attached to the system is not functioning.


USB release intf error: libusb0-dll:err [release_interface] could not
release interface 0, win error: The device does not recognize the command.


I have tried on 2 systems, same 1st error (the second error only appears
on my main machine, not the older one)

Jim

--
RETRO Innovations, Contemporary Gear for Classic Systems
www.go4retro.com
store.go4retro.com

[Spiro Trikaliotis]

Hello Jim

* On Thu, Jun 16, 2016 at 06:22:57PM -0500 RETRO Innovations wrote:
> Windows 10, 64 bit. opencbm 0.4.99.98. Zadiq install, zoomfloppy works
> fine in usage.

Do you have the possibility to test with other setups? (i.e. 0.4.99.95,
or Windows 7 or 8, or on 32 bit systems)?


I must admit that I did not test xum1541 cfg in a while.

I will try to have a look this night (if time permits).

Regards,
Spiro.

--
Spiro R. Trikaliotis
http://www.trikaliotis.net/

[RETRO Innovations]

On 6/17/2016 1:30 AM, Spiro Trikaliotis wrote:
> Hello Jim
>
> * On Thu, Jun 16, 2016 at 06:22:57PM -0500 RETRO Innovations wrote:
>> Windows 10, 64 bit. opencbm 0.4.99.98. Zadiq install, zoomfloppy works
>> fine in usage.
> Do you have the possibility to test with other setups? (i.e. 0.4.99.95,
> or Windows 7 or 8, or on 32 bit systems)?

Can you clarify:

Do you want me to test an older build on the existing Win10 boxes?
Or, do you want me to test the new .98 on my older Win32 Win7 box?

If the former, I have not done so, but I can. It's a Windows 10 Win64
box, and I can install anything you need.

If the latter, I do have a working 0.4.99 Win32 Win7 install, but it's
currently the only one that I have working, and since I just got a new
batch ZFs (which is why the issue is being reported now), I am in
process of programming them. I hesitate to ruin the good install until
I get all of the units programmed.

> I must admit that I did not test xum1541 cfg in a while.

I theorized as much

>
> I will try to have a look this night (if time permits).

It's not a huge rush, as I have an older install that is working.
>
> Regards,
> Spiro.

[Nate Lawson]

xum1541cfg is a bit sensitive to device enumeration. In the first phase, it puts the device in DFU mode (which appears to have worked) and then it waits for it to come up as an Atmel DFU device. It sounds like the USB control message after it’s detached and possibly re-enumerated times or errors out.

Is it a newer version of libusb or the wrapper for the Windows USB that might be different?

-Nate

> --
> You received this message because you are subscribed to the Google Groups "ZoomFloppy Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to zoomfloppy-use...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.


-Nate

[RETRO Innovations]

On 6/17/2016 6:39 PM, Nate Lawson wrote:
> xum1541cfg is a bit sensitive to device enumeration. In the first phase, it puts the device in DFU mode (which appears to have worked) and then it waits for it to come up as an Atmel DFU device. It sounds like the USB control message after it’s detached and possibly re-enumerated times or errors out.
>
> Is it a newer version of libusb or the wrapper for the Windows USB that might be different?

It's 1.2.6, via Zadig, as per Spiro's instructions.

I can run diagnostics, if you tell me what you'd like to see.

Jim

[Spiro Trikaliotis]

Hello,

* On Fri, Jun 17, 2016 at 09:27:56PM -0500 RETRO Innovations wrote:
> On 6/17/2016 6:39 PM, Nate Lawson wrote:

> >Is it a newer version of libusb or the wrapper for the Windows USB that might be different?
> It's 1.2.6, via Zadig, as per Spiro's instructions.

That's the problem.

Zadig installs the driver for the currently connected device.
Unfortunately, the Atmel in DFU mode presents itself as a completely
different device. Thus, there is no driver installed for it.

The .inf file has all USB VID/PID combinations, so everything is
installed together. Zadig does not do this.

This means I have to fix my Zadig install in order to be able to use our
provided .inf file.

In the mean time, the following should help:

1. Put the ZF into DFU mode
2. Now, run Zadig for the "Atmel firmware update device", and install
the driver for it.

Now, you should be able to run the xum1541cfg updater.

[RETRO Innovations]

Hmm, I hate to say this, but I thought of that. I took an unprogrammed
ZF (which is in DFU mode), installed the Zadig driver for that device,
to no avail.

But, I just tried it again, with no luck. It says this:

error: no xum1541 device found
initialization error, aborting

Interesting that it does not say that it is waiting for DFU devices,
like it does on my Win7 install.


Jim

[Nate Lawson]

xum1541cfg should detect that the device is already in DFU mode and say it's just going to skip that step and go straight to programming.

Can you just look at Device Manager and see if the Atmel DFU device shows up and its VID/PID?

-Nate

[RETRO Innovations]

On 6/19/2016 10:29 AM, Nate Lawson wrote:
> xum1541cfg should detect that the device is already in DFU mode and say it's just going to skip that step and go straight to programming.
>
> Can you just look at Device Manager and see if the Atmel DFU device shows up and its VID/PID?

Name: ATmega32U2 DFU
Description: ATmega32U2
VIC:03eb
PID: 2ff0

Jim

[Spiro Trikaliotis]

Hello Jim,

I finally found some time to do some more tests on my Win 10 install
(VirtualBox, that is), 64 bit, with Zadig installed drivers.


Note: I used the pre-compiled Windows version of xum1541cfg from Nate's
site (http://www.root.org/~nate/c64/xum1541/). Did you use that one,
too?

* On Sun, Jun 19, 2016 at 01:47:51AM -0500 RETRO Innovations wrote:

> >In the mean time, the following should help:
> >
> >1. Put the ZF into DFU mode
> >2. Now, run Zadig for the "Atmel firmware update device", and install
> > the driver for it.
> >
> >Now, you should be able to run the xum1541cfg updater.
> Hmm, I hate to say this, but I thought of that. I took an unprogrammed ZF
> (which is in DFU mode), installed the Zadig driver for that device, to no
> avail.

Have a look into my log:

C:\opencbm-0.4.99.98\opencbm-ZoomFloppy-2.0-i386\exe>xum1541cfg.exe info xum1541-ZOOMFLOPPY-v07.hex
xum1541 firmware, model 2 version 7

C:\opencbm-0.4.99.98\opencbm-ZoomFloppy-2.0-i386\exe>xum1541cfg.exe update xum1541-ZOOMFLOPPY-v07.hex
finding and preparing device for update...
note: device has version 7 but firmware is not newer (version 7)
add the -f flag if you really have the right firmware.

C:\opencbm-0.4.99.98\opencbm-ZoomFloppy-2.0-i386\exe>xum1541cfg.exe -f update xum1541-ZOOMFLOPPY-v07.hex
finding and preparing device for update...
note: device has version 7 but firmware is not newer (version 7)
warning: version mismatch but proceeding to update anyway
error: no devices found to update

Here, I had installed the ZADIG driver for VID/PID 16D0/0504
(ZoomFloppy), but NOT for VID/PID 03EB/2FF0 (the ATMEL DFU device).

Now, I also installed ZADIG for 03EB/2FF0 and retried:

C:\opencbm-0.4.99.98\opencbm-ZoomFloppy-2.0-i386\exe>xum1541cfg.exe -f update xum1541-ZOOMFLOPPY-v07.hex
finding and preparing device for update...
warning: no xum1541 found, continuing to look for devices in DFU mode
updating firmware...
Validating...
update completed ok!
error, failed to release interface 0

The "failed to release interface 0" is interesting, isn't it?
Because of this, I retried:

C:\opencbm-0.4.99.98\opencbm-ZoomFloppy-2.0-i386\exe>xum1541cfg.exe -f update xum1541-ZOOMFLOPPY-v07.hex
finding and preparing device for update...
note: device has version 7 but firmware is not newer (version 7)
warning: version mismatch but proceeding to update anyway
updating firmware...
Validating...
update completed ok!

Ok, here, it succeeded.

And here again:

C:\opencbm-0.4.99.98\opencbm-ZoomFloppy-2.0-i386\exe>xum1541cfg.exe -f update xum1541-ZOOMFLOPPY-v07.hex
finding and preparing device for update...
note: device has version 7 but firmware is not newer (version 7)
warning: version mismatch but proceeding to update anyway
updating firmware...
Validating...
update completed ok!

C:\opencbm-0.4.99.98\opencbm-ZoomFloppy-2.0-i386\exe>

After installing the driver for the DFU device with ZADIG, every update
worked. I have to admit, that I sometimes got the "error, failed to
release interface 0" message, but it seems it does not do any harm,
anyway.

[RETRO Innovations]

On 6/21/2016 2:46 PM, Spiro Trikaliotis wrote:
> Hello Jim,
>
> I finally found some time to do some more tests on my Win 10 install
> (VirtualBox, that is), 64 bit, with Zadig installed drivers.
>
>
> Note: I used the pre-compiled Windows version of xum1541cfg from Nate's
> site (http://www.root.org/~nate/c64/xum1541/). Did you use that one,
> too?

No, I did not. I used the one in the 0.4.99.98 binaries.

And, I am sorry to waste your time, as when I went back to the 0.4.99,
it now works fine. I was trying to "dogfood" the .98 release, and I
didn't know the newer Zadig option would work with the older code, so I
did not try it.

So, 0.4.99 of xum1541cfg.exe works fine on Windows 10. 0.4.99.98
xum1541cfg.exe does not. (I just checked again)

Jim

[Spiro Trikaliotis]

Hello Jim,

* On Tue, Jun 21, 2016 at 07:24:47PM -0500 RETRO Innovations wrote:
> On 6/21/2016 2:46 PM, Spiro Trikaliotis wrote:

> >Note: I used the pre-compiled Windows version of xum1541cfg from Nate's
> >site (http://www.root.org/~nate/c64/xum1541/). Did you use that one,
> >too?
> No, I did not. I used the one in the 0.4.99.98 binaries.

Well, that one is identical (source-wise) to the one from Nate's site. I
did not remember that I updated my sources, so I thought "my" version
was much older. It is not.

> And, I am sorry to waste your time, as when I went back to the 0.4.99, it
> now works fine. I was trying to "dogfood" the .98 release, and I didn't
> know the newer Zadig option would work with the older code, so I did not try
> it.
>
> So, 0.4.99 of xum1541cfg.exe works fine on Windows 10. 0.4.99.98
> xum1541cfg.exe does not. (I just checked again)

There is no 0.4.99 version of opencbm and/or of xum1541cfg.exe. There
must be some x behind, that is, some 0.4.99.x with x >= 95. Can you give
me the exact version number of the version that actually works?

Note, however, that the sources for xum1541cfg.exe have not changed
since they have been included in 0.4.99.95 (2014-01-28). Thus, the only
differences I can see would be in the compiler (I used a newer VS for
0.4.99.98).

[RETRO Innovations]

On 6/22/2016 12:30 AM, Spiro Trikaliotis wrote:
>
> There is no 0.4.99 version of opencbm and/or of xum1541cfg.exe. There
> must be some x behind, that is, some 0.4.99.x with x >= 95. Can you give
> me the exact version number of the version that actually works?

>
>

I can't quite get xum1541cfg to give me a version via --version or -v ,
etc. , but it's the version from Nate's web site (I must have
dismembered the version: 0.4.98?)