Slashdot Mirror
Embedded Ethernet and Internet Complete
Axelson's writing style is a little difficult to describe. At times you feel you could be reading a "For Dummies" (TM, Patent Pending, Please Don't Sue Me) book since her writing style is so easy to digest, but simultaneously, she's covering quite a bit of depth and breadth which you expect from a more advanced volume. This seems paradoxical yet the point stands: you will retain what you read from Axelson.
ContentsThe networking basics sections describes the network protocol stack (Ethernet, TCP, UDP, and IP frames), collision mediation, and how to use a sniffer (Ethereal in her case). It's of moderate detail suitable for an introduction. Much more detail is provided in later sections. Axelson also uses this section to describe, in good detail, the Ethernet media access control scheme that arbitrates which device talks when and how to handle packet collisions.
These network hardware sections are an in-depth description of cabling (Cat-5, fiber, wireless, etc.) which includes bit rate, max lengths, encoding types, etc. She also includes a small section on building your own Cat-5 for you really cheap Joes. There is a cursory review of hubs, switches, and routers and the network architecture limitations imposed by each for each type of network cabling.
Axelson goes on to describe some common embedded systems including TINI (Java-based) and Rabbit (C-based), which are the two systems she uses and provides examples for. Thankfully, keeping with her Circuit Cellar hobbyist tradition, both of these systems are very affordable to the casual hobbyist. She also provides detailed descriptions of some common Ethernet chipsets down to the registers (at least for the ubiquitous NE2000 registers). Also included are schematics for typical interfaces to these chipsets for the reader who wishes to build his own Ethernet-aware embedded system.
The Internet basics sections describe the various connection solutions such as dial-up, DSL, and satellite and the benefits and limitations of each. Axelson provides a cursory discussion of firewalls, domain naming and DNS, URL dissection, DHCP, NAT, ARP, and ICMP. These sections, I believe, are suitably informational for the embedded system designer, but not exhaustive. She then launches into an in-depth discussion of IP addressing and the IPv4 header which, in my opinion, is required for anyone working at the packet level. Axelson uses some data from Ethereal to support her discussion of IPv4. She also reminds us that Ethernet communications need not use the full TCP or UDP stack but can, if desired, use only IP-wrapped packets or even just Ethernet frames to communicate.
We finally get to some real code in the TCP/UDP socket communication sections. Axelson begins with samples of UDP, then TCP, socket communications. She bounces back and forth between Rabbit C code and TINI Java code. Both sets of examples are properly threaded so as to be more than just academic-example hogwash. Then she delves into the details of UDP and TCP, beginning with descriptions of the frame headers, then concludes with handshaking/flow-control (SYN-ACK and so forth). She includes suggestions for other books that continue even deeper into socket communications which is very nice especially since they aren't gratuitous promotions from the same publisher. (They are, in fact, from two different publishers.) By the way, Lakeview Research is her own company, so Axelson self-publishes. Nice.
Fully half of the book is dedicated to describing the top layer of the protocol stack: applications. Specifically, HTTP client and server, receiving and sending email, and FTP client and server. The HTTP samples leverage the bundled TINI and Rabbit libraries to serve web pages. Axelson also includes examples of running a third-party servlet engine (Tynamo) on the TINI system. Similarly, the sections for sending and receiving email and the FTP client/server leverage the bundled libraries of Rabbit and TINI. I find this appropriate -- why write low-level socket code when there are available libraries that perform all the grunge work for you? If you do need to modify the support libraries, the Rabbit Dynamic C source code is available, but the TINI Java library source code is not.
The last few sections of the book discuss security. Axelson doesn't leave security as a footnote, as she does include sample code for basic authentication, but she also doesn't give security the depth she provided the other topics. Sure, security is a huge topic which would take numerous volumes to cover, but I thought this section could use a little more detail. I would like to have seen example code in the sections on encryption (both symmetric and asymmetric). I would like to have seen what is required to enable SSL in the web server examples. If these were not to be provided, I would have like to have her cite other books which would have completed her discussion as she did in the raw socket communications sections.
What Could Be ImprovedI don't really like the large font and spacing used in this book; I prefer a more condensed text which probably would have reduced the book size some 20% or so. But as I think about it, perhaps this is one characteristic that make Axelson's books so easy to read: there is little eye-strain.
In the hardware sections, I would like to have seen even a trivial example of an NE2000 device driver. It wouldn't even have to be an Ethernet-compliant driver, just something that demonstrates sending and receiving with flow and error control. This would be useful if you were building your own device which didn't include a protocol stack.
In the low-level socket communications sections, I would have preferred to see two things. First, I would have liked to see a test program that communicated between the C-based Rabbit and the Java-based TINI to demonstrate a heterogeneous distributed embedded system. Second, I would have like to seen an echo test program. When prototyping communications to any embedded system I always write an echo test program which begins by transmitting a small message with a numeric value, then listens for messages, increments their value, and sends them back out. Validation testing is performed during this process. This program is easy to write and a great diagnostic tool.
ConclusionSince this is my first book review I can't objectively give it an absolute rating like 4 stars or 8/10 since you have nothing to compare my judgment to. However, I can say that this book is well worth the money spent which, all too often, isn't the case anymore these days. I think Axelson has struck an ideal blend of detail where needed and summary when detail is not required. The book is organized well and should satisfy both the casual bathroom reader and the rigorous, horribly-cracked-binding, lab-bench-reference reader.
I like Axelson's writing style; it's an ideal blend of assume I'm an idiot-style when you need it and in-depth when you want to dig. Another great point: she doesn't stuff the appendices with data sheets, API documentation, or command syntax references. All those can be found on-line and have no place in a book, where they quickly become dated. If you absolutely must have a definite rating, then I'd give it an 8 or 9 out of 10. I would place books like Stevens' Unix Network Programming at a solid 10 and about 99% of the other books out there around a 5.
You can purchase Embedded Ethernet and Internet Complete from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
The anti-salmon
It sounds like a good title to have around, I will probably buy it just for that reason.
However, if the device or embedded system you're working on is already designed and your goal is to network-enable it, what do you guys turn to? From what I've seen around, Lantronix XPort is a good option for cheap embedded device servers, but what else is available?
Hi, I represent Indian computer services company. It sounds like we could talk to your boss about replacing you with two smart ambitious goal-oriented individuals that I have in my office right here.
Ethernet, TCP, UDP, and IP frames
Uhh.. Ethernet uses frames, IP uses packets.
-Jim
Used to be that San Francisco sent it's laundry by ship to be done in China. That was a temporary situation, too.
And so many people at /. wonder why they don't have a girlfriend...
The smartest person I know is female.
...let me suggest not starting your list improvements talking about fonts ;-)
"Ain't I a stinka..." - Bugs
The smartest person I know is female.
Then you don't seem to know many smart people indeed.
And the usual code quality report courtesy PMD:
The Army reading list
You mean I can buy the Internet?
I wonder if the book includes a CD?
- - - - - - - - - - -
I am a programmer. I am paid to produce syntax not grammar. Deal with it.
Embedded and real-time are not equivalent.
And Java, too.
Good luck in that. You pretty much narrowed your choices down to Sun, Apple, and Redhat. And I am not even sure that they don't have at least one machine around just to compare to.
Anybody seen something similar, but for USB? I.e., if you want to build an embedded USB slave device?
"Eve of Destruction", it's not just for old hippies anymore...
fwiw, I've been using a Rabbit (RCM2200) for almost a year now on a personal project. It's connected to my house network, which is connected to the internet via the normal methods (Linksys hardware). The supplied libraries that come with the Rabbit are very capable as-is, but you can expand them if need be since you get the source (as the reviewer mentioned). I added code to be able to do authenticated smtp logins, for example. Getting code up and running to be able to do a telnet login to check on its status, and change settings was dead easy. It runs 24/7 and has been very reliable... the uptime hasn't exceeded a few months simply because I usually don't go that long without performing a code update of some kind, or otherwise powering down for a hardware reconfig, etc. Someday I may document the project and submit it to /. .... those who have seen it thus far think it's pretty kewl.
w
Not at all.
The fact that I'm as ugly as a smacked arse would put women off.
I was just pointing out that not all women are stupid.
No, the reviewer made a mistake. Jan is a man. It is not Jan as in, "Marsha, Marsha, Marsha!" Jan is prounced like "yawn" and is a male's name that is germanic (scandinavian? something in that general vicinity) in origin.
BWAHAHAHAHA!!!! Even my wife thought this one was funny. Gawd the mods are really puritanical now, aren't they? Get a clue and a sense of humor you dilholes.
Correct. In fact, I'm a German and my name's Jan (pronounced "Jun").
No, Jan is a woman.
By the way, Lakeview Research is her own company, so Axelson self-publishes. Nice.
While I admire Jan for making a viable business out of something she obviously loves, she seems to have bitten off a lot for herself. After building some prototype hardware based on Parallel Port Complete, I found the book had an error making my hardware quite crippled (a software workaround was possible, but inefficient and ugly). I pointed it out to her via e-mail, but it was never resolved to my satisfaction. AFAIK, to this day that error still exists.
I began to wonder what it must be like to self-publish and then deal with an error report when you are author, editor, publisher and tech support all rolled into one. A bigger company may not have handled my issue any better, but certainly it would have the resources do so easier than a small self-publisher. My two cents are: Jan's stuff is great for hobbyists, but beware of accuracy.
Mac OS X: A server strength operating system that your granny could install and use.
I like the way you think on two counts.
malia8888, OS X user & female
TCP/IP Lean by Jeremy Bentham, ISBN: 1-929629-11-7
Cirrus Logic CS8900a Ethernet module, it works in 8-bit mode
Buy a CS8900 module.
** Shameless plug **
Read my thesis about how to put it all together.
Loser.
It may be a better fit for those of us with absolutely no background, really short attention spans and very strange ideas about what might be cool to do to a toilet...
Don't look now, but you are being cheated on.
You refer to Jan as "her" and "she". Jan is a (Swedish) male name, however.
Assuming they mean making up network cable and not actually fabricating CAT-5 wire, why on Earth would you NOT make your own cables?
CDN$.30/foot + connectors is a hell of a lot cheaper than the precut lengths that are only available in standard sizes (25ft, 50ft), and it's very easy..
Jan is also a woman's name in English (the language the book is written in.)
The publisher's bio shown at the linked Barnes and Noble site for the book says, "She".
The fact that I'm as ugly as a smacked arse would put women off.
I was just pointing out that not all women are stupid.
Somebody modded this as "Informative". Precisely what didn't they know?
We routinely publish her work in Nuts & Volts (hobby electronics) as well as SERVO Magazine (personal robotics).
Dan Danknick
Technical Editor (of both)
I found this the other day in a Dev Kit at http://store.systronix.com. It came with a TINI400 (TStik), Socket Board and this book.
It was the only book they sell on their site (which piqued my interest).