Matchbox sized 6502 / Z80 / 6809 Co Pro

discussion of games, software, hardware & emulators relating to the Acorn Atom and Acorn System machines.
User avatar
flynnjs
Posts: 830
Joined: Tue Jul 06, 2010 9:33 pm
Contact:

Re: Matchbox sized 6502 / Z80 / 6809 Co Pro

Post by flynnjs » Mon Nov 16, 2015 7:53 am

hoglet wrote: I wish I'd had the ICE-T65 when we started this project - it's far easier to use than the logic analyser.
Dave
That's why I've set an ICE up, it's going to be somuch easier to debug my next development.
Having said that, to get it off the ground I suspect I'll be using both ICE and LA :?

At some point soon, I'm going to be looking to put an image on the next batch of CoPros.
Is there anything else you'd like to squeeze in before I do so? It seems to have settled
down a bit now.

User avatar
hoglet
Posts: 8830
Joined: Sat Oct 13, 2012 6:21 pm
Location: Bristol
Contact:

Re: Matchbox sized 6502 / Z80 / 6809 Co Pro

Post by hoglet » Mon Nov 16, 2015 9:05 am

flynnjs wrote: At some point soon, I'm going to be looking to put an image on the next batch of CoPros.
Is there anything else you'd like to squeeze in before I do so? It seems to have settled
down a bit now.
I'm not working on anything else Co Pro related at the moment, so the most recent firmware should be good.

Dave

User avatar
jgharston
Posts: 3802
Joined: Thu Sep 24, 2009 11:22 am
Location: Whitby/Sheffield
Contact:

Re: Matchbox sized 6502 / Z80 / 6809 Co Pro

Post by jgharston » Mon Nov 16, 2015 5:56 pm

hoglet wrote:
jgharston wrote:
jgharston wrote:Give me a mo, I'm building a new version which I think has fixed things...
Here we are: RamFS101fx. I'd missed off inserting the jump to the patched release code. Patched with PatchRFS.
Hmmm, it's still not sending Tube Release. But at least the version number is printed as 1.01. :lol:
Weird. I've hooked some debug code into the Tube Host, and the patched RamFS is doing a Tube Relase, but not a Tube Claim!

Code: Select all

>*TDEBUG
>*RAM
>LOAD "HELLO"
018F>
>*NET
>LOAD "HELLO"
C20382C20382C20382C20382>
RamFS is calling &406 with A=1 "SendBytes" then A=8F "Release ID=15".
NetFS is calling &406 with A=C2 "Claim ID=2", A=3 "SendWords", A=82 "Release ID=2".

As RamFS has not actually claimed the Tube, the Tube Host does not sent the Release call to the CoPro as as far as the Tube Host is concerned, it hasn't been claimed, so there's no Release to send.

Code: Select all

$ bbcbasic
PDP11 BBC BASIC IV Version 0.25
(C) Copyright J.G.Harston 1989,2005-2015
>_

User avatar
jgharston
Posts: 3802
Joined: Thu Sep 24, 2009 11:22 am
Location: Whitby/Sheffield
Contact:

Re: Matchbox sized 6502 / Z80 / 6809 Co Pro

Post by jgharston » Mon Nov 16, 2015 8:12 pm

jgharston wrote:As RamFS has not actually claimed the Tube, the Tube Host does not sent the Release call to the CoPro as as far as the Tube Host is concerned, it hasn't been claimed, so there's no Release to send.
Here we are, seems to be fixed.
RamFS101fx patched with with PatchRFS.
Demo:

Code: Select all

>*TDEBUG
>*RAM
>*DRIVE 0
>LOAD "FRED"
CF018F>REM Loaded from RAM drive
>*DRIVE 4
>LOAD "FRED"
CF018F>REM Loaded from NV drive
>*DRIVE 5
>LOAD "FRED"
CF018F>REM Loaded from USB drive
SAVE does the same, with action 00 instead of 01.

....it's just occured to me that I haven't check for OSGBPB data transfer.

Edit: just tested, and OSGBPB neither claims nor releases the Tube. #-o

Code: Select all

>P.OPENIN"CPMDISC"
        96
>PROCgbpb(4,96,&10000,512,0)
01>

Code: Select all

$ bbcbasic
PDP11 BBC BASIC IV Version 0.25
(C) Copyright J.G.Harston 1989,2005-2015
>_

User avatar
jgharston
Posts: 3802
Joined: Thu Sep 24, 2009 11:22 am
Location: Whitby/Sheffield
Contact:

Re: Matchbox sized 6502 / Z80 / 6809 Co Pro

Post by jgharston » Mon Nov 16, 2015 9:42 pm

In light of the RamFS problems, I'm going to roll the 6809 Tube Client version number back to 0.25 until after the ABUG meeting next weekend so I can do some hand-on hardware testing, in case there's any tweeks I still need to make. There's no difference between v0.25 and v1.00 other than the version number. I'm hoping that next week I can just go back to making the version number 1.00 with no other changes.

Code: Select all

$ bbcbasic
PDP11 BBC BASIC IV Version 0.25
(C) Copyright J.G.Harston 1989,2005-2015
>_

User avatar
hoglet
Posts: 8830
Joined: Sat Oct 13, 2012 6:21 pm
Location: Bristol
Contact:

Re: Matchbox sized 6502 / Z80 / 6809 Co Pro

Post by hoglet » Mon Nov 16, 2015 9:46 pm

jgharston wrote:In light of the RamFS problems, I'm going to roll the 6809 Tube Client version number back to 0.25 until after the ABUG meeting next weekend so I can do some hand-on hardware testing, in case there's any tweeks I still need to make. There's no difference between v0.25 and v1.00 other than the version number. I'm hoping that next week I can just go back to making the version number 1.00 with no other changes.
Argggghhhhh!!! Is that really necessary?????

It's a pain having to re-build and re-test the complete Matchbox Firmware package, just for a version number change.

User avatar
hoglet
Posts: 8830
Joined: Sat Oct 13, 2012 6:21 pm
Location: Bristol
Contact:

Re: Matchbox sized 6502 / Z80 / 6809 Co Pro

Post by hoglet » Mon Nov 16, 2015 9:47 pm

I've just tested the 1.01 version of RamFS on the real hardware and LOAD/SAVE no longer hang.

Dave

User avatar
jgharston
Posts: 3802
Joined: Thu Sep 24, 2009 11:22 am
Location: Whitby/Sheffield
Contact:

Re: Matchbox sized 6502 / Z80 / 6809 Co Pro

Post by jgharston » Tue Nov 17, 2015 12:10 am

hoglet wrote:I've just tested the 1.01 version of RamFS on the real hardware and LOAD/SAVE no longer hang.
Wonderful. That makes me confidant that there's no problem in the 6809 client, so it can stay at version 1.00.

Just one last thought: Does running 6809 code from disk work, ie can EXBAS09.bin and Test09.bin (load=8000, exec=8000) be run from disk with *EXBAS09 as opposed to doing *LOAD EXBAS09 then *GO 8000. (see edit)

