1
USB Infrared Toy / Programming USBIRToy with PICKit3...
I would eventually like to make a custom USBIRToy firmware load. But in the meantime, I have managed to just about brick my USBIRToy. I'm not new to PIC's or MPLAB. I'm just not sure how the BOOT and APPLICATION code work together. For instance, I assumed when my USBIRToy was new it contained both BOOT and APPLICATION code. So, after some unsuccessful programming, I decided to return the PIC to it's original state. So I programmed it with the BOOT hex file (bootloader.hex) found in the USBIRToy.package.v22.zip. Then I programmed it with the APPLICATION hex file (USBIRToy.v22.hex) found in the same package.
Well, I noticed that MPLAB programmed both HEX images starting at address 0x0 (in the case of the BOOT hex 0x0 to 0x87f and in the case of the APPLICATION hex 0x0 to 0x3dff). It if fairly apparent that the BOOT was over written by the APPLICATION.
So, I'm thinking I still have a brick on my hands, right?
Is there a howto that describes how to write custom code for the USBIRToy?
And, is there a single HEX image of the USBIRToy as it leave the factory?
(i.e. Assuming the BOOT and APPLICATION should be both present leaving the factory, what can be done is to dump a HEX file out of a properly programmed 18F2550 from the beginning of the BOOT to the end of the APPLICATION. Then, such a HEX file can be very easily used to restore a bricked PIC to factory condition in a single operation.)
-thanks