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

Very rare REU/HyperRAM issues: TreuLove #55

Closed
sy2002 opened this issue May 10, 2023 · 6 comments
Closed

Very rare REU/HyperRAM issues: TreuLove #55

sy2002 opened this issue May 10, 2023 · 6 comments
Assignees
Labels
5.1 (R4/R5 Surge) bug Something isn't working

Comments

@sy2002
Copy link
Collaborator

sy2002 commented May 10, 2023

Very rare HyperRAM/TreuLove issues: We are talking about two users and strange "fixed by re-synthesizing" situations.

Since these discors links are only readable for me (sy2002): I need to first describe the situation better here in GitHub before we can tackle it.

@sy2002 sy2002 added bug Something isn't working V6 or later labels May 10, 2023
@sy2002 sy2002 changed the title HyperRAM/TreuLove issues Very rare HyperRAM/TreuLove issues May 10, 2023
@sy2002
Copy link
Collaborator Author

sy2002 commented Jun 17, 2023

Discord user "muse" aka on GitHub as @sho3string confirmed on June 10, 2023 (Skype conversation) that this issue is still reproducible with our Version 5 RELEASE CANDIDATE (WIP-V5-B4).

@sy2002 sy2002 changed the title Very rare HyperRAM/TreuLove issues Very rare REU/HyperRAM issues: TreuLove Aug 29, 2023
@sy2002
Copy link
Collaborator Author

sy2002 commented Aug 29, 2023

Maybe related to this one: #86

@sy2002
Copy link
Collaborator Author

sy2002 commented Nov 2, 2023

Quotes from a Skype conversation between MJoergen and sy2002:

MJoergen:

I have an idea to tackle GitHub issue 55. My hypothesis is to change line 292 in digital.vhd from "N_BURST => 256" to "N_BURST => 128". This will reduce the maximum time the C64 core needs to wait before getting access to the HyperRAM.

I'm fully aware of your vigilance regarding graphics. So there are two questions to answer:

  1. Does this change actually fix the problem seen (i.e. the specific issue)?
  2. Does this change have any negative side-effects (e.g. graphics glitches or other problems)?

I'm 99.999999% sure that 2) is not a problem. However, this is something that is best verified in practice, probably with the help of Olivier. So such a change - if implemented - should be carefully planned.

@sy2002
Copy link
Collaborator Author

sy2002 commented Nov 2, 2023

@sho3string (aka muse) and @mpryon can you please re-test the TreuLove issue with this Alpha 3 version of the upcoming V5.1 core of the C64 (attached to this comment)? @MJoergen came up with an idea that might fix the bug.
c64v51a3.zip

@sho3string
Copy link

I tested two versions ( reu1750 release and the first release )

No glitching in both cases. Well done guys.

@sy2002
Copy link
Collaborator Author

sy2002 commented Nov 3, 2023

Thank you @sho3string ! :-)

@sy2002 sy2002 closed this as completed Nov 3, 2023
MJoergen added a commit that referenced this issue Nov 14, 2024
joystick 2 disability fixed - Issue 54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
5.1 (R4/R5 Surge) bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants