RE: SPI calls and bluetooth send from GPIOTE handler

Emil — Tue, 16 Jun 2015 10:30:40 GMT

Thanks for your quick answer!

I thought passing it to the scheduler is smart to not hinder the IRQ and to not cause issues. This is the right design, right?

There is nothing else in the IRQ handler. My "in_pin_handler" has nothing else than in the code I posted. It seems like my ISP is unstable (wiring problem). Good to know that my code is "clean"!

However, when I try to connect through the Nordic UART Android I get disconnected as fast as I connect.

#define APP_TIMER_MAX_TIMERS            (2 + BSP_APP_TIMERS_NUMBER)                 /**< Maximum number of simultaneously created timers. */
void in_pin_scheduler_func(void *data, uint16_t size)
{	
	uint8_t status = Adxl362_GetStatus();
	UNUSED_VARIABLE(status);

	int16_t x, y, z;
	Adxl362_GetAcceleration(&x, &y, &z);
	//
	sprintf((char *)&m_buffer[0], "%X (%d) - %d,%d,%d", status, status & (1 << 6) ? 1 : 0, x,y,z);
	ble_nus_string_send(&m_nus, m_buffer, sizeof(m_buffer));

	//nrf_drv_gpiote_out_toggle(BSP_LED_3);
}

Is this correct? I stopped initializing LEDs and buttons as you can see in main ()

EDIT: The m_buffer was too small for the string. How big strings can I send in one go?

EDIT2: Found it! BLE_NUS_MAX_DATA_LEN

RE: SPI calls and bluetooth send from GPIOTE handler

RK — Tue, 16 Jun 2015 09:14:08 GMT

Well no it's not supposed to hardfault, that would be bad.

Most common cause of hardfault is calling an sd_* function from an interrupt level higher (ie numerically lower) than the SVC call is set up to use, which is 2.

You're shuffling the GPIOTE interrupt servicing off to a scheduler routine, ok so what's in that runs in main thread context, so that shouldn't be it - you have anything else, anything in a timer handler, GPIOTE handler, any other handler at all which calls any kind of BTLE-related code which ends up calling an sd_* function? If so what's the priority of the context you're calling it in, if it's APP_HIGH, it's too high and the device will hardfault.

If not - what's the exact line of code you're crashing on?