There was a nagging thought at the back of my mind there was some problem. I had a quick skim through the threads but didn't find anything I remembered. I think it might be an issue with Flex boot disks not running from Shift-Break *Run !Boot but does work from *FLEX.

Edit: Sample 6809 code now bundled into a Samples DFS disk image.

Code: Select all

$ bbcbasic
PDP11 BBC BASIC IV Version 0.25
(C) Copyright J.G.Harston 1989,2005-2015
>_

User avatar
hoglet
Posts: 8830
Joined: Sat Oct 13, 2012 6:21 pm
Location: Bristol
Contact:

Re: Matchbox sized 6502 / Z80 / 6809 Co Pro

Post by hoglet » Tue Nov 17, 2015 10:53 am

jgharston wrote: Just one last thought: Does running 6809 code from disk work, ie can EXBAS09.bin and Test09.bin (load=8000, exec=8000) be run from disk with *EXBAS09 as opposed to doing *LOAD EXBAS09 then *GO 8000. (see edit)
*RUNing both of these works fine now.
jgharston wrote: There was a nagging thought at the back of my mind there was some problem. I had a quick skim through the threads but didn't find anything I remembered. I think it might be an issue with Flex boot disks not running from Shift-Break *Run !Boot but does work from *FLEX.
I've just tried FLEX (from Rob's BBCFLEX09) and there does seem to be a problem, even with *FLEX. I've tried with and without *DRTRAP, and the results are the same. It just hangs.

Here's an ICE T65 trace:

Code: Select all

15.274757: Mem Wr Watch hit at 069A writing FEE3 = 7F

15.274783: Mem Wr Watch hit at 069A writing FEE3 = 52
15.274816: Mem Wr Watch hit at 069A writing FEE3 = 55
15.274849: Mem Wr Watch hit at 069A writing FEE3 = 4E
15.274882: Mem Wr Watch hit at 069A writing FEE3 = 20
15.274915: Mem Wr Watch hit at 069A writing FEE3 = 46
15.274948: Mem Wr Watch hit at 069A writing FEE3 = 4C
15.274981: Mem Wr Watch hit at 069A writing FEE3 = 45
15.275014: Mem Wr Watch hit at 069A writing FEE3 = 58
15.275047: Mem Wr Watch hit at 069A writing FEE3 = 0D

15.275281: Mem Rd Watch hit at 004B reading FEE3 = 02
15.275315: Mem Rd Watch hit at 06CA reading FEE3 = 52
15.275351: Mem Rd Watch hit at 06CA reading FEE3 = 55
15.275387: Mem Rd Watch hit at 06CA reading FEE3 = 4E
15.275423: Mem Rd Watch hit at 06CA reading FEE3 = 20
15.275459: Mem Rd Watch hit at 06CA reading FEE3 = 46
15.275495: Mem Rd Watch hit at 06CA reading FEE3 = 4C
15.275531: Mem Rd Watch hit at 06CA reading FEE3 = 45
15.275567: Mem Rd Watch hit at 06CA reading FEE3 = 58
15.275603: Mem Rd Watch hit at 06CA reading FEE3 = 0D

15.317730: Mem Wr Watch hit at 06A3 writing FEE7 = 01
15.317759: Mem Wr Watch hit at 06A3 writing FEE7 = CF
15.317786: Mem Wr Watch hit at 06A3 writing FEE7 = 00
15.317818: Mem Wr Watch hit at 06A3 writing FEE7 = 00
15.317850: Mem Wr Watch hit at 06A3 writing FEE7 = C1
15.317882: Mem Wr Watch hit at 06A3 writing FEE7 = 00
15.317929: Mem Wr Watch hit at 06A3 writing FEE7 = 22

15.342106: Mem Wr Watch hit at 06A3 writing FEE7 = 05
15.342138: Mem Wr Watch hit at 06A3 writing FEE7 = CF

15.342445: Mem Wr Watch hit at 06A3 writing FEE7 = 04
15.342474: Mem Wr Watch hit at 06A3 writing FEE7 = 80
15.342501: Mem Wr Watch hit at 06A3 writing FEE7 = 00
15.342533: Mem Wr Watch hit at 06A3 writing FEE7 = 00
15.342565: Mem Wr Watch hit at 06A3 writing FEE7 = C1
15.342597: Mem Wr Watch hit at 06A3 writing FEE7 = 20
15.342644: Mem Wr Watch hit at 06A3 writing FEE7 = 06

15.342691: Mem Wr Watch hit at 06A3 writing FEE7 = 05
15.342723: Mem Wr Watch hit at 06A3 writing FEE7 = 80

15.342763: Mem Wr Watch hit at 069A writing FEE3 = 80

15.344799: Mem Rd Watch hit at 004B reading FEE3 = 08
15.344823: Mem Rd Watch hit at 06CA reading FEE3 = 7F
15.344841: Mem Rd Watch hit at 0630 reading FEE3 = 10
15.344883: Mem Rd Watch hit at 063B reading FEE3 = 3C
15.344903: Mem Rd Watch hit at 063B reading FEE3 = FF
15.344930: Mem Rd Watch hit at 063B reading FEE3 = 7F
15.344950: Mem Rd Watch hit at 063B reading FEE3 = 00
15.344970: Mem Rd Watch hit at 063B reading FEE3 = 00
15.344990: Mem Rd Watch hit at 063B reading FEE3 = 00
15.345010: Mem Rd Watch hit at 063B reading FEE3 = 21
15.345037: Mem Rd Watch hit at 063B reading FEE3 = 00
15.345057: Mem Rd Watch hit at 063B reading FEE3 = 01
15.345077: Mem Rd Watch hit at 063B reading FEE3 = 57
15.345097: Mem Rd Watch hit at 063B reading FEE3 = 03
15.345117: Mem Rd Watch hit at 063B reading FEE3 = 00
15.345144: Mem Rd Watch hit at 063B reading FEE3 = 00
15.345164: Mem Rd Watch hit at 063B reading FEE3 = C3
15.345184: Mem Rd Watch hit at 063B reading FEE3 = 00
15.345204: Mem Rd Watch hit at 063B reading FEE3 = 00
15.346356: Mem Rd Watch hit at 0651 reading FEE3 = 10

15.346374: Mem Wr Watch hit at 065F writing FEE3 = 3C
15.346393: Mem Wr Watch hit at 065F writing FEE3 = FF
15.346412: Mem Wr Watch hit at 065F writing FEE3 = 7F
15.346431: Mem Wr Watch hit at 065F writing FEE3 = 00
15.346717: Mem Wr Watch hit at 065F writing FEE3 = 00
15.346736: Mem Wr Watch hit at 065F writing FEE3 = 00
15.346755: Mem Wr Watch hit at 065F writing FEE3 = 21
15.346774: Mem Wr Watch hit at 065F writing FEE3 = 00
15.346793: Mem Wr Watch hit at 065F writing FEE3 = 01
15.346812: Mem Wr Watch hit at 065F writing FEE3 = 57
15.346831: Mem Wr Watch hit at 065F writing FEE3 = 03
15.346850: Mem Wr Watch hit at 065F writing FEE3 = 00
15.346869: Mem Wr Watch hit at 065F writing FEE3 = 00
15.346888: Mem Wr Watch hit at 065F writing FEE3 = C3
15.346907: Mem Wr Watch hit at 065F writing FEE3 = 00
15.346926: Mem Wr Watch hit at 065F writing FEE3 = 00

