Commodore floppy drive to USB adapter (mini xum 1541)

Hi everyone,

I stumbled onto this project online: http://www.waitingforfriday.com/index.php/Mini_xum1541

It's essentially a trimmed down version of the ZoomFloppy with just the essentials needed for connecting a CBM floppy drive to a computer via USB.

I needed something like this and since it was not economical to build just one, I had extra boards manufactured and sourced extra components.


Demonstration

I recorded a video clip demonstrating the use of one of these, in this case reading a floppy to a .d64 image. You can also write images back and format disks etc.

Please read up on the ZoomFloppy and OpenCBM before buying one, I can't supply a manual, only the device itself!




Completed device - Sold out

All parts soldered on, firmware installed, device tested by me with a 1571 drive.

	Finland	Europe	Worldwide
Price + shipping	€20	+ €2	+ €3

Several devices can be shipped in the same parcel at no extra cost.

After declaring interest, please send a PM to me, just in case I don't happen to notice your message here on the thread.


Casing

Additionally, I designed a case for the board. I have had one 3D printed and it came out nicely. I've made the model available for purchase on Shapeways.


Order status

User	Quantity	Status
acer	1	Received
Junior	1	Received
nightflyer	1	Received
Silverburst	1	Received
golgotha	1	Received
PantherUK	1	Received
ViperSan	1	Received
stalkr3	1	Received
TGE	1	Received
ecaredit	1	Received

Also selling these elsewhere. Some photos follow.

Hi, how much would these sell for?

@CUF85

Do you mean all of them? I'm sure we can work out a little discount if that's the case, but otherwise 18 or 25 euros as mentioned in the original post :thumbsup:

Declaring interest in one DIY kit, PM will follow.

@ajk

I was just wondering of the price for 1 unit as these seem pretty interesting. Got myself a C64 today but it came without any floppy disks so i will need to transfer some d64 files.

@CUF85

Indeed, exactly the reason I wanted to build one :)

@demolition

PM answered, one kit is reserved for you!

Payment has now been sent.

I have an Easy1541 cable which I am using with the Amiga. It is working fine, but it takes over 10 minutes to transfer one d64 image, and this interface looks a lot faster.

@demolition

Thanks! Will ship your kit soon.

It takes about one minute to copy a floppy with this adapter and the 1571 drive, as seen in the video. It's quite comfortable in my opinion.

hi will this work with 1581 drives if so I'm intrested in fully built 1 without case

I will pm later

Declaring interest in one DIY kit. Will pm you in a couple of hours.

Thank you

interested in one if still available

@johnim

Yes any drive including 1581 should work fine, but I haven't got one to test with. Look into OpenCBM and ZoomFloppy for reference and let me know if you want to buy one, I will keep one reserved for you.

@CUF85

Excellent, one is reserved for you.

@Flare

Sure, a built one or a kit? Assuming built one for now.

Interested in a built one, will pm when i get back from work.

On a side note would this work with a c64 emulator do you think ?

Sent from my GT-S5830 using Tapatalk 2

@Cryton

Alright, one is reserved for you. I believe there is some support for VICE in OpenCBM (or the other way around), but I have not tried it out.

Pm sent!

Declaring interest in one completed device.

@JD6

Alright, you have the last one :)

Are completed devices still available ? If so I'm interested.

@owen2471

Flare did not mention which one he wants, but if it's a completed one then there aren't any more ready right now.

I can put one of the kits together for you if you wish, but it'll have to wait until next week. If that's ok I'll reserve one for you.

Payment sent

Payment sent.

pm sent for paypal info

pm sent for paypal details :D

---------- Post added at 17:28 ---------- Previous post was at 17:22 ----------

Payment Made :thumbsup:

payment sent :thumbsup:

Thank you all who have paid :) I will try to send these off tomorrow or on Friday at the latest!

paymend send

Yes please reserve a complete kit. How much is total to uk ?

