Those of you following this blog early on may have noticed that I abandoned the Atari XEGS system as a platform for the Liber809 due to an issue that I was having with getting the system working in All-RAM mode. My initial suspicion was that there was some subtle timing issue with the Liber809 board that caused it to fail in the XEGS. Any write to $BXXX would cause what I *thought* was a write to $DXXX.
In actuality, writes to $BXXX were going to $FXXX and blowing away the bitmap font and display list that were setup there. I confirmed this, then asked the folks on atariage.com for some assistance. After looking at the schematic, it became apparent that either the two 4464 DRAMs or the FREDDIE chip were at fault.
I spent some time this evening desoldering and socketing the two 4464s, then replaced them with known working extras that I had. After hooking everything up, the problem still persisted. Any attempt to write to $BXXX was actually going to $FXXX. That left the FREDDIE as the possible culprit. All address lines go into that chip, and it's responsible for reading/writing/refreshing the DRAMs. It seemed like the next logical step.
Since I don't have spare chips around, I turned to my trusty 130XE which had its FREDDIE soldered onto the board. I carefully desoldered the chip and removed it gently, then inserted it into the already socketed FREDDIE location on the XEGS and started it up... SUCCESS! The XEGS did not have any problems booting with the Liber809 ROM and 6809 processor. NitrOS-9 came right up and I was able to interact just fine.
So it appears the FREDDIE that was in the XEGS was "sticking" A14 somehow. Now to find a replacement FREDDIE.
On another note, my 130XE keyboard mylar was failing. Keys were simply not working. I found a supplier of replacement mylar keyboards, http://www.best-electronics-ca.com, and sent an email. They were very prompt in responding, and I even picked up replacement key cups for both the 130E and XEGS keyboards, which eliminate the "spongy" feel. I ordered on a Friday and the parts were here on Monday. I then installed the keyboard mylar and key cups, and boy did it make a difference! Check these guys out. They are EXCELLENT Atari product suppliers!
A blog about my exploits in getting the Motorola 6809 microprocessor mated to the Atari XEGS (and beyond).
Tuesday, August 7, 2012
Thursday, May 24, 2012
Liber809 at the CoCoFest
This past weekend I attended the 21st Annual Chicago CoCoFest and brought over the Atari 130XE as well as a passel of assemble Liber809 boards. Interest in the project was high even though attendance was obviously geared toward the Color Computer.
On Saturday afternoon I gave a presentation on the development of the board and the software. There were good questions asked, and everyone seemed pleased.
Currently, we have plans to attend both VCF Southwest and the VCF Midwest this year. Our hope is to have the Liber809 board expanded to other 8-bitters by that point. Stay tuned.
On Saturday afternoon I gave a presentation on the development of the board and the software. There were good questions asked, and everyone seemed pleased.
Currently, we have plans to attend both VCF Southwest and the VCF Midwest this year. Our hope is to have the Liber809 board expanded to other 8-bitters by that point. Stay tuned.
Sunday, May 6, 2012
Up and Ready for Sale
Today I updated the Cloud-9 website at www.cloud9tech.com to reflect the fact that the Liber809 is now shipping.
Several folks have asked what is required to really make use of the Liber809. A SIO2PC device, which mates the Atari SIO port to a PC via a USB cable, is required to do any loading of applications into the Atari itself. SIO2PC devices are available at various places on the Internet.
Several folks have asked what is required to really make use of the Liber809. A SIO2PC device, which mates the Atari SIO port to a PC via a USB cable, is required to do any loading of applications into the Atari itself. SIO2PC devices are available at various places on the Internet.
Monday, April 30, 2012
And Another One Down...
This evening I verified that the Atari 130XE works great with the Liber809 board (thanks to Mike Rowen for graciously donating the system to me for testing). Since the latest incarnation of the Liber809 is so compact, I was able to put the Atari 130XE together, case, screws and all. Makes it look all natural!
You can see how it looks, and even watch it boot NitrOS-9 from DriveWire on this YouTube video.
You can see how it looks, and even watch it boot NitrOS-9 from DriveWire on this YouTube video.
Almost Ready...
The last 5 days or so have been spent putting together the board and testing. Three trace cuts and three added wires later, the board is coming up on the Atari 800XL here on the bench. The trace cuts and wires were needed to work around omissions in the latest board run (our fault, not the PCB manufacturer's).
Because of this extra post assembly work, I've decided against selling kits and will instead sell entire boards already put together. This allows some quality control and assures me that what I'm sending out actually works.
There's still an issue with the board working the Atari XEGS, so we're trying to pin down the proper equations to deal with the timing issues surrounding that system. Once that's in place, the boards will start going out the door.
Because of this extra post assembly work, I've decided against selling kits and will instead sell entire boards already put together. This allows some quality control and assures me that what I'm sending out actually works.
There's still an issue with the board working the Atari XEGS, so we're trying to pin down the proper equations to deal with the timing issues surrounding that system. Once that's in place, the boards will start going out the door.
Thursday, April 26, 2012
They're Here....
The boards arrived this morning via FedEx and they look great. I'm still waiting on another order of parts to arrive before I begin to assemble and test the board. That should happen early next week. Assuming all goes well, we'll start making kits available shortly thereafter.
Thursday, April 19, 2012
Coming Together
The absence of a post over the last couple of weeks shouldn't be an indication that nothing is going on.
On the contrary, things are on the move. A few days ago, we sent final artwork over to the PCB manufacturer and should be getting boards next week. Parts have been ordered and I will be assembling a number of boards. The preferred method of selling the Liber809, however, will be in kit form.
The product will be sold through www.cloud9tech.com. A final price hasn't been set yet, but that should be set soon. In the mean time, anyone interested in one of these boards, either in kit or in assembled form, can email me to be put on the list.
On the contrary, things are on the move. A few days ago, we sent final artwork over to the PCB manufacturer and should be getting boards next week. Parts have been ordered and I will be assembling a number of boards. The preferred method of selling the Liber809, however, will be in kit form.
The product will be sold through www.cloud9tech.com. A final price hasn't been set yet, but that should be set soon. In the mean time, anyone interested in one of these boards, either in kit or in assembled form, can email me to be put on the list.
Monday, April 2, 2012
Progress On The Software Side
This evening I spent some time reworking the NitrOS-9 port. The change in the Liber809 boot ROM made it necessary to do some modifications to the kernel to accommodate the new loading style. But now all is good and we're booting NitrOS-9 Level 1 on the Atari 800XL.
Which brings me to Slor's excellent demo. Fuji started life out as a blob of code loaded from the ROM load routines via DriveWire. It was later modified to be position independent, but still had absolute references and self modifying code, neither of which are welcome in an OS-9 environment.
I spent some time with Slor tonight, reworking Fuji to actually run as an OS-9 executable. It's not quite the good NitrOS-9 citizen that it should be, but with a bit more work, we will be able to run it from the shell, then quit it at our leisure and return back to the OS.
Finally, I'll be doing a KeyNote presentation on the project at the upcoming CoCoFest (http://www.glensideccc.com). I plan on making this a very thorough and detailed presentation and will post the notes when I'm done.
Friday, March 30, 2012
Back in the Saddle
As I mentioned in a previous post, work and other tasks have pretty much sidelined the Liber809 project. However, I'm spending some time this weekend to rework the NitrOS-9 port based on several pieces of good news:
- The Liber809 board had stopped working for some inexplicable reason. As it turns out, a piece of solder flake had found its way onto the trace from the Maxim DS1100 that leads to the Q clock on the 6809, leaving it perpetually grounded. Needless to say, I'm going with solder masked boards from now on.
- The XEGS had timing issues with the firmware going into all-RAM mode. The ANTIC was picking up writes to addresses outside of its range of $D000-$D7FF. We have theories on this subtle timing problem, but reports from others that the 800XL and 1200XL worked fine in all-RAM mode has us thinking this is something unique to the XEGS.
Sloopy, a member of the AtariAge forums, sent over an Atari 800XL which I readily disassembled. After some mucking around, the Liber809 board came up, and indeed worked well, even in all-RAM mode. Slor's excellent Liber809 demo in the previous post came up just fine, sound and all.
With a solid, reliable Atari system running the Liber809 board, I can now focus on bringing up NitrOS-9 through DriveWire, which is how I envision the majority of folks will want to use the operating system. So I've carved out some time this weekend to do just that.
Wednesday, March 28, 2012
Demo Time
Slor sent over a link to a YouTube video which shows an impressive demo of the Liber809 in his Atari 1200XL. Check it out here.
Thanks Slor! Great job!
In other news, work has had me sidelined for a while on the project, but we are still working on the next revision of the board. More news as it comes.
Thanks Slor! Great job!
In other news, work has had me sidelined for a while on the project, but we are still working on the next revision of the board. More news as it comes.
Tuesday, March 6, 2012
1200XL Success
We've verified that another machine besides the Atari XEGS works with the Liber809. Slor (pseudonym), a guy from the Atari group, purchased one of the Liber809 prototypes and has installed it in his Atari 1200XL. We spent some time last night going over test code with DriveWire 4 Server. Here's a screen shot of it in the 1200XL:
I've got some tidying up to do on the Liber809 ROM for the Atari, but expect to get all of the bugs worked out. We're not sure on the final design of the Liber809 board yet, but Gary's working on it, so we'll have an update soon.
I've got some tidying up to do on the Liber809 ROM for the Atari, but expect to get all of the bugs worked out. We're not sure on the final design of the Liber809 board yet, but Gary's working on it, so we'll have an update soon.
Monday, March 5, 2012
Liber309?
The Motorola 6809 has a cousin. Yes, her name is 6309. Actually the 6309 is a clone of the 6809 and is/was made by Hitachi. For years, CoCo guys were sticking them in their systems to replace the 6809 because the 6309 is made from a CMOS process and runs cooler and takes up less power.
It took a Japanese guy named Hirotsugu Kakugawa to write a post to the comp.sys.m6809 Usenet newsgroup in 1992 entitled "A Memo on the Secret Features of 6309" to open up the potential of this chip to the CoCo world (see this link for the original message). It turns out that the chip that a lot of CoCo users were running for years had extra registers, 16 bit multiply and 16/32 bit hardware divide instructions, plus other cool bit manipulation and block copy instructions. Not only that, but the chip could be put into a mode that would shave 1 cycle off of many instructions.
Soon, intrepid developers began writing software to take advantage of the new-found power of the 6309, including updating Microware's OS-9 operating system (where NitrOS-9 got its name). Performance was improved greatly and it set new speed records for the CoCo.
You would expect that the 6309 would also work in the Liber809, and that was the plan, but for a few weeks now, I was aware of a problem. The 6309 wouldn't work in the Liber809 board, neither the Frankenproto wire beast that I handmade, nor the prototypes that came in last week. The 6809 ran fine, but the 6309 would just lock up the machine.
It turns out that gate delays caused a glitch in the E and Q clocks. Gary noted this in one of the logic analyzer shots I sent over to him, and surmised that switching two pins on the 7400 would cause the signal to arrive two gate delays earlier and eliminate the clock spike. Today for lunch I quickly rewired the prototype and tried the 6309, and sure enough it came up. So now the Liber809 also works with the 6309.
Speaking of prototypes, both have been sold and are getting into the hands of their new owners as we speak. Some additional testing on their end will solidify things and we'll soon move to a larger run of boards that are optimized for both part count and space.
It took a Japanese guy named Hirotsugu Kakugawa to write a post to the comp.sys.m6809 Usenet newsgroup in 1992 entitled "A Memo on the Secret Features of 6309" to open up the potential of this chip to the CoCo world (see this link for the original message). It turns out that the chip that a lot of CoCo users were running for years had extra registers, 16 bit multiply and 16/32 bit hardware divide instructions, plus other cool bit manipulation and block copy instructions. Not only that, but the chip could be put into a mode that would shave 1 cycle off of many instructions.
Soon, intrepid developers began writing software to take advantage of the new-found power of the 6309, including updating Microware's OS-9 operating system (where NitrOS-9 got its name). Performance was improved greatly and it set new speed records for the CoCo.
You would expect that the 6309 would also work in the Liber809, and that was the plan, but for a few weeks now, I was aware of a problem. The 6309 wouldn't work in the Liber809 board, neither the Frankenproto wire beast that I handmade, nor the prototypes that came in last week. The 6809 ran fine, but the 6309 would just lock up the machine.
It turns out that gate delays caused a glitch in the E and Q clocks. Gary noted this in one of the logic analyzer shots I sent over to him, and surmised that switching two pins on the 7400 would cause the signal to arrive two gate delays earlier and eliminate the clock spike. Today for lunch I quickly rewired the prototype and tried the 6309, and sure enough it came up. So now the Liber809 also works with the 6309.
Speaking of prototypes, both have been sold and are getting into the hands of their new owners as we speak. Some additional testing on their end will solidify things and we'll soon move to a larger run of boards that are optimized for both part count and space.
Thursday, March 1, 2012
Dual CPU Mission Accomplished
Today I received the rest of the parts in the mail to finish assembling the prototype boards. Since I only had lunch time to do some work on the project, I quickly got down to soldering. After carefully checking my work for proper continuity with an Ohm meter, I placed the chips in, set the jumpers and voila! The Liber809 board came up!
I turned off the Atari XEGS, programmed the ROM emulator with the contents of the original Atari 32K ROM, then set the two jumpers into the alternate position. When I powered the Atari up, the familiar READY prompt came up into Atari BASIC.
Now that we have a solid board running, the plan is for more testing and retesting to make sure everything is super stable.
As you can see in the pictures below, the board is a little long due to the specific size requirements that were placed on us by the prototype manufacturer. The final board will be optimized, and we also expect to drop the number of support chips down as well.
As I have time, I'll assemble the other two prototypes then get them off to their respective buyers.
I turned off the Atari XEGS, programmed the ROM emulator with the contents of the original Atari 32K ROM, then set the two jumpers into the alternate position. When I powered the Atari up, the familiar READY prompt came up into Atari BASIC.
Now that we have a solid board running, the plan is for more testing and retesting to make sure everything is super stable.
As you can see in the pictures below, the board is a little long due to the specific size requirements that were placed on us by the prototype manufacturer. The final board will be optimized, and we also expect to drop the number of support chips down as well.
As I have time, I'll assemble the other two prototypes then get them off to their respective buyers.
Wednesday, February 29, 2012
Prototypes And 57.6Kbps!
The three prototypes came in today, and I spent some time this evening starting the assembly process. Not all parts are in yet, but they are on their way. So far I have the capacitors and resistors I need, plus several of the Maxim DS-1100Z+175 chips. Soldering these little buggers on the board isn't easy!
Add to the fact that most of the board is an unmasked ground plane (for electrical stability) so I have to be extra careful in my soldering not to create any shorts. As the parts trickle in the next couple of days, I should be able to move away from the Frankenstein wire beast that I'm currently using (but which is now remarkably stable since I carefully went over it). The other two boards are spoken for, and I'll build them as well.
Another bit of news... I'm now running the SIO on the Atari XEGS at 57.6Kbps and tweaked the FTDI chip in the adapter to minimize its transmit delay so we can squeeze every bit of performance out of the thing. It's holding up quite well, except for a few glitches that I hope to nail as I solidify the boot ROM and get a stable prototype in place.
Add to the fact that most of the board is an unmasked ground plane (for electrical stability) so I have to be extra careful in my soldering not to create any shorts. As the parts trickle in the next couple of days, I should be able to move away from the Frankenstein wire beast that I'm currently using (but which is now remarkably stable since I carefully went over it). The other two boards are spoken for, and I'll build them as well.
Another bit of news... I'm now running the SIO on the Atari XEGS at 57.6Kbps and tweaked the FTDI chip in the adapter to minimize its transmit delay so we can squeeze every bit of performance out of the thing. It's holding up quite well, except for a few glitches that I hope to nail as I solidify the boot ROM and get a stable prototype in place.
Tuesday, February 28, 2012
SIO, You're A Tricky Devil...
I had a little bit of time over the weekend to buffet up the SIO routines. While they still aren't giving 100% error-free transmission in all cases, they're a lot better than my first cut. I used the 6502 code that this guy wrote (http://www.horus.com/~hias/atari/) as a guide to the 6809 version, which has proven pretty stable at 38,400bps.
So with that in place, I can now boot into DriveWire and access disk services.
The next thing to tackle is a more stable booting environment. Currently my boot ROM is just a hacked together lump of code, but I'm planning on bringing Brett Gordon's Forth-based CoCoBoot into the picture soon.
Boards should be here mid-week, and other parts are trickling in day by day from UPS and the post office. Hopefully this weekend I'll have some time to put together a board.
So with that in place, I can now boot into DriveWire and access disk services.
The next thing to tackle is a more stable booting environment. Currently my boot ROM is just a hacked together lump of code, but I'm planning on bringing Brett Gordon's Forth-based CoCoBoot into the picture soon.
Boards should be here mid-week, and other parts are trickling in day by day from UPS and the post office. Hopefully this weekend I'll have some time to put together a board.
Saturday, February 25, 2012
PIA = Pain In the Ass
I swear, it's the little things that trip you up. I fought two battles today with the continuing effort to get the NitrOS-9 port more smoothly working with the Atari XEGS. The first was getting the SIO port to work reliably. The second was getting the Atari into all-RAM mode. Both were necessary to bring the project forward.
Some background: booting NitrOS-9 from ROM is fine for development, but to make Liber809 convenient as a product, people don't want to burn ROMs every time they want to reconfigure the OS (not everybody has a ROM burner). The ideal situation is to have a bootstrap ROM installed in the ROM socket of the Atari. The code in that bootstrap ROM would pull in additional code from some external source (like a disk drive). The ROM code wouldn't change, and the malleable code on the disk would be easy to update, etc.
Well, the obvious solution these days is a Mac, Linux or PC based server that acts as a virtual disk server... like DriveWire. It turns out that the Atari guys have their own SIO protocol and server-side software, but since I waned to turn out something quick, and being more familiar with DriveWire, I decided to start with that.
So the first battle was to understand and tame the SIO. POKEY, which is one of the chips on the Atari, handles serial communications and has an internal shift register so all the software needs to do is write a byte and read a byte, etc. But it's a little tricky, and I learned that. It was an exercise in frustration trying to get reliable communication to the DriveWire 4 server at 38,400 bps, but after studying some example 6502 code and doing some experimentation, I finally got something that worked. So now my boot ROM is happily pulling sectors off of DriveWire server. Sloopy (a guy on the Atari forums) was kind enough to drop an SIO to USB adapter in the mail to me, which was critical in getting this to work. Thanks Sloopy (not Sloppy!)
Now for the second battle. A critical component in getting the OS loaded is to tell ROM to get the hell out of the way at the right time. This is called "all-RAM" mode, and the Atari is capable of doing it. However, for the life of me I could not get it to work. I tickled bits, tried standing on my head, etc. But nothing worked. The helpful guys on the Atari forums gave me some hints and clues, and while working through everything, we came to the realization that the PIA needed to be initialized. After more experimentation, I was finally able to get all-RAM mode working, albeit with a different value than what the documentation expects to be placed into the PIA's port register. That's another battle for another time....
So the bottom line is that NitrOS-9 on the Atari XEGS is now booting from the DriveWire 4 server running on the Mac. This is *BIG* because it gives users an easy way to introduce code into the system. It also further proves out that the Liber809 design is continuing to perform well.
Friday, February 24, 2012
All Night Long
Frustrated with the finickiness of the spaghetti prototype, I spent some time last evening buzzing out and resoldering wires on the prototype board. I found a few questionable places that could have been contributing to the problem and tightened up connections.
Another cause of the possible flakiness: the 68B09E that I'm using in the machine socket was desoldered from a CoCo 3 years ago. The pins are noticeably shorter and the contacts they make into the machine socket holes in some places are questionable. I flared out the pins slightly so that they would make a better contact in the holes and seated the microprocessor more firmly.
After that, I placed the prototype back in the 6502C socket on the Atari XEGS and things seemed more stable. I loaded a bootfile into ROM, booted NitrOS-9 and left the debug command running all night long.
This morning I arrived in the office to find that the prompt was still showing, the video was still sane, and the XEGS was still up and running. So it appears that the rework I did on the prototype cleared up those issues.
Another accomplishment was to finally sort out the clock problems that I was having with NMI. It turns out that it was a simple coding error, and I fixed it right up. Now, clock module is called during the kernel's initialization. The clock sets up a vector, then tells the ANTIC to fire off an NMI every vertical blanking interval (1/60 of a second). The vector routes the NMI to a short handler which then redirects it to the vector that was populated by the clock module. This vector handles the software clock (increments seconds, then minutes, then days, and so on), and also polls the virtual interrupt table, a feature that NitrOS-9 has for devices to use the clock interrupt as a pseudo-interrupt source. So now NMIs are firing 60 times a second and keyboard interrupts are working along with that.
With all of that activity going on and the computer staying up strong for 12 hours running, I would say that things are looking quite well.
Another cause of the possible flakiness: the 68B09E that I'm using in the machine socket was desoldered from a CoCo 3 years ago. The pins are noticeably shorter and the contacts they make into the machine socket holes in some places are questionable. I flared out the pins slightly so that they would make a better contact in the holes and seated the microprocessor more firmly.
After that, I placed the prototype back in the 6502C socket on the Atari XEGS and things seemed more stable. I loaded a bootfile into ROM, booted NitrOS-9 and left the debug command running all night long.
This morning I arrived in the office to find that the prompt was still showing, the video was still sane, and the XEGS was still up and running. So it appears that the rework I did on the prototype cleared up those issues.
Another accomplishment was to finally sort out the clock problems that I was having with NMI. It turns out that it was a simple coding error, and I fixed it right up. Now, clock module is called during the kernel's initialization. The clock sets up a vector, then tells the ANTIC to fire off an NMI every vertical blanking interval (1/60 of a second). The vector routes the NMI to a short handler which then redirects it to the vector that was populated by the clock module. This vector handles the software clock (increments seconds, then minutes, then days, and so on), and also polls the virtual interrupt table, a feature that NitrOS-9 has for devices to use the clock interrupt as a pseudo-interrupt source. So now NMIs are firing 60 times a second and keyboard interrupts are working along with that.
With all of that activity going on and the computer staying up strong for 12 hours running, I would say that things are looking quite well.
Thursday, February 23, 2012
Of Prototypes and Shout Outs
I just got off the phone with Gary, who completed the design of revision 1 of the Liber809 board. Three prototype boards will be ordered and should be in late next week or early the week after. The plan is to populate and test them to further improve the design and work out any remaining issues (there don't appear to be any). I'll keep one around and get the other two into the hands of people who can take the project a bit farther along.
After that, we'll look at a larger run that will be sold in kit form through Cloud-9.
I thought I would dedicate the rest of this blog post to the people and products that made the project a success. Nothing is created in a vacuum, and it was certainly true in this case. So thanks to:
After that, we'll look at a larger run that will be sold in kit form through Cloud-9.
I thought I would dedicate the rest of this blog post to the people and products that made the project a success. Nothing is created in a vacuum, and it was certainly true in this case. So thanks to:
- My wife, for putting up with my being holed up in the shop late into the evenings while I hammered this thing out.
- Gary Becker for his significant contributions to the design of the Liber809, doing the board layout and just generally being available for questions and the like. Without Gary's help it would have taken much, much longer for me to complete this project.
- Mark Marlette and James Daggett for their input during the electrical mating phase of the project.
- The great folks on the AtariAge forums (www.atariage.com/forums) for the help and encouragement., including Rybags (thanks for all of the 6502 test code!) and sloopy (for the SIO2PC adapter and technical guidance on the Atari stuff).
- The CoCo guys on the Malted Media mailing list for championing me forward.
- tschak, dmlloyd, syscall, a8isa1, joey_z and others in the Atari IRC group who helped me decipher the ANTIC and other Atari hardware.
- My trusty iMac (www.apple.com) which powers the cross assemblers and other tools which made the NitrOS-9 port go quick and easy. Gotta love Apple computers.
- Intronix (www.pctestinstruments.com) for their LogicPort analyzer, which made this project SO much easier (and fun!)
- Craig Moates (www.moates.net) for his awesome Ostrich 2.0 ROM emulator which saved me tons of development time.
- The ToolShed software (http://sourceforge.net/projects/toolshed/) and specifically, the mamou 6809 cross-assembler which rocked the house.
- NitrOS-9 (www.nitros9.org) for being such a cool little OS, and to the guys at Microware (Larry, Ken, and Robert) who created OS-9 for the 6809 over 30 years ago...
I hope I didn't miss anybody.
Wednesday, February 22, 2012
Excuse the Interruption
Well, I hit another milestone... the POKEY chip on the Atari XEGS can be setup to send an interrupt when a key is pressed. After spending some time this evening figuring out how to orchestrate that, and getting re-accustomed to NitrOS-9's IRQ polling system call, POKEY is doing its thing and the OS is handling it right along. I can now type commands at the shell prompt and have them execute. Also, notice the scrolling is working as well.
Also, the kernel is now scanning modules from $C000-$CFFF and $D800-$FFFF, skipping the $D000-$D7FF I/O range. It takes a few extra steps to build a ROM image to cope, but usable ROM space for NitrOS-9 is now up to 14K.
What Hath Been Wrought?
Now that the board is working pretty well, I thought it would be a good time to sit back and reflect on exactly what has been accomplished here, as well as looking at what the Liber809 is and what it isn't.
The first thing I want to talk about is the name: Liber809. This came to me some years ago when I was first planning the project. The name is, of course, an amalgamation of the words "liberate" and "6809". The idea was to convey a sense of freedom and liberation... that the 6809 could actually run on something outside of just the CoCo. The choice of name was never meant to imply that systems who can use the 6809 are somehow liberated from the 6502.
Second, some people have used the term "CoCoTari" or similar names to describe the Liber809's success in the Atari XEGS. I want to discourage use of that term, because this project has more to do with the 6809 than the platform that it was popular on. Sure, the CoCo has the 6809 and also has NitrOS-9, but both of these elements existed outside of the CoCo. There were other 6809 systems back in the day that ran OS-9, such as the GIMIX, Smoke Signal, and others. And while the CoCo was certainly the jumping point for me to get this project going, it should in no way be seen as an attempt to meld the two systems together per se.
With all of that said, there were a few goals that I aimed to accomplish with this project:
Pretty much every one of these goals has been met to some degree. But this is just the start. Getting the hardware working and proven is one thing. Now the real challenge is to see if people will take it to the next level with software that takes advantage of this new platform.
The first thing I want to talk about is the name: Liber809. This came to me some years ago when I was first planning the project. The name is, of course, an amalgamation of the words "liberate" and "6809". The idea was to convey a sense of freedom and liberation... that the 6809 could actually run on something outside of just the CoCo. The choice of name was never meant to imply that systems who can use the 6809 are somehow liberated from the 6502.
Second, some people have used the term "CoCoTari" or similar names to describe the Liber809's success in the Atari XEGS. I want to discourage use of that term, because this project has more to do with the 6809 than the platform that it was popular on. Sure, the CoCo has the 6809 and also has NitrOS-9, but both of these elements existed outside of the CoCo. There were other 6809 systems back in the day that ran OS-9, such as the GIMIX, Smoke Signal, and others. And while the CoCo was certainly the jumping point for me to get this project going, it should in no way be seen as an attempt to meld the two systems together per se.
With all of that said, there were a few goals that I aimed to accomplish with this project:
- Get my hardware chops up and learn the hardware of another platform.
- Bring the 6809 to other home computing platforms with first-rate graphics and sound features. The CoCo has always been hobbled with less than ideal sound and graphics. The CoCo 3 did manage to elevate the graphics a bit, but sound still lacked. And yes, we made do with it, and did quite well considering the limitations. However, bringing the powerful 6809 together with equally powerful hardware on the Atari and other platforms is just a dream come true.
- Doing something that others said couldn't be done, or wouldn't be done.
- Bring people from different platform camps together, to mix the pot up, so to speak. For years, each group has had its own cliques and personalities. With all of that talent being segregated, I thought that the Liber809 could be one way to bring some of these folks together for greater collaboration.
- See NitrOS-9 used on other hardware platforms. It's a great little operating system, and the fact that it runs on the CoCo, the Dragon, and now the Atari shows just how versatile it can be.
Pretty much every one of these goals has been met to some degree. But this is just the start. Getting the hardware working and proven is one thing. Now the real challenge is to see if people will take it to the next level with software that takes advantage of this new platform.
Subscribe to:
Posts (Atom)


