ramapcsx2 / gbs-control

GNU General Public License v3.0
773 stars 110 forks source link

Installed clockgen and gbs board is not responding #439

Open israpps opened 1 year ago

israpps commented 1 year ago

As title says. Asked a friend to solder the clockgen (he makes boards for a kinda big factory, so he surely knows what he did)

got it back today, plugged it in and did not get any signal

opened web UI and enabled developer mode to see the log

touching any item displays on log

GBS board not responding!

any ideas?

will attach pics of the board in a few mins

In the meantime, ill try updating the firmware to the newer builds, as the clockgen library has been updated

israpps commented 1 year ago

this is a duplicate of #291 buuut. there are no messages there that point into the solution

israpps commented 1 year ago

IMG_20230313_190937472 ![Uploading IMG_20230313_190958270.jpg…]()

israpps commented 1 year ago

@ramapcsx2 any idea?

ramapcsx2 commented 1 year ago

Not really.. The message means that the GBS chip didn't respond on the I2C bus. It could be power related, signals conflicting (SDA/SCL swap or so), etc.

israpps commented 1 year ago

Not really.. The message means that the GBS chip didn't respond on the I2C bus. It could be power related, signals conflicting (SDA/SCL swap or so), etc.

I'm using a 6v PSU IIRC

israpps commented 1 year ago

IMG_20230313_095423026

israpps commented 1 year ago

I just installed the clockgen. The esp8266 was working flawlessly for some months before

ramapcsx2 commented 1 year ago

Okay, try to remove the clock gen SDA and SCL wires. If it then works, you know that the I2C bus is getting bad with the clock gen on it, and you can look into why that might be.

israpps commented 1 year ago

Okay, try to remove the clock gen SDA and SCL wires. If it then works, you know that the I2C bus is getting bad with the clock gen on it, and you can look into why that might be.

could it be swapped SDA/SCL? (either by mistake of who installed it or by bad labeled clockgen), I bought it here on argentina, so its 99% not original xd.

israpps commented 1 year ago

Tested the GBSControl UI clockgen related stuff and it seem to respond

user command f at settings source 10, custom slot 65, status 0
GBS board not responding!
user command s at settings source 0, custom slot 65, status 0
GBS board not responding!
user command r at settings source 5, custom slot 65, status 0
Deinterlacer: Motion Adaptive
user command X at settings source 5, custom slot 65, status 0
ExternalClockGenerator disabled
user command h at settings source 5, custom slot 65, status 0
GBS board not responding!
user command g at settings source 1, custom slot 65, status 0
GBS board not responding!
user command f at settings source 3, custom slot 65, status 0
GBS board not responding!
user command 5 at settings source 0, custom slot 65, status 0
FTL on
Active FrameTime Lock enabled, adjusting external clock gen frequency
user command g at settings source 0, custom slot 65, status 0
GBS board not responding!
user command f at settings source 3, custom slot 65, status 0
GBS board not responding!

@ramapcsx2

Could this mean the issue is on the ESP8266 ---> GBS connection instead of the clock gen?

Re readed docks of clock gen...

Activating frametimelock shout trow

Active FrameTime Lock not necessary with external clock gen installed
ramapcsx2 commented 1 year ago

"GBS board not responding!" means that the main ASIC is not responding (or responds with errors) on the I2C bus. It means that it is still not fixed. If it was working before you installed the clock gen, then something broke. You should first try to restore the old functionality, then slowly re-add the clock gen to see where it breaks.

YoImLee commented 1 year ago

"FTL on - Active FrameTime Lock enabled, adjusting external clock gen frequency" Is what you want to see on recent versions of gbs control. It is better to leave frametime lock enabled now even with the clock gen installed.

In the first picture, the pin next to pin 40 for the clock generator input is tinned and may be bridged. There might also be a bridge in the second picture at the debug pin. Kind of hard to tell though in both cases, I might be wrong.

israpps commented 1 year ago

"FTL on - Active FrameTime Lock enabled, adjusting external clock gen frequency" Is what you want to see on recent versions of gbs control. It is better to leave frametime lock enabled now even with the clock gen installed.

In the first picture, the pin next to pin 40 for the clock generator input is tinned and may be bridged. There might also be a bridge in the second picture at the debug pin. Kind of hard to tell though in both cases, I might be wrong.

Issue must be related to clockgen install...

As I used the board without it for months.

And the esp setup hasn't been changed.

israpps commented 1 year ago

Tested with multimeter...

Clockgen wire that goes into scaler chip is not bridged (measured continuity between CLK0 and the pin next to the one soldered)

Debug pin on GBS chip is not bridged.

To be sure, I checked continuity of SDA/SCL from clockgen pin up to their esp8266 equivalents. Everything ok there

Only possible clue is power.

The esp8266 is taking power from the 3.3v of GBS board

ramapcsx2 commented 1 year ago

Can you please unsolder the 2 clock gen SDA/SCL wires and check what happens then?

israpps commented 1 year ago

Can you please unsolder the 2 clock gen SDA/SCL wires and check what happens then?

Same issue

There is a short between r11 and r37... Is that normal?

israpps commented 1 year ago

Also, made esp8266 take power from PSU

israpps commented 1 year ago

IMG_20230317_120923586~2 I have continuity testing between red and yellow dots

israpps commented 1 year ago

Disconnected whole clock

GBS board is still dead🙄

israpps commented 1 year ago

Anyone can help troubleshooting this?

Or should I buy a new GBS board instead

ramapcsx2 commented 1 year ago

So since it's still dead with the I2C wires for the clock gen removed, it means that when installing, you accidentally broke something else. Find that "else" next. You mention a short between R11 and R37. One side of them would be correct (the Vcc side), the other must not be shorted. If you probe the 2 sides and both are shorted, this is your problem.

israpps commented 1 year ago

not sure what else to test

tried everything that came to my mind... Not sure what else to do!

ser51 commented 1 year ago

I have been successfully using GBS 8220 + ESP8266 + SI5351 for a year. But since yesterday, the device began to give me "GBS board not responding!". Checked all wiring. All OK. Disconnected SI5351, the problem did not go away. My problem was solved only by replacing the Y1 quartz with 27.000. Perhaps someone will help.