Assembler issues when building cmake project with FreeRTOS

Hello, I am trying to build a project that uses FreeRTOS, and am coming across the following error message:

[build] [34/97] Building C object API/BSP/stm32h753zi_bsp/CMakeFiles/STM32H7_BSP_Lib.dir/stm32H753ZI/Drivers/STM32H7xx_HAL_Driver/Src/stm32h7xx_hal_eth.c.obj
[build] FAILED: API/BSP/stm32h753zi_bsp/CMakeFiles/STM32H7_BSP_Lib.dir/stm32H753ZI/Drivers/STM32H7xx_HAL_Driver/Src/stm32h7xx_hal_eth.c.obj 
[build] C:\ST\STM32CubeCLT\GNU-tools-for-STM32\bin\arm-none-eabi-gcc.exe -fdata-sections -ffunction-sections --specs=nano.specs -Wl,--gc-sections  -IC:/Users/myUser/Documents/git/my_app/API/BSP/stm32h753zi_bsp/stm32H753ZI/Core/Inc -IC:/Users/myUser/Documents/git/app/API/BSP/stm32h753zi_bsp/stm32H753ZI/Drivers/CMSIS/Device/ST/STM32H7xx/Include -IC:/Users/myUser/Documents/git/my_app/API/BSP/stm32h753zi_bsp/stm32H753ZI/Drivers/CMSIS/Include -IC:/Users/myUser/Documents/git/my_app/API/BSP/stm32h753zi_bsp/stm32H753ZI/Drivers/STM32H7xx_HAL_Driver/Inc -g -std=gnu17 -MD -MT API/BSP/stm32h753zi_bsp/CMakeFiles/STM32H7_BSP_Lib.dir/stm32H753ZI/Drivers/STM32H7xx_HAL_Driver/Src/stm32h7xx_hal_eth.c.obj -MF API\BSP\stm32h753zi_bsp\CMakeFiles\STM32H7_BSP_Lib.dir\stm32H753ZI\Drivers\STM32H7xx_HAL_Driver\Src\stm32h7xx_hal_eth.c.obj.d -o API/BSP/stm32h753zi_bsp/CMakeFiles/STM32H7_BSP_Lib.dir/stm32H753ZI/Drivers/STM32H7xx_HAL_Driver/Src/stm32h7xx_hal_eth.c.obj -c C:/Users/myUser/Documents/git/my_app/API/BSP/stm32h753zi_bsp/stm32H753ZI/Drivers/STM32H7xx_HAL_Driver/Src/stm32h7xx_hal_eth.c
[build] C:\Users\USER~1\AppData\Local\Temp\ccYseRvJ.s: Assembler messages:
[build] C:\Users\USER~1\AppData\Local\Temp\ccYseRvJ.s:999: Error: selected processor does not support `dsb 0xF' in ARM mode
[build] C:\Users\USER~1\AppData\Local\Temp\ccYseRvJ.s:1210: Error: selected processor does not support `dsb 0xF' in ARM mode
[build] C:\Users\USER~1\AppData\Local\Temp\ccYseRvJ.s:1631: Error: selected processor does not support `dmb 0xF' in ARM mode
[build] C:\Users\USER~1\AppData\Local\Temp\ccYseRvJ.s:6221: Error: selected processor does not support `dmb 0xF' in ARM mode
[build] C:\Users\USER~1\AppData\Local\Temp\ccYseRvJ.s:6275: Error: selected processor does not support `dmb 0xF' in ARM mode
[build] C:\Users\USER~1\AppData\Local\Temp\ccYseRvJ.s:6467: Error: selected processor does not support `dmb 0xF' in ARM mode
[build] C:\Users\USER~1\AppData\Local\Temp\ccYseRvJ.s:6568: Error: selected processor does not support `dmb 0xF' in ARM mode
[build] C:\Users\USER~1\AppData\Local\Temp\ccYseRvJ.s:6740: Error: selected processor does not support `dmb 0xF' in ARM mode
[build] C:\Users\USER~1\AppData\Local\Temp\ccYseRvJ.s:6811: Error: selected processor does not support `cpsid i' in ARM mode
[build] C:\Users\USER~1\AppData\Local\Temp\ccYseRvJ.s:6832: Error: selected processor does not support `cpsie i' in ARM mode

A bit of background:
I am using the STM32H753, and using FreeRTOS v202212.01. This project was building and running fine before the addition of FreeRTOS; within the RTOS, I have set the port to “GCC_ARM_CM7”, and I have attached my config file.

Summary

/*
#ifndef FREERTOS_CONFIG_H
#define FREERTOS_CONFIG_H

/*********************************/
/
Hardware description related definitions. /
/
/

/* In most cases, configCPU_CLOCK_HZ must be set to the frequency of the clock

  • that drives the peripheral used to generate the kernels periodic tick interrupt.
  • The default value is set to 20MHz and matches the QEMU demo settings. Your
  • application will certainly need a different value so set this correctly.
  • This is very often, but not always, equal to the main system clock frequency. */
    #define configCPU_CLOCK_HZ ( ( unsigned long ) 480000000 )

/* configSYSTICK_CLOCK_HZ is an optional parameter for ARM Cortex-M ports only.
*

  • By default ARM Cortex-M ports generate the RTOS tick interrupt from the
  • Cortex-M SysTick timer. Most Cortex-M MCUs run the SysTick timer at the same
  • frequency as the MCU itself - when that is the case configSYSTICK_CLOCK_HZ is
  • not needed and should be left undefined. If the SysTick timer is clocked at a
  • different frequency to the MCU core then set configCPU_CLOCK_HZ to the MCU clock
  • frequency, as normal, and configSYSTICK_CLOCK_HZ to the SysTick clock
  • frequency. Not used if left undefined.
  • The default value is undefined (commented out). If you need this value bring it
  • back and set it to a suitable value. */

