New firmwares for SNES/N64/Classic controller to Gc/Wii adapters, implementing seldom used Gamecube controller status reporting where the C-stick and/or the L/R analog triggers can be made 4 or 8 bits. This fixes Luigi's Mansion vacuum and possibly other games!
N64 to Gc/Wii v2.5
SNES to GC/Wii v2.5
Classic to GC/Wii v1.7
Command-line: --gc_pollraw now takes an argument corresponding to the reporting mode (Use 3 for 8 bit C-Stick and L/R triggers)
Add support for adapters with acceleration sensors
Updates for Classic to USB, GC/N64 to USB, Dreamcast to USB, Classic to N64, Gamecube to N64...
New Classic controller to USB adapter firmware version 2.2.4: Add support for connecting a button to the RJ11 connector on Wii Guitars.
GC/N64 to USB adapter firmware version 3.6.1: Brawler 64 wireless support and new Swap main joystick and D-Pad feature.
New Classic controller to N64 adapter firmware v2.1.0: Fixes a joystick value overflow (Corrects a problem with some controllers, such as Wired Fight Pads, where pointing the stick all the way down did the same as pointing it up)
New Gamecube to N64 adapter firmware v2.3:
Add a way to invert Joystick and C-Stick values (For instance, inverted up/down)
The C-Stick is now auto-calibrated like the main joystick (Fixes drifting)
The Controller Pak (Memory card) can now be disabled (In management mode, press R, then Y to enable/disable it)
New Dreamcast to USB adapter firmware 2.0.1: Fix a problem where the sliders were too sensitive and would jump to a negative value when fully held down under Windows.
Support for the Swap main joystick and D-Pad feature of some adapters
The poll frequency (in Hz) resulting from the current poll interval setting is now shown for reference.
The management tool can perform a vibration/rumble test, can update an adapter's firmware and
perform read/write operations on N64 mempaks. The built-in mempak editor supports common .N64 and .MPK mempak image file formats. Downloading
cheats from gamefaqs and using them on the real N64 system is therefore possible! The editor also supports importing and exporting
individual saves (notes) in separate files.
The adapter update function asks you to select the firmware .hex file and does a few checks to prevent mistakes (ex: Installing an incompatible firmware). Once
the file is selected, clicking "Start update" is all there is to do. If everything goes well (please, do not disconnect anything!) after a few moments
the Update successful window should confirm the update.
IMPORTANT: Always use the latest version of the adapter management tool to update adapters.
The command-line tools are very useful if you appreciate simplicity and efficiency. They are available in the tools/ subdirectory
of the source code, and will also be available in compiled form (.exe) when I start releasing builds for Windows.
Here are a few examples of use for gcn64ctl. Use the --help option for more information.
# Listing adapters
$ ./gcn64ctl -l
Simply listing the devices...
Found device 'GC/N64 to USB v3.0', serial '000001'
1 device(s) found
# Displaying the adapter version
$ ./gcn64ctl -s 000001 --get_version
Firmware version: 3.1.0
# Displaying the configured polling interval
$ ./gcn64ctl -s 000001 --get_poll_rate
Poll interval: 5 ms
# And to configure it:
$ ./gcn64ctl -s 000001 --set_poll_rate 10
Setting poll interval to 10 ms
# Reading a N64 mempak
$ ./gcn64ctl -s 000001 --n64_mempak_dump --outfile backup.n64
Output file: backup.n64
Reading address 0x7fe0 / 0x8000
Wrote file 'backup.n64' in N64 format
Tools for handling mempak images
These tools make it possible to convert mempak image files (.MPK to/from .N64), display and manipulate the content (add/remove/export/import notes), etc.
Note that these tools operate on files and never access a physical mempak. To read/write a real mempak, use gcn64ctl or the graphical tool.
Note: Everything shown below is also possible using the mempak editor built in the graphical adapter management tool.
# Importing a note
$ ./mempak_insert_note new.n64 rampage.note
File size: 36928 bytes
.N64 file detected
Loaded pakfile in N64 format.
Current free blocks: 123
Note size: 7 blocks
Note name: RAMPAGE WT.
Note imported and written to slot 0
Updating an adapter under Windows
Windows users, please read this:
When you will attempt to update an adapter for the very first time, Windows will
detect a new device and will want to install a driver. This is an expected behaviour. However,
installation will take so much time that the update will timeout and fail. Do not panic,
disconnect the adapter, reconnect it, restart you computer and try again.
With the current version of the tool, there is unfortunately a black window
that keeps flashing during the update. Do not worry, this is a known issue. I will
try to correct it in the future, but meanwhile at least updates work.
If update fails and your adapter becomes unusable, please follow these
steps to recover your adapter.
Note: Before you complain for the issues described above, please consider that my lack
of interest for GUI programming combined with a strong aversion against Windows software
development means that the very existence of this tool is almost a miracle.
If the tool does not detect your adapter despite it being properly connected, the most likely cause
is that your user does not have the required permissions to access it.
Running the tool as root would work, but it is a very bad practise. Not recommended. Configuring
udev to give your user the appropriate permissions is much cleaner. On my system, my user is
a member of the plugdev group, and I use the following files to give the plugdev group
direct access to the adapter in normal mode (99-raphnet.rules) and in update mode (99-atmel-dfu.rules).
Note: Of course, the above may need modifications for your specific distro or to fit to your needs.
Failed update recovery
I know the update function offered by the graphical user interface has a lot of room for improvement,
especially under Windows where for many users, updating fails, leaving the adapter in an unusable state.
There are two variations of the issue:
The adapter comes back to life once disconnected and reconnected. If it does not show the new adapter
version in the management tool, the update may be re-attempted and then usually works.
The adapter does not come back to life, even if disconnected a few times. When connected,
it appears as a device named "ATmega32U2 DFU" and is not detected as a joystick. The adapter management
tool does not "see" it either.
In this section, I will explain how to deal with the second issue described above.
Step 1: Disconnect the adapter
Disconnect the adapter and only reconnect it when told so at step 3 below.
Step 2: (re)Install the adapter management tool
Make sure you have the very latest version of the adapter management tool installed. Even if you do, re-install it, and make sure to check the "Install driver for updating adapter firmware" option during installation. This installs the driver to handle the adapter when it is in update mode.
Windows Security will warn that a device driver by Atmel Norway is about to be installed. Make sure to click Install (beware: The
button saying Don't Install has focus by default). Atmel is the manufacturer of
the micro-controller the adapter is based on.
Option to install the driver (please check!)
Security message: Click 'Install'
Driver installation completed
Step 3: Connect the adapter and wait
It is now the time to re-connect the adapter. At this point, if your system begins installing something, please
let it finish. The appearance and exact text may vary depending on your Windows version. Here is an example:
Example installation feedback
You can check that the driver was installed correctly by looking at the Device Manager. The adapter should
now appear under the "Atmel USB Devices" section, under the name "ATmega32U2". If on the other hand it
appears in the "Other devices" section, it means the driver was not installed (did you check the installation
option and did you allow the driver to get installed?) or installation is still in progress (as shown for instance
by a popup+system tray icon).
Here are screenshots demonstrating how the device should and should not appear in the Device Manager:
OK! (Atmel USB Devices)
NOT ok (Other Devices)
Step 4: Attempt to recover the adapter
In the management tool, use the Recover adapter function from the Tools menu, select the
adapter firmware .hex file, and click Start update.
Step 5: Did it work?
Use the File->Rescan adapters function, and the adapter should be present. If not, please
try the manual command-line recovery described in the next section.
If the instructions above did not solve the problem, try using the steps in this section.
Step 1: Driver check
As described in the previous section at step 3, the driver must be installed and working. Confirm
that the device is properly listed in the "Atmel USB Devices" category in the Device manager as
shown below. Refer to the above section for more details.
Driver NOT OK
Step 2: Opening a terminal
A shortcut for opening a terminal in the adapter management tool's installation directory was
created at installation. Use it to open a terminal:
Command-line tools shortcut
This will open a terminal window in the correct working directory.
From this point, please take screenshots of the terminal window after running each command, even if you
think there were no errors. If there is still a problem after performing the steps that follows, I will
really need those screenshots to understand what went wrong.
Step 3: Erasing the adapter
Run the following commands, in this order, taking a screenshot after each command.
dfu-programmer atmega32u2 erase
dfu-programmer atmega32u2 erase --force
Step 4: Uploading the firmware
Copy the firmware file (in this example: gcn64usb-3.4.0.hex) to the adapter manager's installation
directory (Typically, "Program Files (x86)\gcn64ctl"). If you place the file elsewhere (eg: On your desktop) you
will have to write the full path on the command-line. Then run the following command:
Once the flash command completes, disconnect the adapter and reconnect it. Start the adapter management
tool to confirm the adapter is working. If it still does not work, please contact me (and include the screenshots).
The Transfer Pak can read and write to the cartridge save RAM, so you can back up your saves, or transfer
them to emulators. The ROM may also be read and then played in an emulator...
There are many different Gameboy cartridge types, and only a few are supported. So far, the following
types are implemented:
ROM-Only: Tetris, Alley Way
MBC1: Final Fantasy Legend II, Nemesis
MBC3: Pokemon blue
MBC5: Mario Golf, Mario Tennis
POCKET CAMERA: Game Boy Camera
Transfering saves to an emulator
Save RAM data read using this tool is stored using the .sav file format which appears to be the standard. Start
the game at least once in the emulator to create a blank save file. Then find out where your emulator
stores its .sav files and overwrite the one matching the game when prompted to save the the data that was
read to a file.
Here is an example using VisualBoyAdvance under Windows 10. The .sav file has is created in the same directory
as the ROM (the .gb file) and has the same name:
Writing emulator saves to a cartridge
Writing an emulator save game to a physical cartridge is the opposite process of what was described above. Find
where your emulator stored your latest save and select it for writing to the cartridge. Data will be written
to RAM first and then read back for verification.
Careful!: Before writing anything to a cartridge containing precious
save data, make a backup copy and test it in an emulator (who knows if it has been corrupted
by a read error?). Whatever happens, regardless of if you made a backup or not, I am not responsible
if for some reason your saves get erased.
I cannot be held responsible for any damages that could occur to you
or your equipment while following the procedures present on this page.
Also, I GIVE ABSOLUTELY NO WARRANTY on the correctness and usability
of the informations on this page. Please note, however, that the procedures
above have worked in my case without any damages or problems.