15.351884: Mem Rd Watch hit at 004B reading FEE3 = 08
15.351908: Mem Rd Watch hit at 06CA reading FEE3 = 7F
15.351926: Mem Rd Watch hit at 0630 reading FEE3 = 10
15.351968: Mem Rd Watch hit at 063B reading FEE3 = 3C
15.351988: Mem Rd Watch hit at 063B reading FEE3 = FF
15.352008: Mem Rd Watch hit at 063B reading FEE3 = 7F
15.352028: Mem Rd Watch hit at 063B reading FEE3 = 00
15.352048: Mem Rd Watch hit at 063B reading FEE3 = 00
15.352075: Mem Rd Watch hit at 063B reading FEE3 = 00
15.352095: Mem Rd Watch hit at 063B reading FEE3 = 21
15.352115: Mem Rd Watch hit at 063B reading FEE3 = 00
15.352135: Mem Rd Watch hit at 063B reading FEE3 = 01
15.352155: Mem Rd Watch hit at 063B reading FEE3 = 57
15.352182: Mem Rd Watch hit at 063B reading FEE3 = 03
15.352202: Mem Rd Watch hit at 063B reading FEE3 = 00
15.352222: Mem Rd Watch hit at 063B reading FEE3 = 00
15.352242: Mem Rd Watch hit at 063B reading FEE3 = C3
15.352262: Mem Rd Watch hit at 063B reading FEE3 = 00
15.352289: Mem Rd Watch hit at 063B reading FEE3 = 00
15.353441: Mem Rd Watch hit at 0651 reading FEE3 = 10

15.353459: Mem Wr Watch hit at 065F writing FEE3 = 3C
15.353478: Mem Wr Watch hit at 065F writing FEE3 = FF
15.353497: Mem Wr Watch hit at 065F writing FEE3 = 7F
15.353516: Mem Wr Watch hit at 065F writing FEE3 = 00
15.353535: Mem Wr Watch hit at 065F writing FEE3 = 00
15.353554: Mem Wr Watch hit at 065F writing FEE3 = 00
15.353573: Mem Wr Watch hit at 065F writing FEE3 = 21
15.353592: Mem Wr Watch hit at 065F writing FEE3 = 00
15.353611: Mem Wr Watch hit at 065F writing FEE3 = 01
15.353630: Mem Wr Watch hit at 065F writing FEE3 = 57
15.353649: Mem Wr Watch hit at 065F writing FEE3 = 03
15.353668: Mem Wr Watch hit at 065F writing FEE3 = 00
15.353687: Mem Wr Watch hit at 065F writing FEE3 = 00
15.353706: Mem Wr Watch hit at 065F writing FEE3 = C3
15.353725: Mem Wr Watch hit at 065F writing FEE3 = 00
15.353744: Mem Wr Watch hit at 065F writing FEE3 = 00

15.358688: Mem Rd Watch hit at 004B reading FEE3 = 08
15.358712: Mem Rd Watch hit at 06CA reading FEE3 = 7F
15.358737: Mem Rd Watch hit at 0630 reading FEE3 = 10
15.358772: Mem Rd Watch hit at 063B reading FEE3 = 3C
15.358792: Mem Rd Watch hit at 063B reading FEE3 = FF
15.358812: Mem Rd Watch hit at 063B reading FEE3 = 7F
15.358832: Mem Rd Watch hit at 063B reading FEE3 = 00
15.358852: Mem Rd Watch hit at 063B reading FEE3 = 00
15.358872: Mem Rd Watch hit at 063B reading FEE3 = 00
15.358892: Mem Rd Watch hit at 063B reading FEE3 = 21
15.358912: Mem Rd Watch hit at 063B reading FEE3 = 00
15.358932: Mem Rd Watch hit at 063B reading FEE3 = 01
15.358952: Mem Rd Watch hit at 063B reading FEE3 = 57
15.358979: Mem Rd Watch hit at 063B reading FEE3 = 03
15.358999: Mem Rd Watch hit at 063B reading FEE3 = 00
15.359019: Mem Rd Watch hit at 063B reading FEE3 = 00
15.359039: Mem Rd Watch hit at 063B reading FEE3 = C3
15.359059: Mem Rd Watch hit at 063B reading FEE3 = 00
15.359086: Mem Rd Watch hit at 063B reading FEE3 = 00
15.360238: Mem Rd Watch hit at 0651 reading FEE3 = 10

15.360256: Mem Wr Watch hit at 065F writing FEE3 = 3C
15.360275: Mem Wr Watch hit at 065F writing FEE3 = FF
15.360294: Mem Wr Watch hit at 065F writing FEE3 = 7F
15.360313: Mem Wr Watch hit at 065F writing FEE3 = 00
15.360332: Mem Wr Watch hit at 065F writing FEE3 = 00
15.360351: Mem Wr Watch hit at 065F writing FEE3 = 00
15.360370: Mem Wr Watch hit at 065F writing FEE3 = 21
15.360389: Mem Wr Watch hit at 065F writing FEE3 = 00
15.360408: Mem Wr Watch hit at 065F writing FEE3 = 01
15.360427: Mem Wr Watch hit at 065F writing FEE3 = 57
15.360446: Mem Wr Watch hit at 065F writing FEE3 = 03
15.360465: Mem Wr Watch hit at 065F writing FEE3 = 00
15.360484: Mem Wr Watch hit at 065F writing FEE3 = 00
15.360503: Mem Wr Watch hit at 065F writing FEE3 = C3
15.360522: Mem Wr Watch hit at 065F writing FEE3 = 00
15.360541: Mem Wr Watch hit at 065F writing FEE3 = 00

15.365274: Mem Rd Watch hit at 004B reading FEE3 = 08
15.365298: Mem Rd Watch hit at 06CA reading FEE3 = 7F
15.365316: Mem Rd Watch hit at 0630 reading FEE3 = 10
15.365358: Mem Rd Watch hit at 063B reading FEE3 = 3C
15.365378: Mem Rd Watch hit at 063B reading FEE3 = FF
15.365405: Mem Rd Watch hit at 063B reading FEE3 = 7F
15.365425: Mem Rd Watch hit at 063B reading FEE3 = 00
15.365445: Mem Rd Watch hit at 063B reading FEE3 = 00
15.365465: Mem Rd Watch hit at 063B reading FEE3 = 00
15.365485: Mem Rd Watch hit at 063B reading FEE3 = 21
15.365512: Mem Rd Watch hit at 063B reading FEE3 = 00
15.365532: Mem Rd Watch hit at 063B reading FEE3 = 01
15.365552: Mem Rd Watch hit at 063B reading FEE3 = 57
15.365572: Mem Rd Watch hit at 063B reading FEE3 = 03
15.365592: Mem Rd Watch hit at 063B reading FEE3 = 00
15.365619: Mem Rd Watch hit at 063B reading FEE3 = 00
15.365639: Mem Rd Watch hit at 063B reading FEE3 = C3
15.365659: Mem Rd Watch hit at 063B reading FEE3 = 00
15.365679: Mem Rd Watch hit at 063B reading FEE3 = 00
15.366831: Mem Rd Watch hit at 0651 reading FEE3 = 10