/*
#define configSYSTICK_CLOCK_HZ [Platform specific]
*/

/*********************************/
/
Scheduling behaviour related definitions. /
/
/

/* configTICK_RATE_HZ sets frequency of the tick interrupt in Hz, normally

  • calculated from the configCPU_CLOCK_HZ value. */
    #define configTICK_RATE_HZ 100

/* Set configUSE_PREEMPTION to 1 to use pre-emptive scheduling. Set

  • configUSE_PREEMPTION to 0 to use co-operative scheduling.
    */
    #define configUSE_PREEMPTION 1

/* Set configUSE_TIME_SLICING to 1 to have the scheduler switch between Ready

  • state tasks of equal priority on every tick interrupt. Set
  • configUSE_TIME_SLICING to 0 to prevent the scheduler switching between Ready
  • state tasks just because there was a tick interrupt. See
    */
    #define configUSE_TIME_SLICING 0

/* Set configUSE_PORT_OPTIMISED_TASK_SELECTION to 1 to select the next task to

  • run using an algorithm optimised to the instruction set of the target hardware -
  • normally using a count leading zeros assembly instruction. Set to 0 to select
  • the next task to run using a generic C algorithm that works for all FreeRTOS
  • ports. Not all FreeRTOS ports have this option. Defaults to 0 if left
  • undefined. */
    #define configUSE_PORT_OPTIMISED_TASK_SELECTION 0

/* Set configUSE_TICKLESS_IDLE to 1 to use the low power tickless mode. Set to

  • 0 to keep the tick interrupt running at all times. Not all FreeRTOS ports
  • support tickless mode.
  • Defaults to 0 if left undefined. */
    #define configUSE_TICKLESS_IDLE 0

/* configMAX_PRIORITIES Sets the number of available task priorities. Tasks can

  • be assigned priorities of 0 to (configMAX_PRIORITIES - 1). Zero is the lowest
  • priority. */
    #define configMAX_PRIORITIES 5

/* configMINIMAL_STACK_SIZE defines the size of the stack used by the Idle task

  • (in words, not in bytes!). The kernel does not use this constant for any other
  • purpose. Demo applications use the constant to make the demos somewhat portable
  • across hardware architectures. */
    #define configMINIMAL_STACK_SIZE 128

/* configMAX_TASK_NAME_LEN sets the maximum length (in characters) of a task’s

  • human readable name. Includes the NULL terminator. */
    #define configMAX_TASK_NAME_LEN 16

/* Time is measured in ‘ticks’ - which is the number of times the tick interrupt

  • has executed since the RTOS kernel was started.
  • The tick count is held in a variable of type TickType_t.
  • configTICK_TYPE_WIDTH_IN_BITS controls the type (and therefore bit-width) of TickType_t:
  • Defining configTICK_TYPE_WIDTH_IN_BITS as TICK_TYPE_WIDTH_16_BITS causes
  • TickType_t to be defined (typedef’ed) as an unsigned 16-bit type.
  • Defining configTICK_TYPE_WIDTH_IN_BITS as TICK_TYPE_WIDTH_32_BITS causes
  • TickType_t to be defined (typedef’ed) as an unsigned 32-bit type.
  • Defining configTICK_TYPE_WIDTH_IN_BITS as TICK_TYPE_WIDTH_64_BITS causes
  • TickType_t to be defined (typedef’ed) as an unsigned 64-bit type. */
    #define configTICK_TYPE_WIDTH_IN_BITS TICK_TYPE_WIDTH_32_BITS

/* Set configIDLE_SHOULD_YIELD to 1 to have the Idle task yield to an

  • application task if there is an Idle priority (priority 0) application task that
  • can run. Set to 0 to have the Idle task use all of its timeslice. Default to 1
  • if left undefined. */
    #define configIDLE_SHOULD_YIELD 1

/* Each task has an array of task notifications.

  • configTASK_NOTIFICATION_ARRAY_ENTRIES sets the number of indexes in the array.
  • See Defaults to 1 if
  • left undefined. */
    #define configTASK_NOTIFICATION_ARRAY_ENTRIES 1

/* configQUEUE_REGISTRY_SIZE sets the maximum number of queues and semaphores

  • that can be referenced from the queue registry. Only required when using a
  • kernel aware debugger. Defaults to 0 if left undefined. */
    #define configQUEUE_REGISTRY_SIZE 0

/* Set configENABLE_BACKWARD_COMPATIBILITY to 1 to map function names and

  • datatypes from old version of FreeRTOS to their latest equivalent. Defaults to
  • 1 if left undefined. */
    #define configENABLE_BACKWARD_COMPATIBILITY 0

/* Each task has its own array of pointers that can be used as thread local

  • storage. configNUM_THREAD_LOCAL_STORAGE_POINTERS set the number of indexes in
  • the array.
  • Defaults to 0 if left undefined. */
    #define configNUM_THREAD_LOCAL_STORAGE_POINTERS 0

/* When configUSE_MINI_LIST_ITEM is set to 0, MiniListItem_t and ListItem_t are

  • both the same. When configUSE_MINI_LIST_ITEM is set to 1, MiniListItem_t contains
  • 3 fewer fields than ListItem_t which saves some RAM at the cost of violating
  • strict aliasing rules which some compilers depend on for optimization. Defaults
  • to 1 if left undefined. */
    #define configUSE_MINI_LIST_ITEM 1