@owen2471

It'll be €25 if regular airmail shipping is fine. I'll put one together next week then and get back to you :)

Ok reserve me 1 complete kit please. Pm me when payment is due.

I'd like to purchase the last DIY kit, if still available (I can solder it myself). I'm from Spain. Please, PM with payment details. Thanks!

Also, I would be interested in the case if you make it available at shapeways. I could print it myself too. We have a 3d Printer in our facilities, but I'm not very used to operate it yet.

BTW: this is my first post here. I was looking for a USB solution to use my 1571 drive from my PC, because when I upgraded the motherbord, it came without a parallel port, and a PCI add-on parallel port didn't do the job (I'm using Windows 7).

@mcleod-ideafix

Certainly, the last kit is yours :) I think you need to make another forum post before you can use private messages, but I will send you the payment details now.

I'll make the Shapeways model also available soon.

Payment sent! Thanks for the prompt reply.

Seven out of the eight adapters have now been posted! I'll build and send the last one next week.

These should be arriving early next week for all you guys in Europe, probably a bit later to Canada.

http://www.amibay.com/attachment.php...0&d=1375965934

Looking forward to trying it. I think you should increase the resolution on your label-printer though. :)

@demolition

Pfft, I'm sure the post office can cope with it ;)

I've made the case now available on Shapeways for anyone who might want one (first post updated).

AJK do you think you will be able to build any more after these? Thanks.

@everblue

I haven't got any more parts right now, but if there is enough interest I can order more. Kits are easier on my part but I'm sure I could also build some complete ones every now and then.

I'm interested in one if that helps :)

thanks ajk looking forward to getting my old programs and stuff on my pc

Thank you very much ajk. Great job!

I miss this kit!:banghead:

@ajk

Now i feel like a complete retard asking for price and everything. I'm using Tapatalk on my iphone and it show a condensed post even when i refresh the thread. There is no price or video on the post. Sorry!

@CUF85

Ah, I imagined it must be something like that, since I thought I was quite clear in the original post... :) No worries!

Package received saturday. Have now assembled and tested it, and it's working great. Will leave feedback. :)

Mine arrived this morning. Assembled and tested. No luck.

Device is recognized by the PC. Firmware updated and it's recognized now as a ZoomFloppy device.

LED doesn't show at all. I took a peek at the Zoom Floopy schematic, and I noticed that the led is connected to pin 5 of microcontroller using one of the inverters at the LS06 device, so when the microcontroller puts a '1', the output of the inverter is connected to GND and the led is on. With the MiniXUM, the microcontroller should put a '0' in order to the led to go on. Besides, the current limiting resistor for the led at the Zoom Floppy is 220 ohm, and the one used in the MiniXUM is 1K. Isn't that too much resistance? Am I missing something? Do I need a specific firmware for the MiniXUM?

The only command that makes something is cbmctrl reset. Any other command shows no result (cbmctrl detect) or something like "overlapped I/O whatever..."

I've checked continuity from the IEC connector down to the microcontroller. No shorts, no missing connections...

Tried pluging it in a powered USB hub and directly in a USB connector at the rear of my PC (no hub). Tried different USB cables. Same result.

I'm using a 1571 drive. Drive is configure as unit 8. IEC cable is tested. Drive is not (worked the last time I used it though)

with XUM1541_DEBUG=99, cbmctrl detect gives me this:

Code:

---

