16 Dec
2012
16 Dec
'12
3:42 a.m.
David Brownlee wrote:
Yes I understand this, but in the KA630 Rom region is no memory assigned
on the rtVAX 300 board, I get a memory fault if I try to access this
region. The VAX_BTYP_43 case is looking better so far...see the snipped i
posted and mouse disassemlbed..
t
Yes, this is NetBSD 6.0 ..installation/netboot/boot (or so..)
On 15 December 2012 19:24, Holm Tiffe <holm at
freibergnet.de> wrote:
Ahh, ok, I'll look into that using my FreeBSD 8 here...
Started do download some tgz's..
David Brownlee wrote:
While it would be helpful to have a normal VAX to hand to sanity check
builds (or at least a simh-vax instance), the NetBSD build system is
designed to be relatively easy to cross build on posix compliant hosts
(Well, certainly most BSDs, Linux & OS X hosts).
You should be able to download a source tree, then run './build.sh -m
vax distribution'. It first builds a set of cross compiler & other
tools, so after the above (or just a './build.sh -m vax tools') you
should be able to go into any directory in the tree and run the
nbmake-vax from the tools build. 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
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)...
If we have a compatible ROM entry point [*] we can ignore the specific
chip implementation for the loader, and once we can output something
to the console future debugging becomes much easier...
[*] eg: ka630_rom_putchar() and friends from
http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/arch/vax/boot/boot/consio2.S?re…
The NetBSD 6 netboot makes a trap:
Is that the stock boot on the rtVAX? >> b eza0
83 BOOT SYS
-EZA0
2..1..0..
?06 HLT INST
PC = 00001801
>>
...so it isn't working any better as it is. I would certainly expect that to
choke as without a vax_boardtype case no console will be assigned. Of
course its possible that the code to determine vax_boardtype is
choking, which would make things potentially more entertaining.
That old boot code I had from the KA630 experiments in the mop dirctory
worked better so far .. it has done nothing visible, but the TIL311 was
displaying a zero, which means that the "OS" is running..
(Yes, I know, an endless loop around a console ready bit in a register
is doing the same)
If it would be of any interest I can drop a couple of versions of boot
with default added to the other cases. It *probably* won't Just Work,
but its quick to change & test.
Oh yes please, I'll try them as fast as possible (to keep things
somewhat interresting at least)
Of course if we have the bootloader generating output the real fun of
getting support for devices & the alternate VM setup can start :)
I don't expect much work in the VM area, from that what I've read DEC
dropped the KA620 way and released a fully working CVAX in that thing.
Got a hint from VAXman in the meantime (German VAx freak, friend of mine)
he heard that the rtVAX was put in the guidance computer from the cruise
missile .. may be the DOD wanted a working CPU..
The Network device should already be supported from netbsd..
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