/* Sets the type used by the parameter to xTaskCreate() that specifies the stack

  • size of the task being created. The same type is used to return information
  • about stack usage in various other API calls. Defaults to size_t if left
  • undefined. */
    #define configSTACK_DEPTH_TYPE size_t

/* configMESSAGE_BUFFER_LENGTH_TYPE sets the type used to store the length of

  • each message written to a FreeRTOS message buffer (the length is also written to
  • the message buffer. Defaults to size_t if left undefined - but that may waste
  • space if messages never go above a length that could be held in a uint8_t. */
    #define configMESSAGE_BUFFER_LENGTH_TYPE size_t

/* If configHEAP_CLEAR_MEMORY_ON_FREE is set to 1, then blocks of memory allocated

  • using pvPortMalloc() will be cleared (i.e. set to zero) when freed using
  • vPortFree(). Defaults to 0 if left undefined. */
    #define configHEAP_CLEAR_MEMORY_ON_FREE 1

/* vTaskList and vTaskGetRunTimeStats APIs take a buffer as a parameter and assume

  • that the length of the buffer is configSTATS_BUFFER_MAX_LENGTH. Defaults to
  • 0xFFFF if left undefined.
  • New applications are recommended to use vTaskListTasks and
  • vTaskGetRunTimeStatistics APIs instead and supply the length of the buffer
  • explicitly to avoid memory corruption. */
    #define configSTATS_BUFFER_MAX_LENGTH 0xFFFF

/* Set configUSE_NEWLIB_REENTRANT to 1 to have a newlib reent structure

  • allocated for each task. Set to 0 to not support newlib reent structures.
  • Default to 0 if left undefined.
  • Note Newlib support has been included by popular demand, but is not used or
  • tested by the FreeRTOS maintainers themselves. FreeRTOS is not responsible for
  • resulting newlib operation. User must be familiar with newlib and must provide
  • system-wide implementations of the necessary stubs. Note that (at the time of
  • writing) the current newlib design implements a system-wide malloc() that must
  • be provided with locks. */
    #define configUSE_NEWLIB_REENTRANT 0

/***************************************/
/
Software timer related definitions. /
/
/

/* Set configUSE_TIMERS to 1 to include software timer functionality in the

  • build. Set to 0 to exclude software timer functionality from the build. The
  • FreeRTOS/source/timers.c source file must be included in the build if
  • configUSE_TIMERS is set to 1. Default to 0 if left undefined. See
  • */
    #define configUSE_TIMERS 1

/* configTIMER_TASK_PRIORITY sets the priority used by the timer task. Only

  • used if configUSE_TIMERS is set to 1. The timer task is a standard FreeRTOS
  • task, so its priority is set like any other task. See
  • Only used
  • if configUSE_TIMERS is set to 1. */
    #define configTIMER_TASK_PRIORITY ( configMAX_PRIORITIES - 1 )

/* configTIMER_TASK_STACK_DEPTH sets the size of the stack allocated to the

  • timer task (in words, not in bytes!). The timer task is a standard FreeRTOS
  • task.
  • Only used if configUSE_TIMERS is set to 1. */
    #define configTIMER_TASK_STACK_DEPTH configMINIMAL_STACK_SIZE

/* configTIMER_QUEUE_LENGTH sets the length of the queue (the number of discrete

  • items the queue can hold) used to send commands to the timer task. See
  • Only used
  • if configUSE_TIMERS is set to 1. */
    #define configTIMER_QUEUE_LENGTH 10

/************************************/
/
Memory allocation related definitions. /
/
/

/* Set configSUPPORT_STATIC_ALLOCATION to 1 to include FreeRTOS API functions

  • that create FreeRTOS objects (tasks, queues, etc.) using statically allocated
  • memory in the build. Set to 0 to exclude the ability to create statically
  • allocated objects from the build. Defaults to 0 if left undefined. See
    **/
    #define configSUPPORT_STATIC_ALLOCATION 1

/* Set configSUPPORT_DYNAMIC_ALLOCATION to 1 to include FreeRTOS API functions

  • that create FreeRTOS objects (tasks, queues, etc.) using dynamically allocated
  • memory in the build. Set to 0 to exclude the ability to create dynamically
  • allocated objects from the build. Defaults to 1 if left undefined. See
  • */
    #define configSUPPORT_DYNAMIC_ALLOCATION 1

/* Sets the total size of the FreeRTOS heap, in bytes, when heap_1.c, heap_2.c

  • or heap_4.c are included in the build. This value is defaulted to 4096 bytes but
  • it must be tailored to each application. Note the heap will appear in the .bss
  • section. */
    #define configTOTAL_HEAP_SIZE 4096

/* Set configAPPLICATION_ALLOCATED_HEAP to 1 to have the application allocate

  • the array used as the FreeRTOS heap. Set to 0 to have the linker allocate the
  • array used as the FreeRTOS heap. Defaults to 0 if left undefined. */
    #define configAPPLICATION_ALLOCATED_HEAP 0

/* Set configSTACK_ALLOCATION_FROM_SEPARATE_HEAP to 1 to have task stacks

  • allocated from somewhere other than the FreeRTOS heap. This is useful if you
  • want to ensure stacks are held in fast memory. Set to 0 to have task stacks
  • come from the standard FreeRTOS heap. The application writer must provide
  • implementations for pvPortMallocStack() and vPortFreeStack() if set to 1.
  • Defaults to 0 if left undefined. */
    #define configSTACK_ALLOCATION_FROM_SEPARATE_HEAP 0

