The board is designed for USB applications, hence the need for 48MHz.
It's "possible" the bootloader overrides the CONFIGs, just like we can with a programmer (never used bootloader).
Robert
The board is designed for USB applications, hence the need for 48MHz.
It's "possible" the bootloader overrides the CONFIGs, just like we can with a programmer (never used bootloader).
Robert
That's correct. It's the bootloader that contains the CONFIG. When you download your PBP program using the bootloader then the CONFIG contained in your "download" will not be used. Exactly how it works may differ from bootloader to bootloader but basically the CONFIG is part of the bootloader and the bootloader protects itself from being overwritten.Maybe the bootloader don´t allows me to change Configs from my PBP program?
Had you been allowed to change the CONFIG via the bootloader then you could possibly set it to such a state the bootloader, which of course is just another piece of code in the PIC, wouldn't run as intended and you end up with a bricked PIC needing to be reprogrammed with a device programmer.
/Henrik.
I always used a bootloader because I used Rentron boards and have I always wondered why others coded configs. Now I know! Thanks guys one less thing to think about.
Steve Earl www.datageo.co.uk
Bookmarks