thanks for this information, I'll check the 8296 documentation for the standard 64k extension I found a solution I can monitor the write in $FFF0 and stop the capture cog when the screen memory is not mapped.... this is the result: https://s26.postimg.org/ox56xyq2h/IMG_0595.jpg and the 8032 board with the vga card https://s26.postimg.org/773icx4rt/IMG_0596.jpg I'll also have to delay the reset of the 6502 to be sure that it is starting only when the propeller is ready Le 18/02/2018 à 22:49, Mia Magnusson a écrit : > Den Sun, 18 Feb 2018 22:11:53 +0100 skrev didier derny > <didier@aida.org>: >> Is there many extension above the area $8000-$8FFF and / or >> $E800-$E8FF ? there is the 64k ram extension >> is there any other board ? superpet ? madison zram ? >> >> I made a vga board for the commodore 8000... >> this board works fine with the base 8032 board >> for the 64k extension I'll add it directly on the vga board >> >> I'm trying to list what could make the vga board fail >> the board works by capturing the write in the screen memory >> it also capture the write in the io area to reconfigure the output in >> case of video configuration change... >> >> one solution is perhaps to add 2 wire for the cs screen ram / io area >> (for example I don't want to capture a write in $8000 but in the 64 >> extension) > IIRC you can with some jumpers use signals from the user port to map in > the last 32k of the 128k in an 8296 in some places above $8000. (Part > of that 32k space is always used as video ram). > > I'd suggest reading the 8296 manual/supplement and check the > schematics. There are two versions of the schematics, the old from > funet is almost unreadable, while this version is good: > http://6502.org/users/sjgray/temp/CBM8296_ServiceManual_DinA4_alle.pdf > Message was sent through the cbm-hackers mailing listReceived on 2018-02-19 14:00:03
Archive generated by hypermail 2.2.0.
