public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: ken king <kknhuntsville@yahoo.com>
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] ROMable Code Still having problems
Date: Thu, 19 May 2005 07:25:00 -0000	[thread overview]
Message-ID: <20050518205404.36947.qmail@web60215.mail.yahoo.com> (raw)
In-Reply-To: 6667

It seems to stop or hang-up while coping FLASH to RAM
after the 1st word is copied (I started with the adder
code).

Actually, sometimes it just stops -- no bus activity.
I found this in variant.inc
	
	.macro hal_cpu_init
        # Disable special MPC8xx "development support"
which
	# suppresses trace exceptions. The CPU seems to hang,
not 
        # executing from offset 0x1e00(?) as expected.
        lwi	r3,0x00000007
        mtspr	ICTRL,r3
        li      r3,0
        mtspr   DER, r3

If I change the 0x7 to a 0 -- it starts to write to
the terminal before "stopping".

Anybody remember this??


--- ken king <kknhuntsville@yahoo.com> wrote:
> I have a MPC852T custom bd I've been running
> with a BDM. Most every thing is working.I tried to
> make this system boot from FLASH.
> 
> Okay, it works with a BDM connected, with *almost*
> no .gdbinit -- i.e. only target type and
> remote (IP:Port) (just enough to connect) -- no
> monitor or set commands -- no program load!
> 
> I can disconnect the BDM after it boots,
> everything keeps running fine.
> 
> Question is; what module might I have forgotten to
> load that gdb/BDM might be handling for me???
> 
> I've single stepped through hal_hardware_init,
> everything looks fine. /CS init, copy ROM to RAM,
> etc.
> 
> Looked at the ROM /CS with and without the BDM with
> scope, signature looks about the same -- ?burst of
> copy? ROM to RAM.
> 
> I know that *part* of hal_hardware_init works,
> because the clocks change to the right frequency.
> 
> I don't *think* CPU is going into debug mode as
> VFLS{0..1] were never seen to both be asserted.
> 
> Any ideas? 
> 
> TIA,
> KK
> 
> 
> 
> 
> 
> 
> 
> 		
> Discover Yahoo! 
> Stay in touch with email, IM, photo sharing and
> more. Check it out! 
> http://discover.yahoo.com/stayintouch.html
> 
> -- 
> Before posting, please read the FAQ:
> http://ecos.sourceware.org/fom/ecos
> and search the list archive:
> http://ecos.sourceware.org/ml/ecos-discuss
> 
> 


		
__________________________________ 
Yahoo! Mail Mobile 
Take Yahoo! Mail with you! Check email on your mobile phone. 
http://mobile.yahoo.com/learn/mail 

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

                 reply	other threads:[~2005-05-18 20:54 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=20050518205404.36947.qmail@web60215.mail.yahoo.com \
    --to=kknhuntsville@yahoo.com \
    --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).