[Nizce]

Thanks!

Then I’ll start with checking continuity between pin 46 on U2 and pin 25 on U2. To verify if my workaround of the broken pad is to blame or not, for the problems I’m having.

If there is no connection I might go ahead and using pin 46 on U2 instead(although it’s very small and high stakes).

• This reply was modified 1 year, 7 months ago by Nizce.

[Nizce]

Hi!
Just made the mod to my OSSC and updated to 1.08.

During the mod I managed to rip the inner pad of R35..(never solder when you’re in a hurry) 🙁
So i scraped the traces leading to R35 and managed to solder the wire to the traces and onto the chip leg.

Firmware update went fine, and test picture looks as good as before.

But when connecting my PC via VGA i do get a vertical line which is “transparent” and darker. I tried to take a picture, but was quite hard to make it noticeable.

When in DOS the OSSC flickers rapidly between 1712-p and 1713-p and also between 120.29kHz and 120.22kHz. Please see pictures.

So I downgraded to firmware 0.9 and the picture is back to normal.

 

Since I ripped the pad, it might be that I got a bad connection when soldering to the traces.
Is there any way to verify that the actual hw mod went well?
Also, is there anywhere else on the board that I can bridge with the chip pin instead of R35 just to be sure?
Never used kicad but just fired it up, if I understand it correctly, would it be possible to use pin 46 on the chip labelled EP4CE15E22 as a substitute for R35?

• This reply was modified 1 year, 7 months ago by Nizce.
• This reply was modified 1 year, 7 months ago by Nizce.
• This reply was modified 1 year, 7 months ago by Nizce.

[Author]

Posts