nrf5280 re-config TRACEDATA pin as general gpio for pulse generation

RE: nrf5280 re-config TRACEDATA pin as general gpio for pulse generation

Vidar Berg — Tue, 09 Feb 2021 13:05:25 GMT

Hi Ziv,

The GPIOTE module must be initialized first with nrf_drv_gpiote_init() before you can assign the pin with nrfx_gpiote_out_init(). Have you done that?

Best regards,

Vidar

RE: nrf5280 re-config TRACEDATA pin as general gpio for pulse generation

ziv123 — Mon, 08 Feb 2021 13:56:05 GMT

hi Vidar

unfortunately my problems did not finish with this pin

i had in my code the "button_init()" function left from the 'app_ble_blinky' example, when i comment it then for some reason when trying to config that pin (p0_11) i get an error 'NRFX_ERROR_INVALID_STATE' here:

nrfx_err_t nrfx_gpiote_out_init(nrfx_gpiote_pin_t                pin,
                                nrfx_gpiote_out_config_t const * p_config)
{
    NRFX_ASSERT(pin < NUMBER_OF_PINS);
    NRFX_ASSERT(m_cb.state == NRFX_DRV_STATE_INITIALIZED);
    NRFX_ASSERT(p_config);

    nrfx_err_t err_code = NRFX_SUCCESS;

    if (pin_in_use(pin))
    {
        err_code = NRFX_ERROR_INVALID_STATE;
    }

my pin configuration looks like that:

 // init pin task for ppi use:
    nrf_drv_gpiote_out_config_t pin_toggle_config = GPIOTE_CONFIG_OUT_TASK_TOGGLE(false);
    err_code = nrf_drv_gpiote_out_init(HYDRATION_FREQ_OUTPUT_PIN, &pin_toggle_config);
    APP_ERROR_CHECK(err_code);

any idea what i am doing wrong ?

in the "custom_board.h" file i commented all the build in defines with that pin

hope to read from you soon

best regards

Ziv

RE: nrf5280 re-config TRACEDATA pin as general gpio for pulse generation

Vidar Berg — Thu, 04 Feb 2021 07:55:42 GMT

Hi Ziv,

It's perfectly ok to change board file as well. I don't see any problem with it.

Best regards,

Vidar

RE: nrf5280 re-config TRACEDATA pin as general gpio for pulse generation

ziv123 — Thu, 04 Feb 2021 07:36:41 GMT

hi Vidar

well i actually solved it differently eventually, changed the boards.h file like so:

elif defined (BOARD_D52DK1)
  #include "d52_starterkit.h"
#elif defined (BOARD_ARDUINO_PRIMO)
  #include "arduino_primo.h"
#elif defined (CUSTOM_BOARD_INC)
  #include STRINGIFY(CUSTOM_BOARD_INC.h)
#elif defined(REDENT_NOVA_BOARD)
  #include "bl652_sa_01.h"
#elif defined(AUDIO_STICKER_BOARD)
  #include "audio_sticker.h"
#else
#error "Board is not defined"

if you think it might cause some problems please inform

Best regards

Ziv

RE: nrf5280 re-config TRACEDATA pin as general gpio for pulse generation

Vidar Berg — Thu, 04 Feb 2021 07:21:47 GMT

Hi Ziv,

You can just change the LEDBUTTON_BUTTON assigment in main.c to a different button.

Best regards,

Vidar

RE: nrf5280 re-config TRACEDATA pin as general gpio for pulse generation

ziv123 — Wed, 03 Feb 2021 19:46:00 GMT

hi Vidar

the problem is that if i change setting in the pca10056.h file then it will be changed for all other projects using that board, same if i add another custom board since i allready have one

#elif defined(BOARD_CUSTOM)
  #include "bl652_sa_01.h"
  #include "audio_sticker.h"
#else
#error "Board is not defined"

i have 2 includes there

is there a way to corelate a specific board.h for each project ?

hope to read from you soon

best regards

Ziv

RE: nrf5280 re-config TRACEDATA pin as general gpio for pulse generation

Vidar Berg — Wed, 03 Feb 2021 07:50:10 GMT

Hi Ziv,

Yes, this error will be returned regardles of whether you are in debug mode or not. To fix this, you either need to change the pin assignment for button 1 to a different pin, or select another GPIO for your output.

PriyeshN, please post your question in a new thread. The problem you are describing appears to be unrelated to the problem OP had.

RE: nrf5280 re-config TRACEDATA pin as general gpio for pulse generation

ziv123 — Tue, 02 Feb 2021 16:01:17 GMT

Hi Vidar

so if i understand you correct the error i am getting has nothing to do with debug mode and will actually accrue also on running ?

RE: nrf5280 re-config TRACEDATA pin as general gpio for pulse generation

PriyeshN — Tue, 02 Feb 2021 15:07:09 GMT

Hi Vidar,

I'm not using default board configuration and have my own custom board configuration. I'm also initializing the pin using nrf_gpio_cfg_output() as I'm not using events on that line. and this function does not return anything.

For further elaboration, I'm not getting any error while initializing the pin. Things go weird when I set the line to HIGH and if TRACE is not used, I don't see any reason for my code to jump to unknown location in memory and stuck there.

Any thoughts you can share which can help me solve this.

RE: nrf5280 re-config TRACEDATA pin as general gpio for pulse generation

Vidar Berg — Tue, 02 Feb 2021 13:12:43 GMT

Hello,

nrf_drv_gpiote_out_init() will return the invalid state error if you try to initialize a pin that has already been assigned, and P0.11 will be assigned as BUTTON_1/BSP_BUTTON_0 if you are using the default board configuration (See "Using the SDK with other boards").

Best regards,

Vidar

RE: nrf5280 re-config TRACEDATA pin as general gpio for pulse generation

PriyeshN — Tue, 02 Feb 2021 11:41:47 GMT

I'm also looking an answer for this. I'm currently using custom board with JLink as my debugger and I'm setting P0.11 line for enabling a voltage booster. As soon as I enable, I see the debugging stalls, RTT prints are stopped and code reaches some undefined location.

Is there a way I can turn off TRACEDATA functionality so that I can use the line as plain GPIO. If yes, will that impact my debugging and RTT logging?

Setup - nrf52840, JLink, SDK v17 (latest), SES IDE