Good point...on storing the data. Just pass it thru, much easier. PIC1 acts like a portal for the data transfer. On the IR device, I can power cycle it...so that might be a solution. Have to think a bit more about that issue. Thanks for the response! Wouter van Ooijen wrote: > So, PIC1 just streams out from the serial memory up to PIC2, I don't see why you would need to store the image if PIC2 in PIC1. Whenever you would update that image, you might as well send it directly to PIC2 (via a pass-through in PIC1). That saves a lot of trouble and storage. > There is a third device, that talks to box2, > that also contains a PIC but has a IR data link. *the* issue with bootloaders is *how to force the target into bootload mode, even when the application is "not cooperative". The easy way is: reset the target, either via the MCLR or by a power cycle. How would you do this with your IR-communication? -- Wouter van Ooijen -- ------------------------------------------- Van Ooijen Technische Informatica: www.voti.nl consultancy, development, PICmicro products docent Hogeschool van Utrecht: www.voti.nl/hvu -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist --------------------------------- Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist