No Sync from any source after attempting 1.00 bodge wire on v1.6 hardware

NewHome Forums OSSC, OSSC Pro and DExx-vd isl OSSC – Discussion and support No Sync from any source after attempting 1.00 bodge wire on v1.6 hardware

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #66611
    bobrocks95
    Participant

      Hi there, looking for a sanity check or debugging steps I can take for updating to the latest firmware on an older OSSC model.

      Haven’t used the OSSC in quite awhile, but I removed R35 and installed the bodge wire to the far leg on the video chip as described in the firmware v1.xx thread.  I verified with a multimeter that the pins on the chip weren’t bridged and that the closer pad to R35 had connectivity.

       

      After getting home (it really sucks but my soldering equipment is elsewhere), flashing firmware v1.12, and trying out NES lumacode I’m getting a solid No Sync message for the AV2 RGsB input.  Not knowing if the OSSC update or the lumacode install was the issue, I hooked the VGA output from my Extron VGA switch to AV3 and tried some other sources (namely SNES via RGBS) and still got a no sync message.  I’m forgetting what the OSSC supports but this would be TTL RGBS with sync on the HSync pin, which should be correct?  EDIT: Also tried Dreamcast RGBHV for something more standard and still had the No Sync message.

       

      Anyways, does this sound like it’s definitely a bad install of the bodge wire?  I still get the test pattern and everything else seems to be working on the OSSC side, other than sync input processing.

      Is there a test point further on from the R35 pad where I can check continuity between the video chip’s end pin and said test point?  I exposed a bit of solder mask near R35 so maybe I managed to sever a trace or something???

      • This topic was modified 1 day, 15 hours ago by bobrocks95.
      • This topic was modified 1 day, 15 hours ago by bobrocks95. Reason: Tested Dreamcast RGBHV
      #66633
      marqs
      Participant

        I recommend downgrading to 0.xx firmware and testing if that still works (no need to revert the mod).

      Viewing 2 posts - 1 through 2 (of 2 total)
      • You must be logged in to reply to this topic.