in gpiote handler,call xEventGroupSetBitsFromISR will cause hardfault

RE: in gpiote handler,call xEventGroupSetBitsFromISR will cause hardfault

Susheel Nuguru — Fri, 30 Apr 2021 10:25:51 GMT

FreeRTOSConfig.h file has this configTOTAL_HEAP_SIZE that you need to increase so that you can increase the task stack size when you are create the task using xTaskCreate

RE: in gpiote handler,call xEventGroupSetBitsFromISR will cause hardfault

great-master — Fri, 30 Apr 2021 09:44:20 GMT

how does modify the stack to bigger? in startup.s file?

RE: in gpiote handler,call xEventGroupSetBitsFromISR will cause hardfault

Susheel Nuguru — Thu, 29 Apr 2021 08:53:35 GMT

For some reason there is a memory corruption when you use xEventGroupSetBitsFromISR . This is most likely a stack overflow from one of your task. It seems that xEventGroupSetBitsFromISR uses more stack which might be overflowing into the neighboring task memery and corrupting it. I guess you can use the non ISR version as it does not look like you have a lot of nesting happening here.

RE: in gpiote handler,call xEventGroupSetBitsFromISR will cause hardfault

Susheel Nuguru — Tue, 27 Apr 2021 12:52:44 GMT

Sorry, I did not manage to finish looking at this today.

I will get more insights and reply to you tomorrow.

RE: in gpiote handler,call xEventGroupSetBitsFromISR will cause hardfault

great-master — Tue, 27 Apr 2021 07:19:34 GMT

thank you very much , wait your answer!

RE: in gpiote handler,call xEventGroupSetBitsFromISR will cause hardfault

Susheel Nuguru — Mon, 26 Apr 2021 11:59:19 GMT

This SDK should not have that bug i was mentioning before. So it is not related to the suspect i have in mind.

I will test your project soon and come back to you.

RE: in gpiote handler,call xEventGroupSetBitsFromISR will cause hardfault

great-master — Mon, 26 Apr 2021 07:32:44 GMT

nRF5_SDK_17.0.2_d674dde

RE: in gpiote handler,call xEventGroupSetBitsFromISR will cause hardfault

Susheel Nuguru — Mon, 26 Apr 2021 06:18:07 GMT

I think I have seen this error before in the earlier SDK where there was a bug related to the tick handling. Which SDK version are you using? I can give it a try to reproduce this hardfault with your project once you let me know the SDK version.

RE: in gpiote handler,call xEventGroupSetBitsFromISR will cause hardfault

great-master — Sun, 25 Apr 2021 02:23:52 GMT

devzone.nordicsemi.com/.../Controller.7z

Thanks for you help, I have attched the project, the project is running in PCA10040 Development Kit, When give P0.17 a raise level, it will trigger gpiote ISR, the it will set event bits and cause hardfault.

void alps_gpio_interrupt_handler(nrf_drv_gpiote_pin_t pin, nrf_gpiote_polarity_t action)
{
    BaseType_t higher_priority_task_woken, result;
    higher_priority_task_woken = pdFALSE;

    if(sample_task_event_handle == NULL)
    {
        NRF_LOG_WARNING("Task event is not create now\r\n");
        return;
    }

    if((pin == IMU_RDY_INT_PIN) && (action == NRF_GPIOTE_POLARITY_LOTOHI))
    {
#if 0
        result = xEventGroupSetBitsFromISR(
                                sample_task_event_handle, 
                                IMU_DATA_DRDY_EVENT, 
                                &higher_priority_task_woken);
        if(result != pdFAIL)
        {
            /* If higher_priority_task_woken is now set to pdTRUE then a context
            switch should be requested. The macro used is port specific and will
            be either portYIELD_FROM_ISR() or portEND_SWITCHING_ISR() - refer to
            the documentation page for the port being used. */
            portYIELD_FROM_ISR( higher_priority_task_woken );
        }
#else
        xEventGroupSetBits(sample_task_event_handle,IMU_DATA_DRDY_EVENT);
#endif
    }
}


static void sample_task_entry(void * pvParameter)
{
    UNUSED_PARAMETER(pvParameter);
    EventBits_t event;

    while (true)
    {
        event = xEventGroupWaitBits(
            sample_task_event_handle,
            IMU_DATA_DRDY_EVENT,
            pdTRUE,  /* bit should be cleared before returning. */
            pdFALSE, /* Don't wait for both bits, either bit will do. */
            portMAX_DELAY);
        if(event == IMU_DATA_DRDY_EVENT)
        {
            led_toggle(0);
        }
    }
}

RE: in gpiote handler,call xEventGroupSetBitsFromISR will cause hardfault

Susheel Nuguru — Fri, 23 Apr 2021 06:01:15 GMT

That is strange,

gpiote_handler is called from the ISR. Can you show me the screenshot of the calltrace of functions when the hardfault happened?

Also, have you changed any priorities values of the kernel itself?