Hi Matt, I would add PPP - Point-to-Point Protocol - which is the natural evolution of SLIP. You'll find everything you need, error checking, framing, even authentication, compression, encryption, auto-negociation, etc...
PPP would sound like the best fit, as it's really aimed to connect two sides (PPP over serial). But it's also a huge project as well. It's more than one protocol, and often considered as a protocol suite. Maybe some of its layers could be implemented, though I have absolutely no idea how greedy implementation would be. I've found this AN from Microchip few days ago (AN724): http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1824&appnote=en011716, did not find time to read in depth, but if you want to have a look. Cheers Seb 2010/7/13 mattschinkel <[email protected]> > Hey william. > > As always, these tiny things like slip become bigger projects :) > > While writing this slip lib, my intention was simply to send serial > data via wireless in packets, along with some error checking like crc. > Slip it's self seems only useful for wired circuits, but maybe not for > wired practical applications. Slip has packet sizes, but does not > check if the packet size is correct or anything like that. So, I do > need a type of packet data to send. > > Thanks for your suggestions. I would like to work on Ethernet, but it > seems like a huge project. What I/we need is some direction. When Joep > mentioned SLIP, that gave me direction, and some of your thoughts have > also given direction although I am lost and need more detail. Maybe if > I have a bunch of small projects, it will eventually build a full > Ethernet project. > > Would you be able to make a list of projects that should be completed > to build ethernet, and in what order they should be done in? Maybe > give some sub-projects within each project? > > so far I have: > 1. SLIP - basic testing from pic to pic or pic to pc > 2. something about checksums? > 3. ICMP (ping) - try to ping via serial port with SLIP using a > terminal? > 4. smalltcp > 5. UDP > 6. TCP > > I would start with your JAL Ethernet project, but it sounds like the > code is quite complicated because of the old jal, and it may be too > much work to clean it up. I will check the documents you suggested. > > Matt. > > -- > You received this message because you are subscribed to the Google Groups > "jallib" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<jallib%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/jallib?hl=en. > > -- Sébastien Lelong http://www.sirloon.net http://sirbot.org -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
