You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,8 +53,8 @@ I want to get the board out to a few people before opening the flood gates. I'm
53
53
begin trying it on M2s and M3s, I want to see what the results are. It *appears* that it should work just fine, and may even work on an M1 with the
54
54
right signal placement, but I'm well aware that with hardware you never know for sure until you've actually seen the results.
55
55
56
-
I did some experimentation with providing my own on-board clock and ignoring the dot clock from the TRS-80, which produced something that *kind of* works.
57
-
Unfortunately I would need to oversample the signals considerably (probably at least 10X) and then come up with an algorithm for using the oversampled
56
+
I did some experimentation with providing my own on-board clock and ignoring the dot clock from the TRS-80, which produced something that *kind of* works. I
57
+
would need to oversample the signals considerably (probably at least 10X) and then come up with an algorithm for using the oversampled
58
58
signals, and at this point that's just a bit beyond my Verilog skills. I'll probably keep toying around with it over time. It's clearly possible, but
59
59
just not as easy as taking the dot clock from the motherboard and using it to synchronize the incoming video. I suspect this is why many -ToVGA boards
60
60
have subtle issues that require options and menu systems to work around. For now the production version of the board still requires the dot clock.
0 commit comments