• Bean name - Name of the bean.
• Conformance class - The attribute specifies the conformance class which is supported by the OS.
  There are 2 modes:
  • BCC1 - Basic conformance class 1 There are no items in this mode.
  • ECC1 - Extended conformance class 1 The following items are displayed in this mode:
    • Interrupt - OSEK uses this interrupt vector in Extended conformance class 1 (for information only)
    • ISR stack size - Specifies ISR stack size in bytes. The stack is used in ISR category 2. In this case current status of the cpu is saved onto the current stack, and stack is switched to the interrupt stack.
• HC Base page - OS system variables will be allocated in base page or in non-volatile registers. This may reduce the OS code size by means of the direct addressing mode usage when possible.
  HC08 derivatives:
  Size of ROM/RAM areas RAM and Z_PAGE in the CPU bean (Build options) should be decreased in order to create space for this area.
  HCS12 derivatives:
  Property Internal RAM mapping in the CPU bean should be set to 0x0000 address to enable access to base page. Also Registers block mapping property in the Cpu bean should be set properly.
  • Name - Memory area name.
  • Address - Start address of the area. This address must be in internal or external memory (if an external bus is supported by the selected derivative).
  • Size - Size of the memory area.
  • Qualifier - Memory access qualifier.
• OS code in separate mem. segment - Place OS code into separate memory segment called .ostext. Macro OSCODESEC must be defined in compiler options (-DOSCODESEC).
  • Name - Memory area name.
  • Address - Start address of the area. This address must be in internal or external memory (if an external bus is supported by the selected derivative).
  • Size - Size of the memory area.
  • Qualifier - Memory access qualifier.
• System Timer - Specifies whether OSEK system timer is used or not. If so, SWCOUNTER or HWCOUNTER mode can be selected for Cpus with direct OSEK support. The Cpus not directly supported by OSEK can use USER SWCOUNTER. In this case inherited TimerInt bean is used to handle selected timer peripheral. See help for list of Cpus directly supported by OSEK.
  There are 4 modes:
  • NONE - No timer selected. There are no items in this mode.
  • HWCOUNTER - Timer implemented as HWCOUNTER The following items are displayed in this mode:
    • OSEK System Counter name - Name of OSEK Counter object which is attached to this timer. It can be changed to any name.
    • System counter min cycle - The property specifies the minimum allowed number of counter ticks for a cyclic alarm linked to the counter.
    • System counter ticks per base - The number of ticks that are required to reach a counter-specific value. The interpretation is up to the user.
    • HWCOUNTER - Timer used for SystemTimer as HWCOUNTER.
      • Timer - Periodic interrupt source: compare register, reload register, (the pull-down menu propose the possible timers).
      • Counter - Name of the counter used by this bean (for information only).
      • Interrupt service - Bean uses the interrupt service for the counter function (always enabled).
        • Interrupt - Interrupt vector invoked from the timer (for information only).
        • Interrupt priority - Priority of the interrupt associated with the timer.
      • Prescaler - Prescaler selected for the timer. There is also a possibility to let Processor Expert decide which prescaler is the best - just select Auto selected prescaler.
        • Internal prescaler - Internal prescaler value.
        • Internal compare - Internal compare prescaler value.
      • Initial period - Time before reinitialize counter. It is necessary to type here both value and unit (see Timing Setting Syntax). The setting may be made with the help of the Timing dialog box that gets open when clicking on button (...).
      • Bean uses entire timer - If set, the bean occupies the entire timer with all its compares, captures and so on. The advantage is that the compare can reset the timer - a shorter event period can be reached. The disadvantage is that no other bean can use this timer.
  • SWCOUNTER - Timer implemented as SWCOUNTER The following items are displayed in this mode:
    • OSEK System Counter name - See previous modes for more details
    • System counter max allowed value - The property defines maximum allowed counter value. After the counter reaches this value it rolls over and starts to count again from zero.
    • System counter min cycle - See previous modes for more details
    • System counter ticks per base - See previous modes for more details
    • SWCOUNTER - Timer used for SystemTimer as SWCOUNTER.
      • Timer - Periodic interrupt source: compare register, reload register, (the pull-down menu propose the possible timers).
      • Counter - Name of the counter used by this bean (for information only).
      • Interrupt service - Bean uses the interrupt service for the counter function (always enabled).
        • Interrupt - Interrupt vector invoked from the timer (for information only).
        • Interrupt priority - Priority of the interrupt associated with the timer.
      • Prescaler - Prescaler selected for the timer. There is also a possibility to let Processor Expert decide which prescaler is the best - just select Auto selected prescaler.
        • Internal prescaler - Internal prescaler value.
        • Internal compare - Internal compare prescaler value.
      • Initial period - Time before reinitialize counter. It is necessary to type here both value and unit (see Timing Setting Syntax). The setting may be made with the help of the Timing dialog box that gets open when clicking on button (...).
      • Bean uses entire timer - If set, the bean occupies the entire timer with all its compares, captures and so on. The advantage is that the compare can reset the timer - a shorter event period can be reached. The disadvantage is that no other bean can use this timer.
  • USER SWCOUNTER - Timer support for derivatives without direct OSEK support. The following items are displayed in this mode:
    • OSEK System Counter name - See previous modes for more details
    • System counter max allowed value - See previous modes for more details
    • System counter min cycle - See previous modes for more details
    • System counter ticks per base - See previous modes for more details
    • User System counter - Settings of inherited bean used as User SWCOUNTER. User SW Counter should be used for derivatives without direct OSEK support (for details about settings see Bean Inheritance & Bean Sharing).
