Cypress Perform

Home > Design Support > Cypress Developer CommunityTM > Cypress Forums > PSoC® Software > *** ERROR 201: INVALID SYNTAX

Bookmark and Share
Cypress Developer CommunityTM
Forums | Videos | Blogs | Training | Rewards Program | Community Components



*** ERROR 201: INVALID SYNTAX
Moderator:
JFMD

Post Reply
Follow this topic



*** ERROR 201: INVALID SYNTAX

Azlan posted on 03 Dec 2010 1:28 AM PST
Senior Member
12 Forum Posts

 I am getting the following error when trying to build a PSOC3 project.

*** ERROR 201: INVALID SYNTAX
The command 'LIBX51.exe' failed with exit code '3'.
 
Any help welcome.
 




Re: *** ERROR 201: INVALID SYNTAX

posted on 09 Dec 2010 09:47 AM PST
Top Contributor
99 Forum Posts

Does this happen for every project you try to build?  I'm trying to better understand if you can build the example projects, but your projects fail, or if all fail.

 

-Bobby

 



Re: *** ERROR 201: INVALID SYNTAX

JJHawg posted on 22 Dec 2010 10:31 PM PST
Senior Member
11 Forum Posts

I have posted a simlar problem on a different board, and it probably should have been put here...

 

Last night I made an important breakthough. It appears that in the Beta 5, linking is done in two steps; first a bunch of ojbect files are put into a library file, then that libarary file is included with a bunch of other object files in a call to the linker.

 

At least one problem is that when PSoC Creator generates the command line to LIBX51, it doesn't put quotation marks around the destination path, so if you have a path that includes spaces, it will cause the syntax error. I copied/modified/pasted the generated command line into a DOS box, and the librarian worked correctly.

 

I am still having problems with this, but I think that I can compile a project, then manually link it... until Cypress can fix this.

 

I hope this helps,

Jim

 



Re: *** ERROR 201: INVALID SYNTAX

JJHawg posted on 22 Dec 2010 02:56 PM PST
Senior Member
11 Forum Posts

As long as I am talking about how PSoC Creator generates command lines to the compiler, librarian, linker, and others, I should add these to the list...

 

There is inconsistent use of forward and back slashes, single and double quotation marks, and full and relative file paths.






ALL CONTENT AND MATERIALS ON THIS SITE ARE PROVIDED "AS IS". CYPRESS SEMICONDUCTOR AND ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY OF THESE MATERIALS FOR ANY PURPOSE AND DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THESE MATERIALS, INCLUDING BUT NOT LIMITED TO, ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT OF ANY THIRD PARTY INTELLECTUAL PROPERTY RIGHT. NO LICENSE, EITHER EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, IS GRANTED BY CYPRESS SEMICONDUCTOR. USE OF THE INFORMATION ON THIS SITE MAY REQUIRE A LICENSE FROM A THIRD PARTY, OR A LICENSE FROM CYPRESS SEMICONDUCTOR.

Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Terms and Conditions of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Terms and Conditions of this site. Cypress Semiconductor and its suppliers reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.

Spec No: None; Sunset Owner: KXP; Secondary Owner: VWA; Sunset Date: 01/01/20