After a few days of head pounding, I’ve traced a problem: enabling vTaskList with: ~~~

define configUSETRACEFACILITY 1

define configUSESTATSFORMATTING_FUNCTIONS 1

~~~ …causes FreeRTOS to halt at vPortFree(). vTaskList worked fine in 7.0 and 7.3, and did not require setting these constants. I have not touched the memory management scheme. Looked at which memmang file has been selected and see** heap_1.c** How to fix? Here’s the entire config: ~~~

ifndef FREERTOSCONFIGH

define FREERTOSCONFIGH

/* For documentation for all the configuration symbols, go to: * http://www.freertos.org/a00110.html. */

if defined (GNUC) || defined (ICCARM)

/* Important: put #includes here unless they are also meant for the assembler. */

include <stdint.h>

void asserttriggered( const char * file, uint32t line );

endif

define configUSE_PREEMPTION 1

define configUSEIDLEHOOK 0

define configUSETICKHOOK 0

define configPRIO_BITS 2

define configCPUCLOCKHZ ( 8000000 )

define configTICKRATEHZ ( ( TickType_t ) 1000 )

define configMAXPRIORITIES ( ( uint32t ) 5 )

define configMINIMALSTACKSIZE ( ( uint16_t ) 100 )

/* configTOTALHEAPSIZE is not used when heap_3.c is used. */

define configTOTALHEAPSIZE ( ( size_t ) ( 15000 ) )

define configMAXTASKNAME_LEN ( 8 )

define configUSETRACEFACILITY 1

define configUSESTATSFORMATTING_FUNCTIONS 1

define configUSE16BIT_TICKS 0

define configIDLESHOULDYIELD 1

define configUSE_MUTEXES 1

define configQUEUEREGISTRYSIZE 0

define configCHECKFORSTACK_OVERFLOW 0

define configUSERECURSIVEMUTEXES 1

define configUSEMALLOCFAILED_HOOK 0

define configUSECOUNTINGSEMAPHORES 1

define configUSEQUEUESETS 1

define configGENERATERUNTIME_STATS 0

define configENABLEBACKWARDCOMPATIBILITY 1

/* Co-routine definitions. */

define configUSECOROUTINES 0

define configMAXCOROUTINE_PRIORITIES ( 2 )

/* Software timer definitions. */

define configUSE_TIMERS 1

define configTIMERTASKPRIORITY ( 2 )

define configTIMERQUEUELENGTH 2

define configTIMERTASKSTACK_DEPTH ( 80 )

/* Set the following definitions to 1 to include the API function, or zero to exclude the API function. */

define INCLUDE_vTaskPrioritySet 1

define INCLUDE_uxTaskPriorityGet 1

define INCLUDE_vTaskDelete 1

define INCLUDE_vTaskSuspend 1

define INCLUDE_xResumeFromISR 1

define INCLUDE_vTaskDelayUntil 1

define INCLUDE_vTaskDelay 1

define INCLUDE_xTaskGetSchedulerState 1

define INCLUDE_xTaskGetCurrentTaskHandle 1

define INCLUDE_uxTaskGetStackHighWaterMark 0

define INCLUDE_xTaskGetIdleTaskHandle 0

define INCLUDE_xTimerGetTimerDaemonTaskHandle 0

define INCLUDE_pcTaskGetTaskName 0

define INCLUDE_eTaskGetState 0

/* Normal assert() semantics without relying on the provision of an assert.h header file. */

define configASSERT( x )

    if( ( x ) == 0 ) { taskDISABLE_INTERRUPTS(); for( ;; ); }

/* Definitions that map the FreeRTOS port interrupt handlers to their CMSIS standard names – or at least those used in the unmodified vector table. */

define vPortSVCHandler SVC_Handler

define xPortPendSVHandler PendSV_Handler

define xPortSysTickHandler SysTick_Handler

/* The lowest interrupt priority that can be used in a call to a “set priority” function. */

define configLIBRARYLOWESTINTERRUPT_PRIORITY 0x0f

/* The highest interrupt priority that can be used by any interrupt service routine that makes calls to interrupt safe FreeRTOS API functions. DO NOT CALL INTERRUPT SAFE FREERTOS API FUNCTIONS FROM ANY INTERRUPT THAT HAS A HIGHER PRIORITY THAN THIS! (higher priorities are lower numeric values. */

define configLIBRARYMAXSYSCALLINTERRUPTPRIORITY 10

/* Interrupt priorities used by the kernel port layer itself. These are generic to all Cortex-M ports, and do not rely on any particular library functions. */

define configKERNELINTERRUPTPRIORITY ( configLIBRARYLOWESTINTERRUPTPRIORITY << (8 – configPRIOBITS) )

define configMAXSYSCALLINTERRUPTPRIORITY ( configLIBRARYMAXSYSCALLINTERRUPTPRIORITY << (8 – configPRIOBITS) )

endif /* FREERTOSCONFIGH */

~~~

I posted the v7 config.. just updated it to that used with v8… /m

Well, as I am using ASF (should have mentioned this)… I looked back inside the FreeRTOS selection mechanism that ASF provides. There’s a hidden additional selection to choose the memory management model. I chose 4, which seems to be the most recommended, and no crash. However, now the task is called much more frequently. It’s set to 1000 ticks, which equated to 1S. Now it’s being hit every 10ms or so. Crazy.

Regarding the task called more frequently, it appears that the memory model selected has some influence on the tick to clock speed setting. By default (and I accepted it) the CPU clock config setting is 8MHz. Mine is 120MHz. So once I set it properly, 1 tick == 1 ms, which is what we want. Why changing from model 1 to model 4 effects this I have no clue.

By memory mode, do you mean the heap memory manger? As in using heap1.c, heap2.c, etc.? That should not effect anything to do with timing directly, but could be a symptom of the code not working previously but starting to work once you switched to heap_4.c Note heap_1.c cannot be used with anything that tries to delete previously allocated memory: http://www.freertos.org/a00111.html

|| Note heap_1.c cannot be used with anything that tries to delete previously allocated memory I suspect there’s something in the FreeRTOS code base that does just this. Using a simple test case from the Atmel Software Framework, it works fine until I upgrade to version 8. Then, I get the vPortFree() trap. No malloc/free operations are in the user code.

vPortFree() is also called internally if you delete an object. In that version (are you sure it is V8 you upgraded to and not V9?) all objects are allocated dynamically, which means if you free an object it will be deallocated too (vPortFree() will be called). This applies to any RTOS object such as a task, queue, semaphore, even group, etc.

Yes, V8. To reproduce, use Atmel Studio and select ASF project for FreeRTOS. Loads with version 7. Runs fine. Now change the FreeRTOS version to 8, make the compatibility changes, and test. It will break.