When I got a CoCo 2 to repair (hopefully just video connector torn off), I started to worry everybody was only developing for CoCo 3 because of the RAM upgrades. I'm really happy to see attention to mods like this and S-video!
Thanks for sharing. There are so many more Coco 1 and 2 out there than 3. Also there is still new game development supporting 1 and 2. I see it thriving for years to come. We may need to have replacement ICs on the ready and that is a big reason to create projects like this to help future proof the CoCo. Thanks for the comments!
Very cool! Looks like you had the PCB manufacture solder the SMT components! Interesting, I was wondering about that service and thought it might be cost prohibitive.I caught a replay of CoCoTALK! That's how I found your youtube site. I don’t think it’s asking too much to have a separate audio connection (a person probably wants better speakers than an average HDMI TV anyway) and stick w/ DVI modes to avoid the licensing issue. Very nice project!
The fees for assembly were not too bad. The setup fee is reasonable at something like $7 but then there are monthly coupons to cover that fee. Most of the components I used were extended components, meaning not normally loaded in the PNP machine, so there was a flat fee for each of those types. Since I used ENIG finish on the PCB that increased its price to a little more than the assembly price. The components were the majority of the cost, and even those were competitive with any other source I could have used. Also, thanks for mentioning your thoughts on the audio. Avoiding hdmi licensing is the easier route to go. Thanks for viewing!
I'd be interested in a tour of the FPGA code you needed to write to get this to work - such as the different algorithms to simulate the artifact colours and what your code writing environment is like. Do you have any plans for an S-Video output option for CoCo1/2 that supports simulated artifact colours? That would be my ideal setup, as I'd like to use a CoCo1 with S-Video on my Commodore 1701 monitor without giving up artifact colours. I know that's not digital, but it would still be cool. Thanks for building this amazing project!
I'm contemplating doing a 3 video miniseries on FPGA topics that would include some of the theory of this project but also just help with the general design strategies and tools. The tools can vary so much however, and some people get frustrated with trying to make newer or older versions work. There are plenty of tools with no licensing charges and the big vendors want students (and hobbyists maybe?) to purchase their devices and then promote them into the workplace. Let me think about that S-Video question such as whether there could be an analog add-on board to do it.
Ac, my hat is off to you sir. A truly wonderful thing you're doing here. I wondered about this type of project before as I have a PAL CoCo so most games are monochrome. I never gave it much thought though (even if I had I would have given up on it, what you've been up to is miles beyond my ability) When they are ready for sale you have a customer right here. I assume that it's you who wrote the code for it too? Excellent job in any case, looking forward to seeing more ;)
Many thanks! I am thinking that this board will take the PAL/NTSC out of the equation which is a good thing for sure. I just need to make sure to test with a PAL machine. More to come as I work through the testing!
I wish more FPGAs were available in QFPs... not only can they be soldered with a regular soldering station, but they’re easier to debug without having to have a whole bunch of test points on the board (just probe a pin).
Since I have zero experience with PAL, I'll need to study up. Tell me, what is different in the chipset besides the main oscillator frequency? Is it the same vdg? Is the schematic available in the archive?
@@acs8-bitzone651 I searched high and low for a PAL coco1 schematic and came up empty handed. The PAL coco2 schematic is on Coco archives but as expected it is very different from the coco1. Most of the chipset is the same as the NTSC, still uses the same VDG. The main difference is the VDG luma+sync output goes through some extra logic before hitting the MC1372 to insert the extra scanlines for PAL systems (it seems). I know for sure that the colour difference signals go straight from the VDG to the 1372. So in theory the same signals arrive at the VDG in both systems, it's just what happens to them at the output that differs
@@TheRetroChannel Okay, we will keep digging into this, but it would seem that this device would also work for PAL. There may be some tweaks to account for the number of hsync and fsync and the sampling of the DRAM Display data, and we just need to determine how I could test a PAL machine.
@@acs8-bitzone651 No problem, let me know if you need a beta tester. I have an Altera programmer and don't mind doing some SMD soldering, but in terms of coding stuff I have no idea 😄
Hi @@acs8-bitzone651 ! It would be nice indeed that it worked with PAL machines. I think you can check the Dragon computer schematics for info on what's being done to convert the signal to PAL. The chip is the same 6847. Also, if your card works on Dragon machines (or other 6847-based machines), it'll be a huge plus! Keep up the good work!
I have a coco 3 too, but I think this board will help promote the coco 1 and coco 2 which are still thriving in the retro space. I actually use them more than my coco 3 recently. Those coco 3's on Ebay are really going for a premium these days.
CocoDV kits are available now. See my channel "About" screen and click on the "view my email address". Send me an email and I'll reply with details and ordering info. Thanks!
Hi, love your content. i need help with something. I think its probly easy but new to me. i have a coco2 64k. im using drivewire to play games on the coco. i have come across a fd500 drive. i am trying to save the .bin files to the floppy but i dont know the proper commands to save it. any help would be great thanks. i know how to turn off the drive in drivewire so i can access the floppy. thanks
You may have already figured this out, but just in case not, check out my video on that topic called "Transferring files between TRS-80 Color Computer and modern PCs with DriveWire". That was using DW3. If you are using DW4, the following may get you going. Start with a formatted floppy in the drive. Like you mentioned, the DRIVE OFF command on the Coco will provide physical access to drives 0 - 3, leaving 4 and higher for Drivewire. If the disk needs formatting, type a DSKINI 0 from the Coco. Load the .dsk image with the files in DW4 in drive 4 or higher. Make sure HDBDOS translation is checked (it's in the DW4 Tools menu). On the Coco, type BACKUP 4 to 0. It's that easy.
Hi, I'll be building the first batch as soon as possible. The only delay is in finding the FPGA. The global IC shortage began just as I was creating CoCoDV. I am hopeful that ICs can recover in a few months.
Cool! Let us know when it will available!
Thanks! Will do!
Cool project! Would love to see one available for the Coco 3 as well.
Great suggestion!
When I got a CoCo 2 to repair (hopefully just video connector torn off), I started to worry everybody was only developing for CoCo 3 because of the RAM upgrades. I'm really happy to see attention to mods like this and S-video!
Thanks for sharing. There are so many more Coco 1 and 2 out there than 3. Also there is still new game development supporting 1 and 2. I see it thriving for years to come. We may need to have replacement ICs on the ready and that is a big reason to create projects like this to help future proof the CoCo. Thanks for the comments!
Amazing! I can't wait to see it connected to an HDMI monitor!
I should have a video out soon with that. Thanks for your comments!
Very cool! Looks like you had the PCB manufacture solder the SMT components! Interesting, I was wondering about that service and thought it might be cost prohibitive.I caught a replay of CoCoTALK! That's how I found your youtube site. I don’t think it’s asking too much to have a separate audio connection (a person probably wants better speakers than an average HDMI TV anyway) and stick w/ DVI modes to avoid the licensing issue. Very nice project!
The fees for assembly were not too bad. The setup fee is reasonable at something like $7 but then there are monthly coupons to cover that fee. Most of the components I used were extended components, meaning not normally loaded in the PNP machine, so there was a flat fee for each of those types. Since I used ENIG finish on the PCB that increased its price to a little more than the assembly price. The components were the majority of the cost, and even those were competitive with any other source I could have used. Also, thanks for mentioning your thoughts on the audio. Avoiding hdmi licensing is the easier route to go. Thanks for viewing!
When can we get these? Fantastic work. Love your channel.
I am thinking within the next 2 months. Have patience with me as I'm mainly working this on the weekends. Thanks for the interest in it!
What happened to this channel? You get sick or quit?
I'd be interested in a tour of the FPGA code you needed to write to get this to work - such as the different algorithms to simulate the artifact colours and what your code writing environment is like. Do you have any plans for an S-Video output option for CoCo1/2 that supports simulated artifact colours? That would be my ideal setup, as I'd like to use a CoCo1 with S-Video on my Commodore 1701 monitor without giving up artifact colours. I know that's not digital, but it would still be cool. Thanks for building this amazing project!
I'm contemplating doing a 3 video miniseries on FPGA topics that would include some of the theory of this project but also just help with the general design strategies and tools. The tools can vary so much however, and some people get frustrated with trying to make newer or older versions work. There are plenty of tools with no licensing charges and the big vendors want students (and hobbyists maybe?) to purchase their devices and then promote them into the workplace. Let me think about that S-Video question such as whether there could be an analog add-on board to do it.
@@acs8-bitzone651 Awesome! I would love that miniseries on FPGA, especially with focus on this project.
Take my moneeeeyyyy!!!
Thanks for the comments!
Ac, my hat is off to you sir. A truly wonderful thing you're doing here. I wondered about this type of project before as I have a PAL CoCo so most games are monochrome. I never gave it much thought though (even if I had I would have given up on it, what you've been up to is miles beyond my ability) When they are ready for sale you have a customer right here. I assume that it's you who wrote the code for it too? Excellent job in any case, looking forward to seeing more ;)
Many thanks! I am thinking that this board will take the PAL/NTSC out of the equation which is a good thing for sure. I just need to make sure to test with a PAL machine. More to come as I work through the testing!
I wish more FPGAs were available in QFPs... not only can they be soldered with a regular soldering station, but they’re easier to debug without having to have a whole bunch of test points on the board (just probe a pin).
True. I have been doing a lot of debugging with an internal logic analyzer.
Amazing work AC, I don't suppose you know if it can be adapted to work with PAL machines?
Since I have zero experience with PAL, I'll need to study up. Tell me, what is different in the chipset besides the main oscillator frequency? Is it the same vdg? Is the schematic available in the archive?
@@acs8-bitzone651 I searched high and low for a PAL coco1 schematic and came up empty handed. The PAL coco2 schematic is on Coco archives but as expected it is very different from the coco1.
Most of the chipset is the same as the NTSC, still uses the same VDG. The main difference is the VDG luma+sync output goes through some extra logic before hitting the MC1372 to insert the extra scanlines for PAL systems (it seems). I know for sure that the colour difference signals go straight from the VDG to the 1372. So in theory the same signals arrive at the VDG in both systems, it's just what happens to them at the output that differs
@@TheRetroChannel Okay, we will keep digging into this, but it would seem that this device would also work for PAL. There may be some tweaks to account for the number of hsync and fsync and the sampling of the DRAM Display data, and we just need to determine how I could test a PAL machine.
@@acs8-bitzone651 No problem, let me know if you need a beta tester. I have an Altera programmer and don't mind doing some SMD soldering, but in terms of coding stuff I have no idea 😄
Hi @@acs8-bitzone651 ! It would be nice indeed that it worked with PAL machines. I think you can check the Dragon computer schematics for info on what's being done to convert the signal to PAL. The chip is the same 6847. Also, if your card works on Dragon machines (or other 6847-based machines), it'll be a huge plus! Keep up the good work!
When will they be available? I would like one for my coco1. Thanks
Keep on the lookout. I should have some updates in about a month. Thanks for your interest.
Love to have a coco 3
I have a coco 3 too, but I think this board will help promote the coco 1 and coco 2 which are still thriving in the retro space. I actually use them more than my coco 3 recently. Those coco 3's on Ebay are really going for a premium these days.
Will it support a subset of the VESA resolutions and aspect ratios?
VGA 640x480 is supported. This is one of the required resolutions in the DVI and HDMI standards as I understand it.
Any chance of Getting a diagram on converting the PC Jr joystick to coco?
Yes, see the article by Rick Ulland here :. www.glensideccc.com/wp-content/uploads/2020/11/coco12340_1.pdf
Super interested in this. Can we purchase somewhere?
CocoDV kits are available now. See my channel "About" screen and click on the "view my email address". Send me an email and I'll reply with details and ordering info. Thanks!
Hi, love your content. i need help with something. I think its probly easy but new to me. i have a coco2 64k. im using drivewire to play games on the coco. i have come across a fd500 drive. i am trying to save the .bin files to the floppy but i dont know the proper commands to save it. any help would be great thanks. i know how to turn off the drive in drivewire so i can access the floppy. thanks
You may have already figured this out, but just in case not, check out my video on that topic called "Transferring files between TRS-80 Color Computer and modern PCs with DriveWire". That was using DW3. If you are using DW4, the following may get you going. Start with a formatted floppy in the drive. Like you mentioned, the DRIVE OFF command on the Coco will provide physical access to drives 0 - 3, leaving 4 and higher for Drivewire. If the disk needs formatting, type a DSKINI 0 from the Coco. Load the .dsk image with the files in DW4 in drive 4 or higher. Make sure HDBDOS translation is checked (it's in the DW4 Tools menu). On the Coco, type BACKUP 4 to 0. It's that easy.
Hello, where can I purchase this? Thanks.
Hi, I'll be building the first batch as soon as possible. The only delay is in finding the FPGA. The global IC shortage began just as I was creating CoCoDV. I am hopeful that ICs can recover in a few months.
Did you ever finish this?
Yes it is finished as far as the backward compatibility. I am continuing to work on some enhanced features.