Did you read
the internal EEPROMs out already?
No. How should I do this?
Are they socketed?
The only way todo is reading them with the internal
Console Software,
but at first I had to know on wich Address a VAX is starting and if
the MMU is mapping the ROM somewhere later ...
You _probably_ can read them with e/l/p from the console, with suitable
addresses - I think that's how I dumped my KA630's ROM.
The problem, of course, is determining the "suitable addresses". In
the case of the KA630 I dealt with, the manual says: EK-KA630-UG-001
says, on page 3-2, that the ROM appears twice in physical address space
(once at 20040000-2004FFFF and again at 20050000-2005FFFF). I seem to
recall someone mentioning upthread that manual contents are known for
the hardware in question; if you're lucky, they may have similar
language. If not, you might be able to get somewhere by just scanning
physical address space...you'd probably want to start with a probe
every 32K or 64K or some such so you don't try doing billions of
attempted accesses (which would get slow - even if done from software
rather than the console, taking failure traps for most of them would be
time-consuming).
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML mouse at
rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B