AndersNielsen wrote:
floobydust wrote:
First, glad you managed to find the issue and work around it by using some of Grant's code.
As the CMOS version of the 6502 came out in the early 80's, I moved over to it immediately. I still have my original pair of Rockwell R65C02P2 (2MHz) CPUs... and the original accompanying (printed) datasheet. From this moment on, I always took advantage of the additional instructions and addressing modes and never looked back.
As only the CMOS version(s) exist (as new), the only chance of running into the older NMOS parts is acquiring and running older retro machines. As I'm designing and building everything from scratch, I default to the WDC processor and the enhanced instruction set.
I guess you could call WDC Tools proprietary, but it is pretty much the de-facto standard for the 6502, 65C02 and 65C816 processors, being from the same company that designed and still manufactures the CPUs. Of course, there are dozens of others out there as well, so you get to take your pick of the lot, or even write your own. I use WDC Tools for all of my own code and also migrate certain other source code to it when I need to, like Enhanced Basic.
I am using CC65/CA65 on Linux (under VMware Fusion) for compiling Fuzix, but that's a very different source tree which I just use as is for the most part.
Best of luck with your continued work on your SBC... nice bit of kit overall.
I didn’t know Chuck Peddle ever worked for WDC?
A lot happened from 1975 to 1983 and the C02 is superior in almost every way, but if you go for a universal design you have to take the millions of 6502s out there into consideration. There are more of them available on the market than will ever be new WDC65C02S’s
My project is all about making it easy to use the IC’s you already have - or can easily get - without buying new.
I’m sure the people who actually need new IC’s with warranty will appreciate them not being gulped up by hobbyists
Also considering the active development and thousands of users I’d say cc65 is closer to a “defacto standard” in this century. I haven’t tried WDC-tools - maybe they’re better in some way.
Thank you so much for the help and support floobydust!
Needless to say, Chuck Peddle did not work for WDC. Then again, the core team were at Motorola, then left to form MOS, which Commodore bought and eventually ended up with Bill Mensch at WDC. Not sure if you've seen the site that Terry Holdt's daughter put together, but it's an interesting read:
https://www.team6502.org/ As far as dev tools go, most have pluses and minuses, you simply pick your poison and move forward. Most folks here have their preferences and some actually opted to write their own instead. When I got back into the 65xx back in 2013, I decided to get a license for WDC Tools (before I found 6502.org) and it's been a good investment for $50. It has some bugs as well, which I've found two over the years, but have also come up with workarounds. TIDE is not very good, to the point where WDC removed it in the free version. Oddly, I still use it for most of my projects, as I've managed to work around those shortcomings as well.
Using old chips is fine... I've got boxes of them, but haven't used them in new projects for various reasons. My current 65xx projects use the W65C02 and that's it from the 65xx chip family. We're just building 65xx projects from opposite sides... all good.
Continuing having fun with your projects, all the best!