Motorola 6809 / Microware OS9 / NitrOS9 Archive

~/gocode/src/github.com/strickyak/doing_os9$ go run bootdisk_to_sbc09_file/bootdisk_to_sbc09_file.go < /home/strick/6809/hg.code.sf.net/nitros9/level1/coco1_yak/nos96809l1coco1_yak_80d.dsk > /tmp/boot-yak

~/gocode/src/github.com/strickyak/sbc09/src$ pp ./v09st -Lff00 -H10000 -0 -i0 -o0 -t -d /tmp/boot-yak -f /home/strick/6809/hg.code.sf.net/nitros9/level1/coco1_yak/nos96809l1coco1_yak_80d.dsk > _

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

[toolshed] hg clone http://hg.code.sf.net/p/toolshed/code toolshed

[toolshed] make -C build/unix INSTALLDIR=$HOME/6809/bin/ install


/subsection Obtain and build LWTOOLS

hg clone http://lwtools.projects.l-w.ca/hg/ lwtools
cd lwtools
make
make install
cd ..
This will build and install lwasm, lwlink, lwar and lwobjdump into your /usr/local/bin directory. If "make install" fails on unsufficient permissions, run "sudo make install".

/subsection Obtain and build the Toolshed tools

hg clone http://hg.code.sf.net/p/toolshed/code toolshed
cd toolshed
make -C build/unix install
cd ..
This will build and install the toolshed tools into your /usr/local/bin directory. Again, use "sudo make -C build/unix install" if needed.

/subsection Obtain and build NitrOS-9

Make sure lwasm is in your path, either by editing your shell startup scripts or by entering PATH=$PATH:/usr/local/bin in your active command shell.

hg clone http://hg.code.sf.net/p/nitros9/code nitros9
cd nitros9

At this point you are ready to rock. To build all of NitrOS9 including things you almost certainly don't want:

make dsk

Alternatively you can first change to the directory containing the system you would like to build, for instance:

export NITROS9DIR=$PWD
cd level2/coco3
make dsk

Or just stay in the top folder and specify a "port" (coco2, coco3, coco3_6309, etc):
make dsk PORTS=coco3

You should now find disk images have been created in the various directories. For instance, the boot disks for level 2, 6309 can be found in the level2/coco3_6309 subdirectory.

 2020  mkdir hg.code.sf.net
 2021  cd hg.code.sf.net
 2022  hg clone http://hg.code.sf.net/p/nitros9/code nitros9
 2023  ls
 2024  cd nitros9/
 2026  PATH=$PATH:$HOME/6809/bin make dsk PORTS=coco3

zip -D -9 -j nos96809l2v030300coco3.zip nos96809l2v030300coco3_40d_1.dsk nos96809l2v030300coco3_40d_1_50hz.dsk nos96809l2v030300coco3_40d_2.dsk nos96809l2v030300coco3_80d.dsk nos96809l2v030300coco3_80d_50hz.dsk nos96809l2v030300coco3_dw.dsk nos96809l2v030300coco3_dw_headless.dsk nos96809l2v030300coco3_becker.dsk nos96809l2v030300coco3_arduino.dsk nos96809l2v030300coco3_becker_headless.dsk nos96809l2v030300coco3_arduino_headless.dsk nos96809l2v030300coco3_cocosdc.dsk ../../ReadMe ../../ChangeLog

 2028  PATH=$PATH:$HOME/6809/bin make dsk PORTS=coco2

zip -D -9 -j nos96809l1v030300coco2.zip nos96809l1v030300coco2_dw.dsk nos96809l1v030300coco2_dw_headless.dsk nos96809l1v030300coco2_becker.dsk nos96809l1v030300coco2_becker_headless.dsk nos96809l1v030300coco2_arduino.dsk nos96809l1v030300coco2_arduino_headless.dsk nos96809l1v030300coco2_40d_1.dsk nos96809l1v030300coco2_40d_2.dsk nos96809l1v030300coco2_80d.dsk nos96809l1v030300coco2_cocosdc.dsk ../../ReadMe ../../ChangeLog

