From: Filippo Capurso - DAVE srl <filippo.capurso@dave-tech.it>
To: linuxppc-embedded@ozlabs.org
Subject: Linux 2.6 on ml403 board
Date: Thu, 15 Jun 2006 16:46:19 +0200 [thread overview]
Message-ID: <449172BB.8010400@dave-tech.it> (raw)
Hi,
I'm trying to get running linux 2.6.17-rc6 (taken from
linux-2.6-denx.git repository) on a Xilinx ml403 board.
I have a custom design in the Virtex-4 (not the reference design) with
U-Boot starting from flash without problems. I'm also able to download
the kernel image via tftp and store it in the flash memory.
U-Boot boots the image correctly:
=> bootm 0xffe00000
## Booting image at ffe00000 ...
Image Name: Linux-2.6.17-rc5-g75429ea3-dirty
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 831805 Bytes = 812.3 kB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Using T32 with the JTAG ICD I've noticed that the kernel code starts its
execution correctly (from 0x00000000), but whet it reaches the MMU
initialization code, it gets into a loop from which it never goes out:
*** 4xx_mmu.c, line 109 ***
while (s <= (total_lowmem - LARGE_PAGE_SIZE_16M)) {
pmd_t *pmdp;
unsigned long val = p | _PMD_SIZE_16M | _PAGE_HWEXEC | _PAGE_HWWRITE;
pmdp = pmd_offset(pgd_offset_k(v), v);
pmd_val(*pmdp++) = val;
pmd_val(*pmdp++) = val;
pmd_val(*pmdp++) = val;
pmd_val(*pmdp++) = val;
v += LARGE_PAGE_SIZE_16M;
p += LARGE_PAGE_SIZE_16M;
s += LARGE_PAGE_SIZE_16M;
}
It is difficult to understand what is really happening with the T32
because all variables in there are cpu registers, so I can't watch them.
Any suggestion will be appreciated.
Thanks in advance
Filippo Capurso
--
DAVE Srl - Electronics System House
via Forniz 2/1
33080 Porcia (PN) - Italy
Telephone: +39.0434.921215
Telefax: +39.0434.1994030
Freefax: +39.02.700520062
web: www.dave-tech.it
e-mail: filippo.capurso@dave-tech.it
how to reach us: http://mail.map24.com/dave
reply other threads:[~2006-06-15 14:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=449172BB.8010400@dave-tech.it \
--to=filippo.capurso@dave-tech.it \
--cc=linuxppc-embedded@ozlabs.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).