* Re: Booting Sandpoint 8240??
@ 2001-02-22 18:26 tsombakos, mark
2001-02-22 15:30 ` Matt Porter
0 siblings, 1 reply; 4+ messages in thread
From: tsombakos, mark @ 2001-02-22 18:26 UTC (permalink / raw)
To: 'linuxppc-embedded@lists•linuxppc.org'
Well, I got the thing to boot, though now I don't quite understand it.
I ended up changing the address used in zsrec and the "go" address
to "0x90000" instead of "0x900000". I saw the memory map in the
DINK32 manual that the "Start of user memory" is at 0x90000. I figured
it was a typo in the HHL CDK manual. So, life was good. Until
I realized the bootloader relocates to 0x80000. Now I'm confused again.
DINK32_MAX >>go 90000
loaded at: 00090000 000A4E20
relocated to: 00800000 00814E20
zimage at: 0009B000 0011B486
relocated to: 00815000 00895486
avail ram: 00400000 00800000
Since "avail ram" is 400000-800000, should I run srec -s (something <
800000)?
I know I read that it should be higher than the relocated image ...
Do these numbers just depend on the amount of ram present??
confused,
Mark
-----Original Message-----
<newbie alert!>
I've just undertaken trying to get a Sandpoint 8240 to boot ppc linux.
I have the mvista CDK 1.2, as well as the code from
ftp://ftp.mvista.com:/pub/Area51/sandpoint-8240/README
My development platform is RH6.2 linux. I'm running version
12.0 of DINK.
Here come the questions :)
1) I tried compiling the code in spdemo-2.3.16-2000.02.10, but
it insists on a ramdisk.image.gz file. I tried removing the
RAMDISK entry from .config, but them got compile errors.
I see instructions on how to build a ramdisk, but - how do
I put the right ppc files in the ram disk if I don't have a ppc
system to get them from?
2) I resorted to compiling the linux-2.4.0-test2 kernel, and
it compiled with the additional network card I needed (tulip).
However, when I boot, I get
DINK32_MAX >>go 900000
loaded at: 00900000 00914E20
relocated to: 00800000 00814E20
zimage at: 0090B000 00988955
avail ram: 00400000 00800000
Linux/PPC load: root=nfs
Uncompressing Linux...done.
Now booting the kernel
and that's it. What should I see next? Should it init the network
card? Will I see that? I have dhcp, tftp, nfs set up but I don't see
any network activity on the host from the sandpoint using tcpdump.
thanks for any pointers!
Mark
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Booting Sandpoint 8240??
2001-02-22 18:26 Booting Sandpoint 8240?? tsombakos, mark
@ 2001-02-22 15:30 ` Matt Porter
2001-02-22 20:30 ` Dan Malek
0 siblings, 1 reply; 4+ messages in thread
From: Matt Porter @ 2001-02-22 15:30 UTC (permalink / raw)
To: tsombakos, mark; +Cc: 'linuxppc-embedded@lists•linuxppc.org'
On Thu, Feb 22, 2001 at 01:26:06PM -0500, tsombakos, mark wrote:
>
> Well, I got the thing to boot, though now I don't quite understand it.
> I ended up changing the address used in zsrec and the "go" address
> to "0x90000" instead of "0x900000". I saw the memory map in the
> DINK32 manual that the "Start of user memory" is at 0x90000. I figured
> it was a typo in the HHL CDK manual. So, life was good. Until
> I realized the bootloader relocates to 0x80000. Now I'm confused again.
DINK32 loads the linear array of bits that comprise the zImage at 0x90000
(576KB). The standard bootloader always relocates to 0x800000 (8MB) and
continues running. The bootloader then uncompresses the included
vmlinux.gz and places it at the start of RAM (0MB).
> DINK32_MAX >>go 90000
> loaded at: 00090000 000A4E20
> relocated to: 00800000 00814E20
> zimage at: 0009B000 0011B486
> relocated to: 00815000 00895486
>
> avail ram: 00400000 00800000
>
>
> Since "avail ram" is 400000-800000, should I run srec -s (something <
> 800000)?
> I know I read that it should be higher than the relocated image ...
You don't need to do a thing, all is well. :)
--
Matt Porter
MontaVista Software, Inc.
mporter@mvista•com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Booting Sandpoint 8240??
2001-02-22 15:30 ` Matt Porter
@ 2001-02-22 20:30 ` Dan Malek
0 siblings, 0 replies; 4+ messages in thread
From: Dan Malek @ 2001-02-22 20:30 UTC (permalink / raw)
To: Matt Porter
Cc: tsombakos, mark, 'linuxppc-embedded@lists•linuxppc.org'
Matt Porter wrote:
> You don't need to do a thing, all is well. :)
Ummmm....I think this should work, but those addresses weren't my
original intention. The original "design" was to use 0x00800000
as the link address, and 0x00900000 as the load address. The code
will copy itself down to the 8 Meg location, then uncompress as you
describe. I don't know if this is still the case, but the uncompress
code used to make some assumptions (take some liberties) about using
the space between the load address and execute address for temporary
storage. If you load below the execute address, this address
arithmetic is screwed up and I'm not sure what would happen.
With the 2.4 kernel you have to allow almost 1.5 Mbytes of space
from the start of RAM for the kernel to do its work, and not write
over some boot information (command line or initrd info) that the
initial bootloader may have dropped into magical memory locations.
Trying to run a bootloader under the 2M boundary is risky, and it
won't run in under the 1.5 M boundary.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 4+ messages in thread
* Booting Sandpoint 8240??
@ 2001-02-20 19:36 tsombakos, mark
0 siblings, 0 replies; 4+ messages in thread
From: tsombakos, mark @ 2001-02-20 19:36 UTC (permalink / raw)
To: 'linuxppc-embedded@lists•linuxppc.org'
<newbie alert!>
I've just undertaken trying to get a Sandpoint 8240 to boot ppc linux.
I have the mvista CDK 1.2, as well as the code from
ftp://ftp.mvista.com:/pub/Area51/sandpoint-8240/README
My development platform is RH6.2 linux. I'm running version
12.0 of DINK.
Here come the questions :)
1) I tried compiling the code in spdemo-2.3.16-2000.02.10, but
it insists on a ramdisk.image.gz file. I tried removing the
RAMDISK entry from .config, but them got compile errors.
I see instructions on how to build a ramdisk, but - how do
I put the right ppc files in the ram disk if I don't have a ppc
system to get them from?
2) I resorted to compiling the linux-2.4.0-test2 kernel, and
it compiled with the additional network card I needed (tulip).
However, when I boot, I get
DINK32_MAX >>go 900000
loaded at: 00900000 00914E20
relocated to: 00800000 00814E20
zimage at: 0090B000 00988955
avail ram: 00400000 00800000
Linux/PPC load: root=nfs
Uncompressing Linux...done.
Now booting the kernel
and that's it. What should I see next? Should it init the network
card? Will I see that? I have dhcp, tftp, nfs set up but I don't see
any network activity on the host from the sandpoint using tcpdump.
thanks for any pointers!
Mark
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2001-02-22 20:30 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-02-22 18:26 Booting Sandpoint 8240?? tsombakos, mark
2001-02-22 15:30 ` Matt Porter
2001-02-22 20:30 ` Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2001-02-20 19:36 tsombakos, mark
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox