CCS C Software and Maintenance Offers
FAQFAQ   FAQForum Help   FAQOfficial CCS Support   SearchSearch  RegisterRegister 

ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

CCS does not monitor this forum on a regular basis.

Please do not post bug reports on this forum. Send them to support@ccsinfo.com
dspic30 Bootloader Question

 
Post new topic   Reply to topic    CCS Forum Index -> General CCS C Discussion
View previous topic :: View next topic  
Author Message
Guest
dspic30 Bootloader Question
PostPosted: Fri Oct 17, 2008 9:40 am     Reply with quote
Has anyone used the ingenia bootloader? So far it's the only bootloader I've been able to get to the point of loading a program on a dspic30. I realize this isn't ingenia's site, but they don't have a ton of documentation.

My question is this:

I get a warning that my hex file contains data in protected 'config' addresses, protected addresses will not be overwritten.

Even with a very simple blinking program, I get this error

Code:

#include <30F4011.h>
#device *=16
#FUSES NOWDT,XT_PLL16,NOCKSFSM,PUT64,NOBROWNOUT,NOPWMPIN,NOPROTECT,NOWRT,NODEBUG,NOCOE,ICS0,RESERVED             
#use delay(clock=117964800)

void main()
{
   while(1)
   {
     output_toggle(PIN_B0);  //hooked up to an LED
     delay_ms(500);
   }
}


what lines of this code would the CCS compiler place in configuration memory
asmallri



Joined: 12 Aug 2004
Posts: 1634
Location: Perth, Australia

View user's profile Send private message Send e-mail Visit poster's website

PostPosted: Fri Oct 17, 2008 10:52 am     Reply with quote
Everything in the #fuse directive is placed in protect memory.

Fuses configure the PIC for your target hardware platform. This is the same information that is required for a bootloader. As the bootloader is the first thing installed on the PIC, the bootloader's fuse setting will be inherited by the application program bootloaded to the PIC.

A bootloader usually silently discards the config records (fuses settings). In your case the bootloader issues a warning message. My suggestion is do NOT make any changes to the application program and simply ignore the bootloader warning message. If possible, modify the bootloader to prevent it from issuing this class of warning message.
_________________
Regards, Andrew

http://www.brushelectronics.com/software
Home of Ethernet, SD card and Encrypted Serial Bootloaders for PICs!!
Guest
PostPosted: Fri Oct 17, 2008 11:30 am     Reply with quote
Even when I comment out the #fuse statements, there are still values in the F80000 adresses.
asmallri



Joined: 12 Aug 2004
Posts: 1634
Location: Perth, Australia

View user's profile Send private message Send e-mail Visit poster's website

PostPosted: Fri Oct 17, 2008 11:54 am     Reply with quote
Anonymous wrote:
Even when I comment out the #fuse statements, there are still values in the F80000 adresses.



The hex file will still contain values at F80000 even if they are all 0xFF

The problem is the bootloader not the application.
_________________
Regards, Andrew

http://www.brushelectronics.com/software
Home of Ethernet, SD card and Encrypted Serial Bootloaders for PICs!!
Display posts from previous:   
Post new topic   Reply to topic    CCS Forum Index -> General CCS C Discussion All times are GMT - 6 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group