nRF52 DK GPIOTE interrupt stops working after approx 400ms after startup.

RE: nRF52 DK GPIOTE interrupt stops working after approx 400ms after startup.

EricDelangis — Fri, 20 Mar 2020 17:31:35 GMT

Hi Kenneth,

I've lost too much time trying to get this working. Decided to create a simple app_timer to signal when to read the temperature probe.

RE: nRF52 DK GPIOTE interrupt stops working after approx 400ms after startup.

Kenneth — Wed, 04 Mar 2020 09:50:41 GMT

Hi,

I have tried to look at the code.

I think it is weird that your screenshots in https://devzone.nordicsemi.com/support-private/support/243221#permalink=533441 show PORT event and not IN event since you have used .hi_accuracy = true

I recommend to single step the code in nrf_drv_gpiote_in_init() to check why it doesn't run to nrf_gpiote_event_configure() in nrfx_gpiote_in_init(). Also set in_config.skip_gpio_setup = false; in gpio_init().

I notice you have configured many gpio's in general with sense directly (not used the nrf_drv_gpiote_in_init() to configure them and at the same time set NRFX_GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS to only 1). I am not sure if this is a good idea, maybe consider using nrf_drv_gpiote_in_init() for all pins you want to wakeup with sense and with the proper number of NRFX_GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS to sense the wakeup on the pins.

I think you should enable log output from nrfx_gpiote module, I think the nrfx_gpiote_irq_handler() may be executing here when failing, the question what it may be doing.

Also check out the pin configuration NRF_GPIO->PIN_CNF[D_TEMP_IRQ] when failing and working, to see if it has changed.

Best regards,
Kenneth

RE: nRF52 DK GPIOTE interrupt stops working after approx 400ms after startup.

EricDelangis — Tue, 03 Mar 2020 17:15:43 GMT

Hi Kenneth,

I am at a standstill until this problem is resolved. Have you had any success determining what the issue could be? Does the Softdevice use or control any GPIOTE resources that could be changing the settings that I set up during initialization?

RE: nRF52 DK GPIOTE interrupt stops working after approx 400ms after startup.

EricDelangis — Thu, 27 Feb 2020 17:16:00 GMT

If you do this, you will need to comment out the while statement at line 1266 that checks for the presents of Dallas part.

RE: nRF52 DK GPIOTE interrupt stops working after approx 400ms after startup.

EricDelangis — Thu, 27 Feb 2020 14:07:26 GMT

You can also set up another GPIO as an output and tie it to P0.25 to toggle the interrupt to simulate the Dallas onewire function.

RE: nRF52 DK GPIOTE interrupt stops working after approx 400ms after startup.

EricDelangis — Thu, 27 Feb 2020 13:43:10 GMT

Hi Kenneth,

Still no resolution on my end.

I think you can trick the system if you change line 927 to have an internal pullup, you should be able to manually trigger the gpiote interrupt with a ground wire on P0.25 on P4 of the dev board. It is set for a LoToHi transition on this pin. Also comment-out the init function void perfect_shower_init(void) at line 1255.

In a nutshell, what I am trying to do is to run the Dallas ds18B20 temperature sensor continuously. It takes 172ms per conversion so I can't use a delay function so I set up it's OneWire pin as an interrupt on pin P0.25. This pin will be held low by the DS18B20 while the conversion takes place then an external pullup resistor on our board pulls it high. (Hence the internal pullup requirement.) When an interrupt is generated the handler goes to read the temperature probe data. First it disables the interrupt so that when I read the probe the act of reading doesn't generate more interrupts. After the temperature data is read then another temperature conversion is immediately initiated and the interrupt is re-enabled and I go off to do other things for another 172ms.

The problem is that this process stops working after about 400ms. The last activity I see on the d_temp_irq line falls in line with my perfect_shower_init() initialization routine. After this, I never get any interrupts from the GPIOTE system. This seems to coincide with the ble_app_uart_c functions starting up.

RE: nRF52 DK GPIOTE interrupt stops working after approx 400ms after startup.

Kenneth — Thu, 27 Feb 2020 09:41:11 GMT

Any progress? I can compile and run the code, but it is stuck in perfect_shower_init() since I don't have an DS18B20 present. Any way I can run the code without it present to recreate the issue?

Best regards,
Kenneth

RE: nRF52 DK GPIOTE interrupt stops working after approx 400ms after startup.

EricDelangis — Wed, 19 Feb 2020 16:44:10 GMT

Hi Kenneth,