/* Set configENABLE_HEAP_PROTECTOR to 1 to enable bounds checking and obfuscation

  • to internal heap block pointers in heap_4.c and heap_5.c to help catch pointer
  • corruptions. Defaults to 0 if left undefined. */
    #define configENABLE_HEAP_PROTECTOR 0

/********************************/
/
Interrupt nesting behaviour configuration. /
/
/

/* configKERNEL_INTERRUPT_PRIORITY sets the priority of the tick and context

  • switch performing interrupts. The default value is set to the highest interrupt
  • priority (0). Not supported by all FreeRTOS ports. See
  • for information specific to ARM
  • Cortex-M devices. */
    #define configKERNEL_INTERRUPT_PRIORITY 0

/* configMAX_SYSCALL_INTERRUPT_PRIORITY sets the interrupt priority above which

  • FreeRTOS API calls must not be made. Interrupts above this priority are never
  • disabled, so never delayed by RTOS activity. The default value is set to the
  • highest interrupt priority (0). Not supported by all FreeRTOS ports.
  • ARM Cortex-M devices. */
    #define configMAX_SYSCALL_INTERRUPT_PRIORITY 0

/* Another name for configMAX_SYSCALL_INTERRUPT_PRIORITY - the name used depends

  • on the FreeRTOS port. */
    #define configMAX_API_CALL_INTERRUPT_PRIORITY 0

/***************************/
/
Hook and callback function related definitions. /
/
/

/* Set the following configUSE_* constants to 1 to include the named hook

  • functionality in the build. Set to 0 to exclude the hook functionality from the
  • build. The application writer is responsible for providing the hook function
  • for any set to 1. */
    #define configUSE_IDLE_HOOK 0
    #define configUSE_TICK_HOOK 0
    #define configUSE_MALLOC_FAILED_HOOK 0
    #define configUSE_DAEMON_TASK_STARTUP_HOOK 0

/* Set configUSE_SB_COMPLETED_CALLBACK to 1 to have send and receive completed

  • callbacks for each instance of a stream buffer or message buffer. When the
  • option is set to 1, APIs xStreamBufferCreateWithCallback() and
  • xStreamBufferCreateStaticWithCallback() (and likewise APIs for message
  • buffer) can be used to create a stream buffer or message buffer instance
  • with application provided callbacks. Defaults to 0 if left undefined. */
    #define configUSE_SB_COMPLETED_CALLBACK 0

/* Set configCHECK_FOR_STACK_OVERFLOW to 1 or 2 for FreeRTOS to check for a

  • stack overflow at the time of a context switch. Set to 0 to not look for a
  • stack overflow. If configCHECK_FOR_STACK_OVERFLOW is 1 then the check only
  • looks for the stack pointer being out of bounds when a task’s context is saved
  • to its stack - this is fast but somewhat ineffective. If
  • configCHECK_FOR_STACK_OVERFLOW is 2 then the check looks for a pattern written
  • to the end of a task’s stack having been overwritten. This is slower, but will
  • catch most (but not all) stack overflows. The application writer must provide
  • the stack overflow callback when configCHECK_FOR_STACK_OVERFLOW is set to 1.
  • See Defaults
  • to 0 if left undefined. */
    #define configCHECK_FOR_STACK_OVERFLOW 2

/********************/
/
Run time and task stats gathering related definitions. /
/
/

/* Set configGENERATE_RUN_TIME_STATS to 1 to have FreeRTOS collect data on the

  • processing time used by each task. Set to 0 to not collect the data. The
  • application writer needs to provide a clock source if set to 1. Defaults to 0
  • if left undefined. */
    #define configGENERATE_RUN_TIME_STATS 0

/* Set configUSE_TRACE_FACILITY to include additional task structure members

  • are used by trace and visualisation functions and tools. Set to 0 to exclude
  • the additional information from the structures. Defaults to 0 if left
  • undefined. */
    #define configUSE_TRACE_FACILITY 0

#define configUSE_16_BIT_TICKS 0

/* Set to 1 to include the vTaskList() and vTaskGetRunTimeStats() functions in

  • the build. Set to 0 to exclude these functions from the build. These two
  • functions introduce a dependency on string formatting functions that would
  • otherwise not exist - hence they are kept separate. Defaults to 0 if left
  • undefined. */
    #define configUSE_STATS_FORMATTING_FUNCTIONS 0

/*******************************************/
/
Co-routine related definitions. /
/
/

/* Set configUSE_CO_ROUTINES to 1 to include co-routine functionality in the

  • build, or 0 to omit co-routine functionality from the build. To include
  • co-routines, croutine.c must be included in the project. Defaults to 0 if left
  • undefined. */
    #define configUSE_CO_ROUTINES 0

/* configMAX_CO_ROUTINE_PRIORITIES defines the number of priorities available

  • to the application co-routines. Any number of co-routines can share the same
  • priority. Defaults to 0 if left undefined. */
    #define configMAX_CO_ROUTINE_PRIORITIES 1

/*****************************************************/
/
Debugging assistance. /
/
/

/* configASSERT() has the same semantics as the standard C assert(). It can

  • either be defined to take an action when the assertion fails, or not defined
  • at all (i.e. comment out or delete the definitions) to completely remove
  • assertions. configASSERT() can be defined to anything you want, for example
  • you can call a function if an assert fails that passes the filename and line
  • number of the failing assert (for example, “vAssertCalled( FILE, LINE )”
  • or it can simple disable interrupts and sit in a loop to halt all execution
  • on the failing line for viewing in a debugger. */
    #define configASSERT( x )
    if( ( x ) == 0 )
    {
    taskDISABLE_INTERRUPTS();
    for( ; ; )
    ;
    }

/****************************************/
/
FreeRTOS MPU specific definitions. /
/
/

