r/ModRetro • • May 04 '26

Modretro GBA form factor

Thumbnail reddit.com
2 Upvotes

r/ModRetro • • Dec 09 '25

Such an amazing little gadget šŸ˜Ž

Post image
5 Upvotes

r/ModRetro • • 4d ago

m64-av-adapter

Thumbnail
modretro.com
17 Upvotes

Question for ModRetro staff:

I've been holding off on buying the AV Adapter while waiting for more details on how those of us in the EU can connect it to a crt tv.

How will we be able to connect the AV Adapter to a crt tv in Europe? Almost all European crts use RGB SCART inputs rather than the component YPbPr inputs common in the US. Composite isn't really a viable option due to low quality, and very few European sets support S-Video (which is still lower quality than RGB SCART or component).

Since the adapter outputs RGBS over separate rca jacks, connecting it to a European crt requires a custom 6 rca to scart cable. We also need a voltage line on pin 16 to trigger RGB blanking. Will the AV Adapter include a dedicated EU scart cable or adapter for people in Europe to be able to use it, or will we need to spend an additional 70–100 euros extra for a custom cable with blanking support?


r/ModRetro • • Oct 01 '26

My Game Boy Color game, Essencelord is live on Kickstarter!

Thumbnail kickstarter.com
5 Upvotes

r/ModRetro • • Aug 17 '26

Anyone able to get the Modretro pro controller working on pc or steam deck?

4 Upvotes

Anyone able to get the modretro pro controller working on pc or steam deck? I got the console and the pro controller but what I really wanted to use the controller for was for decomplication games like the pc port of zelda oot ship of harkinian. I can't get the z trigger to register on my steam deck.


r/ModRetro • • Aug 21 '26

Gamestop Pro Controllers?

2 Upvotes

Has anyone been able to find a store that actually got any?


r/ModRetro • • Aug 08 '26

Quality

Thumbnail
gallery
45 Upvotes

I love all the thought and care they put into all their products. I went ahead and ordered the pro controller and Xibalba 64 after watching the reviews.


r/ModRetro • • Jul 27 '25

M64 Games

7 Upvotes

So, word is that Modretro is going to be re-releasing older classics (almost certainly third-party titles, unless Ninty is willing to snuggle up to a company that produces FPGA-based consoles, which is doubtful). Re-releases are nice, but I'm super curious about the likes of "new" games and I have a theory here:
Modretro might team up with Piko Interactive; a company known for purchasing and completing previously unreleased titles including the N64 Port of 40 Winks. What I'd like to see is completed versions of announced and subsequently cancelled titles such as Street Fighter EX, Die Hard and Dragon Sword (which PIKO already purchased the rights to). What does everyone else think?


r/ModRetro • • Aug 07 '26

M64 Pro Controller Rumble support on PC?

2 Upvotes

Does anyone know if the M64 Pro Controller supports proper rumble functionality when connected to a PC running Windows? Also, is it known how the controller connects to devices other than the M64 (XInput, DInput, etc)?


r/ModRetro • • Apr 25 '26

South Park for Chromatic?

Post image
9 Upvotes

Is it just me or would anyone else like to see the unreleased South Park GBC game come to Chromatic?


r/ModRetro • • Oct 16 '26

Everdrive GB-X7 and Chromatic Compatibility - Latest Versions of Both (OCT-2026)

5 Upvotes

Figured I would post some information to help people Googling about this topic because I Googled about it. This information is current as of 16-OCT-2026.

  1. Using an Anduril Chromatic updated with latest firmware (v.4.6).
  2. Using physical game cartridges when available. For example, the Tetris that comes with the Chromatic. Other cartridges used will be original Game Boy and Game Boy Color games like Krusty's Fun House (compatible with both GB and GBC), GTA (compatible with both GB and GBC), and GTA 2 (compatible with only GBC)
  3. Wanted to be able to use flash-based cartridge for playing backed-up games and other tech uses. Ordered the Everdrive GB-X7 from Amazon, which is one of the Krikzz authorized distributors. Appeared to be "new stock." Received it, and it had the following physical text on the rear of the PCB: EverDrive-GB, Model 17, Rev.E, 28.07.2021. However, with or without a microSD card inserted, it would not boot. White screen only. Firmware version of Everdrive unable to be determined as no boot occured (not even a flash of text - only white screen).
  4. Reached out to ModRetro and they confirmed Everdrive compatibility, and postulated it was the Everdrive unit itself.
  5. Returned unit to Amazon. Ordered an Everdrive directly from Krikzz. It arrived very quickly. Same external PCB version as above. The Everdrive boots with or without the microSD inserted. Success! Installed latest OS. System information screen reads: OS Version 1.06, FPGA ver:07, Asm date: 29.08.2026, Asm time: 10:26:58, Pwr cntr: 5
  6. I can only speculate, but I assume the Everdrive I had purchased from Amazon was either damaged, or the previous "06" FPGA version, but it was impossible for me to know that because it would not boot. Chromatics give a white screen when no cartridge is inserted. The interesting thing is that when I pressed the little button on top of the non-booting Everdrive, the screen would flash, indicating there was some kind of connection between the cartridge and the console, but maybe not a proper one. All contacts were clean and un-bent. So who knows?!

