Port-vax archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: About support for rtVAX300

Ok. I'll try some obvious comments once more, but I'm ready to give up.

On 2013-01-13 17:11, Holm Tiffe wrote:
Anders Magnusson wrote:

First:  Gratulations to getting the console printout work :-)  Good job!

On 01/13/2013 02:25 PM, Holm Tiffe wrote:
Ok, after a bit cleaning of LED Register stuff and some __asm("halts")
it ends now here:

2070876+92264 [155104+148119]=0x25a65c

scncprobe passed.
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
     2006, 2007, 2008, 2009, 2010, 2011, 2012
     The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
     The Regents of the University of California.  All rights reserved.

NetBSD 6.0 (RTVAX300-test) #158: Sun Jan 13 13:01:32 CET 2013

VAXstation RTVAX
total memory = 16380 KB
avail memory = 13064 KB
mainbus0 (root)
cpu0 at mainbus0: RTVAX300, CVAX microcode rev 6 Firmware rev 17
rtvbus0 at mainbus0
r0=81800e00 r1=00000001 r2=8028c820 r3=00010080 r4=00000001 r5=00000200
r6=80fdf640 r7=801ee848
r8=801fff68 r9=801ee848 r10=80fcd900 r11=8025c68c
ap=8025c4e0 fp=8025c4b4 sp=ffffffff pc=800f104c
panic: SEGV in kernel mode: pc 0x800f104c addr 0

..which is in my cloned rtvbus.c file, in rtvbus_dma_start():

rtvbus_dma_start(struct rtvbus_dma *vd)

         SIMPLEQ_INSERT_TAIL(&rtvbus_dma, vd, vd_q);

         if (rtvbus_active == 0)

Don't know what this stuff is doing at all..
Ok, I say it again:  You do not want the rtvbus, at least not now :-)
There is no DMA stuff you have to setup, nor any resources you must handle.
So, there are no use of it.

To get the SGEC to work everything is already there; you only need to:

Ok, you say it, I'll try to get the stuff out again.
But then I must connect that scn driver to the mainbus?

That whole thing is just software anyway, so what is the problem?

Ok, I'm back.
Fixed that VAXstation Thing in locore.c:
Is it ok this way?

NetBSD 6.0 (RTVAX300-test) #171: Sun Jan 13 14:07:20 CET 2013

Embedded VAX rtVAX 300
total memory = 16380 KB
avail memory = 13064 KB

All VAXen get (and use) the size of the internal memory they get from
the RPB, passed up by the boot loader.
The RPB is setup by the firmware, so it should be correct.  It also
provide the system with bad block information, which is currently
unhandled on vax.

If it isn't, the kernel can count the memory itself.  Just comment out
the size check from rpb in locore and then everything will be fine :-)

-- Ragge

Don't call me penetrant, bu what the heck ist that RPB, where it is located
and how the kerenel accesses it? I read something about RPB or faked PRB,
but it isn't so that there where any comment that maked me know more now..

You know, I posted a link to the VAX Architecture Reference Manual quite a few posts ago. I would suggest you read it. That will answer this, and many other questions.

Remeber: Mouse and I couldn't find the correct etry point for the ROM
Console..the data structures on that thing aren't really good documented.

I can't comment much on your specific board, but the console drivers as such are mentioned in the same VARM. I don't remember exactly to what detail right now, but it's at least worth checking out.

2nd: The _start() in locore.c:

  * Start is called from boot; the first routine that is called
  * in kernel. Kernel stack is setup somewhere in a safe place;
  * but we need to move it to a better known place. Memory
  * management is disabled, and no interrupt system is active.
_start(struct rpb *prpb)

...isn't called from ROM code, it is called from my own hacked thogether
standalone netbsd bootloader...don't think that his informations are
correct. Good alone know how I set variables there to boot something :-)

Are you saying that you did not use the normal VAX NETBSD bootloader, with just some modifications by you? How did you even figure out where the start entrypoint is in your bootloader?


Home | Main Index | Thread Index | Old Index