GPIOTE input pins dont work

RE: GPIOTE input pins dont work

LeonardPak — Mon, 02 Sep 2019 07:30:50 GMT

No, I used HITOLOW or LOWTOHI mode.

Thank you for your help!

RE: GPIOTE input pins dont work

Edvin — Wed, 28 Aug 2019 07:37:11 GMT

That is good news. I didn't understand exactly what the issue was. Didn't you already use toggle?

Best regards,
Edvin

RE: GPIOTE input pins dont work

LeonardPak — Tue, 27 Aug 2019 14:34:15 GMT

I dont now, why RTT Viewer doesnt work. But I find the solution! My problem is the same as this . Now all is well.

RE: GPIOTE input pins dont work

Edvin — Mon, 26 Aug 2019 07:40:58 GMT

[quote user="LeonardPak"]and rtt logging with RTT Viewer doesnt work.[/quote]

Why?

[quote user="LeonardPak"]I use define DEBUG, but I havent got hard error.[/quote]

Do you mean that it doesn't stop on line 73 in app_error.c?

If you want to check whether it is the application that contains a bug or not, you can try your project on a DK, and just test by shorting GND to the pins that you use as input (remember to set pullup in the configuration, since the DK doesn't have external pull-up resistors).

RE: GPIOTE input pins dont work

LeonardPak — Fri, 23 Aug 2019 14:31:36 GMT

NRF_LOG_ENABLED is set.

I can not use logging, because it`s a custom board, and it hasnt got any external pin for uart logging and rtt logging with RTT Viewer doesnt work.

I use define DEBUG, but I havent got hard error.

Now, I trying to find mistake in the board. Maybe, it is not problem in the code.

RE: GPIOTE input pins dont work

Edvin — Fri, 23 Aug 2019 13:07:12 GMT

Ok. And NRF_LOG_ENABLED is 0 or 1?

The reason I ask is because it sounds like somewhere in the project the application "crashes", and the most common reason is because an APP_ERROR_CHECK(err_code) receives an err_code != 0.

I don't know what HW you are testing on, but if you can connect an UART to it (if it is a DK, then it is connected to the on board Segger chip). Alternatively you can use the RTT backend if you have a segger debugger. You can use JLink RTT Viewer.

The error handler is a very useful tool while developing, and one way is to monitor it via the log. It will let you know if APP_ERROR_CHECK() receives != 0.

Another way is to define DEBUG in your preprocessor defines and set a breakpoint on line 73 in the app_error.c. But you may need to disable optimization to see what err_code it was and where it occured.

RE: GPIOTE input pins dont work

LeonardPak — Fri, 23 Aug 2019 11:27:20 GMT

Yes. I have this function and log_init(), but dont undestand, how it can help me.

// <h> nRF_Log 

//==========================================================
// <e> NRF_LOG_BACKEND_RTT_ENABLED - nrf_log_backend_rtt - Log RTT backend
//==========================================================
#ifndef NRF_LOG_BACKEND_RTT_ENABLED
#define NRF_LOG_BACKEND_RTT_ENABLED 0
#endif
// <o> NRF_LOG_BACKEND_RTT_TEMP_BUFFER_SIZE - Size of buffer for partially processed strings. 
// <i> Size of the buffer is a trade-off between RAM usage and processing.
// <i> if buffer is smaller then strings will often be fragmented.
// <i> It is recommended to use size which will fit typical log and only the
// <i> longer one will be fragmented.

#ifndef NRF_LOG_BACKEND_RTT_TEMP_BUFFER_SIZE
#define NRF_LOG_BACKEND_RTT_TEMP_BUFFER_SIZE 64
#endif

// </e>

// <e> NRF_LOG_BACKEND_UART_ENABLED - nrf_log_backend_uart - Log UART backend
//==========================================================
#ifndef NRF_LOG_BACKEND_UART_ENABLED
#define NRF_LOG_BACKEND_UART_ENABLED 1
#endif
// <o> NRF_LOG_BACKEND_UART_TX_PIN - UART TX pin 
#ifndef NRF_LOG_BACKEND_UART_TX_PIN
#define NRF_LOG_BACKEND_UART_TX_PIN 6
#endif

RE: GPIOTE input pins dont work

Edvin — Fri, 23 Aug 2019 11:22:01 GMT

If you use one of the examples with BLE, then you probably see some calls to NRF_LOG_INFO(); in the project, do you?

What is the following defines set to in your sdk_config.h:

NRF_LOG_ENABLED
NRF_LOG_BACKEND_UART
NRF_LOG_BACKEND_RTT

RE: GPIOTE input pins dont work

LeonardPak — Fri, 23 Aug 2019 11:17:59 GMT

What do you mean by logging?

// <o> GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS - Number of lower power input pins 
#ifndef GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS
#define GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS 8
#endif

RE: GPIOTE input pins dont work

Edvin — Fri, 23 Aug 2019 10:45:23 GMT

What is your GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS defined to in sdk_config.h?

And do you have logging enabled? Can you please try to define DEBUG in your preprocessor defines, and monitor the log? Does the log say anything?

BR,

Edvin

RE: GPIOTE input pins dont work

LeonardPak — Fri, 23 Aug 2019 09:17:10 GMT

Input pin has external pullup, no pullup settings in code. It switche like this ESE22MV21 . And it pulls down.

RE: GPIOTE input pins dont work

Edvin — Fri, 23 Aug 2019 09:07:09 GMT

How about your pullup/down settings on the input pins? How do you trigger the pins? The thing that you use to trigger them, does it pull up or down?

RE: GPIOTE input pins dont work

LeonardPak — Fri, 23 Aug 2019 08:51:31 GMT

err_code = 0 always. I have found than it doesnt connect with number of pins. So, if i config some pin (for example, 31), response of GPIOTE_IRQHandler will disappear. State in IN register is toggled, but CNF->SENS doesnt react

RE: GPIOTE input pins dont work

LeonardPak — Fri, 23 Aug 2019 08:37:14 GMT

No. it`s right.

RE: GPIOTE input pins dont work

Edvin — Fri, 23 Aug 2019 08:17:45 GMT

Hello,

[quote user=""]but if I config more than 3 pins, all signals disappear.[/quote]

It sounds like your error handler catches something. Have you tried to debug?

Probably one of your APP_ERROR_CHECK(err_code) receives an err_code != 0. Turn off optimization to be able to see the value of err_code while debugging, and set breakpoints on APP_ERROR_CHECK(). Which one has an err_code != 0?

(NRF_SUCCESS = 0)

RE: GPIOTE input pins dont work

tommy.lane — Thu, 22 Aug 2019 18:49:52 GMT

Just a guess, but make sure you're using the digital pin numbers, not the physical pin numbers.