Multiload problems

[lunadog]

I can load multiload CRT images from the One Load collection fine, but when I press the menu button I get "communication with cartridge failed" error. If I press menu enough times I can sometimes get back to the games list and switch to a single load which works fine.

This is with breadbin v1.51.
Have reproduced same issue on C64C.

[lunadog]

Just tried to replicate today on C64C after cold boot and the problem is much more intermittent - only occurred 1 time out of 10. Completely baffled as to why.

[KimJorgensen]

The issue you are describing could be caused by a bad connection to the C64, see #77
Try to clean the connector on the PCB and see if that helps

[lunadog]

It only happens with the larger multiload one load images so I think it is more likely to be a timing error. I will see if there is any improvement with contact cleaning though

[lunadog]

Just tried contact cleaning and no improvement (might be worse in actual fact). No issue with single load CRTs only multi-load.

Also affects another user - see post by Sebby75 here: https://www.lemon64.com/forum/viewtopic.php?t=76305&start=645

[lunadog]

I've just downloaded to 1.31 (from 1.51) and multiloads work fine so must be a regression..

[lunadog]

1.35 is the last version that doesn't have this bug. From 1.36 I get the error about 1 in 2 times (not as bad as later versions)

[KimJorgensen]

Did you try to adjust the phi2 offset with the newest firmware?
There was a lot changes to the timing in theres old releases, trying to make the cartridge work on as many C64s as possible

[lunadog]

Hi - yep - phi2 offset on 1.51 didn't help. It is working perfectly with 1.31-1.36 so something must have happened to the code between 1.36 and 1.37 that broke it on my computer (not having looked at the code, maybe not waiting long enough for the cartridge to be ready?)

[KimJorgensen]

Which phi2 offset values did you try?
As said, changes was done to the timing in theses releases and why I'm asking about the phi2 offset

[lunadog]

I tried a number of different settings (+/- 3-5) up to the level that the cartridge stopped being recognised. I am not really sure what settings I would need to use though. The Phi2 numbers seemed to be around 100+ different from the target value but changing them more than 10 or so led to the cartridge no longer being recognized from what I recall. I can do some more extensive testing on this if you advise what phi2 values to try. Best wishes, James

…

On Tue, Dec 3, 2024 at 1:39 PM Kim Jørgensen ***@***.***> wrote: Which phi2 offset values did you try? As said, changes was done to the timing in theses releases and why I'm asking about the phi2 offset — Reply to this email directly, view it on GitHub <#206 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABD32PVXTFUIAUDL5WNOSP32DWYAJAVCNFSM6AAAAABSOVPFY6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJUGU4DGNRSHA> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>

[KimJorgensen]

The reports I have received suggest -1 or -2 for some C64 breadbin/longboards and +1 or +2 for some C64C/shortboards. This is very machine specific what offset is needed, if any.
If this doesn't change the stability we need to look elsewhere

[lunadog]

OK - I have tried all settings from -5 to +5, and there is no effect. I also went back and tested the old firmware. I was incorrect about 1.36 - the bug is still there. Version 1.35 works fine though.

…

On Tue, Dec 3, 2024 at 4:57 PM Kim Jørgensen ***@***.***> wrote: The reports I have received suggest -1 or -2 for some C64 breadbin/longboards and +1 or +2 for some C64C/shortboards. This is very machine specific what offset is needed, if any. If this doesn't change the stability we need to look elsewhere — Reply to this email directly, view it on GitHub <#206 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABD32PVALY772K7VF2RUB4L2DXPH5AVCNFSM6AAAAABSOVPFY6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJVGEYDENJUHA> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>

[KimJorgensen]

OK, thank you for all your testing. Since I can't reproduce the problem on my C64s, I need some more information to find the cause.
When you get the error, does it only say "Communication with cartridge failed"? Or does the error message also say "Unexpected command" or
"Check hardware"?
What happens if you press reset after you get that error? What happens if you power cycle the C64?

[lunadog]

It just says communication with cartridge failed. If I press reset it restarts the game (alien syndrome in this case). If I cycle the power it restarts the game and still often gives the error message when I press menu (maybe 7 or 8 out of 10 times).

…

On Tue, 3 Dec 2024, 20:16 Kim Jørgensen, ***@***.***> wrote: OK, thank you for all your testing. Since I can't reproduce the problem on my C64s, I need some more information to find the cause. When you get the error, does it only say "Communication with cartridge failed"? Or does the error message also say "Unexpected command" or "Check hardware"? What happens if you press reset after you get that error? What happens if you power cycle the C64? — Reply to this email directly, view it on GitHub <#206 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABD32PQA2UYE3Q5GNHSXR732DYGTFAVCNFSM6AAAAABSOVPFY6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJVGQ3DKMZZGA> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>

[KimJorgensen]

I found a race condition that could cause Kung Fu Flash to get stuck with the "Communication with cartridge failed" message. A fix has been included in the latest release .
@lunadog Can you please report back if this indeed solves the problem?

[lunadog]

Appears to now be fixed. Thanks so much!