PSoC™ 4 Forum Discussions

Background to the issue:

When customers use PSoC Creater, sometimes in order to fix bugs or find problems, they often need to add customized test programs to the code in Generated_Source, but if they add user-defined code directly to the code in Generated_Source, it will be overwritten once it is recompiled, is there a way to make the code in Generated_Source not be overwritten? Is there a way to make sure that the code in Generated_Source will not be overwritten by the customer's own additions?

Solution:

1Macro Callbacks

Macro Callbacks is a term defined in PSoC Creator to call user code from macros specified in a Component's generated code. These macros can be used by defining them in the user-defined header file named cyapicallbacks.h. This file will be included in all generated source files that offer callbacks.

A callback requires you to complete the following.

• Define a macro to signal the presence of a callback (in cyapicallbacks.h ).
• Write the function declaration (in cyapicallbacks.h ).
• Write the function implementation (in any user file).

To complete the example, the cyapicallbacks.h file would include this code.

#define SimpleComp_1_START_CALLBACK

void SimpleComp_1_Start_Callback( void ).

In any other user file, you could include cyapicallbacks.h and write the SimpleComp_1_Start_Callback() function.

For example.

2,

Merge Regions

Merge Regions provide another method to insert user code, through the use of specially marked sections in generated code, such as.

/* `#START isr_Interrupt` */

/* `#END` */

Anything you place in this region will be preserved in subsequent updates of the file. If a subsequent version of the file does not contain the same named region, the entire region from the previous file will be copied to the end of the file and placed in comments.

smartconx_target@Q!w2e3r4t5y6u7i8o9p0||/t5/PSoC-4/PSoC-Creater-IDE-%E5%A6%82%E4%BD%95%E4%BF%AE%E6%94%B9-Generation-Code/td-p/492049

Background to the issue:

When using the Em_EEPROM function module of PSoC ™ 4 and using PSoC Creator to simulate and debug, the customer found that once the program runs to the "Em_EEPROM_Write" function, the simulation will be interrupted, and the following error message appears:

Problem Analysis:

1, Em_EEPROM implementation mechanism is in the chip's internal Flash divided into a region as Em_EEPROM storage space, so the erase and write of the analog Em_EEPROM is ultimately called to the internal Flash erase and write operations.

2, the operation of the chip internal Flash must use the internal clock, if the customer project is using an external clock, and did not turn on the internal clock, when writing FLash operation must be switched to the internal clock, wait for the Flash write operation is completed in the re-switching bit internal clock. After the write operation is completed, the internal clock is turned off during the process of switching to the external clock, which leads to the above exception error.

3, the user outside the use of Flash operation regardless of the time when the system uses the external clock need to turn on the internal IMO:

This avoids the need to simulate the project with internal flash writing operations.

smartconx_target@Q!w2e3r4t5y6u7i8o9p0||/t5/PSoC-4/PSoC-4-%E6%A8%A1%E6%8B%9FE2%E4%BB%BF%E7%9C%9F%E5%BC%82%E5%B8%B8%E4%B8%AD%E6%96%AD%E8%A7%A3%E5%86%B3%E6%96%B9%E6%A1%88/td-p/492044