2016-10-17 12:38 PM
int32_t osSignalSet(osThreadId thread_id, int32_t signals)
Parameters
[in] thread_id thread ID obtained by osThreadCreate or osThreadGetId.
[in] signals specifies the signal flags of the thread that should be set.
Returns
previous signal flags of the specified thread or 0x80000000 in case of incorrect parameters.
But STM32CubeMX creates:
/**
* @brief Set the specified Signal Flags of an active thread.
* @param thread_id thread ID obtained by \ref osThreadCreate or \ref osThreadGetId.
* @param signals specifies the signal flags of the thread that should be set.
* @retval osOK if successful, osErrorOS if failed .
* @note MUST REMAIN UNCHANGED: \b osSignalSet shall be consistent in every CMSIS-RTOS.
*/
int32_t osSignalSet (osThreadId thread_id, int32_t
signal
)
And indeed the only return values are osErrorOS (=255) or osOK (=0) !
Same applies to function osSignalClear()
Bug or feature ??? ;)
Best regards,
Michael.
#stm32cubemx #stm32cube-free-rtos-cmsis
2016-10-31 02:34 AM
Dear User,
Thank you for highlighting this issue. Please note that your feedback is reported internally and it is under review. Best Regards STM32.forum2017-01-09 07:34 AM
Hi
Katzenberger.Michael
,Your bug has been solved and will be delivered in CubeMX4.
BR.
Eric Dampierre
2017-01-10 03:46 AM
Hi again
Katzenberger.Michael
,For your information, I have a recent update from our development team and the bug will be delivered in CubeMX4.21 (instead ofCubeMX4.20).
BR. Eric Dampierre