Image Map Image Map
Page 2 of 2 FirstFirst 12
Results 11 to 13 of 13

Thread: Source listing for Jade Z80 CPU: "Jade Computer Systems Monitor 2.2B" anyone? :-(

  1. Default

    Hello Tom, sounds like you have made great progress on getting your Jade DD card to boot CP/M. If you get the disk drive head to load you are 99% there. The only thing I can think of is to check the DIP switch settings on the JadeDD positions 5,6 and 7 to see if they correspond to $0E000H (default setting) of "A10=0,A11=0,A12=0" for the DDBOOT.ASM EPROM. This is where being able to see system memory comes in handy. If system memory stops short of $D800H, you can clearly see the 1K block of RAM at $E000H, the BOOT EPROM at $F000H and the Monitor EPROM at $F800H (for my system). I could never get the original Jade Monitor to display memory so I modified that portion of code to use the Doctor Dobbs/John Monahan memory display routing (the second image in my first post). The "Insert System Disk" comes from the DDBOOT.ASM code so it looks like your CP/M disk may not be good. The first image in my post above, shows all the information the Jade CP/M 2.2 disk gives when it boots. I never had an original Jade CP/M disk so I assumed the Dunfield version was it. His version of Jade CP/M does in fact work from the Image File on his site.
    If you have the .lst file from the System Monitor 2.2B, you should be able to find the "Menu Jump Table" in the code and follow it to the Memory Display routine to decipher the commands. If you want to compile and burn a new EPROM from the code in my 1st post, it has the memory display routine as well as the "DISK" and "RUN" routines to jump to the Boot ROM. If you go this route, you may have to modify the Console settings as it is currently set to work with the Propeller Console board.
    > Charles

  2. #12
    Join Date
    Mar 2013
    Chaffee, MO


    It may not be of any help, but I've got the JADEDD.IMD (JADEDD.RAW) file with all of the *.ASM extracted. The ASM list is:

    cpmls -f a1 -li JADEDD.RAW
    4 -rwxrwxrwx 8192 Dec 31 1969
    11 -rw-rw-rw- 12288 Dec 31 1969 bios.asm
    16 -rwxrwxrwx 768 Dec 31 1969
    19 -rw-rw-rw- 5888 Dec 31 1969 bioslder.asm
    20 -rw-rw-rw- 50048 Dec 31 1969 dcm2.asm
    29 -rw-rw-rw- 2432 Dec 31 1969 dcm2.hex
    17 -rwxrwxrwx 768 Dec 31 1969
    24 -rw-rw-rw- 21504 Dec 31 1969 ddbios.asm
    12 -rw-rw-rw- 25600 Dec 31 1969 ddboot.asm
    5 -rwxrwxrwx 4864 Dec 31 1969
    14 -rw-rw-rw- 10240 Dec 31 1969 deblock.asm
    15 -rw-rw-rw- 6272 Dec 31 1969 diskdef.lib
    10 -rw-rw-rw- 4224 Dec 31 1969 dump.asm
    9 -rwxrwxrwx 512 Dec 31 1969
    3 -rwxrwxrwx 6656 Dec 31 1969
    26 -rw-rw-rw- 34304 Dec 31 1969 format.asm
    30 -rwxrwxrwx 2816 Dec 31 1969
    6 -rwxrwxrwx 1792 Dec 31 1969
    0 -rwxrwxrwx 9728 Dec 31 1969
    8 -rwxrwxrwx 1024 Dec 31 1969
    31 -rwxrwxrwx 7424 Dec 31 1969
    7 -rwxrwxrwx 5248 Dec 31 1969
    1 -rwxrwxrwx 1280 Dec 31 1969
    18 -rwxrwxrwx 768 Dec 31 1969
    2 -rwxrwxrwx 768 Dec 31 1969

    You will probably want to have a look at the .ASM files as it appears to be 2.2 and release 2A for Disk Controller Module.
    Same version 2A for Double Density BIOS.

    All of the .ASM file listings look sane. The A1 definition will get cpmtools access to the JADEDD.RAW files.

    # A1 Generic CP/M - SSSD 8" - 128 x 26
    diskdef a1
    seclen 128
    tracks 77
    sectrk 26
    blocksize 1024
    maxdir 64
    skew 6
    boottrk 2
    os 2.2

    # libdsk data below
    description = A1 Generic CP/M - SSSD 8" - 128 x 26
    cylinders = 77
    heads = 1
    secsize = 128
    sectors = 26
    secbase = 1
    datarate = HD

    You will have to massage the .RAW file a bit to get past the large Track1 problem.

    I don't have any other JADE (.TD0, .IMD, or other ext) files that I have gleaned as I travel over the internet.

    Email me if you want the code.

    Check here:


    Last edited by ldkraemer; May 13th, 2018 at 07:08 PM. Reason: updated

  3. #13
    Join Date
    Nov 2016
    Muskego, Wisconsin


    Thank you Larry! (And all others who have responded.)
    With out going into a lot of detail, my "bring - CP/M - alive - again" project has been riddled with frustration.
    I was using an "old" XP machine (off line) to save all my re-documenting, assembling, EPROM burning, xmodem, hyper terminal etc.
    Well, the stooopid 2018 1T drive in the XT crashed .. So, I'm going to have to go back and try to reconstruct what I
    thought I was thru doing >



Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts