-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: Is there an easy transistion? #3
Comments
Your theories about possible problems in your timing generator all sound reasonable. It will probably help us both to try inserting my timing generator in your project. Happy to assist... You'll need something like this to translate my outputs to yours:
|
Thank you for your support - very helpful! So I will do the "plug-in" experiment and plug-in your timing generator in our project to see, if this fixes issue #2 . |
@amb5l Today I will perform the "plug-in" experiment. What is the idea behind / semantics of |
You can safely ignore it - set align to zero. |
@amb5l There is no polarity input in |
@sy2002 Yes that's correct, the sync polarity of |
@amb5l Oh - then everything only worked "by chance" in past, because I mis-understood your inputs at |
I will close this issue because I managed to plug your timing generator into our gbc4mega65 project and it works like a charm on my Monitor. Now we can continue to work on issue #2 using your timing generator and check, if it solves it. |
@amb5l while reading your comment #2 (comment) a nagging little thought came up:
I reckon that our timing generator, originally developed by Scott Larson and "improved or damaged" by me and @MJoergen is not accurate.
Why should it be necessary to tweak V_BP and V_FP at all instead of using the reference values?
Or asked the other way round: Why are we getting HDMI Analyzer errors while just sticking in the correct reference timing values?
Here are possible answers:
So just in case that the new bitstream is not solving issue #2 and/or just in case we want to improve the code quality in our project:
I wonder, if there is a kind of quick and easy way to just replace our our timing generator with your timing generator.
Our timing generator outputs these signals:
Your timing generator outputs these signals:
We actually do need
disp_ena
andcolumn
androw
for our overlay menu and other things. So we would need to make sure that there is a way to map your output to ours and our a formula that translates ax/ay to row/column.Also some parts of the screen scaler depend on certain timing characteristincs, I do remember that @MJoergen added 1-clock-cycle delays here and there so that the Game Boy on MEGA65 screen looks as it should. Maybe he can chime in here, too.
The text was updated successfully, but these errors were encountered: