This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

CMSIS RTOS RTX invalid thread id token ?

Note: This was originally posted on 8th August 2012 at http://forums.arm.com

Hi,

I am using Keil's RTX implementation of the CMSIS RTOS and need to communicate between an interrupt routine and a thread. I intend to use the osSignalSet() call for this which the documentation says is suitable for use in an interrupt routine. This function takes an osThreadId parameter which I intend to store in a global variable for access by the ISR and will set it from the thread.

My question relates to interrupts that might conceivably occur before the creation of the thread : I need a default value to use for the osThreadId which can never occur as a real thread id. Obviously Keil's RTX comes complete with source and I am pretty sure "NULL" is a suitable value but the CMSIS RTOS documentation states that the implementation of osThreadId is implementation defined so I cannot rely on this being always true. I have looked up and down "cmsis_os.h"but cannot find any #define like GUARANTEED_INVALID_THREAD_ID, so can anyone tell me whether this is an oversight in CMSIS RTOS, or am I missing something ?

Also, while I am here, my use above of a global variable to communicate data between an ISR and a thread is quite common but very ugly. I am new to ARM Cortex and I wondered if there is anything I am missing in terms of alternatives ? I am reminded of the early days of Windows when Windows drivers communicated with DOS counterparts via software interrupts in an arrangement like a kind of multi-level dumb waiter, I can't remember what they called that arrangement but is there anything in the Cortex that would allow a similar scheme to work ?

Many thanks,

Mike

Parents

Bastian Schick over 12 years ago

Note: This was originally posted on 9th August 2012 at http://forums.arm.com

I guess uglyness is in the eye of the beholder but I prefer to avoid global data where at all possible.

However you are wrong to say that my threads are created at start-up and, in addition, the objects which access the hardware need to be deleted and created dynamically in my application so some form of INVALID_THREAD_ID token is required by my software.

Didn't know RTX allows to create dynamic processes.
Anyway, the cleanest way would be to send a message to the interrupt process to tell it the thread id.
And of course, if the receiver gets killed, also notify the interrupt thread about that so it will discard the thread id.
BTW found this in the RTX sources:
if (tsk == 0) { // Invalid task ID sysThreadError(osErrorNoMemory); // Create task failed (Out of memory) return NULL; }

So it is perfect clear the NULL is an ivalid thread ID esp. because it is a pointer.
Cancel
Vote up 0 Vote down

Cancel

Reply

Bastian Schick over 12 years ago

Note: This was originally posted on 9th August 2012 at http://forums.arm.com

I guess uglyness is in the eye of the beholder but I prefer to avoid global data where at all possible.

However you are wrong to say that my threads are created at start-up and, in addition, the objects which access the hardware need to be deleted and created dynamically in my application so some form of INVALID_THREAD_ID token is required by my software.

Didn't know RTX allows to create dynamic processes.
Anyway, the cleanest way would be to send a message to the interrupt process to tell it the thread id.
And of course, if the receiver gets killed, also notify the interrupt thread about that so it will discard the thread id.
BTW found this in the RTX sources:
if (tsk == 0) { // Invalid task ID sysThreadError(osErrorNoMemory); // Create task failed (Out of memory) return NULL; }

So it is perfect clear the NULL is an ivalid thread ID esp. because it is a pointer.
Cancel
Vote up 0 Vote down

Cancel

Children

No data