PSoC™ Creator & Designer Forum Discussions

Hello

Although I am just debugging my firmware in PSoC Creator, I cannot show disassemble window. There is no information of the disassemble window in PSoC Creator User Guide. So Please let me know how I can run the window.

Best regards,

After building a project which has Amux1 and other components,  The API for Amux1_Start() is not available (same for other components).  There's Amux1_Stop(),  and in my other projects there is the _Start();  but not here.  Why would this be????

I would like to use a proximity detector, the application I'm looking for is:

When I put my finger close to a sensor , the sensor detect it.

the issue is that I need: while I keep my finger close to the sensor (1-6 minutes), the sensor still detect that and not calibrate itself and toggle the output.

The interface must be GPO and not I2C...!

Does CY8CMBR3102-SX1I apply my need?

Hello. Very new to PSOC tools and kits (started Friday) so may be wrong but we are experimenting with PSOC 4.1 and PSOC4 evalkit.

With the PSOC Creator 4.1 - unable to switch the Build Settings from DEBUG to RELEASE.

1) Can someone please confirm if the results are the same on your side?

Right mouse click on the project name -> Build Settings -> Change CONFIGURATION from DEBUG to RELEASE -> Apply -> OK.

Leave this pull down menu and enter again the same menu. For us, DEBUG is back again as the ACTIVE setting. Even if you attempt to make RELEASE as the ACTIVE setting, no go for us.

2) However, the pull-down setting in the toolbar does appear to work. Please confirm if this is true for you as well.

Toolbar selection appears to stick and is reflected in the above setting.

Compiler bug or a local issue??                                                                              

Hello,

I have to design a PCB using a capsens button sensor. As it is my first time design a board with cypress product, I have some questions about the layout:

-If the button sensor is on the top layer, can I have something, like the CY8CMBR3108 beneath it, or does it needs some clearance?

-I want to ad some LEDs for feedback, is it possible to put 2 in the middle of the sensor ( soldered on the bottom, facing a hole)? If I want to add other LED on th side, with the same technic, what is the minimal distance from the side of the sensor I can go?

-If I understand well this document http://www.cypress.com/file/41076/download page 81, a hatched ground must be present on layer 3, and on empty space of the bottom layer, but what about the top layer? Do I need an other hatched ground on the top layer with clearance around the sensor?

-Can I use the 3rd layer ( aka the ground layer I think) for rooting the non-capsense traces ?

Sorry if my questions seems trivial, but after reading the documentation I am not 100% sure and wanted some advice

Thanks in advance

In Creator 4.1 update 1, after grabbing from the repository I need to build twice.  To kick off the initial build, I use Build->Clean and Build All Projects.  The build will fail on a file generated by the fitter and take a long time to come back.  (The file seems to have a lot of null characters in it).  After the first build fails (takes about 3 or 4 minutes where Creator seems to be waiting for some sort of timeout), I then choose Build->Clean and Build All Projects a second time.  This time the build completes without errors within 30 or 40 seconds).

Only difficult aspect of the workspace is that the project is using an external library.  (The dependencies are set properly to depend on the external library, and the external library builds properly before getting to the main project where the build fails).  The file that is failing is not part of the library, but it is a simple clock signal being fed into the library using the schematic tool.

This issue is more of annoyance than anything.  The workspace is stored in a repository, so there is the possibility that the timestamps of all the files are essentially the same.  No generated files are stored in the repository (and doing a clean build should remove those files anyway).

I did not run into this issue on previous versions of Creator, but at that time I also did not have any external libraries (besides the standard ones) being linked to the application.