15.366849: Mem Wr Watch hit at 065F writing FEE3 = 3C
15.366868: Mem Wr Watch hit at 065F writing FEE3 = FF
15.366887: Mem Wr Watch hit at 065F writing FEE3 = 7F
15.366906: Mem Wr Watch hit at 065F writing FEE3 = 00
15.366925: Mem Wr Watch hit at 065F writing FEE3 = 00
15.366944: Mem Wr Watch hit at 065F writing FEE3 = 00
15.366963: Mem Wr Watch hit at 065F writing FEE3 = 21
15.366982: Mem Wr Watch hit at 065F writing FEE3 = 00
15.367001: Mem Wr Watch hit at 065F writing FEE3 = 01
15.367020: Mem Wr Watch hit at 065F writing FEE3 = 57
15.367039: Mem Wr Watch hit at 065F writing FEE3 = 03
15.367058: Mem Wr Watch hit at 065F writing FEE3 = 00
15.367077: Mem Wr Watch hit at 065F writing FEE3 = 00
15.367096: Mem Wr Watch hit at 065F writing FEE3 = C3
15.367115: Mem Wr Watch hit at 065F writing FEE3 = 00
15.367134: Mem Wr Watch hit at 065F writing FEE3 = 00

15.372076: Mem Rd Watch hit at 004B reading FEE3 = 08
15.372100: Mem Rd Watch hit at 06CA reading FEE3 = 7F
15.372125: Mem Rd Watch hit at 0630 reading FEE3 = 10
15.372160: Mem Rd Watch hit at 063B reading FEE3 = 3C
15.372180: Mem Rd Watch hit at 063B reading FEE3 = FF
15.372200: Mem Rd Watch hit at 063B reading FEE3 = 7F
15.372220: Mem Rd Watch hit at 063B reading FEE3 = 00
15.372240: Mem Rd Watch hit at 063B reading FEE3 = 00
15.372267: Mem Rd Watch hit at 063B reading FEE3 = 00
15.372287: Mem Rd Watch hit at 063B reading FEE3 = 21
15.372307: Mem Rd Watch hit at 063B reading FEE3 = 00
15.372327: Mem Rd Watch hit at 063B reading FEE3 = 01
15.372347: Mem Rd Watch hit at 063B reading FEE3 = 57
15.372374: Mem Rd Watch hit at 063B reading FEE3 = 03
15.372394: Mem Rd Watch hit at 063B reading FEE3 = 00
15.372414: Mem Rd Watch hit at 063B reading FEE3 = 00
15.372434: Mem Rd Watch hit at 063B reading FEE3 = C3
15.372454: Mem Rd Watch hit at 063B reading FEE3 = 00
15.372481: Mem Rd Watch hit at 063B reading FEE3 = 00
15.373633: Mem Rd Watch hit at 0651 reading FEE3 = 10

15.373651: Mem Wr Watch hit at 065F writing FEE3 = 3C
15.373670: Mem Wr Watch hit at 065F writing FEE3 = FF
15.373689: Mem Wr Watch hit at 065F writing FEE3 = 7F
15.373708: Mem Wr Watch hit at 065F writing FEE3 = 00
15.373727: Mem Wr Watch hit at 065F writing FEE3 = 00
15.373746: Mem Wr Watch hit at 065F writing FEE3 = 00
15.373765: Mem Wr Watch hit at 065F writing FEE3 = 21
15.373784: Mem Wr Watch hit at 065F writing FEE3 = 00
15.373803: Mem Wr Watch hit at 065F writing FEE3 = 01
15.373822: Mem Wr Watch hit at 065F writing FEE3 = 57
15.373841: Mem Wr Watch hit at 065F writing FEE3 = 03
15.373860: Mem Wr Watch hit at 065F writing FEE3 = 00
15.373879: Mem Wr Watch hit at 065F writing FEE3 = 00
15.373898: Mem Wr Watch hit at 065F writing FEE3 = C3
15.373917: Mem Wr Watch hit at 065F writing FEE3 = 00
15.373936: Mem Wr Watch hit at 065F writing FEE3 = 00

15.378882: Mem Rd Watch hit at 004B reading FEE3 = 08
15.378906: Mem Rd Watch hit at 06CA reading FEE3 = 7F
15.378931: Mem Rd Watch hit at 0630 reading FEE3 = 10
15.378966: Mem Rd Watch hit at 063B reading FEE3 = 3C
15.378986: Mem Rd Watch hit at 063B reading FEE3 = FF
15.379006: Mem Rd Watch hit at 063B reading FEE3 = 7F
15.379026: Mem Rd Watch hit at 063B reading FEE3 = 00
15.379046: Mem Rd Watch hit at 063B reading FEE3 = 00
15.379066: Mem Rd Watch hit at 063B reading FEE3 = 00
15.379086: Mem Rd Watch hit at 063B reading FEE3 = 21
15.379106: Mem Rd Watch hit at 063B reading FEE3 = 00
15.379133: Mem Rd Watch hit at 063B reading FEE3 = 01
15.379153: Mem Rd Watch hit at 063B reading FEE3 = 57
15.379173: Mem Rd Watch hit at 063B reading FEE3 = 03
15.379193: Mem Rd Watch hit at 063B reading FEE3 = 00
15.379213: Mem Rd Watch hit at 063B reading FEE3 = 00
15.379240: Mem Rd Watch hit at 063B reading FEE3 = C3
15.379260: Mem Rd Watch hit at 063B reading FEE3 = 00
15.379280: Mem Rd Watch hit at 063B reading FEE3 = 00
15.380432: Mem Rd Watch hit at 0651 reading FEE3 = 10

15.380450: Mem Wr Watch hit at 065F writing FEE3 = 3C
15.380469: Mem Wr Watch hit at 065F writing FEE3 = FF
15.380488: Mem Wr Watch hit at 065F writing FEE3 = 7F
15.380507: Mem Wr Watch hit at 065F writing FEE3 = 00
15.380526: Mem Wr Watch hit at 065F writing FEE3 = 00
15.380545: Mem Wr Watch hit at 065F writing FEE3 = 00
15.380564: Mem Wr Watch hit at 065F writing FEE3 = 21
15.380583: Mem Wr Watch hit at 065F writing FEE3 = 00
15.380602: Mem Wr Watch hit at 065F writing FEE3 = 01
15.380621: Mem Wr Watch hit at 065F writing FEE3 = 57
15.380640: Mem Wr Watch hit at 065F writing FEE3 = 03
15.380659: Mem Wr Watch hit at 065F writing FEE3 = 00
15.380678: Mem Wr Watch hit at 065F writing FEE3 = 00
15.380697: Mem Wr Watch hit at 065F writing FEE3 = C3
15.380716: Mem Wr Watch hit at 065F writing FEE3 = 00
15.380735: Mem Wr Watch hit at 065F writing FEE3 = 00

