Replies: 1 comment
-
You simple modify the firmware (.uf2) file with SKpicopatch firmware.uf2 15 11 20 (default timing value 15 and 11, and offsetting paddle values by 20 <- try slighty larger values if it doesn't help) or SKpicopatch firmware.uf2 15 11 100 (100 = 80 + 20, meaning "offsetting up to 20, when diagnostic scenario is detected") Before doing that you may want to have a look at the paddle values first, e.g. using https://csdb.dk/release/?id=179703 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Need some help with my SidKick Pico
Ive installed the latest hardware and firmware version of the SidKick Pico on my C64.
I'd like to have my machine pass the Diagnostic with Harness test. But Im getting the "bad SID" and Bad Communications port.
From the GitHub Documentation:
If a diagnostic ROM reports "bad SID" this might be due to too low values (this might be due to capacitors becoming old, ...). You can also check the values with a diagnostic harness in the configuration tool (afaik the diagnostic ROMs check for values between 80 to 120). If they are too low, and you want the diagnostic ROM to pass, you can offset them (statically or only then a diagnostic situation is detected) using SKpicopatch.
Another user posted this:
Turns out the issue was how the paddles were reported.
Frenetic has released a minor revision of firmware.
The latest firmware resolves the issue by permitting paddle offsetting in the firmware patch.
An offset of 20 passes diagnostic 100% 👍
https://github.com/frntc/SIDKick-pico/r ... pico_v0.21
Is there any documentation somewhere that is a little more descript on how to perform this or how to use the SKpicopatch?
Beta Was this translation helpful? Give feedback.
All reactions