make[2]: Leaving directory `/home/strick/6809/hg.code.sf.net/nitros9/level1/coco2'
make[1]: Leaving directory `/home/strick/6809/hg.code.sf.net/nitros9/level1'


;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
[v09.h]

#define IOPAGE 0xe000

[engine.c]
 124 /* Macros for load and store of accumulators. Can be modified to check
 125    for port addresses */
 126 #define LOADAC(reg) if((eaddr&0xff00)!=IOPAGE)reg=mem[eaddr];else\
 127            reg=do_input(eaddr&0xff);
 128 #define STOREAC(reg) if((eaddr&0xff00)!=IOPAGE)SETBYTE(eaddr,reg)else\
 129      do_output(eaddr&0xff,reg);

[io.c]
117 int do_input(a)
118 {
119  static int c,f=EOF;
120  if(a==0) {
121   if(f==EOF) f=char_input();
122   if(f!=EOF)c=f;
123
124   fprintf(stderr, "## INPUT(0) -> %d\n", 2+(f!=EOF)); // yak
125
126   return 2+(f!=EOF);
127  }else if(a==1) { /*data port*/
128   if(f==EOF) f=char_input();
129   if(f!=EOF){c=f;f=EOF;}
130
131   fprintf(stderr, "## INPUT(1) -> %d\n", c); // yak
132
133   return c;
134  }
135 }


~/6809/sbc09$ fgrep -v 'INPUT(0) -> 2' /tmp/log
## INPUT(0) -> 3
## INPUT(1) -> 97
## INPUT(0) -> 3
## INPUT(1) -> 98
## INPUT(0) -> 3
## INPUT(1) -> 99
## INPUT(0) -> 3
## INPUT(1) -> 100
## INPUT(0) -> 3
## INPUT(1) -> 101
## INPUT(0) -> 3
## INPUT(1) -> 102
## INPUT(0) -> 3
## INPUT(1) -> 103
## INPUT(0) -> 3
## INPUT(1) -> 13
## INPUT(0) -> 3
## INPUT(1) -> 3

;;;;;;;;;;;;;;;;;;;;;;;;;

$ go run grok_os9_disk/grok_os9_disk.go < .../nitros9/nos96809l1v030208coco_40d_1.dsk

DD.TOT: 00 05 a0        [3] "Total number of sectors" :: 1440
DD.TKS: 12      [1] "Track size in sectors" :: 18
DD.MAP: 00 b4           [2] "Number of bytes in allocation bit map" :: 180
DD.BIT: 00 01           [2] "Number of sectors/bit" :: 1
DD.DIR: 00 00 02        [3] "Address of root directory fd" :: 2
DD.OWN: 00 00           [2] "Owner" :: 0
DD.ATT: ff      [1] "Attributes" :: 255
DD.DSK: 01 80           [2] "Disk ID" :: 384
DD.FMT: 03      [1] "Disk format; density/sides" :: 3
DD.SPT: 00 12           [2] "Sectors/track" :: 18
DD.RES: 00 00           [2] "Reserved for future use" :: 0
DD.SIZ:         [0] "Device descriptor minimum size" :: @21
DD.BT:  00 00 0c        [3] "System bootstrap sector" :: 12
DD.BSZ: 34 c3           [2] "Size of system bootstrap" :: 13507
DD.DAT: 6c 05 1a 0f 35          [5] "Creation date" :: 2008-05-26 15:53
DD.NAM: 4e 69 74 72 4f 53 2d 39 2f 36 38 30 39 20 4c 65 76 65 6c 20 31 20 44 69 73 6b 20 b1 00 00 00 00         [32] "Volume name" :: "NitrOS-9/6809 Level 1 Disk 1"
DD.OPT: 01 01 00 20 01 00 28 02 00 00 12 00 12 03 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00         [32] "Option area" :: --


