nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: CanFestival CAN interfaces nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210:
nico@210: nico@210: next nico@210: nico@210: up nico@210: nico@210: previous nico@210: nico@210: contents nico@210:
nico@210: Next: CanFestival events scheduling nico@210: Up: Understanding Canfestival nico@210: Previous: Implement CanFestival in your nico@210:   Contents nico@210:
nico@210:
nico@210: nico@210: nico@210:

nico@210: CanFestival CAN interfaces nico@210:

nico@210: Because most CAN controllers and drivers implement FIFOs, CanFestival nico@210: consider sending message as a non bloking operation. nico@210: nico@210:

nico@210: In order to prevent reentrent calls to the stack, messages reception is nico@210: implemented differently on µC and OS.: nico@210: nico@210:

nico@210: nico@210:

    nico@210:
  1. µC must provide interuption masking for timer and can nico@210: receive IT nico@210:
    nico@210:
    nico@210: Image 10000201000003CA0000016604E6A5EF nico@210: nico@210:
    nico@210:
    2. nico@210:
  2. OS must provide a receive thread, a timer thread and a mutex. CAN nico@210: reception is a bloking operation. nico@210:
    nico@210:
    nico@210: Image 10000201000003F9000002CF8B0CDAEA nico@210: nico@210:
    nico@210:
    3. nico@210:
nico@210:
nico@210:
nico@210: epimerde nico@210: 2007-06-05 nico@210:
nico@210: nico@210: