From: Christian.Peter@ascom.ch
To: linuxppc-embedded@lists.linuxppc.org
Subject: Linux boot fails after MMU (MPC8260)
Date: Thu, 04 Jan 2001 14:47:53 +0100 (CET) [thread overview]
Message-ID: <0G6N00K6Y4ZYFB@pmdf-it.hasler.ascom.ch> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1614 bytes --]
Hi
I try to boot linux 2.4.0test8 on a custom 8260 board. It fails to start the kernel (no output) and
i think it hangs somewhere after the mmu initialization (ppc/kernel/head.S).
My knowledge of the mmu and the 8260 is not very good, therefore i'm not sure!
A prior co-worker (unfortunately not in the company anymore) had successfully started the kernel
on a SBC8260 board with a vxworks bootloader and some patches for the mbxboot.
I have near the same configuration, some difference in the vxworks bootloader (chip-select, IMMR 0x0f00000), but
i set this new in mbxboot/head_8260.S to the following values.
Memory Map
----------
0x00000000 60x SDRAM
0x20000008 some LEDs
0xFE000000 Flash
IMMR 0xF0000000
Currently i'm debugging with 2 LEDs on the board and i can switch the LED's on and off until
the RFI. After RFI the code should jump to start_here, but it never gets there.
ppc/kernel/head.S
mfmsr r0
ori r0,r0,MSR_DR|MSR_IR
mtspr SRR1,r0
lis r0,start_here@h
ori r0,r0,start_here@l
mtspr SRR0,r0
SYNC
RFI /* enables MMU */
This is a extract of the terminal output.
TFTP_CLIENT...
Starting at 0x400000...
CPU/CPM/BUS: 165/132/66 Mhz
Ethernet (in decimal): 0:160:30:1:4:5
loaded at: 00400000 0040B274
board data at: 00FFFFC0 00FFFFEC
relocated to: 00200100 0020012C
zimage at: 0040B274 0047F33D
avail ram: 00480000 01000000
Linux/PPC load:
Uncompressing Linux...
done.
Now booting the kernel
Is this a configuration problem (memory map)? Any ideas or suggestions?
Many thanks in advance.
Chris
next reply other threads:[~2001-01-04 13:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-04 13:47 Christian.Peter [this message]
2001-01-04 18:24 ` Linux boot fails after MMU (MPC8260) Dan Malek
2001-01-05 2:36 ` David Schleef
2001-01-05 2:52 ` Dan Malek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0G6N00K6Y4ZYFB@pmdf-it.hasler.ascom.ch \
--to=christian.peter@ascom.ch \
--cc=linuxppc-embedded@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).