>>> 1224 / 18.0
68.0

$ dd if=.../nitros9/nos96809l1v030208coco_40d_1.dsk  bs=256 skip=1224 of=/tmp/bs

$ od -c /tmp/bs | head
0000000   O   S     023 022 005 207 315  \0   u  \0  \r 301 205 211  \0
0000020 021  \0  \0   R   E 314 005 177 377 003 267 377 337 306 006 216
0000040 377 306 247 201   Z   & 373 247 001 216 200  \0 020 216 002  \0
0000060 206   ` 247 200   1   ?   & 372 216 201  \n   1 214   . 306  \f
0000100 246 240 247 200   Z   & 371 314 022 022 020 223   x   ' 026   3
0000120 215 377 255 216 020 200 020 216 356  \0 246 300 247 240   0 037
0000140   & 370   ~ 356   e   0 214 023 354  \t   n 213   N   I   T   R
0000160   O   S   y   `   B   O   O   T 341 350   - 207 315  \b  \v  \0
0000200  \r 301 201 373  \0   t  \0  \0   K   r 356 017   I   n   i 364
0000220   k   r   n   p 262     017 022     020 022     021 022     022

Making an archive of things related to OS9 & the Motorola 6809.

Thanks:

https://sites.google.com/a/aaronwolfe.com/cococoding/home/docs

http://www.classiccmp.org/dunfield/coco/index.htm ( Daves Old Computers - RadioShack-Tandy Color Computer/Dragon )

https://web.archive.org/web/20070112041235/http://www.striker.ottawa.on.ca/6809/

https://web.archive.org/web/20070114010804/http://koti.mbnet.fi/~atjs/mc6809/index.html

ocem == ocem emulator COCO 3/OS-9

ftp://os9archive.rtsi.com/OS9

https://github.com/maly/6809js

http://www.lcurtisboyle.com/nitros9/nitros9.html

https://launchpad.net/~tormodvolden/+archive/ubuntu/m6809

http://lwtools.projects.l-w.ca/

https://web.archive.org/web/20061029033720/http://www.roug.org/soren/6809

6809 Emulation

The OS9L1 is an OS9 level One emulator (for Motorola 6809) that runs under UNIX/Linux. It is almost full-featured, and can emulate fork, signals, pipes etc. All without needing the OS9 kernel from Microware.

The emulator is built on Ray Bellis' Usim emulator, and also fixes some bugs in same.

version 1.0 source (~142K). Released 23/9-2001 version 1.1 source (~90K). Released 19/6-2002

http://sourceforge.net/p/nitros9/wiki/The_NitrOS-9_Boot_Process_Explained/

Typing 'DOS' at the Disk Extended Color BASIC 'OK' prompt on a CoCo loads in track 34 off of the disk. Track 34 consists of 18 total 256 byte sectors; that's 4,608 bytes. Here's what happens when 'DOS' is typed:

Track 34 gets loaded into address $2600. The first two bytes of the contents at track 34 are 'O' and 'S'. Upon load, execution of code starts at $2602.

$2602 contains a BRA to the execution point of the REL module.

REL copies the boot track ($2600 to $3800) to address $ED00, and jumps to another routine inside of REL, at the new address.

REL then jumps to KRN, which sets up system variables, the system memory map, system call tables, IRQ & SWI setup, and calls BOOT.

BOOT reads sector $000000 off of a disk, and finds out where the OS9Boot file is.

BOOT requests system memory for the size of OS9Boot, seeks to where OS9Boot is, and loads it directly into RAM.

It then returns to KRN, after setting up pointers in low memory to the OS9Boot file.

KRN links to KRNP2, and jumps into it.

KRNP2 sets up more system calls, links to the CLOCK module, and calls it.

CLOCK sets up some more system calls, starts multitasking, and returns to KRNP2.