15.385492: Mem Rd Watch hit at 004B reading FEE3 = 08
15.385516: Mem Rd Watch hit at 06CA reading FEE3 = 7F
15.385534: Mem Rd Watch hit at 0630 reading FEE3 = 10
15.385576: Mem Rd Watch hit at 063B reading FEE3 = 3C
15.385596: Mem Rd Watch hit at 063B reading FEE3 = FF
15.385623: Mem Rd Watch hit at 063B reading FEE3 = 7F
15.385643: Mem Rd Watch hit at 063B reading FEE3 = 00
15.385663: Mem Rd Watch hit at 063B reading FEE3 = 00
15.385683: Mem Rd Watch hit at 063B reading FEE3 = 00
15.385703: Mem Rd Watch hit at 063B reading FEE3 = 21
15.385730: Mem Rd Watch hit at 063B reading FEE3 = 00
15.385750: Mem Rd Watch hit at 063B reading FEE3 = 01
15.385770: Mem Rd Watch hit at 063B reading FEE3 = 57
15.385790: Mem Rd Watch hit at 063B reading FEE3 = 03
15.385810: Mem Rd Watch hit at 063B reading FEE3 = 00
15.385830: Mem Rd Watch hit at 063B reading FEE3 = 00
15.385857: Mem Rd Watch hit at 063B reading FEE3 = C3
15.385877: Mem Rd Watch hit at 063B reading FEE3 = 00
15.385897: Mem Rd Watch hit at 063B reading FEE3 = 00
15.387049: Mem Rd Watch hit at 0651 reading FEE3 = 10

15.387067: Mem Wr Watch hit at 065F writing FEE3 = 3C
15.387086: Mem Wr Watch hit at 065F writing FEE3 = FF
15.387105: Mem Wr Watch hit at 065F writing FEE3 = 7F
15.387124: Mem Wr Watch hit at 065F writing FEE3 = 00
15.387143: Mem Wr Watch hit at 065F writing FEE3 = 00
15.387162: Mem Wr Watch hit at 065F writing FEE3 = 00
15.387181: Mem Wr Watch hit at 065F writing FEE3 = 21
15.387200: Mem Wr Watch hit at 065F writing FEE3 = 00
15.387219: Mem Wr Watch hit at 065F writing FEE3 = 01
15.387238: Mem Wr Watch hit at 065F writing FEE3 = 57
15.387257: Mem Wr Watch hit at 065F writing FEE3 = 03
15.387276: Mem Wr Watch hit at 065F writing FEE3 = 00
15.387295: Mem Wr Watch hit at 065F writing FEE3 = 00
15.387314: Mem Wr Watch hit at 065F writing FEE3 = C3
15.387333: Mem Wr Watch hit at 065F writing FEE3 = 00
15.387352: Mem Wr Watch hit at 065F writing FEE3 = 00

15.392294: Mem Rd Watch hit at 004B reading FEE3 = 08
15.392318: Mem Rd Watch hit at 06CA reading FEE3 = 7F
15.392343: Mem Rd Watch hit at 0630 reading FEE3 = 10
15.392378: Mem Rd Watch hit at 063B reading FEE3 = 3C
15.392398: Mem Rd Watch hit at 063B reading FEE3 = FF
15.392418: Mem Rd Watch hit at 063B reading FEE3 = 7F
15.392438: Mem Rd Watch hit at 063B reading FEE3 = 00
15.392458: Mem Rd Watch hit at 063B reading FEE3 = 00
15.392485: Mem Rd Watch hit at 063B reading FEE3 = 00
15.392505: Mem Rd Watch hit at 063B reading FEE3 = 21
15.392525: Mem Rd Watch hit at 063B reading FEE3 = 00
15.392545: Mem Rd Watch hit at 063B reading FEE3 = 01
15.392565: Mem Rd Watch hit at 063B reading FEE3 = 57
15.392585: Mem Rd Watch hit at 063B reading FEE3 = 03
15.392612: Mem Rd Watch hit at 063B reading FEE3 = 00
15.392632: Mem Rd Watch hit at 063B reading FEE3 = 00
15.392652: Mem Rd Watch hit at 063B reading FEE3 = C3
15.392672: Mem Rd Watch hit at 063B reading FEE3 = 00
15.392692: Mem Rd Watch hit at 063B reading FEE3 = 00
15.393844: Mem Rd Watch hit at 0651 reading FEE3 = 10

15.393862: Mem Wr Watch hit at 065F writing FEE3 = 3C
15.393881: Mem Wr Watch hit at 065F writing FEE3 = FF
15.393900: Mem Wr Watch hit at 065F writing FEE3 = 7F
15.393919: Mem Wr Watch hit at 065F writing FEE3 = 00
15.393938: Mem Wr Watch hit at 065F writing FEE3 = 00
15.393957: Mem Wr Watch hit at 065F writing FEE3 = 00
15.393976: Mem Wr Watch hit at 065F writing FEE3 = 21
15.393995: Mem Wr Watch hit at 065F writing FEE3 = 00
15.394014: Mem Wr Watch hit at 065F writing FEE3 = 01
15.394033: Mem Wr Watch hit at 065F writing FEE3 = 57
15.394052: Mem Wr Watch hit at 065F writing FEE3 = 03
15.394071: Mem Wr Watch hit at 065F writing FEE3 = 00
15.394090: Mem Wr Watch hit at 065F writing FEE3 = 00
15.394109: Mem Wr Watch hit at 065F writing FEE3 = C3
15.394128: Mem Wr Watch hit at 065F writing FEE3 = 00
15.394147: Mem Wr Watch hit at 065F writing FEE3 = 00

15.399091: Mem Rd Watch hit at 004B reading FEE3 = 08
15.399115: Mem Rd Watch hit at 06CA reading FEE3 = 7F
15.399140: Mem Rd Watch hit at 0630 reading FEE3 = 10
15.399175: Mem Rd Watch hit at 063B reading FEE3 = 3C
15.399195: Mem Rd Watch hit at 063B reading FEE3 = FF
15.399215: Mem Rd Watch hit at 063B reading FEE3 = 7F
15.399235: Mem Rd Watch hit at 063B reading FEE3 = 00
15.399255: Mem Rd Watch hit at 063B reading FEE3 = 00
15.399275: Mem Rd Watch hit at 063B reading FEE3 = 00
15.399295: Mem Rd Watch hit at 063B reading FEE3 = 21
15.399315: Mem Rd Watch hit at 063B reading FEE3 = 00
15.399335: Mem Rd Watch hit at 063B reading FEE3 = 01
15.399362: Mem Rd Watch hit at 063B reading FEE3 = 57
15.399382: Mem Rd Watch hit at 063B reading FEE3 = 03
15.399402: Mem Rd Watch hit at 063B reading FEE3 = 00
15.399422: Mem Rd Watch hit at 063B reading FEE3 = 00
15.399442: Mem Rd Watch hit at 063B reading FEE3 = C3
15.399469: Mem Rd Watch hit at 063B reading FEE3 = 00
15.399489: Mem Rd Watch hit at 063B reading FEE3 = 00
15.400641: Mem Rd Watch hit at 0651 reading FEE3 = 10

