Bootloader on dsPIC?
Bootloader on dsPIC?
Is there such a thing as a bootloader for the dsPIC family?
Hi,
Yes, Microchip AN1094. http://ww1.microchip.com/downloads/en/A ... 01094a.pdf
1. Ingenia: http://www.ingenia-cat.com/developmenttools.php
Commercial product, excellent support. CAN bootloader too. They also have a GPL version.
2. Microsockets: http://www.microsockets.com/resources.htm
Creative common, dsPIC33, PIC24.
3. The famous Tiny: http://www.etc.ugal.ro/cchiculita/softw ... loader.htm
Free, dsPIC30.
4. MSU: http://www.reesemicro.com/Home/pic24-so ... bootloader
Free, PIC24.
Any one of these can recompile bootloaders for the other 16bit families and devices.
Yes, Microchip AN1094. http://ww1.microchip.com/downloads/en/A ... 01094a.pdf
1. Ingenia: http://www.ingenia-cat.com/developmenttools.php
Commercial product, excellent support. CAN bootloader too. They also have a GPL version.
2. Microsockets: http://www.microsockets.com/resources.htm
Creative common, dsPIC33, PIC24.
3. The famous Tiny: http://www.etc.ugal.ro/cchiculita/softw ... loader.htm
Free, dsPIC30.
4. MSU: http://www.reesemicro.com/Home/pic24-so ... bootloader
Free, PIC24.
Any one of these can recompile bootloaders for the other 16bit families and devices.
My little contribute
http://mrmackey.no-ip.org/elektronik/ds30loader/
I've used this one and I think are really fantastic.
http://mrmackey.no-ip.org/elektronik/ds30loader/
I've used this one and I think are really fantastic.
Cheers
Nervous
Nervous
As nervous wrote, my bootloader supports dsPIC. It also supports PIC18 and PIC24.
It's fully open source and comes with one single ready to use mplab projects per family, supporting all devices in each family. These are some of the features:
* Checksum control
* Write verification
* EEPROM write
* Config write
* Device reset byt dtr or rts
* Device activation byt dtr or rts
* Supports over 300 different devices out of the box
See the homepage for more info and download
http://picbootloader.com
It's fully open source and comes with one single ready to use mplab projects per family, supporting all devices in each family. These are some of the features:
* Checksum control
* Write verification
* EEPROM write
* Config write
* Device reset byt dtr or rts
* Device activation byt dtr or rts
* Supports over 300 different devices out of the box
See the homepage for more info and download
http://picbootloader.com
Last edited by irdra on 29 Aug 2015 07:32, edited 1 time in total.
ds30 Loader - open source bootloader for PIC16, PIC18, PIC24, and dsPIC
http://mrmackey.no-ip.org/elektronik/ds30loader/
http://mrmackey.no-ip.org/elektronik/ds30loader/
Code protect
I got the ds30 loader working on a dsPic30F6012A- happy with it. But how can I prevent someone from reading the program out of the chip with a programmer? I tried setting "config __FGS, CODE_PROT_ON" in settings.inc. I then have to comment out the verify stage in the main bootloader loop (and just return an ACK). Now, although my user app seems to get downloaded OK, the bootloader never seems to jump to it. Or prehaps the bootloader is always resetting the micro. Or something else?
Any ideas or hints would be greatly appreciated.
Any ideas or hints would be greatly appreciated.
I've looked a bit deeper, and I think one would have to start messing with boot segments and general segments. Ds30Loader is also in the general segment at the moment along with the user application code. It would [possibly] need moving to a boot segment. The boot segment can only be at the start of memory, so the address calculations would have to change.
Whether or not this would give the ds30Loader the necessary "permission" to write to the general code segment when code protection is set, remains to be seen. I guess this is what Microchip are intending with their "Code Protection". Does anyone else have any experience or comments to share?
Whether or not this would give the ds30Loader the necessary "permission" to write to the general code segment when code protection is set, remains to be seen. I guess this is what Microchip are intending with their "Code Protection". Does anyone else have any experience or comments to share?