Re: NetBSD support PXA255?

Keichii Moto writes:

> I took a look at NetBSD lubbock and g42xxeb code,
> the entry and load addresses are 0xa0200000, and the
> virtual address is 0xc0200000. I loaded netbsd.bin at
> 0xa0200000, and go 0xc0200000, I saw the data abot
> message on u-boot. Did I miss something? Thanks.

Yes you did.
To make "go 0xc020000" work MMU has to prepare
RAM paddr 0xa000.0000 to vaddr 0xc000.0000.
I suggest to track how address space is crafted
(changed) before setttb() is called.
Beware, please.  evbarm code is biased to redboot.

Toru Nishimura/ALKYL Technology

Re: NetBSD support PXA255?

check the l1 page table before the call to setttb() if
it does contain the mapping of vaddr
0cc0200000->0xa0200000,Otherwise, your code will hang
after switching to virtual memory addressing.

regards
-kamal

--- Toru Nishimura <locore64 <at> alkyltechnology.com>
wrote:
> Keichii Moto writes:
> 
> > I took a look at NetBSD lubbock and g42xxeb code,
> > the entry and load addresses are 0xa0200000, and
> the
> > virtual address is 0xc0200000. I loaded netbsd.bin
> at
> > 0xa0200000, and go 0xc0200000, I saw the data abot
> > message on u-boot. Did I miss something? Thanks.
> 
> Yes you did.
> To make "go 0xc020000" work MMU has to prepare
> RAM paddr 0xa000.0000 to vaddr 0xc000.0000.
> I suggest to track how address space is crafted
> (changed) before setttb() is called.
> Beware, please.  evbarm code is biased to redboot.
>  
> 
> Toru Nishimura/ALKYL Technology
> 

Re: NetBSD support PXA255?

At Mon, 28 Mar 2005 20:08:26 -0800 (PST),
Keichii Moto wrote:
> 
> 
> I took a look at NetBSD lubbock and g42xxeb code,
> the entry and load addresses are 0xa0200000, and the
> virtual address is 0xc0200000. I loaded netbsd.bin at
> 0xa0200000, and go 0xc0200000, I saw the data abot
> message on u-boot. Did I miss something? Thanks.
> > 

  How about loading netbsd.bin at 0xa0200000, and go 0xa0200000?
That's what we do with redboot.

--
bsh.

Re: NetBSD support PXA255?

Hiroyuki Bessho wrote:
> At Mon, 28 Mar 2005 20:08:26 -0800 (PST),
> Keichii Moto wrote:
> > 
> > 
> > I took a look at NetBSD lubbock and g42xxeb code,
> > the entry and load addresses are 0xa0200000, and
> the
> > virtual address is 0xc0200000. I loaded netbsd.bin
> at
> > 0xa0200000, and go 0xc0200000, I saw the data abot
> > message on u-boot. Did I miss something? Thanks.
> > > 
> 
>   How about loading netbsd.bin at 0xa0200000, and go
> 0xa0200000?
> That's what we do with redboot.

Still the same. I got an error message about "data
abort"
for u-boot.
> 
> --
> bsh.

-kt 

		
__________________________________ 
Do you Yahoo!? 

Re: NetBSD support PXA255?

At Sun, 3 Apr 2005 18:28:08 -0700 (PDT),
Keichii Moto wrote:
> 
> Hiroyuki Bessho wrote:
> > At Mon, 28 Mar 2005 20:08:26 -0800 (PST),
> > Keichii Moto wrote:
> > > 
> > > 
> > > I took a look at NetBSD lubbock and g42xxeb code,
> > > the entry and load addresses are 0xa0200000, and
> > the
> > > virtual address is 0xc0200000. I loaded netbsd.bin
> > at
> > > 0xa0200000, and go 0xc0200000, I saw the data abot
> > > message on u-boot. Did I miss something? Thanks.
> > > > 
> > 
> >   How about loading netbsd.bin at 0xa0200000, and go
> > 0xa0200000?
> > That's what we do with redboot.
> 
> Still the same. I got an error message about "data
> abort"
> for u-boot.

  I've had no experience with u-boot, but if it doesn't use MMU, codes
in #ifdef BUILD_STARTUP_PAGETABLE of lubbock_start.S may help you.

--
bsh.

netBSD support Integrator/CP

Hi,

Does netBSD support Integrator/CP + CM920T ?

I found the description about Integrator/AP from the following pages. 
http://www.netbsd.org/Ports/evbarm/
=>
----------------------------------------------------------------------
ARM, Ltd. Integrator 
The Integrator/AP is an ATX form-factor board that is used for develoment 
of ARM 
processor-based designs. It supports up to four processors on plug-in core 
modules, and 
provides clocks, a bus interface, and interrupt support. The Integrator/AP 
also supports logic 
modules which provide additional peripherals, and can accomodate up to 
three PCI expansion 
cards. The Integrator/AP can also be inserted into a CompactPCI backplane. 

Support for the Integrator was written by Richard Earnshaw, and contributed 
by ARM, Ltd. 

PrimeCell PL010 UARTs in the System Controller FPGA (plcom) 
PrimeCell PL030 Real-time Clock in the System Controller FPGA (plrtc) 
Other devices inserted into the PCI expansion slots 
----------------------------------------------------------------------
However, I was not able to find whether Integrator/CP would support 
netBSD...

Thank you very much in advance.

Re: netBSD support Integrator/CP

On Tue, 2005-04-05 at 03:28, 飯塚 晶子 wrote:
> Hi,
> 
> Does netBSD support Integrator/CP + CM920T ?

Sorry, no.  At least, not at present.  There's no fundamental reason why
it can't be supported (with an appropriate core module -- CM920 would be
fine) but it has a slightly different core logic and different
peripherals.

R.

Re: NetBSD support PXA255?

>>   How about loading netbsd.bin at 0xa0200000, and go
>> 0xa0200000?
>> That's what we do with redboot.
>
> Still the same. I got an error message about "data
> abort" for u-boot.

Are you sure how address space is prepared at the moment
when u-boot runs go command?  ARM requires to enable
MMU to make VIVT cache work and it's unrealistic to leave
MMU turned off for real usage.  This makes somehow
confusing and aweful consequence to switch address space
which MMU provides.  It's apparent to address space will
differ in two different OS (u-boot and NetBSD) and "run
in dark before dawn" strategy is unavoidable.  I think ARM
camp is suffered from the cold fact and it's the reason why
address space arrangements are quite inconsistent across
various product implementations.

I emphasis again check the way address space is crafted.
Note; Linux has a bad habit to use a naked executable to 
start OS.  It's wrong not to use ELF header to go. 

Toru Nishimura/ALKYL Technology

porting NetBSD on a IXP2400

Dell Axim X5 uses Intel XScale at 400MHZ