----- Original Message ----- From: "Kev" <KKlopp@erols.com>
<EXEC> <YES>
generally gets you going.
Thanks, I'm having fun trying it out now! I will make some notes of how I got started and what I found. I just did a ridiculous surgical wiring and soldering job on the Z80 pod 40 pin DIP target cable, it was bad just near where it went into the pod case, so I cut the whole cable off shorter, and peeled and stripped the whole thing and spliced it onto a new IDC connector that had a short cable coming out of it already. Now it works :) lots and lots of nice little heatshrink covered attached wires. I have an 8080 pod, and I expected the target 40pin dip cable to behave the same, so I swapped the perfect condition 8080 cable into the Z80 pod, and got a whole lot of intermittent errors (if I put it in loop it would toggle between fail and ok on some tests) It would pass the pod self test fine, but if I used the Z80 pod with the 8080 cable, it would give data errors in use on the board. Now I have some errors from the galaga script, even on a known good working (orig namco) board, I get errors like: ILLEGAL ADDRESS @ 300000-LOOP? ILLEGAL ADDRESS @ 303FFF-LOOP? ILLEGAL ADDRESS @ F0300D-LOOP? ... and so on, and some more after ram tests to begin (but ram tests ok after skipping errors) These start just after selecting which processor (0=4M), and the tests seem to continue ok after ignoring the errors with the CLEAR/NO button.
I was thinking that it would be nice to have a text file (I was thinking Word Doc or PDF) that you could print out, 1 page that would tell you some basics to go along with the program.
It might be nice to make up a template for program/comments text to put in the top of the .s file, and have it all in one place?
But then again I've been trying to champion the idea of a uniform "bare bones" program that everyone could use as sort of a standard.
Yes I've been saving them and intend to use it too, thanks for the great work.
Press 1 for RAM Press 2 for ROM ..... Press 9 for RUN UUT etc...
but if we can get anywhere on the 9100s I may just forget the 9010 (unless someone can dig up the cross compiler!).
I'd be surprised if the 9100's last that long really, with the non-standard drive interface, OS, old hard disks, they are going to rapidly become doorstops unless some major work is done to clone the OS and drives at least to keep them going. At least the 9010A's are easy to service and maintain. I've not heard of any 9100's here in Australia at all in my searching, and only a few 9010A's. I'm the only person here in the country that I know of with a 9010A even!
I thought my 232 cable was simpler, 4 wires but I cann't find my notes on that now.
Your notes and email are the one included below on the one I sent (here below too)
John, do we have a list archive? Would be handy (or just add a file to the FTP with this info as you compile it Marc).
ok.
Third thought. Has anyone tried to tie pins 2 & 3 of the 232 plug together to make the 9010A "fault tolerant". I want to put a switch on my cable to do that, load the program, flip the switch & run the program. Or is there anyway to have the PC monitor output from the 9010A serially & send <CONT> on failures?
I don't understand this feature yet? Thanks, Marc
-----Original Message----- From: Marc Alexander <marcwolf123@yahoo.com> To: TechToolsList@flippers.com <TechToolsList@flippers.com> Date: Monday, April 15, 2002 9:54 PM Subject: Fluke <> 232 cable, and what do I press :-)
I think the pinouts I saw archived below, though they may work?, could
cause
damage to the 9010A or com port on the PC, as the handshake lines are wired as two outputs shorted together. Measuring the unconnected pins on both units showed that 4-RTS and 20-DTR were live outputs out of the 9010A, so connecting them to outputs on the PC may cause some problems.
I just got mine working with this pinout:
DB9 Female to PC DB25 Female to 9010A 1 CD input 2 RX input ------------2 TX output 3 TX output------------3 RX input 4 DTR output--------------------\ 5 GND-------------------7 GND | 6 DSR input --------------------/ 7 RTS output----\ 8 CTS input ----/ 9 RI input 4 RTS output 20 DTR input
and it works at 2400,N,8,1 at least, obviously no hardware handshaking may limit the transfer speed, I will try higher. I just used the old Windows 3.11 Terminal program and sent the galaga.h file successfully.
Now the big question! What do I press to run the script/tests? I'm trowelling through PDF files but won't have time to read it all for a couple of days, and haven't found the right pages yet, arrghh :) I understand the script, just not how to run it all, and what to do with each test and failures, etc. Ahh, I just worked out some of it, EXEC, ENTER/YES, etc.. Any tips and steps anyone has would be great, examples of a board test and repair from turn-on to finish, anything.. I will put it into a 'Getting Started' doc, c'mon guys! :-)
Thanks,
Marc
----- Original Message ----- From: "Kev" <KKlopp@erols.com> To: <TechToolsList@flippers.com> Sent: Monday, February 11, 2002 4:21 AM Subject: Fluke <> 232
Okay I finally got my Fluke 9010A talking to the PC.
Cable is
DB9 <-> DB25
2 2 3 3 4 20 5 7 7 4
For some reason I can only get
7, E, 1, 9600 (or slower to work)
I can not get 8, N, 1 to work properly?
Kev
To UNSUBSCRIBE from techtoolslist, send a message with "UNSUBSCRIBE" in the message body to: techtoolslist-request@flippers.com. Please direct other questions, comments, or problems to jrr@flippers.com.