I am facing problem with ethernet communication on LPC2368 Rev D. my code works fine on LPC2368 Rev B and same code is not working on LPC 2368 Rev D .. I have used uTasker stack for TCPIP.

Please suggest changes which are required so it works..

Thanks
Pankaj

Start a New Thread

What's the failure? Have you looked into the errata sheer
from NXP website? In the very early revision(rev. '-'), there
is a revision dependent issue on RMII related problem. I doubt
it applys to your case.

best,
Tom
--- In l..., "Pankaj" wrote:
>
> I am facing problem with ethernet communication on LPC2368 Rev D. my code works fine on LPC2368 Rev B and same code is not working on LPC 2368 Rev D .. I have used uTasker stack for TCPIP.
>
> Please suggest changes which are required so it works..
>
> Thanks
> Pankaj
>

Start a New Thread

Hi:

Take a look at this note from the Errata Sheet (Version 9, 20 April 2011)

"5.2 Note 2
On the LPC2368 Rev D, design changes to the Memory Accelerator Module were made to enhance timing and general performance. Design changes are intended to enhance performance in general and will result in minor differences in the code execution timing between the previous device revisions and rev D. Actual performance impact is code dependent, some code sequences may speed up while other code sequences may slow down between the previous device revisions and rev D. This might be observed when using software delays and in such cases, a hardware timer should be used to generate a delay instead of a software delay."

Regards,

Alex R.

--- In l..., "Pankaj" wrote:
>
> I am facing problem with ethernet communication on LPC2368 Rev D. my code works fine on LPC2368 Rev B and same code is not working on LPC 2368 Rev D .. I have used uTasker stack for TCPIP.
>
> Please suggest changes which are required so it works..
>
> Thanks
> Pankaj
>

Start a New Thread

HI All

Thanks a lot for suggestions it helped.. Actual resolution is as follows.

This is hardware issues is with LPC2368 and PHY IC DP83848. and was because of old ref ckt which I have used from Keil eval board . We have connect 25MHZ_OUT of DP83848 to LPC 2368 ENET_REF_CLK which as per application note is not rt connection and may cause issues in 100mbps.. as RIM gives this as delayed o/p..

Solution is to connect the 50MHz signal on X1 directly to the RMII Ethernet clock reference on LPC23xx pin P1.15.

Hope this helps people facing this issue.

Looks like in this world nothing is Constant and as things are changing we are in demand to do work :-) .

For more details look at following...

[http://www.keil.com/support/docs/3384.htm]

http://www.lpcware.com/content/blog/lpc2300-and-lpc2400-rev-b-rev-d-change-ethernet-and-code-execution
http://tech.groups.yahoo.com/group/lpc2000/message/55274

Thanks
Pankaj Zanwar

--- In l..., "alexander_ribero" wrote:
>
> Hi:
>
> Take a look at this note from the Errata Sheet (Version 9, 20 April 2011)
>
> "5.2 Note 2
> On the LPC2368 Rev D, design changes to the Memory Accelerator Module were made to enhance timing and general performance. Design changes are intended to enhance performance in general and will result in minor differences in the code execution timing between the previous device revisions and rev D. Actual performance impact is code dependent, some code sequences may speed up while other code sequences may slow down between the previous device revisions and rev D. This might be observed when using software delays and in such cases, a hardware timer should be used to generate a delay instead of a software delay."
>
> Regards,
>
> Alex R.
>
> --- In l..., "Pankaj" wrote:
> >
> > I am facing problem with ethernet communication on LPC2368 Rev D. my code works fine on LPC2368 Rev B and same code is not working on LPC 2368 Rev D .. I have used uTasker stack for TCPIP.
> >
> > Please suggest changes which are required so it works..
> >
> > Thanks
> > Pankaj
>

Start a New Thread

It is true I have a lpc2478 board using the CLK_OUT of the DP as reference,
and it does not work at 100Mbps, but a LPC2378 chip is working at that rate
with the same clk connection.. odd isn't it?
2012/1/15 Pankaj

> **
> HI All
>
> Thanks a lot for suggestions it helped.. Actual resolution is as follows.
>
> This is hardware issues is with LPC2368 and PHY IC DP83848. and was
> because of old ref ckt which I have used from Keil eval board . We have
> connect 25MHZ_OUT of DP83848 to LPC 2368 ENET_REF_CLK which as per
> application note is not rt connection and may cause issues in 100mbps.. as
> RIM gives this as delayed o/p..
>
> Solution is to connect the 50MHz signal on X1 directly to the RMII
> Ethernet clock reference on LPC23xx pin P1.15.
>
> Hope this helps people facing this issue.
>
> Looks like in this world nothing is Constant and as things are changing we
> are in demand to do work :-) .
>
> For more details look at following...
>
> [http://www.keil.com/support/docs/3384.htm]
> http://www.lpcware.com/content/blog/lpc2300-and-lpc2400-rev-b-rev-d-change-ethernet-and-code-execution
> http://tech.groups.yahoo.com/group/lpc2000/message/55274
>
> Thanks
> Pankaj Zanwar
> --- In l..., "alexander_ribero" wrote:
> >
> > Hi:
> >
> > Take a look at this note from the Errata Sheet (Version 9, 20 April 2011)
> >
> > "5.2 Note 2
> > On the LPC2368 Rev D, design changes to the Memory Accelerator Module
> were made to enhance timing and general performance. Design changes are
> intended to enhance performance in general and will result in minor
> differences in the code execution timing between the previous device
> revisions and rev D. Actual performance impact is code dependent, some code
> sequences may speed up while other code sequences may slow down between the
> previous device revisions and rev D. This might be observed when using
> software delays and in such cases, a hardware timer should be used to
> generate a delay instead of a software delay."
> >
> > Regards,
> >
> > Alex R.
> >
> > --- In l..., "Pankaj" wrote:
> > >
> > > I am facing problem with ethernet communication on LPC2368 Rev D. my
> code works fine on LPC2368 Rev B and same code is not working on LPC 2368
> Rev D .. I have used uTasker stack for TCPIP.
> > >
> > > Please suggest changes which are required so it works..
> > >
> > > Thanks
> > > Pankaj
> > >
> >
>


Start a New Thread