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

18F45K22 and 18F46K22

 
Post new topic   Reply to topic    CCS Forum Index -> General CCS C Discussion
View previous topic :: View next topic  
Author Message
dyeatman



Joined: 06 Sep 2003
Posts: 1934
Location: Norman, OK

View user's profile Send private message

18F45K22 and 18F46K22
PostPosted: Sat Apr 20, 2013 9:32 am     Reply with quote

I went back to open up an old thermostat interface project originally built
under 4.137. After compiling, CCLoad with the ICD-U64 gives me a corrupt
hex file with 4.139, 4.140 and 4.141 versions.

With 4.137 and 4.138 the Hex file is good again. Anyone else seen this?

CCLoad complains of a bad start memory location in 4.139, 4.140 and 4.141.

This happens with both the 18F45K22 and the 18F46K22
_________________
Google and Forum Search are some of your best tools!!!!
asmboy



Joined: 20 Nov 2007
Posts: 2128
Location: albany ny

View user's profile Send private message AIM Address

PostPosted: Sat Apr 20, 2013 10:43 am     Reply with quote

I have used 18f46k22 under 4.135 using both pwms and max ADC resolution, rs232, pretty full i/o situation.

Just recompiled under 4.141 and had slight file size difference - but no issue with compile error or running correctly.
dyeatman



Joined: 06 Sep 2003
Posts: 1934
Location: Norman, OK

View user's profile Send private message

PostPosted: Sat Apr 20, 2013 10:53 am     Reply with quote

The program shows as compiling with no errors. Only the corrupted hex file
when loaded by CCS Load.

Are you using CCSLoad and/or the U64?
_________________
Google and Forum Search are some of your best tools!!!!
asmboy



Joined: 20 Nov 2007
Posts: 2128
Location: albany ny

View user's profile Send private message AIM Address

PostPosted: Sat Apr 20, 2013 11:58 am     Reply with quote

Quote:

Are you using CCSLoad and/or the U64?


NEITHER ---
i use the MEI programmer and L O V E it .......
no issue loading .hex file
PCM programmer



Joined: 06 Sep 2003
Posts: 21708

View user's profile Send private message

PostPosted: Sat Apr 20, 2013 12:27 pm     Reply with quote

Possible problems could be:

1. Certain compiler versions may generate corrupt hex files.
2. Your verison of CCSLoad is falsely reporting corrupt hex files.
3. Some other problem, such as configuration settings in the
compiler or CCSLoad, or a hard disk corruption issue.

Tests:
You could use the File/Import feature of MPLAB and test if the file
imports without errors. Set the PIC in the Configure / Select Device
menu before importing.
dyeatman



Joined: 06 Sep 2003
Posts: 1934
Location: Norman, OK

View user's profile Send private message

PostPosted: Sat Apr 20, 2013 1:12 pm     Reply with quote

Thanks guys, with the additional info I agree that it looks like a CCSLoad
problem. First I'll roll back to the 4.137 CCSLoad to see what happens.

I don't have MPLab installed but I'll try that if the CCSLoad regression
doesn't help.
_________________
Google and Forum Search are some of your best tools!!!!
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