Monday, December 11th 2017, 10:28am UTC+1

You are not logged in.

  • Login
  • Register

Dear visitor, welcome to SEGGER Forum. If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

Scott W

Beginner

Date of registration: Mar 2nd 2016

Posts: 1

1

Thursday, March 30th 2017, 2:52am

Can OS_TASK_EVENT be 64-bit unsigned on 32-bit ARM Cortex-M?

Hi,


We need more than 32 signals. Can OS_TASK_EVENT be safely defined as a 64-bit unsigned on 32-bit ARM Cortex-M, or does this violate the requirement for atomic types?

If limited to 32 bits, is there a standard pattern for using perhaps a second event object and an 'Extension' signal sent to the Task Event?

Thanks!
Scott

SEGGER - Til

Super Moderator

Date of registration: Nov 14th 2007

Posts: 261

2

Thursday, March 30th 2017, 8:54am

Hi Scott,

basically that should be doable since we already disable the interrupts while modifying the task event bit mask.
You will need to define OS_TASK_EVENT as a 64 bit unsigned in e.g. your project settings while working with the embOS sources.

But please contact us directly by email.
That makes it easier to discuss the details.

Best regards,
Til