Problem using GPIO- and BSP-module simultaneously

RE: Problem using GPIO- and BSP-module simultaneously

Ray Breslin — Tue, 11 Apr 2017 19:13:54 GMT

Problem finally solved... :)

This issue was caused by a missing adaption for handling the bsp-module in SDK v12.2.0, that required a change in the Makefile and the project-structure within Eclipse.

Previously in SDK v12.0.0 the bsp-sources where available through the examples/bsp-folder, while in SDK v12.2.0 they got moved to components/libraries/bsp. Since the SDK-structure for v12.2.0 didnt got setup properly with deleting all previous content of SDK v12.0.0, it caused an indexing-error in Eclipse so that the bsp-module-source still got referenced to the examples/bsp-location.

Somehow that also created a problem with handling the BOARD_PCA10040-flag properly, which basically made the functions in bsp_config() doing nothing at all. In addition to that the Makefile obviously needed certain changes in the SRC_FILES- and INC_FOLDERS-section (also including boards.c as new file).

Thanks again for your help!

RE: Problem using GPIO- and BSP-module simultaneously

Ray Breslin — Mon, 10 Apr 2017 13:19:24 GMT

Now I did run the test with disabling bsp_btn_ble_init(), but there was no change in the behaviour!

RE: Problem using GPIO- and BSP-module simultaneously

Ray Breslin — Fri, 31 Mar 2017 23:07:23 GMT

I will do that asap, but I cant do it during the next week, since I am on a business-trip! I will get back to you - thank you very much for your efforts so far!

RE: Problem using GPIO- and BSP-module simultaneously

Jørn — Fri, 31 Mar 2017 14:17:07 GMT

It is quite likely the timer has nothing to do with your errors, I just want to eliminate any possibility to be sure. What happens if you comment away the bsp_btn_ble_init function? Any change in behavior?

RE: Problem using GPIO- and BSP-module simultaneously

Ray Breslin — Fri, 31 Mar 2017 13:41:19 GMT

Well I actually do need the timer_clk to be initialized first, since I do want to have reliable timestamps for my log-messages and that was never a problem before! But I tried it as you said and it just made the entire situation worse, so that the log-output showed everything till the 2nd additional log-message in bsp_config() and then I even got a reset, which keeps repeating on the same spot everytime. It has to be something within bsp_config() because without it everything else runs fine, except the advertising...

RE: Problem using GPIO- and BSP-module simultaneously

Jørn — Fri, 31 Mar 2017 08:45:11 GMT

I see you enable the timer at the end of the timer_clk_init function. This is not optimal as the timer could potentially trigger events while your system is still running inits. Enabling timers is one of the last things you should do before entering your main while loop. Just to be sure it is not interfering with anything, could you try moving the timer enable to after all initialize functions are run?

RE: Problem using GPIO- and BSP-module simultaneously

Ray Breslin — Thu, 30 Mar 2017 14:47:09 GMT

I even added additional log-messages inside bsp_config() - one before bsp_init() and one more directly after bsp_btn_ble_init(), but before the previous "initialized"-message posted above. While the first one is displayed normally, the 2nd is also displayed but without the "initialized"-message afterwards!

RE: Problem using GPIO- and BSP-module simultaneously

Ray Breslin — Thu, 30 Mar 2017 14:42:46 GMT

Thats precisely my problem!

I did comment out everything related to GPIOTE and wake-on-motion, but I am not seeing any error-message at all... It is that just nothing happens after bsp_config() - no log output, just nothing!

Here is also my check_error_code()-function:

void check_error_code(const char* function_name, uint32_t err_code, int8_t err_position)
{
	#ifdef DEBUG_APP_ERROR_CODE
		if (err_code != NRF_SUCCESS) {
			printf("%s(): Error '%#04lx' [%d]\r\n", function_name, err_code, err_position);
		}// if (err_code != NRF_SUCCESS)
	#endif /* DEBUG_APP_ERROR_CODE */

	APP_ERROR_CHECK(err_code);
}

RE: Problem using GPIO- and BSP-module simultaneously

Jørn — Thu, 30 Mar 2017 14:29:44 GMT

Could you comment out the gpio_config function, or change the pin to one not used by the bsp_init function, to remove the GPIOTE conflict, and then run debug? It would be helpful to know exactly which error you are getting, and what part of the bsp_init function is triggering it.

RE: Problem using GPIO- and BSP-module simultaneously

Ray Breslin — Thu, 30 Mar 2017 14:12:53 GMT

Thank you for your replay Jorn and for doing the tests with my code!

While I do understand the behaviour for a) (which does make sense), I still cant get bsp_config() to run properly even if its standalone in b).

Here are some additional code-snippets from before and after the bsp_config()-call!

Contents of system-startup() [before]

static void timer_clk_init(void) { nrf_drv_timer_config_t timer_cfg = NRF_DRV_TIMER_DEFAULT_CONFIG; // Time(in milliseconds) between consecutive compare events uint32_t time_ms = 1; uint32_t time_ticks; uint32_t err_code = NRF_SUCCESS;

 APP_TIMER_INIT(...);

 err_code = nrf_drv_timer_init(...);

 time_ticks = nrf_drv_timer_ms_to_ticks(...);
 nrf_drv_timer_extended_compare(...);

 nrf_drv_timer_enable(&TIMER_CLK);

}

static void uart_init(void) { uint8_t uart_mode = NRF_LOG_ENABLED; uint32_t err_code = NRF_SUCCESS;

 if (uart_mode == 1)
 {
     err_code = NRF_LOG_INIT(NULL);
     check_error_code(__func__, err_code, 1);
 }
 else
 {
     ...

     APP_UART_FIFO_INIT(&comm_params,
                        UART_RX_BUF_SIZE,
                        UART_TX_BUF_SIZE,
                        uart_evt_handler,
                        APP_IRQ_PRIORITY_LOW,
                        err_code);
     check_error_code(__func__, err_code, 1);
 }// if (uart_mode == 1)

}

Contents of pm_config() [after]

static void pm_config(bool erase_bonds) { ble_gap_sec_params_t sec_param; ret_code_t err_code;

 printf("%s(): Peer Manager initializing...\r\n", __func__);

 err_code = pm_init();
 check_error_code(__func__, err_code, 1);

 if (erase_bonds)
 {
     pm_peers_delete();
 }// if (erase_bonds)

 memset(&sec_param, 0, sizeof(ble_gap_sec_params_t));

 // Security parameters to be used for all security procedures
 ...

 err_code = pm_sec_params_set(&sec_param);
 check_error_code(__func__, err_code, 2);

 err_code = pm_register(pm_evt_handler);
 check_error_code(__func__, err_code, 3);

 printf("%s(): Peer Manager initialized\r\n", __func__);

}

RE: Problem using GPIO- and BSP-module simultaneously

Jørn — Thu, 30 Mar 2017 13:10:05 GMT

Hello Ray Breslin

I copied your code and did a couple of tests. First a comment on the error you received from bsp_config(). I believe the NRF_ERROR_INVALID_STATE arises due to a conflict in GPIOTE channel assignments. You said in your comment that you use pin P0.16 for the wake up functionality. In your gpio_config function you assign a GPIOTE channel to this pin.

The bsp_config() function initializes the leds and buttons of the development kit. So when bsp_config() is called it too tries to assign a GPIOTE channel to pin 16, which is wired to button 4 on the development kit. The function performs a check, and notices the pin is already in use. It then generates the NRF_ERROR_INVALID_STATE error.

If I remove the gpio_config function in my test, everything functions as normal. If you still get errors when you comment away your gpio_config function, then there might be a problem in parts of your code, which you have not posted here. Now on to your questions

a) when initializing the bsp module, it configures pins P0.13 to P0.20 for leds and buttons. If you configure any of these pins before that, chances are they're gonna be overridden. As mentioned above, the bsp module uses GPIOTE for the pins, so keep that in mind when initializing your GPIOTE. In your case I think the best way would be to first initialize the bsp module, and then change the configurations for pin 16, and any other pin you use, to suit your needs. That way the bsp module is allowed to initialize as it should, before you change the functionality of the buttons or leds.

b) To my knowledge, it should not be necessary to make any adjustments to the bsp module or the order of initializations when changing from SDK 12.0.0 to SDK 12.2.0

Best regards

Jørn Frøysa

RE: Problem using GPIO- and BSP-module simultaneously

Ray Breslin — Thu, 30 Mar 2017 12:44:30 GMT

I used this definement here #define MOTION_IRQ_PIN 16 - but like I said the wake-on-motion-functionality isnt my problem! Even if I uncomment everything related to gpio_config() then I still got the same errors (which I cant see) for bsp_config()...

RE: Problem using GPIO- and BSP-module simultaneously

Jørn — Thu, 30 Mar 2017 12:13:41 GMT

What pin have you assigned to the MOTION_IRQ_PIN?