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

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • 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

  • 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
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.