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 CCS Technical Support
0x37AE halts

 
Post new topic   Reply to topic    CCS Forum Index -> General CCS C Discussion
View previous topic :: View next topic  
Author Message
Guest
0x37AE halts
PostPosted: Mon Apr 19, 2004 11:26 pm     Reply with quote
Friends,

Here's a uber-weird one: whatever instruction winds up at address 0x37AE of my .lst file, and I mean ANY kind of instruction, halts the processor. Just commenting out different lines makes different instructions wind up at this location, and it's the end of the line. Even the watchdog won't reboot it!

Does anyone have any idea what's up with this? If the code download "verifies" okay... then is this some kind of new weird boundary?

I haven't investigated this very fully... but when I saw that this was what was happening, I am pretty confused... and can only think of a hardware failure or witchcraft...

Thanks,

Smile Robert

ps. PIC18F8720, CCS v3.187
PCM programmer



Joined: 06 Sep 2003
Posts: 21708

View user's profile Send private message

PostPosted: Tue Apr 20, 2004 1:08 am     Reply with quote
I wonder if you have the ICD2 set so it only programs up to a
certain address, but your code actually extends beyond that point ?

To find this setup screen, go to the Programmer menu in MPLAB
(assuming MPLAB 6.xx ) and click on Settings. Then click on
the Program tab. See if it's set to "Manually select memories
and ranges". If so, then put it back in the mode that lets the
ICD2 select them.

If you're using ICD2 in debugger mode, then the Debugger
menu also has a similar screen.
Ttelmah
Guest
PostPosted: Tue Apr 20, 2004 5:05 am     Reply with quote
PCM programmer wrote:
I wonder if you have the ICD2 set so it only programs up to a
certain address, but your code actually extends beyond that point ?

To find this setup screen, go to the Programmer menu in MPLAB
(assuming MPLAB 6.xx ) and click on Settings. Then click on
the Program tab. See if it's set to "Manually select memories
and ranges". If so, then put it back in the mode that lets the
ICD2 select them.

If you're using ICD2 in debugger mode, then the Debugger
menu also has a similar screen.


The ICD, needs this space.
If you read the manual (...), it says:
"A small 'debug executive' program is loaded into the high area of program memory on the target PICmicro MCU. Since the debug executive must reside in program memory, the application program must not use this reserved space. The debug executive typically needs about 0x120 words of program memory."
The space needed is more than this on chips like the 18Fxx2.

You can still use the ICD2, as a programmer (dsable debug mode in the compiler fuses), but if the debugger is enabled, this program is there, and overwritting the area will cause very odd crashes...

Best Wishes
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