Closed brandon-arnold closed 1 year ago
Yes, "Active FrameTime Lock enabled, adjusting external clock gen frequency" means your clock generator is working correctly in more recent versions of the firmware.
It's also better to leave it enabled now despite having one installed to take advantage of the new and improved clockgen-based sync lock method.
Yes, "Active FrameTime Lock enabled, adjusting external clock gen frequency" means your clock generator is working correctly in more recent versions of the firmware.
It's also better to leave it enabled now despite having one installed to take advantage of the new and improved clockgen-based sync lock method.
Thanks, @YoImLee . Does it do anything different, without the clock gen mod?
In my troubleshooting, there were times I was pretty sure the a pin or two wasn't connected right, but as I recall I got the same output in the console.
If the clock generator isn't installed (or not correctly installed) and you activate the frametime lock option you will see "Active FrameTime Lock enabled, disable if display unstable or stays blank!" instead.
This also happens if you toggle the "Disable External Clock Generator" option and restart the GBS. I believe it's also possible to get a "GBS board not responding!" message if the SCL/SDA wires are swapped around, but I'm not sure.
Is the clock gen test method up to date in the doc? I've performed a GBS-C AIO build, including the clock mod. The clock mod was done according to both Rama's Github documentation and the GBS-C AIO documentation. But the clock generator test is not passing, for me.
I should say before anything, I do not trust the AIO PLCC connection with the chip on the GBS-8200. That thing is finicky and I've had to pin it down with zip ties to even get the WiFi module to stay on and the GBS Control settings in the UI to actually change the resolution correctly. But, it is working generally, now, and as I mention below, I've done some fail-safes to ensure the clock mod connections.
The documentation states:
When I perform this test, the console reads:
This indicates the clock mod isn't working, but I've tried so many things to fix it. Has anyone confirmed this is up-to-date and indeed the right way to validate the clock mod?
Things I've tried