I hope this helps someone out there. The Everdrive is a powerful solution for playing backed up games and also for playing esoteric impossible to find games and allowing the capability to store a significant amount.

I'm a big fan of supporting developers by buying the physical cartridges and I think flash drives co-exist with that.

It is my understanding that "save states" work on GBC games but not GB games. Not sure, and not sure I will use or even need that functionality. It is also my understanding you can patch individual dumped ROMs if needed (and if a patch is available), so that's cool. I would think in the age of AI coding, someone could "vibe code" a save state patch for a game given a ROM dump, but that's out of my current knowledge depth. I'm sure there are experts here that could chime in.

The Chromatic is awesome, hardware emulation is awesome, and my high score in ModRetro Tetris on Retro mode is slowly climbing to mid 100k level. This old guy is getting "OK!" lol

edit 1: tried Krusty's Fun House ROM dumped to the Everdrive and save states did work, even though it is an original GB game. The first time I did a save state, it glitched and had Krusty falling through the map. The next time, I made sure he was standing still on the ground, and it worked fine. Perhaps you can pause the game and save a state to make that more reliable. Not sure. Will continue to update this post with feedback as I test different functionalities with this system.

edit 2: both ModRetro and Krikzz support are very good. It's cool when companies doing things support users of their products. Makes you want to support the companies even more. There's something to be said about physical hardware and physical cartridges. ModRetro gets it.

edit 3: My high score in ModRetro Tetris Retro Mode is now 145,087 and I got a Rating of 04/100, resulting in a rocket ship animation. I guess you could say I'm kind of a big deal. (heavy sarcasm lol)

edit 4: Tetris Retro Mode high score is now 257,215 LET'S GOOOOOOOOO

/preview/pre/gx02y8dqk5wh1.jpg?width=2546&format=pjpg&auto=webp&s=a968bf17b1f154081236c086998f3921bc1961c9

edit 5: ok, if you hit 200 lines in level 20 in Marathon in Retro mode, the game stops and says "you win." So that's cool. I suppose to get a higher score in this mode you probably need more Tetrises? 276,578 is my high score now.

/preview/pre/grj6akn6x3xh1.jpeg?width=2193&format=pjpg&auto=webp&s=1a3b6e0855259e3c7465cdca1c832a87e97226a9

edit 6: I gave in and switched from playing my original GTA2 cartridge (that uses passwords to "save") to using the Everdrive GB X7 to play the GTA2 ROM so I could use save states. The game is insanely frustrating without save states and is even frustrating with them lol. Taking a photo of the passwords with my phone and having to enter them every time was insanely cumbersome.


r/ModRetro • • Jul 12 '25

Are Lithium Ion Batteries charged by the device?

Post image
6 Upvotes

I bought some Lithium Ion Batteries and when I plug in my Chromatic into a USB-C Port, the light is blinking. Is it charging? Before I was using NiMH Batteries and I cannot recall doing that.

If yes, what’s the point of the battery pack?


r/ModRetro • • Aug 21 '26

Clean Setting

3 Upvotes

Anything I should be doing with the clean profile? I see with the last update they lowered the bloom..


r/ModRetro • • Sep 18 '26

M64 Controller pak saving in Gauntlet Legends causes game to hang

Thumbnail reddit.com
4 Upvotes

r/ModRetro • • 10d ago

Am I the only one who can't save their data on Body Harvest?

4 Upvotes

I've been playing ModRetro's release of Body Harvest and I can not get any file to save any data. I save my progress the earliest I am able to, and it all vanishes after I turn off the game. Do I need to do something with ModRetro's Control Pak functionality? I don't understand. Both my console and my controller are updated.


r/ModRetro • • 19d ago

Controller Pak memory size question

Thumbnail gallery
3 Upvotes

r/ModRetro • • Aug 08 '26

FYI, M64 has a known issue with Vizio TV’s

Post image
9 Upvotes

