Cube Central
10 REM *** PROGRAM: MODCHK4.BAS 20 REM *** CUBECENTRAL LABS 2018 30 REM ***SETUP*** 40 Randomize 50 MAX=32766 : REM Set the maximum value for the integers to test 60 REM ***BEGIN LOOP*** 70 B=Int(Rnd*MAX)+1 : REM Create a pair of integers 80 A=Int(Rnd*MAX)+1 90 X=X+1 : REM simply a counter 100 C=A Mod B : REM the problem statement. C should be the "remainder" of when A is divided by B 110 Q=Int(A/B) : REM begins the alternate computation of the modulus, taking just the integer part of the division 120 P=Q*B : REM The result of the previous division is then multiplied by the divisor 130 M=A-P : REM the resulting subtraction of the dividend from the previous multiplication is the "remainder" or modulus 140 D=M : REM simply setting M to D to keep with naming convention 150 If Len(INKEY$) Then Print "CHECK: A=";A;" B=";B;" C=";C;" D=";D;" X=";X : REM print a status when a key is pressed 160 If C<>D Then GOSUB 200 : REM In theory, C should ALWAYS equal D. Always. 170 B=0 : C=0 : D=0 : Q=0 : P=0 : M=0 : REM Set the variables used back to zero, just in case 180 Goto 60 : REM Loop the program forever 190 End 200 REM ***ERROR*** The program should never get here, unless the modulus was computed wrong. 210 REM 220 Print "ERROR! A=";A;" B=";B;" C=";C;" D=";D;" X=";X : REM Show the values of the variables 230 REM STOP 240 Return
Cube Central
Chris Scullion
Cube Central
Stephan van Radecke
Jon Langseth
Stephan van Radecke
Jon Langseth
Jon Langseth
CubeCentral
Just to be clear, line 150, the “INKEY” line, only checks to see if the user has pressed a key, and if so, print a status report. Otherwise it continues to run by itself, there is no need to press a key. That was simply put in there so that I could check on the system to see if it was still running and not to print out the results of every passed test. Printing every line slowed the program and I didn’t care about successful comparisons, only the failures.
--
You received this message because you are subscribed to the Google Groups "LiNC80" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linc80+un...@googlegroups.com.
To post to this group, send email to lin...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/linc80/f09a682f-7a43-42df-8525-49924c5ebfbb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
CubeCentral
I just tied a version of the MODCHK5 program in ROM BASIC (selecting “basic” from the initial load screen) and there isn’t a modulus operator (A MOD B) in this version of BASIC. Without it, this test is useless. So much for testing it without a IDE/CF adapter.
-Randal (at CubeCentral)
From: lin...@googlegroups.com [mailto:lin...@googlegroups.com] On Behalf Of Cube Central
Sent: Tuesday, May 29, 2018 11:16
To: LiNC80 <lin...@googlegroups.com>
Subject: [linc80] Re: Modulus Madness
Hi Chris, thank you for running that!
--
You received this message because you are subscribed to the Google Groups "LiNC80" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linc80+un...@googlegroups.com.
To post to this group, send email to lin...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/linc80/0563f428-34fb-4f87-92dd-34d7ab4d8c75%40googlegroups.com.
Cube Central
Jon Langseth
OK, I now ran it for about 10 minutes with constant input (keyboard repeat <3) without issues. As I need to use the PC for other things,I have put a REM at line 150, and I'm now running it "background" to see if the error triggers.
Jon Langseth
On Wednesday, May 30, 2018 at 1:31:21 AM UTC+2, Cube Central wrote:
Just to clarify, so I understand. When I boot my LiNC80 SBC1 I can go into ROM BASIC like so:*BASICMemory top?Z80 BASIC Ver 4.7bCopyright (C) 1978 by Microsoft47811 Bytes freeOkI found a PDF for the manual this version of ROM BASIC is based upon, and there is no mention of a MOD operator (or INKEY$)
There is two copies of Nascom ROM BASIC from Microsoft in ROM, one SCMon-launched via the BASIC keyword, and one that can be started via GSL.
Both are based on the 80-BUS code adapted by Grant Searle, as per the source code at https://github.com/linc80/z80sbcFiles/blob/master/source/basic.asm
Randal is correct about the MOD and INKEY$ statements not being implemented in this version of BASIC.
The link to Philip's copy of the manual is also correct. I should probably host a copy of that as well :)
Oh, and ... I'll cross-copy a bit, as this should probably be in the other thread....
Stephan van Radecke
Stephan van Radecke
Jon Langseth
CubeCentral
Jon –
I would be happy to give a different power supply a try. I have always used the same power supply for all the testing I’ve done. As the power input to the computer is the screw terminals, where would you suggest placing the ferrite choke?
I am using a lab bench power supply at 10V going into something similar to this: https://www.sparkfun.com/products/114 … Which puts out a very nice, steady 5V, with little to no ripple that I could see on the scope. I wanted to use a regulated supply like this rather than straight from the bench power supply as this has reverse polarity and overcurrent protection. This is the same supply that I used to drive IDE/CF adapter cards requiring external power. I also used this same supply on the RC2014 before installing the on-board regulator.
The next step in my testing was going to be switching power supplies, and seeing if the problem persists, so this post is timely.
Please specify the test parameters and what you would like to see and I will make it happen here later today. Cheers!
-Randal (at CubeCentral)
From: lin...@googlegroups.com [mailto:lin...@googlegroups.com] On Behalf Of Jon Langseth
Sent: Wednesday, May 30, 2018 08:11
To: LiNC80 <lin...@googlegroups.com>
Subject: [linc80] Re: Modulus Madness
That does seem to correlate with my suspicion that this is noise or power-supply induced, but that makes me just as confused about why Steve's build is experiencing errors when it hasn't done so before :(
--
You received this message because you are subscribed to the Google Groups "LiNC80" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linc80+un...@googlegroups.com.
To post to this group, send email to lin...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/linc80/d5e6cd5e-9277-48e0-863d-cb162f2181e7%40googlegroups.com.
Jon Langseth
Where to place the choke? On the cable feeding power in to the board, reasonably (1-3inches) close to the board. I used an oversized ferrite core as an example choke here. If you have a choke of the clip-on type, even better than my example.
Cube Central
I can't begin tests right now, maybe this afternoon or tomorrow if this setup looks OK. I have more of these chokes and can add them on the Bench Power Supply, the Power Adapter, etc. if they aren't already on there!
Jon Langseth
Stephan van Radecke
Jon Langseth
Stephan van Radecke
CubeCentral
Stephan,
20 hours is pretty good! A single memory glitch like that might happen due to a cosmic ray strike. Since this memory isn’t error correcting ECC RAM it is susceptible to interference. If you live at higher altitude, the problem is worse than for those near sea level.
Stay tuned for a post detailing my testing results, which I hope to post later today. Cheers!
-Randal (at CubeCentral)
--
You received this message because you are subscribed to the Google Groups "LiNC80" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linc80+un...@googlegroups.com.
To post to this group, send email to lin...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/linc80/4d984499-cbe9-486a-8b77-c70190cca8d6%40googlegroups.com.
Jon Langseth
Derry UK
CubeCentral
Hi Derry,
If you’re trying to run the MODCHK program, it won’t look like it is doing anything unless you press a key. Would you try that and let me know?
I’m afraid I disagree with you about it not being power supplies. All the testing I’ve done seems to indicate that the power supply is – if not the root cause – a major factor in the failures. All things left the same, the only variable which changed was the power supply which lead to much better outcomes.
And I agree that the cable issue is a puzzle. Right now, I am doing some tests involving the direct-connect IDE CF adapters. As soon as more time has passed I will update my post with the results later today.
I do agree that the failures are seemingly random, as they are not reproduceable by the usual means.
The problem with running the test without a CF card is that one would have to use the supplied ROM BASIC to run the test program. Unfortunately, the version of BASIC on the ROM doesn’t support the MOD operator used in the tests. I’ve considered using a “spinning rust” hard drive, but would need some way to place the CP/M image on it. I purchased an IDE/USB adapter for this purpose but haven’t yet had the opportunity to try it out. When I do, I will for sure post an update.
Thanks for your input and please do let me know if I can help with running the MODCHK test program. Cheers!
-Randal (at CubeCentral)
From: lin...@googlegroups.com [mailto:lin...@googlegroups.com] On Behalf Of Derry UK
Sent: Sunday, June 3, 2018 09:26
To: LiNC80 <lin...@googlegroups.com>
Subject: Re: [linc80] Re: Modulus Madness
I wish I was able to run the basic program and test my system but sadly I do not know how too. Just download and run this basic program leaves me blank at the moment.
--
You received this message because you are subscribed to the Google Groups "LiNC80" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linc80+un...@googlegroups.com.
To post to this group, send email to lin...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/linc80/527e425a-cae8-463e-81ba-d168b6a59b84%40googlegroups.com.
Jon Langseth
And I agree that the cable issue is a puzzle. Right now, I am doing some tests involving the direct-connect IDE CF adapters. As soon as more time has passed I will update my post with the results later today.
The problem with running the test without a CF card is that one would have to use the supplied ROM BASIC to run the test program. Unfortunately, the version of BASIC on the ROM doesn’t support the MOD operator used in the tests. I’ve considered using a “spinning rust” hard drive, but would need some way to place the CP/M image on it. I purchased an IDE/USB adapter for this purpose but haven’t yet had the opportunity to try it out. When I do, I will for sure post an update.
Derry UK
Derry UK
Cube Central
Derry,
Not to worry, it happens to the best of us!
I’ve not tried different ICs on my board, but would be willing to do so if I knew exactly what other ICs to put in there. Unfortunately, that’s where my experience and knowledge falls a bit short, and would be terrified of guessing. If a Bill of Materials were put together with alternate ICs, I would gladly order them from Mouser or Digi-Key.
Attached, please find MODCHK5.BAS. This one differs from MODCHK4.BAS in that instead of trying random combinations of numbers, it instead loops through integers from 1 to some maximum (set by variable to 32766). This is the one that I’ve been using most recently.
On a related note, I’ve been using the MODCHK program – as you’ve all seen - to weed out what appear to be noise issues, coming from either the Power Supply or the IDE/CF Card Adapter. If this program runs for a good long while without errors, I then move to the more data-intensive “Media Mayhem” program, MM8.BAS (also attached) to determine if the IDE/CF bus and adapter are working well. I’ve found that if the MODCHK program generates errors, then the MM program is sure to fail. The MODCHK program was created due to bizarre errors encountered by earlier MM programs, which used the MOD operator (and the STRING$ function) to generate data to move back and forth from the CF card. I had made an earlier claim about the STRING$ function also not working properly, but I’ve yet to create a program just to test for it (as I did the MODCHK program) – I may do that later this week.
I look forward to seeing what PCB you’ve created and do please let me know if you have any further questions, concerns, or suggestions. Cheers!
-Randal (at CubeCentral)
Derry UK
Well see.
CubeCentral
I saw this posted on the RC2014 group, and thought that it might be of use to you since you said you write Z80 assembler:
https://smallcomputercentral.com/projects/small-computer-workshop/
I’ve played with it some and it looks very full featured, but might be finicky as it is homebrew software. I hope it can help?
-Randal (at CubeCentral)
From: lin...@googlegroups.com [mailto:lin...@googlegroups.com] On Behalf Of Derry UK
Sent: Tuesday, June 5, 2018 04:14
To: LiNC80 <lin...@googlegroups.com>
Subject: Re: [linc80] Re: Modulus Madness
Randal I was just thinking in terms of trying another IC of the same type - just to eliminate the possibility of a flaky IC on your board.
--
You received this message because you are subscribed to the Google Groups "LiNC80" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linc80+un...@googlegroups.com.
To post to this group, send email to lin...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/linc80/fec206f7-5dd5-4c77-bf90-674f209ddbac%40googlegroups.com.
Derry UK
Random number seed (-32768 to 32767)? 999
CHECK: A= 620 B= 1 C= 0 D= 0 X= 620 Y= 32766
CHECK: A= 905 B= 1 C= 0 D= 0 X= 905 Y= 32766
CHECK: A= 1289 B= 1 C= 0 D= 0 X= 1289 Y= 32766
CHECK: A= 1574 B= 1 C= 0 D= 0 X= 1574 Y= 32766
ERROR A= 4856 B= 1 C= 0 D= 8 X= 4856 Y= 32766
CubeCentral
Derry,
Yup, and early on as well. The program had just started and was 4856th iteration of the first loop (B=1). Interestingly, the MOD operator returned the correct value (C=0) but the alternative calculation returned the wrong answer! (D=8).
If you have some time I sure would appreciate you running this a bit longer on your system … either a few hours or five or so errors? I just want to see if the errors are similar to what I get. Thanks!
To view this discussion on the web visit https://groups.google.com/d/msgid/linc80/bb178354-2a23-4a6b-898f-5bc536e894a2%40googlegroups.com.
Derry UK
BASIC-80 Rev. 5.21
[CP/M Version]
Copyright 1977-1981 (C) by Microsoft
Created: 28-Jul-81
29752 Bytes free
CHECK: A= 276 B= 1 C= 0 D= 0 X= 276 Y= 32766
ERROR A= 488 B= 1 C= 0 D= 0 X= 488 Y= 32766
ERROR A= 846 B= 1 C= 0 D= 0 X= 846 Y= 32766
CHECK: A= 4835 B= 1 C= 0 D= 0 X= 4835 Y= 32766
ERROR A= 5753 B= 1 C= 0 D= 0 X= 5753 Y= 32766
ERROR A= 5822 B= 1 C= 0 D= 0 X= 5822 Y= 32766
CHECK: A= 7248 B= 1 C= 0 D= 0 X= 7248 Y= 32766
ERROR A= 8319 B= 1 C= 0 D= 0 X= 8319 Y= 32766
ERROR A= 14403 B= 1 C= 0 D= 0 X= 14403 Y= 32766
CHECK: A= 23624 B= 1 C= 0 D= 0 X= 23624 Y= 32766
ERROR A= 29910 B= 1 C= 0 D= 0 X= 29910 Y= 32766
Derry.
CubeCentral
Derry,
I’m sure your BASIC is fine, getting random nonsensical errors is a part of the issue. It is probably a memory location getting randomly changed by the same process that causes the MOD operation to report incorrect values.
Looking at your output now, maybe I see what you are thinking, where C and D are both equal to zero.
I’ve found that this could be BASIC reporting a very small floating point value (I do not wish to get into a discussion of floating point arithmetic here, it’s beyond the scope of the Group, but here are a couple of links)
In either case, the error is valid because if C and D are actually zero, then the comparison of C=D should be true. In the program, an error is reported if C doesn’t equal D.
I would review the program (using LIST in BASIC) and visually compare it to a known good copy to be sure that the program is intact and didn’t get altered when transferred to the SBC1.
(Not sure if you know enough BASIC to do this, but you would start in CPM, load BASIC by typing MBASIC, once there you can “LOAD x:MODCHK5.BAS” where x: is the drive letter. Once loaded you can issue a “LIST” command to view the program.
Please let me know if you have any further questions or concerns, as I am happy to help!! Cheers!
-Randal (at CubeCentral)
From: lin...@googlegroups.com [mailto:lin...@googlegroups.com] On Behalf Of Derry UK
Sent: Tuesday, June 5, 2018 08:56
To: LiNC80 <lin...@googlegroups.com>
Subject: Re: [linc80] Re: Modulus Madness
At the moment I am beginning to think my basic is at fault. I am now getting errors reported where there are none! However I was poking about with my scope probe at the time...........
--
You received this message because you are subscribed to the Google Groups "LiNC80" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linc80+un...@googlegroups.com.
To post to this group, send email to lin...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/linc80/a97d45e5-4dc2-484b-9cee-2a18f503f069%40googlegroups.com.
Derry UK
Jon Langseth
CubeCentral
The real trick would be to see if one of these pulses syncs up with an error in MODCHK.
Unfortunately, I don’t have a scope with dual triggers that would allow me to view a pulse over some limit, but under another. Will have to play around a bit and see if I can find another way of viewing these interim “runt” pulses.
Would it really cause an issue if the voltage is 0.9V below the lower threshold? I’ve been reading some and came across this page which talks about logic signal voltage levels and I’m just not sure a pulse at 1.2V would be outside the noise margin for the gates.
Keep up your investigations, Derry, I am also interested in your findings! Cheers!
-Randal (at CubeCentral)
PS: Jon, you’re not weird.
From: lin...@googlegroups.com [mailto:lin...@googlegroups.com] On Behalf Of Jon Langseth
Sent: Tuesday, June 5, 2018 15:20
To: LiNC80 <lin...@googlegroups.com>
Subject: Re: [linc80] Re: Modulus Madness
I may be weird, but seeing your 'scope-trace made me really excited.
--
You received this message because you are subscribed to the Google Groups "LiNC80" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linc80+un...@googlegroups.com.
To post to this group, send email to lin...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/linc80/81bf12fe-3bac-4600-9ce0-6cb86bc91a5e%40googlegroups.com.
Cube Central
The first photo includes the scope "cursor" function which allows me to measure portions of a waveform. I noted that the maximum value is around 600mV.
The second photo is the same shot but without the cursors.
Derry UK
Cube Central
The blue trace is from D0 and the yellow is from D1. It feels to me as if the "bumps" or "runts" that are observed at the very small voltages could simply be from neighboring data lines. The following snapshots may illustrate that:
With the U1 power supply:
With the W1 power supply:
Derry UK
Derry UK
Derry.
Derry UK
Derry.
CubeCentral
Derry,
Thanks for the follow up. I’ve learned the hard way to double check my oscilloscope results, especially if I see something out of the ordinary. So many small variables, like an IC clip, or using a bit longer length of wire, can add up!
You pose an excellent question about where the error might be occurring. I don’t know for sure, but I can infer a bit from the test program results. I first was thinking maybe it was RAM, but I modified the MODCHK program to immediately do the calculation again after encountering an error, and the results are always the correct value. If it were RAM, and somehow a variable was stored or retrieved incorrectly, then doing an operation on that memory location (i.e. variable) would repeatedly give the same error, or at least another incorrect value. Also, sometimes the program will stop with a nonsensical “Syntax Error” on a line that has been executed millions of times before, but if I view that line in the program, all is as it should be. If it were RAM then that program line would be mangled.
As you said, the path between does seem to be the most likely suspect. I think we could rule out the CPU as it is ROM, and an older, well proven architecture. It there was an issue with the CPU I think we would see it in the form of more repeatable errors or more serious ones (including perhaps system hangs). Having data somehow become corrupt somewhere between the RAM and CPU or RAM and other RAM could account for the types of issues we are seeing. Changing the power supplies, thus changing the “noise profile”, would certainly influence the communication paths. This is all my best guess, as I have no direct proof one way or the other.
Hope that helps and if anyone disagrees, please do let me know – I’m always eager to learn something new! Cheers!
-Randal (at CubeCentral)
From: lin...@googlegroups.com [mailto:lin...@googlegroups.com] On Behalf Of Derry UK
Sent: Wednesday, June 6, 2018 04:27
To: LiNC80 <lin...@googlegroups.com>
Subject: Re: [linc80] Re: Modulus Madness
Relax all.
--
You received this message because you are subscribed to the Google Groups "LiNC80" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linc80+un...@googlegroups.com.
To post to this group, send email to lin...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/linc80/cf314783-6a92-4ecb-9555-5d97e9c89fdd%40googlegroups.com.
Derry UK
CubeCentral
Derry,
I hadn’t thought about swapping parts with the RC2014, it just didn’t occur to me. Well done!
I’m currently testing yet another different power supply, an old faithful one that I’ve had for decades. I’m also testing a shielded cable to power the SBC1 but it’s too early to report any findings and will update my other post.
I would be more than happy to buy a whole set of ICs from Mouser or Digi-Key if I could get a BOM specifying exactly what to get – as I said, I haven’t the experience to know which ones for sure to get, and am not keen to guess! ;)
Out of curiosity, I wanted to ask what is this “Win10 pc in Yatze” you speak of? Is it an emulator? If you’ve a link that would be very handy as googling for it gets me results for the dice game. Cheers!
-Randal (at CubeCentral)
From: lin...@googlegroups.com [mailto:lin...@googlegroups.com] On Behalf Of Derry UK
Sent: Wednesday, June 6, 2018 13:58
To: LiNC80 <lin...@googlegroups.com>
Subject: Re: [linc80] Re: Modulus Madness
Your second para has just saved me a job Randal, I was going to try a recalculation after error myself.
--
You received this message because you are subscribed to the Google Groups "LiNC80" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linc80+un...@googlegroups.com.
To post to this group, send email to lin...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/linc80/0015561c-323d-48b3-a768-a4055096ca7f%40googlegroups.com.
Derry UK
Derry UK
Jon Langseth
Derry UK
Jon Langseth
I presume you use the same supply with your working and non-working boards? If so then the error is with the board, all that is required is another revision and it should solve the problem (he says lightly :-)
Derry UK
CubeCentral
Derry,
I’m curious about the oscilloscope used to measure this? I am wondering if we should account for the rise time of the probes as well as the bandwidth of the scope. I remember the following formula from way back, and is applied to the leading edge of a pulse in a dynamic system, related to resistor-capacitor filter time constants and settling time:
Rise time (in seconds) = 0.35/bandwidth (in Hz), or Bandwidth (Hz) = 0.35/rise time(s)
So, for an oscilloscope that has 20 MHz bandwidth:
Rt (s) = 0.35 / 20000000 = 1.75 × 10^-8 (s) = 17.5 ns
… that has 100MHz bandwidth:
Rt (s) = 0.35 / 100000000 Hz = 3.5 × 10^-9 (s) = 3.5ns
… that has 200MHz bandwidth:
Rt (s) = 0.35 / 200000000 Hz = 1.75 × 10^-9 (s) = 1.75ns
Rise time is defined as the time required for a signal to move from 10% to 90% of a rising waveform, so is your scope making that measurement for you? (if so, that’s pretty cool!) I would be suspicious of any result of 4ns even with a 200MHz scope, as that’s nearly half of the rise time of the measuring instrument.
And, of course, we should all make sure we have carefully compensated probes to minimize induced ringing.
Thanks for sharing your measurement, and I will have a look later today at any differences between a signal at the oscillator and at the Z50Bus connector. Cheers!
-Randal (at CubeCentral)
From: lin...@googlegroups.com [mailto:lin...@googlegroups.com] On Behalf Of Derry UK
Sent: Saturday, June 9, 2018 04:45
To: LiNC80 <lin...@googlegroups.com>
Subject: Re: [linc80] Re: Modulus Madness
whoops
--
You received this message because you are subscribed to the Google Groups "LiNC80" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linc80+un...@googlegroups.com.
To post to this group, send email to lin...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/linc80/ff7f91aa-2db0-46e5-bb97-c94d4e99642c%40googlegroups.com.
Derry UK
Jon Langseth
Derry UK
Jon Langseth
coinst...@gmail.com
https://www.retrobrewcomputers.org/doku.php?id=builderpages:plasmo:z280rc
I ran modchk5.bas and everything appears to work after 10-15 minutes.
d>a:mbasic80 modchk5.bas
BASIC-80 Rev. 5.21
[CP/M Version]
Copyright 1977-1981 (C) by Microsoft
Created: 28-Jul-81
Random number seed (-32768 to 32767)? 1000
CHECK: A= 78 B= 1 C= 0 D= 0 X= 78 Y= 32766
CHECK: A= 457 B= 1 C= 0 D= 0 X= 457 Y= 32766
CHECK: A= 8816 B= 1 C= 0 D= 0 X= 8816 Y= 32766
CHECK: A= 16565 B= 1 C= 0 D= 0 X= 16565 Y= 32766
CHECK: A= 30415 B= 1 C= 0 D= 0 X= 30415 Y= 32766
CHECK: A= 12847 B= 2 C= 1 D= 1 X= 45613 Y= 32766
CHECK: A= 28902 B= 2 C= 0 D= 0 X= 61668 Y= 32766
CHECK: A= 25739 B= 3 C= 2 D= 2 X= 91271 Y= 32766
CHECK: A= 13834 B= 4 C= 2 D= 2 X= 112132 Y= 32766
CHECK: A= 25551 B= 4 C= 3 D= 3 X= 123849 Y= 32766
CHECK: A= 1892 B= 5 C= 2 D= 2 X= 132956 Y= 32766
After that I ran mm8.bas which I edited line 60 to MD=5 because I only have 5 drives set up in my BIOS (the 5th drive is actually a RAM drive). I ran for about 40 minutes when I control-C to stop it.
d>a:mbasic80 mm85.bas
BASIC-80 Rev. 5.21
[CP/M Version]
Copyright 1977-1981 (C) by Microsoft
Created: 28-Jul-81
Random number seed (-32768 to 32767)? 1000
AaBbCcDdEeFfGgHhIiJjKkLlMmNnOoPpQqRrSsTtUuVvWwXxYyZz
Configured for 5 drive letters A: to E:
W>B:RC1.MMM V<B:RC1.MMM C>D:RC1.MMM V<D:RC1.MMM .246094 23341
W>A:GH2.MMM V<A:GH2.MMM C>B:GH2.MMM V<B:GH2.MMM .738281 23341
W>D:LQ3.MMM V<D:LQ3.MMM C>E:LQ3.MMM V<E:LQ3.MMM 1.47656 23341
W>A:PD4.MMM V<A:PD4.MMM C>E:PD4.MMM V<E:PD4.MMM 2.46094 23341
W>B:FZ5.MMM V<B:FZ5.MMM C>A:FZ5.MMM V<A:FZ5.MMM 3.69141 23341
W>C:GW6.MMM V<C:GW6.MMM C>B:GW6.MMM V<B:GW6.MMM 5.16797 23341
W>A:MC7.MMM V<A:MC7.MMM C>C:MC7.MMM V<C:MC7.MMM 6.89063 23341
W>E:QX8.MMM V<E:QX8.MMM C>A:QX8.MMM V<A:QX8.MMM 8.85938 23341
W>C:IL9.MMM V<C:IL9.MMM C>D:IL9.MMM V<D:IL9.MMM 11.0742 23341
W>B:LZ10.MMM V<B:LZ10.MMM C>C:LZ10.MMM V<C:LZ10.MMM 13.5352 23339
W>E:JI11.MMM V<E:JI11.MMM C>B:JI11.MMM V<B:JI11.MMM 16.2422 23339
W>E:ZG12.MMM V<E:ZG12.MMM C>D:ZG12.MMM V<D:ZG12.MMM 19.1953 23339
W>C:TC13.MMM V<C:TC13.MMM C>E:TC13.MMM V<E:TC13.MMM 22.3945 23339
W>A:PY14.MMM V<A:PY14.MMM C>C:PY14.MMM V<C:PY14.MMM 25.8398 23339
W>A:NG15.MMM V<A:NG15.MMM C>D:NG15.MMM V<D:NG15.MMM 29.5313 23339
W>A:NE16.MMM V<A:NE16.MMM C>E:NE16.MMM V<E:NE16.MMM 33.4688 23339
W>B:YV17.MMM V<B:YV17.MMM C>E:YV17.MMM V<E:YV17.MMM 37.6523 23339
W>C:MH18.MMM V<C:MH18.MMM C>E:MH18.MMM V<E:MH18.MMM 42.082 23339
W>C:WH19.MMM V<C:WH19.MMM C>E:WH19.MMM V<E:WH19.MMM 46.7578 23339
W>E:FJ20.MMM V<E:FJ20.MMM C>B:FJ20.MMM V<B:FJ20.MMM 51.6797 23339
W>C:UQ21.MMM V<C:UQ21.MMM C>D:UQ21.MMM V<D:UQ21.MMM 56.8477 23339
W>D:AK22.MMM V<D:AK22.MMM C>C:AK22.MMM V<C:AK22.MMM 62.2617 23339
W>B:NL23.MMM V<B:NL23.MMM C>E:NL23.MMM V<E:NL23.MMM 67.9219 23339
W>E:WS24.MMM V<E:WS24.MMM C>B:WS24.MMM V<B:WS24.MMM 73.8281 23339
W>A:IN25.MMM V<A:IN25.MMM C>E:IN25.MMM V<E:IN25.MMM 79.9805 23339
W>C:BL26.MMM V<C:BL26.MMM C>D:BL26.MMM V<D:BL26.MMM 86.3789 23339
W>A:NM27.MMM V<A:NM27.MMM C>B:NM27.MMM V<B:NM27.MMM 93.0234 23339
W>E:CX28.MMM V<E:CX28.MMM C>C:CX28.MMM V<C:CX28.MMM 99.9141 23339
W>C:HV29.MMM V<C:HV29.MMM C>D:HV29.MMM V<D:HV29.MMM 107.051 23339
W>A:FX30.MMM V<A:FX30.MMM C>C:FX30.MMM V<C:FX30.MMM 114.434 23339
W>E:QG31.MMM V<E:QG31.MMM C>C:QG31.MMM V<C:QG31.MMM 122.063 23339
W>E:CG32.MMM V<E:CG32.MMM C>A:CG32.MMM V<A:CG32.MMM 129.938 23339
W>A:JK33.MMM V<A:JK33.MMM C>E:JK33.MMM V<E:JK33.MMM 138.059 23339
W>D:XZ34.MMM V<D:XZ34.MMM C>B:XZ34.MMM V<B:XZ34.MMM 146.426 23339
W>C:LH35.MMM V<C:LH35.MMM C>A:LH35.MMM V<A:LH35.MMM 155.039 23339
W>C:ZG36.MMM V<C:ZG36.MMM C>E:ZG36.MMM V<E:ZG36.MMM 163.898 23339
W>D:RU37.MMM V<D:RU37.MMM C>E:RU37.MMM V<E:RU37.MMM 173.004 23339
W>A:SD38.MMM V<A:SD38.MMM C>E:SD38.MMM V<E:SD38.MMM 182.355 23339
W>D:WG39.MMM V<D:WG39.MMM C>B:WG39.MMM V<B:WG39.MMM 191.953 23339
W>E:YQ40.MMM V<E:YQ40.MMM C>A:YQ40.MMM V<A:YQ40.MMM 201.797 23339
W>E:AF41.MMM V<E:AF41.MMM C>B:AF41.MMM V<B:AF41.MMM 211.887 23339
W>C:XF42.MMM V<C:XF42.MMM C>E:XF42.MMM V<E:XF42.MMM 222.223 23339
W>E:PD43.MMM V<E:PD43.MMM C>B:PD43.MMM V<B:PD43.MMM 232.805 23339
W>C:CQ44.MMM V<C:CQ44.MMM C>E:CQ44.MMM V<E:CQ44.MMM 243.633 23339
W>B:EC45.MMM V<B:EC45.MMM C>A:EC45.MMM V<A:EC45.MMM 254.707 23339
W>C:TY46.MMM V<C:TY46.MMM C>A:TY46.MMM V<A:TY46.MMM 266.027 23339
W>C:TW47.MMM V<C:TW47.MMM C>D:TW47.MMM V<D:TW47.MMM 277.594 23339
W>E:OP48.MMM V<E:OP48.MMM C>D:OP48.MMM V<D:OP48.MMM 289.406 23339
W>B:XY49.MMM V<B:XY49.MMM C>E:XY49.MMM V<E:XY49.MMM 301.465 23339
W>A:WI50.MMM V<A:WI50.MMM C>C:WI50.MMM V<C:WI50.MMM 313.77 23339
W>D:XB51.MMM V<D:XB51.MMM C>A:XB51.MMM V<A:XB51.MMM 326.32 23339
W>D:VH52.MMM V<D:VH52.MMM C>C:VH52.MMM V<C:VH52.MMM 339.117 23339
W>C:VE53.MMM V<C:VE53.MMM C>B:VE53.MMM V<B:VE53.MMM 352.16 23339
W>E:HB54.MMM V<E:HB54.MMM C>D:HB54.MMM V<D:HB54.MMM 365.449 23339
W>A:HM55.MMM V<A:HM55.MMM C>C:HM55.MMM V<C:HM55.MMM 378.984 23339
W>B:DZ56.MMM V<B:DZ56.MMM C>A:DZ56.MMM V<A:DZ56.MMM 392.766 23339
W>D:GW57.MMM V<D:GW57.MMM C>A:GW57.MMM V<A:GW57.MMM 406.793 23339
W>A:PT58.MMM V<A:PT58.MMM C>E:PT58.MMM V<E:PT58.MMM 421.066 23339
W>A:OD59.MMM V<A:OD59.MMM C>E:OD59.MMM V<E:OD59.MMM 435.586 23339
W>B:OW60.MMM V<B:OW60.MMM C>C:OW60.MMM V<C:OW60.MMM 450.352 23339
W>A:YG61.MMM V<A:YG61.MMM C>E:YG61.MMM V<E:YG61.MMM 465.363 23339
W>B:NW62.MMM V<B:NW62.MMM C>C:NW62.MMM V<C:NW62.MMM 480.621 23339
W>A:HX63.MMM V<A:HX63.MMM C>B:HX63.MMM V<B:HX63.MMM 496.125 23339
W>D:OI64.MMM V<D:OI64.MMM C>E:OI64.MMM V<E:OI64.MMM 511.875 23339
W>A:AN65.MMM V<A:AN65.MMM C>B:AN65.MMM V<B:AN65.MMM 527.871 23339
W>D:BT66.MMM V<D:BT66.MMM C>A:BT66.MMM V<A:BT66.MMM 544.113 23339
W>D:HX67.MMM V<D:HX67.MMM C>C:HX67.MMM V<C:HX67.MMM 560.602 23339
W>A:XA68.MMM V<A:XA68.MMM C>D:XA68.MMM V<D:XA68.MMM 577.336 23339
W>C:WJ69.MMM V<C:WJ69.MMM C>B:WJ69.MMM V<B:WJ69.MMM 594.316 23339
W>E:VX70.MMM V<E:VX70.MMM C>A:VX70.MMM V<A:VX70.MMM 611.543 23339
W>A:IV71.MMM V<A:IV71.MMM C>D:IV71.MMM V<D:IV71.MMM 629.016 23339
W>A:SJ72.MMM V<A:SJ72.MMM C>C:SJ72.MMM V<C:SJ72.MMM 646.734 23339
W>B:US73.MMM V<B:US73.MMM C>C:US73.MMM V<C:US73.MMM 664.699 23339
W>B:WQ74.MMM V<B:WQ74.MMM C>C:WQ74.MMM V<C:WQ74.MMM 682.91 23339
W>D:RX75.MMM V<D:RX75.MMM C>A:RX75.MMM V<A:RX75.MMM 701.367 23339
W>E:HP76.MMM V<E:HP76.MMM C>B:HP76.MMM V<B:HP76.MMM 720.07 23339
W>B:QO77.MMM V<B:QO77.MMM C>C:QO77.MMM V<C:QO77.MMM 739.02 23339
W>A:MS78.MMM V<A:MS78.MMM C>D:MS78.MMM V<D:MS78.MMM 758.215 23339
W>B:IU79.MMM V<B:IU79.MMM C>D:IU79.MMM V<D:IU79.MMM 777.656 23339
W>A:UD80.MMM V<A:UD80.MMM C>B:UD80.MMM V<B:UD80.MMM 797.344 23339
W>D:GW81.MMM V<D:GW81.MMM C>C:GW81.MMM V<C:GW81.MMM 817.277 23339
W>D:OJ82.MMM V<D:OJ82.MMM C>E:OJ82.MMM V<E:OJ82.MMM 837.457 23339
W>D:XG83.MMM V<D:XG83.MMM C>C:XG83.MMM V<C:XG83.MMM 857.883 23339
W>E:QB84.MMM V<E:QB84.MMM C>A:QB84.MMM V<A:QB84.MMM 878.555 23339
W>A:LI85.MMM V<A:LI85.MMM C>E:LI85.MMM V<E:LI85.MMM 899.473 23339
W>D:FX86.MMM V<D:FX86.MMM C>B:FX86.MMM V<B:FX86.MMM 920.637 23339
W>C:HW87.MMM V<C:HW87.MMM C>E:HW87.MMM V<E:HW87.MMM 942.047 23339
W>E:KP88.MMM V<E:KP88.MMM C>A:KP88.MMM V<A:KP88.MMM 963.703 23339
W>B:SX89.MMM V<B:SX89.MMM C>E:SX89.MMM V<E:SX89.MMM 985.606 23339
W>B:JT90.MMM V<B:JT90.MMM C>C:JT90.MMM V<C:JT90.MMM 1007.75 23339
W>C:TK91.MMM V<C:TK91.MMM C>D:TK91.MMM V<D:TK91.MMM 1030.15 23339
W>E:PB92.MMM V<E:PB92.MMM C>A:PB92.MMM V<A:PB92.MMM 1052.79 23339
W>C:LH93.MMM V<C:LH93.MMM C>E:LH93.MMM V<E:LH93.MMM 1075.68 23339
W>A:JF94.MMM V<A:JF94.MMM C>B:JF94.MMM V<B:JF94.MMM 1098.81 23339
W>A:LX95.MMM V<A:LX95.MMM C>E:LX95.MMM V<E:LX95.MMM 1122.19 23339
W>D:WG96.MMM V<D:WG96.MMM C>A:WG96.MMM V<A:WG96.MMM 1145.81 23339
W>A:TV97.MMM V<A:TV97.MMM C>B:TV97.MMM V<B:TV97.MMM 1169.68 23339
W>D:RW98.MMM V<D:RW98.MMM C>A:RW98.MMM V<A:RW98.MMM 1193.8 23339
W>A:OP99.MMM V<A:OP99.MMM C>D:OP99.MMM V<D:OP99.MMM 1218.16 23339
W>D:CY100.MMM V<D:CY100.MMM C>A:CY100.MMM V<A:CY100.MMM 1242.77 23337
W>C:LJ101.MMM V<C:LJ101.MMM C>D:LJ101.MMM V<D:LJ101.MMM 1267.63 23337
W>D:FW102.MMM V<D:FW102.MMM C>B:FW102.MMM V<B:FW102.MMM 1292.73 23337
W>E:AC103.MMM V<E:AC103.MMM C>A:AC103.MMM V<A:AC103.MMM 1318.08 23337
W>A:YD104.MMM V<A:YD104.MMM C>D:YD104.MMM V<D:YD104.MMM 1343.67 23337
W>C:OZ105.MMM V<C:OZ105.MMM C>B:OZ105.MMM V<B:OZ105.MMM 1369.51 23337
W>B:WH106.MMM V<B:WH106.MMM C>A:WH106.MMM V<A:WH106.MMM 1395.6 23337
W>D:ND107.MMM V<D:ND107.MMM C>C:ND107.MMM V<C:ND107.MMM 1421.93 23337
W>A:AX108.MMM V<A:AX108.MMM C>C:AX108.MMM V<C:AX108.MMM 1448.51 23337
W>B:VK109.MMM V<B:VK109.MMM C>E:VK109.MMM V<E:VK109.MMM 1475.33 23337
W>E:OY110.MMM V<E:OY110.MMM C>D:OY110.MMM V<D:OY110.MMM 1502.4 23337
W>C:JG111.MMM V<C:JG111.MMM C>A:JG111.MMM V<A:JG111.MMM 1529.72 23337
W>B:SH112.MMM V<B:SH112.MMM C>C:SH112.MMM V<C:SH112.MMM 1557.28 23337
W>C:LE113.MMM V<C:LE113.MMM C>D:LE113.MMM V<D:LE113.MMM 1585.09 23337
W>D:GN114.MMM V<D:GN114.MMM C>C:GN114.MMM V<C:GN114.MMM 1613.14 23337
W>A:JD115.MMM V<A:JD115.MMM C>B:JD115.MMM V<B:JD115.MMM 1641.45 23337
W>B:JJ116.MMM V<B:JJ116.MMM C>E:JJ116.MMM V<E:JJ116.MMM 1669.99 23337
W>C:ED117.MMM V<C:ED117.MMM C>A:ED117.MMM V<A:ED117.MMM 1698.79 23337
W>A:KW118.MMM V<A:KW118.MMM C>B:KW118.MMM V<B:KW118.MMM 1727.82 23337
W>D:HE119.MMM V<D:HE119.MMM C>E:HE119.MMM V<E:HE119.MMM 1757.11 23337
W>D:XJ120.MMM V<D:XJ120.MMM C>C:XJ120.MMM V<C:XJ120.MMM 1786.64 23337
W>A:SX121.MMM V<A:SX121.MMM C>D:SX121.MMM V<D:SX121.MMM 1816.42 23337
W>A:WL122.MMM V<A:WL122.MMM C>D:WL122.MMM V<D:WL122.MMM 1846.44 23337
W>E:WH123.MMM V<E:WH123.MMM C>A:WH123.MMM V<A:WH123.MMM 1876.71 23337
W>A:LX124.MMM V<A:LX124.MMM C>B:LX124.MMM V<B:LX124.MMM 1907.23 23337
W>D:CW125.MMM V<D:CW125.MMM C>C:CW125.MMM V<C:CW125.MMM 1937.99 23337
W>D:UN126.MMM V<D:UN126.MMM C>A:UN126.MMM V<A:UN126.MMM 1969 23337
W>C:YZ127.MMM V<C:YZ127.MMM C>E:YZ127.MMM V<E:YZ127.MMM 2000.25 23337
W>C:ZL128.MMM V<C:ZL128.MMM C>B:ZL128.MMM V<B:ZL128.MMM 2031.75 23337
W>A:JQ129.MMM V<A:JQ129.MMM C>D:JQ129.MMM V<D:JQ129.MMM 2063.5 23337
W>D:ZJ130.MMM V<D:ZJ130.MMM C>B:ZJ130.MMM V<B:ZJ130.MMM 2095.49 23337
W>E:IY131.MMM V<E:IY131.MMM C>B:IY131.MMM V<B:IY131.MMM 2127.73 23337
W>D:LP132.MMM V<D:LP132.MMM C>A:LP132.MMM V<A:LP132.MMM 2160.21 23337
W>C:RP133.MMM V<C:RP133.MMM C>B:RP133.MMM V<B:RP133.MMM 2192.94 23337
W>E:BS134.MMM V<E:BS134.MMM C>B:BS134.MMM V<B:BS134.MMM 2225.92 23337
W>A:UI135.MMM V<A:UI135.MMM C>C:UI135.MMM V<C:UI135.MMM 2259.14 23337
W>B:WA136.MMM V<B:WA136.MMM C>C:WA136.MMM V<C:WA136.MMM 2292.61 23337
W>A:DQ137.MMM V<A:DQ137.MMM C>C:DQ137.MMM V<C:DQ137.MMM 2326.32 23337
W>D:DS138.MMM V<D:DS138.MMM C>C:DS138.MMM V<C:DS138.MMM 2360.29 23337
W>C:JX139.MMM V<C:JX139.MMM C>A:JX139.MMM V<A:JX139.MMM 2394.49 23337
W>E:MO140.MMM V<E:MO140.MMM C>C:MO140.MMM V<C:MO140.MMM 2428.95 23337
W>B:XS141.MMM V<B:XS141.MMM C>D:XS141.MMM V<D:XS141.MMM 2463.64 23337
W>D:UW142.MMM V<D:UW142.MMM C>A:UW142.MMM V<A:UW142.MMM 2498.59 23337
W>B:TL143.MMM V<B:TL143.MMM C>E:TL143.MMM V<E:TL143.MMM 2533.78 23337
W>A:HX144.MMM V<A:HX144.MMM C>E:HX144.MMM V<E:HX144.MMM 2569.22 23337
W>B:UU145.MMM V<B:UU145.MMM C>D:UU145.MMM V<D:UU145.MMM 2604.9 23337
W>B:WO146.MMM V<B:WO146.MMM C>D:WO146.MMM V<D:WO146.MMM 2640.83 23337
W>C:QS147.MMM V<C:QS147.MMM C>E:QS147.MMM V<E:QS147.MMM 2677.01 23337
W>B:MI148.MMM V<B:MI148.MMM C>C:MI148.MMM V<C:MI148.MMM 2713.43 23337
W>C:OW149.MMM V<C:OW149.MMM C>A:OW149.MMM V<A:OW149.MMM 2750.1 23337
W>D:BV150.MMM V<D:BV150.MMM C>C:BV150.MMM V<C:BV150.MMM 2787.01 23337
W>C:TN151.MMM V<C:TN151.MMM C>D:TN151.MMM V<D:TN151.MMM 2824.17 23337
W>B:KC152.MMM V<B:KC152.MMM C>C:KC152.MMM V<C:KC152.MMM 2861.58 23337
W>A:QA153.MMM V<A:QA153.MMM C>B:QA153.MMM V<B:QA153.MMM 2899.23 23337
W>D:XR154.MMM V<D:XR154.MMM C>E:XR154.MMM V<E:XR154.MMM 2937.13 23337
W>E:CU155.MMM V<E:CU155.MMM C>A:CU155.MMM V<A:CU155.MMM 2975.27 23337
W>B:ZZ156.MMM V<B:ZZ156.MMM C>C:ZZ156.MMM V<C:ZZ156.MMM 3013.66 23337
W>E:DS157.MMM V<E:DS157.MMM C>B:DS157.MMM^C
I have not encountered problems yet, but I want to make sure I have a proper understanding of mm8.bas and modchk5.bas before I run them overnight.
My power supply is an adjustable bench power supply over 24" pigtail. The voltage on board is 4.99V
Bill
Jon Langseth
First, it seems we have concluded that the errors we have seen are not caused by the version of BASIC used, or the powersupply. We have not come to a proper conclusion, but it seems there is either crosstalk, capacitive coupling or interference causing the errors that the LiNC80 exhibits, and that it is caused by the board layout or bus termination. These issues seem to only manifest on the LiNC80 when it is running repetitive tight-loop tasks, as the modchk is, and it has been shown that the impact of the issue can be reduced by selection of powersupply and cf-card.
As you are using the Z280RC, I would be very surprised if you encounter any of the same problems. It has a very different, even if somewhat compatible design, and it uses a very different CF-card approach.
On Monday, August 20, 2018 at 6:33:10 AM UTC+2:
[snip]
Bill Shen
I think you are right that Z280RC won't see problems with mm8 and modchk5. I ran the mm8 with 5 disk partitions twice and both times it ran OK for over an hour until it ran out of disk space on the small RAM disk (1.5 meg). I think I can run it longer if I change mm8.bas to only use 4 disk partitions of 8 meg per drive.
I also have another Z280-based SBC that has 8-bit Z80-compatible bus:
https://www.retrobrewcomputers.org/doku.php?id=builderpages:plasmo:zz80rc
But it has no CF interface, just two small RAM disks. It ran modchk5 fine for many hours and can run mm8 OK for a few minutes until it ran out of disk space. I do like the mm8 diagnostics and when I do add a CF interface, I'll run the mm8 diagnostic again.
Bill