KRNP2 then does F$Chain of SYSGO. This prints a start up banner, and runs your 'startup' file through a shell.

Troubleshooting the NitrOS-9 Level2 boot

See Chris Hawks post http://five.pairlist.net/pipermail/coco/2012-September/062120.html

http://www.lcurtisboyle.com/nitros9/nitros9.html

Since some people have been having problems with Alan's larger .DSK images on his site, I have decided to put up a bare bones, 40 track boot DSK image (in ZIP format) here. If you have a real Coco running OS-9 Level II (or an earlier version of NitrOS9), you can use my OS9 DSK Converter program as a base to make a real disk. The program is written in BASIC09, but defaults to a 35 track DSK image... you will have to change it slightly before running to make it 40 track ready. You will also need DMODE (rename it to 'dmode', and set the execution attributes) in your CMDS directory. To create your disk, you will need to do the following (after installing the above DMODE command):

1) Use DMODE to change your floppy drive to 40 tracks, and single sided. Do this by typing: 'DMODE /D0 cyl=28 sid=1' (Please substitute whichever drive name you are using for /D0 above).

2) Format the disk by typing: 'FORMAT /D0' (or whatever drive name you are using).

3) Type 'BASIC09' (it may be on a different disk, if you are using the stock OS-9 disks. If this is the case, switch disks, and then type '/dd/cmds/basic09' instead).

4) After BASIC09 boots, type 'LOAD convdsk.b09'.

5) Type 'e' (To enter EDIT mode).

6) Type 's!dmode' (Will find the dmode command line).

7) Type 'c!cyl=23!cyl=28' (Will change for 40 track disks).

8) Type 's!TO 34' (Searches for track loop).

9) Type 'c!34!39' (Changes 35 track to 40 track... with base 0).

10) Type 'q' (exit EDIT mode).

At this point, you should see a 'B:' prompt. At this point, type 'RUN'. It will prompt you for the name of the .DSK image file (type in the full path, if necessary). This can be on another floppy drive, a hard drive, or a RAM drive. If you typed in a good path, it will then prompt you for the drive to write it on. BE CAREFUL - DON'T SELECT ANY DRIVE UNLESS IT HAS YOUR BLANK, 40 TRACK FORMATTED DISK THAT WE CREATED IN STEP 2 ABOVE! The program should then create a real, 40 track bootable disk for you.

Download the NITROS9.ZIP zipped .DSK file. If you need the UNZIP utility for the Coco, you will need to download both UNZIP and FUNZIP. Because of problems with web browswer downloads, you will have to rename them to UNZIP and FUNZIP yourself (they will currently have a .bin extension). You will also have to set the execution attributes (ATTR [filename] e pe). Then, just run UNZIP for instructions.

This boot disk for NitrOS9 contains the most up to date graphics drivers (from my NitrOS9 beta page), and Shellplus Version 2.2a (the one with command history, accessed by the up and down arrow keys). It has a few useful programs on it, but not a lot. It does NOT currently contain the Y2K compliant clock drivers or SETIME command. It also uses a fairly stock CC3Go module, which is why it will boot up with a regular OS-9 screen (after the NitrOS9 boot information goes flying by).

The boot track contains the 32 column version of REL, which is why you are in 32 column mode right after you type 'DOS' to boot. It also has the BOOT module for the stock Tandy floppy controller. After it loads the OS9Boot file, you will kick into an 80x25 hardware text window (/term), and you have the following drivers/descriptors loaded:

VRN/VI/FTDD - This is Bruce Isted's Virtual IRQ driver. This combines the functionality of several special drivers used by some games (the Sierra VI driver, used by Leisure Suit Larry and Kings Quest III, and the FTDD driver from Flight Sim II), as well as the /NIL device. Basically, it means you can use NIL, and any of the three above games, without rebooting with a special boot disk. It should be noted that KQIII and LSL will only run properly with machines with either 256K or 512K of RAM; 1MB and above will not work properly due to some hard-coding in the Sierra programs. Flight Sim II has no such problem.

