About

Archives

01 Jul - 31 Jul 2006
01 Aug - 31 Aug 2006
01 Sep - 30 Sep 2006
01 Oct - 31 Oct 2006
01 Nov - 30 Nov 2006
01 Dec - 31 Dec 2006
01 Jan - 31 Jan 2007
01 Feb - 28 Feb 2007
01 Mar - 31 Mar 2007
01 Apr - 30 Apr 2007
01 May - 31 May 2007
01 Jun - 30 Jun 2007
01 Jul - 31 Jul 2007
01 Aug - 31 Aug 2007
01 Oct - 31 Oct 2007
01 Nov - 30 Nov 2007
01 Dec - 31 Dec 2007
01 Jan - 31 Jan 2008
01 Feb - 28 Feb 2008
01 Mar - 31 Mar 2008
01 Aug - 31 Aug 2009
01 Sep - 30 Sep 2009
01 Jan - 31 Jan 2010
01 May - 31 May 2010
01 Jun - 30 Jun 2010
01 Aug - 31 Aug 2010
01 Sep - 30 Sep 2010

Links

Search!

Last Comments

Alvaro Oliver (StackBook Part 4 …): Hey! nice post. I just bo…
Tiago Gomes (Let's start again…): ok, now feel happy, you a…
Tiago Gomes (Let's start again…): ok, now feel happy, you a…
ir0nhide (StackBook Part 4.…): Very cool, nice work
Toby (Gigabyte, LCDs, a…): Good stuff, although now …
luke (StackBook part 3 …): what are you planing to u…
Toby (A quick rant...): Bastards
Hugh (StackBook Part 2 …): Nicely done, but you now …
gm (StackBook Part 2 …): Hmm, I plan to go a littl…
luke (StackBook Part 2 …): i cant help but wonder if…

Stuff

Powered by Pivot - 1.40.4: 'Dreadwind' 
XML: RSS Feed 
XML: Atom Feed 

« Tip - Data recovery f… | Home | StackBook Part 7 - Ke… »

StackBook Part 6 - Ethernet

07 09 09 - 20:31 I got about half way through soldering a small bit of board to the bottom of the graphical LCD so I could plug a 16-pin header in it (I wasn't in the mood for extensive point-to-point soldering...).

So instead I tried something easier - the ethernet module. I soldered up the SPI pins, and plugged the ethernet module into the board... but I couldn't seem to make it behave. Initially I had the module's chip select tied high, but still no luck. The module would come up, and the computer would recognise the ethernet cable as plugged in, but it wasn't showing up at that IP - or generating any traffic. So I wired it to the AVR's CS line - I figured the AVR may have a problem with not being able to see that something is on the CS line.

Sometimes after programming, lights would come on, sometimes it wouldn't - and after replugging the power cable it'd come sometimes as well. But I still couldn't send any traffic. Anyway, I read somewhere else that this arrangement sometimes does not produce a long enough reset pulse for the ethernet module and that it should be connected to a normal pin. So I put it on one, and pulled the line low for 10ms upon startup (much longer than necessary). The module then had lights every time it was turned on, which was a bit better than before. But still no data.

I decided to look through the header files, and eventually found spi.h in the Utility folder of the ethernet library... apparently using the hardware SPI does require setting pins. A few changes later, and it worked!

A bit more messing round, and I had this going:



Ethernet controlled character LCD :D

Now I just need to wire up the GLCD board, and once the keyboard arrives, get some IRC'ing going :D
No comments

Trackback link: http://gm.stackunderflow.com/blog/pivot/tb.php?tb_id=143

  
Remember personal info?

Emoticons / Textile

To prevent automated comment spam, the answer to this rather simple question is required...

 

  (Register your username / Log in)

Notify:
Hide email:

Small print: All html tags except <b> and <i> will be removed from your comment. You can make links by just typing the url or mail-address.

 

Linkdump