/* If configINCLUDE_APPLICATION_DEFINED_PRIVILEGED_FUNCTIONS is set to 1 then

  • the application writer can provide functions that execute in privileged mode.
  • See:
  • Defaults to 0 if left undefined. Only used by the FreeRTOS Cortex-M MPU ports,
  • not the standard ARMv7-M Cortex-M port. */
    #define configINCLUDE_APPLICATION_DEFINED_PRIVILEGED_FUNCTIONS 0

/* Set configTOTAL_MPU_REGIONS to the number of MPU regions implemented on your

  • target hardware. Normally 8 or 16. Only used by the FreeRTOS Cortex-M MPU
  • ports, not the standard ARMv7-M Cortex-M port. Defaults to 8 if left
  • undefined. */
    #define configTOTAL_MPU_REGIONS 8

/* configTEX_S_C_B_FLASH allows application writers to override the default

  • values for the for TEX, Shareable (S), Cacheable (C) and Bufferable (B) bits for
  • the MPU region covering Flash. Defaults to 0x07UL (which means TEX=000, S=1,
  • C=1, B=1) if left undefined. Only used by the FreeRTOS Cortex-M MPU ports, not
  • the standard ARMv7-M Cortex-M port. */
    #define configTEX_S_C_B_FLASH 0x07UL

/* configTEX_S_C_B_SRAM allows application writers to override the default

  • values for the for TEX, Shareable (S), Cacheable (C) and Bufferable (B) bits for
  • the MPU region covering RAM. Defaults to 0x07UL (which means TEX=000, S=1, C=1,
  • B=1) if left undefined. Only used by the FreeRTOS Cortex-M MPU ports, not
  • the standard ARMv7-M Cortex-M port. */
    #define configTEX_S_C_B_SRAM 0x07UL

/* Set configENFORCE_SYSTEM_CALLS_FROM_KERNEL_ONLY to 0 to prevent any privilege

  • escalations originating from outside of the kernel code itself. Set to 1 to
  • allow application tasks to raise privilege. Defaults to 1 if left undefined.
  • Only used by the FreeRTOS Cortex-M MPU ports, not the standard ARMv7-M Cortex-M
  • port. */
    #define configENFORCE_SYSTEM_CALLS_FROM_KERNEL_ONLY 1

/* Set configALLOW_UNPRIVILEGED_CRITICAL_SECTIONS to 1 to allow unprivileged

  • tasks enter critical sections (effectively mask interrupts). Set to 0 to
  • prevent unprivileged tasks entering critical sections. Defaults to 1 if left
  • undefined. Only used by the FreeRTOS Cortex-M MPU ports, not the standard
  • ARMv7-M Cortex-M port. */
    #define configALLOW_UNPRIVILEGED_CRITICAL_SECTIONS 0

/* FreeRTOS Kernel version 10.6.0 introduced a new v2 MPU wrapper, namely

  • mpu_wrappers_v2.c. Set configUSE_MPU_WRAPPERS_V1 to 0 to use the new v2 MPU
  • wrapper. Set configUSE_MPU_WRAPPERS_V1 to 1 to use the old v1 MPU wrapper
  • (mpu_wrappers.c). Defaults to 0 if left undefined. */
    #define configUSE_MPU_WRAPPERS_V1 0

/* When using the v2 MPU wrapper, set configPROTECTED_KERNEL_OBJECT_POOL_SIZE to

  • the total number of kernel objects, which includes tasks, queues, semaphores,
  • mutexes, event groups, timers, stream buffers and message buffers, in your
  • application. The application will not be able to have more than
  • configPROTECTED_KERNEL_OBJECT_POOL_SIZE kernel objects at any point of
  • time. */
    #define configPROTECTED_KERNEL_OBJECT_POOL_SIZE 10

/* When using the v2 MPU wrapper, set configSYSTEM_CALL_STACK_SIZE to the size

  • of the system call stack in words. Each task has a statically allocated
  • memory buffer of this size which is used as the stack to execute system
  • calls. For example, if configSYSTEM_CALL_STACK_SIZE is defined as 128 and
  • there are 10 tasks in the application, the total amount of memory used for
  • system call stacks is 128 * 10 = 1280 words. */
    #define configSYSTEM_CALL_STACK_SIZE 128

/* When using the v2 MPU wrapper, set configENABLE_ACCESS_CONTROL_LIST to 1 to

  • enable Access Control List (ACL) feature. When ACL is enabled, an
  • unprivileged task by default does not have access to any kernel object other
  • than itself. The application writer needs to explicitly grant the
  • unprivileged task access to the kernel objects it needs using the APIs
  • provided for the same. Defaults to 0 if left undefined. */
    #define configENABLE_ACCESS_CONTROL_LIST 1

/******/
/
SMP( Symmetric MultiProcessing ) Specific Configuration definitions. /
/
/

/* Set configNUMBER_OF_CORES to the number of available processor cores. Defaults

  • to 1 if left undefined. */

/*
#define configNUMBER_OF_CORES [Num of available cores]
*/

/* When using SMP (i.e. configNUMBER_OF_CORES is greater than one), set

  • configRUN_MULTIPLE_PRIORITIES to 0 to allow multiple tasks to run
  • simultaneously only if they do not have equal priority, thereby maintaining
  • the paradigm of a lower priority task never running if a higher priority task
  • is able to run. If configRUN_MULTIPLE_PRIORITIES is set to 1, multiple tasks
  • with different priorities may run simultaneously - so a higher and lower
  • priority task may run on different cores at the same time. */
    #define configRUN_MULTIPLE_PRIORITIES 0

