From: nprasad3@gmu.edu
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] MPC860, hal_delay_us fails
Date: Thu, 27 Nov 2003 01:00:00 -0000 [thread overview]
Message-ID: <a9312a87d8.a87d8a9312@gmu.edu> (raw)
Hi,
I am trying to get eCos running on a custom board that has an MPC860 processor. Can someone please provide more insight into this routine and why it fails.
1. hal_delay_us - processor stays put in the following loop (*forever*).
do {
asm volatile("mfdec %0;" : "=r"(new_dec) : );
} while (old_dec == new_dec);
The register values for old_dec and new_dec do not change at all and hence cpu is spinning in it forever. I replaced the routine with a simple for loop to simulate delay ofcourse not at all accurately and redboot comes up fine. This routine is called in the early phases of redboot (before even redboot writes information so it was giving the false impression that there was something seriously wrong with the config).
2. Initialization of MMU in vector.S throws an exception.
# Initialize MMU.
bl hal_MMU_init
# Enable MMU so we can safely enable caches.
lwi r3,CYG_MSR # interrupts enabled later
sync
mtmsr r3
sync <--- processor jumps to cyg_hal_default_exception_vsr
I've blocked out this code for now but would like to understand whats going wrong. Is there a way for me to prevent configtool from defining CYGHWR_HAL_POWERPC_ENABLE_MMU (it is grayed out in my config).
Thanks in advance and please let me know if these have been addressed somewhere as I am very new to eCos and this is the first time that I am trying to play with it as well as the MPC860!
Nirmal
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next reply other threads:[~2003-11-27 1:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-27 1:00 nprasad3 [this message]
2003-11-27 7:35 ` Eric Doenges
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=a9312a87d8.a87d8a9312@gmu.edu \
--to=nprasad3@gmu.edu \
--cc=ecos-discuss@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).