> Oooook,
>
> I am sorry I was so under-pressure that could not focus the real point of you.
> One more question, what if use the same C code and create a new project here
would it make me get rid of contacting him back???
>
> Thanks
I don"t think so as you clearly do not have the files thst he used to build the
project. As things are not running at the same rate it would be natural to
assume that the startup code has been edited to change PLL settings. All you
have is the standard startup code that will set the PLL up but possibly not the
same frequency.
Reply by aamir shakoor●February 16, 20112011-02-16
Oooook,
I am sorry I was so under-pressure that could not focus the real point of
you. One more question, what if use the same C code and create a new
project here would it make me get rid of contacting him back???
Thanks
--- On Wed, 2/16/11, Paul Curtis wrote:
From: Paul Curtis
Subject: RE: [lpc2000] CrossWorks lpc2138 Project build
To: l...
Date: Wednesday, February 16, 2011, 9:09 AM
> I right clicked and imported all the system files in
> System Files Folder, and built the project "ARM
flash
> release", No difference.
Of course not. I said:
> You (or more accurately, the person who provided
you
> the project) can break the dependence on the
package
> files by right clicking on the system files in
the.
All you have done is copy the files from one place to another, you don't
have the files that are quite probably different from the person who provided
you the project. Like I said, read what I wrote.
You need to get the person who provided you with the project files to send you
what he used to build it. What I described is how to bring those files in
locally by the other developer, who must do it, not you.
> I right clicked and imported all the system files
in
> System Files Folder, and built the project "ARM flash
> release", No difference.
Of course not. I said:
> You (or more accurately, the person who provided
you
> the project) can break the dependence on the package
> files by right clicking on the system files in the.
All you have done is copy the files from one place to another, you don't
have the files that are quite probably different from the person who provided
you the project. Like I said, read what I wrote.
You need to get the person who provided you with the project files to send you
what he used to build it. What I described is how to bring those files in
locally by the other developer, who must do it, not you.
Reply by aamir shakoor●February 16, 20112011-02-16
I right clicked and imported all the system files in System Files Folder, and
built the project "ARM flash release", No difference.
--- On Wed, 2/16/11, Paul Curtis wrote:
From: Paul Curtis
Subject: RE: [lpc2000] CrossWorks lpc2138 Project build
To: l...
Date: Wednesday, February 16, 2011, 6:48 AM
> Hi all,
> I got a problem if some one could help pls.
> I got a project created by one company (although one
guy works
> there), it is in crossworks IDE and lpc2138
processor. The hex
> file that is created by their system is 156 kb size.
But when
> I build the same project (release configuration), the
file is
> 177 kb size. Also the wake up (blink red led twice
with a
> difference of 200 ms) signals this files give are
faster then
> the hex created by their system. and the hex I create
by
> building project in my system does not work.
> Please can some one tell what problem it could be
(compiler options are
> inherited by the project).
If you were distributed with the correct project files and source files, and are
using the same version of the compiler and libraries, the only difference can be
the files that are installed as part of the package system or you are building
in a different configuration.
You (or more accurately, the person who provided you the project) can break the
dependence on the package files by right clicking on the system files in the
System Files folder and Importing them. You can also right click on the project
and import both the section placement and the memory map files which, again,
breaks the dependence on the package files.
Some customers wish to do this so everything is all in the project directories,
but then by breaking the ties to the package files they don't get updated
memory maps, headers, or startup code when new packages are released by us.
Reply by aamir shakoor●February 16, 20112011-02-16
Thanks for reply,I broke the dependencies as per your sugestions but same size
of hex file, I also compare opening this file in bonary editor and its different
from the one he built. What may be the difference in building configurations???
Are there more then one compiler versions in crossworks IDE? ans so with
libraries? if I inherit the project properties even????
RGDS
--- On Wed, 2/16/11, Paul Curtis wrote:
From: Paul Curtis
Subject: RE: [lpc2000] CrossWorks lpc2138 Project build
To: l...
Date: Wednesday, February 16, 2011, 6:48 AM
> Hi all,
> I got a problem if some one could help pls.
> I got a project created by one company (although one
guy works
> there), it is in crossworks IDE and lpc2138
processor. The hex
> file that is created by their system is 156 kb size.
But when
> I build the same project (release configuration), the
file is
> 177 kb size. Also the wake up (blink red led twice
with a
> difference of 200 ms) signals this files give are
faster then
> the hex created by their system. and the hex I create
by
> building project in my system does not work.
> Please can some one tell what problem it could be
(compiler options are
> inherited by the project).
If you were distributed with the correct project files and source files, and are
using the same version of the compiler and libraries, the only difference can be
the files that are installed as part of the package system or you are building
in a different configuration.
You (or more accurately, the person who provided you the project) can break the
dependence on the package files by right clicking on the system files in the
System Files folder and Importing them. You can also right click on the project
and import both the section placement and the memory map files which, again,
breaks the dependence on the package files.
Some customers wish to do this so everything is all in the project directories,
but then by breaking the ties to the package files they don't get updated
memory maps, headers, or startup code when new packages are released by us.
> Hi all,
> I got a problem if some one could help pls.
> I got a project created by one company (although one guy works
> there), it is in crossworks IDE and lpc2138 processor. The hex
> file that is created by their system is 156 kb size. But when
> I build the same project (release configuration), the file is
> 177 kb size. Also the wake up (blink red led twice with a
> difference of 200 ms) signals this files give are faster then
> the hex created by their system. and the hex I create by
> building project in my system does not work.
> Please can some one tell what problem it could be (compiler options are
> inherited by the project).
If you were distributed with the correct project files and source files, and are
using the same version of the compiler and libraries, the only difference can be
the files that are installed as part of the package system or you are building
in a different configuration.
You (or more accurately, the person who provided you the project) can break the
dependence on the package files by right clicking on the system files in the
System Files folder and Importing them. You can also right click on the project
and import both the section placement and the memory map files which, again,
breaks the dependence on the package files.
Some customers wish to do this so everything is all in the project directories,
but then by breaking the ties to the package files they don't get updated
memory maps, headers, or startup code when new packages are released by us.
Reply by aamir shakoor●February 16, 20112011-02-16
Hi all,I got a problem if some one could help pls.I got a project created by one
company (although one guy works there), it is in crossworks IDE and lpc2138
processor. The hex file that is created by their system is 156 kb size. But when
I build the same project (release configuration), the file is 177 kb size. Also
the wake up (blink red led twice with a difference of 200 ms) signals this files
give are faster then the hex created by their system. and the hex I create by
building project in my system does not work.Please can some one tell what
problem it could be (compiler options are inherited by the project).
Best regards,Aami
--- On Sun, 2/13/11, boB G wrote:
From: boB G
Subject: [lpc2000] Re: USB Class Suggestion
To: l...
Date: Sunday, February 13, 2011, 8:52 PM