I've attached the entire structure. devzone.nordicsemi.com/.../nRF5_5F00_SDK_5F00_15.3.0_5F00_59ac345.zip

I've made no more progress with this.

RE: nRF52 DK GPIOTE interrupt stops working after approx 400ms after startup.

Kenneth — Tue, 18 Feb 2020 08:45:10 GMT

Have you gotten any further? It seems I need the entire structure yes (I need something self contained that compile out of the box).

Best regards,
Kenneth

RE: nRF52 DK GPIOTE interrupt stops working after approx 400ms after startup.

EricDelangis — Thu, 13 Feb 2020 22:08:28 GMT

Kenneth,

I ran your PerfShwr-Valve_fix.emProject and it compiled just fine on my end.

Eric

RE: nRF52 DK GPIOTE interrupt stops working after approx 400ms after startup.

EricDelangis — Wed, 12 Feb 2020 18:25:15 GMT

I"ve attached a screen shot of my build. It is working on my end. Should I try zipping up my entire Nordic directory structure so all files are included?

I did have a few dozen errors to clean up as I combined all the example programs that I need for my application. BSP files and sdk_config should be part of the zipped files I sent you but I can send the entire subdirectory structure if you need.

Also, to be clear, I am running SDK 15.3, SES 4.30 (although it works on all versions down to 4.10. I haven't tested older ones) and nRF52-DK.

RE: nRF52 DK GPIOTE interrupt stops working after approx 400ms after startup.

Kenneth — Wed, 12 Feb 2020 09:13:17 GMT

devzone.nordicsemi.com/.../examples.zip

I fixed the path by edit the .emproject files and search and replace (see example.zip). However the project still does not compile (seems to be some issue with bsp, possible other).

Kenneth

RE: nRF52 DK GPIOTE interrupt stops working after approx 400ms after startup.

EricDelangis — Wed, 12 Feb 2020 02:15:36 GMT

Kenneth,

For some reason, the compiler isn't finding files that seem to be in the relative path locations. That is why I had to add absolute paths.

RE: nRF52 DK GPIOTE interrupt stops working after approx 400ms after startup.

EricDelangis — Mon, 10 Feb 2020 17:58:54 GMT

I had the same problems when I merged the different example files. This is why I had to add paths for the files that weren't found. All I did was to locate the Nordic files that were needed and add their paths to the project. I don't think that I can "fix" that.

RE: nRF52 DK GPIOTE interrupt stops working after approx 400ms after startup.

Kenneth — Mon, 10 Feb 2020 12:32:13 GMT

I wasn't able to compile the project, something seems missing. Which project should I open in \pca10040\s132? Can you double check that it compiles when placed in a fresh installation of SDKv15.3?

Edit: I notice you are writing SES v4.3, I will try again.

Edit2: I notice some of the include paths go to folders that seems not to be relative (but absolute). Can you fix those?

Thanks,
Kenneth

RE: nRF52 DK GPIOTE interrupt stops working after approx 400ms after startup.

EricDelangis — Fri, 07 Feb 2020 19:15:29 GMT

Kenneth,

I give up. The zipped file is attached. Unzip in your examples folder. It will run on nRF52-DK, SDK 15.3, SES 4.3. If you change line 927 to have an internal pullup, you should be able to trigger the gpiote interrupt with a ground wire on P0.25 on P4 of the dev board. It is set for a LoToHi transition on this pin. Also comment-out the init function void perfect_shower_init(void) at line 1255.

Thanks devzone.nordicsemi.com/.../_2100_PerfShwrValve.zip

RE: nRF52 DK GPIOTE interrupt stops working after approx 400ms after startup.

EricDelangis — Fri, 07 Feb 2020 02:12:01 GMT

Kenneth,

When I setup a GPIOTE interrupt, how do I know what interrupt is being used? It's looking to me that my GPIOTE interrupt is being disabled by some other module such as: ble_stack_init(), gatt_init(), nus_c_init() or scan_init(). If I run the code continuously before enabling these functions, the interrupt works fine. This would account for the 400ms run time at startup.

If this is the case, how do I specify an interrupt that isn't used by the softdevice or other code?

RE: nRF52 DK GPIOTE interrupt stops working after approx 400ms after startup.

EricDelangis — Fri, 07 Feb 2020 00:14:49 GMT

Hi Kenneth,

Since this code is setting an irq for an external Dallas temperature device, I'm not sure how I can give you a copy of the code that you can run directly. However, I've setup 4 breakpoints and took 4 screen shots that show the GPIOTE registers after each. You can see what is going on from these.

What to do next?

RE: nRF52 DK GPIOTE interrupt stops working after approx 400ms after startup.

Kenneth — Thu, 06 Feb 2020 23:10:39 GMT

It is not that I don't believe you, but I am not aware of any issue that may be similar to what you describe. My best suggestion is to take a look at the gpiote example one more time, comment out everything in your project that is not related for gpiote until it works, and then comment in code again until it fails. If you are not able to find the root cause, then I need a project I can unzip to the example folder in the nRF5 SDK and run on a standard nRF52-DK (without any third party hardware attached).

I don't see any better suggestion, but please share any findings you may have.

Best regards,
Kenneth

RE: nRF52 DK GPIOTE interrupt stops working after approx 400ms after startup.

EricDelangis — Thu, 06 Feb 2020 22:18:54 GMT

Hi Kenneth,

I've traced the GPIOTE port enable setting to be performed by err_code = nrf_drv_gpiote_init(); in main.c.

the call to: nrf_gpiote_int_enable(GPIOTE_INTENSET_PORT_Msk); from nrfx_err_t nrfx_gpiote_init(void) in nrfx_gptioe.c sets the GPIOTE port enable bit.

My subsequent call to configure the pin PIN_IN:

nrf_drv_gpiote_in_config_t in_config =
{
.sense = NRF_GPIOTE_POLARITY_LOTOHI,
.pull = NRF_GPIO_PIN_NOPULL ,
.is_watcher = false,
.hi_accuracy = true,
};

doesn't change the port bit even though I am setting the hi_accuracy bit to true.

RE: nRF52 DK GPIOTE interrupt stops working after approx 400ms after startup.

EricDelangis — Thu, 06 Feb 2020 21:19:50 GMT

Hi Kenneth,

If you look at the first code segment I pasted in my first post, you will see that I have set high accuracy to (true) so I don't understand why I am getting the Port output enabled.

nrf_drv_gpiote_in_config_t in_config = GPIOTE_CONFIG_IN_SENSE_LOTOHI(true); // true = high accuracy

in_config.pull = NRF_GPIO_PIN_NOPULL;

Also, your links refer to:

Tasks and events pin configuration

Each GPIOTE channel is associated with one physical GPIO pin through the CONFIG.PSEL field.

When Event mode is selected in CONFIG.MODE, the pin specified by CONFIG.PSEL will be configured as an input, overriding the DIR setting in GPIO. Similarly, when Task mode is selected in CONFIG.MODE, the pin specified by CONFIG.PSEL will be configured as an output overriding the DIR setting and OUT value in GPIO. When Disabled is selected in CONFIG.MODE, the pin specified by CONFIG.PSEL will use its configuration from the PIN[n].CNF registers in GPIO.

I cannot find any modules that define CONFIG.MODE or CONFIG.PSEL. How do I make sure that I get high accuracy and that I am set to Event?

RE: nRF52 DK GPIOTE interrupt stops working after approx 400ms after startup.

Kenneth — Thu, 06 Feb 2020 20:34:49 GMT

The picture show that you have enabled interrupt on PORT event only (high accuracy false will do that), there will be no IN[] events, only PORT event:
https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52832.ps.v1.1/gpiote.html#register.INTENSET

The PORT events will trigger for all pins that have configured sense:
https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52832.ps.v1.1/gpio.html?#register.PIN_CNF-0

Note that sense is level triggered, not edge.

RE: nRF52 DK GPIOTE interrupt stops working after approx 400ms after startup.

EricDelangis — Thu, 06 Feb 2020 18:23:00 GMT

Hi Kenneth,

I've attached the GPIOTE registers here:

I believe that I've deactivated all button functionality. From what I can tell, there are no other calls to nrf_drv_gpiote_init(). No other calls in any other files are being linked in.

Please advise.

RE: nRF52 DK GPIOTE interrupt stops working after approx 400ms after startup.

Kenneth — Mon, 27 Jan 2020 12:15:27 GMT

Can you search through your code if you may be calling nrf_drv_gpiote_init() somewhere else? Can you set a breakpoint shortly after init the GPIOTE module and read out the GPIOTE peripheral registers and compare when it doesn't work? Also, check out if the GPIO pin configuration may have been reconfigured by other functionality in the code.

To view peripheral registers in breakpoints you can check out this reply (replace RADIO with GPIOTE in your case):
https://devzone.nordicsemi.com/f/nordic-q-a/56344/dynamic-switching-of-prefixes-not-working-with-esb/229153#229153

Best regards,
Kenneth