Re: SuperPET 6702 IC

is there somewhere a verilog or vhdl file to reproduce the 6702 in a cpld ?

Le 10/22/2022 à 5:57 PM, David Roberts a écrit :
> I have posted my 6702 reverse engineering work (for those who are 
> interested) at 
> https://drive.google.com/drive/folders/1zSlATKktnqrmED8qstq9JTWhHr_ceEsV?usp=sharing. 
>
>
> I completed this work back in 2013 (ish).
>
> Dave
>
> On Sat, 22 Oct 2022 at 16:27, Frank Wolf <webmaster_at_frank-wolf.org> wrote:
>
>     You might want to take a look here:
>
>     http://forum.6502.org/viewtopic.php?f=4&t=6674
>     <http://forum.6502.org/viewtopic.php?f=4&t=6674>
>     https://www.forum64.de/index.php?thread/116391-mos6702-superpet-dongle-dissected/&postID=1695189
>     <https://www.forum64.de/index.php?thread/116391-mos6702-superpet-dongle-dissected/&postID=1695189>
>
>
>
>     On 22.10.2022 16:30, ruud_at_baltissen.org wrote:
>     > Hallo allemaal,
>     >
>     >
>     > I once had a SuperPET but sold it. Main reason: I want to tinker
>     with
>     > computers I have and tinkering with a perfect SuperPET is not done
>     > IMHO. The idea was to create my own upgrade to turn a 8032, 8096 or
>     > 8296 into a SuperPET anyway. To avoid inventing the wheel twice
>     I did
>     > some research lately and found two old projects:
>     >
>     https://forum.vcfed.org/index.php?threads/commodore-8032-add-on-board-superpet.49423/page-4
>
>     >
>     > https://github.com/nils-eilers/uMMF
>     >
>     > I was able to contact Dave, the owner of the first project and he
>     > pointed me to the 6702. I completely forgot about that one. To
>     make it
>     > short: what is known about it now? Bo Zimmerman's site still says
>     > nothing is known and I found a PDF that mentions patching the
>     various
>     > Waterloo disks.
>     >
>     > But I wonder: hasn't anybody tried a brute force attack yet? And
>     you
>     > don't have to start from zero; Mike Naberezny wrote the document I
>     > mentioned above so the routines that approach the 6702 are known,
>     > including input and output: Waterloo-D64-Disk-Patches.pdf
>     >
>     https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwjRo4ThgfT6AhVMPewKHaO6BfMQFnoECEUQAQ&url=http%3A%2F%2Fmikenaberezny.com%2Fwp-content%2Fuploads%2F2012%2F04%2FWaterloo-D64-Disk-Patches.pdf&usg=AOvVaw0r69W200tHnCnujugkTap9
>     <https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwjRo4ThgfT6AhVMPewKHaO6BfMQFnoECEUQAQ&url=http%3A%2F%2Fmikenaberezny.com%2Fwp-content%2Fuploads%2F2012%2F04%2FWaterloo-D64-Disk-Patches.pdf&usg=AOvVaw0r69W200tHnCnujugkTap9>
>
>     >
>     >
>     > If I create a board, I won't use the same, IMHO stupid, idea of
>     > powering the 6502 off so the 6809 can access the bus. I'm using a
>     > 65816 anyway and it can be tri-stated, so why not making use of it?
>     > Another advantage (I think), the 6502/65816 can continue after the
>     > instruction it gave to activate the 6809.
>     >
>     > Any comment, ideas, etc is welcome!
>     >
>     >
>
>