borti4938 / snes_multiregion_with_dejitter_qid Goto Github PK

Is the CDCEL913 a valid substitute for CDCE913? The main differences appears to be Vddout max.

I'm also assuming the PIC16F18324 will be a valid sub for the older PIC16F684.

Hello,

Is there any suitable replacement for U3 = EPM7032AETC44-10N ?

The chip is now obsolete.

Thanks!

I cannot get my hand on TSH122ICT Chips. Are they required if I do not use the bufferd output line? I am fine with the raw line, can I just leave the Chip out of the design? I cannot see why not when looking at the schematics, but I am not too familiar with it.

Hi,
I have some SMR20190813 boards left since I made one some time ago.
Since I want to make another pair but don't want to throw the left over PCBs away, am I missing some major features/fixes?
Like, looking at the BOM I've seen that it's missing Video Drivers.

Also, I need to install it to a PAL 1CHIP, do I need to do something else since it's PAL?

Have a nice day,
Sonno

When programming the DFO, the readme says "Set V-target jumper on programmer to 5V"
(here: https://github.com/borti4938/SNES_MultiRegion_with_DeJitter_QID/blob/master/fw/dfo/SOURCE.md)

I am using this DFO programmer https://oshpark.com/shared_projects/SeJLCY52 which is recommended, but it only outputs 3.3V. How did you modify the DFO programmer output 5V for this process?

Thanks for this project! 👍

I get this error on both UNO and NANO boards, testing with 2 different PCBs.
Of course this could be a user issue.
Value read at reg 0x1E: 0x2 (0x72 expected) looks suspicious.

This is my first SNES_MultiRegion_with_DeJitter_QID install and I wanted to say thanks and give a big hug!

Wait for CDCE913: ... Found! (CDCE913 I2C Address: 0x65)
Write registers: ................................ done!
Verify registers: ... 
 - Number of bytes returned: 32
 - Value read at reg 0x0: 0x81 (not evaluated as reg is read only)
 - Value read at reg 0x1: 0x1 (0x1 expected)
 - Value read at reg 0x2: 0xBC (0xBC expected)
 - Value read at reg 0x3: 0x6 (0x6 expected)
 - Value read at reg 0x4: 0x1 (0x1 expected)
 - Value read at reg 0x5: 0x90 (0x90 expected)
 - Value read at reg 0x6: 0x40 (0x40 expected)
 - Value read at reg 0x7: 0x40 (not evaluated as reg is read only)
 - Value read at reg 0x8: 0x40 (not evaluated as reg is read only)
 - Value read at reg 0x9: 0xCF (not evaluated as reg is read only)
 - Value read at reg 0xA: 0xFF (not evaluated as reg is read only)
 - Value read at reg 0xB: 0xFF (not evaluated as reg is read only)
 - Value read at reg 0xC: 0xFF (not evaluated as reg is read only)
 - Value read at reg 0xD: 0xFF (not evaluated as reg is read only)
 - Value read at reg 0xE: 0xFF (not evaluated as reg is read only)
 - Value read at reg 0xF: 0xFF (not evaluated as reg is read only)
 - Value read at reg 0x10: 0x0 (0x0 expected)
 - Value read at reg 0x11: 0x0 (0x0 expected)
 - Value read at reg 0x12: 0x0 (0x0 expected)
 - Value read at reg 0x13: 0x1 (0x1 expected)
 - Value read at reg 0x14: 0x6B (0x6B expected)
 - Value read at reg 0x15: 0x1 (0x1 expected)
 - Value read at reg 0x16: 0x18 (0x18 expected)
 - Value read at reg 0x17: 0x5 (0x5 expected)
 - Value read at reg 0x18: 0x4F (0x4F expected)
 - Value read at reg 0x19: 0x55 (0x55 expected)
 - Value read at reg 0x1A: 0x53 (0x53 expected)
 - Value read at reg 0x1B: 0xEC (0xEC expected)
 - Value read at reg 0x1C: 0x96 (0x96 expected)
 - Value read at reg 0x1D: 0xF1 (0xF1 expected)
 - Value read at reg 0x1E: 0x2 (0x72 expected)
... VERIFICATION ERROR!
Number of Bytes not as expected!
First register error at 0x1E!

Hey, first of all thanks for this awesome work!

I have a PAL SNES with a SNSP-CPU-02 mainboard. Yesterday I put in the modchip according to the documentation on this site and everything seems to be okay. My PAL cartridges work fine and the modchip is detecting the Game as PAL 50Hz in Auto Mode (unfortunately I don't have NTSC cartridges to test with). I can also switch the modes manually with the reset button and with the Controller Inputs that come with the uIGR, so everything ok.

Now with my FXPAK PRO on the latest Firmware there is a strange behavior (didnt test other firmware). I have done all settings as described to turn on the pairing mode for the SuperCIC and the FXPAK PRO. Now when I turn on the console, I get 60Hz, but when I start a PAL rom it changes to 50Hz for some miliseconds and then jumps back to 60Hz. I can't switch the mode with the reset button anymore, only with Controller Inputs over uIGR, but this should normally not be necessary in pairing mode? Do you have any idea why this happens? I didn't find anything on the net and any help would be appreciated.

• I tested several PAL roms
• I turned off auto region patch in the FXPAK PRO
• Region patch from SuperCIC is active
• Turned on the SuperCIC mode for uIGR as described.

I checked the values of the frequency over a Retrotink to be sure.

Thanks in advance and greetings from Germany 🙂

PS: I bought the modchip from Retroupgrades.co.uk

Hi ... I bought the mod from VGP and did not check upfront which board version I have (stupid I know).
Turns out I have a first generation US SNES (with the discrete audio card) and the SHVC-CPU-01 board and there is no installation guide listed here for that :-(
Because it was my first own console back in the days I'm emotionally attached to that US device and would really love to use it with the mod, but I'm not sure if I'm good enough to just follow the general installation instructions and figure everything out by myself.

Has anyone experience with the installation in that SNES model and can provide instructions or pictures?
Or is there maybe someone in Germany that could offer installation service?
Thanks!

Hi,
I am trying to program the new ATMEL CPLD part no. ATF1504ASV(L) as per the instructions on the GitHub page but am having a bit of trouble.

When initializing the jtag connection, I get the error:

C:\Users\X>openocd -f openocd-ft2232h.conf Open On-Chip Debugger 0.11.0 Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html C:/msys64/mingw64/bin/../share/openocd/scripts/openocd-ft2232h.conf:3: Error: invalid command name "ftdi" in procedure 'script' at file "embedded:startup.tcl", line 26 at file "C:/msys64/mingw64/bin/../share/openocd/scripts/openocd-ft2232h.conf", line 3

I was told elsewhere to "Not to use some out-of-tree way to init JTAG adapter and instead source ftdi/minimodule.cfg."

Moreover, I was also told "This odd script isn't suitable for this version of OpenOCD, use scripts that come with the binary you got there."

Any help would be appreciated, I must say it was much more straightforward when I programmed two boards in the past using the EPM7032.

Hi, Ive had my board installed for a couple of weeks now and its been working great. But today while playing the key combinations stopped working. It wont let me region switch, or reset the console. I can still change the region using the reset button which makes me think the uIGR is good. As i understand it its both the input sniffer and what holds the region?

Is it possible to disable the input sniff accidentally maybe? Or do you have any other clues for what i need to check? Maybe theres a test point i can probe to see if the inputs are registered?

Apologies to raise an issue on this project about an installation rather than the build of the mod itself, just looking for some advice and this seemed like a good place to start. I'm experiencing some faint diagonal bars, most noticeable on grays, following installation of this mod — but only in PAL mode.

I've installed a recent version of this board into a SNSP-CPU-1CHIP-01 console following all the relevant instructions as detailed in this repo for that particular revision, including colour carrier and CSYNC on pin 3.

Along side this, I've completed the following:

• Recapped the entire console.
• Replaced the voltage regulator with a 78S05.
• Added a 750Ω resistor to each RGB line for brightness fix.
• Replaced C11 with a 470nF capacitor for ghosting fix.
• Replaced C61 with a 22µF capacitor for the "vertical line" fix.

For reference, the SNES is outputting via a RetroGamingCables NTSC CSYNC (attenuated) cable to an OSSC 256 optimised. I can see that the VMODE is correctly switching on the S-CPUN on pin 111, as sd2snes' system information view reports the correct Hz. Similarly, I can see that the OSSC is also getting the same, so assume the correct mode is being set in S-RGB on pin 9.

Installation seems sound and everything is continuous as expected, so not sure what the issue could be. Seems like some frequency is bleeding into a line somewhere, that's causing interference when in 50Hz.

What I do notice is that without any cart, switching on the SNES produces a very noisy black screen. Not sure if that's expected or not…

Not sure if anyone has experienced a similar issue and might be able to provide some insight?

More comparisons:
https://files.sha.wtf/jamie/waNESebi11.jpg
https://files.sha.wtf/jamie/VoQIQONo49.jpg
https://files.sha.wtf/jamie/QOQuPodi10.jpg

I just got my board and I'm attempting to install it in a SNES Mini (following the SNN-CPU-01 instructions) that already has Voultar's RGB Bypass. According to the instructions:

I do have an RGB bypass PCB in this repository. Just take a [look](../../../RGB Bypass/). If you use a version with CSYNC you can connect /CS.o (raw) to this PCB to use it.

I can connect /CS.o (raw) to the bypass board. If I do this, am I taking CSYNC from the CPUN? Or am I taking it from S-Video as per the provided instructions?

Someone wrote me on Twitter the following.

I still trying install that board on SNS-CPU-GPM-02. And i almost finished. But not sure about CCLK_output. Due to schematics i should be in chain before 14 pin of S-Enc (VCXO Input), right?
Can you help me what i should?
Same as with SNS-CPU-RGB-01 remove R29 or R27, and solder through 470 ohm resistor? P.S. I use 8 pin of s-enc, not 7 as in s-rgb. Others seems the same.

Or if you have good schematics of SNS-CPU-RGB-01, with s-rgb and right names of caps and res, please share. Thanks.

Or just explain, where in schematic R4 from your installation manual on SNS-CPU-RGB-01. Right after 3 pin of S-PPU2, or right before VCXO input on S-RGB?

I need to know where exactly R4 in chain between PPU2 and S-RGB.

Later I also received this picture

Hi, is the cs.o raw (ttl) dejittered too, because it only says dejittered for the cs.o buff (75 ohm) in the readme file. If both are dejittered which one would you recommend to use. I'm using a RGB Bypass Amp from Tzorri Mahm.

Best regards

I'm using the old Switchless Modboard (https://github.com/borti4938/SNES_MultiRegion_with_DeJitter_QID/tree/master/old.pcbs/SNES-1Chip) in my Switchless modded 1CHIP Super Famicom.

The console ran perfectly well for the first 5-6 months, I've been playing a lot on it.
But since a couple of weeks, if I want to boot cartridges (or my FXPAK Pro), the console won't output a video signal after I turn it on. The screen just stays black. I already found a workaround: if I press the reset button (short), then the cartridge will boot. Sometimes I have to press the reset button twice, then it boots.

This doesn't annoy me much, since the workaround fixed the "problem" entirely. I was just wondering what kind of problem this could be. I haven't had this behaviour in the first couple of months, and now, all of a sudden this problem exists.

Thanks for and advice or help.

Hello. I want to say thank you for such a good mod, it works just fine. But I still saw some strange picture. After I installed this mod in my console, I noticed that the colors changed in the image at the top of the screen. Sometimes they can be seen very well in blue and orange. Sometimes it may flicker a little. I tried two consoles SNSP-CPU-02 and SNS-CPU-RGB-01. Please tell me, can this be fixed somehow?

This is before installing the mod.

This is after installing the mod.

This is more of a question than an issue...
I have an Altera USB-Blaster that I kept for flashing updated firmwares to the nesrgb. On my DIY-adapter I connect a 3.3V power supply.
Since you mentioned "please use the 5V power supply rail to not harm the DC converters" in the readme I'm unsure if it's safe to use the 3.3V instead of 5V while the pcb is not installed into the console yet.

Does this board support 1CHIP-03? If so, is the installation procedure the same as the other 1CHIP models?

I had a hard time figuring out all possible combinations of parts and connections when using the SMR20200325 and SNES_RGBAmp_wCSYNC into a SNSP-CPU-1CHIP-02, so I made this flowChart:

https://www.dropbox.com/s/7jbngqexuoay9ys/FlowChart_-_SMR20200325_and_SNES_RGBAmp_wCSYNC.pdf?dl=1

alternative download/view link:
https://drive.google.com/file/d/19KD6h5U29KIDaIiM5uR2cwm81-4a2RUT/view?usp=sharing

If you find the time to review it and leave some feedback for improvements, I'd like to offer to make a chart for all SNES models, so you can add them to the repository for others that may have trouble gathering all the info on both projects.

Adding a sliding switch is not always an elegant solution to enable/disable dejitter via SJ31.
I think it should be possible to add a transistor to enable/disable dejitter. SJ31 should still remain because of backwards compatibility. Of course it will need a circuit to prevent SJ31 and the transistor to both be enabled and disabled at the same time. In any case if SJ31 is closed, this should count as master. This will require a new pcb.
For the button combination I would suggest the retrobit combination and switch Start with Select.
This is mostly for speedrunners and I even try to come up with a circuit and software by myself.