PSoC™ Creator & Designer Forum Discussions

When a project is built, the .cyprj file often ends up with a change such as this, even though the project was not modified:

-<current_generation v="263" />

+<current_generation v="267" />

That creates confusion when using source control, because it's not clear whether there was any substantive change to the file that requires it to be committed. So we end up polluting the commits as well as creating confusion over whether someone changed something in the project.

It appears that a similar problem occurs with the .cyfit file.

How can we disable that behavior?

I expected that under Psoc Creator 4.3 --> menu bar --> Tools --> Options Under "project Management",  the setting for "My Template projects location:" could be used to specify the location that holds a number of snippet (xml) files.

This however did NOT show them as an active snippets (Psoc Creator 4.3 --> menu bar --> Edit --> Snippets --> Insert Snippet ... ).

When I added the snippets manually to the C:\Program Files (x86)\Cypress\PSoC Creator\4.3\PSoC Creator\conf\snippets\c directory they showed up (and were functional).

Is this the intended way to add snippets?

When a new project is created,it created a main (for example main_cm0p.c) which seems to follow a template. Is it possible to change that template (just the header comment part?

Hi all,

A new miniprog4 bought for kit050 programming.

Environment: PSOC programmer 3.27.1

Miniprog4 10 pin SWD to CYKIT-050 10 pin SWD

No external power supply for KIT050, miniprog4 supply for the kit.

However, sonething might be wrong with miniprog4! See below, toggle power button grey and Voltage row grey too.

Besides, I have another miniprog3 programmer, it can successfully download .hex file under the same situation(miniprog3 supply for KIT050).

And I have also tried to program using PSOC CREATOR 4.2, 'port acquire' failed.

Thanks if anyone have the same experience and share with me.

Jia

Hi all,

I'd opened the "Day020_BLE_UART". I'd used CY8C4247LQI-BL483 as central and  CYBLE-012011 as peripheral. They connect succesfully as I see in Teraterm. The problem is that I can send data from peripheral to central, but not viceversa.

Some help?

Thanks!

Hello,

I want to use PSoC Creator on a PC in my corporate network, but access to the Internet is restricted by firewall (not a Windows firewall, but a corporate firewall).

I would like to register the server address and port number accessed by PSoC Creator to the firewall white list.

Please tell me all the addresses and port numbers that may be accessed.
(For example, downloading code examples, new components, start page, etc...)

Regards,

Shimamura

Example CE220675 – PSoC 6 MCU: Motion Sensor does not appear in PSOC Creator, and only the PDF shows up in search.

Where can I download the code?

Thanks.

Hi.

I am using Psoc Creator 3.3 and am designing a Bootloader component to be used with a Bootloadable component.

One of the requirements is that the bootloader needs to validate itself before proceeding with bootloading, which is provided by the "Bootloader application validation" setting in the bootloader component in "TopDesign.cysch" file.

However, after building and flashing the project in Eclipse with a J-Link (not Miniprog3), the code hangs during checksum calculation. The reason is these two following lines in Bootloader_1.c:

const uint32 CYCODE Bootloader_1_SizeBytes = 0xFFFFFFFFu;
const uint32 CYCODE *Bootloader_1_SizeBytesAccess = (const uint32 CYCODE *)(&Bootloader_1_SizeBytes);

As you can see, the bootloader's size is hard coded and as a result it will calculate the checksum forever. I confirmed this by pausing the program with the debugger.

According to Cypress:

Bootloader application validation If this option is enabled, the bootloader validates itself by calculating the checksum and comparing it with the saved one that resides in the internal variable. PSoC Creator generates and puts the exact value into this variable during the post-build step.If validation does not pass, the device halts.If this option is disabled, the bootloader is executed even if it is corrupted. This can lead to unpredictable results.

this should be handled during post-build.

Am I missing a setting somewhere?

The toolbar that was there last week is gone. Once I deleted the software and reinstalled it, it didn't improve. (Deleted all Cypress folders)
Currently, I cannot compile or write.
OS: Windows10Pro

Hi,

i recently updated to Creator 4.3 from 4.2 and the programmer to the latest version. WIN10 16GB RAM. Before that I had only the common, mild issues such as: Creator from time to time closes suddenly and with no reason.

First Creator and programmer could not establish a connection to the target at all or even compiling did not start.

Then creator 4.3/Programmer/4.2 hanged at CyPPDeviceIOPlugin and did not start at all.

Many reinstallations with Registry cleanup etc later I still have the problem that creator (downgraded to 4.2 now) sometimes takes quite a while to start (CyPPDeviceIOPlugin again), that programmer/creator do not find the target at all or it takes very long.

Connection loss during flashing/debugging and nonsense error messages such as "KitProg version Expecting 2.20, but found 2.21. Please use PSoC Programmer GUI to upgrade firmware."

I had no hardware changes and the USB port never had nay problems with PSoC. I also tried different ports and cables. Same result.

What can I do to get the old stability back?

Reinstalling Windows definitely is no option!