Closed furrtek closed 4 years ago
Thanks a lot for the patch. I have not applied it directly because I think all the control registers should be affected by the !part condition. Please have a look at this commit I made based on your patch.
Confirming that it works just as well :)
Great! I still have to check I didn’t break anything on the Megadrive but I think it should be ok.
Notice that I have left the separated output signals. If you don’t need them you can leave them unconnected in the instance. If you call the name but leave empty the assignment in the brackets you won’t get any warning. Like this
Jt10 myjt10( .unused( ), // other stuff );
El El lun, 10 jun 2019 a las 10:08, Furrtek notifications@github.com escribió:
Confirming that it works just as well :)
— You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/jotego/jt12/pull/37?email_source=notifications&email_token=AAOG27C4Y3A44IANDG64IODPZYDXTA5CNFSM4HWPSLS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXJG5WQ#issuecomment-500330202, or mute the thread https://github.com/notifications/unsubscribe-auth/AAOG27AUO5AZ2ZZ5RTXXXGDPZYDXTANCNFSM4HWPSLSQ .
Could you leave the separated output pins in jt12_top intact? They are used in other instantiations. For instance, they are used in the ZX Spectrum core of MiSTer (for recreating a real-life add-on with two YM2203) for instance.
I think the rest of the corrections are fine. If you reverse jt12_top I can do the merge.
Didn't meant to update the file here, sorry. I'm still confused about some things with git, I'll restore jt12_top to your version with the separated outputs.
We left this thread open. Closing it!
Some registers didn't have part checks for writes, this was messing up the timer A (part 0) and some ADPCM-B (part 1) register values.
Also, IRQ enables for timers were swapped in jt12_top.