Found it. I looked at the creator xml config file and it had content nullnullnull...
I deleted this config file and ran the program and it works ok now. Must have got corrupted somehow?
1 of 1 people found this helpful
I had a similar problem with PSoC Creator 3.3 CP3: each time I tried to build the project, cydsfit.exe flagged an error when it was attempting to synthesize a custom component in my PSoC Creator project.
The error message was of the type:
The instance '....', of component MY_COMPONENT, contains an error. Component MY_COMPONENT is not available.
Component security is disabled for the project <my_component_project>. If you trust the author of the project and wish to allow this component to run the code on your computer during the design process, select Tools->Options->Design Entry->Component Security and add the project folder to the approval list.
And this despite the fact that I "allowed" the custom component in Tools > Options > Design Entry > Component Security (i.e. I added its project folder to the list of trusted projects).
It turned out not being a problem with a corrupted project nor a corrupted PSoC Creator.
I noticed that the settings entered in Tools > Options > Design Entry > Component Security were never saved, and also all the other Workspace settings.
After some digging I found that PSoC Creator 3.3 stores all that information in the folder (in the case of PSoC Creator 3.3 and Windows XP):
C:\Documents and Settings\<user>\Local Settings\Application Data\Cypress Semiconductor\PSoC Creator\3.3\
(where <user> is the user login name on that PC and subfolder \3.3\ refers to PSoC Creator version 3.3: fortunately every PSoC Creator uses its own subfolder).
The content (files, subfolders) of that folder must have been corrupted.
It was enough to quit PSoC Creator, delete that folder and restart PSoC Creator.
The folder will be recreated and "Build" runs without errors.
By the way, the action that triggered all this mess was that I once cancelled a project build in progress (by pressing ctrl+break) because I had forgotten something. This seems to be a bug with PSoC Creator 3.3. Therefore my advice: never interrupt a build in progress. It's better to wait until it finishes even if you are going to ignore the output.