MMA8453 interface with BLE

RE: MMA8453 interface with BLE

Petter Myhre — Thu, 02 Feb 2017 06:53:11 GMT

Strange. Are you sure the pin is actually toggling? Have you checked with a logic analyzer? Have you tried to connect the pin to ground when you have a breakpoint in in_pin_handler()?

RE: MMA8453 interface with BLE

Murugan — Thu, 02 Feb 2017 05:21:31 GMT

yes i am tried but not yet get interrupt.

RE: MMA8453 interface with BLE

Petter Myhre — Wed, 01 Feb 2017 16:24:23 GMT

Seems to be working fine here. Have you tried to put a breakpoint in the start of in_pin_handler()?

RE: MMA8453 interface with BLE

Murugan — Tue, 31 Jan 2017 12:00:12 GMT

yes after optimization off i am getting returns 0x00000008. After command the nrf_drv_gpiote_init() this function the code is running but i cant get gpio interrupt.

RE: MMA8453 interface with BLE

Petter Myhre — Tue, 31 Jan 2017 11:08:20 GMT

Have you turned off optimizations? Options for Target->C/C++->Optimization: Level 0.

RE: MMA8453 interface with BLE

Murugan — Tue, 31 Jan 2017 05:37:40 GMT

Thank for reply. I already tested above you are mentioned i am always getting returns 0x00000000 But code is not run next line.

RE: MMA8453 interface with BLE

Petter Myhre — Mon, 30 Jan 2017 12:48:31 GMT

advertising_start() doesn't return anything, it's a void. I tested your project, nrf_drv_gpiote_init() returns 0x00000008, which is NRF_ERROR_INVALID_STATE. It is returned if the driver already has been initialized. You could easily have checked this yourself, just turn off optimizations and put a breakpoint on APP_ERROR_CHECK() below nrf_drv_gpiote_init();

RE: MMA8453 interface with BLE

Murugan — Fri, 27 Jan 2017 12:30:16 GMT

Thanks for reply. The advertising_start() returns always zero. But whenever where it is i call below function the system is going to be hang.

static void gpio_init(void)
{
    ret_code_t err_code;

    err_code = nrf_drv_gpiote_init();
    APP_ERROR_CHECK(err_code);
    
    //nrf_drv_gpiote_out_config_t out_config = GPIOTE_CONFIG_OUT_SIMPLE(false);

    //err_code = nrf_drv_gpiote_out_init(PIN_OUT, &out_config);
    //APP_ERROR_CHECK(err_code);

    nrf_drv_gpiote_in_config_t in_config = GPIOTE_CONFIG_IN_SENSE_TOGGLE(true);
    in_config.pull = NRF_GPIO_PIN_PULLUP;

    err_code = nrf_drv_gpiote_in_init(DEVICE_INT_PIN, &in_config, in_pin_handler);
    APP_ERROR_CHECK(err_code);

    nrf_drv_gpiote_in_event_enable(DEVICE_INT_PIN, true);
}

RE: MMA8453 interface with BLE

awneil — Fri, 27 Jan 2017 11:55:33 GMT

You didn't answer the questions:

Have you tried to debug? Are you able to get to advertising_start() if you put a breakpoint there? Have you checked the error handler?

RE: MMA8453 interface with BLE

Murugan — Fri, 27 Jan 2017 10:07:47 GMT

hi @ Petter Myhre, Any updates ??? i am waiting your reply.

RE: MMA8453 interface with BLE

Murugan — Thu, 26 Jan 2017 11:44:15 GMT

Thanks for reply.Here posted my complete code in answer.

RE: MMA8453 interface with BLE

Petter Myhre — Thu, 26 Jan 2017 11:30:26 GMT

Seems like you are using an allowed interrupt priority for the TWI peripheral. Have you tried to debug? Are you able to get to advertising_start() is you put a breakpoint there? Have you checked the error handler? Maybe you can upload your complete project so I can test it here?