15 Dec
2012
15 Dec
'12
12:18 p.m.
Holm Tiffe wrote:
David Brownlee wrote:
I've looked in the file you referenced above, the Address from the KA630
gives a memory fault (#define KA630_NVR_ADRS 0x200B8024),
but the following block may fit:
case VAX_BTYP_43:
case VAX_BTYP_410:
case VAX_BTYP_420:
put_fp = rom_putchar;
get_fp = rom_getchar;
test_fp = rom_testchar;
rom_putc = 0x20040058; /* 537133144 */
rom_getc = 0x20040044; /* 537133124 */
break;
....
On 15 December 2012 16:59, Holm Tiffe <holm at
freibergnet.de> wrote:
Hmm ...sounds interesting.
...and it sounds as I have to put eighter the KA630 back in my BA23 where
currently A 11/83 lives or I have to put a 2nd disk into my 4000/90 to have
at least a kind of NetBSD development system to compile something :-(
I'm fascinated from those machines but I've done alsmost nothing in the
direction of wirting software from them. (But I used the soldering iron
often and repaired the machines (more the Boards that build them since I
gote never a complete machine). I do even own a russian 11/03 (something
like that, metrical Q-Bus, RX02 like Floppies) that is working again.
I don't think that The KA630 code will work, (ok, maybe for the loader)
since the KA630 is using standard SLUs like the PDP11s. The SCN2681 however
is a real serial chip with it's own register layout, I remember that I have
programmed an 68681 sometimes in the past (which ist mostly the same)...
The NetBSD 6 netboot makes a trap:
I'm pretty sure the loader works as such un the rtVAX, the networki
interface should be supported so far as I've read, but I think the SLU's
are not and so there is nothing to see...
[...]
...so I think the Console SLU is the problem, one
needs a decent
documentation for the rtVAX300 that includes the programming manual for the
SLUs and the NetBSD source to make the Console driver work.
That shouldn't be to much work.
As long as I'm not finding a person that's a little bit involved in
VAX Assembler and is using NetBSD on VAXen, my trip ends here.
Maybe Dave is interested since he has at least such a rtVAX Card.
NetBSD's boot consinit() uses vax_boardtype to determine what console
calls to use:
http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/arch/vax/boot/boot/consio.c?rev…
If the rtVAX ROM console is 'close enough' to a normal VAX then it may
be a simple case of adding its boardtype to the switch statement. If
docs are not available it may even be worth adding a 'default' to each
of them in turn to see if it matches any of them (I'd start with a 630
:)
My level of VAX assembly is probably at the "can recognise it two
times out of three", but I'm happy to help with the boot console
poking... >> b eza0
83 BOOT SYS
-EZA0
2..1..0..
?06 HLT INST
PC = 00001801
>>
...so it isn't working any better as it is.
Regards,
Holm
>> e/l 20040044/n:16
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
>>
>> e/l 200418AD/n:16
P 200418AD 8FDD003C
P 200418B1 000000EF
P 200418B5 66CF01FB
P 200418B9 0ACF9E38
P 200418BD 50D45200
P 200418C1 000C9F9A
P 200418C5 91512004
P 200418C9 03135150
P 200418CD 9E012E31
P 200418D1 52000BCF
P 200418D5 9A50019A
P 200418D9 04000D9F
P 200418DD 50915120
P 200418E1 31031351
P 200418E5 CF9E0117
P 200418E9 9A52000B
P 200418ED 9F9A5002
P 200418F1 2004000E
P 200418F5 51509151
P 200418F9 00310313
P 200418FD 0BCF9E01
P 20041901 039A5200
P 20041905 0F9F9A50
>>
...at least there is some code.
Dows anyone know of an VAX Dissassembler where one can disas just some
bytes..?
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