PSoC™ Creator & Designer Forum Discussions

I found PSoC Creator 4.0 can compile C++ source.

But text editor of PSoC Creator doesn't support C++, so keyword highlight, auto complete doesn't work.

So, I exported project to eclipse, but I have trouble in setting up eclipse to compile C++.

First, I exported project as C project, at that time, compile was successful.

After that, I added C++ nature by "File > New > Convert to a C/C++ project".

I set include path of c++ compiler same as c compiler.

Then,  I built the project, but eclipse output some errors as following.

"undefined reference to `__cy_regions`" in Cm3Start.c

"undefined reference to `__cy_stack`" in Cm3Start.o

How to fix that?

I have a trouble in adding existing header file and source file.

The directory structure is like following,

workspace folder/

        project folder(.cydsn)/

                 main.c

                 UserCode/

                        header.h

                        source.c

I added include path "./UserCode", so, I could call constants declared in header.h from main.c.

But, when I call the function declared in header.h and defined in source.c from main.c, 

PSoC Creator outputs error "undefined reference to the function".

When I create new header and source in PSoC Creator Workspace Explorer, and copy the contents from existing files, PSoC Creator outputs no error.

How to fix this error?

I've edited my code and now the indentation is wrong.

No problem, in every code editor I've seen you hit a command key and it re-indents the file properly.  

Sometimes you have to select the code you want to re-indent and then hit this command key. 

I know there must be a way to do this in PSoC Creator.

Can someone please tell me where it is?!

Hello,

I've been using the example project AN86526 to learn how to push a bootloadable from a host to my psoc. I've come across an issue with the checksums: regardless of whether I choose standard summation or crc-16 for the bootloader the cyacd file only has the standard summation checksum at the end of each line. I would like to employ the crc-16 check instead, is there a setting I'm missing?

Thanks

-Andrew

Hi,

I using PSoC creator 4.0, and the "target kit" is grayed out, when I try to create a new project. What is the issue here? How do I "ungray out" the target kit and choose a kit from this drop down?

I tried running PSoC creator as administrator on my PC, but I got the same result.

Regards,,

Vishnu

I feel silly asking this question, but I have not been able to figure out how to, for a while, enlarge any of the editor tabs to span the full window.

I am used to the eclipse tool implementations where double clicking on a particular tab will switch to full size, and then double click will resize it back to its position in the frames.

How is this done in PSoC Creator ?

Hi,

I'm enjoying the new features of PSoC Creator 4.0, but I would happily give them all up for something which would be so useful to our company: A pre-build step in the build process.

Background: We use SVN as a version control system. A nice feature we have in our firmware is that it's possible to ask it which SVN version of the code it has programmed into it. To achieve this, we have a Python script which you can run, which checks the SVN version of the code on disk, and generates a .H file with that number in it. When the code is compiled, that number is included in the code.

Ideally, that script would be automatically run every time the code is built, so that it's impossible to forget, and we can guarantee that the correct version number is compiled into the code.

Back when we used to use PIC microcontrollers, MPLAB had the option to add a pre-build step, and we'd put the python script into that. And so we could be sure that every MCU knew what version of the code it contained.

Problem: PSoC Creator doesn't have a pre-build step, so our engineers have to remember to run the script before each build. As you can imagine, it's possible for them to forget, and so we can never be 100% sure which firmware each MCU contains. 

Request: Please, please add a pre-build step option into PSoC creator. It's such a small feature. It's also useful for a range of other things, like running code generators (e.g. Flex and Byson).

Many thanks - Hugo

Hello,

I want to define a macro callback in a UART component by following the guide provided by Cypress. In the guide, it says that I have to define a macro in the file called "cyapicallbacks.h". However, the compiler isn't recognizing the defined the macro despite me putting the code in there. Then I realized that the project doesn't have #include "cyapicallbacks.h" written in any file anywhere. Is there a setting in the project that makes it so that somewhere in the generated code the cyapicallbacks.h file is included?

Thanks,

Alex

Hi 

I moved source files in my projects to folders to clean/make project more clear.

After this, few files are not being compiled, I am geting error:

arm-none-eabi-gcc.exe: error: .\CortexM0\ARM_GCC_493\Debug\sample_file.o: No such file or directory

It happens after Clean and built. When I compile those .c filest manualy from list (right mouse -> Compile_file) then .o files are generated.

But again, cleaning deletes them. 

What happened?