[XUM1541] scanning usb ...
[XUM1541] scanning bus bus-0
[XUM1541] device 16d0:0504 at \\.\libusb0-0001--0x16d0-0x0504
[XUM1541] found xu/xum1541 version 0207 on bus bus-0, device \\.\libusb0-0001--0x16d0-0x0504
[XUM1541] xum1541 name: xum1541 floppy adapter (ZOOMFLOPPY)
[XUM1541] xum1541 serial number:  0
[XUM1541] firmware version 7, library version 7
[XUM1541] device capabilities 03 status 10
[XUM1541] write 16 2 bytes from address 0014F690 flags 2
[XUM1541] wrote 2 bytes
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 2
[XUM1541] wait done, extended status 2
[XUM1541] write done, got 2 bytes
[XUM1541] write 16 6 bytes from address 0014F6DC flags 0
[XUM1541] wrote 6 bytes
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 1 bytes from address 0014F67F flags 2
[XUM1541] wrote 1 bytes
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 1
[XUM1541] wait done, extended status 1
[XUM1541] write done, got 1 bytes
[XUM1541] write 16 2 bytes from address 0014F690 flags 2
[XUM1541] wrote 2 bytes
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 2
[XUM1541] wait done, extended status 2
[XUM1541] write done, got 2 bytes
[XUM1541] write 16 6 bytes from address 0014F6DC flags 0
[XUM1541] wrote 6 bytes
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 1 bytes from address 0014F67F flags 2
[XUM1541] wrote 1 bytes
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 1
[XUM1541] wait done, extended status 1
[XUM1541] write done, got 1 bytes
[XUM1541] write 16 2 bytes from address 0014F690 flags 2
[XUM1541] wrote 2 bytes
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 2
[XUM1541] wait done, extended status 2
[XUM1541] write done, got 2 bytes
[XUM1541] write 16 6 bytes from address 0014F6DC flags 0
[XUM1541] wrote 6 bytes
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 1 bytes from address 0014F67F flags 2
[XUM1541] wrote 1 bytes
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 1
[XUM1541] wait done, extended status 1
[XUM1541] write done, got 1 bytes
[XUM1541] write 16 2 bytes from address 0014F690 flags 2
[XUM1541] wrote 2 bytes
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 2
[XUM1541] wait done, extended status 2
[XUM1541] write done, got 2 bytes
[XUM1541] write 16 6 bytes from address 0014F6DC flags 0
[XUM1541] wrote 6 bytes
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 1 bytes from address 0014F67F flags 2
[XUM1541] wrote 1 bytes
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 1
[XUM1541] wait done, extended status 1
[XUM1541] write done, got 1 bytes
[XUM1541] write 16 2 bytes from address 0014F690 flags 2
[XUM1541] wrote 2 bytes
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 2
[XUM1541] wait done, extended status 2
[XUM1541] write done, got 2 bytes
[XUM1541] write 16 6 bytes from address 0014F6DC flags 0
[XUM1541] wrote 6 bytes
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 1 bytes from address 0014F67F flags 2
[XUM1541] wrote 1 bytes
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 1
[XUM1541] wait done, extended status 1
[XUM1541] write done, got 1 bytes
[XUM1541] write 16 2 bytes from address 0014F690 flags 2
[XUM1541] wrote 2 bytes
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 2
[XUM1541] wait done, extended status 2
[XUM1541] write done, got 2 bytes
[XUM1541] write 16 6 bytes from address 0014F6DC flags 0
[XUM1541] wrote 6 bytes
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 1 bytes from address 0014F67F flags 2
[XUM1541] wrote 1 bytes
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 1
[XUM1541] wait done, extended status 1
[XUM1541] write done, got 1 bytes
[XUM1541] write 16 2 bytes from address 0014F690 flags 2
[XUM1541] wrote 2 bytes
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 2
[XUM1541] wait done, extended status 2
[XUM1541] write done, got 2 bytes
[XUM1541] write 16 6 bytes from address 0014F6DC flags 0
[XUM1541] wrote 6 bytes
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 1 bytes from address 0014F67F flags 2
[XUM1541] wrote 1 bytes
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 1
[XUM1541] wait done, extended status 1
[XUM1541] write done, got 1 bytes
[XUM1541] write 16 2 bytes from address 0014F690 flags 2
[XUM1541] wrote 2 bytes
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 2
[XUM1541] wait done, extended status 2
[XUM1541] write done, got 2 bytes
[XUM1541] write 16 6 bytes from address 0014F6DC flags 0
[XUM1541] wrote 6 bytes
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 0
[XUM1541] wait done, extended status 0
[XUM1541] write done, got 0 bytes
[XUM1541] write 16 1 bytes from address 0014F67F flags 2
[XUM1541] wrote 1 bytes
[XUM1541] xum1541_wait_status checking for status
[XUM1541] return val = 1
[XUM1541] wait done, extended status 1
[XUM1541] write done, got 1 bytes
[XUM1541] Closing USB link