15.400659: Mem Wr Watch hit at 065F writing FEE3 = 3C
15.400678: Mem Wr Watch hit at 065F writing FEE3 = FF
15.400697: Mem Wr Watch hit at 065F writing FEE3 = 7F
15.400716: Mem Wr Watch hit at 065F writing FEE3 = 00
15.400735: Mem Wr Watch hit at 065F writing FEE3 = 00
15.400754: Mem Wr Watch hit at 065F writing FEE3 = 00
15.400773: Mem Wr Watch hit at 065F writing FEE3 = 21
15.400792: Mem Wr Watch hit at 065F writing FEE3 = 00
15.400811: Mem Wr Watch hit at 065F writing FEE3 = 01
15.400830: Mem Wr Watch hit at 065F writing FEE3 = 57
15.400849: Mem Wr Watch hit at 065F writing FEE3 = 03
15.400868: Mem Wr Watch hit at 065F writing FEE3 = 00
15.400887: Mem Wr Watch hit at 065F writing FEE3 = 00
15.400906: Mem Wr Watch hit at 065F writing FEE3 = C3
15.400925: Mem Wr Watch hit at 065F writing FEE3 = 00
15.400944: Mem Wr Watch hit at 065F writing FEE3 = 00

15.405698: Mem Rd Watch hit at 004B reading FEE3 = 08
15.405722: Mem Rd Watch hit at 06CA reading FEE3 = 7F
15.405747: Mem Rd Watch hit at 0630 reading FEE3 = 10
15.405782: Mem Rd Watch hit at 063B reading FEE3 = 3C
15.405802: Mem Rd Watch hit at 063B reading FEE3 = FF
15.405822: Mem Rd Watch hit at 063B reading FEE3 = 7F
15.405842: Mem Rd Watch hit at 063B reading FEE3 = 00
15.405862: Mem Rd Watch hit at 063B reading FEE3 = 00
15.405882: Mem Rd Watch hit at 063B reading FEE3 = 00
15.405902: Mem Rd Watch hit at 063B reading FEE3 = 21
15.405922: Mem Rd Watch hit at 063B reading FEE3 = 00
15.405949: Mem Rd Watch hit at 063B reading FEE3 = 01
15.405969: Mem Rd Watch hit at 063B reading FEE3 = 57
15.405989: Mem Rd Watch hit at 063B reading FEE3 = 03
15.406009: Mem Rd Watch hit at 063B reading FEE3 = 00
15.406029: Mem Rd Watch hit at 063B reading FEE3 = 00
15.406056: Mem Rd Watch hit at 063B reading FEE3 = C3
15.406076: Mem Rd Watch hit at 063B reading FEE3 = 00
15.406096: Mem Rd Watch hit at 063B reading FEE3 = 00
15.407248: Mem Rd Watch hit at 0651 reading FEE3 = 10
It seems like the FLEX boot strap is for some reason repeatedly re-issuing the same OSWORD 7F.

Dave

User avatar
hoglet
Posts: 8830
Joined: Sat Oct 13, 2012 6:21 pm
Location: Bristol
Contact:

Re: Matchbox sized 6502 / Z80 / 6809 Co Pro

Post by hoglet » Tue Nov 17, 2015 11:49 am

Hi Jonathan,

There is something weird about RamFS 1.01.

I have the following ROMs in a Model B:
- 0F Basic II (disabled)
- 0B RAM Master (disabled)
- 0A Acorn ADFS 1.33 (disabled)
- 08 RamFS 1.01
- 07 RamFS 1.00
- 03 DFS 2.26
- 02 ADE (disabled)

RAM Master is a ROM manager (amongst other things) that I wrote in the '80s which allows you to enable/disable ROMs.

Anyway, if the following configuration works, and allows me to boot FLEX off DFS:
- 07 RamFS 1.00
- 03 DFS 2.26

Code: Select all

6809 TUBE 64K 1.00

RetroClinic RamFS

6809>*DISK
6809>*FLEX

6809 FLEX V3.01

DATE (MM,DD,YY)? 17,11,15

+++
If I switch to RamFS 1.01, it just hangs.
- 08 RamFS 1.01
- 03 DFS 2.26

Code: Select all

6809 TUBE 64K 1.00

RetroClinic RamFS

6809>*DISK
6809>*FLEX
Now, unfortunately I can't currently debug this with the ICE, because when I use it the Disk Drive stops working - too much bus load I guess from the GODIL pullups. I'll have a think to see if there is any more data I can get.

Dave

User avatar
jgharston
Posts: 3802
Joined: Thu Sep 24, 2009 11:22 am
Location: Whitby/Sheffield
Contact:

Re: Matchbox sized 6502 / Z80 / 6809 Co Pro

Post by jgharston » Tue Nov 17, 2015 4:07 pm

hoglet wrote:Hi Jonathan,
There is something weird about RamFS 1.01.
...
I'll investigate when I get home sometime later today. At least we've isolated the problem to RamFS and not the Tube client.

Code: Select all

$ bbcbasic
PDP11 BBC BASIC IV Version 0.25
(C) Copyright J.G.Harston 1989,2005-2015
>_

User avatar
jgharston
Posts: 3802
Joined: Thu Sep 24, 2009 11:22 am
Location: Whitby/Sheffield
Contact:

Re: Matchbox sized 6502 / Z80 / 6809 Co Pro

Post by jgharston » Wed Nov 18, 2015 12:32 am

hoglet wrote:If I switch to RamFS 1.01, it just hangs.
- 08 RamFS 1.01
- 03 DFS 2.26

Code: Select all

6809 TUBE 64K 1.00
RetroClinic RamFS
6809>*DISK
6809>*FLEX
Doing the same test with a Z80 CoPro and a CP/M disk image on RAM drive 0 I get the same problem:

Code: Select all

ACORN TUBE Z80 64K 1.20
RetroClinic RAMFS
BASIC
(hangs)
Press Break, type *CPM, same thing happens.

However, doing *DTRAP then Ctrl-Break boots straight into CP/M.

Doing *DTRAP again, then pressing Ctrl-Break goes back to hanging. However, I can't boot from a physical floppy, with *DTRAP off OSWORD &7F should be ignored by RamFS and be picked up by DFS, as you're seeing with RamFS 1.00.[/s]

Edit: Doh! I actually had my floppy drive power plug unplugged! Ignore the above.

