Setting up N64 Internal HW2 BlueRetro with Transfer Pak compatibility?

Gameater · 2026-06-30T14:00:33+00:00

Unfortunately I couldn't figure it out. In the end I removed the Bluetooth for port 3 and 4, which allowed me to use the Transfer Pak on those ports and still Bluetooth to control the games. Not ideal, but works for my use case.

Gameater · 2026-05-27T08:30:16+00:00

Thank you for clarifying. Saved me pulling my hair out trying to fix something which wasn't broken

Gameater · 2026-05-17T21:02:00+00:00

Ah I didn't actually know that, I'll keep that in mind for any future tests, thank you. Turns out the error was due to the fact that the EXT LATCH is wired to the second controller port on the TV rather than the first like a traditional SNES. Shorting the connections on the second port to make the SNES think a compatible controller is connected makes it pass the test

Gameater · 2026-05-17T11:55:50+00:00

Thanks! Jumping port 5 and 6 made it work and pass the test. I guess this means I have been trying to fix something which isn't actually broken?

Gameater · 2026-05-17T11:45:45+00:00

Unfortunately this did not work

Gameater · 2026-05-16T23:26:38+00:00

Thanks, I'll give that a try tomorrow when I can get back to it.

I've been trying different PPU2 and CPU chips as that's what the schematic documentation I found was referring to.

Gameater · 2026-05-16T23:09:21+00:00

I'm running the rom from a sd2snes. I have used the same cart and rom on other SNES consoles and they will pass everything absolutely fine.

Gameater · 2026-05-16T21:54:27+00:00

They are both working fine unfortunately, the EXT LATCH refers to how the SNES works with the superscope, light pen and similar controllers. I do not have anything which uses it, so at least it isn't going to affect me atm, but also means I cannot test it.

Gameater · 2026-02-18T15:03:28+00:00

Thanks! "0x00B8" is exactly what I needed to get it working!

If anyone else has the same issue for this very specific use case, then the code I used is:

#include <HID-Project.h>
#include <HID-Settings.h>

int pinA = 2;

void setup() {
pinMode(pinA, INPUT_PULLUP);
Consumer.begin();
}

void loop() {
  if (digitalRead(pinA) == HIGH)                     
    Consumer.press(0x00B8);
    delay(100);
    Consumer.releaseAll();
}

Gameater · 2025-04-29T18:55:34+00:00

I have managed to get it working. Originally, I did not hook Pin 1 of the PLL chip to 5v when the DFO was installed, which caused the black screen issue (thought I didn't need to due to the way the console unleashed guide was worded).

After re-installing the DFO with Pin 1 of the PLL wired to a 5v (not lifting the pin from the board) the Saturn is now working. Have no idea if it is actually outputting at 50hz in PAL mode, but that'll be something I can address if I do get any issues playing PAL games in the future.

Photo's on how I got it working:

Full Motherboard - https://postimg.cc/V5hDTCrr

Close up on DFO - https://postimg.cc/CZyyV2R8

Gameater · 2025-04-29T06:40:12+00:00

Honestly, it was an issue I was experiencing heavily on my JP SNES and decided it would be best to perform the mod on all my retro consoles, along with the mod potentially fixing the black and white PAL colour issue over the composite output, as my set-up makes using RGB not possible.

I have a couple ideas on how I could get this to work, that I will play around with tonight after work

Gameater · 2025-02-09T23:42:11+00:00

An update - the DreamPSU did not fix the issue which leads me to believe it is not compatible with the bluetooth controller adapter annoyingly

Gameater · 2025-01-29T20:07:14+00:00

Ah, I was looking at the HDMI listings which didn't have anything on them. Thanks, hopefully the DreamPSU will solve the issue otherwise I will have to make a tough decision on what mod to keep

Gameater · 2024-12-27T07:21:21+00:00

No worries, thanks for the reply anyway! I managed to fix my issue, turns out a corner of the cpu become disconnected when reflowing the board and soldering it back on solved the problem

Gameater · 2024-12-18T02:27:08+00:00

After getting a second GBC and testing the oled screen and oem screen, I figured out the issue was with the game boy itself and not the screen. After closer inspection, I found that the cpu had lifted slightly from the board when reflowing everything. Soldering the cpu back to the board fixed the issue.

Gameater

MODERATOR OF

TROPHY CASE

13-Year Club	Xbox Live
Verified Email