/* When using SMP (i.e. configNUMBER_OF_CORES is greater than one), set

  • configUSE_CORE_AFFINITY to 1 to enable core affinity feature. When core
  • affinity feature is enabled, the vTaskCoreAffinitySet and vTaskCoreAffinityGet
  • APIs can be used to set and retrieve which cores a task can run on. If
  • configUSE_CORE_AFFINITY is set to 0 then the FreeRTOS scheduler is free to
  • run any task on any available core. */
    #define configUSE_CORE_AFFINITY 0

/* When using SMP (i.e. configNUMBER_OF_CORES is greater than one), if

  • configUSE_TASK_PREEMPTION_DISABLE is set to 1, individual tasks can be set to
  • either pre-emptive or co-operative mode using the vTaskPreemptionDisable and
  • vTaskPreemptionEnable APIs. */
    #define configUSE_TASK_PREEMPTION_DISABLE 0

/* When using SMP (i.e. configNUMBER_OF_CORES is greater than one), set

  • configUSE_PASSIVE_IDLE_HOOK to 1 to allow the application writer to use
  • the passive idle task hook to add background functionality without the overhead
  • of a separate task. Defaults to 0 if left undefined. */
    #define configUSE_PASSIVE_IDLE_HOOK 0

/* When using SMP (i.e. configNUMBER_OF_CORES is greater than one),

  • configTIMER_SERVICE_TASK_CORE_AFFINITY allows the application writer to set
  • the core affinity of the RTOS Daemon/Timer Service task. Defaults to
  • tskNO_AFFINITY if left undefined. */
    #define configTIMER_SERVICE_TASK_CORE_AFFINITY tskNO_AFFINITY

/*****************************/
/
ARMv8-M secure side port related definitions. /
/
/

/* secureconfigMAX_SECURE_CONTEXTS define the maximum number of tasks that can

  • call into the secure side of an ARMv8-M chip. Not used by any other ports. */
    #define secureconfigMAX_SECURE_CONTEXTS 5

/* Defines the kernel provided implementation of

  • vApplicationGetIdleTaskMemory() and vApplicationGetTimerTaskMemory()
  • to provide the memory that is used by the Idle task and Timer task respectively.
  • The application can provide it’s own implementation of
  • vApplicationGetIdleTaskMemory() and vApplicationGetTimerTaskMemory() by
  • setting configKERNEL_PROVIDED_STATIC_MEMORY to 0 or leaving it undefined. */
    #define configKERNEL_PROVIDED_STATIC_MEMORY 1

/************************/
/
Definitions that include or exclude functionality. /
/
/

/* Set the following configUSE_* constants to 1 to include the named feature in

  • the build, or 0 to exclude the named feature from the build. */
    #define configUSE_TASK_NOTIFICATIONS 1
    #define configUSE_MUTEXES 1
    #define configUSE_RECURSIVE_MUTEXES 1
    #define configUSE_COUNTING_SEMAPHORES 1
    #define configUSE_QUEUE_SETS 0
    #define configUSE_APPLICATION_TASK_TAG 0

/* Set the following INCLUDE_* constants to 1 to incldue the named API function,

  • or 0 to exclude the named API function. Most linkers will remove unused
  • functions even when the constant is 1. */
    #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_eTaskGetState 0
    #define INCLUDE_xEventGroupSetBitFromISR 1
    #define INCLUDE_xTimerPendFunctionCall 0
    #define INCLUDE_xTaskAbortDelay 0
    #define INCLUDE_xTaskGetHandle 0
    #define INCLUDE_xTaskResumeFromISR 1

#endif /* FREERTOS_CONFIG_H */

and finally, I am just linking the FreeRTOS kernel library through cmake like so:
target_link_libraries(${CMAKE_PROJECT_NAME} PUBLIC freertos_kernel).

The Compile Options I am using are:
-mcpu=cortex-m7
-std=gnu17
-g3
-DDEBUG
-DUSE_HAL_DRIVER
-DSTM32H753xx
-Og
-ffunction-sections
-fdata-sections
-Wall
-fstack-usage
-fcyclomatic-complexity
-mfpu=fpv5-d16
-mfloat-abi=hard
-mthumb

Please let me know if anyone has come across this bug before, I have been looking at this for the past few days, and am totally stumped.

Thanks,
Vink

From looking up this error, the likely cause is that the compiler isn’t getting the -mcpu option, and generation code for the wrong processor. This would seem to be an error in the make file , so I would look carefully at how you added FreeRTOS in to make sure that you didn’t accidentally change something you didn’t mean to.

Hi Richard,

Thanks for your response. That does seem to be the source of the issue, I can remove the CMake connection to the FreeRTOS directories, and I can see the -mcpu option in the command line. (It only fails because my main file tries to add FreeRTOS.h still)

[1/79] Building C object App/CMakeFiles/My_App.dir/Src/app.c.obj
[build] FAILED: App/CMakeFiles/My_App.dir/Src/app.c.obj
[build] C:\ST\STM32CubeCLT\GNU-tools-for-STM32\bin\arm-none-eabi-gcc.exe -fdata-sections -ffunction-sections --specs=nano.specs -Wl,--gc-sections -DSTM32H753xx -DUSE_HAL_DRIVER -IC:/Users/User/Documents/git/my_app/API/BSP/stm32h753zi_bsp/stm32H753ZI/Core/Inc -IC:/Users/User/Documents/git/my_app/API/BSP/stm32h753zi_bsp/stm32H753ZI/Drivers/CMSIS/Device/ST/STM32H7xx/Include -IC:/Users/User/Documents/git/my_app/API/BSP/stm32h753zi_bsp/stm32H753ZI/Drivers/CMSIS/Include -IC:/Users/User/Documents/git/my_app/API/BSP/stm32h753zi_bsp/stm32H753ZI/Drivers/STM32H7xx_HAL_Driver/Inc -g -std=gnu17 **-mcpu=cortex-m7** -std=gnu17 -g3 -Og -ffunction-sections -fdata-sections -Wall -fstack-usage -fcyclomatic-complexity -mfpu=fpv5-d16 -mfloat-abi=hard -mthumb -MD -MT App/CMakeFiles/My_App.dir/Src/app.c.obj -MF App\CMakeFiles\My_App.dir\Src\app.c.obj.d -o App/CMakeFiles/My_App.dir/Src/app.c.obj -c C:/Users/User/Documents/git/my_app/App/Src/app.c

