Add FreeRTOS to do a lot of caculation and BLE data data transmission in MutilRole device

RE: Add FreeRTOS to do a lot of caculation and BLE data data transmission in MutilRole device

Bruse — Wed, 08 Dec 2021 02:44:19 GMT

I have solved the issue causing by flash erasing. I use the queue mechanism like this:

		while(1)
		{				
			if(xQueueReceive(ble_task_handle,&ble_task_msg,portMAX_DELAY)==pdTRUE)							
			{					
				switch(ble_task_msg.task_id)
				{
					case APP_COMMAND_QUEUE_ID:				
							 process_ble_commands();	
					break;
					
					case WRITE_FLASH_QUEUE_ID:
							 flash_operate(fs_event_num);		
					break;
											
				}
				ble_task_msg.task_id = 0;
			}			
		}

RE: Add FreeRTOS to do a lot of caculation and BLE data data transmission in MutilRole device

Susheel Nuguru — Tue, 30 Nov 2021 06:19:18 GMT

[quote user="Bruse"]However, if I commen out if (pdPASS != xTaskCreate(app_task_demo, "TaskDemo", 256, NULL, 1, &m_demo_thread)), that is to say, the task app_task_demo has not been created, the flash erasing and writing is all OK.[/quote]

It does not sound to me that the taskCreate function was successful and it looks like your application is not handling that fault correctly. I would first advise you to find out the error code for that failure in xtaskCreate function and if it is due to insufficient heap memory, then you need to increase the heap size in configTOTAL_HEAP_SIZE in your FreeRTOSConfig.h file.

[quote user="Bruse"]But I meet other issue. I need to write some data to flash which is receive from UART. When it runs nrf_fstorage_erase() function, the code is dead and it couldn't run any more. [/quote]

There is no such thing as the code is dead, the PC of the CPU still needs to execute something so you need to figure out the context in which your program counter (PC) is still executing. Start your application in debugger after compiling it without any debug optimizations and when the error occurs, then halt the debugger to check the context in which your code is being executed. It could be a loop, app_error_check handler or an hardfault. Once you figured out why your code seems dead to you (most likely because it might be looping somewhere) then you can try to understand the nature of your problem.

RE: Add FreeRTOS to do a lot of caculation and BLE data data transmission in MutilRole device

Bruse — Tue, 30 Nov 2021 01:16:35 GMT

I also try to lock when flash is erasing like this:

			taskENTER_CRITICAL();
    		flash_clear();				
			taskEXIT_CRITICAL();

However,the code still would die and it couldn't run any more when it runs to flash_clear unless I reset or power up again.

Is there any solutions for this issue? Thanks.

RE: Add FreeRTOS to do a lot of caculation and BLE data data transmission in MutilRole device

Bruse — Mon, 29 Nov 2021 14:06:44 GMT

Hi,

I just add a delay vTaskDelay(xDelay) to the while(1) in the BLEAppTask task, then the two task could run, also I have add a while(1) to the app_task_demo task.

But I meet other issue. I need to write some data to flash which is receive from UART. When it runs nrf_fstorage_erase() function, the code is dead and it couldn't run any more.

static void BLEAppTask(void * pvParameter)
{	
	uint8_t task_run_count = 0;
	const portTickType xDelay = pdMS_TO_TICKS(50); 

		if (pdPASS != xTimerStart(m_battery_timer, OSTIMER_WAIT_FOR_QUEUE))
		{
				APP_ERROR_HANDLER(NRF_ERROR_NO_MEM);
		}		
		while(1)
		{	
			  process_ble_commands();				
				flash_operate(fs_event_num);
				taskYIELD();
				vTaskDelay(xDelay);	
		}
}

