Customers Performing Own Upgrades. How Hard Can It Be?

[rsocor01]

For a tipical individual that wants to upgrade the programming in their PIC, I don't think the Microchip Bootloader program would be that complicated for him. If you create a good tutorial with pictures on how to use the Microchip Bootloader, I think that that's the way to go.

[towlerg]

@rsocor01 I suspect that the target user wouldn't know a PIC from a pick.

@timmers There are many PIC devices similar to *6K22 with USB builtin but I suspect you have already decided against porting. In which case CDC must look very attractive but I would suggest falsely so. Just a couple of ways that you can have HID, a cheap PIC with USB as a buffer or maybe MCP2210. BTW you do realize that USB bootloader is purely software.

Anyways, I leave you with this thought - CDC bad, HID good.

George

[retepsnikrep]

Perhaps I'm missing something. :?

Can you not supply or advise your customers to buy a cheap pic programmer and simply send them hex files.
The hex files could be zipped and password protected if required on an individual customer basis.

http://www.piccircuit.com/shop/pic-p...rogrammer.html

That's what I do. Same pic programmer covers all of my projects/products.
Even some very elderly punters have been able to cope with using pickit2 and the programmer.

Perhaps it's possible to use pickit 2 in a command line mode with file name in the script.

[towlerg]

Yes you are. He's trying to find a method for a non-technical person to upgrade a "black box", to repeat myself - I suspect that the target user wouldn't know a PIC from a pick.

George

[pedja089]

MikroE have nice little hid bootloader.
http://www.mikroe.com/img/developmen...der_window.jpg
It would be nice to have open source bootloader like that in PBP.

[Ioannis]

Hmm, if you send a hex file to your customer, how hard is to copy the circuit and use the hex on a new project, without you knowing it?

I prefer to keep my hex files really secret and away from any customer. Except if they have paid for it, and they own it.

Ioannis

[pedja089]

If loader is open source you can easily add encryption. Then you send encrypted file to customer, application send encrypted data to pic(prevent someone to try find encryption in exe file, or to tap communication). Also you could use every 4th byte, load dummy bytes in encrypted file, write file from bottom to top, etc. So hex should be pretty safe...
Searching forum I found this http://www.etc.ugal.ro/cchiculita/so...bootloader.htm, and it should be good starting point for pic firmware. App for PC shouldn't be problematic, read byte from file then send it to HID or serial port, easily to do in VB6...
But I'm not still sure how to use loader with PBP, how to remap interrupt vectors, etc...
Only thing is that I don't have enough time to try it. I thing it should be doable...
EDIT:
If someone really wants your hex, then he'll just send one or two mcu from your device to company like this http://itresearch.weebly.com/services.html, and copy your board.