• Please review our updated Terms and Rules here

Rockwell RM 65 Family (AIM 65) Development system?

Thanks Mike.

Both AIM-65s have a R3222-11, R3223-11, R3225-11 and R3226-11

One of them has a R3224-11 (your list just shows R3224 so maybe that's a typo?)

I am happy to dump my RM-65 FDC 090 1.0 R324E-11 ROM What can I use as chip type for the programmer? Also, can I use the same chip type to dump the R3224-11 ROM?

Dwight, I will take pictures of the table of contents of the RM65-0110 INPUT/OUTPUT ROM manual. It's quite thick and half of it is source code.
 
You're probably right, that the R3224 assembler part and file #s should end in -11, as also the Monitor F ROM file name; as I said, I used Rich's names and labels as a base and I'll have to find my actual assembler ROM to check the number. You've got the normal full complement, Monitor, assembler and BASIC.

Note that Rich's DOS ROM is V 1.1; the binary file seems to be incomplete but the HEX file looks OK.

All the AIM etc. ROMs I've seen have been type 2332, equivalent to a 2532 EPROM; try reading it as a 2532 and if not, a 2732.

Have fun!
 
MikeS said:
Here's a list of the common AIM65 ROMs (the file names and notes refer to Rich C's site); use the monitor to dump the first four bytes of your ROMs and compare to the list.

View attachment 55573
Click to expand...

Be careful some of the programmers leave the programming voltage at VPROG. This will damage a ROM. Make an adapter socket and tie the VPROG pin to +5v but you can use the 2532 setting otherwise to read it. You can also just make an adapter to use a 2732 if you can't do the 2532 pinout.
Dwight
 
Last edited:
The pinout is different than the 2732. I made an adapter with a stacking a couple sockets.

div---reader
21 24
20 18
18 21
----- 20 remove pin on socket

I though I was having issues reading the device as the first location was FF. I checked the wiring several times and even read a 2732 with data on it. Then is occurred to me that maybe it didn't use the full size of the device. I checked address 400 and there were 00 and then some data. I thought for a while the ROM was bad. The data looks good so it is likely all fine.
 
Last edited:
Dwight Elvey said:
The pinout is different than the 2732. I made an adapter with a stacking a couple sockets.

div---reader
21 24
20 18
18 21
----- 20 remove pin on socket

I though I was having issues reading the device as the first location was FF. I checked the wiring several times and even read a 2732 with data on it. Then is occurred to me that maybe it didn't use the full size of the device. I checked address 400 and there were 00 and then some data. I thought for a while the ROM was bad. The data looks good so it is likely all fine.
Click to expand...

I was putting the file here and noticed that is was raw hex and not intel hex as I intended. I errored, look at 800 not 400.
The file is labeled *.TXT to get it on the forum. Rename it to R14C5.HEX when you get it.
 

Attachments

  • R14C5.TXT
    9.7 KB · Views: 13
MikeS said:
You're probably right, that the R3224 assembler part and file #s should end in -11, as also the Monitor F ROM file name; as I said, I used Rich's names and labels as a base and I'll have to find my actual assembler ROM to check the number. You've got the normal full complement, Monitor, assembler and BASIC.

Note that Rich's DOS ROM is V 1.1; the binary file seems to be incomplete but the HEX file looks OK.

All the AIM etc. ROMs I've seen have been type 2332, equivalent to a 2532 EPROM; try reading it as a 2532 and if not, a 2732.

Have fun!
Click to expand...

It looks like this is the code that runs on a socket of the AIM65. It doesn't look the same as that in my ROM from the RM65-FDC board. I wonder if it uses calls to the FDC's ROM. My code seems to match the code in the FDC manual.
Looking at the manual it says the ROM I have starts at 8800 while the other ROMs start at 8000. That makes sense from what I can see.
Dwight
 
Last edited:
Hi
Sunci, did you ever put the 32k RAM manual up?
Also, can others post their floppy ROM images. It looks like mine is the only one posted?
Dwight
 
I have some boards to assemble into a system!

From left to right, top to bottom, I see:

ROM board, video board, ADC board
floppy board, cpu board, gpio board
different floppy board?, 8k ram board, unknown board

I have a backplane on order. Quick question for the RM65 folks here. I don't have a serial board, so far as I can tell. Is there a particular way that folks go about connecting a serial terminal to one of these systems?

Scott

rm65-boards.JPG
 
In my particular case, I run mine cards/backplane through the AIM-65 and use it's display and screen. I have not tried to connect a serial terminal but if I did. I'd probably do that through the AIM-65. Since your CPU board is on the backplane, your set up would be different but I am sure @Dwight Elvey will reply soon. I suspect he will know.
 
Thanks @snuci. I'm going to have fun dumping roms and see if I can figure out what all I have. The AIM65 was easier for me to wrap my head around knowing it had a display and keyboard. The RM65 with a display and no serial and (as far as I know) no keyboard is a little more of a mystery how you're supposed to use it.

The board on the lower right that I had listed as "unknown" is an EPROM programmer.

Update - dumping the 2532 on the ROM board reveals what I have -- it's some kind of engine analyzer. That would explain the ADC board as there's stuff in the ROM about voltages being too high or too low.
 
Last edited:
@Dwight Elvey I can see that it has a 6522 VIA on it, so I assume this means I can hook up serial drivers to the VIA and proceed from there. Do you know if your boards have a custom monitor program? Mine don't have any monitor ROM or any BASIC ROM. Just whatever this program is for the automotive analyzer.

Also, it occurs to me that there is no RIOT, and the AIM65 monitor stores variables in the RIOT RAM, so the boards can't run the AIM65 monitor. It'll have to be a different monitor for the RM65 CPU board.

Scott
 
Last edited:
smbaker said:
@Dwight Elvey I can see that it has a 6522 VIA on it, so I assume this means I can hook up serial drivers to the VIA and proceed from there. Do you know if your boards have a custom monitor program? Mine don't have any monitor ROM or any BASIC ROM. Just whatever this program is for the automotive analyzer.

Also, it occurs to me that there is no RIOT, and the AIM65 monitor stores variables in the RIOT RAM, so the boards can't run the AIM65 monitor. It'll have to be a different monitor for the RM65 CPU board.

Scott
Click to expand...
There should be level converter chips for RS232.
Maybe your processor is different than mine. Mine are in storage so I can't look at them now.
Of course, I could be wrong.
Dwight
 
You must log in or register to reply here.
Back
Top