Hi Stev, I agree! See below. > > > > At times, it's not even possible to use C on the smaller ones. > > 3 level hardware stack with C? :) > > > So use a decent compiler that has a software stack. > > -- > cheers, > Stef Mientki > http://pic.flappie.nl > > I've used Bytecraft C for more than a decade now. In fact I also recently used it for a small project that used an RFPIC12F675. With the growing pains of that compiler I've had to develop an intimate understanding of what the compiler does and what the code it generates looks like. With only a few exceptions, I couldn't write it any tighter in assembly; so I don't. The 12F675 was a radio transmitter inside Wireless Operated Replica Mines (WORMs) used for testing demining equipment. The little RF transmitters are buried up to 25cm into the ground which can be wet, iron laded sand (such as on the Cambodia Thailand border). The demining equipment runs over this and the receiver listens for mines that are tripped. Then they go back over the area looking for all the pieces. Broken mines that never sent a message are considered mechanically destroyed. Broken or intact mines that sent a message are considered blown up. Intact mines that still function when the button is pressed are considered missed. The transmitter code which sends the bit stuffed preamble, ID and compliment of the ID is all written in Bytecraft C. You don't have to write in assembler but I think it's important to understand the assembler the compiler generates to create efficient C programs. Some statements become compact, others quite large strings of machine instructions. In the case of the WORM, the client was able to easily modify the code without impacting the application when then needed other information transmitted. http://www.itep.ws/pdf/WORMBrochure_LowResolution.pdf John Dammeyer Automation Artisans Inc. http://www.autoartisans.com Ph. 1 250 544 4950 > -----Original Message----- > From: piclist-bounces@mit.edu > [mailto:piclist-bounces@mit.edu] On Behalf Of stef mientki > Sent: Saturday, March 10, 2007 3:33 PM > To: Microcontroller discussion list - Public. > Subject: Re: [PIC] Why bother with Assembly? > > > -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist