From: "Daly, Jeffrey" <jeffrey.daly@intel.com>
To: <ecos-devel@ecos.sourceware.org>
Subject: RE: initlizing stack for IXP 425 board
Date: Fri, 24 Feb 2006 10:14:00 -0000 [thread overview]
Message-ID: <F7DC2337C7631D4386A2DF6E8FB22B30062B6761@hdsmsx401.amr.corp.intel.com> (raw)
the manual is referring to the debug stub that the JTAG tool downloads
to the mini icache of the processor. has nothing to do with the code
you are working on.
>-----Original Message-----
>From: ecos-devel-owner@ecos.sourceware.org [mailto:ecos-devel-
>owner@ecos.sourceware.org] On Behalf Of sumanth.kondlada@wipro.com
>Sent: Friday, February 24, 2006 12:44 AM
>To: ecos-devel@ecos.sourceware.org
>Subject: RE: initlizing stack for IXP 425 board
>
>
>
>
>
>Hi all,
>
>
>
> We are porting bsp for IXP 425 board
using
>AXD debugger and
>
>multi-ice(JTAG) which needs debug mode (correct ?).The manual
"Intel(r)
>IXP42X Product Line of Network Processors and IXC1100 Control Plane
>Processor" , say's that in debug mode does not have a dedicated stack
>pointer and following instructions should not be executed in Debug
Mode,
>they may result in unpredictable behavior LDM ,STM,LDR w/ Rd=PC , LDR
w/
>RRX addressing mode, SWP, LDC, STC
>
> But as part of boot up code these
>instructions ( in reset_vector after PLATFORM_SETUP) Are used like
>stmfd, ldmfd.
>
> Any pointers to resolve this or any sugessitons
>
>
>Thanks & regards,
>Sumanth.
>
>
>The information contained in this electronic message and any
attachments to
>this message are intended for the exclusive use of the addressee(s) and
may
>contain proprietary, confidential or privileged information. If you are
not
>the intended recipient, you should not disseminate, distribute or copy
this
>e-mail. Please notify the sender immediately and destroy all copies of
this
>message and any attachments.
>
>
>WARNING: Computer viruses can be transmitted via email. The recipient
>should check this email and any attachments for the presence of
viruses.
>The company accepts no liability for any damage caused by any virus
>transmitted by this email.
>
>
>www.wipro.com
next reply other threads:[~2006-02-24 10:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-24 10:14 Daly, Jeffrey [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-24 5:44 sumanth.kondlada
2006-02-22 11:02 sumanth
2006-02-22 13:44 ` Mark Salter
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=F7DC2337C7631D4386A2DF6E8FB22B30062B6761@hdsmsx401.amr.corp.intel.com \
--to=jeffrey.daly@intel.com \
--cc=ecos-devel@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).