Hello, I have a doubt regarding physical identifier of an Ethernet physical IC. What is the importance of their physical identifier. when I compared DP83848C and DP83640 and found not much difference in their registers. While programming, only when these identifiers are valid its starts its actual working. What might be the importance of this identifier?
when I compared DP83848C and DP83640 and found not much difference in their registers.
That is exactly why the physical identifier is of use.
You might have two (or more) devices supported by the firmware. They might have similar or vastly dis-similar registers. Taking note of the physical identifier and testing the value allows the code to ensure that you use the correct registers and appropriate settings.
Quote of the day: Give a man a fish and you'll feed him for the day. Teach a man to google and he'll stop asking you stupid questions all the time ... maybe.
The question seem very awkward. What I gleaned, if you program it correctly it works, if you program it incorrectly or without care it doesn't. This doesn't seem like an earth shattering observation where doubt would be involved.
If reading the correct ID and programming it based on the ID works, look at what it does differently in these two cases, and then related that data back to the manuals and data sheets.
John and Stephen looks very similar. They are twins. John is married to Mary. Stephen is married to Susy.
If you want to give a suggestion of a good birthday present for Susy, it obviously helps if you correctly identify Stephen...
That's sounds good.So, while changing my dp83848c to dp83640 what all things should be there in my mind. Any useful links or something like that will be helpful.
I think some component manufacturers have started producing documents detsiling setup, register allocation, etc.
Maybe you should look at them?
Or maybe I'm too much the traditionalist.
That's Ok. But I am asking for a helpful link because I am beginner to HTTP server. In the example code given by KEILMDK5 is using DP83848C. But I am using DP83640. I found physical identifier is different. I made changes accordingly and mapped registers as per the datasheet. Still I am unable to get the Web page on my system after required system LAN configuration is done. Hardware connections are checked with the datasheet. I am doing this as part of my PG course in Embedded System. May be your suggestions will be able to enlighten me.
But I am asking for a helpful link because I am beginner to HTTP server.
Then try with something simpler than HTTP. First off, see if you can get a response to a ping from the board. Get that going first. In all probability, assuming that the HTTP project isn't fundamentally broken, the HTTP functionality would then likely just work.
I support your suggestion. How can I ping my board rather than HTTP?
How can I ping my board rather than HTTP?
Any of the networking projects will support ping.
On your host computer, just use the ping command.
The ping facility is a core component of TCP/IP. I don't understand how anyone could consider starting an HTTP based project without having knowledge of, and experience in, using ping.
I have tried for ping. But 'Request time out' is shown
So either the board can't handle your chip. Or your board requests an IP over DHCP and you have no DHCP server in the network. Or you have configured a fixed IP that your PC doesn't know how to route to. Or just about any number of other possible errors.
But with the lack of information from you, it isn't so meaningful to make random guesses. We don't even know if your device shows any link lamp activity.
DHCP server isn't there in the network. I have configured the IP address myself as told in the sample program which is 192.168.0.100. Whereas my desktop is having 192.168.0.101 and have same subnet mask, gateway and all. Let me know what you meant by 'link lamp activity'.
'link lamp activity'
It's a light that typically blinks when there is network activity. Do they flash?
No its not blinking. Once hardware is switched on the LED blinks. When that LAN connection is made enable from the host PC, the LED stops blinking.