---

Any idea about what should I test/look/check? Thanks! :)

UPDATE: Just tested the drive, same IEC cable, against a C64 breadbin. Works flawesly: shows directory and load games.

I used a 1.1k resistor for the LED and it still lights up fine so that shouldn't be a problem. It just affects how bright or dim the LED will be. The original ZoomFloppy might have used a blue LED which needs more voltage than greens or reds.

Firmware is exactly the same as the regular ZoomFloppy so that should be ok too. I can check the exact archive I used when I get back home from work.

How did you test your IEC cable? I had a lot of issues actually using a drive with the first IEC cable I tried, but then I swapped it to an original Commodore one and everything started working. I don't remember the exact error messages anymore but the detect command worked, other ones didn't, like in your case. The bad cable also worked with the actual C64. Have you got another cable to try, just to be sure?

Quote:

---

Originally Posted by ajk

How did you test your IEC cable? I had a lot of issues actually using a drive with the first IEC cable I tried, but then I swapped it to an original Commodore one and everything started working. I don't remember the exact error messages anymore but the detect command worked, other ones didn't, like in your case. The bad cable also worked with the actual C64. Have you got another cable to try, just to be sure?

---

I just used it with the drive and the C64. It's the same cable that came with this drive and a C128. I'm afraid I haven't got any other IEC cable at this moment :(

About the LED: the point is not how high or low is the resistor, but the behaviour of pin 5 at the microcontroller. By the ZoomFloppy schematic, I deduce that the microcontroller has to put a high value at pin 5 when it wants the LED to go on. I think so because one of the inverter gates from the LS06 (unused in the MiniXUM) is used to invert this signal. The output of that inverter is connected to the led, and the other led pin is tied to +5V with a resistor in between.

To turn on the led, the output of the inverter must be low, and that means that the input of the inverter has to be high. If the input is low, the output of the inverter is disconnected (open collector) from the rest of the led circuit.

See schematic:
Attachment 50234

With the led circuit implemented in the MiniXUM, pin 5 has to go low in order for the led to bright, as it is connected directly to the cathode of the led.
Attachment 50235

Is it possible that I'm using a broken version of the firmware? How is it possible that two different led circuits, one of them with an inverter in between, behave the same way with the same firmware?

Thanks!

I understand that, but the LED just blinks when there is some activity, and it will also blink with an inverted signal. It is perhaps inverted when the device is idle, but it shouldn't affect any actual functions. I don't have an original ZoomFloppy so I don't know how the LED is supposed to behave. You can see how mine works in the video on the first post.

The more important question is what is preventing the drive from working properly... I don't imagine it's the LED, and at the moment I have no other ideas apart from the cable issue :( I'll check the exact firmware version later when I can.

I used this exact package to program my device and it is working fine:
http://root.org/~nate/c64/opencbm-ZoomFloppy-i386.zip
When it has been installed, the LED lights continuously and flashes on activity.

Have you looked closely at whether there might be a short somewhere between two pins of the uC? The pitch is quite small.

@mcleod-ideafix

Alright, I am home now and checked my own board. As demolition said, the LED should light up once the device is plugged in. Have you double-checked the polarity is correct?

The archive demolition mentioned is also the same one I have so that firmware should work.

Could you take a good close-up photograph of the board? I could compare it with mine, perhaps there would be something easy to spot.