Code: Select all

$ bbcbasic
PDP11 BBC BASIC IV Version 0.25
(C) Copyright J.G.Harston 1989,2005-2015
>_

User avatar
jgharston
Posts: 3802
Joined: Thu Sep 24, 2009 11:22 am
Location: Whitby/Sheffield
Contact:

Re: Matchbox sized 6502 / Z80 / 6809 Co Pro

Post by jgharston » Wed Nov 18, 2015 12:55 am

Testing with a Z80 CoPro and a CP/M disk image on RAM drive 0 and a CP/M floppy in disk drive 0 I get:

Code: Select all

Ctrl-Break
ACORN TUBE Z80 64K 1.20
Acorn 1770 DFS
BASIC
(chug chug floppy light on) (clear screen)
Acorn CP/M 2.2 - BIOS 1.20
A>
Doing *DTRAP again, then pressing Ctrl-Break boots from the RAM disk:

Code: Select all

Ctrl-Break
ACORN TUBE Z80 64K 1.20
RetroClinic RamFS (DT)
BASIC
(clear screen)
Acorn CP/M 2.2 - BIOS 1.20
A>
It could be the problem in the *FLEX bootstrap you mentioned earlier.

This is with a BBC Master with:
12 BASIC (config. lang 12)
9 DFS (config. file 9)
2 RamFS 1.01
1 ADFS 1.53
everything else unplugged. I'll try swapping RamFS and DFS around so they're in the same order as yours.

Code: Select all

$ bbcbasic
PDP11 BBC BASIC IV Version 0.25
(C) Copyright J.G.Harston 1989,2005-2015
>_

User avatar
jgharston
Posts: 3802
Joined: Thu Sep 24, 2009 11:22 am
Location: Whitby/Sheffield
Contact:

Re: Matchbox sized 6502 / Z80 / 6809 Co Pro

Post by jgharston » Wed Nov 18, 2015 1:32 am

jgharston wrote:I'll try swapping RamFS and DFS around so they're in the same order as yours.
Swapping DFS and RamFS around resulted in me never accessing the floppy drive regardless of the DTRAP state. I realised I'd left a debug NOP'd out test in place. Removing it now results in *DTRAP off booting from floppy and *DTRAP on booting from RAM drive, regardless what ROM sockets DFS and RamFS are in.

I think it's time for bed.

Code: Select all

$ bbcbasic
PDP11 BBC BASIC IV Version 0.25
(C) Copyright J.G.Harston 1989,2005-2015
>_

User avatar
hoglet
Posts: 8830
Joined: Sat Oct 13, 2012 6:21 pm
Location: Bristol
Contact:

Re: Matchbox sized 6502 / Z80 / 6809 Co Pro

Post by hoglet » Wed Nov 18, 2015 7:00 pm

jgharston wrote:
jgharston wrote:I'll try swapping RamFS and DFS around so they're in the same order as yours.
Swapping DFS and RamFS around resulted in me never accessing the floppy drive regardless of the DTRAP state. I realised I'd left a debug NOP'd out test in place. Removing it now results in *DTRAP off booting from floppy and *DTRAP on booting from RAM drive, regardless what ROM sockets DFS and RamFS are in.
Does that explain the difference I was observing between RamFS 1.00 and RamFS 1.01?

Dave

User avatar
jgharston
Posts: 3802
Joined: Thu Sep 24, 2009 11:22 am
Location: Whitby/Sheffield
Contact:

Re: Matchbox sized 6502 / Z80 / 6809 Co Pro

Post by jgharston » Wed Nov 18, 2015 11:26 pm

hoglet wrote:
jgharston wrote:...Removing it now results in *DTRAP off booting from floppy and *DTRAP on booting from RAM drive, regardless what ROM sockets DFS and RamFS are in.
Does that explain the difference I was observing between RamFS 1.00 and RamFS 1.01?
Probably. I'll know for sure when I get my Matchbox updated with the latest build so I can have a "real" live 6809 in front of me.

Code: Select all

$ bbcbasic
PDP11 BBC BASIC IV Version 0.25
(C) Copyright J.G.Harston 1989,2005-2015
>_

User avatar
fordp
Posts: 1036
Joined: Sun Feb 12, 2012 9:08 pm
Location: Kent, England
Contact:

Co Pro on the Electron

Post by fordp » Wed Nov 25, 2015 1:23 pm

I have been reading this thread over the last week, interesting ...

After reading this thread I know that Dave would like to get the Co Pro's working on the Electron. This gave me the impression that Co Pro's had never been run on the Electron before.

Today I was reading about the "Electron AP5" which had a "Tube" port and allowed the connection of Second Processors from 1986.

Is this not a good way to do it no or was the AP5 Second Processor capability more vapour-ware than hardware?

Cheers.

FordP
FordP (Simon Ellwood)
Time is an illusion. Lunchtime, doubly so!

User avatar
hoglet
Posts: 8830
Joined: Sat Oct 13, 2012 6:21 pm
Location: Bristol
Contact:

Re: Co Pro on the Electron

Post by hoglet » Wed Nov 25, 2015 1:57 pm

fordp wrote: After reading this thread I know that Dave would like to get the Co Pro's working on the Electron. This gave me the impression that Co Pro's had never been run on the Electron before.
Actually, you might be confusing the Atom and the Electron.

I think the Matchbox board just works as-is in the electron, with a the AP5.

It's the Atom that is an earlier machine, so was/is more of a challenge. See this thread for more:
viewtopic.php?f=44&t=10090

And yes, I think I'm crazy as well :lol:

Dave

User avatar
danielj
Posts: 7783
Joined: Thu Oct 02, 2008 4:51 pm
Location: Manchester
Contact:

Re: Matchbox sized 6502 / Z80 / 6809 Co Pro

Post by danielj » Wed Nov 25, 2015 3:31 pm

If it is the elk you're interested in, it works fine - you can use an AP5 (if you can find one!) or Dave Hitchens has produced a Tube interface for it (you'll still need a Plus 1/Rombox Plus):

viewtopic.php?f=3&t=5588

d.

User avatar
1024MAK
Posts: 9608
Joined: Mon Apr 18, 2011 4:46 pm
Location: Looking forward to summer in Somerset, UK...
Contact:

Re: Matchbox sized 6502 / Z80 / 6809 Co Pro

Post by 1024MAK » Wed Nov 25, 2015 11:32 pm

Err, yes, the Elk does work okay with a second processor. This is me doing some testing with an Acorn 6502 second processor :D

As said above, I think that you are thinking about efforts to get an Atom to work with a second processor :mrgreen:

Mark

User avatar
flynnjs
Posts: 830
Joined: Tue Jul 06, 2010 9:33 pm
Contact:

Re: Matchbox sized 6502 / Z80 / 6809 Co Pro

Post by flynnjs » Tue Dec 22, 2015 8:06 pm

For those taking receipt of a CoPro, it might be worth noting that
it is possible for the board to touch the keyboard screw if mounted
directly on a B and therefore a bit of tape can prevent shorting out
and odd behaviour/damage.

