Skip to content
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

VERTICAL BAR OVER HDMI on R3 with core 5.1 #166

Open
paich64 opened this issue Nov 24, 2024 · 11 comments
Open

VERTICAL BAR OVER HDMI on R3 with core 5.1 #166

paich64 opened this issue Nov 24, 2024 · 11 comments
Assignees
Labels
5.2 Maintenance bug Something isn't working

Comments

@paich64
Copy link

paich64 commented Nov 24, 2024

@sy2002 @MJoergen The issue is back again, but this time on R3 with core 5.1.

@jherig is experiencing VERTICAL BARS over HDMI with his MEGA65 from batch 1 using the C64 core 5.1

Because of personal constraints he had to postpone his experience with the mega65 and now he is starting to use his machine and just discovered the issue.

The link of the original discord discusssion is here :
https://discord.com/channels/719326990221574164/719326990221574168/1310035903896354886

He has provided the following pictures:

Mega65 model:
2024-11-23_18_52_19-Vertical_bars_over_HDMI___HyperRAM_controller_lock-up_Issue_145_MJoergen_C6

c64 core version:
2024-11-23_19_07_44-JiffyDOS_and_alternative_Kernals_-_C64_for_MEGA65_Mozilla_Firefox

The issue occures very quickly when he starts the core.

I'm waiting for him to confirm if this happens when he uses the standard kernal, since original pictures where specifically named "Jiffydos" so i need to be sure it's not related.

Unfortunately he does not have a VGA monitor so there's no way to confirm if vga is working find (presumably, if it's the issue we're well aware of, vga should be working).

We can't test V4 nor V5.0 because the latest stable Mega65 core loader fails to check CRC and won't flash these core versions.

If you see other tests that he could perform please let me know.

In addition to this, @jherig mentionned he is having backpower issues here : https://discord.com/channels/719326990221574164/719326990221574168/1310096636529217677

Now i don't know if backpower issues can lead to these vertical bars.

@jherig
Copy link

jherig commented Nov 24, 2024

To recap, this has happened with and without JiffyDos kernel, it happens approximately 60% of the time, and usually within 3 minutes of core boot up. The core appears to still be working, as sound effects etc still are happening and seem to follow what inputs you can supply and guess at what might be happening without visual reference.

@paich64
Copy link
Author

paich64 commented Nov 24, 2024

To recap, this has happened with and without JiffyDos kernel, it happens approximately 60% of the time, and usually within 3 minutes of core boot up. The core appears to still be working, as sound effects etc still are happening and seem to follow what inputs you can supply and guess at what might be happening without visual reference.

@MJoergen @sy2002 exactly the same symptoms as the one we observed on R6.

@sy2002
Copy link
Collaborator

sy2002 commented Nov 25, 2024

@MJoergen Interesting. The first R3 that shows HDMI jailbars. Question: Is the fix that we did for R6 a "pure R6" fix, or could we (i.e. you) just build an R3 bitstream of V5.2A1 i.e. commit f4df717 for @jherig to test? Currently we only did build that for R6 machines, this is why I ask, because I do not remember, if this fix was a R6 specific fix or if it might improve all builds for all platforms.

@sy2002 sy2002 added bug Something isn't working 5.2 Maintenance labels Nov 25, 2024
@MJoergen
Copy link
Owner

@jherig Please try this file:
C64MEGA65_V5.2A1_R3.zip

@jherig
Copy link

jherig commented Nov 25, 2024

Installled and testing. First impressions are good (no repeats of the barcode).

@sy2002
Copy link
Collaborator

sy2002 commented Nov 25, 2024

@MJoergen Thank you for your support and for acting that fast. @jherig 's feedbeck sounds encouraging. Question: Is C64MEGA65_V5.2A1_R3.zip "just an R3 build" of commit f4df717 or did you do anything else? (Sorry for asking dump questions that I could theoretically research on my own, I am travelling a hell of a lot of very limited nerd time ;-) But I am still curious.)

@MJoergen
Copy link
Owner

Sorry for not explaining. I did indeed just make an R3-build from the commit f4df717 .

@sy2002
Copy link
Collaborator

sy2002 commented Nov 26, 2024

@jherig Thank you for reporting this bug and for testing.

Can you please test two/three weeks or so and report back here, if this fix leads to a stable and reliable core?

Background info for you: @MJoergen and I are planning to release an official V5.2 "Maintenance" release end of this year / early next year that stabilizes a lot of aspects of the core. We never encountered the problem you have on any R3 board so far (but we had a lot of problems on R6 boards) so this is a super important finding - also for making sure that V5.2 is the most stable release we ever had...

@jherig
Copy link

jherig commented Nov 26, 2024

After 1 day of testing (18 boots, approximately 3.5 hrs of runtime) there has been no repeat of the 'barcode' symptom. So things look very promising indeed as to this being a solution. Will keep testing.

@sy2002
Copy link
Collaborator

sy2002 commented Dec 7, 2024

@jherig I am curious: Is this fix still working for you and appears to be stable?

@jherig
Copy link

jherig commented Dec 8, 2024

After quite a bit of testing, the problem has not reoccurred. Things are looking quite good!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
5.2 Maintenance bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants