initlizing stack for IXP 425 board

[sumanth]

Hi all,

            I am sumanth porting ecos to Intel xscale ixp425 board .

            i am initilizing the stack in the  reset_vector, but it is not getting effected

            I am getting problem when i am encountering the instruction

            stmfd/stmdb  

            and in the same way when encountering the instruction

            ldmfd/ldmdb

            can any one help me how to solve this problem of initilizing the
            stack ,so that it can continue execution when encountering

            stmfd/stmdb
            ldmfd/ldmdb

  Thanks in advance,
  Sumanth.

[Mark Salter-2]

On Wed, 2006-02-22 at 03:02 -0800, sumanth wrote:

> Hi all,
>
>             I am sumanth porting ecos to Intel xscale ixp425 board .
>
>             i am initilizing the stack in the  reset_vector, but it is not
> getting effected
>
>             I am getting problem when i am encountering the instruction
>
>             stmfd/stmdb  

You don't give enough information. Have you looked at how the existing
ixp425 ports work? You have to initialize the SDRAM controller before
using a stack.

--Mark

[sumanth]

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

[Daly, Jeffrey]

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@... [mailto:ecos-devel-
>owner@...] On Behalf Of sumanth.kondlada@...
>Sent: Friday, February 24, 2006 12:44 AM
>To: ecos-devel@...
>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