Open sy2002 opened 2 weeks ago
Please consider adding BUFR on RWDS strobe signal, it should fix the HyperRAM issue on R6 and be safe to use on other rev also,
@AnttiLukats Thank you for your support! We are now testing your solution proposal with a "Release Candidate 3A", here is the commit: https://github.com/MJoergen/C64MEGA65/commit/ce927cb387150162837e71112ffe995fd870a561
@paich64 I will approach you via Skype on this to please do some very thorough testing.
@sy2002 @.***> testing is in progress ;)
Le ven. 21 juin 2024 à 12:18, sy2002 @.***> a écrit :
@AnttiLukats https://github.com/AnttiLukats Thank you for your support! We are now testing your solution proposal with a "Release Candidate 3A", here is the commit: ce927cb https://github.com/MJoergen/C64MEGA65/commit/ce927cb387150162837e71112ffe995fd870a561
@paich64 https://github.com/paich64 I will approach you via Skype on this to please do some very thorough testing.
— Reply to this email directly, view it on GitHub https://github.com/MJoergen/C64MEGA65/issues/141#issuecomment-2182462028, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABROXOCLMGZWAMCIBDOPCVLZIP4XHAVCNFSM6AAAAABJL6SL2SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBSGQ3DEMBSHA . You are receiving this because you were mentioned.Message ID: @.***>
The R6 board that is in the hands of the 2024 MEGA65 customers (aka 2024 batch) behaves differently than the R5 board. While the M2M HyperRAM implementation was rock solid on R3/R3A, R4 and R5, it became unstable on R6 leading to HyperRAM lock-ups that manifest themselves for example as HDMI stopping to work (as ASCAL needs HyperRAM). The problem would also be visible when one uses the REU or CRTs.
Here is a high level problem description that I sent to Trenz:
After a discussion, @MJoergen and I decided this road ahead, which will also impact the M2M framework:
@paich64: FYI so that you have this issue on your radar. I will suggest tests for you as soon as time is ripe.