From: Tristan W. <tri...@gm...> - 2009-01-27 02:51:25
|
ARM and Coldfire are both 32-bit and much larger SoC lines. I'm using a MCF54455 running vxWorks, and there's Linux for it too. That said, they're much, MUCH bigger than a tiny PIC in space, support, and cost. You may be interested in a WIZnet W5100 chip. It's a dedicated Ethernet MAC and PHY chip with a bunch of network layers built into it, including TCP/IP, all accessible over a SPI interface. Then all you need is a uC that has hardware SPI and to implement the HTTP layer and motor control. There are even two Arduino shields that use this chip with code and example stuff out there. The drawback is it's another chip just for net connections. If you're short on board space then you're probably not going to like adding another chip to the layout. The PIC18 chip you selected is fine hardware and feature wise but, from what I've read on this mailing list, SDCC has a number of PIC18 shortcomings. You're going to be a bit of a trailblazer here. On Mon, Jan 26, 2009 at 3:25 PM, Peter Theobald <pe...@pt...> wrote: > Thanks Tristan, I'm wondering if the pic18f is the best chip for this as it > doesn't seem to have too many ports. Would I be better off with an 8051, arm > or coldfire? > Regards > Peter > > 2009/1/26 Tristan Willy <tri...@gm...> >> >> When I was looking for small networking stacks, uIP >> <http://www.sics.se/~adam/uip/index.php/Main_Page> looked good. Never >> got around to trying it, but it appears to have been ported to PIC18 >> using HITECH's compiler. >> >> On Mon, Jan 26, 2009 at 5:30 AM, Peter Theobald <pe...@pt...> >> wrote: >> > Thanks Pedro, Thats a shame. I wonder if its possible to compile the >> > microchip stack into asm, and then wrap them up into functons that sdcc >> > can >> > handle? >> > Regards >> > Peter >> > >> > 2009/1/26 Ov3rM1nd <ove...@gm...> >> >> >> >> Hi Peter, >> >> >> >> I've tried to do what you are doing but without success. It would give >> >> a >> >> lot of work to redo the code, using sdcc syntax. Now i'm using >> >> Microchip C18 >> >> compiler to compile the tcp/ip stack and sdcc to compile my other >> >> applications. I'm running C18 compiler and MPLAB in Wine, and its >> >> working >> >> fine. >> >> >> >> Pedro Henrique Palhares. >> >> >> >> On Sun, Jan 25, 2009 at 8:49 PM, Peter Theobald <pe...@pt...> >> >> wrote: >> >>> >> >>> Hi List, >> >>> I'm very new to SDCC. I'm just starting to develop a project using a >> >>> pic18f66j60 device to connect a motor drive to an ip network. MY plan >> >>> is to >> >>> have a webserver (http/tcp) control protocol that can be accessed >> >>> through a >> >>> web browser or other software. So far i've had an attempt at getting >> >>> the >> >>> microchip free tcp/ip stack to compile in sdcc with the correct >> >>> target. I've >> >>> found a few complications, primarily language syntax such as packed >> >>> structs >> >>> and a rom declaration in a function header that doesn't seem to be >> >>> supported >> >>> by SDCC (I assume this is specific to the microchip compiler). Has >> >>> anyone >> >>> had any success compiling the microchip tcp/ip stack? or is there a >> >>> GPLd >> >>> stack that I could use instead. The pic18 device i'm planning to use >> >>> includes an integrated ethernet controller, but i'm open to >> >>> suggestions for >> >>> other controllers that might be easier to implement. >> >>> Any help would be gratefully received as i'm pretty stuck at the >> >>> moment >> >>> and not looking forward to rewriting a lot of microchip source code. >> >>> Regards >> >>> Pete >> >>> >> >>> >> >>> >> >>> ------------------------------------------------------------------------------ >> >>> This SF.net email is sponsored by: >> >>> SourcForge Community >> >>> SourceForge wants to tell your story. >> >>> http://p.sf.net/sfu/sf-spreadtheword >> >>> _______________________________________________ >> >>> Sdcc-user mailing list >> >>> Sdc...@li... >> >>> https://lists.sourceforge.net/lists/listinfo/sdcc-user >> >>> >> >> >> >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> >> This SF.net email is sponsored by: >> >> SourcForge Community >> >> SourceForge wants to tell your story. >> >> http://p.sf.net/sfu/sf-spreadtheword >> >> _______________________________________________ >> >> Sdcc-user mailing list >> >> Sdc...@li... >> >> https://lists.sourceforge.net/lists/listinfo/sdcc-user >> >> >> > >> > >> > >> > ------------------------------------------------------------------------------ >> > This SF.net email is sponsored by: >> > SourcForge Community >> > SourceForge wants to tell your story. >> > http://p.sf.net/sfu/sf-spreadtheword >> > _______________________________________________ >> > Sdcc-user mailing list >> > Sdc...@li... >> > https://lists.sourceforge.net/lists/listinfo/sdcc-user >> > >> > >> >> >> >> -- >> >> - Tristan >> >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by: >> SourcForge Community >> SourceForge wants to tell your story. >> http://p.sf.net/sfu/sf-spreadtheword >> _______________________________________________ >> Sdcc-user mailing list >> Sdc...@li... >> https://lists.sourceforge.net/lists/listinfo/sdcc-user > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > _______________________________________________ > Sdcc-user mailing list > Sdc...@li... > https://lists.sourceforge.net/lists/listinfo/sdcc-user > > -- - Tristan |