This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Ethernet Code for LPC 1769

Hi all,
We are planning to use Ethernet in our project with LPC 1769 processor. We are using DP83848(national instruments) transceiver.

The problem for me is that i don't where to start with. what are the steps to follow to write code for ethernet. Why should one use TCP/IP stack? How to test the code we have is correct or wrong??

Please guide me through this....

Thanks,
Pavan

Parents
  • Hi Neil,
    Thanks neil for your suggestion.

    Its true i have to concentrate more on C skills.

    Can you tell me how to start working with the TCP/IP code that was given in NXP (niche-lite). I mean how to start looking at the code and make it useful for my application.

    Are there any specific things to consider while porting the stack to the processor i intend.

    Thanks for the links.

    Pavan

Reply
  • Hi Neil,
    Thanks neil for your suggestion.

    Its true i have to concentrate more on C skills.

    Can you tell me how to start working with the TCP/IP code that was given in NXP (niche-lite). I mean how to start looking at the code and make it useful for my application.

    Are there any specific things to consider while porting the stack to the processor i intend.

    Thanks for the links.

    Pavan

Children
  • Exactly the same way you'd start looking at any other code!

    Read the Documentation - look for examples, app notes, etc (remember that Nichelite is not unique to NXP)

    Ensure that you understand at least the basics of TCP/IP

    "Are there any specific things to consider while porting the stack to the processor i intend."

    The Documentation will tell you that!

    As far as the compiler is concerned, it's all just source code - it has no knowledge of TCP/IP or any other application details.

    For compiler errors, you need to realise that just one simple error early in a source can lead to a very large number of resulting errors in the rest of the file.

    eg, if a needed header can't be found, that will cause one error; and then everything else that relies upon something from that header will cause another error (or even errors) - so simply fixing the first error will also remove all those resulting errors!

    Again, this is a perfectly normal and standard part of the 'C' development process!
    Do not be alarmed by large numbers of errors - just start at the first one, take care to understand it, then fix it, then move on...