However, adding the CMake connection again shows:

[build] [4/61] Building C object API/BSP/stm32h753zi_bsp/CMakeFiles/STM32H7_BSP_Lib.dir/stm32H753ZI/Drivers/STM32H7xx_HAL_Driver/Src/stm32h7xx_hal_cortex.c.obj
[build] FAILED: API/BSP/stm32h753zi_bsp/CMakeFiles/STM32H7_BSP_Lib.dir/stm32H753ZI/Drivers/STM32H7xx_HAL_Driver/Src/stm32h7xx_hal_cortex.c.obj 
[build] C:\ST\STM32CubeCLT\GNU-tools-for-STM32\bin\arm-none-eabi-gcc.exe -fdata-sections -ffunction-sections --specs=nano.specs -Wl,--gc-sections  -IC:/Users/User/Documents/git/my_app/API/BSP/stm32h753zi_bsp/stm32H753ZI/Core/Inc -IC:/Users/User/Documents/git/my_app/API/BSP/stm32h753zi_bsp/stm32H753ZI/Drivers/CMSIS/Device/ST/STM32H7xx/Include -IC:/Users/User/Documents/git/my_app/API/BSP/stm32h753zi_bsp/stm32H753ZI/Drivers/CMSIS/Include -IC:/Users/User/Documents/git/my_app/API/BSP/stm32h753zi_bsp/stm32H753ZI/Drivers/STM32H7xx_HAL_Driver/Inc -g -std=gnu17 -MD -MT API/BSP/stm32h753zi_bsp/CMakeFiles/STM32H7_BSP_Lib.dir/stm32H753ZI/Drivers/STM32H7xx_HAL_Driver/Src/stm32h7xx_hal_cortex.c.obj -MF API\BSP\stm32h753zi_bsp\CMakeFiles\STM32H7_BSP_Lib.dir\stm32H753ZI\Drivers\STM32H7xx_HAL_Driver\Src\stm32h7xx_hal_cortex.c.obj.d -o API/BSP/stm32h753zi_bsp/CMakeFiles/STM32H7_BSP_Lib.dir/stm32H753ZI/Drivers/STM32H7xx_HAL_Driver/Src/stm32h7xx_hal_cortex.c.obj -c C:/Users/User/Documents/git/my_app/API/BSP/stm32h753zi_bsp/stm32H753ZI/Drivers/STM32H7xx_HAL_Driver/Src/stm32h7xx_hal_cortex.c

All my CMake does is add the freeRTOS directory as a library to the project.

    set(FREERTOS_CONFIG_FILE_DIRECTORY "${CMAKE_CURRENT_LIST_DIR}/freertos/Config")
    set(FREERTOS_PORT "GCC_ARM_CM7")
    add_subdirectory(freertos/Source)
    target_link_libraries(${CMAKE_PROJECT_NAME} PUBLIC freertos_kernel)

Is there any specific way that the FreeRTOS library expects to be added to a cmake project?

I saw a previous post with a similar issue here. In an attempt to try this solution I added this:

add_compile_options(${EXECUTABLE} PUBLIC
	-mcpu=cortex-m7
)
add_subdirectory(App)
add_subdirectory(API)

Within my App dir, I keep my main.c, the API directory contains the CubeMX generated BSP, as well as the RTOS directory. I should also note that I am using CMake to build Ninja

High Level Structure
CMakeLists.txt (Where the CMake snippet above exists)
- App
     - Src
          - Main.c
      CMakeLists.txt (Creates executable)
- API
     - BSP
          - STM32H7_Gen
          - CMakeLists.txt
     - RTOS
          - freeRTOS
          - freeRTOS_Plus
          - freeRTOS_Config
          - CMakeLists.txt 

After making that adjustment, there are now linker errors…

