on further examination it turns out that the line
if rise_edge then GPIO0_IEV = (1<<3)
must be included to make the interrupt happen on the rising edge (otherwise it happens on the falling edge)
Chris

Thanks again, I got it to work on P0.3, although I had to "comment out" 2 lines that I thought you said should be there (see below). Chris 'LPC1114Int_tst3 this test routine demonstrates using an external interrupt on P0.3 #if defined(LPC1114) #define INT_STR "GPIO0.1" #endif dim e0 as integer dim s...

Thanks, the example works, but I can't figure out how to modify the example for an external interrupt coming in on, say, P0.3.
Chris

I could really use a sample program (using BASIC) of using an external interrupt on a PRO start board. Ultimately I would like to have 2 interrupting devices.
Thank you, Chris

I have a Super Pro, trying to get HWPWM to work. The following little test program will compile, but there is no output on IO(64) (which is channel 1) that I can see with my scope. Any ideas? Thanks, Chris

#include <HWPWM17.bas>
main:
HWPWM(1,1000,750)
end

I am trying to interface my Super Pro board (with Basic) to (up to six of) these new (and inexpensive) TOF VL53L1X distance sensors. These sensors only interface with serial I2C interface, and require special setup software (which I have not seen in Basic). Does anyone have a suggestion of where I c...

I just installed the latest Basictools on my Windows 10 PC. Everything had been working fine on my old XP machine (which just kicked the bucket), so I was surprised when I went to run the same programs on my new setup and all I get is "unreachable statement" errors on all my statements. I am using N...

I believe I have solved the problem of the program stopping. It turned out there was a loop in the interrupt sub that I just didn't see-in all the times I stared at it! But now I have some questions about interrupts, am I right that the interrupt line should be normally high and active low? Also, do...

Thanks Bruce for the suggestions. In my troubleshooting a new issue has made itself apparent, which is that after unit B sends an interrupt (or two) , unit A simply stops working, like it's hit an "end" command, (or stuck in a loop, and I think I've eliminated that possibly). The only "end" command ...