stan@phx.mcd.mot.com (Stan Fisher) (01/04/91)
HELP ANYONE!
I've recently aquired a 2630 board.. and replaced a 2620 in my Amiga.
I also have a 2091 and WAS using SetCPU 1.5 to relocate its firmware
to 32bit ram (on the 2620). Now that the 2630 is in place, I grabbed
a copy of SetCPU 1.6 and tried to fire it (the 2630) up with the
same cardromlist that I used before. My original entry for the 2091 was:
0x202 0x03 0x10000 0x2000 0x3fff CBM_2091_SCSI_Controller
After reading the SetCPU.txt file, I find that it now only transfers even
increments of 16k (0x4000) so I changed that field in the above entry:
0x202 0x03 0x10000 0x2000 0x4000 CBM_2091_SCSI_Controller
Prior to that change I noticed (with VERBOSE) that the rom wasn't getting
relocated. (expected since size was < 16k) After the change, I get a task
held requestor and complete system lockup (mouse, keyboard etc.) at the
point where the rom is being relocated. I examined the memory space that
the 2091 takes in my system with the 2630 rom monitor, and found that
the board starts at E90000 (apparently registers etc up to E91FFF) and
that the rom starts at E92000 and repeats in it's map at E96000, E9A0000
and partially at E9E000. The board ends at EA0000. The rom size (0x4000)
looks good for the cardrom entry, the offset (0x2000) looks good, the board
size (0x10000) looks good, the manufacturer and product codes (0x202 0x03)
look good according to a utility I used to check them.
Then I tried remapping the other images of the rom instead (those at E96000,
E9A000 etc.) and the following resulted:
0x202 0x03 0x10000 0x6000 0x4000 CBM_2091_SCSI_Controller
^^^^ offset to the second rom image...: Guru #3
0x202 0x03 0x10000 0xA000 0x4000 CBM_2091_SCSI_Controller
^^^^ offset to the third rom image....: no complaints
I realized after this that even though I apparently made a copy of the rom
image in 32bit ram and pointed all access to that range to the 32bit ram
via MMU... that the system is probably still accessing the REAL rom in 16
bit space on the 2091 since it was probably using the 1st image of it at
offset 0x2000. So I figure I didn't fix anything, just that I'm wasting
16K of 32bit RAM. My system is a 4.5 A2000 with a 2091 and the 2630/4Meg.
If anyone is successfully using a 2630, 2091 and SetCPU 1.6 to relocate the
2091 firmware to 32 bit RAM, I would appreciate the cardromlist entry
you're using and any other advice.
Thanks in advance.
Stan
Stan Fisher - stan@teroach.phx.mcd.mot.com - asuvax!mcdphx!teroach!stan
Motorola Microcomputer Division, Tempe, Arizona - Voice (602) 438-3228