Clock - the non-Y2K compliant, but otherwise fully updated, software clock for 60Hz systems.

RBF - This is the editon #34 version, which has the capability of undeleting files.

CC3Disk - This is the edition #11 version, which has the capability (with the right utilities) of reading 512 byte sector disks, including MS-DOS disks.

DD and D1 - These are currently set up as 40 track, double-sided drive descriptors (drive 0 and 1). Since OS-9 reads the first sector of a disk to determine it's format, it can properly read single sided disks as well. However, if you only have a single side drive, you should use the DMODE utility to change the # of sides to 1.

RAMMER/R0/MD - RAM disk driver. R0 is the standard RAM disk, that is DMODE compatible and can be set up to exactly match physical drives, making it useful in making one pass backups. MD is a special descriptor for editing the Coco's memory raw WHILE THE SYSTEM IS RUNNING - only use if you REALLY know what you are doing. This version of RAMMER knows how to handle memory above 512k, if I remember correctly.

Windint/CC3IO/TERM/W/W1 thru W7 - The full windowing version of the graphics drivers, including the 3D look menus. Includes some additions and bug fixes that may not be in Alan's version (see my NitrOS9 page for details.

VDGINT/VERM - The older, Coco 2 compatible graphics drivers, which allows older games to run, 32 column Coco 1/2 screens, and also some of the Coco 3 direct screen write games (Rescue of Fractalus, for example) to run. NOTE: This is the FULL version, not the Tiny or Small versions mentioned on Alan's page.

PIPE/PIPER/PIPEMAN - The really fast pipes that Alan did.

SERMIDI - I think I left this in by accident, but it is to drive a MIDI synthesizer from the bit banger port (used by Ultimuse).

When the SHELL is loaded, it brings along some other utilities that will always be loaded in memory for you to use, without having to read from disk. They are:

SHELL - Command history Shellplus V2.2a - includes advance scripting, shell variables, redirection, etc.

D0OFF - A little utility to shut your drive motors off, in case the boot doesn't do it on it's own.

MERGE - utility to merge files to other files, or to devices (used to load fonts by merging with a window, for example).

ECHO - Echos text to the standard output device... which can be redirected.

LIST - Used to list text files to the standard output device - useful for listing documentation files.

MAKDIR - Makes directories.

DEL - Deletes files (but not directories).

UNLINK - Unlinks a module in memory (or decrements link count if linked more than once).

LINK - Increments the link count of a module in memory.

LOAD - Loads a module in memory. If you don't want to constantly have to load a command off of disk, use this first.

The CMDS directory contains a lot more commands that you can run. Most of these have built in help, so I won't list their function here. GRFDRV is actually part of the graphics driver sub-system... don't try to run it. DED is a disk editor, VU is a much more versatile text file lister than LIST is, KUTIL is a utility for creating or changing the OS-9 Kernal track (what runs when you type DOS), KWIKGEN is a complete Boot disk editor, which is MUCH faster than EZGEN or OS9GEN, DIRM is a fast MDIR -E style utility, DDIR is a utility that lists your current active device table, FRMEM lists your free memory (including >512K), and there are others (do a DIR CMDS to see them). Special mention should be made about the two FORMAT commands (FORMAT and FORMAT.ORIG): FORMAT.ORIG is the normal FORMAT command from Tandy/Microware, but the FORMAT command itself is a special version: it shrinks the number of 'extra' bytes between sectors on a disk. Using this, you can set your number of sectors per track to up to 20 (instead of the normal 18), thus gaining .5K per track on your disk. With an 80 track, double sided drive, you increase your storage from 720K to 800K.

If you get any errors, and are wondering what the error #'s mean, just type 'ERROR ###', where ### is the error number itself. This will give you an english version of the error.