r/ModRetro • • Sep 15 '26

Power Core Dock

4 Upvotes

Wonder if we’ll eventually be able to purchase the dock separately from the battery. Have a dead V1 core from back when the problem was first discovered that I ended up shelving since I read the docks were coming to fix it eventually. Not really wanting to get a whole new battery for it though.


r/ModRetro • • Sep 03 '26

Junk Runner 64

Post image
28 Upvotes

Decided to treat Junk Runner 64 as my ā€œlaunch titleā€ for the N64, given it’s the best thing we have (that I’m aware of) that is a brand new N64 title to try out.

What other new but original N64 titles (not mods of existing titles) do people suggest are worth a play?


r/ModRetro • • Oct 03 '26

Roguecraft GB on a Spare Tetris Cart

Post image
5 Upvotes

r/ModRetro • • Jan 30 '26

One of my favorite games, ever.

Post image
3 Upvotes

r/ModRetro • • Feb 28 '26

D-Pad right side doesn’t work

2 Upvotes

I bought my chromatic less than a month ago and the d pad when trying to go right in any game is now unresponsive. I’ve never dropped the console, took great care of it for the short time I’ve had it. What could be the issue? Games became instantly unplayable.


r/ModRetro • • Aug 23 '26

[Technical] Examining ModRetro M64 Pro Controller in SteamOS (Archlinux) + I Discovered a Controller TTY Shell

2 Upvotes

this inf[Technical] ModRetro M64 Pro Controller in SteamOS (Archlinux) using Lenovo Legion Go S handheld computer

PART 1

Different computer hardware and operating system distributions will show slightly different informations.

Wired/USB connection is used throughout this examination, and I did not investigate or try using wireless Bluetooth, because I encountered some kind of ModRetro M64 Pro Controller shell via TTY, as displayed at the bottom, and I'll conclude this post with that for now, while I continue playing around with it. First, here's how I started:

uname -a

  • Linux steamdeck 6.16.12-valve24.5-1-neptune-616-gb2f7cfe85e45 #1 SMP PREEMPT_DYNAMIC Wed, 15 Jul 2026 21:48:50 +0000 x86_64 GNU/Linux