static void ble_task(void *arg)
{		
		advertising_start(); 	
		scan_start();                          // Start scanning for peripherals and initiate connection to devices which  advertise.	
}	
static void app_task_demo(void *arg)
{		
		
		if (pdPASS != xTimerStart(m_test_timer, OSTIMER_WAIT_FOR_QUEUE))
		{
				APP_ERROR_HANDLER(NRF_ERROR_NO_MEM);
		}	
		uart_printf("app_task_demo start.\n");
		
		while(1)
		{

		}
}	
static void run_task(void)
{
	nrf_sdh_freertos_init(ble_task, NULL);	                                 // Create a FreeRTOS task for the BLE stack.

    if (pdPASS != xTaskCreate(BLEAppTask, "BLEAppTask", 256, NULL, 2, &m_app_thread))
    {
        uart_printf("Failed to create BLEAppTask.\n");
    }

    if (pdPASS != xTaskCreate(app_task_demo, "TaskDemo", 256, NULL, 1, &m_demo_thread))
    {
        uart_printf("Failed to create TaskDemo task.\n");
    }
}
int main(void)
{
    ....
    ....
	run_task();
		
	uart_printf("MutilRole application start %s\n",FIRM_WARE_REVERSION);	
    vTaskStartScheduler();		

    for (;;)
    {	
		APP_ERROR_HANDLER(NRF_ERROR_FORBIDDEN);
    }
		
}

I refer to flash_fstorage example to do flash writing and the main code as follow:

nrf_fstorage_api_t * p_fs_api;

//uint32_t data_arry[5]={0x110A0B0C,0x220A0B0C,0x330A0B0C,0x440A0B0C,0x550A0B0C};

void fstorage_evt_handler(nrf_fstorage_evt_t * p_evt)
{
    if (p_evt->result != NRF_SUCCESS)
    {
        uart_printf("--> Event received: ERROR while executing an fstorage operation.\n");
        return;
    }

    switch (p_evt->id)
    {
        case NRF_FSTORAGE_EVT_WRITE_RESULT:
        {
            uart_printf("--> Event received: wrote %d bytes at address 0x%x.\n",
                         p_evt->len, p_evt->addr);
							
        } break;

        case NRF_FSTORAGE_EVT_ERASE_RESULT:
        {
            uart_printf("--> Event received: erased %d page from address 0x%x.\n",
                         p_evt->len, p_evt->addr);
        } break;
				
        default:
            break;
    }
}
NRF_FSTORAGE_DEF(nrf_fstorage_t fstorage) =
{
    /* Set a handler for fstorage events. */
    .evt_handler = fstorage_evt_handler,

    /* These below are the boundaries of the flash space assigned to this instance of fstorage.
     * You must set these manually, even at runtime, before nrf_fstorage_init() is called.
     * The function nrf5_flash_end_addr_get() can be used to retrieve the last address on the
     * last page of flash available to write data. */
    .start_addr = 0x3e000,
    .end_addr   = 0x3ffff,
};
static void print_flash_info(nrf_fstorage_t * p_fstorage)
{
    uart_printf("========| flash info |========\n");
    uart_printf("erase unit: \t%d bytes\n",      p_fstorage->p_flash_info->erase_unit);
    uart_printf("program unit: \t%d bytes\n",    p_fstorage->p_flash_info->program_unit);
		uart_printf("start_addr: \t0x%x\n",    p_fstorage->start_addr);
		uart_printf("end_addr: \t0x%x\n",    p_fstorage->end_addr);
    uart_printf("==============================\n");
}
void wait_for_flash_ready(nrf_fstorage_t const * p_fstorage)
{
    /* While fstorage is busy, sleep and wait for an event. */
    while (nrf_fstorage_is_busy(p_fstorage))
    {
       ;
    }
}

void flash_clear(void)
{
    ret_code_t rc = nrf_fstorage_erase(&fstorage, fstorage.start_addr, 1, NULL);
    if (rc != NRF_SUCCESS)
    {
        uart_printf("nrf_fstorage_erase() returned: 0x%x\r\n", rc);
    } 	
}
void flash_store(uint32_t *dat,uint16_t len)
{
		ret_code_t rc;
	  rc = nrf_fstorage_write(&fstorage, fstorage.start_addr, dat, len, NULL); //Write data to memory address 0x100000. Check it with command: nrfjprog --memrd 0x100000 --n 16
    APP_ERROR_CHECK(rc);
    wait_for_flash_ready(&fstorage);
    uart_printf("Done.\n");
}

