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

List file content

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



Joined: 18 Nov 2013
Posts: 160

View user's profile Send private message

List file content
PostPosted: Tue Jun 09, 2015 10:00 am     Reply with quote

I'm curious about some assembly code that shows up in the list file.

I'm using v5.046 PCWHD with an 18F87J60. Naturally, the first include file is the device, 18F87J60.h. At the end of the device header file is #list. But since I don't want to list all the contents of the standard include files, I have a #nolist immediately after the device header file.

#include <18F87J60.h>
#nolist

Then at the beginning of my code I have a #list. Pretty basic.

In the list file, right after the memory usage header there is a goto statement followed by 70 lines of setup code. Again, expected. Then it shows the first line of the device header (#device PIC18F87J60) followed by 1510 lines of assembly code. What is all that code. Does the PIC need that much initialization code?? And why is it showing up in the list file?
temtronic



Joined: 01 Jul 2010
Posts: 9221
Location: Greensville,Ontario

View user's profile Send private message

PostPosted: Tue Jun 09, 2015 11:07 am     Reply with quote

Without seeing the code it's hard to say what it is, but there's a lot of code needed for USE RS232(...) as well as printf...... .
As to what it is, you can decode it all by looking at the PIC datasheet's 'registers' and 'instruction set'.

Jay
Ttelmah



Joined: 11 Mar 2010
Posts: 19499

View user's profile Send private message

PostPosted: Tue Jun 09, 2015 11:43 am     Reply with quote

Try it without your nolist/list statements.

#nolist, turns off listing of the CCS code, but leaves _your_ code still being listed.

There is a #nolist already at the start of the processor include file.

Your #list is turning back on the listing of the CCS code used in your routines.

Now it is impossible to know what your block of assembler is actually for. However there will be large blocks for const arrays, the RS232 code, any routines for things like I2C. Do you have interrupts being used?. etc. etc..
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