task threads blocking the device connection.

RE: task threads blocking the device connection.

manoj97 — Wed, 12 Aug 2020 04:35:40 GMT

https://www.freertos.org/RTOS-task-priority.html

I referred the above link and given equal priority to the two tasks by enabling the "configUSE_TIME_SLICING" from 0 to 1 in FreeRTOSConfig.h

it worked.

RE: task threads blocking the device connection.

Wavecake — Tue, 11 Aug 2020 14:12:19 GMT

Use your debugger. Figure out where the program halts when the connection process fails. You should be able to tell if it is a memory issue or not. If the program hits the assert or goes to reset, you'll know it's a memory issue. If the debugger shows that the program continues to execute without issue, you'll know it's not a memory issue.

Definitely hook up the debugger and post your results.

RE: task threads blocking the device connection.

Wavecake — Tue, 11 Aug 2020 14:08:28 GMT

it doesn't look like they are using the task manager. They are using the FreeRTOS API.

I think you brought up a good point though. For two tasks at the same level, one will need to yield. In FreeRTOS you have the option to yield or add a delay. They delay effectively provides the yield. They have a delay in the device thread. They are missing a yield or a delay in the oled_thread.

Try adding taskYield or vTaskDelay() to oled_thread.

I'm not convinced this will solve the issue though. The connection process happens through interrupts, which supersede tasks in priority. They had a problem with the connection process.

RE: task threads blocking the device connection.

haakonsh — Tue, 11 Aug 2020 13:45:50 GMT

At what point in your threads do you call task_yield or task_events_wait?

From Experimental: Task manager docs:

task_create() creates and activates the task. If task is executed it will not be preempted by other task unless task explicitly triggers task switching. Task switch may be triggered by calling task_yield() or task_events_wait(). If task_yield() is called then task manager will switch to next active task. If there is no active task then switch will not occur. If task_events_wait() is called then context switch will occur if there are no events waiting for the task. task_events_wait() returns mask of events. Events are triggered by calling task_events_set() from any context.

RE: task threads blocking the device connection.

manoj97 — Tue, 11 Aug 2020 12:59:45 GMT

sorry i didn't get your point

RE: task threads blocking the device connection.

haakonsh — Tue, 11 Aug 2020 09:34:34 GMT

At what points does your tasks yield?

RE: task threads blocking the device connection.

manoj97 — Tue, 11 Aug 2020 09:27:29 GMT

 //main.c
 void DeviceApplicationTask(void)
{
    if (pdPASS != xTaskCreate(device_thread, "device", 256, NULL, 2, &m_device_thread))
    {
       APP_ERROR_HANDLER(NRF_ERROR_NO_MEM);
    }
}

void OLEDAutoRefreshTask(void)
{
    if (pdPASS != xTaskCreate(oled_thread, "device", 256, NULL, 2, &m_oled_thread))
    {
       APP_ERROR_HANDLER(NRF_ERROR_NO_MEM);
    }
}

  main()
  {
    DeviceApplicationTask();
    OLEDAutoRefreshTask();
  }

//oled.c
void oled_thread(void * arg)
{

   while(1)
   {
    menu_function(); //displays the screens when button press
    test_handler();   //handles the button operation
   }  
    nrf_delay_ms(200);

}

//task_thread.c
void device_thread(void * arg)
{
        ret_code_t err_code;

      twi_init();
      while(1)
      {

          temperature_read();   //temperature read from sensor

          if(tmp_flg==1)
          {
          notify_tmp();
          }
         if(hum_flg==1)
         {
          notify_hum();
         }
          if(soc_flg==1)
         {
          notify_soc();
         }
          if(soh_flg==1)
         {
          notify_soh();
         }
          vTaskDelay(500);
               
      }  
}

RE: task threads blocking the device connection.

haakonsh — Tue, 11 Aug 2020 09:08:36 GMT

Can you share the two threads with us?

RE: task threads blocking the device connection.

manoj97 — Tue, 11 Aug 2020 05:27:18 GMT

Present heap size is 1024

stack size is 2048

if I want to increase those size what is the value? how it is calculated?

How did my firmware fail?

When I power ON my device and trying to connect my device with nrf connect application.

When I click on connect in nrf connect application it will be in connecting state Foronly not able to connect the device you can see in below photo.

On application in logs I found this error: Error34(0x22):GATT CONN LMP TIMEOUT

for this I tried to comment on one task then the device is connected immediately.

This is the situation I want those tasks also.

RE: task threads blocking the device connection.

Wavecake — Mon, 10 Aug 2020 15:19:42 GMT

Can you tell how your firmware fails? A heap/memory problem would crash the firmware. Other kinds of problems may prevent the connection, but you will still be able to confirm the firmware runs without issue by pausing and continuing the debugger.

RE: task threads blocking the device connection.

manoj97 — Mon, 10 Aug 2020 14:43:48 GMT

2 tasks

1) temperature and humidity sensor with I2c communication

2) Oled connection with SPI communication.

if I comment anyone peripherals/tasks device will be paired (ble_communication).

RE: task threads blocking the device connection.

haakonsh — Mon, 10 Aug 2020 11:39:12 GMT

[quote user=""]When I comment on one task the device getting paired.[/quote]

Perhaps you care to share exactly what this task does?