PSoC API Regeneration causes vanishing code - Cypress.com Forums http://www.cypress.com/? Re: PSoC API Regeneration causes vanishing code http://www.cypress.com/?rID=51318 Ah yes.. thanks! Somehow completely missed the obvious...

~Abhijit

]]>
Mon, 16 May 2011 06:32:45 -0600
Re: PSoC API Regeneration causes vanishing code http://www.cypress.com/?rID=51096 The code which has to be executed upon occurrence of interrupt should be written in the section CY_ISR(isr_xxx_Interrupt). And the statements which has to be executed has to be written between the statements

    /* `#START isr_rx_Interrupt` */

    /* `#END` */

The code written within this part will not be erased upon build.

The snapshot below shows the same:

]]>
Sun, 08 May 2011 12:59:13 -0600
Re: PSoC API Regeneration causes vanishing code http://www.cypress.com/?rID=51095 Abhijit,

 

Please don't forget to include the necessary header files in the ISR file. In this case, you'll have to include the header file of the UART component used (like UART.h). The extern declaration and header files to be included should be written between the  following lines

/* `#START isr_rx_intc` */

/* `#END` */

The snap shot below shows the same.

 

]]>
Sun, 08 May 2011 12:51:54 -0600
Re: PSoC API Regeneration causes vanishing code http://www.cypress.com/?rID=51093 In every Interrupt.c file(For example if the name of ISR component instance is isr1, isr1.c),  there is a dedicated region for defines and includes which looks like this, 

/* `#START isr_1_intc` */


/* `#END` */

As long as the includes, in your case the extern variable is placed within this start and end construct, even if a clean and build is performed the includes will be retained. Picture attached illustrates the same.

]]>
Sun, 08 May 2011 12:07:41 -0600