• Second Timer - Specifies whether OSEK second timer is used or not. If so, SWCOUNTER or HWCOUNTER mode can be selected for Cpus with direct OSEK support. The Cpus not directly supported by OSEK can use USER SWCOUNTER. In this case inherited TimerInt bean is used to handle selected timer peripheral. See help for list of Cpus directly supported by OSEK.
  There are 4 modes:
  • NONE - No timer selected. There are no items in this mode.
  • HWCOUNTER - Timer implemented as HWCOUNTER The following items are displayed in this mode:
    • OSEK Second Counter name - Name of OSEK Counter object which is attached to this timer. It can be changed to any name.
    • Second counter min cycle - The property specifies the minimum allowed number of counter ticks for a cyclic alarm linked to the counter.
    • Second counter ticks per base - The number of ticks that are required to reach a counter-specific value. The interpretation is up to the user.
    • HWCOUNTER - Timer used for SecondTimer as HWCOUNTER.
      • Timer - Periodic interrupt source: compare register, reload register, (the pull-down menu propose the possible timers).
      • Counter - Name of the counter used by this bean (for information only).
      • Interrupt service - Bean uses the interrupt service for the counter function (always enabled).
        • Interrupt - Interrupt vector invoked from the timer (for information only).
        • Interrupt priority - Priority of the interrupt associated with the timer.
      • Prescaler - Prescaler selected for the timer. There is also a possibility to let Processor Expert decide which prescaler is the best - just select Auto selected prescaler.
        • Internal prescaler - Internal prescaler value.
        • Internal compare - Internal compare prescaler value.
      • Initial period - Time before reinitialize counter. It is necessary to type here both value and unit (see Timing Setting Syntax). The setting may be made with the help of the Timing dialog box that gets open when clicking on button (...).
      • Bean uses entire timer - If set, the bean occupies the entire timer with all its compares, captures and so on. The advantage is that the compare can reset the timer - a shorter event period can be reached. The disadvantage is that no other bean can use this timer.
  • SWCOUNTER - Timer implemented as SWCOUNTER The following items are displayed in this mode:
    • OSEK Second Counter name - See previous modes for more details
    • Second counter max allowed value - The property defines maximum allowed counter value. After the counter reaches this value it rolls over and starts to count again from zero.
    • Second counter min cycle - See previous modes for more details
    • Second counter ticks per base - See previous modes for more details
    • SWCOUNTER - Timer used for SecondTimer as SWCOUNTER.
      • Timer - Periodic interrupt source: compare register, reload register, (the pull-down menu propose the possible timers).
      • Counter - Name of the counter used by this bean (for information only).
      • Interrupt service - Bean uses the interrupt service for the counter function (always enabled).
        • Interrupt - Interrupt vector invoked from the timer (for information only).
        • Interrupt priority - Priority of the interrupt associated with the timer.
      • Prescaler - Prescaler selected for the timer. There is also a possibility to let Processor Expert decide which prescaler is the best - just select Auto selected prescaler.
        • Internal prescaler - Internal prescaler value.
        • Internal compare - Internal compare prescaler value.
      • Initial period - Time before reinitialize counter. It is necessary to type here both value and unit (see Timing Setting Syntax). The setting may be made with the help of the Timing dialog box that gets open when clicking on button (...).
      • Bean uses entire timer - If set, the bean occupies the entire timer with all its compares, captures and so on. The advantage is that the compare can reset the timer - a shorter event period can be reached. The disadvantage is that no other bean can use this timer.
  • USER SWCOUNTER - Timer support for derivatives without direct OSEK support. The following items are displayed in this mode:
    • OSEK Second Counter name - See previous modes for more details
    • Second counter max allowed value - See previous modes for more details
    • Second counter min cycle - See previous modes for more details
    • Second counter ticks per base - See previous modes for more details
    • User Second counter - Settings of inherited bean used as User SWCOUNTER. User SW Counter should be used for derivatives without direct OSEK support (for details about settings see Bean Inheritance & Bean Sharing).
• HC Low power - This attribute defines that low power mode shall be used when there is no ready or running tasks and scheduler goes into idle loop.
• OSEK interrupt handlers - Declaration of following interrupt handlers will be added to OSEK configuration file (oil). If any other bean uses interrupt(s) in the project, ISR declarations are automatically added to the oil file with category 1.
  If other ISR category is desired or additional attributes are needed (Resources, Accessors), the interrupt vector(s) must be inserted in this section and attributes configured as needed.
  One item of the list looks like:
  ISR - Interrupt handler properties.
  • Interrupt vector - Interrupt vector associated with an interrupt handler. To add declaration of an interrupt handler from a bean, use the same interrupt vector as in corresponding bean.
  • Category - Category 1 - ISR is executed on current stack most OS services are disabled.
    Category 2 - execution switched to the ISR stack calling of OS service enabled.
  • Resources - The reference specifies resources accessed by the ISR (not available if Category value equals to 1).
    One item of the list looks like:
    Resource Name0 - The resource reference name.
  • Accessors - The attributes define type of usage for the message, message reference, and reference for the message data.
    One item of the list looks like:
    Accessors0 - Accessor.
    • Accessor - The attribute is used to define the type of usage for the message.
    • Message - The message specifies the message to be send or received by the task.
    • Access Name - The attribute defines the reference which can be used by the application to access the message data.