Will you please post your complete project, there might be settings that hinder your interrupt to be raised.
Use "File -> Create Workspace Bundle(minimal)" and upload the resulting archive (DO NOT use chrome, does not work)
Regarding Project: The interrupt type is "Derived" which is used for fixed-function blocks. Use "rising edge" here.
You do not need to use a control register, you may remove the "Hardware Connection" check un a pin and write directly wit Pinname_Write().
Regarding the "Small Window": Turn on "Compatibility Mode" in IE.
For simple projects, turning on led, your approach OK. But mechanical switches,
relays, etc.. have a nasty habit of bouncing on contact and release. So consider
using the glitch component when handling this problem.
I had it all configured with logic and a debouncer. But to make it simple I removed all but the basic.
However I think the board is no good. Nothing seems to generate a signal from the pushbuttons.
We did not have a case like you describe in the forum yet. *ALL* boards have been working and there was initially a self-test programmed into which you may reload and run again.
How did you confirm that no interrupt is generated? By LED not working or did you set a breakpoint in the interrupt handler?
Did you correctly support the required external connections to the LEDs?
Already checked the buttons.
The soldering around the cpu looks very dry and un flowed on the side with the IO im using. Ill going to reflow it and see what happens.
Bob. I can generate a interrupt and light the LED by inserting a not condition between the pin and the interrupt..
Thanks for the HW tip.
Im not the best programmer. But not the worse either. 😄
Is there a setting to prevent the IDE from erasing user code?
Well, when you invert the pin-signal with a NOT-gate there will be a rising edge that triggers the interrupt, quite o.k.
I always use the CY_ISR_PROTO() and CY_ISR() macros (all described in the "System Reference Guide" accessable from help menu) and the API isr_StartEx(). So I keep the interrupts in my own files and not within the generated sources which might be overwritten by accident.
Nobody questioned your programming skills and style (yet) so keep on coding...
I have learned (at a time where µPs where a lot slower) to NEVER connect an mechanical switch to an interrupt because the bouncing could easily fire a couple of hundred ints.
A switch can be polled easily and when you set up a timer that fires 100 times a second you may poll the switch(es) in the timer-int and still the system is not stressed much. Additionally this might be used as the point to introduce a self-written de-bounce routine.