Skip to main content
RLee.2
RLee.2
Associate
February 18, 2020
Question

Undefined reference to 'osThreadJoin'

  • February 18, 2020
  • 3 replies
  • 2063 views

Hi forum,

I'm developing using the STM32CubeIDE on the NUCLEO-F746ZG board running FreeRTOS. In the process of developing my application that makes heavy use of OS constructs, I've run into a missing/unimplemented function problem, namely osThreadJoin. The function is declared in cmsis_os2.h, but not defined in cmsis_os2.c, with all the other OS functions. How can I get access to this function?

Thanks,

Richard

    This topic has been closed for replies.

    3 replies

    JBaco.1
    JBaco.1
    Visitor II
    September 16, 2020

    Hi all,

    Same problem here. Anyone as a solution ?

    Thanks.

    Julien

    SGeof.1
    SGeof.1
    Visitor II
    March 24, 2022

    Hi,

    Did you guys figure out a solution?

    Thanks,

    Sam

    ZDima
    ZDima
    Associate
    September 5, 2022

    After hour of search found this on github.com:

    /ARM-software/CMSIS-FreeRTOS/blob/9cf2e4b4f621abfed0ee2de421d31988f8b1b0f6/DoxyGen/General/src/cmsis_freertos.txt#L733

    Thread Management:

    - osThreadDetach: \token{not implemented}

    - osThreadEnumerate: supported

    - osThreadExit: supported

    - osThreadGetCount: supported

    - osThreadGetId: supported

    - osThreadGetName: supported

    - osThreadGetPriority: supported

    - osThreadGetStackSize: \token{not implemented}

    - osThreadGetStackSpace: supported

    - osThreadGetState: supported

    - osThreadJoin: \token{not implemented}

    - osThreadNew: supported

    - osThreadResume: supported

    - osThreadSetPriority: supported

    - osThreadSuspend: supported

    - osThreadTerminate: supported

    - osThreadYield: supported

    Also in the same document:

    - osThreadDetach, osThreadJoin() and attribute osThreadJoinable are not supported (osThreadNew returns NULL when osThreadJoinable attribute is specified).

    It would be nice if this information was clearly stated in documentation (?) and in the headers.

    Terms & ConditionsAccessibility statement