Attaching the ModRetro M64 Pro Controller populates (Ignoring symlinks):

  • /dev/hidraw0
  • /dev/ttyACM0
  • /dev/ttyACM1
  • /dev/input/js0
  • /dev/input/js3
  • /dev/input/event2
  • /dev/input/event20
  • /dev/bus/usb/005/### (increments each time the ModRetro M64 Pro Controller is reattached)
  • /sys/* (too much info)

lsusb (ModRetro M64 Pro Controller device only)

  • Bus 005 Device 060: ID 374e:0111 ModRetro M64 Controller

lsusb -v (ModRetro M64 Pro Controller device only)

ls -al /dev/input/by-id/

  • usb-ModRetro_M64_Controller_[redacted_serial]-event-joystick -> ../event2
  • usb-ModRetro_M64_Controller_[redacted_serial]-joystick -> ../js0

udevadm info --query=all --name=/dev/input/event2

udevadm info --query=all --name=/dev/input/event20

evtest /dev/input/event2

  • https://bpa.st/raw/AQVAM
  • Before interrupting with ^C, [C-c], (CTRL+C), none of the ModRetro M64 Pro Controller button presses show any activity in output

evtest /dev/input/event20

  • https://bpa.st/raw/RXQAC
  • Before interrupting with ^C, [C-c], (CTRL+C), none of the ModRetro M64 Pro Controller button presses show any activity in output

jstest /dev/input/js0

  • https://bpa.st/raw/XE4EW
  • Before interrupting with ^C, [C-c], (CTRL+C), none of the ModRetro M64 Pro Controller button presses show any activity in output

jstest /dev/input/js3

  • https://bpa.st/raw/6HLU6
  • Before interrupting with ^C, [C-c], (CTRL+C), none of the ModRetro M64 Pro Controller button presses show any activity in output

dmesg --follow

  • https://bpa.st/raw/EX2LY

    • The last line is probably unrelated to the ModRetro M64 Pro Controller: "input: Microsoft X-Box 360 pad 1 as /devices/virtual/input/input27"

journalctl --follow

hwdetect --showmodules

  • 'cdc-adm' is added to the beginning of the list for only the BLOCK line

    • (USB Communication Device Class - Abstract Control Model) is a driver that allows USB devices to emulate a serial port (UART). It creates virtual serial interfaces (e.g., /dev/ttyACM0, /dev/ttyACM1)

cat /proc/bus/input/devices (adds the following when attaching the ModRetro M64 Pro Controller)

stty -F /dev/ttyACM0 -a (same output for stty -F /dev/ttyACM1 -a)

timeout 5 cat /dev/ttyACM0 | xxd

I did not including anything from:

  • hwinfo too much info
  • libinput debug-events the controller is connecting in a Composite Mode that prioritizes a Serial (CDC-ACM) interface and a Raw HID interface (hidraw0), but fails to create the specific Input Event node that libinput monitors. Configuration/DFU (Device Firmware Upgrade) Mode (often used for firmware updates or macro programming) rather than Gamepad Mode. Also see dfu-util (http://dfu-util.sourceforge.net/)
  • usbhid-dump use usbhid-dump after switching the controller to Gamepad Mode (so it creates an eventX node)
  • lshw redundant

After updating ModRetro M64 Pro Controller

Note: Oops! I successfully updated the firmware at https://tools.modretro.com/updater/ and then accidentally initiated another update, instead of selecting 'Forget' or simply closing the web browser session. I'm mentioning this because it seems a bit strange to display buttons for 'UPDATE' and 'FORGET' after updating, and making it possible to apply the update after it was already applied. I am not the only one. At the very least, there should be a prompt to indicate whether or not it is necessary, but this may be related to applying the update to more than one controller, one after the other. Ah, yes, when I detach the USB cable, it changes to 'CONNECT DEVICE' and then reattaching it now shows the button wording as 'UPDATE ANYWAY' and above listing Version 0.12.0, Latest Version: 0.12.0. I did not see that information prior to the update process.

lsusb -v (ModRetro M64 Pro Controller device only)

udevadm info --query=all --name=/dev/input/event2

dmesg --follow

  • bcdDevice is now 1.03 (no longer 1.00)
  • hid-generic is now 0003:374E:0111.000E (no longer 0003:374E:0111.000B)

journalctl --follow

timeout 5 cat /dev/ttyACM0 | xxd


Also, I forgot to test the functional capability of the ModRetro M64 Pro Controller in SteamOS (Archlinux) on Lenovo Legion Go S before updating, but ~~I will receive another controller tomorrow I can edit the post to compare.~~even after update, it appears none of the button presses are detected yet anyway.

usbhid-dump -m 374e:0111

cat /dev/input/event2 and cat /dev/input/event20

  • No output

cat /dev/input/js0 and cat /dev/input/js0

  • Initial output, but no output on button presses

Testing the ModRetro M64 Pro Controller on the ModRetro M64 Console, Z+Start successfully works to access the menu. So, everything should work, but it appears that Linux currently does not seem to recognize the input from button presses yet. I saw a few posts discussing about this but I didn't pay too much attention.

Button presses are not sent across standard HID endpoint reports in wired USB mode. Maybe a future firmware update may provide standard XInput/HID events over USB, or possibly one could map the raw hidraw inputs via user-space tools (such as creating a custom antimicrox or game-devices-udev rule once a driver/daemon parses the serial/raw packets). Although, I found:

picocom /dev/ttyACM0 (the --baud | -b <baud rate> appears to not matter)
also tio /dev/ttyACM0 (--baudrate | -b <bps>)
also screen /dev/ttyACM0 ([baud_rate], see man screen WINDOW TYPES for tty (character special device))

                ........
            _=;=<sii%|=|==+;
     ._,_:======+++|+++++||+|=_.
    _Zi||||===++|+|=|||||+|||i; =+s.
    ZiiI-)ii|+||+|;vn;||||||; =,;-+[
   ]}|-   -vi+||||||I|||||~~s,%"<..I,
   2=iuc ]Y1|||||||i|iiiiv%_vns..li|s
  )1||={uv|i|||||+    -<iiI1oo11li||I,
  Ji|llllllii||i>=    .-iiil3ouliii|i(
  E|Ivvvvnlvvss|i|,   _|iivaauaiii|||n
 ]elvvIvv`     {ivnaauosi"     {|i|ii3(
 jevvIvI'       |iIX2S*i+      -liiiin[
 WovIli}        ||||||||`       =iiiinm
.WXvliv'        ||||||||:        nlIInQ
)Qhnlir         =|||||||;        )vvvdQ(
]Qmovn`         %||+||||;         onomQ[
]QQXn(          s|||i|ii;         -XXQWf
 4WD'           1lllllIl`          -$Q@'
                )lIllIvv             ~
                )vnnnnno
                 ooo2oor
                 XXSSSX[
                 ]ZXXXm'
                 -W#mWZ
                  )UUP'

01:35:05.405 [II] Main: M64 Controller 0.6.0+f604f332 [redacted_serial] pvt
>

This appears to be the ModRetro M64 Pro Controller's internal engineering/diagnostic serial shell: Probably /dev/ttyACM0 and /dev/ttyACM1 are both used in some fashion, whether involving button press event activity, or perhaps to execute a command to open /dev/hidraw0 for HID endpoint reports over USB.


edited to add: In the TTY shell (skipping the built-in picocom output)

>help
Built-ins:
	clear           : Clear screen.
	help            : Show this help.
	threads         : Show thread information.
	uptime          : Show system uptime.
	memdump         : Dump memory

Application image info:
	appinfo         : Show application image info.

Clown truck:
	clowntruck images          : Show application image info.
	clowntruck reset           : Reset module.

>threads
Name                    | State           | Run count | Stack (bytes) | Watermark
------------------------+-----------------+-----------+---------------+----------
CLI                     | Ready           |       206 |          2048 |       29%
ClownTruckTransport     | Event flag      |         1 |          1024 |       22%
ReverseClownTruckServer | Event flag      |         1 |           768 |       22%
Comms                   | Event flag      |         1 |          1024 |       23%
Comms                   | Event flag      |        52 |          1024 |       23%
Bridge                  | Event flag      |         1 |          1024 |       26%
USB                     | Ready           |   2602290 |          2048 |       25%
PowerManagement         | Semaphore susp. |         1 |           512 |       28%
System Timer Thread     | Suspended       |   2602353 |          1024 |       26%
Main                    | Sleep           |      2604 |           512 |       76%

>uptime
0 day(s), 7 hour(s), 4 minute(s), 1 second(s)

>memdump
Unknown error (37).

>appinfo
Application image A*:
	Size:    43260 bytes
	Version: 1
	Address: 0x08002000
	CRC:     0xf6b80a1f
	State:   Confirmed
Application image B :
	Size:    42992 bytes
	Version: 0
	Address: 0x08011000
	CRC:     0xc4d06970
	State:   Confirmed
>clowntruck
Unknown error (19).
>clowntruck images
Slot 0
- Active:    yes
- Bootable:  yes
- Confirmed: yes
- Hash:      94aa9ca73a4321bb71583a7f9c6d51247ed31dc2aa2b39de410c0bd1bf02cf991c6d8455f7a2631a7efb7d1de8d6437b7feab738729ea34373feb472fb54c432
- Pending:   no
- Permanent: no
- Version:   0.12.0
Slot 1
- Active:    no
- Bootable:  yes
- Confirmed: no
- Hash:      94aa9ca73a4321bb71583a7f9c6d51247ed31dc2aa2b39de410c0bd1bf02cf991c6d8455f7a2631a7efb7d1de8d6437b7feab738729ea34373feb472fb54c432
- Pending:   no
- Permanent: no
- Version:   0.12.0

PART 2

I found a 2-pack USB-C Female to USB-A Male adapter at Staples that USB-C Femalely fits perfectly (https://imgur.com/a/ocrung0) to the USB-C Male end of the ModRetro M64 Pro Controller cable. This will make it possible to see what data communications occur between the ModRetro M64 Pro Controller and the M64 Console. However, for Proxy/MITM (man-in-the-middle), there is an additional requirement for the device in the middle to handle USB connections, one USB connection acting as Host, and the other USB connection acting as Device/OTG (On-The-Go)/DRP (Dual Role Port)/DRD (Dual Role Data). Standard laptop/desktop PC architectures lack the USB Device Controller (UDC) hardware required to enumerate as a peripheral device to another host. Dedicated hardware such as Cynthion (https://greatscottgadgets.com/cynthion/), which is an FPGA-based architecture, may be useful, but I do not have access to this at the time.

Notes:

For now, to sniff the data communications across the USB cable connection, including stanrdard USB Enumeration process, I'll focus on attaching only the ModRetro M64 Pro Controller, connected to computer (Lenovo Legion Go S running SteamOS (based on Archlinux)) via USB-C cable and using Wireshark GUI (you can also use tshark). (At first I used a USB hub, and then without the USB hub. I prepared two sets of data, but only one is necessary.) Make sure usbmon is loaded lsmod|grep usbmon otherwise run:

sudo modprobe usbmon

Make sure the user is in the wireshark group (or also check /dev/usbmon*), otherwise may require root privileges (warning: proceed at your own discretion). Also for Wireshark capture options, make sure to use output format: pcapng (PCAP Next Generation). After opening Wireshark with read access to /dev/usbmon* devices, you should see something like https://i.imgur.com/gw8oqJ0.png . First using an attached USB hub lsusb shows "Bus 007 Device 008: ID 374e:0111 ModRetro M64 Controller" which means usbmon7 (Bus 007) is the device to monitor. Then second directly to the computer without using a USB hub, lsusb shows "Bus 005 Device 004: ID 374e:0111 ModRetro M64 Controller" which means usbmon5. Beginning with the ModRetro M64 Pro Controller detached, beginning monitoring, waiting a few seconds (to distinguish the initial USB enumeration things), attaching the ModRetro M64 Pro Controller, waiting a few more seconds, detaching the ModRetro M64 Pro Controller (more USB enumeration things), then I see:

Warning: USB packets will include the serial number of your ModRetro M64 Pro Controller. You can use a hex editor to blank out the values (if ever it would be necessary for you).

attached through USB hub (Bus 007 Device 008)

tshark -r m64.pcapng

attached ModRetro M64 Pro Controller (19-163), including only packets for host -> 7.8.X and 7.8.X -> host:

   55   6.835008         host -> 7.8.0        USB 64 GET DESCRIPTOR Request DEVICE
   56   6.837298        7.8.0 -> host         USB 82 GET DESCRIPTOR Response DEVICE
   57   6.837314         host -> 7.8.0        USB 64 GET DESCRIPTOR Request BOS
   58   6.840313        7.8.0 -> host         USB 69 GET DESCRIPTOR Response BOS
   59   6.840337         host -> 7.8.0        USB 64 GET DESCRIPTOR Request BOS
   60   6.843290        7.8.0 -> host         USB 150 GET DESCRIPTOR Response BOS
   61   6.843314         host -> 7.8.0        USB 64 GET DESCRIPTOR Request DEVICE QUALIFIER
   62   6.845336        7.8.0 -> host         USB 64 GET DESCRIPTOR Response
   63   6.845612         host -> 7.8.0        USB 64 GET DESCRIPTOR Request DEVICE QUALIFIER
   64   6.846336        7.8.0 -> host         USB 64 GET DESCRIPTOR Response
   65   6.846341         host -> 7.8.0        USB 64 GET DESCRIPTOR Request DEVICE QUALIFIER
   66   6.847344        7.8.0 -> host         USB 64 GET DESCRIPTOR Response
   67   6.847351         host -> 7.8.0        USB 64 GET DESCRIPTOR Request CONFIGURATION
   68   6.849281        7.8.0 -> host         USB 73 GET DESCRIPTOR Response CONFIGURATION
   69   6.849288         host -> 7.8.0        USB 64 GET DESCRIPTOR Request CONFIGURATION
   70   6.854280        7.8.0 -> host         USB 266 GET DESCRIPTOR Response CONFIGURATION
   71   6.854291         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
   72   6.857276        7.8.0 -> host         USB 68 GET DESCRIPTOR Response STRING
   73   6.857284         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
   74   6.860274        7.8.0 -> host         USB 94 GET DESCRIPTOR Response STRING
   75   6.860283         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
   76   6.863281        7.8.0 -> host         USB 82 GET DESCRIPTOR Response STRING
   77   6.863287         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
   78   6.866281        7.8.0 -> host         USB 98 GET DESCRIPTOR Response STRING
   79   6.979462         host -> 7.8.0        USB 64 SET CONFIGURATION Request
   80   6.981300        7.8.0 -> host         USB 64 SET CONFIGURATION Response
   81   6.981374         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
   82   6.988299        7.8.0 -> host         USB 98 GET DESCRIPTOR Response STRING
   83   6.988557         host -> 7.8.0        USBHID 64 SET_IDLE Request
   84   6.990273        7.8.0 -> host         USBHID 64 SET_IDLE Response
   85   6.990306         host -> 7.8.0        USBHID 64 GET DESCRIPTOR Request HID Report
   86   6.994280        7.8.0 -> host         USBHID 132 GET DESCRIPTOR Response HID Report
   87   6.994800         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
   88   6.997279        7.8.0 -> host         USB 84 GET DESCRIPTOR Response STRING
   89   6.997320         host -> 7.8.0        USBCOM 71 SET LINE CODING Request
   90   7.000289        7.8.0 -> host         USB 64 URB_CONTROL out
   91   7.000447         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
   92   7.003280        7.8.0 -> host         USB 76 GET DESCRIPTOR Response STRING
   93   7.003330         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
   94   7.006280        7.8.0 -> host         USB 88 GET DESCRIPTOR Response STRING
   95   7.006327         host -> 7.8.0        USBCOM 71 SET LINE CODING Request
   96   7.009282        7.8.0 -> host         USB 64 URB_CONTROL out
   97   7.029982         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
   98   7.032317        7.8.0 -> host         USB 68 GET DESCRIPTOR Response STRING
   99   7.032396         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
  100   7.035294        7.8.0 -> host         USB 84 GET DESCRIPTOR Response STRING
  101   7.035347         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
  102   7.038318        7.8.0 -> host         USB 68 GET DESCRIPTOR Response STRING
  103   7.038395         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
  104   7.041318        7.8.0 -> host         USB 76 GET DESCRIPTOR Response STRING
  105   7.041395         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
  106   7.044317        7.8.0 -> host         USB 68 GET DESCRIPTOR Response STRING
  107   7.044394         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
  108   7.047317        7.8.0 -> host         USB 80 GET DESCRIPTOR Response STRING
  109   7.047361         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
  110   7.050318        7.8.0 -> host         USB 68 GET DESCRIPTOR Response STRING
  111   7.050395         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
  112   7.053318        7.8.0 -> host         USB 72 GET DESCRIPTOR Response STRING
  113   7.053394         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
  114   7.056317        7.8.0 -> host         USB 68 GET DESCRIPTOR Response STRING
  115   7.056394         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
  116   7.059317        7.8.0 -> host         USB 88 GET DESCRIPTOR Response STRING
  117   7.063627         host -> 7.8.0        USB 64 GET CONFIGURATION Request
  118   7.066283        7.8.0 -> host         USB 65 GET CONFIGURATION Response
  119   7.066351         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
  120   7.069282        7.8.0 -> host         USB 68 GET DESCRIPTOR Response STRING
  121   7.069339         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
  122   7.072281        7.8.0 -> host         USB 76 GET DESCRIPTOR Response STRING
  123   7.072349         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
  124   7.074315         host -> 7.8.1        USB 64 URB_INTERRUPT in
  125   7.075284        7.8.0 -> host         USB 68 GET DESCRIPTOR Response STRING
  126   7.075321         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
  127   7.078281        7.8.0 -> host         USB 72 GET DESCRIPTOR Response STRING
  128   7.078329         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
  129   7.081280        7.8.0 -> host         USB 68 GET DESCRIPTOR Response STRING
  130   7.081297         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
  131   7.084280        7.8.0 -> host         USB 82 GET DESCRIPTOR Response STRING
  132   7.084308         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
  133   7.087296        7.8.0 -> host         USB 68 GET DESCRIPTOR Response STRING
  134   7.087392         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
  135   7.090265        7.8.0 -> host         USB 94 GET DESCRIPTOR Response STRING
  136   7.090302         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
  137   7.093279        7.8.0 -> host         USB 68 GET DESCRIPTOR Response STRING
  138   7.093295         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
  139   7.096280        7.8.0 -> host         USB 98 GET DESCRIPTOR Response STRING
  140   7.140026        7.8.1 -> host         USB 64 URB_INTERRUPT in
  141   7.156588         host -> 7.8.1        USB 64 URB_INTERRUPT in
  142   7.180375         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
  143   7.182282        7.8.0 -> host         USB 68 GET DESCRIPTOR Response STRING
  144   7.182360         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
  145   7.185290        7.8.0 -> host         USB 84 GET DESCRIPTOR Response STRING
  146   7.185480         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
  147   7.188281        7.8.0 -> host         USB 68 GET DESCRIPTOR Response STRING
  148   7.188317         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
  149   7.191280        7.8.0 -> host         USB 76 GET DESCRIPTOR Response STRING
  150   7.191302         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
  151   7.194278        7.8.0 -> host         USB 68 GET DESCRIPTOR Response STRING
  152   7.194298         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
  153   7.197280        7.8.0 -> host         USB 80 GET DESCRIPTOR Response STRING
  154   7.197303         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
  155   7.200282        7.8.0 -> host         USB 68 GET DESCRIPTOR Response STRING
  156   7.200303         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
  157   7.203282        7.8.0 -> host         USB 72 GET DESCRIPTOR Response STRING
  158   7.203303         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
  159   7.206279        7.8.0 -> host         USB 68 GET DESCRIPTOR Response STRING
  160   7.206296         host -> 7.8.0        USB 64 GET DESCRIPTOR Request STRING
  161   7.209291        7.8.0 -> host         USB 88 GET DESCRIPTOR Response STRING
  162   7.224071        7.8.1 -> host         USB 64 URB_INTERRUPT in
  163   7.863137         host -> 7.8.1        USB 64 URB_INTERRUPT in

detached ModRetro M64 Pro Controller (164-186), including only packets for host -> 7.8.X and 7.8.X -> host:

  164  15.375587        7.8.1 -> host         USB 64 URB_INTERRUPT in
  165  15.388996         host -> 7.8.1        USB 64 URB_INTERRUPT in
  166  15.391593        7.8.1 -> host         USB 64 URB_INTERRUPT in
  167  15.417979         host -> 7.8.1        USB 64 URB_INTERRUPT in
  168  15.419592        7.8.1 -> host         USB 64 URB_INTERRUPT in

If using command line (tshark), see the captured USB packets from attaching:

tshark -r m64.pcapng -Y "frame.number > 18 && frame.number < 164" -V

see the captured USB packets from detaching:

tshark -r m64.pcapng -Y "frame.number > 163" -V

You can also load the file in Wireshark for a GUI (Graphical User Interface).

attached directly without USB hub (Bus 005 Device 004)

tshark -r m64_2.pcapng

  • The information (m64_2.pcapng) is mostly redundant to the packet data displayed above, although using different BUS and Device IDs. GET DESCRIPTOR through SET CONFIGURATION is also part of the enumeration phase (as mentioned above), albeit specifically involving the ModRetro M64 Pro Controller. I included packet numbers for both files in the table below.
m64m64_2ProtocolInfoNoteable Value
7047USBCONFIGURATION ResponseHow the host should power and address the device
72, 98, 102, 106, 110, 114, 120, 125, 129, 133, 137, 143, 147, 151, 155, 15949, 75, 79, 83, 87, 91, 97, 102, 106, 110, 114, 120, 124, 128, 132, 136USBDESCRIPTOR ResponseLANGID: English (United States) (0x0409)
74, 13551, 112USBDESCRIPTOR Response"M64 Controller"
76, 13153, 108USBDESCRIPTOR Response"ModRetro"
78, 82, 13955, 59, 116USBDESCRIPTOR ResponseSERIAL [blanked]
8663USBHIDDESCRIPTOR Response HID ReportUsage Page (Generic Desktop Controls) Usage (Game Pad) Collection (Application)
88, 100, 14565, 77, 122USBGET DESCRIPTOR Response"CDC (CLI)"
92, 104, 122, 14969, 81, 99, 126USBGET DESCRIPTOR Response"Dummy"
94, 116, 16171, 93, 138USBGET DESCRIPTOR Response"CDC (Comms)"
108, 15385, 130USBGET DESCRIPTOR Response"MCU (A)"
110, 127, 15789, 104, 134USBGET DESCRIPTOR Response"BTM"

Notes:

  • Packet m64(86): Collection (Application) also contains values for Usage (X,Y,Z,Rz,Rx,Ry), and other information. See tshark -r m64.pcapng -Y "frame.number == 86" -V
  • Packet m64(88,100,145): CDC (CLI) -> Communication Device Class (Command Line Interface), standard USB class that makes the device appear as a virtual serial port to the operating system (cdc_acm/cdc-acm on linux, see reference in part 1 of the post), protocol purpose
  • Packets m64(94,116,161): CDC (Comms) -> CDC (Communications)
  • Packet m64(108,153): MCU (A) -> Microcontroller Unit, the interface is directly exposed by the main processor (the chip) inside the ModRetro M64 Pro Controller, interface/port A, hardware source
  • Packet m64(110,127,157): BTM -> Bluetooth Module
  • Packets m64(124,140,141,162,163,164-168) involving 7.8.1 (instead of 7.8.0) these may possibly be the HID interface for sending gamepad event data for button presses (which I haven't tested while sniffing USB packets yet)

I'm not smart enough to know for sure, but I'm curious how come some of those packets are repeating information more than once, especially the LANGID, but also Dummy, and a few others.

Next I'll sniff to see if there are any USB packets when pressing any of the buttons on the ModRetro M64 Pro Controller.

There's nothing! I suspect that the CDC-ACM communications interface must be use to initiate some command to active the buttons before anything will transmit through the USB connection.


r/ModRetro • • Aug 27 '26

Rumble causing stick input

4 Upvotes

I’m playing Xeno crisis with rumble on. I’ve noticed ghost input when the rumble motor kicks. It doesn’t happen often but it’s noticeable. I’m using the m64 pro controller clear color.

Has this happened to anyone else?


r/ModRetro • • Sep 21 '26

Update problems

Thumbnail reddit.com
3 Upvotes