[proc] Executing command: "C:\Program Files\CMake\bin\cmake.EXE" --build C:/Users/User/Documents/git/my_app/build/Debug --parallel 8
[build] [1/120] Building ASM object App/CMakeFiles/My_App.dir/__/API/BSP/stm32h753zi_bsp/stm32H753ZI/Core/Startup/startup_stm32h753zitx.S.obj
[build] FAILED: App/CMakeFiles/My.dir/__/API/BSP/stm32h753zi_bsp/stm32H753ZI/Core/Startup/startup_stm32h753zitx.S.obj 
[build] C:\ST\STM32CubeCLT\GNU-tools-for-STM32\bin\arm-none-eabi-gcc.exe -fdata-sections -ffunction-sections --specs=nano.specs -Wl,--gc-sections -DSTM32H753xx -DUSE_HAL_DRIVER -IC:/Users/User/Documents/git/my_app/API/BSP/stm32h753zi_bsp/stm32H753ZI/Core/Inc -IC:/Users/User/Documents/git/my_app/API/BSP/stm32h753zi_bsp/stm32H753ZI/Drivers/CMSIS/Device/ST/STM32H7xx/Include -IC:/Users/User/Documents/git/my_app/API/BSP/stm32h753zi_bsp/stm32H753ZI/Drivers/CMSIS/Include -IC:/Users/User/Documents/git/my_app/API/BSP/stm32h753zi_bsp/stm32H753ZI/Drivers/STM32H7xx_HAL_Driver/Inc -IC:/Users/User/Documents/git/my_app/API/RTOS/freertos/FreeRTOS/Source/include -IC:/Users/User/Documents/git/my_app/API/RTOS/freertos/Config -IC:/Users/User/Documents/git/my_app/API/RTOS/freertos/FreeRTOS/Source/portable/GCC/ARM_CM7/r0p1 -g My_App PUBLIC -mcpu=cortex-m7 -std=gnu17 -g3 -DDEBUG -DUSE_HAL_DRIVER -DSTM32H753xx -Og -ffunction-sections -fdata-sections -Wall -fstack-usage -fcyclomatic-complexity -mfpu=fpv5-d16 -mfloat-abi=hard -mthumb -MD -MT App/CMakeFiles/My_App.dir/__/API/BSP/stm32h753zi_bsp/stm32H753ZI/Core/Startup/startup_stm32h753zitx.S.obj -MF App\CMakeFiles\My_App.dir\__\API\BSP\stm32h753zi_bsp\stm32H753ZI\Core\Startup\startup_stm32h753zitx.S.obj.d -o App/CMakeFiles/My_App.dir/__/API/BSP/stm32h753zi_bsp/stm32H753ZI/Core/Startup/startup_stm32h753zitx.S.obj -c C:/Users/User/Documents/git/my_app/API/BSP/stm32h753zi_bsp/stm32H753ZI/Core/Startup/startup_stm32h753zitx.S
[build] arm-none-eabi-gcc.exe: warning: My_App: linker input file unused because linking not done
[build] arm-none-eabi-gcc.exe: error: My_App: linker input file not found: No such file or directory
[build] arm-none-eabi-gcc.exe: warning: PUBLIC: linker input file unused because linking not done
[build] arm-none-eabi-gcc.exe: error: PUBLIC: linker input file not found: No such file or directory

It seems that your CMake file has issues. Did you use CubeMX to generate a CMake project and then added FreeRTOS? Can you share your project?

Hi Gaurav,

I am using CubeMX to generate code for pin usage, but, I am encapsulating that code within my own cmake structure. FreeRTOS is being added as a separate library to my cmake build.

I have posted the project in it’s current state here: GitHub - VKirandumkara/tipApp

Thanks,
Vink

The stm32h753zi_bsp directory is empty here causing the build failure - tipApp/API/BSP at main · VKirandumkara/tipApp · GitHub.

Other than that I needed to make the following 2 changes -

diff --git a/API/RTOS/CMakeLists.txt b/API/RTOS/CMakeLists.txt
index 08a59f9..a22cc5f 100644
--- a/API/RTOS/CMakeLists.txt
+++ b/API/RTOS/CMakeLists.txt
@@ -10,7 +10,7 @@ if(RTOS_FAMILY STREQUAL "FreeRTOS")
 
     message("FreeRTOS Port: ${FREERTOS_PORT}")
 
-    add_subdirectory(freertos/FreeRTOS/Source)
+    add_subdirectory(FreeRTOS/FreeRTOS/Source)
     target_link_libraries(${CMAKE_PROJECT_NAME} PUBLIC freertos_kernel)
 
     message("FreeRTOS added.")
diff --git a/API/RTOS/FreeRTOS/FreeRTOS/Source/CMakeLists.txt b/API/RTOS/FreeRTOS/FreeRTOS/Source/CMakeLists.txt
index 7c87ce4..3567d52 100644
--- a/API/RTOS/FreeRTOS/FreeRTOS/Source/CMakeLists.txt
+++ b/API/RTOS/FreeRTOS/FreeRTOS/Source/CMakeLists.txt
@@ -10,7 +10,7 @@ cmake_minimum_required(VERSION 3.15)
 # using heap_4.c.
 
 # Absolute path to FreeRTOS config file directory
-set(FREERTOS_CONFIG_FILE_DIRECTORY "${PROJECT_SOURCE_DIR}/API/RTOS/freertos/Config" CACHE STRING "Absolute path to the directory with FreeRTOSConfig.h")
+set(FREERTOS_CONFIG_FILE_DIRECTORY "${PROJECT_SOURCE_DIR}/API/RTOS/FreeRTOS/Config" CACHE STRING "Absolute path to the directory with FreeRTOSConfig.h")
 message("Config: ${FREERTOS_CONFIG_FILE_DIRECTORY}")

In any case, the errors you are seeing are CMake related and I am not an CMake expert. I’d recommend that you first get the bare metal code (without FreeRTOS) working in CMake. Once you get that working, you can try to add FreeRTOS.

That was my bad, I thought I had removed the submodule linking to the BSP as well. Thank you both for your help through this debug.
Ultimately, I have come to the solution of the problem, so I’ll document here my findings for future searchers.

FreeRTOS requires the Compile Options and Compile Definitions as used by your BSP.
My initial thoughts of adding the compile options and definitions to the CMAKE_PROJECT_NAME target did not propagate to all the children the way I was expecting, and thus the error.
To fix this, I added the compile options and definitions directly to my BSP target, as well as the freertos_kernel_port target. For whatever reason, adding the options and definitions to the freertos_kernel target caused an error as well.

I hope this helps future visitors.

1 Like

Thank you for sharing your solution!