headers
Shakthi Kannan | 1 Feb 2006 17:37
Picon

ecos on LN2410SBC

Greetings!

I would like to know if anyone has ported ecos to littlechips.com
LN2410SBC board. It has an ARM920T core.

Since there is ARM9 implementation in ecos, I will only need to do
board-level porting and drivers?

Thanks,

SK

--
Shakthi Kannan, MS
Software Engineer, Specsoft (Hexaware Technologies)
[E]: shakthimaan <at> gmail.com           [M]: (91) 98407-87007
[W]: http://www.shakthimaan.com   [L]: Chennai, India
Permalink | Reply | 1 comment |
headers
Andrew Lunn | 1 Feb 2006 17:55
Picon

Re: ecos on LN2410SBC

On Wed, Feb 01, 2006 at 10:07:55PM +0530, Shakthi Kannan wrote:
> Greetings!
> 
> I would like to know if anyone has ported ecos to littlechips.com
> LN2410SBC board. It has an ARM920T core.

None that i know of.

> Since there is ARM9 implementation in ecos, I will only need to do
> board-level porting and drivers?

Correct.

        Andrew
Permalink | Reply | 0 comments |
headers
oliver munz @ s p e a g | 2 Feb 2006 00:15
Picon

What is the reason of not using the same struct for usbs_rx_endpoint and usbs_tx_endpoint ???

Im want my USB-driver to be able to change dynamical his endpoint 
configurations... I dont't really understand the difference between the 
usbs_rx_endpoint and usbs_tx_endpoint struct's. I want use only one of them, 
and fill it with the rx- or tx-functions.

I think the only problem i can get, are the optional static IO-entry for the 
USB-endpoints. But maybe its the better idea to make IO-entrys in a 
USB-Class like CDC Package...

Is there somebody who can see other problems in using "usbs_rx_endpoint" as 
tx-endpoint?

Thanks for any answer
Oliver Munz
Permalink | Reply | 0 comments |
headers
oliver munz @ s p e a g | 7 Feb 2006 01:04
Picon

Changing the USB-driver datas... Using an array: usb_working_endpoint ep[ENDPOINTS-1]

I think the eCos-USB-slave endpoint data structures should be changed. The 
USB-slave-package should define one struct for all endpoint types whitout 
the control-endpoint.

The device-driver should define an array of all working endpoint-structs 
ep1..n. All enndpoint-functions should get an index variable, so that they 
can address the right struct from the array.

The device-driver and the USBS-interface should define a function to control 
the type and state of an working endpoint.

I don't see any reason in using blabla_ep1(&ep1) and so on, instead of 
something like blabla_ep(ep_array, 1);

Are there other ideas how to improve the USBS and USB-driver APIs?

Thanks
Oliver Munz
Permalink | Reply | 1 comment |
headers
sumanth (sent by Nabble.com | 21 Feb 2006 12:39
Favicon

about configuring interrupts


HI ,
           I am porting ecos to Ixp425 intel xscale processor, i  am
downloading the   
           image through   multi-ice , i am using xscale grg as the source,
i am getting
           struck -up at 

           hal_interrupt_configure in plf_hardware_init  is the problem with
the grg or 
           culprit is using multi-ice

           To say iam in the initilization process of platform related
hardware where i was
           struck 

           i am getting error as data abort at instruction ldrls

          any sugessitions are welcome.

Thanks in advance,
Sumanth.
--
View this message in context: http://www.nabble.com/about-configuring-interrupts-t1161413.html#a3048423
Sent from the Sourceware - ecos-devel forum at Nabble.com.
Permalink | Reply | 0 comments |
headers
sumanth | 22 Feb 2006 12:02

initlizing stack for IXP 425 board


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.

--
View this message in context: http://www.nabble.com/initlizing-stack-for-IXP-425-board-t1168289.html#a3067866
Sent from the Sourceware - ecos-devel forum at Nabble.com.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Mark Salter | 22 Feb 2006 14:44
Picon
Favicon

Re: initlizing stack for IXP 425 board

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
Permalink | Reply | 0 comments |
headers
sumanth.kondlada | 24 Feb 2006 06:43

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
(Continue reading)

Permalink | Reply | 0 comments |
headers
Daly, Jeffrey | 24 Feb 2006 11:14
Picon
Favicon

RE: initlizing stack for IXP 425 board

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 <at> ecos.sourceware.org [mailto:ecos-devel-
>owner <at> ecos.sourceware.org] On Behalf Of sumanth.kondlada <at> wipro.com
>Sent: Friday, February 24, 2006 12:44 AM
>To: ecos-devel <at> 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
(Continue reading)

Permalink | Reply | 1 comment |
headers
sumanth | 28 Feb 2006 11:10

strucking up in infinite loop for IXP 425


Hi,

              we are porting  ecos for ixp425 we have flashed the image as
per the sugessition in the forum but we are running in the infinite loop at
this point

icache_boundary:
        // Here is where we switch from boot address (0x000000000) to the
        // actual flash runtime address. We align to cache boundary so we
        // execute from cache during the switchover. Cachelines are 8 words.
        str     r1, [r2, #IXP425_EXP_CNFG0]    // make the EXP bus switch
        nop
        nop
        nop
        nop
   ----> mov     pc, r0
        nop

  where the instruction says pc value to load into r0 is at the same
location and it goes into infinite loop and never stops execution

                                  if i change the pc to ignore the step mov
pc,r0 then the code is allowing single stepping but the instruction is not
getting effected

can any one help out to sort this problem.

thanks & regards,
Sumanth
(Continue reading)

Permalink | Reply | 0 comments |

Gmane