Carlos Marcano wrote: > Can you tell us how your TCP/IP stack implementation is going? Yes, it's going very nicely. I created a development board with a 18F67J60 on it and both wired ethernet and a ZeroG WiFi module. The stack previousl= y supported a ENC28J60 external ethernet MAC/PHY, and the additional support for the internal MAC/PHY of the 'J60 was easier than expected. The native support for the ZeroG module is almost working. It can associat= e with a access point given parameters in the EEPROM, and then send and receive packets. It apparently isn't receiving broadcast packets. Microchip confirmed at Masters that this is due to the module rejecting broadcast packets and there is a switch to enable them but not in the documentation I was given. It sounds like it will be easy to fix this once I get the details on how to do it. Otherwise the ZeroG version works. I can manually send a ARP response to a particular node PC on the network, then ping the board successfully from that PC. > Do you plan to release this to the public? Yes. > If so, what licensing > arrangements are you anticipating going with. My usual, which is basically nothing except you have to keep my copyright message at the very beginning of every file. > I'm asking because we are just now starting on a project where the > client wants to be able to monitor the status of his product via a > web interface. We've got a lot of choices available but the person > working on this project is most comfortable with programming in > assembler rather than C. Note that you can call my stack from C with at most a few additional interface routines in assembler. Using C18 will slow down the stack and increase its footprint a bit because it will then need to adhere to some of the brain dead C18 conventions. I've actually done that for another customer. I used the HTTP server code from Microchip on top of my own network stack from the TCP layer on down. With development in C18 stopped in favor of the HighTech compiler, I wouldn't start any new projects with C18. > I'd very much like to have a look at the current implementation if > that's possible. The stack as a whole is not ready yet for release, but most of the source code can be looked at. Install the PIC development tools release from http://www.embedinc.com/pic/dload.htm and look for files with "net" in thei= r name in the SOURCE > PIC directory. Once the stack is ready for others to use, I will mention it on the download page and probably provide some overview documentation and a example. Note that the network stack requires my multi-tasking system, as embodied i= n TASK.INS.ASPIC. However, if you're doing something complex enough to need = a network stack, then multi-tasking is probably something you'd want to use anyway. ******************************************************************** Embed Inc, Littleton Massachusetts, http://www.embedinc.com/products (978) 742-9014. Gold level PIC consultants since 2000. --=20 http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .