The xum1541 is currently in beta, which means you'll have to build your own device and compile code from cvs in order to use it. It is reasonably stable in that it already passes a lot of tests, including parallel d64copy in both directions. It also has nibbler support via nibtools. NOTE: both the host side (OpenCBM xum1541 plugin) and firmware protocols are still subject to change, so be prepared to upgrade both sides in the future.
While I plan to continue development of the firmware, I can't provide too much debugging support if you aren't capable of getting the device working on your own. At some point, there will probably be a packaged device available but not from me. So if you're not comfortable debugging your own hardware, you might want to wait.
After you've got the firmware installed, you'll need to build OpenCBM from source. The xum1541 is not yet supported in any released versions of OpenCBM. Build and install the code in the cbm4win directory as specified in the OpenCBM README files.
As of this writing, OpenCBM has a plugin configuration file called "opencbm.conf". You'll need to edit it to list your xum1541 plugin as the default plugin.
If you want to enable high speed transfers and copy protected disks, you also need to install nibtools. Here's the latest source code from the SVN repository.
You're done! If everything is working ok, you can now use your xum1541 with OpenCBM, just like the previous interfaces.
Here are some pics of the xum1541-AT90USBKEY model. As you can see, the devel board is connected directly to an XAP1541 adapter via a DB25 port. The "S" and "P" mean IEC serial and parallel connections.
Here is a more detailed picture.
| Copyright © 2005-2009 Nate Lawson | ![]() |