It's early days yet to see if this batch behaves any differently to the
previous but it should be better behaved with more decoupling built
in from day one. However if anyone experiences technical problems,
hang in there and we'll sort them out in due course.... I think we
got everyone up and running on the last batch and I'll aim to on this
one too.

User avatar
danielj
Posts: 7783
Joined: Thu Oct 02, 2008 4:51 pm
Location: Manchester
Contact:

Re: Matchbox sized 6502 / Z80 / 6809 Co Pro

Post by danielj » Wed Dec 23, 2015 3:59 pm

Received :D - thanks Jason. Seems to be working fine now, however initial boot on my master (w/external data centre) was a bit odd. It really didn't want to play. Garbled startup messages and random hanging. A few ctrl-breaks and it started behaving. I'll give it another go later on and report back...

User avatar
jonb
Posts: 2584
Joined: Sat May 21, 2011 12:42 pm
Location: South Coast of England
Contact:

Re: Matchbox sized 6502 / Z80 / 6809 Co Pro

Post by jonb » Wed Dec 23, 2015 7:32 pm

I got it and it's showing on the boot screen as a 65C102 co processor.

A few oddities, though.

Only a single beep on boot and the sound chip does not seem to be working .
Turbo MMC working OK
I have a sideways RAM which is misbehaving, though the battery might need swapping. However it's not necessarily causing the problem as the machine is fine without the co pro fitted.
The STH menu / archive I have on this MMC doesn't run (says "Tube on"!) so I can't load and run Tube Elite yet.

Cheers
JonB

User avatar
danielj
Posts: 7783
Joined: Thu Oct 02, 2008 4:51 pm
Location: Manchester
Contact:

Re: Matchbox sized 6502 / Z80 / 6809 Co Pro

Post by danielj » Wed Dec 23, 2015 7:47 pm

Single beep is normal with the co-pro installed on a B.

d.

User avatar
DutchAcorn
Posts: 2148
Joined: Fri Mar 21, 2014 9:56 am
Location: Maarn, Netherlands
Contact:

Re: Matchbox sized 6502 / Z80 / 6809 Co Pro

Post by DutchAcorn » Wed Dec 23, 2015 7:59 pm

jonb wrote:...Only a single beep on boot ...
That's the correct behaviour.
jonb wrote:...and the sound chip does not seem to be working..
A beep without a working sound chip? Please elaborate! :?
jonb wrote:...I have a sideways RAM which is misbehaving, though the battery might need swapping. However it's not necessarily causing the problem as the machine is fine without the co pro fitted...
What does it (not) do? The memory map is different using the copro so it may have something to do with that.
jonb wrote: The STH menu / archive I have on this MMC doesn't run (says "Tube on"!) so I can't load and run Tube Elite yet.
Yes, it does not work with the copro active. You can use *din <image name/number> to select the right image and then use shift-break to boot Elite.

I don't remember what image name Elite has in the standard beeb.mmc file but you can find out the lazy way by using the STH menu to start Elite, immediately press escape and use *cat to see the disc title. Use that in your *din command to select it (with the copro active).
Paul

Image

User avatar
hoglet
Posts: 8830
Joined: Sat Oct 13, 2012 6:21 pm
Location: Bristol
Contact:

Re: Matchbox sized 6502 / Z80 / 6809 Co Pro

Post by hoglet » Wed Dec 23, 2015 8:01 pm

jonb wrote: The STH menu / archive I have on this MMC doesn't run (says "Tube on"!) so I can't load and run Tube Elite yet.
Try:

Code: Select all

*DIN 45
*TUBEELT
Dave

User avatar
jonb
Posts: 2584
Joined: Sat May 21, 2011 12:42 pm
Location: South Coast of England
Contact:

Re: Matchbox sized 6502 / Z80 / 6809 Co Pro

Post by jonb » Wed Dec 23, 2015 8:33 pm

@Paul: It's a BASIC program loaded from the MMC with a SOUND command.

No sound... but with the co-pro out, it works.

Glad the single beep is normal. But - correct me if I'm wrong - it is caused by the boot process, not a specific instruction to the sound chip that says "play this beep", so I think it beeping on boot doesn't prove the co-pro and sound chip are misbehaving. There is certainly something wrong.

The Sideways RAM is a Sprow model and I say it's playing up because there is nothing when I type *HELP. However, I have to try some other commands here before calling it out properly.

@Dave: Thanks, I'll try that. Not that I'm any good at BBC Elite, I used to play it on the Spectrum back then. Pretty sure I got to "Deadly". :D

User avatar
TheCorfiot
Posts: 671
Joined: Mon Jan 08, 2007 5:22 pm
Contact:

Re: Matchbox sized 6502 / Z80 / 6809 Co Pro

Post by TheCorfiot » Thu Dec 24, 2015 11:41 am

Got my copros from Jason yesterday and they work great...68K mode looks promising .

So, i decided to upgrade my existing copros to the current version but ended up with 2 non functioning copros.
reflashed the previous version and all was fine.

Can someone please confirm the current build we should be using, maybe Jason can tell us what firmware he is shipping with.

Merry Christmas all
:)

User avatar
hoglet
Posts: 8830
Joined: Sat Oct 13, 2012 6:21 pm
Location: Bristol
Contact:

Re: Matchbox sized 6502 / Z80 / 6809 Co Pro

Post by hoglet » Thu Dec 24, 2015 12:26 pm

Hi Bas,
TheCorfiot wrote:Got my copros from Jason yesterday and they work great...68K mode looks promising .

So, i decided to upgrade my existing copros to the current version but ended up with 2 non functioning copros.
reflashed the previous version and all was fine.

Can someone please confirm the current build we should be using, maybe Jason can tell us what firmware he is shipping with.
This is the firmware Jason is using in the second batch:
LX9CoProCombined_20151215_1004_dmb.zip
(1.53 MiB) Downloaded 41 times
It fixes a configuration bug in LX9CoProCombined_20151115_1858_dmb that is probably why your two other boards became non-functional. For some reason, this bug didn't affect my board. Give this version a try and report back when you get a chance.

Dave

User avatar
jgharston
Posts: 3802
Joined: Thu Sep 24, 2009 11:22 am
Location: Whitby/Sheffield
Contact:

Re: Matchbox sized 6502 / Z80 / 6809 Co Pro

Post by jgharston » Thu Dec 24, 2015 12:59 pm

jonb wrote:The Sideways RAM is a Sprow model and I say it's playing up because there is nothing when I type *HELP. However, I have to try some other commands here before calling it out properly.
If there's nothing in the sideways RAM, then there's nothing to respond to *HELP, so what you are seeing is correct operation.
There are SROM/SRAM tools on ROMS1.zip ROMS1.ssd. The *ROMS command on the disk lists if a bank is ROM or writable RAM.

Code: Select all

$ bbcbasic
PDP11 BBC BASIC IV Version 0.25
(C) Copyright J.G.Harston 1989,2005-2015
>_

Post Reply