PSoC™ Creator & Designer Forum Discussions
My project is building for more than 5 minutes. I think its because PSoC Creator is compiling everyfile even if I make a small change. Is it possible to speed this up?
End-User License Agreement for ARM Keil Software Development Tools
SECTION 2 SEPARATE FILES AND THIRD PARTY TERMS内、
B. Windows Driver Development Kit redistributables.
See www.microsoft.com for more details.
If the code has
some = code;
some = other(code);
Then it should be possible to fold up whichever branch is unused to hide them from view. PSoC Creator only allows folding up the entire #if-#endif block, though.
Also, it should be possible to fold/hide unused code by default when a file is open so there is less clutter.
PSoC Creator 4.2 (184.108.40.2061)Show Less
Dear all PSoC enthusiasts.
I believe that my PSoC Creator has a little BUG that quite bothers me. Whenever I build a project the notice list does not clear, showing errors and alerts even after all of them were corrected, even the Build is succeed, but the list keeps full of past errors.
Have any of you guys faced the same issue already?
I can view the ADC conversion of thermistor voltage in oscilloscope, but LCD is not displaying any text and numbers.Show Less
I like to test Creator with new GNU ARM Embedded Toolchains, recently version 6.2 was released, so i installed it and set Creator to use it, now i'm unable to build the attached project, which is not using the EEPROM at all.
Creator is throwing the following error:
ERROR: .cyeeprom data will not fit in EEPROM
collect2.exe: error: ld returned 1 exit status
The command 'arm-none-eabi-gcc.exe' failed with exit code '1'.
Using version 5.4 of the GNU ARM Toolchain compile the same project successfully.
So, my question would be:
Why is the EEPROM used on the design if i'm not implicitly using it?
It does save any PSoC configuration?
Any pointer to cyeeprom usage on projects that doesn't use the EEPROM component would be appreciated.
Thanks in advance and happy holidays.
This post is kind of a follow-up of this other post http://www.cypress.com/forum/psoc-creator-software/unable-debug-newer-version-arm-gnu-toolchainShow Less
Would it make sense to change cytypes.h to use stdbool.h's bool type for CYBIT variables?
Currently, for non-PSoC3, it defines:
#define CYBIT uint8
But this means when you hover over a CYBIT variable, it shows "uint8" as the type, so it's not obvious if it's meant to be boolean or integer. If this were changed to bool type, it would show that when hovering over it, to clarify that the variable is meant to be true or false, not an integer.
#define CYBIT boolShow Less
How do you do a 'Save As' of a project so that you keep the original project intact and start a new one benefitting from all the code of the original?
There must be a better way than having to start a completely new project, having to cut and paste all the code from the original project to reuse it.
I had upgraded my system from Win10-32 bits to Win10-64 bits. I had absolutely no problems in the 32 bit machine except the SVG file display issue that I ignored.
A month ago I had an issue regarding the build of the PSoC1 software, refer(
that was corrected by removing the spaces in directory names.
Now my issue is that I get an error - sometimes, not always - when I try to program using a Miniprog ver 1.8
The error is
Failed to initialize PSoC3 ES0-2 operations
FAILED! Failed to initialize PSoC3 ES0-2 operations
I do not have anything with PSoC3. How do I remove this error. It takes place while verifying.
This with the built in programmer s/w in PSoCDesigner-5.4 build 3191
I tried using the programmer s/w separately (PSoC Programmer 220.127.116.1158)
There too, I get an error while verifying.
Please advise.Show Less