void flash_load(uint32_t *dat,uint16_t len)
{
		ret_code_t rc;
	  rc = nrf_fstorage_read(&fstorage, fstorage.start_addr, dat, len); //Write data to memory address 0x100000. Check it with command: nrfjprog --memrd 0xFF000 --n 16
    APP_ERROR_CHECK(rc);	
}	


/**@brief   Helper function to obtain the last address on the last page of the on-chip flash that
 *          can be used to write user data.
 */
static uint32_t nrf5_flash_end_addr_get()
{
    uint32_t const bootloader_addr = NRF_UICR->NRFFW[0];
    uint32_t const page_sz         = NRF_FICR->CODEPAGESIZE;
    uint32_t const code_sz         = NRF_FICR->CODESIZE;

		uart_printf("bootloader_addr=%x page_sz=%x code_sz=%x\n",    bootloader_addr,page_sz,code_sz);
    return (bootloader_addr != 0xFFFFFFFF ?
            bootloader_addr : (code_sz * page_sz));
}		
void fstorage_init(void)
{		
    ret_code_t rc;	
		p_fs_api = &nrf_fstorage_sd;
		fstorage.start_addr = nrf5_flash_end_addr_get()- 0x1000;	
		fstorage.end_addr = fstorage.start_addr + 0x1000;
    rc = nrf_fstorage_init(&fstorage, p_fs_api, NULL);
    APP_ERROR_CHECK(rc);
		print_flash_info(&fstorage);

}
void flash_operate(fs_evt event)
{
		switch(event)
		{
			case FS_STORE_EVT:
				uart_printf("Store......\r\n");	
				break;
			
			case FS_ERASE_EVT:
					uart_printf("Erase......\r\n");
			//		flash_load((uint32_t *)&at_com_data,sizeof(at_com_data_t));	
    			flash_clear();
					flash_store((uint32_t *)&at_com_data,sizeof(at_com_data_t));			
					fs_event_num = FS_IDLE;
				break;			
		}
}

However, if I commen out if (pdPASS != xTaskCreate(app_task_demo, "TaskDemo", 256, NULL, 1, &m_demo_thread)), that is to say, the task app_task_demo has not been created, the flash erasing and writing is all OK.

Best regards,

Bruse

RE: Add FreeRTOS to do a lot of caculation and BLE data data transmission in MutilRole device

run_ar — Fri, 26 Nov 2021 09:52:30 GMT

Hi,
Please try to add the workaround for the issue to your code to see if that helps. Since there is a known issue, it's probably better to test that first, before starting to benchmark other functions.

One way to do the benchmarking is to add gpio toggling to parts of your code that you want to check run time for, then observe that using a logic analyzer.

RE: Add FreeRTOS to do a lot of caculation and BLE data data transmission in MutilRole device

Bruse — Fri, 26 Nov 2021 09:11:38 GMT

How to do bench marking of the various tasks?

Now I just have two task. One task(BLEAppTask) mainly is used for BLE data transmission. Another task(app_task_demo) is just used to start a timer to toggle a LED.

Should I merge BLEAppTask into the task which's created by nrf_sdh_freertos_init(). I have tried to do it as follow, but it couldn't funciton properly.

static void ble_task(void *arg)
{		
		advertising_start(); 	
		scan_start();                          // Start scanning for peripherals and initiate connection to devices which  advertise.	
	
		while(1)
		{
			  process_ble_commands();				
			flash_operate(fs_event_num);
			taskYIELD();
		}
}

nrf_sdh_freertos_init(ble_task, NULL);

I see some issues about nRF52 SDK on https://devzone.nordicsemi.com/f/nordic-q-a/34155/what-are-sdk-15-x-0-known-issues. Would these issues cause my issue？

Best regards,

Bruse

RE: Add FreeRTOS to do a lot of caculation and BLE data data transmission in MutilRole device

run_ar — Wed, 24 Nov 2021 12:03:47 GMT

Hi,

Have you done any bench marking of the various tasks you have? Sounds as you are running out of CPU time and would need to optimize some function or adapt you app to handle that in some way.

As for raising app priorities to a higher level, this could disturb the SD behavior and is not recommended. If you use the app high level for some of your tasks you need to make sure the sd has some time to run tasks in SD low priority as well, or it will not able to funciton properly.