dwl10@uts.amdahl.com (Dave Lowrey) (01/23/90)
While trying to figure out why my printer driver wasn't working, I
had the "oppertunity" to use ROM-Wack. I have a few questions on
using it:
- I was under the impression that you could get into ROM-Wack
automatically, when you had a GURU. I was not able to get this to
happen. The only way I could get into it was through the WB menu item,
or by hitting DEL on the terminal, after selecting "CONTINUE" on the
"Software error...." requestor. Is there a way to get it to go into
ROM-Wack automatically?
- When entering ROM-Wack by hitting DEL at GURU time, location zero
(0x00000000) contains the text "HELP". Where did this come from?
- Does ROM-Wack have a disassembler?
- I got the impression that there was a full blown Wack avaliable.
Where can I get it?
- I use the FASTROM option of SETCPU on my A2500. When FASTROM is enabled,
and I get a GURU, I have to boot twice. After the "Software error..."
requestor, I get a blank (white or gray) screen. The 3 finger salute
brings up the GURU alert. Then either the "left button" (and right
button also, whats the difference?) or another 3 finger salute, will
re-boot the system. Why does this happen?
I am glad that ROM-Wack is avaliable, as I was able (through the Stack
Traceback) to determine where my program was going nuts. However, the
little doc I have on it, The "RKM: Libraries And Devices" manual isn't
really enough. Is there any other doc avaliable?
--
"What is another word | Dave Lowrey | [The opinions expressed MAY be
for 'Thesaurus'?" | Amdahl Corp. | those of the author and are not
| Houston, Texas | necessarily those of his
Steven Wright | amdahl!dwl10 | employer] (`nuff said!)daveh@cbmvax.commodore.com (Dave Haynie) (01/24/90)
in article <71QR025m81NF01@amdahl.uts.amdahl.com>, dwl10@uts.amdahl.com (Dave Lowrey) says: > - I use the FASTROM option of SETCPU on my A2500. When FASTROM is enabled, > and I get a GURU, I have to boot twice. After the "Software error..." > requestor, I get a blank (white or gray) screen. The 3 finger salute > brings up the GURU alert. Then either the "left button" (and right > button also, whats the difference?) or another 3 finger salute, will > re-boot the system. Why does this happen? When you specify FASTROM, SetCPU will take your ROM code, copy it to a buffer in your 32 bit memory, set up the appropriate MMU table, and then bang the MMU such that this RAM buffer is now mapped to the location of the ROM. Thus you magically appear to have a 32 bit ROM, and things go faster. The problem is when you get a GURU, and the ROM code decides to reset the system, via the 680x0 RESET instruction. The MMU is an extension of the CPU register map, and just like any other part of the CPU, it remains intact through a RESET. However, the rest of the world, including any cards that have been autoconfigured (eg, the 32 bit memory in your system), get reset. So bascially, that RESET instruction yanks the ROM out from under the system. As you might expect, this kind of hangs things until a full system reset (powerup or keyboard) comes along and bangs the MMU registers back to their harmless state. The easiest way to make SetCPU handle this would be to have an operating system call for reset that everything in the OS uses. That would allow SetCPU to vector that Reset() function with SetFunction() to a reset function that knew what SetCPU was doing. Though hopefully next time around the OS will know more about the MMU and handle things even more robustly.... > "What is another word | Dave Lowrey | [The opinions expressed MAY be -- Dave Haynie Commodore-Amiga (Systems Engineering) "The Crew That Never Rests" {uunet|pyramid|rutgers}!cbmvax!daveh PLINK: hazy BIX: hazy Too much of everything is just enough
MARKV@kuhub.cc.ukans.edu (MARK GOODERUM - UNIV. OF KANSAS ACS - MARKV@UKANVAX) (01/25/90)
> While trying to figure out why my printer driver wasn't working, I > had the "oppertunity" to use ROM-Wack. I have a few questions on > using it: > > - I was under the impression that you could get into ROM-Wack > automatically, when you had a GURU. Easy. Instead of pressing "left mouse button to contine", try pressing the right one, and ROM-Wack will come up on the serial port. > - When entering ROM-Wack by hitting DEL at GURU time, location zero > (0x00000000) contains the text "HELP". Where did this come from? I hadn't heard of this one... > - Does ROM-Wack have a disassembler? Don't think so, Wack does (I believe.) > - I got the impression that there was a full blown Wack avaliable. > Where can I get it? I think it can be ordered from CATS like other various materials. > brings up the GURU alert. Then either the "left button" (and right > button also, whats the difference?)... This was just mentioned, left to reboot, right to ROM-Wack. > I am glad that ROM-Wack is avaliable, as I was able (through the Stack > Traceback) to determine where my program was going nuts. However, the > little doc I have on it, The "RKM: Libraries And Devices" manual isn't > really enough. Is there any other doc avaliable? Don't know. Another good tool for this kind of debugging is debug.lib which is at least documented in the new Includes and Autodocs (I got a copy off the actual file off my original Textcraft disk of all places along with old Amiga classics like Download, etc... -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Mark Gooderum Only... \ Good Cheer !!! Academic Computing Services /// \___________________________ University of Kansas /// /| __ _ Bix: markgood \\\ /// /__| |\/| | | _ /_\ makes it Bitnet: MARKV@UKANVAX \/\/ / | | | | |__| / \ possible... Internet: mark@kuhub.cc.ukans.edu ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~