30 Dec
2012
30 Dec
'12
11:36 a.m.
Mouse wrote:
Are they socketed?
Fast Check:
P 20040000 0004A531
P 20040004 09110002
P 20040008 6E6E6E6E
P 2004000C 03020100
P 20040010 55555555
P 20040014 AAAAAAAA
P 20040018 33333333
P 2004001C 00000000
P 20040020 200452B6
P 20040024 200452EF
P 20040028 200452C2
P 2004002C 20045145
P 20040030 2004559C
P 20040034 2004770C
P 20040038 20045308
P 2004003C 00000000
P 20040040 2004539C
P 20040044 200418AD
P 20040048 2004C359
P 2004004C 20041881
P 20040050 2004539C
P 20040054 20041887
P 20040058 2004E4A0
P 2004005C 20041890
P 20040060 2A2A2A2A
P 20040064 2A2A2A2A
P 20040068 2A2A2A2A
P 2004006C 2A2A2A2A
P 20040070 2A2A2A2A
P 20040074 2A2A2A2A
P 20040078 2A2A2A2A
P 2004007C 2A2A2A2A
P 20040080 2A2A2A2A
P 20040084 2A2A2A2A
P 20040088 2A2A2A2A
P 2004008C 2A2A2A2A
P 20040090 2A2A2A2A
P 20040094 2A2A2A2A
P 20040098 2A2A2A2A
P 2004009C 2A2A2A2A
P 200400A0 2A2A2A2A
P 200400A4 2A2A2A2A
P 200400A8 2A2A2A2A
P 200400AC 092A0A0D
P 200400B0 09090909
P 200400B4 09090909
...at least here is something, but w/o knowing the machine code, I would
say that this are some vectors, not code and that followed by some
deadbeef.
Did you read the internal EEPROMs out already?
No. How should I do this? 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
I'm courious what that hardware manual tell to us..
Regards,
Holm
--
Technik Service u. Handel Tiffe, www.tsht.de, Holm Tiffe,
Freiberger Stra?e 42, 09600 Obersch?na, USt-Id: DE253710583
www.tsht.de, info at tsht.de, Fax +49 3731 74200, Mobil: 0172 8790 741