Em 26/3/2011 13:25, Andre Abelian escreveu:
>
> Hi Isaac,
>
> I use CCS compiler every day. I can tell CCS is my favorite compiler and =
has=20
> excellent=20
> tech support and they always help. I personally believe they are one of t=
he=20
> best.
> call 262-522-6500 #32 is Mark very nice guy, #85 is Richard very very=20
> knowledgeable guy
> and ask Darien for USB questions. now back to your question.


Yes, my client could request support.


> as far as boot loader you may end up using their own boot loader see ccs=
=20
> examples folder.


This boot-loader is for a very special application, I don't think any
existing boot-loader will work.


> Why do you want to change the stack size?


Because the application will call an external function that uses more stack=
..


>  compiler manages by itself.


The compiler cannot know how much memory an external function will use.
MPLAB C30 allows me to choose how much stack I want and even where it
will be located.


> how do you get W0?


It is in the assembly code.


>  what temp registers?.


The parameters are passed in fixed locations in RAM memory (File
Registers), like in the smaller PICs without a data stack.
The PIC24 and dsPIC devices are a completely different beast compared to
the smaller PICs (PIC12 and PIC16).
Restricting the programming model to the same model necessary for the
smaller PICs is too wasteful, preventing the use of the full potential
of the devices.

With 16kbyte of RAM, those devices can make use of truly recursive
functions, which the CCS C model prevents, besides other useful constructs.


>  what do you mean by generated code is poor?


Because it generates lots of unnecessary instructions and inefficient
sequences that other compilers optimize better.


>  how did you check it?=20


By analyzing the generated assembly code in the "Program Memory" window.


Best regards,

Isaac

--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.