The STARTUP file (in the root directory) is the equivalent of AUTOEXEC.BAT on DOS/Windows systems. This particular one loads in all the standard 2/4/16 color pattern buffers, mouse pointers, and the standard hi-res font, so you can see what you are doing on graphics windows.

There may be some glitches on this disk image (I think the 224 character fonts got fried), but you can replace some of the stuff, or add to it, from my NitrOS9 web link above (such as GSHELL), or from Alan's site. Hopefully, this will give some of you a start with NitrOS9...and a definate speed up from what you are used to if you are running on a real Coco 3 with the 6309 upgrade chip.

For those of you wondering what the fuss is about, here is a screenshot of the last GShell I did, which one can get at The NitrOS9 Project. This version included a new 3D look, live folder updates, base palette settings, and the drag and drop printer option.

More to come later!

-L. Curtis Boyle, Jan. 26/2001-

http://sourceforge.net/p/nitros9/wiki/Main_Page/

NitrOS-9 FAQ

What is NitrOS-9?

NitrOS-9 is an "OS-9 compatible" operating system for the TRS-80 Color Computer, Radio Shack Color Computer 2 and Tandy Color Computer 3. It is intended to replace both OS-9 Level One and OS-9 Level Two (once sold by Tandy through Radio Shack stores), as those products are no longer available, and have not been sold for years.

Is NitrOS-9 completely compatible with OS-9 for the Color Computer?

Yes, NitrOS-9 maintains compatibility with OS-9 Level One and OS-9 Level Two by using identical system calls and I/O handling. Existing utilities and applications developed for those operating systems should work fine under NitrOS-9.

I thought NitrOS-9 was only for the Tandy Color Computer 3 with a 6309 CPU. Is that true?

Historically, NitrOS-9 has been a 6309-only product. However, it has now been ported to the 6809 processor and supports Level 1 for the Color Computer. Since all Color Computers can now run NitrOS-9, the name was extended to cover all Color Computer platforms using either the 6309 or 6809.

How do I know which version of NitrOS-9 is for which Color Computer?

NitrOS-9 supports three "levels" and two processors, yielding six potential distributions: NitrOS-9/6809 Level 1 for the Color Computer NitrOS-9/6309 Level 1 for the Color Computer with a 6309 NitrOS-9/6809 Level 2 for the Color Computer 3 NitrOS-9/6309 Level 2 for the Color Computer 3 with a 6309 NitrOS-9/6809 Level 3 for the Color Computer 3 NitrOS-9/6309 Level 3 for the Color Computer 3 with a 6309

In short, Level 2 and Level 3 are exclusively for the Color Computer 3. Level 2 is compatible with OS-9 Level Two, and Level 3 contains additional features to manage system memory more efficiently.

Currently, NitrOS-9/6809 Level 1, NitrOS-9/6809 Level 2, and NitrOS-9/6309 Level 2 are available. The other distributions are still under development.

Is it legal to download and use NitrOS-9?

NitrOS-9 has been in existence since 1994, having been created by a number of dedicated individuals within the Color Computer community. Much of the code was written by the original NitrOS-9 team: Wes Gale, Bill Noble and Curtis Boyle. Later, Alan DeKok made even further improvements. Therefore, NitrOS-9 is an operating system created by the Color Computer Community, for the Color Computer Community.

How critical is it for me to use NitrOS-9? Can't I just stick with OS-9 Level One or Two?

There are two issues with OS-9 Level One or OS-9 Level Two today: first, there is no upgrade path for the products; second, neither operating system has been sold in Radio Shack stores for years, denying new users the ability to purchase valid licenses.

NitrOS-9 is today's and tomorrow's operating system for all Color Computers. It is constantly being improved and enhanced, is freely available, and is also faster and more optimized than Tandy's OS-9 operating systems.

Whatever happened to TuneUp for OS-9 Level Two?

That product is now superseded by NitrOS-9.