Hi Everyone,
I was talking to Rolf earlier about how all RJ45 connectors seem to have different pinouts for thier PCB connection, and how it introduces uncertainly for bringing up new experiments.
Then I remembered that in the early days of mbed we were a little more gung-ho with stuff like this, and one preferred method was the (destructive) reuse of cheap off the shelf cables.
In the spirit of Simons suggestion of testing one thing at a time, you could start by testing your conenction without having an RJ45 connector to confuse things.
So, you know what pins are what on the mbed Micrcocontroller, and the actual RJ45 contacts are well defined, as are the colour codes of the cores in CAT5 cable.
So:
1. Cut a perfectly good working CAT5 cable in half.
2. Refer to the pinout/wiring spec for CAT5 cables, or some useful webpage like :
3. Strip back the relevent cores (Green, Green/White, Orange, Orange/White) and stick them in your bread board to connect to the mbed Microcontrollers RD+/-, TD+/- pins as appropriate. Hey presto, the RJ45 socket is out of the equation, and you are now wired for ethernet.
SUGGESTION: keep the length of CAT5 cable form your mbed to you hub/switch/router short, 1m or under.
WARNING: Do not plug into a Power Over Ethernet enable Hub/switch/router, as you now have no magnetics to protect you. Failure to observe this will destroy your mbed. We know this for fact :-)
The bonus is that with every cable hack like this, you get *two* new experiment cables for the price of one.. now that is good value :-)
Cheers,
Chris
Hi,
I'm trying to experiment with mbed as a web server and client. I'm using the sample HTTP Server (http://mbed.org/projects/cookbook/wiki/EMAC), but can't get it any response from the my mbed web server. I see the server outputting it's IP address on the serial terminal - 192.168.1.66 - which looks promising and presume this indicates that my ethernet connection is good. I've placed a simple html file 'index.htm' on the mbed flash drive and tried browsing to http://192.168.1.66 the browser eventually times-out. I've also tried: http://192.168.1.66/rpc/led1/write+1 again the browser times-out and no LEDs change on the board.
Is it possible to look at the source for the lwip library and add debugging code. Any other ideas how I can debug this.
Thanks
Nick