You are here

Creator best practice with ISR | Cypress Semiconductor

Creator best practice with ISR

Summary: 2 Replies, Latest post by repsoc on 28 Oct 2015 03:04 AM PDT
Verified Answers: 1
Last post
Log in to post new comments.
Juan-Carlos Furest's picture
8 posts


In the new Creator, there is the new feature to handle API callback that will handle also interrupts.

What will be the preferred way to code isrs:

  1. Add the code in the generated file between the defined region?
  2. Write the external function and register it with StartEx()?
  3. Use the cyapicallbacks.h mechanism?

Best regards


user_1377889's picture
9293 posts

Welcome in the forum, Juan-Carlos!

The API callbacks are for some special cases where the component does not offer an interrupt signal as the I2C for instance.

Usually, when the component has got an interrupt signal (or an output that can be used for that purpose) as an UART or ADC you just connect an isr-component to it and configure it as rising edge. In your code you specify the interrupt handler as

CY_ISR_PROTO(YourHandler); // Declaration only

CY_ISR(YourHandler)   // Definition

// Handler code goes here

And lastly the initialization with




repsoc's picture
18 posts

This is a good questions. That seems no bee very consistent.

I have a part with a ADC component (without ISR component! - PSoC 4 Creator 3.3).

The isr is a custom isr, as Bob writes, in main.c It works well. A separate isr-component was not necessary.


Log in to post new comments.