bobrocks95
Forum Replies Created
-
AuthorPosts
-
August 9, 2025 at 3:18 AM in reply to: [SOLVED] No Sync after attempting 1.00 bodge wire on 1.6 hardware #66781
Issue resolved, sorry for the trouble. No clue what was doing it but I was grounded over by the R35 pad to something. OSSC is working now (though my NES Lumacode install is not)
August 7, 2025 at 11:55 PM in reply to: [SOLVED] No Sync after attempting 1.00 bodge wire on 1.6 hardware #66768Well here’s something that might actually be helpful- that pin on U1 and the closer pad on R35 appear to be connected to ground. Is that expected or did I maybe hit a via near the pin on U1 or something? I’d assume if you just needed to ground the pin or pad there’d be a much closer connection point for the mod.
EDIT: Duh, open source project with gerbers available. Looks like the U1 pin is normally floating, and then after the bodge wire, should connect to pin 46 on the FPGA, IO_16 if that earlier diagram is right?

Still don’t know how I managed to ground it all- the R35 pad I guess is surrounded by ground plane, maybe I need to check if I scraped some soldermask off and managed to short to it???
-
This reply was modified 8 months, 3 weeks ago by
bobrocks95.
-
This reply was modified 8 months, 3 weeks ago by
bobrocks95.
August 7, 2025 at 11:46 PM in reply to: [SOLVED] No Sync after attempting 1.00 bodge wire on 1.6 hardware #66767Going to take another stab at this tomorrow. Wanted to ask again though, if I remove the wire, do you know where the far pin on U1 connects to test, or is it left floating on the stock PCB? Same question for the pad on R35, if there’s a way to verify either of those are still in-circuit and good.
Thanks for the help so far marqs.
August 1, 2025 at 8:27 PM in reply to: [SOLVED] No Sync after attempting 1.00 bodge wire on 1.6 hardware #66725Difficult to measure with no help from the silkscreen, but if the below pinout is correct (model number does differ slightly), then pin 126 is grounded. It was around the 2 on the U2 marking, and I counted in from both directions verifying other ground points as I went.

-
This reply was modified 9 months ago by
bobrocks95.
August 1, 2025 at 12:31 AM in reply to: [SOLVED] No Sync after attempting 1.00 bodge wire on 1.6 hardware #66717Any thoughts on what I can check marqs? Hoping to try and square it away this weekend while I have access to my soldering stuff. I suppose I’ll flux and touch up both points if I don’t hear anything else specific.
July 25, 2025 at 9:52 PM in reply to: [SOLVED] No Sync after attempting 1.00 bodge wire on 1.6 hardware #66675Good point- things look perfectly fine with PS1, PC Engine, and dejittered Famicom. This is again back on firmware 0.90 with the wire still installed.
No shorts apparent on the resistor side between any of the 4 pads.
July 25, 2025 at 3:08 AM in reply to: [SOLVED] No Sync after attempting 1.00 bodge wire on 1.6 hardware #66665Some crummy installation photos- never have been able to get good zoom/closeup shots of anything with a phone camera.
https://photos.app.goo.gl/ZsxXaMcJe4E1eU4V7
Checked continuity again for fun, and the chip pins aren’t bridged and things are beeping fine to the inner R35 pad… Still curious if there’s a better place up the board or anything to confirm continuity, or whatever else you can tell me marqs. Thanks!
July 23, 2025 at 12:17 AM in reply to: [SOLVED] No Sync after attempting 1.00 bodge wire on 1.6 hardware #66653Hi marqs,
Just flashed 0.90 to test and I get a very flickery/jittery image seemingly regardless of output modes and settings, though some are better than others. This is feeding into a Tink 4K’s HDMI input.
May 7, 2021 at 1:18 AM in reply to: Intermittent flickering pixels (usually green) in x5 mode #47204Assuming the TX Mode setting is the right one to change, there was no difference in DVI or YCbCr444 mode. Haven’t had a chance to try out any older firmware builds yet.
May 6, 2021 at 3:01 AM in reply to: Intermittent flickering pixels (usually green) in x5 mode #47178I finally tracked down some old shmups posts about the alternative firmware- it was related to fitter seeds used at compile time.
https://shmups.system11.org/viewtopic.php?p=1378441#p1378441
Those small flickering pixels are the kind of thing I’m seeing- not awful or anything, but definitely annoying when they crop up.
Marqs, would it be possible to recompile the latest firmware with an alternate seed if that’s easy enough to do? Maybe it’s a crapshoot and I’m misunderstanding though. In the meantime I will try some older firmware versions and see if I can get one that works better.
May 3, 2021 at 11:24 PM in reply to: Intermittent flickering pixels (usually green) in x5 mode #47145Hmm, I was using a powered HDMI splitter, which was the first thing I got rid of to make sure. But I’m straight to the TV (LG B9 OLED) now, and tried with different cables, including my nice HDMI 2.1 certified one that works with my PC at 4K 120Hz 10 bit color, so absolutely overkill.
I thought I’d check the VGP forum for an official topic on this.
Do people really dislike the OSSC’s 480px2 scaling that much? Even with upsample x2 enabled? I hate how 480p looks on my HDTV, I want it much sharper- exactly what the OSSC can offer (with from what I understand a middle-ground sharpness with upsampling as well).
The added value is incredibly obvious to me- full digital signal path for HDMI mods that output 480p max. That’s Gamecube, Wii, and surely more in the future. A little future-proofing goes a long way.
And as someone said that HDMI mod creators should instead implement upscaling for their mods- why raise the cost and complexity of every single HDMI mod when you could instead do all the upscaling with a single device that a lot of people doing these console mods are already going to own?
Plus, I’ve already invested a lot of money in a GCVideo modded Gamecube- if the project switches to a larger FPGA that can upscale I’m looking at a cost similar to a new OSSC anyway to completely redo the mod. I’m sure others would feel the same way.
-
This reply was modified 8 months, 3 weeks ago by
-
AuthorPosts
