GC8TECH
Grand Master
Yes! with out the need to add a manual switchDoes that mean that DDP is now switchable between the two versions in one cart?
@iq_132 This seems to be a decrypted one, it's been since 2018 that i looked at this and i'm sorry to say as i am getting older and more stuff happens irl.. Covid, Newborn all made me forget what i did to re-encrypt this thing for a kovsh board.
I tried re-doing my work, byteswapping etc, but this does not boot on my kovsh board. Am i missing something?
IIRC the only difference between the pinout of 27c160 and 27c322 is that pin 32 is /BYTE and not A20. So having the middle jumper set should force it into word mode. Or you could modify the GAL to output A20 as permanently 1 if you don't want to use the jumper.27C160 version . You might have issues running this on a "Fluffy" PCB. But the 27C322 version i "joined" work fine!
From what I understand the encryption is configured by the boot code on the ASIC. I guess one option would be to remove the ASIC and connect the EPROM directly to the connector, the other is to use a later board that uses the encryption for external ARM code.If nothing else helps and this works 100% confirmed on non-encrypted boards, how do i stop the MCU from doing its work and run non-encrypted mode?
Can you make a video of it so I can see exactly where it crashes and see what it does when it crashes? I've got a couple of guesses as to why, but nothing concrete without more info.@GC8TECH & @iq_132
Do you have a crc for the file i should be using?
I had a free hour today, but the white label (version-a) still crashes for me at the exact same point.
There's mention of the timer on the startup, it still counts down on mine. I'm using a KovSH boot, perhaps the MCU needs some sort of command to keep alive?
Black version B still works fine past the crash point.
If nothing else helps and this works 100% confirmed on non-encrypted boards, how do i stop the MCU from doing its work and run non-encrypted mode?