Ccl
Module -- Ccl
2.2 Advanced Task Settings Configuration 3
3 Known Issues / Limitations With Configuration 4
References
Communication Control LayerTechnical Reference v1.8 (TechnicalReference_CCL.pdf)
TMS570LS Series Microcontroller Technical Reference Manual (TMS570 Tech Ref_spnu489.pdf)
Configuration Settings
Ccl__core Configuration
Attribute Name | Value | Rationale |
---|---|---|
Configurable Options | ||
CCL Canbedded Handling | Yes | Default setting |
Emc Wake Up Timeout (ms) | 500 | Default setting |
Ecu Mode | Stop mode ECU | Default setting |
Enable Transceiver In Wake Up Interrupt | No | Default setting |
Naming Conventions | ||
CCL Task Prefix | Ccl | Default setting |
Advanced Task settings | ||
Scheduler Base Time (ms) | 10 | Default setting |
CANbedded Tasks | Task Container | ”Task Container” allows separate generated scheduling functions per timebase and offset that can be scheduled in separate tasks. Separate task scheduling is used to properly prioritize the ComStack cyclic main functions with the system control tasks. |
CCL Task Mode | Function Call | ”Function Call” provides generation of functions that provide scheduling flexibility among separate tasks which is required in the EPS system to properly prioritize the cyclic functions with the system control tasks. |
Debug handling | ||
Internal Debug | No | Nexteer has no design in place to log the fatal failures in the event an assertion is triggered during development. Perhaps the assertions should be mapped to the Autosar Det. Until a design use case is determined, this feature is being disabled, The production intended setting is “None” to reduce the driver operating overhead (i.e. runtime and program space) by eliminating unnecessary error checking in the final tested configuration. |
Use CCL Error Hook | No | See above. |
Transceiver Settings | ||
Transceiver Config File | None | Default setting |
Advanced Task Settings Configuration
Attribute Name | Value | Rationale |
---|---|---|
CANdesc Task | ||
Cycle Time (ms) | 10 | Default setting |
Offset Time (ms) | 2 | ”Offset” is used for the purposes of grouping cyclic functions into a generated “Task Container” in order to group cyclic functions together of a determined priority into a generated schedulable function. An offset is not actually used in scheduling. The diagnostic service handler is run in a low priority task in the system, offset 0 items run at 10ms are run at a higher priority. |
Pre Task | No | Default setting |
Post Task | No | Default setting |
XCP Task | ||
Cycle Time (ms) | 0 | Default setting |
Offset Time (ms) | 0 | Default setting |
Pre Task | No | Default setting |
Post Task | No | Default setting |
DPM Task | ||
Cycle Time (ms) | 20 | Default setting |
Offset Time (ms) | 0 | Default setting |
Pre Task | No | Default setting |
Post Task | No | Default setting |
TP Tx Task | ||
Cycle Time (ms) | 10 | Default setting |
Offset Time (ms) | 0 | |
Pre Task | No | Default setting |
Post Task | No | Default setting |
TP Rx Task | ||
Cycle Time (ms) | 10 | Default setting |
Offset Time (ms) | 0 | |
Pre Task | No | Default setting |
Post Task | No | Default setting |
FRFM Task | ||
Cycle Time (ms) | 10 | Default setting |
Offset Time (ms) | 2 | ”Offset” is used for the purposes of grouping cyclic functions into a generated “Task Container” in order to group cyclic functions together of a determined priority into a generated schedulable function. An offset is not actually used in scheduling. The FRFM is run in a low priority task in the system, offset 0 items run at 10ms are run at a higher priority. |
Pre Task | No | Default setting |
Post Task | No | Default setting |
DBKOM Tx Task | ||
Cycle Time (ms) | 10 | Default setting |
Offset Time (ms) | 0 | |
Pre Task | No | Default setting |
Post Task | No | Default setting |
DBKOM Rx Task | ||
Cycle Time (ms) | 10 | Default setting |
Offset Time (ms) | 0 | |
Pre Task | No | Default setting |
Post Task | No | Default setting |
NM OSEK Task | ||
Cycle Time (ms) | 10 | Default setting |
Offset Time (ms) | 0 | |
Pre Task | No | Default setting |
Post Task | No | Default setting |
Known Issues / Limitations With Configuration
The Ccl generator generates the DescTask() and does not provide a mechanism to generate the DescStateTask() and DescTimerTask() in separate function containers. A patch is made and commented in ccl_par.c
Revision Control Log
Item # | Rev # | Change Description | Date | Author Initials |
---|---|---|---|---|
1 | 1.0 | Initial Creation | 30JUL13 | JJW |
2 | Updated for Task Container generation and rationale for offset usage to group cyclic functions of the same priority together. | 08AUG13 | JJW |