This action might not be possible to undo. Are you sure you want to continue?
ECU Sof tware
Date: March 2011 · Responsible for the contents: Vector Informatik GmbH, Stuttgart, Germany All mentioned product names are either registered or unregistered trademarks of their respective owners. The constant worldwide availability of all products or services is not warranted. No information contained in this catalog may be reproduced without expressed permission, in writing, from Vector Informatik GmbH. Errors and omissions excepted. Illustration & Design: SATZTEAM Fotosatz & Neue Medien GmbH, Eberdingen, Germany
Trainees. Support. we are present worldwide. On Location Worldwide For Vector. partnership with its customers means understanding their requirements. Founding of customer care center north in Braunschweig and customer care center south in Munich/Germany Vector has more than 500 employees worldwide Founding of office in Regensburg/Germany Vector has more than 600 employees worldwide Vector has more than 700 employees worldwide Start of construction for the third company building in Stuttgart/Germany Founding of Vector Korea. Paris/France. Tokyo/Japan. Vector Informatik is DIN EN ISO 9001:1994 certified Vector has more than 100 employees worldwide Move to the new company building in Stuttgart. Excellent Working Atmosphere 70 % of our highly-qualified employees work in the development environment. confirms how each person at Vector understands his or her work: as mental work with a “fun” factor. Vector has more than 250 employees worldwide Vector has more than 400 employees worldwide Move to the second company building in Stuttgart. interns. of Korea Vector has more than 800 employees worldwide Move to the third company building in Stuttgart Founding of Vector Great Britain. China aquintos becomes part of the Vector Group High Customer Satisfaction The delivery quality and delivery time as well as consulting competence from Sales. but are constantly being improved. Göteborg/Sweden. For optimal support on location. Reliable Partner with Quality For many years. Detroit/USA Founding of Vector Japan. Founding of Vector Consulting Vector Informatik is DIN EN ISO 9001:2000 certified. Birmingham Founding of Vector Informatik India. Pune Opening of Representative Office Shanghai. In order to be responsive to our partners quickly and to be able to act purposefully. a globe-spanning network of distributors. This reliability is based upon the factors below: > Global unique processes and standards > All Vector subsidiaries are certified according to ISO 9001:2000 > SPICE level 3 (HIS scope) reached in the area of ECU software > CMMI maturity level 2 reached in the area of software services Milestones / Key Data 1988 1992 1994 1996 1997 1998 1999 2001 2002 Founding of Vector Informatik GmbH Sale of the first CANalyzer license Vector has more than 25 employees Sale of the first CANoe and CANape license Founding of Vector CANtech. and graduating students also profit from the many opportunities to work actively with the newest technologies. 2003 2004 2005 2006 2007 2008 2009 2010 . software components and services for creating embedded systems. and Consulting are not just maintained on a high level. Founding of VecScan. Founding of Vector France. Seoul/Rep. The success: our customers judge us on a scale of 1 to 5 (where 1 is the best grade and 5 the worst) with an average grade of 1. the Vector Group has established. our customers have realized what they have in Vector: a reliable and competent partner for efficient solutions in electronic networking. in addition to its own locations. Employee turnover at Vector.Vector – the Company 1/0 Vector provides OEMs and suppliers of automotive and related industries a professional and open development platform of tools. Customers worldwide place their trust in the solutions and products of the independent and self-contained Vector Group. Teamwork in modern structures ensures a working atmosphere that in the past few years has been judged “very good” according to internal surveys.6. which has been extremely low for many years.
workflows and projects. LIN.g. stored in a consistent database and used during the ECU‘s lifecycle. Basic software for AUTOSAR. and supplying special tools that allow the management of complex data. Tools to simulate. ECU Testing Tools and services that allow the test of ECUs in all development phases. analyze and test the communication of the network. or request further information about the Vector Solutions for various tasks in automotive networking: Internet: www. Process Management. Please request other catalogs in the application areas Development of Distributed Systems. check the functionality of prototypes or execute regression and conformity tests. Vehicle Diagnostics Tools to describe.com Development of Distributed Systems Tools and Services to design and develop a network of ECUs. so the ECU algorithms can be modified and optimized.VECTOR –XXXXXXXXXXXX THE COMPANY 1/1 1/1 This catalog provides you an overview of Vector products and Services of the application area ECU Software: ECU Software Embedded software like real time operating systems (RTOS) and communication modules for e. ECU Calibration Tools to access the ECU at run-time. ECU Testing. ECU Calibration. Diagnostic functionalities are set up during the ECU development. Vehicle Diagnostics.vector. coaching. This allows acquiring and modifying measurement data and parameters. Development services for software components. Software for memory management and for reprogramming of ECUs.com/catalog/ • E-mail: catalog@vector. Process Management Tools and Services to support the process management required to develop complex vehicle electronics. CAN. implement and test the diagnostic functionalities that are required to run diagnostic services on an ECU. This includes qualification of human resources. . FlexRay and Ethernet.
CANaero CANoe. CAN was specifically developed for the serial data exchange between electronic control units in automobiles but is also used for the realization of industrial microcontroller networks.LIN CANalyzer/CANoe Option SCOPE CANape CANbedded LIN Communication Embedded Gateway Flash Bootloader CANister CANlog 3/4 GL1000. 20 kBaud > synchronization mechanism integrated in the protocol (no expensive quartz needed) Application Area Automotive engineering. simulation cockpits and especially on drones (UAVs).MOST 5/2 Flash Bootloader 2/22 MICROSAR MOST Multilog ● VN2610 – USB-Interface for MOST ● FlexRay CANalyzer. parameterization) with FlexRay. Standards and appropriate Vector Products 1/2 Bus System CAN Description CAN (Controller Area Network) was developed by the Robert Bosch GmbH in the early eighties and was internationally standardized (ISO 11898) in 1994. Avionics and space technology ● ● .) Automotive engineering (e. founded by leading automotive OEMs and suppliers. ARINC 825 specifies both the fundamental communication within CAN-based subsystems and between CAN subsystems. Key protocol applications of CANaerospace are in engineering simulators. GL3000/4000/4200 MICROSAR LIN Multilog Network Designer LIN VN8900 XL-Interface-Family 3/8 3/12 5/2 ● ● ● ● ● ● ● ● ● ● ● ● 2/18 MOST MOST (Media Oriented Systems Transport) has been developed especially for the transmission of multimedia data in automobiles.CANaero 5/2 2/16 ● ● ● ● ● ● ● ● Protocol resp. tuner.MOST CANoe. Galley Inserts). securityrelevant applications. MOST bus system characteristics: > optical data transmission up to 25 Mbit/s > ring structure of the bus system > usage of the standardized XML Function Catalog > plug&play capability FlexRay has been designed as a bus system for all securityrelevant applications as well as for transmission of large amount of data in automobiles. LIN (Local Interconnect Network) has been developed especially for the cost-efficient communication of intelligent sensors and actuators in automobiles.g. LIN bus system characteristics: > master/slave architecture > time-controlled data transmission > single-wire data transmission max. ARINC 826 specifies Software Data Load over CAN.FlexRay CANape CANoe.LIN/CANoe. is the definition of an open reference architecture for ECU-specific software. Description Exchange Format AUTOSAR The goal of the development partnership. Automotive engineering (multimedia applications.g. networking within a seat) CANalyzer.FlexRay Flash Bootloader FlexCard Cyclone II SE/E-Ray FRstress MICROSAR FR Multilog Network Designer FlexRay VN3300. which for example are interconnected by AFDX. basic software Page 2/2 2/54 2/6 2/44 2/28 ARINC 8xx CANaerospace ARINC 810 and 812 specify communication between modules in the on-board galley (Galley Master.g. The focus here is on power management. brake-by-wire. networking of infotainment devices e. DVD changer. VN3600 and VN7600 FlexRay-Interfaces Appropriate Vector Product AUTOSAR Evaluation Bundle AUTOSAR Services AUTOSAR Basic Software Modules AUTOSAR Tools MICROSAR DIAG CANalyzer.Bus Systems. Embedded Network Protocols. the XML based FIBEX format (Field bus Exchange) is predominantly used. FlexRay bus system characteristics: > data transmission up to 10 Mbit/s > redundant implementation of all networks > deterministic transmission behavior As an exchange format for tools for the configuration of bus communication (design. etc. Application Area Automotive ECUs. highspeed backbone for other bus systems) CANalyzer. automation engineering Appropriate Vector Product All Vector Products Page LIN Automotive engineering (body electronics bus e.
PassThru re-programming Ethernet/IP Car2x.g. It describes the information exchanged between the ECUs in such a system.com . railway engineering. development of electronic control units. FlexRay.J1939 CANbedded J1939 CANoe/CANalyzer. ISO 14230) and “Unified Diagnostic Services” (UDS. The ODX format (Open Diagnostic Data Exchange) is based on the ASAM-MCD-2D-Basic working draft. agricultural engineering Marine engineering Appropriate Vector Product CANoe. EMBEDDED NETWORK PROTOCOLS. SAE J1708 defines a serial. ECU Calibration. Keyword Protocol 2000 (KWP2000. The main benefit of XCP is the independence concerning the transport layer.vector. GL3000/4000/4200 CANape CANdelaStudio CANdesc CANoe CANoe. The main focus is on transmission of periodic signals and real-time capability.J1939 CANalyzer. Application Area Commercial vehicle engineering. Process Management or Vehicle Diagnostics at: Internet: www. and can be implemented free of license. electronic control units.ISO11783 CANbedded J1939 CANape CANoe. vehicles engineering.CANopen CANalyzer. SPI. This interface offers functionality for bus systems – such as CAN and J1708 – as well as for higher layer protocols such as J1939 and J1587.1. In the meantime they continue to grow in importance in the embedded environment. Description Exchange Format J1939/ ISO11783 J1939 is a communication protocol based on CAN for realtime data exchange between electronic control units (ECUs) in the area of commercial vehicles. Manufacturers of vehicles. which covers all manufacturers. engine control ◆ X/XX = Product information included in this catalog ● = Product information included in other application area catalogs or on the internet.com/catalog/ • E-mail: catalog@vector.DiVa vFlash Indigo RP1210 API 3/30 ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● KWP2000/ UDS 3/14 5/12 ODX Diagnostics of vehicle electronic control units 5/10 5/12 RP1210 The RP1210 specification defines an open interface (API) between Windows-based applications and in-vehicle communication networks. CANopen is maintained by “CAN in Automation” (CiA). measurement and calibration CANoe. UDS-on-CAN). (CCP). ISO 14229) are standardized diagnostic protocols for electronic control units. XCP can be used also in nonCAN networks (e. The physical access to the ECU is possible via a serial connection (“K-line” KWP-on-K-Line) or via CAN (KWP-on-CAN. The SAE J1587 Standard regulates communication and standardized data exchange between different ECU based on SAE J1708 networks. NMEA 2000® is a communication protocol based on J1939 from the National Marine Electronics Association (NMEA) for the realtime data exchange between electronic control units in maritime electronics. STANDARDS AND APPROPRIATE VECTOR PRODUCTS Protocol resp.J1939 CANalyzer. Vehicle ECUs.IP CANalyzer. CAN embedded CANoe. ISO11783 is a further development for agricultural engineering.DiVa vFlash Indigo CANdelaStudio CANdelaFlash ODX Studio CANape CANoe CANoe.IP MICROSAR IP 2/20 ● ● XCP/CCP CANape XCP software component CANoe Option XCP GL1000. ECU Testing. bidirectional network for use in the commercial vehicle industry. XCP is an improved and generalized version of the CAN Calibration Protocol V2.J1587 Page 3/6 ● ● ● ● ● ● ● NMEA 2000 1/3 3/6 J1587/ J1708 Commercial vehicles engineering CANopen Automation engineering.BUS SYSTEMS. Diagnostics. Commercial vehicles engineering. SCI). The CANopen profile family specifies standardized communication mechanisms and device functionalities. Please request further catalogs about the application areas Development of Distributed Systems. Ethernet-based networks and the protocols built upon them are used in IT networks for decades. factory automation Automotive engineering. The purpose of this standard is to provide a unified communication capability via a standardized PC interface basically intended for flashing but also for diagnostics and other purposes. automation engineering. and testers can write and exchange electronic control unit data in the uniform ODX format.J1939 CANoe. measurement and calibration Diagnostics of vehicle electronic control units.CANopen CANerator CANopen ProCANopen CANeds CANopen Master Source Code CANopen Slave Source Code PassThru XL Library 3/28 3/20 3/24 ● ● ● ● ● J2534 The SAE J2534 standard defines the re-programming of ECUs via a PassThru interface.
+ = additional application area Development of Distributed Systems ECU Software Components Process Management Vector Product ASAP2 Editor ASAP2 Lib ASAP2 Tool-Set AUTOSAR Basic Software (MICROSAR) CANalyzer CANape Option Adv.Application Areas of the Vector Products 1/4 The following matrix gives you an overview which Vector products support you in your specific application area. ++ = main application area.DiVa CANopen Master Source Code CANopen Slave Source Code CANscope CANstressD/DR ECU Testing Diagnostics ECU Calibration ++ ++ ++ Page ● ● ● ++ 2/2 ++ + + + + + ++ ++ ++ ++ ++ ++ ++ ++ ++ ++ ++ ++ ++ + ++ ++ ++ + ++ ++ + ++ + + ++ ++ ++ ++ ++ ++ ++ + ● ● ● ● ● 3/2 3/12 3/6 3/8 ● ● ● 5/10 3/14 ● ● 3/28 ● ● ● ● ● ● 3/20 3/24 ● ● . Multimedia Option GPS Option Simulink XCP Server CANbedded CANbedded Gateway CANbedded J1939 CANbedded LIN CANdb++ Admin.J1939 CANdbLib CANdelaStudio CANdelaFlash CANdesc CANdito CANeds CANerator CANopen CANextender CANgraph CANister CANlog 3 and 4 CANoe CANoe.
Please request further catalogs about the application areas Development of Distributed Systems. CANcaseXL.pm eASEE.vector. VN3600. CANcardXL.rqm eASEE. GL3000/ 4000/4200 High Resolution Timer Indigo Multilog Network Designer CAN/LIN/FlexRay ODX Studio osCAN PassThru XL Library ProCANopen RP1210 API Test Automation Editor Timing Analyzer vFlash VN2610 USB Interface for MOST VN3300. VN7600 Interfaces for FlexRay VN8900 VT System VX1000 XL-InterfaceFamily (e. ECU Calibration. Process Management or Vehicle Diagnostics at: Internet: www.cdm eASEE.com . …) Development of Distributed Systems ECU Testing Diagnostics SteuergeräteECU Calibration Kalibrierung SteuergeräteECU Software SoftwareComponents Komponenten ProzessProcess management Management ++ Seite Page ● 2/46 2/50 2/52 2/44 ++ ++ ++ ++ + ++ ++ ++ ++ ++ ++ + ++ ++ ++ ++ + ++ ++ ++ ++ ++ ++ + ++ + ++ ++ ++ ++ ++ ++ ++ + ++ ++ ++ ++ 1/5 ● ● ● ● ● 5/6 5/2 ● ● ● 4/4 ● ● ● ● 4/2 ● ● ● ● 4/6 5/12 ● ● ● ● ● ● X/XX = Product information included in this catalog ● = Product information included in other application area catalogs or on the internet.com/catalog/ • E-mail: catalog@vector.APPLICATION AREAS OF THE VECTOR PRODUCTS Vector Product COMPASS DaVinci Component Tester Configurator Pro Configurator Kit Developer eASEE.chm eASEE. ECU Testing.g.sdm EEPROM Emulations Modul Flash Bootloader FlexCard Cyclone II FRstress GL1000.
LIN.com . FlexRay. a test is performed based on your specified hardware and compiler combination. Flash. LIN. FlexRay. HIS. etc. Vector can also integrate drivers.g. > Communication software for CAN. diagnostics. FlexRay. e. It is assembled according to the following criteria: > Basic software that is needed (depends on functionality) > Bus system > Hardware > Vehicle manufacturer or platform Before delivery. CANopen.com/ecat_es The list for CANopen can be found on the product pages for the Master and Slave source code: www. This solution lets you port your application conveniently and quickly onto different hardware platforms and for different OEMs. Application Areas You can obtain basic software from Vector for the following use areas: > Hardware drivers for CAN. real-time operating systems. Ethernet. LIN. > Available in numerous OEM-specific variants > Proven algorithms used in production development at all OEMs > Support of many different hardware platforms via a standardized API > Customization of basic software for your use case > Simple. OSEK. Ethernet and MOST > Administration of nonvolatile data (EEPROM. Timer. ADC. etc. tool-supported configuration You can get mature standardized basic software from Vector for ECU communication. Ethernet and MOST > Gateway solutions for CAN. EEPROM programming and control of IO drivers. Hardware For the latest list of supported hardware platforms for automotive software please visit our e-catalog: www. PWM. flashing. Flash) > Diagnostics with error memory module > Watchdog > Flash Bootloader > Operating system > Calibration protocols XCP and CCP > Higher protocols: J1939. EEPROM. You get a software package specially tailored to your project.vector.Use of Standardized Basic Software for ECUs Supported Hardware Platforms and Vehicle Manufacturer (OEMs) 1/6 Overview of advantages > Support of the standards AUTOSAR. drivers supplied by semi-conductor manufacturers.canopen-solutions. If necessary. IEC. ISO. SAE. etc.
Mercury. Dongfeng. BMW.vector-academy. Honda. Fisker. Land Rover. Mini. Volvo AB. Mitsubishi > NAC. Volkswagen. PSA > Renault > Saab. Buick > Cadillac. SsangYong > TATA > Vauxhall. Seat. Claas > DAF. Pontiac. FCC. Suzuki. Chevrolet. Daimler. Skoda. Lancia. Nissan > Opel > Peugeot.ECU SOFTWARE Training In the framework of our training program. Geely. Lincoln > MAN Commercial Vehicles. Smart. Fiat. For more information on individual training events and dates please visit: www. Bugatti. Ford > GAC. please contact your Vector Sales representative. Porsche. Mazda.com OEMs and brands from A-Z (1) > Alfa Romeo. VW Commercial Vehicles If your OEM is not included in the list. Nanjing MG. An independent variant of the basic software is available for non-OEM-specific communication. Saturn. Hyundai (HMC) > Isuzu > Jaguar > Kia > Lamborghini. Maybach. Brilliance. GMC. Bentley. ◆ 1/7 (1) Revision level: January 2011 . Citroen. SAIC. Vector can develop basic software for other automotive OEMs and brands upon request. Chrysler. we can offer you OEM-specific training courses and workshops for our software components and Flash Bootloader in our classrooms as well as at your business site. GM-Daewoo > Holden. FAW-VW. Mercedes. Volvo. Daimler Commercial Vehicles > FAW. Hummer. Chery. Scania. Aston Martin. Ferrari. Audi > BAIC.
even with safety-related content according to ISO DIS 26262. installation and coaching. Services for the development of ECU software . Model-based software development can also be provided. which you use in your development. our consultation and support is entirely based on your needs. we can provide the following support: > Product-related Software Engineering Services In conjunction with Vector embedded software products. e. in the framework of joint workshops. support. and has been successfully supporting customers worldwide in developing ECU software and networking ECUs. Starting with your aspired goals.g. Our experts bring success to your project with individually tailored technical consulting and engineering services. In every phase of development. helps you in tasks such as these: > Introducing a new operating system > Optimizing an existing software architecture > Porting your application software to a multi-processor ECU > Layout of safety-related “mixed SIL” systems > Migration of ECUs to FlexRay or AUTOSAR > Engineering Services Our engineers would be glad to take on the specification and development of your ECU software. our engineers work together with you to plan and implement an individual package of services. > Technical consulting In taking on your technical challenges. Vector has been creating software components as well as professional tools. our expert team provides you with technical consulting or individual concept development. This lets you attain maximum relief of work load and ideal transparency. Projects are handled in close coordination with your project team and based on a process that is optimally aligned to your needs. which we would also be glad to provide at your business site. Application Areas > ECU Software Development > Vehicle Networks Design ECU Software In developing your ECU software with our embedded standard software. we can offer you professional support with training.Technical Consulting/Engineering Services Individual support in the development of ECU software and vehicle networks 1/8 Overview of Advantages > Tailored support > Quick implementation of your application > Sustained build-up of know-how For over 15 years. review. Our technical consulting. such as CANbedded or MICROSAR.
you can obtain the following support from Vector: > Technical Consulting Technical consulting focuses on sustainable transfer of the necessary technological information. Vehicle Networks In the development of vehicle networks.vector. For a detailed description of our service line-up in the area of ECU software. please refer to the datasheets on AUTOSAR Services and Software Development Services.ECU SOFTWARE Contact We would be glad to support you on your projects. Please feel free to contact us at: www. we conceptualize solutions together with you for: > Distribution of vehicle functions > Creating and extending network architectures > Optimizing your system layout > Definition of routing concepts for gateways > Engineering Services Beyond technical consulting. During individual workshops.com/contact Our services line-up ranges from a standard “Extended Integration Package (EIP)” via the development of system functions and software integration to the take-over of overall responsibility for all application software. we would also be glad to handle all of the project related development tasks such as: > Specification of CAN. Close cooperation with our experts guarantees intensive knowledge transfer to your professional team. LIN and FlexRay based vehicle networks > Specification of individual communication protocols > Creating and maintaining communication relationships between the ECUs > Specifications of gateway components ◆ 1/9 Services for Vehicle Networks .
diagnostics. Many OEMs and their suppliers are already benefiting from our know-how. diagnostics and flash download for initial sample submission to the OEM > Tailored support from entry-level to the take-over of entire software projects For over 15 years. Vector is the market leader in OEM-specific standard software. bus-off) > Flash download using an EEPROM emulation in RAM memory . It offers an efficient entry into your project and enables early and successful execution of initial network testing at the OEM.g. Our experts bring success to your project too with individually tailored software engineering services. Application Areas > Extended Integration Package (EIP): Extended integration of the standard software on your ECU as quick entry-level assistance in an initial sample submition for network testing at the OEM > System Functions and Software Integration: Full integration of the standard software with your application and development of additional system functions > Complete Application Software: Full development of your ECU applications Extended Integration Package (EIP) The Extended Integration Package is a predefined project scope for integration of OEM-specific standard software on your ECU. including control of the start and stop states as well as sleep and wake-up > Basic diagnostic functionality including implementation of error memory entries concerning communication errors (e.g. e. Vector has been developing software components and professional tools and has been successfully supporting customers worldwide in the development of ECU software. timeout. flash download and low level drivers. for communication.Software Engineering Services Professional Support for your ECU software 1/10 Overview of Advantages > Take advantage of our expertise in embedded standard software for your project > Quick implementation of the communication. It includes: > Installation of the basic software on your ECU hardware with the help of a sample application > Specification-conformant configuration of the standard software and the OEM-specific system modules > Test execution with the OEM-specific tool chain > Test reports on fulfillment of OEM specification requirements The following functions are started up with the EIP: > Communication on the vehicle bus. operating systems.
Typical project contents: > Specification-conformant configuration and integration of the standard software on your ECU hardware > Development of specific auxiliary functions. quality gates and production release by Vector Complete Application Software Perhaps you do not wish to develop your application software yourself and are seeking a partner that can handle its implementation for you? We would be glad to assume responsibility for executing an entire ECU software project. In addition.vector. for controlling the communication buses and error behavior.com/contact System Functions and Software Integration Perhaps you want to focus more on your application development and are seeking a partner to assume responsibility for implementing a portion of your software project. Using our support. Please find your personal contact at: www. project services include: > Creating documentation such as requirements specification. you get maximum work load relief and ideal transparency on the current status of the project. We can offer you project support tailored to your individual needs.ECU SOFTWARE Contact We would be glad to support you in your projects. we link it completely to your software application.g. We integrate the standard software on your ECU hardware under consideration of your design and OEM requirements. the development can be performed according to ISO DIS 26262. test specifications > Project control by project and release planning. ◆ 1/11 Vector can develop individual system functions or the entire application software . design documentation. The project is executed in close cooperation with your project team and is based on a process that is optimally aligned to your needs: from prototype to serial production. If you need safety-related software. Model-based software development can also be performed. MISRA reports. e. even for multi-processor systems In addition. project report. development of special routings or signal conversions for the communication channel used > Development of the entire diagnostic software component (SWC) > Development of sensor and actuator software components > Integration of the flash bootloader. ranging from requirements analysis to verification. We would be glad to develop additional system functions for you. status reports.
your Trusted Partner for AUTOSAR Projects As one of the first premium members of the AUTOSAR Consortium. Overview of the Vector AUTOSAR Solution Vector supports you in all development phases of projects with tailor-made AUTOSAR solutions for design. Many advantages are realized by standardization and using clearly specified interfaces between the basic software modules to the functional software : e. Vector‘s experience with AUTOSAR is also reflected in AUTOSAR tools and the basic software.g.0. Practice-based extensions and features implemented in anticipation of AUTOSAR Release 4. The proven GENy tool is used for the communication modules. MICROSAR – The AUTOSAR Basic Software Modules from Vector With MICROSAR. Vector offers AUTOSAR-conformant software modules for efficient development of production-mature ECUs. development and implementation: DaVinci – The AUTOSAR Tools from Vector > DaVinci Developer is the optimal tool for graphic-based definition of AUTOSAR software components and for configuration and generation of the MICROSAR RTE. complex device drivers) in DaVinci Configurator Pro. In partnership with TTTech Automotive. > DaVinci Configurator Kit optimally supports you in integrating modules you have developed (e. FlexRay IsoTp.g.x and cover all aspects of the AUTOSAR standard. . They are based on AUTOSAR Release 3.g. e. Vector.Solutions for AUTOSAR 2/0 The core idea of AUTOSAR is to master the growing complexity of software in modern vehicles by standardization. > DaVinci Component Tester lets you conveniently test AUTOSAR software components on a PC. XCP and J1939. This active participation was recognized by the AUTOSAR Consortium in awarding Vector the first AUTOSAR Premium Member Award in 2007. encrypted communication. Vector can already offer you software modules for end-to-end communication validation of ISO DIS 26262 Integrity Level D per AUTOSAR 4. Vector has been actively involved in the development of new technology for a long time. The development partnership founded by leading automotive OEMs and suppliers set the goal of defining an open reference architecture for ECU software. which is already being used in numerous production projects.0 complete this solution. with support of Ethernet. > DaVinci Configurator Pro is used to create a consistent configuration of the MICROSAR basic software from Vector and of basic software from third-party suppliers. re-usability of the same software for different microcontrollers and functions with a simultaneous increase in quality.
> You do not need to migrate to AUTOSAR all at once. which you can use individually or in conjunction with third-party components. > The eASEE Automotive Solution lets you specify and manage in-vehicle electronic systems. We support your projects with experience and integration know-how. Vector can offer you a complete solution for your projects together with numerous other tools for ECU testing as well as measurement and calibration. Support for Your Projects Vector accompanies you from the early evaluation phase to production projects. The Easy Way to Get Started with AUTOSAR Besides training courses on fundamentals and on specific products. offers you a reliable solution for safety-relevant ECUs per ISO DIS 26262. > You are choosing a future-oriented solution with a reliable partner. Vector can show you solutions for stepwise migration without loss of quality. > Network Designer is used to design a vehicle’s networking architecture and data communication for the networks. Further Tools Take advantage of the comprehensive Vector tool chain to develop your AUTOSAR ECUs and systems. > Vector. Together with you.AUTOSAR When choosing the AUTOSAR solution from Vector: > You benefit from a seamless tool chain: From the design of your system to the development of your functional software and integration of the software in your ECU. > With MICROSAR you get a complete set of basic software from a single source. The AUTOSAR Evaluation Bundle from Vector gives you a solution for prototype development of AUTOSAR systems. Data communication in the networks can also be defined with eASEE. 2/1 >> CONTENTS AUTOSAR Evaluation Bundle MICROSAR MICROSAR OS MICROSAR COM MICROSAR CAN MICROSAR FR MICROSAR LIN MICROSAR IP MICROSAR MOST MICROSAR MEM MICROSAR SYS MICROSAR DIAG MICROSAR CAL MICROSAR EXT 2/2 2/6 2/10 2/12 2/14 2/16 2/18 2/20 2/22 2/24 2/26 2/28 2/32 2/34 MICROSAR IO MICROSAR RTE MICROSAR Safe Identity Manager for AUTOSAR DaVinci Developer DaVinci Component Tester DaVinci Configurator Pro DaVinci Configurator Kit AUTOSAR Services 2/36 2/38 2/40 2/42 2/44 2/46 2/50 2/52 2/54 . In the process. Vector also offers on-site support in project implementation and in introducing the AUTOSAR software. together with its partner TTTech Automotive. your own in-house developments or third-party components. it does not matter whether you are using Vector products. This ranges from defining requirements to designing distributed functions and defining components such as sensors. > CANdela Studio let’s you specify the diagnostic functionality of your ECUs. It offers a structured approach for training in the AUTOSAR methodology and gives you an opportunity to evaluate the functionality and performance of the AUTOSAR software. actuators and ECUs. we can develop a comprehensive solution for your ECU.
If your focus is on evaluation of the AUTOSAR method and tools. In this case. you can obtain the AUTOSAR Evaluation Bundle with MICROSAR CANoe Emulation as well. Since the tools and basic software are at a level of production maturity. to implement a complete set of ECU software > Enables realistic evaluation of execution time and memory requirements for your ECU project > Conveniently test your software components on a PC on the Virtual Function Bus level > Available for many different micro-controllers and the PC as runtime platform > Quick way to train in AUTOSAR with a detailed sample project > Support of both AUTOSAR-conformant files and conventional description files The AUTOSAR Evaluation Bundle is a comprehensive package of AUTOSAR basic software and design and configuration tools from Vector. Runtime Environment (RTE) and basic software (BSW). you work with the same methods. As input for configuring the MICROSAR software. you would use an ”ECU Extract of System Description“ AUTOSAR Tools AUTOSAR Basic Software Additional Tools V2.x. The DaVinci tools are tailored to AUTOSAR and simplify your work in designing complex AUTOSAR applications. Functions The AUTOSAR Evaluation Bundle contains all tools and software from Vector for creating a complete set of AUTOSAR ECU software.vector. Application Areas The AUTOSAR Evaluation Bundle supports both the automotive OEM − in evaluating AUTOSAR processes and methods – and suppliers in creating their first AUTOSAR-conformant ECU software. Nonetheless. You get an in-depth look into the AUTOSAR world – from the design and configuration process to implementation of the actual basic software. This package lets you develop entire ECU software with an AUTOSAR-conformant software architecture.EMBEDDED SOFTWARE AUTOSAR Evaluation Bundle The complete package for the evaluation of AUTOSAR basic software and tools Overview of advantages > Production-quality tools and basic software per AUTOSAR Release 3.com/contact . you would use the PC with the CANoe test and development tool from Vector as the runtime platform and can work without startup of real hardware.4 2011-05 More Information: www. you can reliably use the Vector solution to evaluate AUTOSAR with regard to: > Efficiency of the basic software > Integration of the tools in your development environment > Potential uses of AUTOSAR concepts in your application area The AUTOSAR Evaluation Bundle also provides an optimal foundation for initial developments of AUTOSAR-conformant software components for service providers who focus on the application level. which consists of software components (SWCs). tools and basic software as in the development of a real ECU.
vector. > The DaVinci Component Tester is used to conveniently test – on a PC . Based on SWC description files.EMBEDDED SOFTWARE Training In the framework of our training program. The SWCs serve as a basis for the RTE configuration process. efficiently and flexibly.implementation of the SWCs. Using the graphic editor. The GENy tool offers special support in configuring the communication basic software. For more information on individual training events and dates on the Internet please visit: www. FIBEX.com (AUTOSAR XML) or as an alternative a conventional network description file (DBC. You can export this data via standard formats. > The CANdelaStudio tool is used to define diagnostic data for your networks and ECUs. available as option) MICROSAR DIAG Contains the AUTOSAR basic software modules > Diagnostic Event Manager (DEM) > Diagnostic Communication Manager (DCM) > Function Inhibition Manager (FIM) MICROSAR MEM Contains the AUTOSAR basic software modules > NVRAM Manager (NVM) Designing software components with DaVinci Developer Configuration of the Basic Software with DaVinci Configurator More Information: www. > The DaVinci Configurator Pro tool is used to configure the basic software modules. LDF). The modules are bundled in these functionally interrelated MICROSAR products: MICROSAR RTE > Contains the AUTOSAR RTE (Runtime Environment) MICROSAR OS Contains the AUTOSAR basic software module Operating System (OS) > Implementation of “Scalability Class” SC1 (SC2-SC4 available as option if supported by processor) > Fully compatible with OSEK OS > Supports Schedule Tables MICROSAR SYS Contains the AUTOSAR basic software modules > Communication Manager (COMM) > Cyclic Redundancy Check Routines (CRC) > ECU Manager (ECUM) > Development Error Tracer (DET) > Watchdog Manager (WDGM) > Watchdog Interface (WDGIF) > Scheduler Module (SCHM) > Basic Software Mode Manager (BswM. we can offer various training events and workshops for MICROSAR in our classrooms as well as at your business site. you can emulate a complete Virtual Function Bus (VFB). The MICROSAR basic software modules contained in the AUTOSAR Evaluation Bundle implement all functions of AUTOSAR Release 3. > The DaVinci Developer tool gives you an easy way to generate AUTOSAR-conformant ECU applications. which you also perform with DaVinci Developer. you can describe your AUTOSAR software components quickly and clearly and define their interfaces.vector-academy.x and many extensions. You can use the convenient and intuitive user interface to adapt parameter values for your ECU project.com/contact . and use the data in automatic configuration of the MICROSAR diagnostic basic software.
you might use it to integrate AUTOSAR software components in an ECU you have developed in a model-based approach using tools like MATLAB® Simulink®. available as option) > FlexRay Driver (FRDRV. available as option) > SPI Driver (SPIDRV) > Input Capture Unit Driver (ICUDRV) > Pulse Width Modulation Driver (PWMDRV) > A/D Conversion Driver (ADCDRV) Special functions DaVinci Developer has an import/export interface for AUTOSAR XML files.Broadcast Announce Message > CMDT . All MICROSAR products conform to: > “Implementation Conformance Class” ICC3. contained in LINIF) > LIN State Manager (LINSM) MICROSAR COM Contains the AUTOSAR basic software modules > Communication (COM) > Network Management Interface (NM) > PDU Router (PDUR) > I-PDU Multiplexer (IPDUM) available as option MICROSAR IO Contains the AUTOSAR basic software modules > IO Hardware Abstraction (IOHW) MICROSAR CAL Contains the AUTOSAR basic software modules > General Purpose Timer Driver (GPTDRV) > Watchdog Driver (WDGDRV) > Microcontroller Unit Driver (MCUDRV) > EEPROM Driver (EEPDRV) > Flash Driver (FLSDRV) > CAN Driver (CANDRV) > LIN Driver (LINDRV. This interface lets you exchange design and configuration data.com/contact . For example. and > “Configuration Conformance Class” CCC 2.Connection Mode Data Transfer MICROSAR FR (available as option) Contains the AUTOSAR basic software modules > FlexRay Interface (FRIF) > FlexRay Transport Protocol (FRTP) > FlexRay Network Management (FRNM) > FlexRay State Manager (FRSM) MICROSAR LIN (available as option) Contains the AUTOSAR basic software modules > LIN Interface (LINIF) > LIN Transport Protocol (LINTP. More Information: www.EMBEDDED SOFTWARE > Memory Abstraction Interface (MEMIF) > EEPROM Abstraction (EA) > Flash EEPROM Emulation (FEE) MICROSAR CAN Contains the AUTOSAR basic software modules > CAN Interface (CANIF) > CAN Transport Protocol (CANTP) > CAN Network Management (CANNM) > CAN State Manager (CANSM) MICROSAR J1939TP (available as option) Contains the transport protocols > BAM .vector.
Vector also offers the AUTOSAR Evaluation Bundle for CANoe as a PC runtime platform. binding statements cannot be made without specific processor device numbers. MICROSAR CANoe Emulation As an alternative.0 or 9. LIN or FlexRay bus systems > Simulation of I/O ports via CANoe panels > Connection of real sensors and actuators > Easy debugging of the application by stopping the global time of the entire emulation when a breakpoint is reached > Interactive and automated tests of the AUTOSAR ECU software and execution of remaining bus simulations > Your own custom extensions are possible. and so it is not provided.0 SP5 or higher > Microsoft Visual Studio 7. 8. and a detailed guide on its use > AUTOSAR Training at Vector (4 days) Further Options The AUTOSAR Evaluation Bundles CAN.vector. Vector can also provide coaching at your business site. Upon request. Available Hardware Platforms The AUTOSAR Evaluation Bundle is available for the most commonly used 16-bit and 32-bit hardware platforms. The EEPDRV is not needed in this case. e.microsar.g.com/contact > PORT Driver (PORTDRV) > Digital IO Driver (DIODRV) MICROSAR EXT Contains the AUTOSAR basic software modules > CAN Transceiver Driver (CANTRCV) > FlexRay Transceiver Driver (FRTRCV) > LIN Transceiver Driver (LINTRCV) MICROSAR Safe (optional) Complete solution for safety relevant functional software according to ISO DIS 26262.EMBEDDED SOFTWARE Contact and Availability You will find information on the availability of hardware-specific MICROSAR BSW modules at: www. to emulate complex device drivers System requirements for the MICROSAR CANoe emulation > CANoe 7. emulations of the MICROSAR CAL modules and the MICROSAR OS are included.0 Functional principle: CANoe as target platform More Information: www. LIN and FlexRay may be used with one another in any combination. Additional Included Features > Sample application in source code. Special functions of the MICROSAR CANoe emulation In conjunction with CANoe. The flash memory of the AUTOSAR ECU is also emulated. Vector can support you with extensive MICROSAR Coaching at initial startup and during integration of the MICROSAR basic software in your application.com/contact . the emulation comprises the following functions: > Access to the CAN.1.vector. Due to the hardware dependency of the MICROSAR CAL modules and the MICROSAR OS. Find your contact person at: www. The Vector Sales Team would be glad to provide this information. In this case.com/availability/ We can also tell you about OEM-specific versions and custom support for your AUTOSAR projects.
Each AUTOSAR BSW module is assigned to a MICROSAR package. and after generation you can integrate them with the functional software. Along with managing the entire flow of information. This produces a complete set of ECU software. Modules from the MICROSAR OS and MICROSAR CAL packages are hardware-dependent.vector. You are able to develop your functional software platform independ- ently. the MICROSAR RTE also assures consistency in the exchange of information. you will need a run-time environment (RTE). because the AUTOSAR architecture follows a consistent strategy of hardware abstraction.g. For detailed descriptions of individual packages and the MICROSAR RTE. You can configure all necessary MICROSAR BSW modules based on your project’s requirements. MICROSAR consists of the MICROSAR RTE and MICROSAR basic software modules (BSW). If the functional software consists of AUTOSAR-conformant SWCs. please refer to the separate datasheets. e. Vector is able to offer a number of OEM-specific BSW modules such as the diagnostic modules.EMBEDDED SOFTWARE MICROSAR The Vector Solution for AUTOSAR ECU Software Overview of Advantages > All AUTOSAR basic software from a single source > Many innovative extensions perfectly tuned to one another > Reliable foundation for your AUTOSAR ECU software > Already in production use at leading OEMs and TIER1 suppliers > Simplifies development of platform-independent functional software > Available for many hardware platforms and automotive OEMs > Mature and long-term solution from an AUTOSAR Premium Member MICROSAR is the AUTOSAR solution for your ECU software. which cover all aspects of the AUTOSAR standard and many extensions. Properties Development of the MICROSAR basic software modules is founded on the Vector development process for standard modules. The MICROSAR RTE handles communication between the SWCs and their access to data and services from the BSW modules. They contain the implementations of AUTOSAR standard services you will need for your functional software.com/contact . which is V2. Vector combines the BSW modules needed in individual “software integration packages”. Vector offers these modules for a large number of different hardware platforms and compilers. Application Areas The BSW modules of the MICROSAR packages assure basic functionality of the ECU. The operating system MICROSAR OS is available for single core and multi coreprocessors.3 2011-06 The MICROSAR packages contain all modules of the AUTOSAR standard More Information: www. to enable quick change-out of the controller device. Based on its ongoing contacts with OEMs.
link-time or post-build) > Communication stack is versatile in its use > Supports multiple ECUs > Optional delivery as source code > Together with MICROSAR Safe: well-suited for safety-relevant functions (ISO DIS 26262) Production Use The MICROSAR BSW modules are already being used in production projects. It is also possible to produce a configuration based on commonly used network description files (DBC.EMBEDDED SOFTWARE Training In the framework of our training program. compiler.).x > Assistants and timely checks support you in achieving consistent configuration of your basic software > Scalable.com based on SPICE.x.g. The packets MICROSAR OS Multi-Core. AUTOSAR Release 3. with/without RTE. it is possible to integrate MCAL drivers of different AUTOSAR Releases.0. etc.vector.). Early in the configuration process. all MICROSAR Software modules undergo systematic integration tests for the specific conditions of your application (hardware platform. All MICROSAR packages offer the following features: > Efficient memory utilization and short execution times > Available for production use > Conformant to AUTOSAR Release 3.x and Extensions All MICROSAR basic software modules fundamentally conform to AUTOSAR Release 3. In addition. Moreover. adaptable to your specific application > Optimally integrated into your development process > AUTOSAR Monitoring for testing and analysis of ECUs > User-selectable configuration point (pre-compile. The intuitive. we can offer various training events and workshops for MICROSAR in our classrooms as well as at your business site. the work of manually developing or adapting the basic functionality of ECU software is replaced by configuration of the BSW modules. user-friendly and well coordinated AUTOSAR tools from Vector (DaVinci) support the user in this process. these tests may be extended to cover software modules from third-party producers (e. complex parameter groups and DaVinci tools are used to consistently configure the MICROSAR RTE and MICROSAR BSW modules More Information: www. the MICROSAR MOST package lets you connect any AUTOSAR ECU to a MOST ring. All of these extensions are compatible with the rest of the MICROSAR basic software modules of Release 3. The DaVinci tools require an “ECU Extract of System Description” file as input.vector-academy. Multi User Support of the DaVinci tools enables simultaneous work on a project by multiple users. MCAL drivers). MICROSAR lets you benefit from Vector’s many years of experience in implementing embedded standard software.x. OEM. all DaVinci tools check the validity of individual parameters. Before delivery. MICROSAR J1939 and XCP as well as the modules from MICROSAR IP already contain important functionality from Release 4. Consistent and Simple Configuration With AUTOSAR.com/contact . etc. processor device. FIBEX. Upon request. LDF. For more information on individual training events and dates on the Internet please visit: www.
This saves you time compared to step-wise configuration of individual BSW modules. engine ECUs. You use DaVinci Configurator Pro to configure the BSW modules You use DaVinci Developer to create the MICROSAR RTE for your application More Information: www. In case of invalid configurations. In the bottom-up approach. > The MICROSAR RTE is configured with DaVinci Developer. In the top-down approach. while topdown is ideal for the other MICROSAR BSW modules. Vector recommends the proven GENy configuration tool for configuring the communication-related MICROSAR modules. This contains the description of important RTE-internal variables such as Send/Receive ports. This reduces configuration effort significantly. door ECUs. Scalability In addition to fulfilling AUTOSAR requirements. > You can configure the MICROSAR BSW modules with DaVinci Configurator Pro. This involves using DaVinci Developer to automatically generate SWC service ports (including runnables) based on BSW service ports. etc. the MICROSAR BSW modules also provide a number of functional extensions. This extension of the AUTOSAR method simplifies integration of the basic software in your ECU and reduces integration time.vector. Flexible Development Process With the DaVinci tools it is possible to execute a top-down configuration or a bottom-up configuration to integrate the MICROSAR products in your development process. AUTOSAR Monitoring AUTOSAR Monitoring simplifies testing and analysis of ECUs with such tools as CANape or CANoe. and you can create your first functionally-capable ECU in a short period of time.EMBEDDED SOFTWARE their interrelationships. MICROSAR is already being implemented in a wide range of ECUs. GENy enables cross-module configuration of specific parameters and parameter groups. DaVinci Developer is used to connect the ports of the SWCs via service mapping to the ports of the BSW modules – in part automatically. A combination of the two approaches offers optimal results. This scalability makes the MICROSAR modules the optimal solution for both small and challenging applications. In testing. MICROSAR may also be used with other operating systems such as Linux or QNX. This approach gives you quick training in AUTOSAR. For more details on DaVinci tools from Vector. the configuration of the interfaces of the functional software is done by using the basic software. it also ensures a compatible configuration of interdependent modules. The extended configuration options let you deactivate unnecessary functions to optimize the MICROSAR code for your application.com/contact . The MICROSAR A2L Generator generates an A2L file for this purpose. central gateways. internal states of the MICROSAR BSW modules and of COM signals. if possible. the design tool for SWCs. such as steering angle sensors. you read them out at runtime with XCP. the tools make recommendations for corrections. please refer to the relevant datasheets. GENy is supplied with DaVinci Configurator Pro. Bottom-up is especially well-suited to MICROSAR DIAG and MICROSAR IO.
GENy has a special graphic mode that is exclusively used to edit post-build parameters. which can be flashed directly to the ECU. Afterwards. In the framework of a maintenance contract. Safety according to ISO DIS 26262 For use of the MICROSAR BSW in safety-related functions. The MICROSAR BSW modules check for compatibility of the replaced configuration at runtime. This option lets you develop physical multiple-ECUs within a car line or multi-configuration of ECUs that are used in different car lines.com/contact User-Selectable Configuration Point The configuration point of all MICROSAR basic software modules is user-selectable.vector. CMDT) > MICROSAR Safe – Solution for safety-relevant application software according to ISO DIS 26262 More Information: www. Per AUTOSAR Configuration Conformance Classes CCC1 to CCC3. transport layer for Ethernet.microsar. The source code lets you make pre-compile optimizations and simplifies testing. Other Services > Consulting on system design > Extension of standard BSW modules per customer wishes > Development of customer-specific software components (SWC) > Support in adapting existing functional software > Complete software integration in your ECU – including thirdparty software > Migration of existing software to AUTOSAR > Hotline. For more information.com/availability/ or upon request. GENy offers optimal process support for the post-build configured communications-related MICROSAR modules. ECU Variants To save on logistical costs in AUTOSAR ECUs. see the datasheet on the AUTOSAR Identity Manager. Post-build lets you replace certain parameter values from the communication matrix without compiling in the ECU.EMBEDDED SOFTWARE Contact and Availability MICROSAR BSW modules are available for a large number of commonly used microcontrollers and in OEM-specific variants.com/contact . License and Maintenance Vector offers you flexible licensing – individually tailored to your requirements. Please find your contact person at: www. Optional Delivery of Source Code The MICROSAR modules are also available as source code. choices are: pre-compile. You can obtain more information at www.vector. Vector – together with TTTech Automotive – offers a complete solution for your AUTOSAR ECU. upon request. special workshops and training courses on the topic of embedded software and AUTOSAR List of available MICROSAR Packages > MICROSAR OS – AUTOSAR operating system > MICROSAR SYS – Basic ECU functions > MICROSAR DIAG – Diagnostics > MICROSAR MEM – Memory Management > MICROSAR COM – Network independent communication > MICROSAR CAN – Communication via CAN > MICROSAR LIN – Communication via LIN > MICROSAR FR – Communication via FlexRay > MICROSAR IP – Communication via Ethernet > MICROSAR MOST – Communication via MOST > MICROSAR CAL – AUTOSAR conform controlling of the microcontroller peripherals > MICROSAR IO – Direct connection of the microcontroller peripherals to the application > MICROSAR EXT – Controlling external hardware > XCP – Measurement and calibration of an AUTOSAR-ECU using XCP incl. For more information. the MICROSAR modules can be delivered with the optional Identity Manager. you get software updates that keep you current to the latest level of development. you can select the configuration point for each BSW module. FlexRay und CAN > MICROSAR J1939TP – Operation of an AUTOSAR ECU in J1939 networks (BAM. GENy generates platform-specific HEX files. please refer to the MICROSAR Safe datasheet. link-time or post-build.
Scalability classes SC1 through SC4 are supported. robust operating system core.g. 16. Properties MICROSAR-OS is based on the AUTOSAR OS specification. MICROSAR OS is fully conformant to the AUTOSAR OS specification and supports all scalability classes: SC1: Real-time operating system implemented per the OSEK/VDXOS standard and extended to include schedule tables SC2: Real-time operating system with time synchronization and monitoring of the time behavior of individual tasks and interrupt service routines SC3: Real-time operating system with memory protection mechanisms on microcontrollers with suitable hardware support SC4: Combines scalability classes SC2 and SC3 Multi-core: Operating system for multi-core processors. quick and resource-economizing operating system > Short boot times > MICROSAR OS provides an ideal runtime environment for embedded software and forms the basis for migration to AUTOSAR-conformant applications > Supplied as source code > Numerous auxiliary functions simplify software development > Quality process per SPICE Level 3 > Graphic configuration tool for easy configuration of the operating system > TimingAnalyzer for runtime analysis of MICROSAR OS applications > Available for many 8. This makes synchronized and simultaneous execution of tasks possible in a distributed system. the time transmitted over the FlexRay bus. an extension of the practice-proven OSEK/VDX-OS operating system standard. 32 and 64 bit microcontrollers > Available as multi-core operating system. > Memory protection (SC3. too MICROSAR OS is a pre-emptive real-time multitasking operating system with optimized properties for use on microcontrollers. It ensures that the data of other applications are not destroyed. Vector’s many years of experience in developing operating systems and drivers for microcontrollers are bundled into this small. SC4) Memory protection protects memory areas so that applications can be reliably integrated. e. This standard was extended to include functions for time monitoring and memory protection as well as functionalities that support distributed applications in networks. Functions > Synchronization with the global system time Schedule tables can be synchronized with the global system time. MICROSAR OS Modul .MICROSAR OS The Real-Time Operating System for the AUTOSAR Standard 2/10 Overview of Advantages > Small.
When protection encounters a defective application section. These measured data can later be used as practice-based values in designing and integrating future applications. checks for conformance to execution time restrictions and represents the schedule tables in a well-organized graphic display. The “High Resolution Synchronization” option gives you resolutions in the microsecond range without increasing interrupt load.com Contact and Availability For information on the availability of hardware-specific MICROSAR BSW modules go to: www. > Execution time measurements (SC2.AUTOSAR Training In the framework of our training program we can offer various training courses and workshops on MICROSAR at our classrooms or at your business site. The graphic user interface visualizes system behavior clearly and concisely. Analysis is performed for every task and every interrupt with the following information: Priority.vector. SC4) You can use functions of scalability classes 2 and 4 to measure the execution times and interrupt disable times of applications. this does not have any negative effects on other running applications.microsar. SC4) Timing protection ensures that assumptions made in the early design phase related to execution times are preserved during runtime as well. MICROSAR-OS conforms to AUTOSAR Specification 3. execution time and end time. Scope of Delivery > Operating system core as source code > Graphic configuration and generation tool for Windows XP/Vista/Windows 7 > Command line based generator > BSW modules description > Description files for DaVinci Configurator Pro > Documentation > TimingAnalyzer 2/11 ◆ The complete AUTOSAR solution from Vector The Vector AUTOSAR solution consists of the DaVinci tools. > TimingAnalyzer Design Assistance TimingAnalyzer design assistance computes the task execution schedule. this may enable resolutions into the microseconds range.com/contact > Timing Protection (SC2.x Additional Services Vector offers you worldwide support related to AUTOSAR: > Training events > Design consulting > Customer-specific implementations > Hotline > Software maintenance The extent and form of all services are tailored to your wishes. the MICROSAR BSW and the MICROSAR RTE. For more information on individual training events and dates please visit: www. it is necessary to synchronize and trigger schedule tables with very high precision using internal or external signal sources. period. which implement this precision without simultaneously increasing interrupt load. You will find information on general properties of the BSW modules from the MICROSAR packages as well as details on functional features of the individual DaVinci Tools in the particular datasheets. .vector-academy. Depending on the controller.com/availability/ We would be glad to provide you with information on OEMspecific versions and individual support for your AUTOSAR projects. Optional Extensions > High Resolution Timer If resolutions finer than 1ms are needed for the timers. Find your contact person at: www. the mechanisms of the High Resolution Timer are advisable. > High Resolution Synchronization for Schedule Tables In some applications.
This makes integration of applications simpler and more reliable. the Multi-Core variant offers various mechanisms for coordinating and synchronizing tasks running on different cores. SC4) Memory protection ensures that the data of different applications do not corrupt one another. Optional Extensions > Memory protection (SC3. V2. Functions The functions and interfaces correspond to the functions of MICROSAR-OS.com/contact .e.EMBEDDED SOFTWARE MICROSAR OS Multi-Core AUTOSAR operating system for multi-core processors Overview of Advantages > Supports symmetrical and asymmetrical multi-core processors > Fast and stable kernel > Easy migration of OSEK/VDX-based projects due to compatible API > Memory protection and timing protection available Application Areas You use MICROSAR OS Multi-Core whenever developing a multicore system according to the AUTOSAR specification. starting and stopping of alarms or Schedule Tables. Typical requirements of a multi-core system are: > Greater computing performance at the same oscillator frequency > A safety concept based on separate processing of application components > A safety concept based on redundancy. SC4) Timing protection ensures that a defective application section will not impair other processes that are running. > Inter-Core Communication The operating system provides an efficient interface for consistent data exchange between two cores in the form of the Inter-OS Application Communicator (IOC). In addition. > Timing protection (SC2.vector. > Shared Resource Access Access to shared resources is synchronized by Spinlocks. > Inter-Core Coordination Processes on different cores are synchronized by task activations.0 2011-03 Architecture model of a multi-core application with MICROSAR OS Multi-Core and MICROSAR Basic Software More Information: www. i. parallel processing of the same algorithms > Reduced power consumption by reducing the oscillator frequency Multi-core processors satisfy these requirements without requiring any additional space on the PC-board. setting of events.
EMBEDDED SOFTWARE More Information: www.vector.com/contact .
they handle control and full integration in the ECU software of bus-specific communication modules from MICROSAR CAN. PDUR and IPDUM from MICROSAR COM. > The Generic Network Management Interface (NM) bundles inter-bus network management activities of all of the ECU’s communication channels. Per AUTOSAR architecture.MICROSAR COM AUTOSAR Basic Software Modules for Communication 2/12 Overview of Advantages > Code and execution time optimized by application-specific configuration > Very efficient signal access via function macros > Contains important functionality of AUTOSAR Release 4. MICROSAR FR. MICROSAR LIN. COM or DCM modules or to other networks (gateway). it synchronizes wake-up and sleep of the communication channels. As NM coordinator. etc. Functions The BSW modules from MICROSAR COM contain functions defined in AUTOSAR Release 3. a user may use an I-PDU Multiplexer (IPDUM) in the communication stack of the ECU software. MICROSAR IP and MICROSAR MOST. They are bus-independent and are needed in every communication stack. event-triggered. > Optionally. NM. All necessary tasks for transmitting messages and for cross-bus network management activities are handled by the configurable BSW modules COM. For a gateway ECU. In the opposite direction. A key task is to implement bus-independent signals of the functional software in PDUs. MICROSAR COM Modules . you do not need any additional software. IPDUM supports multiple usage of fixed I-PDUs with variable data contents. the PDUR receives the PDUs and routes them to the relevant services of the NM. The COM and PDUR BSW modules from MICROSAR COM enable routing of signals and TP or application messages. > The PDU Router (PDUR) distributes the PDUs to the bus-specific AUTOSAR communication modules. so that they can transmit the information.x: > Services of the COM module organize transmission of messages according to their send type (cyclic. These services can support any number of communication channels.0 and many other useful extensions > Extended support for NM coordinators > NM module: OSEK NM compatibility is configurable > Supports simultaneous operation of AUTOSAR NM and OSEK NM in NM migration projects The basic software modules (BSW) of MICROSAR COM include AUTOSAR services for ECU communication. Application Areas MICROSAR COM lets users develop their functional software by a fully bus-independent approach.).
with Burst Transmission) together with CANTP or optimized routing as extension to ASR 3. > PDUR: Generic interface for integrating a TP and bus communication as complex device driver > PDUR: Intra-ECU communications for TP connections > PDUR: Optimized routing per ASR 4. PDUR: Transport of long I-PDUs and signals via CANTP and via J1939 as specified in ASR 4.0 together with CANTP and FRISOTP > NM: Synchronous sleep and wake-up of multiple networks via different NM coordinators > NM: Backup coordinator > NM: Pre-compile optimizations such as function macros > NM: Support of OSEK NM (configurable) > NM: Mixed operation of OSEK and AUTOSAR-NM on one channel Scope of Delivery > Software modules as library with C header files. You will find information on properties of BSW modules from the MICROSAR packages and detailed descriptions of functional features of individual DaVinci Tools in the relevant datasheets.0): > COM: Indication and timeout flags for signals and signal groups > COM: Signal conversion. > COM: Extension by signal callout functions. the BSW modules from MICROSAR COM contain the following functionalities.0 (e.microsar. e.com Contact and Availability You will find information on the availability of hardware-specific MICROSAR BSW modules at: www. optionally as source code > Command line based generator (for Windows NT/2000/XP/Vista/ Windows 7) > BSW modules description > DLLs for configuration with GENy > Documentation The complete AUTOSAR solution from Vector The AUTOSAR solution from Vector consists of the DaVinci tools. we can offer various training events and workshops for MICROSAR in our classrooms as well as at your business site. Other TPs are available upon request.0 (ASR 4. Some of them are part of AUTOSAR Release 4. MICROSAR-basic software and the MICROSAR RTE.vector-academy.AUTOSAR Training In the framework of our training program.0.com/availability/ We can also tell you about OEM-specific versions and custom support for your AUTOSAR projects.vector. This conversion may be configured with an A2L ASAP2 database. to integrate gateways as complex device drivers.com/contact The following functions are optionally available: > COM: TX deadline monitoring > PDUR: TP layer fan-out and zero cost operation > PDUR: Transmit cancellation and change parameter request Furthermore.g.g. For more information on individual training events and dates please visit: www. > COM: Invalidity declaration of TX signals in case of RX signal timeout > COM: Deactivation of the TX confirmation interrupt > COM: Pre-compile optimizations such as function macros for very efficient signal access > COM. Find your contact person at: www. ◆ 2/13 Configuring the COM module with GENy .
MICROSAR CAN AUTOSAR Basic Software Modules for CAN Communication The MICROSAR CAN package contains the BSW modules defined in the AUTOSAR architecture for CAN communication: CANIF. You can also combine MICROSAR CAN with the separately available MICROSAR J1939TP package to enable operation of an AUTOSAR ECU in a J1939 network. The BAM and CMDT transport protocols are available for this. The following functions are available as options for the CANIF module: > Support of an external CAN controller > Increased number of Full CAN objects by combining multiple CAN controllers on one physical CAN bus (Common CAN) > Individual polling of messages in Full CAN objects > Support of multiple Basic CAN objects to further optimize acceptance filters > Rx queue for short interrupt execution times In addition. BSW modules from MICROSAR CAN or MICROSAR J1939TP contain the following extensions.0): > CANIF: Double hash search algorithm for filtering the Rx messages > CANNM: Pre-compile optimizations. Application Areas MICROSAR CAN is used to handle communication in CAN networks. It is also well-suited as a foundation for calibration with XCP. for single-channel systems > CANSM: Optimization of the wakeup process by wakeup detection at ECU startup > CANSM: Support of ECU Passive Mode > CANSM: Extended Callback Interface for the error states “BusOff Begin” and “BusOff End” MICROSAR CAN modules . CANNM.g.x. CANTP. gateways or flashing. Some of them are from AUTOSAR Release 4. BAM and CMDT 2/14 Functions The BSW modules in MICROSAR CAN contain functions defined in AUTOSAR Release 3. Overview of Advantages > Code and execution time are optimized based on needspecific configuration > Inter-module configuration of all communication-specific software modules > Fast wakeup handling at ECU startup > Includes high-performance gateway functionality > CANTP: ISO 15765-2 compatibility is configurable > CANNM: OSEK NM compatibility is configurable > Optionally available: J1939 Transport Layer.0 (ASR 4. e. CANSM and CANXCP.
> CANTP: Supports full duplex communication > CANTP: Supports mixed addressing (11 bit CAN ID). > CANTP: ISO 15765-2 compatibility is configurable > CANTP: Sets BlockSize and STmin at runtime > BAM and CMDT: Transport protocols for J1939 networks available as option Scope of Delivery > Software modules as library with C header files. a complete communication stack for CAN can be formed using MICROSAR CAN together with the BSW modules from the separately available MICROSAR COM. typically for CAN/LIN gateway applications > CANTP: Optimized routing per ASR 4. Find your contact person at: www.com Contact and Availability You will find information on the availability of hardware-specific MICROSAR BSW modules at: www.vector-academy. MICROSAR-basic software and the MICROSAR RTE.g. with Burst Transmission) together with the PDUR from MICORSAR COM.vector. we can offer various training events and workshops for MICROSAR in our classrooms as well as at your business site. optionally as source code > Command line based generator (for Windows NT/2000/XP/ Vista/Windows 7) > BSW modules description > DLLs for configuration with GENy > Documentation The complete AUTOSAR Solution from Vector The AUTOSAR solution from Vector consists of the DaVinci tools. In case of error. 2/15 Other MICROSAR Products for a Complete CAN Communication Stack Based on the AUTOSAR architecture. ECUM and COMM from MICROSAR SYS > XCP ◆ Vector offers a comprehensive range of products and services for your CAN projects . MICROSAR CAL and MICROSAR EXT packages.AUTOSAR Training In the framework of our training program.com/availability/ We can also tell you about OEM-specific versions and custom support for your AUTOSAR projects. IPDUM) from MICROSAR COM Modules in MICROSAR CAL and MICROSAR EXT are available for many microcontrollers and transceivers. you will still need the following BSW modules: > Hardware-specific CAN driver (CANDRV) from MICROSAR CAL > Hardware-specific transceiver control (CANTRCV) from MICROSAR EXT > General communication modules (COM.0 (e. an automatic repetition is executed. You will find information on properties of BSW modules from the MICROSAR packages and detailed descriptions of functional features of individual DaVinci Tools in the relevant datasheets. To interface MICROSAR CAN to the application and the hardware. Other relevant MICROSAR Products for CAN > DCM and DEM from MICROSAR DIAG > DET. PDUR. NM.com/contact > CANSM: Checks whether states were successfully set in the CAN driver (CANDRV) or CAN transceiver driver (CANTRCV). For more information on individual training events and dates please visit: www.microsar.
Application Areas MICROSAR FR is used to handle communication in FlexRay networks. e. an AUTOSAR-conformant package for FlexRay communication.g. It contains the following BSW modules defined in the AUTOSAR architecture: FRIF. immediate startup after passive wakeup (ASR 4.0) > FRSM: Support of ECU Passive Mode (ASR 4. extended error handling by State Change Notification.x. configurable time delay for FlexRay startup at passive wakeup as well as configurable number of wakeup patterns (ASR 4. FRSM and FRXCP. Direct sending of NM user data from the COM module > FRNM and FRSM: Detection and recovery from synchronization losses (Long/Short Term Sync) (ASR 4. GetClockCorrection. it is ideal as a foundation for calibration with XCP.EMBEDDED SOFTWARE MICROSAR FR AUTOSAR Basic Software Modules for FlexRay Communication Vector offers you MICROSAR FR. gateways or flashing. conformant to ISO 10681. It is compatible with the rest of the MICROSAR BSW modules. for single-channel systems.com/contact . However. CancelTransmit.0) > FRNM: Pre-compile optimizations.0). and upon request it can replace FRTP in your FlexRay communication stack. ReadCCConfig and LpdU reconfiguration > FRDRV & FRIF: FIFO support > FRIF: Automatic repetition of job list execution in case of errors or loss of bus synchronization > FRISOTP: Optimized TP routing for gateway operation (ASR 4.0).0 (ASR 4. The following functions are available as an option: > FRISOTP: Unknown Message Length Transmission > FRIF: Dual Channel Redundancy for redundant transmission of frames as well as PDU-specific voting functions for the SWCs In addition.5 2011-02 More Information: www. GetSyncFrameList. MICROSAR FR also includes the BSW module FRISOTP. FRTP or FRISOTP. FRNM. Some of them are part of ASR 4.0: > FRDRV: Optimized wakeup during operation (WUDOP) > FRDRV & FRIF: Support of the following ASR 4. it makes sense to use an AUTOSAR OS V2. the BSW modules from MICROSAR FR contain the following services. In anticipation of AUTOSAR Release 4. Overview of Advantages > Small code size and short execution times due to optimized administration of job lists of the FlexRay interfaces > Either the FRTP (AUTOSAR) or FRISOTP (ISO 10681) transport protocol may be used > Support of ECU passive mode in the FlexRay State Manager > Early detection of synchronization losses Functions The BSW modules in MICROSAR FR contain functions defined in AUTOSAR Release 3.0). Furthermore.vector.0 APIs: GetChannelStatus.0) Operating System FlexRay basic software modules can be used entirely without an operating system.
NM. Vector osCAN). MICROSAR CAL.com Contact and Availability You can find information on the availability of hardware-specific MICROSAR BSW modules at: www. ECUM and COMM from MICROSAR SYS > XCP Additional Services > Consultation in system design > Integration of basic software in existing ECUs > Extension of standard modules per customer requirements > Development of customer specific AUTOSAR software components (SWC) > Hotline. Find your contact person at: www. For more information on individual training events and dates please visit: www.microsar. special workshops and training events on the topic of embedded software and AUTOSAR Vector offers a comprehensive portfolio of products and services for your FlexRay projects More Information: www. a complete communication stack for FlexRay can be made with MICROSAR FR together with the BSW modules from the separately available MICROSAR COM. Ideally suited for FlexRay applications is MICROSAR OS from Vector.com/availability/ We would be glad to provide you with information on OEM-specific versions as well as customized support for your AUTOSAR projects. we can offer various training courses and workshops on MICROSAR at our classrooms or at your business site. Scope of Delivery > Software modules as library with C header files. You will also need the following BSW modules to interface MICROSAR FR to the application and hardware: > Hardware-specific FlexRay driver (FRDRV) from MICROSAR CAL > Hardware-specific transceiver control (FRTRCV) from MICROSAR EXT > General communication modules (COM. optionally as source code > Command line based generator (for Windows NT/2000/ XP/Vista/Windows 7) > BSW modules description > DLLs for configuration with GENy > Documentation The complete AUTOSAR Solution from Vector The AUTOSAR solution from Vector consists of the DaVinci tools. MICROSAR basic software and the MICROSAR RTE. IPDUM) from MICROSAR COM The modules in MICROSAR CAL and MICROSAR EXT are available for many different microcontrollers and transceivers.com/contact or a conventional OSEK-OS (e. PDUR.vector.com/contact . MICROSAR SYS and MICROSAR EXT packages. Other MICROSAR Products for a complete FlexRay Communication Stack Based on the AUTOSAR architecture. Other MICROSAR Products for FlexRay > DCM and DEM from MICROSAR DIAG > DET. You will find information on properties of BSW modules from the MICROSAR packages and detailed descriptions of functional features of individual DaVinci Tools in the relevant datasheets.vector.g.vector-academy.EMBEDDED SOFTWARE Training In the framework of our training program.
LINSM. BSW modules from MICROSAR LIN contain the following services.0 (ASR 4. Application Areas MICROSAR LIN is used to handle communication tasks for a LIN Master in a LIN network. LINTP is a component of LINIF. it may be used as a foundation for gateways or flashing.x Slaves. the user can acquire information on the connected LIN1. Functions The BSW modules in MICROSAR LIN contain functions defined in AUTOSAR Release 3. LINTP. Some of them are specified in AUTOSAR Release 4. Per AUTOSAR. In addition. This is especially appealing for controllers with segmented memory. This information is saved in the ECU Configuration Description and is considered when configuring the master.x.3 and LIN2. > LINTP: Extends gateway functionality for precise switchover of the schedule tables for diagnostic requests and responses > LINSM: Extended interface for monitoring the LINSM submodes for controlled switchover of the LIN schedule tables > LINSM: Optimized startup behavior by automatic selection of a schedule table (configurable) Configuration With GENy support.0): MICROSAR LIN modules . In addition. Overview of Advantages > Core component of the complete LIN communication stack for AUTOSAR ECUs > Optimized routing of diagnostic requests to LIN Slaves > Quick start of the LIN channel > Reliable switching of schedule tables possible > Based on Vector’s many years of experience with production software for LIN 2/18 > LINIF: Configurable wakeup delay > LINIF/LINSM: Production/Development Error Reporting (DEM/DET) has been extended by additional and more precise events > LINIF and LINTP: Separately configurable memory mapping of configuration data for LINIF and LINTP. The MICROSAR LIN product includes two separate generators for LINIF and LINTP for this purpose.MICROSAR LIN AUTOSAR Basic Software Modules for LIN Communication MICROSAR LIN contains the BSW modules defined in the AUTOSAR architecture for LIN communication: LINIF. This lets the master evaluate the response error bits sent by the slaves and then initiate the associated DEM events.
com/contact Scope of Delivery > Software modules as library with C header files. ECUM and COMM from MICROSAR SYS 2/19 ◆ Other MICROSAR Products for a Complete LIN Communication Stack Based on the AUTOSAR architecture.vector-academy. Other Relevant MICROSAR Products for LIN > DET.microsar. > Hardware-specific LIN driver (LINDRV) from MICROSAR CAL > Hardware-specific transceiver control (LINTRCV) from MICROSAR EXT > General communication modules (COM. a complete communication stack for LIN is formed by MICROSAR LIN together with the BSW modules from the separately available MICROSAR COM. For more information on individual training events and dates please visit: www.com Contact and Availability For information on the availability of hardware-specific MICROSAR BSW modules go to: www. PDUR) from MICROSAR COM The modules in MICROSAR CAL and MICROSAR EXT are available for many different microcontrollers and transceivers.vector.com/availability/ We would be glad to provide you with information on OEMspecific versions and individual support for your AUTOSAR projects. MICROSAR CAL and MICROSAR EXT packages. optionally as source code > Command line based generator (for Windows NT/2000/XP/ Vista/Windows 7) > BSW modules description > DLLs for configuration with GENy > Documentation The complete AUTOSAR Solution from Vector The AUTOSAR solution from Vector consists of the DaVinci tools. Find your contact person at: www. you will still need the following BSW modules: Vector offers you a comprehensive range of products and services for your LIN projects . You will find information on properties of BSW modules from the MICROSAR packages and detailed descriptions of functional features of individual DaVinci Tools in the relevant datasheets. MICROSAR-basic software and the MICROSAR RTE.AUTOSAR Training In the framework of our training program we can offer various training courses and workshops on MICROSAR at our classrooms or at your business site. To interface MICROSAR LIN to the application and hardware.
> Simultaneously and efficiently measure and calibrate many parameters with XCP on Ethernet. > Perform vehicle diagnostics per ISO 13400-2 (DoIP) over IP. > Conveniently access vehicle data. In its MICROSAR IP. it contains the base package for IPv4: IPBASE.0.x compatible interfaces which assure compatibility to the rest of the MICROSAR BSW modules. The modules DHCP and TCP are available as an option. Modules from IPBASE assure basic functionality of the TCP/IP protocols MICROSAR IP modules .0. In addition. The package contains BSW modules for Ethernet communication defined in the AUTOSAR architecture: ETHXCP. ETHSM. ETHIF. Application Areas With MICROSAR IP in the ECU and a conventional PC as a communication partner. MICROSAR IP implements the necessary gateway functionality in combination with other MICROSAR packages. you can do the following with no extra hardware other than an Ethernet cable: > Quickly flash large quantities of data.0 > Contains both UDP and TCP protocols > Configurable number of sockets > Execution time advantages due to reduced number of copying operations > Supports Diagnostics over IP (DoIp) per ISO 13400-2 > Data is exchanged up to 200 times faster than over a conventional High-Speed CAN interface Functions The BSW modules in MICROSAR IP contain functions defined in AUTOSAR Release 4.MICROSAR IP AUTOSAR Basic Software Modules for Communication over Internet Protocol via Ethernet 2/20 The Internet Protocol (IPv4) based on TCP/IP via Ethernet represents a very widely used standard for transporting data at high rates. SOAD. > ETHXCP: Ethernet-specific transport layer for XCP (Universal Calibration Protocol) per the ASAM standard > IPBASE: The basic package for IP contains all necessary modules from the RFC standard: Socket. ICMP. it requires a gateway in the vehicle. Standardization of this Internet technology for use in automotive projects is part of AUTOSAR Release 4. ARP and IPv4.x. Overview of Advantages > Supports Internet Protocol IPv4 > Compatible with AUTOSAR Release 3. > ETHIF: The AUTOSAR Ethernet Interface enables hardwareindependent control of the various Ethernet drivers. > In future: Intelligent charging of batteries (Smart Charging according to ISO/IEC 15118 The superior data throughput of Ethernet enables enormous reductions in overall flash and diagnostic times. > ETHSM: The AUTOSAR Ethernet State Manager handles activation/deactivation of the microcontroller and transceiver. which interconnects the various in-vehicle networks to the external Ethernet. MICROSAR IP contains AUTOSAR 3. However. UDP. In addition. Vector is providing this as a supplement to AUTOSAR 3.
vector-academy.com/contact per AUTOSAR requirements. we can offer various training courses and workshops on MICROSAR at our classrooms or at your business site. go to: www. You will also need the following BSW modules to interface MICROSAR IP to the application and hardware: > Hardware-specific Ethernet driver (ETHDRV from MICROSAR CAL) > Hardware-specific transceiver control (ETHTRCV from MICROSAR EXT) > General communication module (PDUR) from MICROSAR COM Modules in MICROSAR CAL and MICROSAR EXT are available for many different microcontrollers and transceivers. ECUM and COMM from MICROSAR SYS > XCP 2/21 ◆ Vector offers you a comprehensive portfolio of products and services for your IP projects . You will find information on properties of BSW modules from the MICROSAR packages and detailed descriptions of functional features of individual DaVinci Tools in the relevant datasheets. > SOAD: The Socket Adapter implements the communication via PDUs defined in AUTOSAR as socket-oriented communication (TCP/IP). Other Relevant MICROSAR Products Based on the AUTOSAR architecture. Find your contact person at: www. MICROSAR-basic software and the MICROSAR RTE.microsar.AUTOSAR Training In the framework of our training program.com/availability/ We would be glad to provide you with information on OEMspecific versions and customized support for your AUTOSAR projects. Configuration MICROSAR IP is configured with the familiar configuration tool GENy. SOAD also contains the diagnostic functionality defined in ISO 13400-2 (DoIP). MICROSAR CAL and MICROSAR EXT packages. Scope of Delivery > Software modules as library with C header files. in flash routines. optionally as source code > Command line based generator (for Windows NT/2000/XP/ Vista/Windows 7) > BSW module description > DLLs for configuration with GENy > Documentation The complete AUTOSAR Solution from Vector The AUTOSAR solution from Vector consists of the DaVinci tools.vector.com Contact and Availability For information on the availability of hardware-specific MICROSAR BSW modules. XCP and diagnostic applications. IP-specific configuration parameters are saved as an extension in the “ECU Configuration Description”. Other Relevant Products for Ethernet > DCM and DEM from MICROSAR DIAG > DET. For more information on individual training events and dates please visit: www. This property offers tremendous execution time savings in gateway routing. The IPBASE modules are optimized to minimize the number of copying operations. a complete communication stack for Ethernet is formed with MICROSAR IP together with the BSW modules from the separately available MICROSAR COM.
MICROSAR MOST contains all of the services required to implement gateway functionality to CAN. MICROSAR MOST is interfaced to the MOST bus via a Network Services Library and a low level driver (MOSTDRV). and the product is fully compatible with the AUTOSAR architecture. > DISP: The Dispatcher is a template for interfacing the MOSTIF module to a Network Services Library for MOST. LIN or FlexRay. Overview of Advantages > Extends AUTOSAR features to include MOST communication > Flexibly routes messages and signals between MOST buses and any desired networks > Provides seamless interface to a Network Services Library for MOST > Supports MOST 150 Functions The MOST-specific BSW module MOSTIF and the Dispatcher (DISP) template are Vector-specific extensions of the AUTOSAR standard: > MOSTIF: MOST Interface for hardware-independent conversion of the PDUs to be transmitted to MOST frames. Vector now offers MICROSAR MOST. The MICROSAR OS from Vector is ideally suited for MOST applications.MICROSAR MOST AUTOSAR compatible Basic Software Modules for MOST Communication Previously. LIN. MOST (Media Oriented Systems Transport) was not part of the AUTOSAR standard. FlexRay and Ethernet buses.g. message and TP routing > Sending signals on MOST via Notification Services > Support of MOST protocols MHP and AMS Operating System MOST basic software modules can be used entirely without an operating system. In addition. 2/22 Application Areas MICROSAR MOST lets you connect AUTOSAR ECUs to a MOST ring to exchange data on the control and asynchronous channel. MOSTIF is compatible with the BSW modules of AUTOSAR Release 3. BSW modules from MICROSAR MOST are interfaced to the application software in a way similar to CAN. Vector osCAN). The BSW modules from MICROSAR MOST are offering the following services: > Support of signal. However. MOST specific configuration parameters are saved as an extension in the “ECU Configuration Description”.x. an AUTOSAR-compatible embedded software solution for your MOST application. it is advisable to use an AUTOSAR OS or a conventional OSEK-OS (e. Configuration MICROSAR MOST is configured with the familiar GENy configuration tool. It contains the BSW modules MOSTIF and DISP. MICROSAR MOST modules .
com Contact and Availability For information on the availability of hardware-specific MICROSAR BSW modules go to: www. a Network Services Library and a low level driver (MOSTDRV) are also necessary.com/contact For gateways.AUTOSAR Training In the framework of our training program we can offer various training courses and workshops on MICROSAR at our classrooms or at your business site. Vector would be glad to create a Low-Level Driver for interfacing the Network Services Library for MOST to your specific hardware. Vector offers customized solutions that take into account the special aspects of OEM-specific data formats in configuration. combine to form a communication stack for MOST. Low-Level Driver In the framework of project work. 2/23 Other Relevant MICROSAR Products for MOST > DCM and DEM from MICROSAR DIAG > DET. These two components are not included with the MICROSAR MOST product.vector.com/availability/ We would be glad to provide you with information on OEMspecific versions and individual support for your AUTOSAR projects.vector-academy. You will find information on properties of BSW modules from the MICROSAR packages and detailed descriptions of functional features of individual DaVinci Tools in the relevant datasheets. For more information on individual training events and dates please visit: www. in particular. Scope of Delivery > Software modules as library with C header files. Vector offers a comprehensive range of products and services for MOST projects . ECUM and COMM from MICROSAR SYS ◆ Other MICROSAR Products for a complete MOST Communication Stack MICROSAR MOST. Find your contact person at: www.microsar. To interface this communication stack to a MOST bus. optionally as source code > Command line based generator (for Windows NT/2000/XP/ Vista/Windows 7) > BSW module description > DLLs for configuration with GENy > Documentation The complete AUTOSAR Solution from Vector The AUTOSAR solution from Vector consists of the DaVinci tools. MICROSAR-basic software and the MICROSAR RTE. together with the general communication modules COM and PDUR from the MICROSAR COM packet.
x. The Basic Software Modules (BSW) from MICROSAR MEM are fast. This gives the functional software hardware-independent access to memory. Vector offers platform-optimized solutions. e. For special requirements. EA and FEE. you will need the BSW modules NVM and MEMIF from MICROSAR MEM.g. The following functions are optionally available: > NVM: Block type “DATASET_ROM” with multiple ROM blocks > NVM: Data protection with CRC8 MICROSAR MEM modules . They support management. writing and erasing persistent application data in flash and/or EEPROM memories. The application does not need to know the specific type of memory that exists on the platform or whether this memory is internal to the controller or externally connected to it. They handle block-oriented and technology-independent access to the memory areas – without requiring prior knowledge of memory attributes. This involves using multiple FEE or IO modules in the ECU software. Application Areas MICROSAR MEM lets you develop your functional software platform-independently. MICROSAR MEM contains AUTOSAR services for reading. It is possible to use multiple flash or EEPROM chips in one ECU. To manage the data. depending on the use case: > When using flash memory: Flash EEPROM Emulation (FEE) from MICROSAR MEM and a flash driver (FLSDRV) from MICROSAR CAL that is suitable for your hardware. for using the EA BSW module in data flashing or optimizing the FEE module for specific hardware. MEMIF. the FEE module needs at least two flash sectors. Your memory stack will need additional BSW modules. Functions The BSW modules in MICROSAR MEM contain functions defined in AUTOSAR Release 3. In each memory stack. checking and restoring of data from nonvolatile memories (Flash or EEPROM).MICROSAR MEM AUTOSAR Basic Software Modules for Memory Management 2/24 Overview of Advantages > Exceptionally secure data transactions > Efficient data accesses > Efficient and robust management of nonvolatile memories > Redundant storage of management data increases reliability of FEE and EA modules > Inter-module configuration of the entire memory stack > Platform-optimized memory stack solution from a single source The MICROSAR MEM package contains all of the AUTOSAR modules for memory management: NVM. reliable and robust. > When using an EEPROM: EEPROM Abstraction (EA) from MICROSAR MEM and an EEPROM driver (EEPDRV) from MICROSAR CAL that is suitable for your hardware.
com/availability/ We would be glad to provide you with information on OEMspecific versions and individual support of your AUTOSAR projects.microsar.com Contact and Availability For information on the availability of hardware-specific MICROSAR BSW modules go to: www. you will need the LIBS module (CRC) from MICROSAR SYS. An update of the ECU software can be done without adjustment of the FBL. > FEE/EA: Redundant storage of management data for increased reliability. optionally as source code > Command line based generator (for Windows NT/2000/XP/ Vista/Windows 7) > BSW modules description > Description files for DaVinci Configurator Pro > Documentation The complete AUTOSAR Solution from Vector Vector offers a fully tuned AUTOSAR solution for developing AUTOSAR ECUs with its DaVinci and MICROSAR products. > FEE: Update support for adjustment of non volatile memory after ECU re-programming. Find your contact person at: www. This is done with a new configuration table (content and size). You can protect your memory data with the checksum module (CRC) at your desired security level.vector. a complete memory stack can be formed with memory services from MICROSAR MEM together with other platform-specific BSW modules from the separately available MICROSAR CAL and MICROSAR EXT packages.com/contact In addition. For more information on individual training events and dates please visit: www.vector-academy. You will find information on properties of BSW modules from the MICROSAR packages as well as detailed descriptions of functional features of the DaVinci Tools in separate datasheets. it is easy to integrate MCAL drivers from semiconductor manufacturers in any MICROSAR memory stack. To do this.0) > NVM and EA: Additional configurable transaction security. predefined maximum execution times for all MICROSAR MEM functions. 2/25 Other MICROSAR Products relevant for a Memory Stack Based on the AUTOSAR architecture. some are from AUTOSAR Release 4.0): > Fixed. > NVM: Allocates RAM for CRC memory storage > NVM: Dedicated interface for the DCM diagnostic module for direct read-out and manipulation of data blocks (ASR4. > FLSDRV and/or EEPDRV from MICROSAR CAL > DRVEXT from MICROSAR EXT for external memory chips In addition. MICROSAR MEM contains the following extensions. This enables system optimizations to shorten access times.AUTOSAR Training In the framework of our training program we offer various training courses and workshops on MICROSAR at our classrooms or at your business site. > FEE: Flexible placement of the FEE sectors in the DataFlash Scope of Delivery > Software modules as library with C header files.0 (ASR 4. ◆ Configuration Dialog for the Non volatile RAM Manager . which is a standard feature of the FEE module > FEE: High-performance administration of stored memory data > FEE: Common usage of FEE module by Flash Bootloader (FBL) and application possible – also with common memory blocks.
x: > BswM: The Basic Software Mode Manager manages specific mode change requests from the BSW modules and executes them based on AUTOSAR 3. COMM supports the bus type ”Internal”. In case of error. SCHM. LIBS. the affected BSW module or SWCs report the faulty function and error type. DET supports the Service Ports. scheduling of all BSW modules and monitoring of individual software components (SWC) of the functional software.vector. The package is platform-independent. To operate MICROSAR SYS on your hardware. ECUM. Functions The BSW modules in MICROSAR SYS contain functions defined in AUTOSAR Release 3. System services for diagnostics and the operating system can be obtained in the MICROSAR DIAG and MICROSAR OS packages. the BswM module is responsible for activating and deactivating PDU groups and NM-PDUs for diagnostics (Service Communication Control). WDGM and WDGIF. > ECUM: The ECU State Manager executes the individually configurable initialization and de-initialization of all basic software modules. It can keep the ECU awake and ready for communication as necessary. control of all communication channels. V2. It also coordinates access to the communication channels by all SWCs. Optionally. They assure start-up and operation of the ECU. DET. For example. > DET: The Development Error Tracer collects the so-called development errors of the SWCs and BSW modules. Application Areas Services from the MICROSAR SYS basic software modules (BSW) cover an important aspect of the basic functionality of your AUTOSAR ECU.6 2011-06 MICROSAR SYS modules More Information: www. Optionally. They are called by the functional software (via the RTE) and the rest of the BSW modules. including the RTE and OS. System services include power management.EMBEDDED SOFTWARE MICROSAR SYS System-related Basic Software Modules for AUTOSAR Overview of Advantages: > The ECUM module is included as either a resource-saving PreCompile variant or as a flexible Post-Build variant > Supports activation/deactivation of PDUs for diagnostics (Service Communication Control) > Cross-module configuration of modules from MICROSAR SYS and MICROSAR CAL The MICROSAR SYS package contains AUTOSAR modules that offer system services: COMM. and are an important part of each AUTOSAR ECU. you combine it with hardware-dependent drivers from the MICROSAR CAL package per the AUTOSAR architecture.com/contact . It puts the ECUs in different operating modes at the request of the SWCs. > COMM: The “communication manager“ checks the states of all communication channels connected to the ECU.2 standardized action lists.
vector-academy. the following extensions are included. Some of them are part of AUTOSAR Release 4. Configuring the SYS module with DaVinci Configurator Pro More Information: www. Scope of Delivery > Software modules as library with C header files. Galpat. March. Link-time implementation > ECUM: Supports validation of the reason for wake-up in Power SetUp and Run modes. ECUM is available as a pre-compile or post-build implementation variant > WDGM.0): > COMM: Compatibility with OSEK NM. You also define the exclusive areas settings for each module centrally. you choose between destructive and non-destructive algorithms (Checkerboard. > WDGM and WDGIF: The Watchdog Manager monitors the functional software for proper operation. Crypto Primitive Library (CPL) and E2ELIB for protection of safety-relevant communication data.com Contact and Availability You will find information on the availability of hardware-specific MICROSAR BSW modules at: www. At configuration time.0 (ASR 4. Crypto Abstraction Library (CAL). > SCHM: The Schedule Manager/BSW Scheduler coordinates execution of the BSW modules.com/contact > LIBS: The LIBS package contains the Cyclic Redundancy Check Library (CRC).vector.) and determine the memory area to be tested. WDGIF: Precise supervision of defined time windows for the watchdog (even for high resolution window watchdogs) Configuration The ECUM module can be configured with either GENy or DaVinci Configurator Pro. In addition. The CRC services. for example. etc. In configuring the SchM you define individual tasks and the cycle times of individual BSW module.com/availability/ We can also tell you about OEM-specific versions and custom support for your AUTOSAR projects. are especially important to BSW modules from the memory stack. Find your contact person at: www. > RAMTST: The hardware-independent module RAM Test enables synchronous or asynchronous checking of the physical functional integrity of the RAM memory. You will find information on properties of BSW modules from the MICROSAR packages and detailed descriptions of functional features of individual DaVinci Tools in the relevant datasheets. These libraries make various services available to the basic software modules and the functional software.vector.EMBEDDED SOFTWARE Training In the framework of our training program. For more information on individual training events and dates please visit: www. it triggers an ECU reset. optionally as source code > Command line based generator (for Windows XP/Vista/Windows 7) > BSW modules description > Description files for DaVinci Configurator Pro > Documentation The complete AUTOSAR Solution from Vector The AUTOSAR solution from Vector consists of the DaVinci tools.microsar.com/contact . MICROSAR-basic software and the MICROSAR RTE. we can offer various training events and workshops for MICROSAR in our classrooms as well as at your business site. If the Watchdog time expires.
It is suited for the series use and is available already for many OEMs. MICORSAR DIAG can be used for current and future legal requirements such as EURO VI. Functions MICROSAR DIAG contains the three BSW modules DCM.5 2011-08 MICROSAR DIAG modules More Information: www. Offering: > OEM-specific implementation of the diagnostic protocol for communication between tester and ECU > Fault memory and management > Disabling of certain functionalities based on active fault entries Combined with CANdelaStudio − the widely used specification tool for creating diagnostic data − you get a complete diagnostic solution from a single source. Their functions are described in the following sections. If your ECU requires diagnostic configuration variants. services or DTCs are combined in the generated diagnostic code. MICROSAR DIAG performs a number of tasks. Vector can offer you DEM variants that have been modified for many different OEMs.com/contact . DEM and FIM from the AUTOSAR architecture. Application Areas Diagnostics are not completely specified in AUTOSAR. Beyond the standard each OEM has its own specifications.vector. so that users can develop their own functional software (SWCs) independent of the use case. For ECUs without diagnostics specification an OEM independent package of MICROSAR DIAG is available. it is the OEM who specifies diagnostic functionality. This avoids redundancies in the ECU software. Diagnostic Event Manager (DEM) Functions According to AUTOSAR.EMBEDDED SOFTWARE MICROSAR DIAG AUTOSAR Basic Software Modules for the UDS Protocol Summary of Advantages > Customized solutions available for many automotive OEMs > Vector’s numerous years of experience in the diagnostics field > Contains all necessary extensions for use in production > Supports OBDII for DCM per AUTOSAR 3. These variants cover the requirements of the V2. For this reason Vector offers MICROSAR DIAG with OEM specific extensions. With GENy you can define up to 31 different parameter sets and save them resource-optimized in the ECU.1 > Also supports WWH-OBD (Euro VI) > Variants handling already included for diagnostic configuration > Configurable via ODX format with CANdelaStudio > Application code templates are generated for the ECU software MICROSAR DIAG contains the AUTOSAR-compatible implementation of UDS protocol ISO 14229-1:2006 and is ideal as diagnostic software for your vehicle project. because identical interfaces to the same data. Only interfaces are defined for the DEM module. MICROSAR DIAG offers a powerful solution. The support of OBDII (ISO 15031/ SAE J1979) as well as WWH-OBD (ISO27145) is available as an option.
g.com/availability/ We would be glad to provide you with information on OEM-specific variants and individual support for your AUTOSAR projects. frequency-based) > WWH-OBD (ISO27145) > Post-build configurability Diagnostic Communication Manager (DCM) Functions The DCM contains functions defined in AUTOSAR Release 3.com/contact . ECUPassiveMode) > Variants handling for diagnostic configurations > Link-time configuration > Multiple client support > Seamless interaction with the Vector Flash Bootloader > Generation of an application code template for the ECU software Function Inhibition Manager (FIM) Functions All functions of AUTOSAR Release 3.g.1 WWH-OBD (ISO27145) Post-build configuration Support of multiple diagnostic protocols per AUTOSAR In addition.vector.0.x are standard features of the MICROSAR FIM. The following functions are optionally available: > > > > Support of OBDII (ISO15031-5) per AUTOSAR 3.vector. the DCM contains the following extensions to AUTOSAR as standard features: > Inclusion of the most important UDS Services not contained in AUTOSAR 3. OccurenceCounter) > Counter and time-based error debounce algorithms > Suppression of low-priority errors when memory is full > Flexible unlearning (aging) of errors > Variants handling for diagnostic configuration > Link-time configuration > Compressed configuration data to optimize code size The following AUTOSAR functions are optionally available: > Support of combined errors > Implementation of additional error debounce algorithms (e.com/contact specific carmakers. RoutineControl Service.0 > OEM-specific extensions (e. Find your contact person at: www. A generic OEM-independent variant is also available.com Contact and Availability You will find information on the availability of hardware-specific MICROSAR BSW modules at: www. The following functions are optionally available: > Post-build configuration > Periodic or event-based evaluation of FIM status to prevent bursts in processor loading > Export of an ASAP2 file for read-out of momentary status information over XCP Configuration of the UDS or OBDII services from the DCM module with GENy More Information: www.g. as well as the necessary tasks of the application software. we offer various training courses and workshops on MICROSAR at our classrooms or at your business site.vector-academy. This version supports the following functions as standard features: > Administration of all DTC status bits per the UDS standard > Definition of individual snapshot records and extended records > Pre-defined extended records (e.EMBEDDED SOFTWARE Training In the framework of our training program.microsar. For more information on individual training events and dates please visit: www. At the end of this datasheet you find a table with an overview of all supported UDS and OBDII services.
vector. For more information on this. Since diagnostic-specific parameterization of the DCM is limited using the standard AUTOSAR 3. You can create them quickly and easily or import them from the most commonly used ODX dialects with the proven “diagnostic authoring tool” CANdelaStudio. The DEM may be configured via either a CDD file or an “ECU Configuration Description”. Scope of Delivery > Software modules as a library with C header files.0 exchange file “ECU Configuration Description”. Other Relevant Vector Products You can combine MICROSAR DIAG with the following MICROSAR products to fulfill relevant ISO standards: > MICROSAR CAN (ISO 15765-3 or ISO/DIS 14229-3) > MICROSAR FR (ISO/DIS 14229-4) > MICROSAR IP (ISO/DIS 14229-5) To parameterize MICROSAR DIAG you will need CANdelaStudio. You will find information on properties of BSW modules from the MICROSAR packages and detailed descriptions of functional features of individual DaVinci Tools in the relevant datasheets.com/contact . MICROSAR-basic software and the MICROSAR RTE. optionally as source code > Command line based generator (for Windows XP/Vista/ Windows 7) > BSW module description > DLLs for configuration with GENy > Documentation > Converters for CANdela diagnostic descriptions The complete AUTOSAR Solution from Vector The AUTOSAR solution from Vector consists of the DaVinci tools. MICROSAR DIAG is parameterized with CANdelaStudio and GENy More Information: www. the MICROSAR DCM modules are parameterized by a CDD file.EMBEDDED SOFTWARE Services for Diagnostic Applications: > Customer-specific extensions of MICROSAR DIAG > Creation of a customer-specific diagnostic application > Integration of diagnostics in your ECU software Configuration and Parameterization You can adapt BSW modules from MICROSAR DIAG to meet the needs of your application by modifying the configuration. see the separate datasheet in Vector’s diagnostics catalog.
com/contact .vector.(is handled in DEM module) Diagnostic Trouble Codes with Permanent Status Input/Output Control Functional Unit InputOutputControlByIdentifier … control I/O for each DataId Remote Activation Of Routine Functional Unit … start (stop/request 31 result) for each RoutineId 2F RoutineControl More Information: www.EMBEDDED SOFTWARE The module DCM from MICROSAR DIAG supports … … by default: UDS diagnostic services Diagnostic Service Name Service AUTOSAR The SCW has to … (ISO 14229-1) ID Extension Diagnostic and Communication Management Functional Unit … grant service DiagnosticSessionControl 10 execution … grant service ECUReset 11 X execution … calculate SecurityAccess 27 seed/key for each security level … grant service CommunicationControl 28 X execution TesterPresent 3E .(internal.(is handled in DEM module) Diagnostic Trouble Codes Clear/Reset Emission-Related 04 .(is handled in DEM module) During Current or Last Completed Driving Cycle Request Control of On-Board 08 … process each TestId System.(is handled in DEM ControlDTCSetting 85 module) Data Transmission Functional Unit … handle data ReadDataByIdentifier (RDBI) 22 acquisition for each DataId ReadMemoryByAddress 23 X .(is handled in DEM module) Data Request Emission-Related 03 . Test or Component … handle data acquisition for each InfoType ID other than Request Vehicle Information 09 the "supported ID" and DEM ones Request Emission-Related 0A .(is handled in DEM module) Diagnostic Information Request On-Board Monitoring Test … handle data acquisition for 06 Results for Specific Monitored each TestId of a MonitorId Systems Request Emission-Related Diagnostic Trouble Codes Detected 07 .(is handled in DEM module) . but data ReadDataByPeriodicIdentifier 2A acquisition is done through RDBI) . but data DynamicallyDefineDataIdentifier 2C acquisition is done through RDBI) …handle data WriteDataByIdentifier 2E access for each DataId WriteMemoryByAddress 3D X Stored Data Transmission Functional Unit ReadDTCInformation ClearDiagnosticInformation 19 14 .(internal.1 Diagnostic Service Name Service The SCW has to … (ISO 15031-5) ID Diagnostic Service Definition for CAN … handle data acquisition for Request Current Powertrain 01 each PID other than the Diagnostic Data "supported ID" and DEM ones Request Powertrain Freeze Frame 02 .(is handled in DEM module) … Optionally: OBD II diagnostic services according to AUTOSAR 3.
In addition. MICROSAR CAN. Lin.0) > IICDRV: Drivers for interfacing to external peripheral chips via the Inter-Integrated Circuit Bus (I2C) > Implementation of Interrupt Service Routines as CAT1.vector.0 (ASR 4. Dem. Pwm. So. For example. Spi and Wdg. etc. They conform to AUTOSAR Release 3. All you need to do is switch out MICROSAR CAL to integrate the appropriate drivers. Dio. Port. Icu. Gpt. CAT2 or void-void function (configurable) > Flexible integration of error handling with user-configurable interface names such as Det. > CANDRV: Notification (Callback) on message reception and after successfully sending a message. Can.) depending on the requirements of your application. These drivers are fully compatible with the AUTOSAR specifications of the “Microcontroller Abstraction Layer”. you could do this to obtain a complete communication stack or memory management per AUTOSAR specification. MICROSAR CAL contains the following extensions. This makes it possible to automatically execute application-specific code. Functions The MICROSAR CAL package contains the driver modules Adc. Each MICROSAR CAL driver is optimized controllerspecifically.EMBEDDED SOFTWARE MICROSAR CAL AUTOSAR Driver for Control of Microcontroller Peripherals Overview of advantages > Optimal support of microcontroller peripherals > Simplified configuration by considering cross-module parameter dependencies in the configurator > Development accelerated by plausibility and completeness tests in the configurator > Resource-saving. MICROSAR MEM. You just add other packages (e. it is not necessary to make changes to the functional software when switching to different hardware. etc. Eep.0): > Ethernet driver (ETHDRV) (ASR 4. The MICROSAR CAL drivers work together optimally with the rest of the MICROSAR packages. MICROSAR CAL modules V2.g.4 2011-06 More Information: www.com/contact . since functionalities can be deactivated > Reduced hardware requirements due to optimal utilization of hardware buffers > Gateway developments are supported by efficient auxiliary functions The MICROSAR CAL package contains the drivers for controlling the microcontroller’s peripherals.x and are available for many commonly used microcontrollers. Some are from AUTOSAR Release 4. Mcu. Fls. Fr. Application Areas MICROSAR CAL gives you a turn-key solution for driving your microcontroller peripherals.
microsar.com/contact > DIODRV: User-configurable locating of the pins within a ChannelGroup > ICUDRV: Notification of timer overrun and in signal measurement mode > MCUDRV: Reset mechanisms are user-configurable for the function Mcu_PerformReset().EMBEDDED SOFTWARE Training In the framework of our training program we can offer various training courses and workshops on MICROSAR at our classrooms or at your business site. If the FlexRay controller detects an error. semiconductor manufacturers. > CANDRV: Extended filter options for multiple basic CAN objects > CANDRV: Rx queue for reducing interrupt execution time while receiving messages Scope of Delivery > Software modules as library with C header files.com Contact and Availability For information on the availability of hardware-specific MICROSAR BSW modules go to: www.vector. > In the framework of project work.vector. The following functionalities are available options: > FRDRV: Bus self-diagnostics. seamlessly and quickly. it sets a status bit that is polled by the FlexRay driver (FRDRV). Configuration of the ADCDRV with DaVinci Configurator Pro More Information: www. Additional Services > Integration of drivers by third-party producers. You will find information on properties of BSW modules from the MICROSAR packages as well as detailed descriptions of functional features of the DaVinci Tools in the particular datasheets. in DaVinci Configurator Pro. e. Vector would be glad to create a low-level MOST driver for your specific hardware to interface it to the Network Services Library. For more information on individual training events and dates please visit: www.g.com/availability/ We would be glad to provide you with information on OEM-specific versions and individual support for your AUTOSAR projects. > FRDRV: The FlexRay configuration can be read out by a diagnostic command. MICROSAR basic software and MICROSAR RTE. This lets the user configure the entire ECU software with a single tool.com/contact . optionally as source code > Command line based generator (for Windows XP/Vista/Windows 7) > BSW module description > DLLs for configuration with GENy > Description files for DaVinci Configurator Pro > Documentation The complete AUTOSAR solution from Vector The AUTOSAR solution from Vector consists of the DaVinci tools.vector-academy. Find your contact person at: www.
So. They have each been optimized for a specific device and are available for many commonly used devices. Functions contained in the drivers were specified by AUTOSAR in the “ECU Abstraction Layer” and they conform to AUTOSAR Release 3. it is not necessary to modify the functional software when switching out external hardware.MICROSAR EXT AUTOSAR drivers for control of external devices 2/34 Overview of Advantages > Optimal control of your external transceiver and memory devices > Additional support for LIN and Ethernet transceivers > Simplified configuration by considering parameter dependencies with other modules > Development accelerated by plausibility and completeness checks in the Configurator MICROSAR EXT contains communication-related AUTOSAR transceiver drivers for CAN (CANTRCV).) for a complete communication stack or memory management per AUTOSAR specification.0) Scope of Delivery > Software modules as library with C header files. you can add other packages (e. flash memory and watchdog (DRVEXT). MICROSAR MEM. Functions The BSW modules in MICROSAR EXT contain functions defined in AUTOSAR Release 3. etc.x plus the following extended functions: > Bus error detection on FlexRay > Active star handling on FlexRay > LIN transceiver drivers > Ethernet transceiver drivers (per AUTOSAR Release 4. MICROSAR CAN. optionally as source code > Command line based generator (for Windows NT/2000/XP/ Vista/Windows 7) > BSW modules description > DLLs for configuration with GENy > Documentation MICROSAR EXT modules . Ethernet (ETHTRCV) and drivers for other external devices such EEPROM. LIN (LINTRCV).g. All you need to do is switch out the relevant drivers from MICROSAR EXT. Application Areas MICROSAR EXT gives you a turn-key solution for driving your external peripheral devices. Depending on the requirements of your application. FlexRay (FRTRCV).x.
Find your contact person at: www.microsar. Additional Services Vector can offer services for integrating the configuration of your drivers or drivers by third-party producers.com/availability/ We would be glad to provide you with information on OEMspecific versions and individual support for your AUTOSAR projects.com/contact # The complete AUTOSAR Solution from Vector The AUTOSAR solution from Vector consists of the DaVinci tools. Other Relevant MICROSAR Products The external devices are physically driven via SPI. DIO or a port. For more information on individual training events and dates please visit: www. such as semi-conductor manufacturers in DaVinci Configurator Pro.AUTOSAR Training In the framework of our training program we can offer various training courses and workshops on MICROSAR at our classrooms or at your business site.vector. You will find information on properties of BSW modules from the MICROSAR packages as well as detailed descriptions of functional features of the DaVinci Tools in separate datasheets. MICROSAR basic software and MICROSAR RTE. This lets you configure the entire ECU software with a single tool.com Contact and Availability For information on the availability of hardware-specific MICROSAR BSW modules go to: www. ◆ 2/35 Configuration of MICROSAR EXT with DaVinci Configurator Pro . DIODRV or PORTDRV) from MICROSAR CAL.vector-academy. seamlessly and quickly. You will need the relevant drivers for this (SPIDRV.
This function already conforms to AUTOSAR Release 4. Configuration MICROSAR IO is configured with DaVinci Configurator Pro. In addition.EMBEDDED SOFTWARE MICROSAR IO AUTOSAR Input-Output Hardware Abstraction Overview of Advantages > Quick implementation of user-specific code for acquiring and providing ECU signals > Generation of complete DIO accesses > Provision of code templates with all necessary interface definitions > Support of “actuator tests” via diagnostics AUTOSAR has defined hardware-independent Set/Get and Diag operations in the “IO Hardware Abstraction” for setting. > Execute functions for the DCM actuator test via the standard interface.vector.3 2011-06 MICROSAR IO modules More Information: www. They let the user condition and filter the signals. In configuring MICROSAR IO. which makes the application software hardware-independent. MICROSAR IO provides all of the necessary Client/Server interfaces and code templates needed to give the functional software access to the I/O signals via the RTE. in which users can directly program their extensions. making it easy to implement application-specific signal processing. DaVinci Configurator Pro can generate code templates. Application Areas MICROSAR IO provides a convenient foundation for developing your “IO Hardware Abstraction”. In addition to functions specified by AUTOSAR. The following “bottom up” approach is recommended: > Configure the CAL driver > Configure MICROSAR IO > Generate SWC description for modeling of MICROSAR IO V2. In combination with the suitable drivers for microcontroller peripherals from MICROSAR CAL.x. Functions BSW modules in MICROSAR IO contain functions defined in AUTOSAR Release 3. reading out and manipulating physical I/O signals (digital or analog) from your ECU’s periphery. The configuration and generation tool checks for plausibility of the configuration parameters for MICROSAR CAL and MICROSAR IO. It interconnects the functional software to physical IO signals of sensors and actuators. you get a complete I/O stack for the ECU software. you can use MICROSAR IO to: > Define user defined ports for acquiring ECU-specific user defined signals. > Process user defined signals from the user defined ports. Upon request. Vector offers them in the MICROSAR IO package. No special extension to the MICROSAR IO code is needed for direct access to DIO signals. you define each individual signal as either a user defined signal or a DIO port signal.com/contact . you can use MICROSAR IO to create your own signal definitions.0.
the Vector design and configuration tool ensures that ECU signals defined in MICROSAR IO are integrated in the overall data flow of the ECU software. which could be created with DaVinci Developer.com/availability/ We would be glad to provide you with information on OEM-specific versions and individual support for your AUTOSAR projects. Scope of Delivery > Software modules as library with C header files. Additional Services Vector would be glad to support you in the development of the “IO Hardware Abstraction Layer” of your special ECU in the framework of project work.com/contact This SWC description later flows into modeling of the entire ECU software. for example. For more information on individual training events and dates please visit: www.com/contact . Here.vector.vector-academy.microsar. your I/O Stack will need an additional suitable driver from MICROSAR EXT. This modeling is the foundation for later generation of the RTE. You will find information on properties of BSW modules from the MICROSAR packages as well as detailed descriptions of functional features of the DaVinci Tools in separate datasheets. Find your contact person at: www.com Contact and Availability For information on the availability of hardware-specific MICROSAR BSW modules go to: www.EMBEDDED SOFTWARE Training In the framework of our training program we can offer you various training courses and workshops on MICROSAR at our classrooms or at your business site. optionally as source code > Command line based generator (for Windows XP/Vista/Windows 7) > BSW modules description > Description files for DaVinci Configurator Pro > Documentation The complete AUTOSAR Solution from Vector The AUTOSAR solution from Vector consists of the DaVinci tools. You benefit from Vector‘s detailed knowledge of the AUTOSAR specification and methodology as well as its extensive experience in integration of ECU software. MICROSAR basic software and MICROSAR RTE. Konfiguration des Moduls IO mit DaVinci Configurator Pro More Information: www.vector. Other Relevant MICROSAR Products If I/O signals are accessed via an external device.
MICROSAR RTE The optimized Run-time Environment for Software Components per the AUTOSAR Standard 2/38 Overview of Advantages > Easy to configure and scalable > In-depth consistency check of the configuration > Highly optimized code with intelligent synchronization mechanisms > Quick entry into working with AUTOSAR. InterRunnable variables and Per-Instance memory MICROSAR RTE (Run Time Environment) is the scalable and highly optimized AUTOSAR runtime environment from Vector. based on generated code templates for the software components (SWCs) > Well-suited for migration projects > Simplified testing of the application by XCP access to S/R ports. CDD and BSW modules together form the overall AUTOSAR ECU software. The RTE is a module introduced by AUTOSAR that manages communication between the software components (SWCs). The RTE only needs to be reconfigured and regenerated for the specific ECU and. It assures consistency of the overall information flow and represents the interface between the functional software. the user needs the RTE as a runtime environment. > RTE generation for the entire ECU software. It is optimized for the entire ECU configuration and makes few demands on system resources due to short execution times and minimal interrupt disable times. basic software (BSW) and complex device drivers (CDD). In generating the MICROSAR RTE. It is also possible to use a SWC in multiple instances on one ECU. the user can choose between two modes: > Contract Phase Generation for developing individual SWCs in an early phase.x: > Sender/Receiver and Client/Server communication > Mode management > InterRunnable variables as well as Exclusive Areas > Trigger for runnables MICROSAR RTE module . This modular layout of the ECU software offers the user maximum flexibility: SWCs that have been manually devel- oped or designed by model-based tools can be re-used in multiple ECU projects. Functions The MICROSAR RTE contains functions defined in AUTOSAR Releases 3. One way this is achieved is by using intelligent synchronization mechanisms that are tuned to the properties of the hardware used. to transfer them to a development partner as object code. if applicable. RTE. e. In this case. Application Areas When the functional software of an ECU is implemented by AUTOSAR-conformant SWCs. the BSW modules. e. The SWCs.g. This makes it possible to compile the SWCs individually. The code generated in this mode is highly efficient and requires only little memory space.g. the generator just creates a header file for each SWC instead of the entire RTE.
MICROSAR basic software and MICROSAR RTE.com/availability/ We would be glad to provide you with information on OEMspecific versions and individual support for your AUTOSAR projects. The subsequent generation of the RTE is performed directly from DaVinci Developer or with a separate generator.com/contact > Online and offline calibration of SWCs are supported as well as measurement of S/R ports. As an extension to the AUTOSAR method.microsar. 2/39 Other Relevant MICROSAR Products: The RTE requires the presence of an operating system such as MICROSAR OS or osCAN. > Configuration of initialization runnables for the AUTOSAR concept of “Mode-Dependent Runnables” > Generation of an A2L file for simple linkage to existing calibration and diagnostic standards > Generation of an HTML report showing RTE properties.vector. Scope of Delivery > Command line based generator (for Windows NT/2000/XP/ Vista/Windows 7) > BSW modules description > Documentation The complete AUTOSAR Solution from Vector The AUTOSAR solution from Vector consists of the DaVinci tools. InterRunnable variables and Per-Instance memory using the XCP protocol.com Contact and Availability For information on the availability of hardware-specific MICROSAR BSW modules go to: www. > Use of memory protection mechanisms as specified in the AUTOSAR operating system. It contains information such as the calculated RTE resource load (RAM + constants). The following AUTOSAR 3. it contains validation rules that ensure the consistency of the RTE’s configuration parameters. the MICROSAR RTE offers: > Generation of code templates for SWCs based on the XML file “SWC Description“. For more information on individual training events and dates please visit: www. You will find information on properties of BSW modules from the MICROSAR packages as well as details on functional features of the DaVinci Tools in separate datasheets. > Multiple instancing of SWCs and per-instance memory Moreover. These templates contain all APIs of the RTE. Find your contact person at: www.AUTOSAR Training In the framework of our training program we can offer various training courses and workshops on MICROSAR at our classrooms or at your business site.x functions are optionally available: > External Client/Server communication (Inter-ECU) > Full support for measurement and calibration > Rx data filter for functional software Configuration You can configure the MICROSAR RTE with DaVinci Developer. This support is especially optimized when MICROSAR OS is used. Users fill these templates with their own application code. Automated generation of the RTE using the command line method is also possible. ◆ MICROSAR RTE enables generation of code templates for the SWCs .vector-academy.
2 2011-10 MICROSAR Safe More Information: www. They were implemented according to the AUTOSAR specification and are compatible with the remaining MICROSAR modules: SafeExecution: > Runtime monitoring of tasks > Flow control of safety-relevant SWCs > Memory protection and safe context switching SafeCom: > Safe intra-ECU and inter-ECU communication SafeSelfTest: > Periodic hardware checking The use of Runtime Monitoring. WDGIF and WDGDRV from SafeExecution. The modules from MICROSAR Safe are SEooCs (Safety Elements out of Context). This solution is the result of collaborative work with TTTech. Their use helps you to drastically reduce effort for qualifying your safety-relevant functions. Functions The SafeCom. V2. our partner with many years of experience in the field of functional safety. SafeExecution and SafeSelfTest bundles from MICROSAR Safe contain the following specific functionalities. It lets you develop AUTOSAR-based applications using software components (SWCs) for ECUs up to ASIL D per ISO DIS 26262.vector.EMBEDDED SOFTWARE MICROSAR Safe Safety according to ISO DIS 26262 for ECUs with AUTOSAR software Overview of advantages > Solution for all Automotive Safety Integrity Levels (ASIL) through ASIL D > Savings in qualification costs > Support of different ASILs on one controller Application areas For using MICROSAR basic software in ECUs with safety-relevant functions. Runtime Monitoring Runtime monitoring assures that tasks have sufficient computing time for their execution.com/contact . Runtime monitoring is provided by MICROSAR OS SC2/SC4 and is validated to ISO DIS 26262 by the modules WDGM. Flow Control. Memory Protection and Safe Context Switching makes it possible to let safety-relevant and non-safety relevant SWCs run next to one another on the same ECU without interference. which are developed according to ISO DIS 26262 / ASIL D. This means that software parts whose correct execution cannot be verified cannot disturb safety-relevant functions unnoticed. you will receive MICROSAR Safe from Vector.
This involves using what are referred to as checkpoints in the software components. which was developed to ASIL D. A checksum protects the data contents and the correct sequence of data is monitored by a message counter. Hardware checking You can perform cyclic tests for error-free functionality of the ECU’s various hardware components during operation using generic test functions of the SafeSelfTest package.g. and it can react accordingly. SafeContext prevents unauthorized writing by one software component to the memory of another software component that could corrupt the data. WDGIF and WDGDRV. The option SafeContext is available for MICROSAR OS (SC3/SC4) and it is used to separate the various software components from one another during task changes and interrupts. The SEooCs conform to ISO 26262 ASIL D and are developed according to the AUTOSAR specification. optionally as source code > Instruction line based generator (for Windows XP/Vista/ Windows 7) > BSW module description files > Description files for DaVinci Configurator Pro > Documentation with Safety Manual Implementation Safety-relevant functions are implemented by the Safety Elements out of Context (SEooC) from MICROSAR Safe. MICROSAR Safe contains the following SEooCs: SafeCom: > E2ELIB: End-to-end library > Protection Wrapper: End-to-end protection Wrapper SafeExecution: > SafeContext: Memory Protection and Safe Context Switching (option for MICROSAR OS) > WDGM: Watchdog Manager > WDGIF: Watchdog Interface > WDGDRV: Driver for internal watchdog devices > WDGEXT: Driver for external watchdog devices SafeSelfTest: > RAMTST: Tests for RAM memory > FLASHTST: Tests for flash memory > CORETST: Tests for the microcontroller core > IOTST: Tests for inputs and outputs More Information: www. Contact and Availability You will find information on the availability of hardware-specific MICROSAR BSW modules at: www.vector.com/availability/ We would be glad to provide you with information on OEM-specific variants as well as individual support for your AUTOSAR projects. RTE for safety-relevant functions The MICROSAR RTE supports partitioning of memory areas via the operating system option SafeContext. MICROSAR basic software and MICROSAR RTE.vector. Safe Intra-ECU and Inter-ECU communication Data that is exchanged between safety-relevant applications must be checked for correct transmission. You will find information on the properties of the BSW modules and a detailed description of the functional features of the individual DaVinci Tools in individual datasheets. The precise scope of monitoring that is necessary is project-specific.com/contact . assures memory protection for ECUs with safety-relevant applications on suitable microprocessors (e. This detects errors such as masquerading. with MPU.microsar. If one of these checks fails. Configuration The safety elements of MICROSAR Safe are configured with the DaVinci tools. the application is informed. failure or reversed data. the Memory Protection Unit). This enables a “Decomposition” in the sense of ISO DIS 26262. Product components > Software modules as library with C header files. Memory Protection and Safe Context Switching The MICROSAR operating system’s option SafeContext. They detect and handle potential errors in non-safety software layers. We would be glad to consult with you in selecting specific monitoring mechanisms for your project. Find your contact person at: www.EMBEDDED SOFTWARE The complete AUTOSAR solution from Vector The AUTOSAR solution from Vector consists of the DaVinci tools.com/contact Program Flow Monitoring Correct execution of safety-relevant SWCs is assured by the modules WDGM.
x. they may exhibit a completely different signal layout or support a different number of buses. the ECU Extracts upon which the configuration of the AUTOSAR ECU software is based may differ very significantly for the different variants. Multiple Configuration With the multiple configuration. This reduces hardware costs and effort in inventory management. No differentiation is necessary in the code. and therefore in completely different communication networks. The application accesses signals and data elements independent of its identity. On the other hand. Identity An ECU is identified by its Identity. it is possible to use an ECU in different car lines. an Identity is really the configuration of an ECU that is active at runtime and is based on a description file. Physical Multiple ECU and multiple configuration . Door ECUs are a typical example of this. Physical Multiple ECU One speaks of Physical Multiple ECUs. it results in increased effort in software development and the management of software variants for production and service areas. Vector is familiar with typical applications for ECU variants and can provide practice-oriented solutions for multiple ECUs based on AUTOSAR Release 3. The Identity establishes which variant of the ECU should be activated (e. when multiple ECUs in a vehicle perform nearly identical functions at different locations.g. The Identity is set when the ECU is initialized. In this case. Via the so-called Identity (see box). a single ECU is developed and produced. Based on its many years of cooperation with automotive OEMs and suppliers. A typical application here would be for what are known as carry-over ECUs. which door side). Here too.Identity Manager for AUTOSAR Solution for Multiple ECUs Overview of Advantages > Efficient handling of ECU variants > Less administration effort > Reduced inventory costs 2/42 In the modern automobile. In this case. there is an increase in the number of ECUs that can be installed in different variants. Your advantage is the use of a single hardware for the different application areas. each ECU knows during startup which one it is and where it is installed. and therefore also which functions it needs to fulfill. So. they are known as multiple ECUs. These ECUs contain the software for all of the car lines in which they are used. the identity of the ECU is determined when it is started. The buffer for the Rx and Tx PDUs can be completly overlaid if their layout is identical. The individual ECUs only differ in their Rx and Tx PDUs or in their diagnostics and address in the network.
Diagnostics To describe the diagnostics of an ECU.microsar. MICROSAR Basic Software and the MICROSAR RTE.com/availability We can also tell you about OEM-specific versions and customer support for your AUTOSAR projects. for optimization no separate set of configuration parameters is created for some BSW modules but only a common set is created for all instances. Both files contain a superset of the relevant ECU-specific information. diagnostic services. etc. The RTE implements this by the so-called fan-in or fan-out mechanism. In these two tools. To describe two or more ECU variants. identical diagnostic services are overlaid. the user finds a superset of the ECU interfaces to be implemented and configures the multiple ECU like a normal ECU. PDUs may be overlaid if only a few signals are identical in the PDUs. For the RTE. Proven Configuration Process The configuration tools DaVinci Developer and GENy read in the merged files (ECU Extract and ECUC). You will find information on properties of BSW modules from the MICROSAR package and detailed descriptions of functional features of individual DaVinci Tools in the relevant datasheets. only one hardware component is needed. two or more ECU Extracts are needed. This applies to such elements as identical messages. Although the ECU must be large enough to offer space for both applications. Exactly as in communication. Integrating both Solutions in the AUTOSAR Concept According to AUTOSAR. The Project Assistant that is contained in the tools supports the user here. The user configures the optimal superset of all diagnostic services as usual in GENy. one diagnostic description file (CDD) is needed per ECU. In multiple configurations.AUTOSAR The complete AUTOSAR solution from Vector The AUTOSAR solution from Vector consists of the DaVinci tools. Afterwards.com/contact For both solutions. these files are merged into one file with DaVinci Developer. Scope of Delivery The scope of delivery of the Identity Manager includes: > License for enabling in the configuration tool > BSW modules with Identity Manager functionality 2/43 ◆ Configuration process of multiple ECUs . ECU resource savings are realized. Find your contact person at: www. an ECU is described by an ECU Extract of System Description. Saving Resources Since Physical Multiple ECUs are identical in much of their content. and so they exist just once. DaVinci Developer generates a higher-order ECU Configuration Description (ECUC) for the basic software.vector. Contact and Availability You will find information on the availability of hardwarespecific MICROSAR BSW modules at: www.
Metrowerks. Wind River X X X X X X X X X X  X X X IAR X X X ARM X GNU.vector. Metrowerks. Metrowerks Green Hills. dsPic33F NXP LPC1768 V2. Green Hills Green Hills X X X X X X X X X X X X GNU.EMBEDDED SOFTWARE Wide Availability of MICROSAR Supported Microcontrollers and Compilers for the hardware-specific AUTOSAR BSW Modules Controller Compiler MICROSAR OS  MICROSAR CAL [2. Tasking X MPC56xx (QORIVVA/ 5xxx/Automotive) Fujitsu 16FX FCR4 FR60 FR81 MB86 MB9E/DF126 (Cortex-R4) Infineon TriCore XC2000 Microchip PIC24 dsPIC33E. Wind River Green Hills.MX25. IAR Cosmic. 3] CAN FlexRay LIN IP/Ethernet Further MCAL Driver Altera NIOS II ARM Cortex M Atmel AVR32 Freescale i. Tasking Tasking VX X X X X X X X X Microchip Microchip X X X Keil X More Information: www. i. Green Hills.4 2011-10 X X X X X X Fujitsu Green Hills Fujitsu Fujitsu GNU.com/contact .MX35 MAC7100 S12X MPC55xx GNU ARM.
Please collect this information as early as possible. 3.1 or 4.1. 3] CAN FlexRay LIN IP/Ethernet Further MCAL Driver Renesas Electronics (NEC/Renesas) 78K0R V85x M32C M32R R32C R8C SH2 STMicroelectronics SPC56xx Green Hills. Green Hills X X X X X X X X X X X X X X X X X X X X STR9 Texas Instruments TMS320 TMS470 TMS570 Vector CANoe osCAN Emulation X Texas Instruments Texas Instruments Texas Instruments X X X X X X X X Microsoft VisualC X X X X X X  = As alternative to MICROSAR OS you can use an osCAN operating system in AUTOSAR systems.0.0. IAR IAR Renesas. Only the modules listed in the table below must be tailored for each hardware platform.  = Some of the MCAL drivers are created by hardware manufacturers and correspond partly to AUTOSAR release 2. Please send a request to Vector for the combination of derivative and compiler you require. IAR.com/contact Controller Compiler MICROSAR OS  MICROSAR CAL [2.EMBEDDED SOFTWARE Availability and Contact The MICROSAR software modules are hardware independent to a large extent. so that Vector can supply your software for the project start. 3. Metrowerks. Wind River GNU X X X X X X IAR Green Hills.  = Currently in development More Information: www.com/contact .vector.vector.  = On request Vector can develop further MCAL drivers or merge the configuration of your MCAL drivers into the configuration tool DaVinci Configurator Pro. IAR Renesas Renesas. Renesas Renesas. Find your contact person at: www.
g. and they facilitate smooth integration of the functional software with the ECU‘s basic software. LDF) > Data mapping of port data to network signals > Consistency check of the SWC definition and the RTE configuration > Interface to model-based development tools via AUTOSAR-SWC description files DaVinci Developer – Design tool for AUTOSAR-conformant ECUs . DaVinci Developer lets you consistently configure the MICROSAR RTE based on previously defined AUTOSAR SWCs. FIBEX. Application Areas DaVinci Developer supports ECU developers in developing AUTOSAR-conformant ECUs. Finally. Convenient graphical editors let you design the structure and interfaces of the functional software for your ECU quickly and clearly. This means that DaVinci Developer is a flexible tool that can be used in different OEM projects. DaVinci Developer is also well-suited as an integration tool you can use to consistently integrate existing AUTOSAR SWCs in an ECU. e. You can use DaVinci Developer as an architecture tool to define application software architectures. calibration and service components > Import and export of AUTOSAR XML formats (System Description Template.DaVinci Developer Designing AUTOSAR Software Components and Configuring the MICROSAR RTE 2/44 Overview of advantages > Convenient graphical definition of software components > Clear representation of complex systems > Special functions simplify data exchange between OEM and ECU developer > Easy connection to configuration management tools > Consistent configuration of the MICROSAR RTE DaVinci Developer is the professional tool for designing AUTOSAR software components (SWCs) and for configuring the MICROSAR RTE. > Signal import from commonly used network description formats (DBC. initial values and timeouts > Definition of runnable entities with activation events and port access > Support for all types of AUTOSAR SWCs and application components. compositions. Software Component Template) > Support for various AUTOSAR XML versions in parallel. Functions DaVinci Developer offers extensive functions for defining and integrating AUTOSAR SWCs: > Graphical definition of SWCs with extensive layout functions > Definition of port interfaces and data types > Definition of port prototypes with service needs and communication specification.
vector-academy. the service components and IO hardware abstraction components generated by DaVinci Configurator Pro can be conveniently imported and linked to the application SWCs. the RTE configuration is saved AUTOSAR-conformantly in an ECU configuration file. Scope of Delivery > DaVinci Developer > Utility tools for automating work steps > Demo data > Documentation System Requirements Component Processor Memory (RAM) Screen resolution Operating system Recommended Pentium 4/2. it supports work steps such as: > Assigning runnable entities to operating system tasks. e. Finally. > Library concept for reusing components or interfaces in multiple ECU projects > Connection to configuration management systems with finegranulation versioning of individual objects. Training Events In the framework of our training program.or 64-Bit) ◆ Special functions > Configuration of multipurpose ECUs > Project assistant for conveniently creating and updating ECU projects > User-specific extension of the data model by generic attributes . DaVinci Developer offers special support by automatically creating suitable service port prototypes and server runnables for the application SWCs. For more information on individual training events and the schedule on the Internet go to: www. we offer various AUTOSAR training courses and workshops at our classrooms. This work is simplified by special views on the runnable entities. the tool offers extensive functionality for data exchange between OEM and ECU developer: > Import/Update function to support an iterative development process > Diff and Merge functions with configurable presettings for individual objects. SWCs Configuration of the MICROSAR RTE DaVinci Developer is used to configure the MICROSAR RTE. For example. Separate datasheets describe general properties of the BSW modules from the MICROSAR packets and detailed functional features of the individual DaVinci Tools. For this purpose. such as the trigger-oriented or component-oriented view. > Configuring optimization options > Consistency checking of the RTE configuration with detailed error reports and tips on correcting inconsistencies DaVinci Developer works seamlessly with DaVinci Configurator Pro to create a consistent overall configuration.AUTOSAR The complete AUTOSAR solution from Vector Vector‘s DaVinci and MICROSAR products offer a fully tuned solution for developing AUTOSAR ECUs. as online Webinars or at your company site.g.com Workflows and AUTOSAR Methods DaVinci Developer can be flexibly used in a distributed development process based on the AUTOSAR method. This makes it possible to extend OEM-generated SWCs by adding port prototypes and runnable entities.6 GHz 2 GB 1280 x 1024 Minimum Pentium III/1 GHz 1 GB 1024 x 768 2/45 Windows XP SP2 or SP3 Windows 7 (32.
DaVinci Component Tester is a universal run-time platform for testing SWCs in all development phases of ECU applications. V2. The original source code is executed directly.g. > Integration tests of software components DaVinci Component Tester supports integrating complex systems consisting of multiple SWCs.0 and 3. Also.TOOLS FOR NETWORKS AND DISTRIBUTED SYSTEMS DaVinci Component Tester 1. By integrating DaVinci Component Tester in the development environment. Together with a unit test tool such as NUnit. in conjunction with a development and test tool such as CANoe you can control the SWCs interactively. When used together with a test tool like CANoe.4 2011-07 Testing atomic AUTOSAR software components with DaVinci Component Tester Testing a composition of multiple software components with DaVinci Component Tester More Information: www.1 > Quick setup of tests without time-consuming configuration > Simplified test cases by emulating AUTOSAR Standard Services > Interfaces to standard test tools: CANoe from Vector and NUnit > Interfaces to development environments such as Microsoft Developer Studio or Eclipse via open interfaces Thanks to AUTOSAR. An example is automated regression tests. e. > Unit Test of software components Use DaVinci Component Tester for testing the functionality and AUTOSAR-conformity of your SWCs. e. It is very easy to configure the DaVinci Component Tester. Application Areas DaVinci Component Tester supports the following application areas: > Rapid Prototyping While developing ECU applications. and analyze their behavior. by using just the SWC description file without modification of the SWCs. this will increase the quality of your SWCs by testing during development. DaVinci Component Tester is a high-performance VFB emulator that enables execution and testing of such SWCs on a PC. you can execute and debug the SWCs right on your development PC.0 Testing AUTOSAR Application Software on the PC Overview of advantages > User-friendly testing of AUTOSAR software components (SWC) on a PC > Wide variety of use cases.g.vector.com/contact . state machines or control systems > Testing of SWCs developed manually or by model-based methods > Unlimited support of all SWC interfaces per AUTOSAR Release 3. this lets you verify system functionality early on. from tests supporting the ECU developer to acceptance tests at the automotive OEM > Suitable for all application SWCs. an ECU’s application software can be developed as hardware-independent software components (SWCs) based on a Virtual Functional Bus (VFB). you can use the DaVinci Component Tester as a convenient run-time platform for SWCs. via user interfaces.
They affect execution of the SWC’s runnable entities: > Programmed execution mode You can implement execution of the runnable entities in an explicit test case. periodically every 10 ms. The external test tool handles control of the test. The finely tuned emulator simulates the AUTOSAR-ECU environment for the SWC under test with realistic behavior. e. Based on the SWC Description. Therefore DaVinci Component Tester synchronizes itself to the time base of your test tool.0 and 3. by programming test cases. DaVinci Component Tester provides a structured API that can be used by an external tool to access the SWC. This execution mode is used for integration testing of complex SWCs or in experimental startup of a SWC during development (Rapid Prototyping).1 SWCs using functions such as: > Setting data elements of receiver ports > Reading data elements from sender ports > Calling up server ports > Controlling mode ports > Setting calibration data > Executing runnables with non-blocking API calls (Category I) > Executing runnables with blocking API accesses (Category II) > Handling internal communication between multiple SWCs > Simulating errors such as timeout or empty queue All you need to configure the test setup or experiments is the SWC description (AUTOSAR XML file).TOOLS FOR NETWORKS AND DISTRIBUTED SYSTEMS Functions The core of DaVinci Component Tester is an emulator that executes the SWCs on a PC. Operating Modes DaVinci Component Tester offers two operating modes.g.com/contact .g. This does not require an AUTOSAR RTE (Runtime Environment) or basic software. which depend on its intended use. The emulation covers full RTE functionality and lets you test any AUTOSAR Release 3.vector. e. > Automatic execution mode DaVinci Component Tester executes the runnable entities independently according to the trigger specification. More Information: www. This execution mode is used in unit tests with focus on detailed inspection of the implementation. and evaluation of the test.
Similarly. such as panels. DaVinci Component Tester automatically handles execution of the runnable entities. This reduces the complexity of the test environments considerably. You describe the test environment in CANoe. The service emulator supports AUTOSAR standard services of the following basic software modules: > > > > > > EcuM (ECU Manager) DEM (Diagnostic Event Manager) FiM (Function Inhibition Manager) NvM (Non-Volatile Memory Manager) ComM (Communication Manager) WdgM (Watchdog Manager) Interface to CANoe You can use DaVinci Component Tester in combination with CANoe to execute integration tests of SWCs. There is no need to explicitly consider the service ports in the test environment. The service emulator may be accessed at any time.TOOLS FOR NETWORKS AND DISTRIBUTED SYSTEMS Special functions > Instruction line support for automated tests > Checking API consistency of the SWC Description and SWC implementation file > Programming callbacks in the test environment for specific reaction to an API call of the SWC under test > Generating the header file of SWCs (Contract Phase Generator) for compiling the SWC implementation with the Microsoft Compiler Service Emulator DaVinci Component Tester contains an emulator for the standard services of an AUTOSAR ECU. or you can check the value changed by the SWC. For example. analysis windows and integration of MATLAB models for an environment simulation. This emulator simulates the behavior of the services in an abstracted form.g. All other CANoe functions are available as well. While CANoe controls the test flow. allowing you to focus entirely on the SWC’s application ports. Functional principle: Interfacing DaVinci Component Tester to CANoe More Information: www. users can control or monitor the current state of the ECU Manager from a test case. the SWC’s service ports are automatically connected to the service emulator. you can preset a block with a certain value that is read out by the SWC from nonvolatile memory. When a test or experiment is set up.vector.com/contact . Therefore DaVinci Component Tester synchronizes itself to the simulation time of CANoe. with the help of the Test Feature Set. e.
The Professional Edition is required for debugging in combination with NUnit.1 or higher > Alternative: NUnit 2.NET Assembly with a structured API for access to the SWC. DaVinci Component Tester can be integrated in your development environment or test tool chain. The test cases typically show the following pattern: Set input vector. For example. Sample projects Manual as PDF document System Requirements > MS Visual Studio 2005 or 2008 (Express.com/contact . > Windows XP or Windows 7 (32. In implementing the test cases. read output vector and check it. Inputs are the SCW imple- > > > > > > mentation compiled by the Microsoft Compiler and the SWC Description (AUTOSAR XML). Vector offers support in integration of DaVinci Component Tester. making it AUTOSAR-capable. Contract Phase Generator: Instruction line tool for generating the SWC’s header file Emulator (including Service Emulator): . Interfacing is via a . a user could easily program access to a receiver port by listing all of the SWC’s receiver ports and selecting the desired port from the list.nunit. Interfacing is via a .NET Node. Microsoft Visual Studio is used to program the test cases. This is done by implementing the test cases in any desired .NET DLL for executing SUT executables NUnit Adapter: Interfaces the emulator to NUnit. Standard or Professional Edition).or 64-Bit) > CANoe 7.4.7 or higher (available at: http://www.vector. execute runnables.org) Functional principle: Interfacing DaVinci Component Tester to NUnit More Information: www. CANoe Adapter: Interfaces the emulator to CANoe.NET language such as C#. Integration in your test environment Due to its open interfaces. The SWC’s input and output data elements are mapped via CANoe system variables. you are supported by programming assistance integrated in the development environment (IntelliSense). Scope of Delivery DaVinci Component Tester consists of the following components: > SUT Executable Generator: Instruction line tool for preparing the SCW under test as an executable system under test (SUT). which you integrate in your CANoe configuration. NUnit handles test execution and reporting.TOOLS FOR NETWORKS AND DISTRIBUTED SYSTEMS Interface to NUnit You can execute unit tests of SWCs in conjunction with the open source tool NUnit.
1).DaVinci Configurator Pro Configuration of AUTOSAR Basic Software Vector’s DaVinci Configurator Pro is the professional tool for configuring the Basic Software (BSW) modules of an AUTOSAR ECU according to the AUTOSAR standard. available as a separate product. FIBEX. Using the DaVinci description files you can: > Edit configuration parameters over a user-oriented interface. DaVinci Configurator Pro offers the Generic Configuration Editor (GCE) mode for modules. Functions DaVinci Configurator Pro offers users two different configuration modes: Comfort Mode and GCE Mode. DaVinci Configurator Pro is also characterized by the following properties: > Support of all available AUTOSAR releases (2. It is a practical. also in mixed forms within a project > Project-oriented working mode by simple activation or deactivation of individual BSW modules 2/50 > Support of commonly used network description formats (DBC. its multi-stage and rule-based validation process assures consistency of all configuration parameters between modules. third party producers (e.1. MCALs from semiconductor manufacturers) and user-developed BSW modules.0 and 3. The DaVinci Configurator Kit from Vector. e. For user-friendly configuration of the BSW modules. In addition.g. This makes it an ideal central configuration tool. The Comfort Mode supports you extensively in configuring the BSW modules. to show complex configuration relationships in simplified form > Validate parameters across modules > Define the value range of input values > Display configurations in GCE or Comfort Mode > Show the syntax of internal module APIs and callouts > Display implementation-specific help texts Configuring BSW modules with DaVinci Configurator Pro . intuitive and user-friendly implementation of the AUTOSAR method. Properties and Advantages DaVinci Configurator Pro was created as an open tool for configuring and generating BSW modules. validating and generating BSW modules from Vector (MICROSAR). DaVinci Configurator Pro uses so-called DaVinci description files which are included in the scope of delivery of Vector AUTOSAR BSW modules (MICROSAR). 3.g. makes it easy to create these DaVinci description files on your own. if only an AUTOSAR “BSWMD” file exists. LDF) and/or the AUTOSAR “ECU Extract of System Description” > Flexible generation options for optimal integration in existing development processes > Project assistant for easily creating and updating ECU projects Application Areas DaVinci Configurator Pro supports users in configuring. As an alternative.
CAN. FR. GENy offers a userfriendly interface specifically optimized for these configuration parameters. MOST and IP packets as well as diagnostic modules from DIAG. validating and generating AUTOSAR BSW modules.AUTOSAR Useful auxiliary tools included in the scope of delivery: > DaVinci Initial ECUC Generator for the initial generation of an “ECU Configuration Description” (ECUC) file from an “ECU Extract of System Description” > DaVinci ECUC Updater for updating an existing ECUC file after a change has been made to the “ECU Extract of System Description” > DaVinci Difference Analyzer for comparing AUTOSAR files Services Vector can support you with standard software for your projects. Beyond the functional features defined in AUTOSAR. DaVinci ECUC Updater. and it can be directly opened from within DaVinci Configurator Pro. as well as with customized services such as a hotline. COM. . For more information go to www. special workshops and training on the topic of embedded software and AUTOSAR. special workshops and training events on the topic of embedded software and AUTOSAR ◆ DaVinci Configurator Pro supports you in conveniently configuring.com or contact us directly. LIN. DaVinci ECUC Difference Analyser 2/51 System Requirements Component Processor Memory (RAM) Screen resolution Operating system Recommended Pentium 4/2.microsar. the GCE Mode of DaVinci Configurator Pro offers the following supplemental functions: > Clearly organized display of all software modules based on the AUTOSAR architecture > Copying of configurations of individual BSW modules from other projects > Efficient searching and modification of AUTOSAR containers.6 GHz 2 GB 1280 x 1024 Minimum Pentium III/1 GHz 1 GB 1024 x 768 Windows XP SP2 or SP3 Windows 7 (32.or 64-Bit) Additional Services > Creating DaVinci description files for convenient and userdefinable configuration. parameters and references over the entire project > Easy integration of external code generators > Flexible definition of target directories > Add module-specific documents for quick access > Logging of configuration settings and listing of important alerts The GENy tool is included in the scope of delivery and is used for time-saving configuration of communication-related MICROSAR BSW modules from the SYS. Scope of Delivery > Windows-based configurators: DaVinci Configurator Pro and GENy > DaVinci Initial ECUC Generator. validation and generation of any desired modules with DaVinci Configurator Pro > Hotline.
Application Areas The DaVinci Configurator Kit supports developers of AUTOSAR basic software modules. Conformance to the AUTOSAR standard is assured by Vector’s many years of experience with AUTOSAR. With just minimal effort it is possible to configure and integrate complex device drivers in an existing AUTOSAR SW architecture. so that you can configure and generate – in a time-saving and user friendly way – your own inhouse embedded software modules. This lets you concentrate fully on the development of your embedded software module. For user-created software modules. As a supplement to the AUTOSAR method. Each module is configured to the needs of an individual ECU. the DaVinci configuration tools from Vector also offer a validation feature. validation rules and generation processes for DaVinci Configurator Pro > Define range and default values for configuration parameters > Conveniently define your own configuration parameters > Describe dependencies between different configuration parameters – within a module or across modules > Create your own code generators > Easily define individual project reports that document the parameter configuration in DaVinci Configurator Pro > Extend the DaVinci Configurator Pro functionality by integrating your own C++ based DLLs > Protect your own know-how by encrypting DaVinci description files DaVinci Configurator Kit supports you in integrating your software module in DaVinci Configurator Pro . and you will not need any additional configuration tool. Before code generation it ensures that individually configured parameters as well as complex parameter groups are consistent with one another. validation rules and generators without requiring knowledge of tool programming. You can extend DaVinci Configurator Pro (see separate datasheet) with the DaVinci Configurator Kit. 50 configurable standard Basic Software (BSW) modules. Functions: The Vector DaVinci Configurator Kit lets you: > Generate the AUTOSAR-conformant “BSW Module Description” > Conveniently create configuration interfaces. you can also use the DaVinci Configurator Kit to define the validation rules. complex device drivers and user-developed software modules. DaVinci Configurator Pro is the AUTOSAR configuration tool from Vector that is used to configure all BSW modules. Properties and Advantages The DaVinci Configurator Kit supports the embedded module developer in designing individual configuration interfaces for user-developed software modules and creating flexible code generators. You can also use the DaVinci Configurator Kit to extend any desired software module to prepare it for integration in an AUTOSAR ECU. Developers benefit from the simplified process of creating configuration interfaces.DaVinci Configurator Kit Creating configuration interfaces and generators for user-developed software modules 2/52 The AUTOSAR architecture currently defines approx.
such as MCAL drivers or IO hardware abstraction > Completely creating complex device drivers > Extensions of AUTOSAR standard BSW modules > Developing customer-specific AUTOSAR software components (SWCs) > Working out individual strategies for migration of your existing systems to AUTOSAR > Hotline.com or contact us directly. Clix and Erule > Elic to incorporate user-developed modules in existing DaVinci Configurator Pro licenses Scope of Delivery > DaVinci Configurator Pro (developer license) > Tools for generating the DaVinci description files > Extensive technical documentation of interfaces.microsar. System Requirements The following development tools are included with the DaVinci Configurator Kit: > Eparm to define and pre-configure individual parameters for a module > Clix to flexibly lay out user interfaces for displaying and editing the module configuration in DaVinci Configurator Pro > Erule to create complex rules for data checking and file generation > Cryps to encrypt DaVinci description files created with Eparm.or 64-Bit) 2/53 Additional Services > Designing convenient configuration interfaces and supplemental validation rules for software modules of third party producers. special workshops and training on the topic of embedded software and AUTOSAR.AUTOSAR Services Vector can support you with standard software for your projects.6 GHz 2 GB 1280 x 1024 Minimum Pentium III/1 GHz 1 GB 1024 x 768 Windows XP SP2 or SP3 Windows 7 (32. . special workshops and training events on the topic of embedded software and AUTOSAR ◆ Defining a module’s configuration parameters with the Eparm tool from the DaVinci Configurator Kit. For more information go to www. as well as with customized services such as a hotline. as well as numerous application examples > Command line based code generator > 3 days of training > 20 hours of hotline support Component Processor Memory (RAM) Screen resolution Operating system Recommended Pentium 4/2.
First. In particular. Afterwards. we conduct an integration and configuration review related to the concrete useage of the MICROSAR stack. hotline support is available to you by telephone or email. OEM-specific aspects are also considered. We would also be glad to conduct these training courses at your business site. we jointly carry out a customized action package for you. MICROSAR Installation and Support You have already gained familiarity with the topic of AUTOSAR and are now using the AUTOSAR Embedded Software (MICROSAR) from Vector in a specific project. we evaluate the completeness. in which you realize sustained benefits from our AUTOSAR competence.AUTOSAR Services Proficient support for your AUTOSAR projects Overview of advantages > Builds up knowledge efficiently and effectively > Tailored support > Quick implementation of your application 2/54 With our AUTOSAR Software Engineering Services. AUTOSAR Training Vector AUTOSAR training courses provide you with an ideal entry into ECU development with AUTOSAR. For the list of Vector in-house training courses on the Internet. Starting with our extensive AUTOSAR experience and your aspired project goals. This quickly gives you a runnable system. we work together with you to setup the MICROSAR basic software (BSW) and RTE on your ECU hardware using the related configuration tools. . For this purpose we use a sample application. which ensures continuous support in case you have questions about how to use our products. MICROSAR Reviews You have been using our AUTOSAR Embedded Software for a longer period of time. It is possible to adapt the training content to your individual needs.com/AUTOSAR-Training. go to: www. letting you focus on your application. This support is typically performed at your business site. and you are approaching an important project milestone. Intensive exercises ensure its relevance to practice. In this process. such as provided software components. correctness and consistency of the selected settings and the required integration code. Based on prepared checklists. we support you in every phase of your ECU development.vector.
AUTOSAR Consulting In the framework of AUTOSAR consulting. please refer to the “Software Engineering Services” datasheet.AUTOSAR For more information On our “AUTOSAR Services” please contact us. which takes your specific requirements into consideration. together with you we can work out individual. technical solutions to various technical questions related to AUTOSAR: > Definition of an AUTOSAR-conformant software architecture > Optimal use of the AUTOSAR tool chain > Migration of existing software to the AUTOSAR architecture > Conceptualization of gateway functions > Structuring of MATLAB/Simulink models to be linked as software components via the RTE > Interfacing external peripheral components > Hardware-dependent Sleep and Wakeup concepts under consideration of individual quiescent current requirements > Consideration of requirements related to Functional Safety (ISO DIS 26262) We typically perform these consulting activities as customized workshops. including signal processing via the RTE > ECU and mode management in power up and shut down > Integration of diagnostics. installation of the MICROSAR software is performed with your concrete application. we ensure individual support of your project. we can support you in: > Initializing the hardware. Based on the specific objectives that were agreed on. This ensures that the worked-out solutions optimally fit into your ECU project. ◆ 2/55 . For example. We focus on addressing your individual needs here.vector. error memory and memory management in your ECU software > Linking of the applications to watchdog management > Integration of further standard software from the OEM The included Premium Support contains on-site support in addition to the telephone and email Hotline. For more detailed information on our engineering services. including CPU clock and PLL > Integrating the MICROSAR components in the project structure > Individual configuration of the operating system > Starting and stopping the bus communication depending on the network state > Providing the necessary I/O signal interfaces. Please find your contact person at: www. Software Development Moreover.com/contact MICROSAR Coaching In MICROSAR Coaching. we would also be glad to handle the entire development of your ECU software.
The necessary hardware drivers are also important here. an area in which Vector has well-founded knowledge. solutions for gateways or state management. Further information and a description of the available software modules can be found in the AUTOSAR section beginning on page 2/0. CANbedded Vector develops high-quality and innovative software components for use in the automotive industry. One focus of the product line is on ECU communication. Uniform solution Network communication is described in a database. while the infrastructure software includes the operating system. The use of uniform communication protocols is absolutely necessary when setting up networks in a vehicle. MOST and Ethernet/IP bus systems. > High level of maturity: It would be hard to find a vehicle with a CAN bus today that did not have a CANbedded stack. Detailed information on this can be found beginning on page 3/20. Further information on tools for development and testing of automotive networks can be found in the combined product catalog “Development of distributed systems” and “ECU testing”. LIN. 3/0 . This software is available for the CAN. CANopen For CANopen communication. code reviews. In addition. You can obtain them for the CAN and LIN networks as well as for the J1939 protocol. project-specific services and other development-supporting software tools.g. In addition.Solutions with CANbedded The software implemented in automotive ECUs can be either infrastructure software or application software. Your partner right from the start Vector offers comprehensive support. It is used to configure the software components and serves as a foundation for Vector development and test tools. Vector can assist you through the ECU development process with on-site startups. > Broad range of applications: Applicable for various use cases – from powertrain via body bus to infotainment > Support of many automotive manufacturers: Available in many OEM-specific variants. communication software and fundamental input and output services. e. FlexRay. The source code contains all functions and services required for the CANopen protocol. The latter implements the desired functionality. This gives software developers a universal and uniform solution. from the start of a project to its successful completion. The use of standardized software components ensures easy portability and reliable integration of ECUs in the vehicle’s network for the automotive OEM and its suppliers. Training sessions and courses provide basic information and in-depth knowledge on working with the software – conducted in Vector’s classrooms or right at your company. which are standardized by CiA. from simulation and design to testing and validation. Vector can offer individual solutions for further simplification of the application. Communication Software for AUTOSAR Systems Vector also provides AUTOSAR-based communications software. CANbedded products from Vector are available for systems without AUTOSAR. Vector offers source code for master and slave ECUs. the software components lead to a substantial reduction in development costs. Advantages of CANbedded > Many years of experience: Vector has been developing basic software for CAN communication in automotive applications since 1992.
COMMUNICATION SOFTWARE 3/1 >> CONTENTS CANbedded CANbedded J1939 CANbedded LIN Communication CANbedded Gateway CANdesc and CANbedded DEM Identity Manager GENy CANopen Master Source Code CANopen Slave Source Code Feature Matrix CANopen Source Codes CANerator CANopen XCP Professional 3/2 3/6 3/8 3/12 3/14 3/16 3/18 3/20 3/24 3/26 3/28 3/30 .
A multichannel variant is also available for communication over multiple CAN channels.CANbedded Basic software for CAN communication Vector CANbedded basic software lets ECUs exchange information over the CAN bus. With CANbedded. 3/2 Overview of the CANbedded software components . because the CANbedded stack handles OEM-conformant sending and receiving of messages over CAN. This provides you with a reliable foundation for your ECU. A single-channel variant of CANbedded has been optimized for use in ECUs connected to a single CAN bus. it handles communication-related tasks as specified by the OEM. As a part of the ECU software. please refer to the specific datasheets on the following pages. Transport Protocol and Communication Control Layer. Interaction Layer. Vector offers OEM-specific CANbedded variants for most OEMs. The use of CANbedded in all of a networks ECUs assures compatibility of all communication stacks. This reduces development costs and test effort. your ECU is able to efficiently communicate with other ECUs in the vehicle and with an external service tester. CANbedded consists of the configurable software components CAN driver. Overview of Advantages: > Reliable and tested through many years of development > Generated source code that is scalable and applicationspecific > Low memory requirement and fast runtimes > Supports over 80 different hardware platforms > Available in platform-specific and OEM-specific variants > Clearly defined and uniform interfaces > Easy to port to other platforms and OEMs > Easy to integrate in your ECU software Application Areas CANbedded lets users focus their efforts completely on their functional software. CANbedded is available in variants for most OEMs and for a large number of microcontrollers. You can extend the CANbedded stack with additional basic software from Vector for your specific application: > CANbedded Gateway > Diagnostics: CANdesc > Commercial vehicles: CANbedded J1939 > Measurement and calibration: CCP or XCP For information on these extensions. The CAN driver (the only hardware-specific component) is available in an optimized version for many different hardware platforms (8 to 64 bit controllers). Network Management. which you can combine as necessary to form a communication stack.
etc.vector. This let’s the user quickly and conveniently integrate CANbedded in the ECU software. IfActive. The following basic functions are provided by the CAN driver: > Initialization of the CAN controller > Sending of CAN messages > Receiving of CAN messages > Overrun and error handling > Notification via wake-up events Interaction Layer (IL) The IL operates signal-oriented and is responsible for: > Sending messages depending on the send types of the signals they contain (Cyclic. AUTOSAR NM or another OEM-specific NM algorithm is used. If possible.COMMUNICATION SOFTWARE Contact and Availability CANbedded basic software is available for many commonly used microcontrollers and in OEM-specific variants. which is available in different variants. This functionality is handled by the NM CANbedded software component. Network Management (NM) The main task of Network Management is to manage the sleep and wake-up states of a network’s ECUs. OnEvent. Vector would be glad to assist you in selecting the components you need. the CANbedded Transport Protocol conforms to ISO 15765-2. bus wake-up or different error states (Assertions) to the application by means of configurable callback functions. either OSEK NM.com/cve/ Or find your personal contact at: www.com/contact Functions CANbedded provides simple interfaces (APIs) that are identical for all applications.g. Transport Protocol (TP) By default. The ISO 15765-2 conformant variant is available in either 3/3 Configuration and parameterization with the GENy configuration tool . The CANbedded components route asynchronous events such as receiving of CAN messages. VWTP or MCNet. The configuration tool GENy from Vector offers preselections for configuring these filters and registers. The IL is available in OEM-specific variants.vector. CANbedded consists of the software components described in the sections that follow. For more information go to: www. All necessary settings such as parameters for the hardware acceptance filter or Bus Timing Register are made at configuration time. > Timeout monitoring of Rx messages and signals. This enables platform-independent use or re-use of the higher software layers. the API is standardized over all OEM and hardware variants.). OEM-specific TP variants are also available. e. > Notification of sending and receiving of signals. You can configure the precise set of generated APIs and callbacks to optimally adapt them to the needs of your specific application. CAN Driver The CAN driver provides an interface for higher software layers that is as hardware independent as possible. Depending on OEM requirements. The Vector tool chain optimally supports you here.
Extended. NM. ShutDown. > The CCL supports what are known as multipurpose ECUs (for details. such as CAN driver. They contain the parameters and function calls of the CANbedded software components that are used. TP. It manages defined system states (PowerOn. In special cases. CANbedded J1939 and CANdesc. It can coordinate state transitions (WakeUp and GotoSleep) according to the requests. the initialization sequence for software components is defined in the CCL configuration.) Configuration You configure CANbedded with the PC-based configuration tool GENy. GENy utilizes information from the communication database (e. StartUp. for time-critical applications on small microprocessors. Normal fixed. IL. the DBC file from the OEM) as well as manual settings. e.the 1999 variant or the 2004 variant and with different addressing methods (Normal. Stop/Sleep. The CCL offers the following functions: > Initializing the CANbedded software components > Calling periodic functions of the CANbedded software components such as Timer Tasks or State Tasks. Communication Control Layer (CCL) The CCL simplifies integration of the CANbedded software components in your ECU software. The scope of delivery of CANbedded includes: > GENy configuration tool as executable Windows program > C header and source files > Documentation and sample programs with makefiles 3/4 The CCL coordinates the state transition “Wakeup” . Scope of Delivery You get the CANbedded components as C source code. Mixed).g. GENy generates parameterization files based on the configuration. > Controlling the bus transceiver Special CCL Functions > The CCL already contains OEM-specific communication requirements such as Wakeup Prevention and Minimum Communication Activity. For example. certain portions of code may be programmed in Assembler. Normal) as well as communication states (Net request. see datasheet on the Identity Manager. Net release).g. and other CANbedded options CANbedded Gateway.
special workshops that address OEM-specific issues and individual consultation on software integration. 3/5 Additional Services You can have Vector perform project work on the following aspects: > Adaptation of the CANbedded software components to special target platforms > Extension of the CANbedded software components > Creation of software components for other bus systems such as FlexRay. ◆ Vector offers a comprehensive range of products and services for your CAN projects . For more information on individual training events and a schedule go to: www.vector-academy. we offer various courses and workshops on CANbedded in our classrooms or at your business site. This support lets you reduce the development time and costs for your ECU.COMMUNICATION SOFTWARE Training In the framework of our training program.com Additional basic software from Vector that is relevant to CANbedded: > CANbedded J1939 > CANbedded Gateway > CANdesc for diagnostics > Measurement and calibration with XCP/CCP > CANbedded LIN > CANopen Master and CANopen Slave You will find details on these products in specific datasheets on the following pages. Ethernet or MOST based on AUTOSAR This list is supplemented with telephone and e-mail hotlines.
the CAN driver and the J1939 components provide a multi-channel interface. as they are needed in heavy-duty vehicles. In this case. CANbedded J1939 is based on software components of the CANbedded product line. These components provide functions for basic communication between ECUs. diagnostics. for details please refer to the CANbedded datasheet.CANbedded J1939 Embedded Software Components for J1939 Applications Overview of Advantages > Convenient configuration via GUI > Code efficiency due to broad configurability of the software > Good portability due to hardware-independent API > Easy to integrate other standard components (e. etc. transport protocol. priority) via macros. Vector CANbedded J1939 software components are available as source code. Supported Standards J1939 software components are based on the following international standards: > ISO: International Organization for Standardization > SAE: US Society of Automotive Engineers Many different projects with international automotive OEMs have confirmed that the Vector software components conform to these standards. static address claiming (J1939-NM) and an interface to OSEK/VDX-OS 3/6 > J1939 Module Virtual ECUs: Multiple instancing of the software on a CAN channel for implementing multiple independent J1939 nodes on one ECU > J1939 Transport protocol BAM > J1939 Transport protocol CMDT > J1939 Dynamic Interaction Layer: Standard access to the signals of PGNs with variable CAN identifiers (node address.) The CANbedded J1939 package contains software components for SAE J1939-based applications.g. J1939 software architecture . Some applications use multiple CAN buses. Application Areas > Powertrain and chassis ECUs in heavy-duty vehicles > FMS (Fleet Management System) > Terminals and agricultural implements Functions The following J1939 software components are available: > J1939 Base Module: Contains queues for sending and receiving J1939 messages (PGNs).
com/j1939 ◆ 3/7 Configuring the J1939 system with a convenient user interface . special workshops focusing on OEM-specific aspects and consultation on software integration tailored to your needs.com Properties of the J1939 Software Components > Configurable standard components > C source code is provided for easy handling during integration > Low ROM and RAM memory requirements due to excellent scalability > Runtime efficiency > Generation of parameter settings and configurations > Easy to integrate in application software > Components are compatible with the SAE J1939 standard Configuration The PC-based GENy software tool is used to configure and generate the CANbedded J1939 software components. You will find a current listing on the Internet at: www. user manual. Scope of Delivery The CANbedded J1939 product includes: > GENy for configuring the software components > C source code > C header files > Documentation.COMMUNICATION SOFTWARE Solutions for ISO11783 and NMEA2000 We offer a CANbedded J1939 extension for ISO11783 (ISOBUS) and NMEA2000.canbedded. Readme > Sample programs Optional Services Vector can perform project work for you covering these aspects: > Adaptation of software components to other target platforms > Extensions for ISOBUS and NMEA2000 > Extension of standard components to add your specific functions > Flash programming This is supplemented by telephone and e-mail hotlines. Supported Hardware Platforms CANbedded J1939 is available for many different controllers and compilers.vector-academy. It contains the following functionalities: > Dynamic address claiming (J1939-NM) > ETP transport protocol and FastPacket > Working sets Training We offer various courses and workshops for CANbedded J1939 in our classrooms as well as at our customers’ sites. This reduces your development time and development costs. For further information on individual classes and dates please visit: www.
Features and Advantages Increasing software complexity makes it advantageous to implement standardized software components.3/2. simulation. 9600. these products serve as universal. analysis and for test purposes. Therefore the LIN driver does not require any auxiliary timers. Timing control of the LIN software components is achieved by having tasks called periodically by the application or an operating system.1 and 2. oscillator frequency. serial communication system for distributed electronic control units in the motor vehicle. For physical bus access one of Vector’s XLIInterface products can be purchased. CANoe. Modifications and settings in detail: > Adaptation of ECU-specific parameters to the network design > Configuration of the LIN driver to the properties of the specific ECU e.0/2. serial bus interfaces for the LIN bus. Functions The fundamental objective of the implementation is to provide an interface that is easy to use and satisfies all applications.3 2011-12 Overview of the software components of CANbedded LIN Communication More Information: www. Vector’s expertise acquired in developing and working with other protocols has been utilized throughout the development of LIN software components: > Standard software components based on a portion of the generated code are scalable for application-specific requirements > Automatic generation of parameter settings and configurations > Runtime efficiency > Low demand for ROM and RAM memory > Simple interfacing to the application software > Compatibility with other Vector products including analysis. The standardized interface offers these features: > Initialization of the LIN hardware > User-configurable baudrate (Recommended: 2400. The tool imports either LDFs or NCF files (Node Capability File) for parameterization. of which Vector is an Associate Member. Vector’s LIN simulation and analysis tools (e.LIN) are available for integration.vector. messages. A configuration tool is used to adapt all LIN software components to ECU-specific requirements.g.EMBEDDED SOFTWARE CANbedded LIN Communication Embedded Software Components for Local Interconnect Network LIN (Local Interconnect Network) is a cost-effective. UART. etc.2/1.g. baud rate and schedule tables.com/contact . The LIN protocol is specified by the LIN Consortium. This includes all of the information needed to define signals. and 19200 Baud) > Sending of LIN messages (confirmation by flags and callback functions) V2.2 > Support of multi-channel LIN configurations LIN networks are described in the LDF (LIN Description File) format according to the “LIN Configuration Language Specification”. and calibration tools > Support of LIN 1.LIN and CANalyzer. > Configuration of diagnostic services for LIN Slave ECUs > Definition of message and signal callbacks The object codes of the LIN software components are compiled and linked with the application.
routes them to the appropriate service and constructs the response in interaction with the application. the LIN driver.3 diagnostics for LIN slave ECUs. It receives requests.com/contact . This makes it easy to implement CAN-LIN gateways. we offer a range of classes and workshops on CANbedded LIN Communication.com/vi_canbedded_lin_en. The driver is a standardized and easy-to-configure software component for communication between master and slave network nodes. One component is a hardware-dependent low-level SIO driver. LIN Master Transport Layer Since the master ECU usually has an auxiliary CAN channel. Overview of Design.vector. The focus is on cost-effective communication networks for ECU subsystems with low data rates. The LIN driver is one of the CANbedded components from Vector. which is included in the delivery. > DTL Cooked accepts assembled data and segments them according to LIN bus requirements (Diagnostic Service Data Units). This API satisfies all of the requirements of the current LIN standard. LIN Slave Diagnostics LINdiag is a very compact implementation of UDS 14229. over which diagnostics are performed from a tester.0/2.html > Receiving of LIN messages (notification by flags and callback functions) > Sleep and wakeup handling > Protocol error handling > Timeout monitoring of messages > Checking of runtime behavior during the development phase (debugging) Application Areas LIN was developed to round out a collection of automotive protocol standards. Hardware Interfaces Two software components are needed for LIN communication. whose task is to implement abstraction of access to the serial interface. is overlaid on this and provides an API to higher-level components. the main task of the LIN master is to pass the received tester requests to the relevant LIN slaves.com Availability Our LIN software components for motor vehicle ECUs are available for a large number of commonly used microcontrollers. To send and receive requests and responses LINdiag needs the LIN Transport Protocol. please visit: www. it assures consistent integration with CAN components. but it has been adopted in other areas such as automation engineering as well.EMBEDDED SOFTWARE Training As part of our training program. it offers two API types according to the LIN 2.vector. The LIN Diagnostic Transport Layer (DTL) is used for this. LIN therefore supplements existing bus protocols.2 specifications: > DTL Raw is used if the data already exist in segmented form (routing of CAN TP messages on LIN).1 and 2.vector-acadamy. For further information please visit: http://www. This involves internal management of a diagnostic buffer to monitor for data consistency and overruns. which are usually implemented as master network nodes. For more information and the dates of our training courses. Configuration and Integration Processes More Information: www. The second component.
More Information: www. e. special workshops with OEM-specific focus and individualized consultation on software integration with the goal of reducing development time and costs.vector. support of the SAE J2602 “Recommended Practice” specification is available for LIN drivers.EMBEDDED SOFTWARE Further Options > Optional for slave ECUs: Diagnostic software components with associated transport protocol > Optional for master ECUs: Transport protocol with raw or cooked API > Gateway: CAN-LIN and LIN-LIN routing for master ECUs > SAE J2602: As a supplemental option.com/contact . > Flashing of LIN slaves Scope of Delivery The following items are supplied with the product: > Configuration tool (executable Windows program) > C sources for LIN driver and optional software components > Sample programs > Documentation and operating instructions Licenses When the same hardware interface and same compiler are used the acquired licenses can be used for all devices of a processor type and any desired projects.g. Supplemental Services Vector also offers related project services such as: > LIN driver expansions > Support of other target hardware > Development of higher OEM-specific protocol layers. diagnostic protocol Services also include telephone and e-mail hotlines.
vector.com/contact .EMBEDDED SOFTWARE More Information: www.
It covers the specific requirements of many different OEMs. the messages may differ in their message-ID. and so it is hardware independent.CANbedded Gateway Standard Embedded Software Components for CAN and LIN Routing Overview of advantages > Selectable coupling of CAN and/or LIN networks with userdefinable routing relationships > Mature standard software component > Solid.g. Message Routing In routing of messages. by scaling signal values). If routing relationships occur that cannot be resolved.g.g. The CANbedded Gateway utilizes bus-specific standard components of CANbedded. In case of an Rx timeout. CANbedded Gateway lets users define routing relationships simply and quickly. Users can select from: > Signal routing > Message routing (with/without data queue) > TP (Transport Protocol) routing Signal Routing Routing of signals makes it possible to exchange dedicated information (e. The signal to be transmitted is written and routed with a predefined signal value (default value or special substitute value). momentary vehicle speed) between the networks. The send cycle times. the CANbedded Gateway implements a substitute value strategy. Functions The CANbedded Gateway contains complex mechanisms for receiving all messages and signals and then sending them to another network under consideration of filter and conversion rules. Both 1:1 and 1:N routings are supported in any direction. The values of the signals to be transmitted are not changed in the process. e. a gateway ECU is needed that only transports to the other network those messages or signals that are actually needed. the application can use C callback functions to flexibly adapt signal contents before routing (e. send types and signal positions within messages – all defined in the communication database – may differ between the source and target networks. but it cannot be applied in all routing relationships. send cycle and send type. the entire message is routed in either the interrupt or task context. Application Areas CANbedded Gateway is a mature standard software component for gateway ECUs between different CAN or LIN networks. This routing type is faster and more efficient than signal routing. In message routing. if the signals of a routing relationship have different sizes. lean and efficient foundation for your gateway ECU > Available for a large number of OEMs To exchange data between different networks. 3/12 Gateway between CAN and LIN buses .
message routing always utilizes the most recent data. the application can enable or disable routing of individual groups with the help of an API. The configuration process is based on a DBC or LDF/NCF description file. The user can control gateway activities by configuring “conditional routing”. Configuration The CANbedded Gateway is configured with GENy. the CANbedded Gateway sends the data of the last Rx event. it is possible to support different protocol addressing modes on the CAN bus. Diagnostic requests from CAN to LIN and the associated responses from LIN to CAN might be transmitted. This is done by defining routing groups and assigning routing relationships to one or more routing groups. TP routing requires the ISO Transport Protocol for CAN or the DTL (Diagnostic Transport Layer) for LIN. Neither the signal layout within the message nor the signal values are changed here. For more information on individual training events and dates please visit: www. If data is transmitted less frequently than the data is processed by the associated Rx event. Other Relevant CANbedded Products Preconditions for use of the CANbedded Gateway are the presence of the Vector Interaction Layer (when signal routing is used) and the relevant Vector CAN or LIN drivers. Using the ISO transport protocol component from CANbedded.vector-academy.com By default. the configuration and code generator tool from Vector. At runtime. such as during software flashing or diagnostic sessions.COMMUNICATION SOFTWARE Training In the framework of our training program. we can offer you various training events and workshops on our software components in our classrooms as well as at your business site. for example. TP Routing The TP Gateway is responsible for routing the transport protocol data. This saves on bandwidth during critical phases. Routing relationships are defined either: > Automatically by OEM-specific algorithms based on clear rules > Manually by targeted selection of the signals and messages to be implemented Scope of Delivery > Configuration tool as executable Windows program > C source code > C header files > Documentation 3/13 ◆ Layer model of the CANbedded Gateway .
Their use helps you to drastically reduce effort for qualifying your safety-relevant functions.0 2011-12 CANbedded Safe More Information: www. WDGIF and WDGDRV from SafeExecution. This means that software parts whose correct execution cannot be verified cannot disturb safety-relevant functions unnoticed. SafeExecution and SafeSelfTest bundles from CANbedded Safe were implemented according to the AUTOSAR specification and are compatible with the CANbedded components. They contain the following specific functionalities: SafeExecution: > Runtime monitoring of tasks > Flow control of safety-relevant functions > Memory protection and safe context switching SafeCom: > Safe intra-ECU and inter-ECU communication SafeSelfTest: > Periodic hardware checking The use of Runtime Monitoring. Functions The SafeCom. Flow Control. V2. The modules from CANbedded Safe are SEooCs (Safety Elements out of Context). This solution is the result of collaborative work with TTTech. our partner with many years of experience in the field of functional safety. Runtime monitoring is provided by MICROSAR OS SC2/SC4 and is validated to ISO DIS 26262 by the modules WDGM. CANbedded Safe lets you develop OEM-specific applications for ECUs up to ASIL D per ISO DIS 26262. which are developed according to ISO DIS 26262 / ASIL D.vector. Runtime Monitoring Runtime monitoring assures that tasks have sufficient computing time for their execution.com/contact .EMBEDDED SOFTWARE CANbedded Safe Safety according to ISO DIS 26262 for ECUs with CANbedded software Overview of advantages > Solution for all Automotive Safety Integrity Levels (ASIL) through ASIL D > Savings in qualification costs > Support of different ASILs on one controller Application areas You will receive CANbedded Safe from Vector for using CANbedded software in ECUs with safety-relevant functions. Memory Protection and Safe Context Switching makes it possible to let safety-relevant and non-safety relevant parts of your application software run next to one another on the same ECU without interference.
SafeContext prevents unauthorized writing by one software part to the memory of another that could corrupt the data. assures memory protection for ECUs with safety-relevant applications on suitable microprocessors (e. We would be glad to provide you with information on OEM-specific variants as well as offer you customized support for your projects. we offer various training courses and workshops on CANbedded at our classrooms as well as at your business site. Please contact Vector to find out whether the hardware you are using is already supported. Please find your contact person: www. The SEooCs conform to ISO 26262 ASIL D and are developed according to the AUTOSAR specification. If one of these checks fails.vector. Memory Protection and Safe Context Switching The MICROSAR operating system’s option SafeContext.vector-academy. Vector would be glad to consult with you in selecting specific monitoring mechanisms for your project. optionally as source code > Instruction line based generator (for Windows XP/Vista/ Windows 7) > BSW module description files > Description files for DaVinci Configurator Pro > Documentation with Safety Manual Implementation Safety-relevant functions are implemented by the Safety Elements out of Context (SEooC) from CANbedded Safe.vector. WDGIF and WDGDRV.EMBEDDED SOFTWARE Training In the framework of our training program. with MPU. Hardware checking You can perform cyclic tests for error-free functionality of the ECU’s various hardware components during operation using generic test functions of the SafeSelfTest package. which was developed to ASIL D. This detects errors such as masquerading.com/contact . For more information on individual training events and a schedule. the application is informed.g. Product components > Software modules as library with C header files. Safe Intra-ECU and Inter-ECU communication Data that is exchanged between safety-relevant applications must be checked for correct transmission. CANbedded Safe contains the following SEooCs: SafeCom: > E2ELIB: End-to-end library > Protection Wrapper: End-to-end protection Wrapper SafeExecution: > SafeContext: Memory Protection and Safe Context Switching (option for MICROSAR OS) > WDGM: Watchdog Manager > WDGIF: Watchdog Interface > WDGDRV: Driver for internal watchdog devices > WDGEXT: Driver for external watchdog devices SafeSelfTest: > RAMTST: Tests for RAM memory > FLASHTST: Tests for flash memory > CORETST: Tests for the microcontroller core > IOTST: Tests for inputs and outputs More Information: www.com Contact and Availability The drivers of CANbedded and the MICROSAR OS module are hardwarespecific. failure or reversed data. The precise scope of monitoring that is necessary is project-specific. please go to: www. and it can react accordingly. Configuration The safety elements of CANbedded Safe are configured with the DaVinci tools. A checksum protects the data contents and the correct sequence of data is monitored by a message counter. They detect and handle potential errors in non-safety software layers. This involves using what are referred to as checkpoints in the safety-relevant application software.com/contact Program Flow Monitoring Correct execution of safety-relevant application software is assured by the modules WDGM. the Memory Protection Unit). The option SafeContext is available for MICROSAR OS (SC3/SC4) and it is used to separate the various software parts from one another during task changes and interrupts.
vector. 8FX 16FX. Metrowerks CANbedded/ CANbedded J1939 CANbedded LIN X X X V2.EMBEDDED SOFTWARE Wide Availability of CANbedded Supported Microcontrollers and Compilers Controller Altera NIOS II with Bosch D-CAN controller Analog Devices Aduc703x AduCM330 Blackfin BF5xx Atmel AT90CANXX ATmega (X8. MC9S12x. FR50 FR60 FR81 MB86R0x Infineon C16x C5x5 TriCore XC16x XC2000 XC800 Microchip dsPic33F PIC18 PIC24 Micronas CDC32xxG CEVF National CR16 NXP LPC2000 Green Hills X National. QCC X X X  X X X X X MPC55xx. IAR Microtec. Metrowerks Metrowerks Metrowerks Cosmic. Green Hills.com/contact . GNU. S12x. Metrowerks X/X X X X X X X X/X X X X X X X ARM X Keil X/HPInfotech. Metrowerks DIABDATA Wind River. IAR. MPC56xx GNU X MPC5200 Compiler CANbedded/ CANbedded J1939 CANbedded LIN Controller Compiler DIABDATA Wind River. Metrowerks. Tasking Keil. XM1) ATtinyX7 AVR32 T89C51CC00x Cypress PSoC3 Europe Technologies easyCAN Freescale 68HC08 DSP56F80x DSP56F83x HC12. X4P. XC1. GAIO. MCS12 HCS12x. S12. MC9S12. IAR. Metrowerks ARM. QCC DIABDATA Wind River. Green Hills.4 2011-12 More Information: www. IAR X X Green Hills IAR X X/Microchip Microchip Microchip X X/X X X Keil. IAR IAR IAR Keil X X/X X X X X X ARM. 16LX FR30. Tasking Tasking Keil X X/X X X X/X X X Fujitsu Fujitsu Fujitsu Fujitsu Fujitsu GNU. Green Hills. MCS12x MAC 7100. HCS12. IAR IAR VisualDSP++ X X X X Fujitsu 8L. Tasking DIABDATA Wind River Cosmic. Tasking Keil GNU. Metrowerks Cosmic. IAR HPInfotech. MAC 7200 MC68k MCF52xx MCS08 MPC5xx Cosmic.
Hiware GNU GNU. IAR IAR Renesas Renesas. IAR Renesas. IAR Renesas. QCC Texas Instruments. Green Hills. GNU. SH2-A Renesas (NEC). IAR Renesas. Metrowerks X X X  = Currently in development More Information: www. Tasking ARM. Green Hills GNU X X X TMS570 Toshiba TLCS870 TLCS900 Tx03 TX39 TX49 X X X X X X X SH4 V85x X X X Xilinx Microblaze Vector CANoe osCAN Emulation Microsoft VisualC X X X Silicon Labs C8051F5XX STmicroelectronics SPC56xx DIABDATA Wind River. IAR Keil X X X X X X X X X X X X X X/X TCC800 Texas Instruments TMS320 TMS470 ARM X Texas Instruments. H8SX M16C M32C M32R R8C R32C SH2. GAIO. IAR Renesas. QCC Renesas (NEC).com/contact . Green Hills ARM. Green Hills.EMBEDDED SOFTWARE Controller SAF7780 SJA20xx OKI AVC-Core ML76Q25xx Panasonic MN101E MN103S Compiler Green Hills Green Hills CANbedded/ CANbedded J1939 CANbedded LIN Controller ST7 Compiler Cosmic. IAR Renesas (NEC). GAIO Renesas. Keil. ARM.vector. ARM Toshiba Toshiba ARM Green Hills GNU. IAR Renesas. GAIO. Green Hills ARM Cosmic CANbedded/ CANbedded J1939 CANbedded LIN X X X X/X/X X X X X/- X X X X ST9 ST10 ARM IAR X X ST30 STA20 Panasonic Panasonic X/X STM32 STM8A Telechips X X X X Renesas Electronics (NEC/Renesas) 78k0 78K0R 78K0S H8 tiny H8S. Green Hills Texas Instruments. IAR Renesas. Green Hills. Green Hills.
Application Areas > ECUs for passenger and commercial vehicles > ECUs in CAN. you can extend CANdesc with the CANbedded DEM component.g. To implement the error memory. This simplifies interfacing of diagnostics to your ECU software. Session and Security of a sub-service > State control (depends on the CANdela database. Sub-Service Id. MOST. $2A (ReadDataByPeriodicIdentifier) and $2C (DynamicallyDefineDataIdentifier) > Validation of diagnostic requests in reference to Service Id. Functions CANdesc and CANbedded DEM are conformant to the OEM-specific diagnostic specification and are available for a number of different OEMs. simple and uniform interface to the OEM-specific diagnostic protocol in the desired version > Available for many bus systems > Together with CANdelaStudio CANdesc gives you a comprehensive diagnostic solution from specification to embedded software > Multiple diagnostic configurations with up to 31 different parameter sets > Guaranteed consistency between diagnostic specification and generated code The diagnostic software component CANdesc (desc = diagnostic embedded software component) is the uniform implementation of the diagnostic protocol for different automotive OEMs. CANdesc is generated according to the configuration based on the diagnostic specification (CDD file). you can also use the two software components in your communication stack. > Full implementation of diagnostic services $28 (CommunicationControl). Session or Security) > Assurance of data consistency in parallel diagnostic requests from the same tester or multiple testers > Generation of a template including the necessary function stubs that lets you realize your own diagnostic implementation quickly and easily. Format. FlexRay and other communication systems CANdesc and CANbedded DEM can easily be incorporated into a CANbedded communication stack from Vector. Complete generation of the ECU’s diagnostic software . They contain the following functionality: CANdesc: > Provides a signal-based interface as a uniform interface to the application. e. However.CANdesc and CANbedded DEM Software components for diagnostics 3/14 Overview of Advantages > OEM-independent implementation of your application software > Quick. Session. which gives you a fully OEM-specific diagnostic solution for your ECU.
Handling of Variants If your ECU requires diagnostic configuration variants. 700 bytes RAM: approx. This avoids redundancies in the ECU software. For each error (DTC). 6 kBytes Tables and constants: approx. With GENy you can define up to 31 different parameter sets and store them in the ECU in a resource optimizing way. the software component stores the following information in error memory: > DTC status byte > Environment data > Cycle counters > Fault detection counter > Aging counter When CANbedded DEM is combined with the diagnostic software component CANdesc.COMMUNICATION SOFTWARE Example of Code Sizes Microprocessor: Motorola HC12. 3/15 ◆ Diagnostic software (CANdesc and CANbedded DEM) in the diagnostic development process . The RAM size depends on the size of the scheduling table and the number of dynamically defined data identifiers. services or DTCs are merged in the generated diagnostic code. it must initiate saving of the related Diagnostic Trouble Codes (DTC). CANdesc and CANbedded DEM offer a powerful solution for this. > Optional: Implementation of the Diagnostic Adaptation Protocol (DAP) for MOST ECUs CANbedded DEM As soon as the application software detects errors. The CANbedded DEM component from Vector can be used for this task. For more details. To create this file you will need the tool CANdelaStudio Version 6. Scope of Delivery > GENy configuration tool as executable Windows program (for Windows NT/2000/XP/Vista/Windows 7) > Documentation/user’s manual/Readme > C source code for CANbedded DEM Additional Services Vector offers project services related to diagnostics: > Adapting the application to CANdesc > Implementing error memory strategies > Process consultation in the area of diagnostics > Testing diagnostic implementations for ECUs. MC9S12P128 Compiler: Cosmic 4. you get a complete implementation of the following error memory related UDS services: > $14 Clear diagnostic information > $19 Read DTC information > $85 Control DTC setting Configuration You configure CANdesc and CANbedded DEM with the GENy tool and a CANdela file (CDD).5 or higher. because identical interfaces to the same data. please refer to the CANdelaStudio datasheet in the diagnostics catalog.7 13 Diagnostic services and 40 subfunctions are implemented Code size: approx. The use of CANdelaStudio offers CANdesc users significant advantages. 14 kBytes. 90 bytes plus bytes for the diagnostic buffer Extended setup with services 0x2A and 0x2C: The code size is increased to approx.
Additionally.5 2011-12 OEM G GAC Geely GM Great Wall Motors H Honda HMC I Isuzu Iveco J JAC Motors Jaguar / Landrover Communication X X X X Diagnostic Software X X X X Flash Bootloader X X X X X X X Communication X X X X Diagnostic Software X Flash Bootloader X X X X X X X X X X X X X X X X X X X X X X X M MAN X X X X X X X X X X X X Mazda Mitsubishi N NAC Nissan P Porsche PSA R Renault S SAIC SsangYong Subaru Suzuki X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Foton X More Information: www. a version without vendor-specific characteristics is available. e.com/contact .g. Please contact Vector.vector. We will help you to find the optimal solution for you requirements. Depending on the OEM the software is available for conventional (CANbedded) and/or AUTOSAR-conformant ECUs. UDS or KWP2000 is used as diagnostic protocol. OEM B BAIC Brilliance BMW BYD C CHANA Chery Chery Quantum Chrysler Claas D DAF Daimler Dongfeng F FAW FCC FIAT Fisker Ford V2. fault memory or flash processes. The diagnostic software and the Flash Bootloader contain OEM-specific diagnostic services. Depending on the OEM the scope of the available diagnostic solution differs.EMBEDDED SOFTWARE Supported OEMs For OEM-specific Basic Software Vector offers embedded software for a large number of OEMs.
com . 24 > 70499 Stuttgart > Tel.vector.EMBEDDED SOFTWARE OEM T Toyota V Volvo AB VW/Audi Communication X Diagnostic Software X Flash Bootloader X X X X X X X OEM independent X X X Vector is pleased to support further OEMs on request. +49 711 80670-0 > Fax +49 711 80670-111 > www. Vector Informatik GmbH > Ingersheimer Str.
only one application needs to be developed. Right ECU). This software is loaded in the left and right ECUs. The decision on whether the software is to be installed in the left or right door ECU is made with each new initialization. Load the database that covers the ECUs in the GENy configuration tool and select both ECUs simultaneously.g. there are differences in the receive and send messages. Vector knows these continually recurring use cases well and has developed optimized solutions especially for them. The differences are automatically read out from the DBC file. Instead. differentiate between the left and right sides using generated macros in the code. An ECU’s identity is set when the ECU is initialized. In the second case. Cost savings are realized by reducing administrative effort. Identity An identity identifies an ECU. It determines which variant of the ECU should be activated (e. one trend is clearly evident – ECUs are becoming increasingly more powerful. Use cases Practice shows that it is primarily the following three use cases that recur frequently: > Physical multiple ECU > Virtual multiple ECU > Multiple configurations ECU The solution approaches presented below lead to substantial simplification. but the ECU acts differently to the outside world depending on the identity which is initialized. At the same time.Identity Manager Solution for Multiple ECUs Physical multiple ECU Advantages > More efficient handling of variants > Less administrative effort > Reduced warehouse costs When tracking the development of ECUs in automobiles. Configure the Identity Manager as a physical multiple ECU and assign a separate identity to each of the nodes (Left ECU. an identity is the configuration of an ECU that is active at run time. based on a description file. It is also easy to implement crossovers of receive and send messages between the two door ECUs while optimizing resources. These ECUs have nearly identical functions. which is reflected in the growing effort required to manage them and also results in growing costs. So. reduce administrative effort and thereby reduce costs. So. diagnostics and Network Management address. the number of variants is growing drastically. This can only be achieved with the assistance of intelligent solutions that can manage the many different variants. However. buffer overlaying is not needed. There are essentially two different ways to proceed in coding: If the message layout is identical between the identities. 3/16 . utilize the manual buffer overlay in GENy. which door side). The steps: Develop an ECU that will later be used for both door sides. A simple function call establishes the ECU’s identity. This means that the same signal APIs can be used regardless of the currently active identity. A typical case of physical multiple ECUs are the ECUs for the driver and passenger side doors. Based on our many years of working together with automotive OEMs and suppliers.
Just as with the physical multiple ECU. you only need to select those nodes that will be implemented and then configure a virtual multiple ECU in the Identity Manager. In the configuration tool GENy. saving on additional hardware. The different communication nodes are derived from one database. First. gateway and radio) in one CPU. A typical application involving multiple configurations is the development of ECUs for both a current car line and a new car line. These are referred to as virtual multiple ECUs. This makes it possible to represent multiple ECUs (e. All nodes are assigned to one identity. These configured. develop the software for both car lines. Changes made within the associated database are often very extensive. The new configuration could even support a different number of CAN buses. In doing so. treat each car line as though it were assigned to one (or more) dedicated CAN channel(s) with an associated database (DBC file). It is possible to use a completely different signal layout or use different messages for different model series. the ECU’s identity is determined by a function call at the start.COMMUNICATION SOFTWARE Virtual multiple ECU Multiple configurations 3/17 Higher-performance control modules also contain more memory space.g. The identity operates from a node superset and all necessary information on the nodes. logical CAN channels are then mapped to physical CAN Controllers. ◆ . These ECUs are also referred to as carry over ECUs.
Vector’s many years of experience in the area of ECU development ensures optimal workflows between OEM and suppliers without altering their tasks or roles. Features and Advantages GENy is a developmental offshoot of the previous configuration tools CANgen and DBKOMgen. 3/18 The following properties characterize the design: > Thoroughly modular structure due to its static framework. Plausibility checks prevent invalid settings and thereby prevent errors. GENy’s graphic interface makes it very easy to use and intuitive. Tool tips and the online help function help to save time and immediately gives you the information needed about possible component settings. The configuration data is shown and processed in a hierarchical tree structure. The GENy architecture was completely redesigned based on experience with those two tools. even in complex heterogeneous systems. and the user gets a clear view of all options. This makes navigation user friendly.GENy PC-Tool for Configuring Embedded Software Components GENy is the convenient configuration tool for software components from Vector. stand-alone graphic user interface (GUI) and dynamically reloadable components > Reloadable hierarchies make it well suited for any configuration task (CANbedded. The latter is essential for an OEM-specific appearance of GENy’s GUI and guarantees that parameters will have functionally relevant preset values. It is used to configure CANbedded components. FlexRay) > A cleverly designed framework mechanism interprets and manages dependencies in configuring components > XML is used throughout as the file format. It was created for development processes of the future. GENy is a collection of components (not a rigid program block). GENy Program Window . LIN. AUTOSAR communication modules and the Flash Bootloader for use in production ECUs. GENy always appears with the same “look and feel” independent of the components to be configured. both for the component descriptions (Attributes) and data saving > Open interfaces offer simple expandability This makes GENy a scalable and fully generic configuration editor/generator that permits consistent configuration from a single integration environment. therefore it can also be expanded very easily by adding auxiliary components. The Configuration View can be modified manually or via an external XML file.
COMMUNICATION SOFTWARE Training As part of our CANbedded training program the configuration tool GENy is also explained.g. mistakes in configuring) and other important information. and this indicates potential errors (e. This is done to avoid tedious debugging efforts.vector-academy. LIN. Functional capabilities of GENy include the configuration of: > Embedded software components for CAN. and FlexRay > Flash Bootloaders > AUTOSAR BSW (communication modules) GENy reads the following input files: > CAN database files (DBC) > LIN files (LDF) > FlexRay files (Fibex) > CANdela database (CDD) > AUTOSAR “ECU Configuration Description” (EDUC) Application Areas The GENy configuration tool is always used in conjunction with other Vector software components for communication and diagnostics. GENy fulfills AUTOSAR Consortium requirements. Configuration and parameter files can be generated to integrate them in the application project. ◆ 3/19 GENy Navigation View . XP and Vista Functions GENy is the tool for configuring any software component. Characteristics: > Configuration templates for different application types > System-wide parameters only need to be configured once > There is only one XML-based configuration file > Expandable due to open interfaces > For the Windows operating systems 2000. For more information on individual training events and schedules please visit: www.com The generation process is logged in the Message Window.
Functions The CANopen Source Code offers the following functions: SDO Server PDO/SYNC Handling Heartbeat Producer/Consumer NMT Slave (supports “Life Guarding”) Simple adjustment to various requirements Broad spectrum of supported hardware platforms Source code configuration and automatic generation of the object directory via CANerator CANopen For special application areas there are expansion modules available for the CANopen Source Code. The user can create up to 200 PDOs and then transmit these event-based through changed data contents. synchronously through the reception of a SYNC message or time-triggered.com/contact . On receipt of a PDO a callback is initiated in which the user can place additional handling code. it is easy to create your own entries.120011-3 Modules of the CANopen Source Code More Information: www. and block transfer for up to two parallel SDO servers. Using these specifications. All PDOs are also configurable via the object directory.vector. To simplify connection of internal application data to the object directory. The user can concentrate on the integration of the application. PDO Handling For the PDOs. the implementation of the CANopen protocol is simplified significantly. especially in systems where resources are at a premium.TOOLS & COMPONENTS FOR OPEN NETWORKING CANopen Source Code Embedded Software for CANopen The CANopen Source Code contains CANopen services required for an implementation. which can be ordered separately: Mini-Master LSS Master LSS Slave SDO Server The SDO Server offers an object directory and supports all defined SDO transfer mechanisms such as expedited transfer. segmented transfer. there are exemplary entries already in the object directory. the initial configuration is specified via static structures that the user can adjust to his circumstances. The code corresponds to the most recent version of the CANopen DS-301 communication profile enabling a secure and CANopen-conforming implementation of the project. Features and Advantages Significant time savings can be achieved during product development by using the CANopen Source Code. V2. The code supports variable mapping up to a granularity of 1 byte. Application Area The code can be used everywhere customers would like to equip their devices with CANopen functionality. It thus offers the user the communication functionality required for internal device development.
The code supports an interface for non-volatile storage of parameters. Adaptation of the Code Before the code is translated. Often. Our support services range from custom-tailored training solutions to workshops to project work.g. by limiting functionality. For current information.vector. Mini-Master The full functionality of a CANopen manager is not required for many embedded networks. appropriate entries must be added to the C files. for example. Support during Integration We can also support you during the integration of the CANopen Source Code into your environment. the user can specify the qualities to be supported allowing the code to be used even on systems with very limited resources.com/contact . Of course.TOOLS & COMPONENTS FOR OPEN NETWORKING The CANopen Source Code by Vector is available for many popular microcontrollers. first an adaptation is always necessary to abstract the CAN controller and the specific timer and interrupt system. the relevant compiler is also considered here. The adaptation occurs via the #define instructions that are set in a configuration file. This makes it possible to set up highly efficient monitoring mechanisms in a network. For each object it is possible to initiate callback functions with user-defined functionality when reading or writing. This makes it possible to adjust settings in the object directories of other nodes and to call up data that is not available through PDO (e. please refer to the CANopen CANerator product information. Vector offers prepared adaptations for many platform combinations. please visit our website: www. Devices without access possibilities via switches (e.com/sourcecode NMT Slave The code supports both guarding and heartbeat. With the aid of the CANopen CANerator. CANopen devices require a setting of baud rate and node number. LSS (Layer Setting Services) Among other things. Thus. Such an object directory contains the object's attributes and a pointer to the actual memory location. SDO Client – the user can thus also initiate an SDO transfer. For additional functional details. CANopen specifies the LSS (CiA 305) for this. It contains: NMT Master – control of the status machine of the NMT slaves to start the network. Monitoring of nodes by means of node guarding. watertight sensors) require a setting of these values via the CAN bus itself. Here it is assumed that the memory is available via a file system or as flash. for example. Adaptation to a Target Hardware To use the CANopen Source Code on a microcontroller platform. For this. The necessary services are provided in the form of source code modules by the LSS Slave and LSS Master add-on modules. It is possible to react to heartbeat messages of other nodes (heartbeat consumer).g. an area test can be implemented when writing an object. for diagnostic purposes). emphasis can be placed on requiring very few resources and the simplest possible use. User-specific emergency messages can also be generated. More Information: www. This is the purpose of the add-on Mini-Master. this adaptation is simplified significantly. SYNC Producer – This module can be used to periodically send the SYNC message.vector. By using the CANerator tools (sold separately). this object directory can be created automatically. Local Object Directory The object directory of the source code can easily be expanded by the user.
[s]. 1001. [e] – expedited [s] – segmented [b] – block More Information: www.vector. [b] – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – 16 [e]. [s]. 1261) 0 – n1 8 bit (byte boundary) – – – V1.com/contact . [b] – – – – (max.TOOLS & COMPONENTS FOR OPEN NETWORKING Feature Matrix CANopen Source Code CANopen Source Code1 Feature Local object dictionary with mandatory entries: 1000.1 2011-03 = available – = not available 1 2 = = The overall number of messages handled by the slave source code is restricted to 255. 1018 Object dictionary: pre-build configuration Maximum number of parallel SDO Servers SDO server protocols2 Maximum number of parallel SDO Clients SDO client protocols2 NMT slave state machine Node guarding Life guarding NMT master (NMT0 message) Heartbeat producer Heartbeat consumer Store/restore (objects 1010/1011) Error behavior (1029) EMCY producer EMCY consumer (object 1028 not supported) Number of PDOs (adjustable) PDO variable communication parameters PDO variable mapping PDO granularity (minimum size of mapped objects) TPDO inhibit & event time RPDO event time (time-out monitoring) PDO SYNC handling Multiplexed PDO SYNC producer RTR for Guarding & TPDO Self-starting device LSS Master LSS Slave Legend: CANopen Source Code1 Add-On Package Mini-Master LSS Slave LSS Master – – – – 1 [e].
TOOLS & COMPONENTS FOR OPEN NETWORKING More Information: www.com/contact .vector.
In addition. Application Areas CANerator CANopen is intended for use together with CANopen Master and Slave Source Code from Vector. Functions CANerator CANopen makes available the following functions: > Configuration of the source code with the aid of a clear display of all #define instructions > Creation and automatic generation of the object directory as source code > Automatic creation of EDS files > Simple management of projects These functions will be described in detail below.CANerator CANopen Generation and Configuration of Source Code CANerator CANopen is a tool for managing source code configuration settings and for creating and generating object directories automatically. This forms the interface between application and CANopen communication and serves to describe the device characteristics. In addition to the actual configuration of the source code. the developer of CANopen devices must also create an object directory. comments are assigned to the settings that explain their purpose and value range. 3/28 Creating the EDS File with the Aid of CANeds . Source Code Configurator CANerator CANopen displays all relevant settings of the source code (#defines) in a tree view. It offers many opportunities for representing necessary device functionality and at the same time accommodating the small resources of a microcontroller. The price for this flexibility is the increased complexity of the development process. With CANerator CANopen. the software developer has available a tool that supports him comfortably in his tasks and significantly speeds up the development process. In addition. An instrumentation of the source code allows the display of only the relevant #define instructions and structures them in problemrelated groups. there is the requirement for reusability and more flexible adaptability of software for entire spectrums of various devices from a manufacturer. Vector’s CANopen Master and Slave Source Code therefore offers a multitude of setting possibilities. Different data types are thus assigned various masks with type-sensitive validators. Features and Advantages The CANopen communication profile distinguishes itself through its broad scalability for use in embedded networks.
Generation of Object Directory Thanks to complete integration of CANeds, all capabilities of this tool are available. These are described in detail in the CANeds product information. With the aid of CANeds, all standard objects of the object directory can be created with drag and drop. In addition, it is possible to define manufacturer-specific objects. The objects are already provided with default values that can be modified if necessary. After the developer has specified the objects, CANerator CANopen displays the structure of the object directory in a hierarchical tree structure. Then variables in the program are assigned to objects. These are ultimately the interface between the protocol-specific part of the software and the application. In addition to the symbolic specification of variable names, the CANerator also supports the specification of physical addresses in order to enable direct access to hardware ports. After the object directory has been created, the corresponding portions of the source code are created automatically. Electronic Data Sheet (EDS) Virtually as a byproduct, the Electronic Data Sheet is generated. This can be processed further and tested with the functions of CANeds.
Project Management CANerator CANopen allows the easy and comfortable management of profiles. When a set of settings has been created, it is stored under its own name. Different profiles of this type can be used in one and the same project for generation. Therefore it is possible, for example, to provide a project with or without debugging information and to change between the profiles with the touch of a button. Another application is the creation of profiles for various device types on the basis of a source code. This simplifies the single source principle. As project documentation, an HTML page is generated, which in addition to general project information contains a list of all objects with their attribute values as well as a list of all settings. ◆
CANerator CANopen in Configuration Mode: All #define Settings can be Edited Clearly.
Measuring and Calibrating via CAN, FlexRay and Ethernet
Overview of advantages > Can be activated/deactivated in production operation > Easy to configure with PC-based tool > Low memory requirement and short execution times based on scaling of the software component to your requirements > Transport layers available for CAN, FlexRay and Ethernet > Compatible with MICROSAR BSW modules (AUTOSAR) Application Areas Automotive in-vehicle ECUs are measured and calibrated with the XCP Protocol (Universal Calibration Protocol) – the successor to CCP (CAN Calibration Protocol). XCP was standardized by ASAM (Association for Standardization of Automation and Measuring Systems), a process in which Vector played a leading role. By clearly differentiating the Protocol Layer and Transport Layer, XCP is able to support many different bus systems: CAN, FlexRay and Ethernet. On the PC side, the CANape tool is used as the XCP master. Its counterpart in the ECU is the XCP slave. This is implemented by the XCP Professional software component. It not only contains all ASAM functional content, but useful extensions as well. You can use XCP Professional together either with a conventional communication stack or in AUTOSAR systems. In either case, it is unnecessary to modify the XCP software. If a software stack by a third-party producer is used, small modifications to the XCP Transport Layer (TL) may be necessary. Vector would be glad to assist you in this area.
Functions XCP Professional contains all necessary functions for communicating with the XCP Master, such as: > Synchronous data acquisition based on DAQ lists > Read and write accesses > Initialization and switchover of the memory area for calibration data > Support of time stamps > Protection against unauthorized writing and reading in memory > Shutoff of XCP in production operation by a single function call > Access protection by Seed & Key support > Synchronous data stimulation (STIM) and Resume mode > Flash and EEPROM programming > Communication mode: Block transfer > Transmission of service request packets > Support of AUTOSAR CRC modules > Bit modification and short download > Configuration by GENy > Generation of an a2l file based on the ECU configuration Synchronous Data Stimulation (STIM) To optimize algorithms and parameters, you can use XCP over the bus system to read a measured signal from the ECU (DAQ) and modify it with a simulation model (e.g. MATLAB). The re-computed value is then written back to the ECU (STIM). Reading and writing are performed synchronously in a predefined time interval (Bypassing).
XCP Professional is available for CAN, FlexRay and Ethernet
Training In the framework of our training program, we can offer you various training events and workshops for XCP in our classrooms or at your business site. For more information on individual training events and dates on the Internet go to: www.vector-academy.com
Resume Mode The Resume mode permits cold-start measurements, e.g. to check ECU behavior in the wakeup phase. This involves activating the XCP stored in the flash memory immediately after a cold-start – even before the application starts. Sending of the measured values begins automatically, and they can be logged for later evaluation. Flash and EEPROM Programming The Vector XCP component is not only able to store measured values in RAM, but also in flash or EEPROM memory. To do this, XCP executes callback functions in which the application could activate the flash algorithms, for example. This gives you the option of individually adapting the algorithms to the flash or EEPROM memory being used. Communication Mode: Block Transfer Block Transfer lets you transfer large quantities of data. This functionality is comparable to that of a transport protocol. The sender segments the data, and the receiver re-assembles them in the correct sequence.
Transmission of Service Request Packets Service request packets let you transmit lines of text. They are stored in program code, and when the program section is executed they are sent to the XCP master where they are displayed. This function is very useful primarily during system development and in debugging. Configuration XCP Professional is configured with the PC-based GENy configuration tool. Compiler switches may be used to deactivate unneeded functions, and this reduces memory loading. When XCP transmission is started, the list of supported functions is communicated to the XCP master via the XCP plug-and-play mechanism. ◆
CANape as XCP Master CANape, the all-round tool for measurement, calibration and diagnostics of ECUs, is the XCP master, while the ECU acts as the XCP slave. The XCP slave allows CANape to access the measured signals and calibration parameters in the ECU with the help of an ECU description file. Values can be displayed or edited in physical units. The key properties of CANape related to measurement and calibration are: > Time-synchronous real-time acquisition and visualization of internal ECU signals with XCP/CCP, of signals from CAN, LIN and FlexRay buses and from external measurement equipment
> Online calibration via XCP/CCP, real-time stimulation via XCP and offline calibration > Flash programming of the ECU via XCP/CCP or the diagnostic protocol > Rapid prototyping for functional development by bypassing a MATLAB/Simulink model with the help of CANape Additional information can be found in the “ECU Calibration” product catalog.
4/0 . A solution can be found for nearly any application. Operating system conforming to the OSEK/VDX standard The use of an operating system helps implement complex flow. You will find detailed information on page 2/10. An operating system based on the OSEK/VDX specification provides even better extendibility. code reviews and other development supporting software tools. Your partner right from the start Vector offers comprehensive support. As supplier of the world’s first certified OSEK/VDX-conformant operating system osCAN. The operating system core conforms to the practicle-proven OSEK/VDX standard. from the beginning of a project until its successful completion.Operating Systems The complexity of software applications is continually growing. MICROSAR OS may include the optional extensions time monitoring and/or memory protection. Operating system conforming to the AUTOSAR standard Vector’s MICROSAR OS is an AUTOSAR-conformant operating system. conducted in Vector’s classrooms or on site. MICROSAR OS is also available as a multi-core operating system for multi-core processors. Vector assists the ECU development process with on-site startups. The related development tasks can only be mastered by modularly structured programming. Vector has many years of experience in implementation. portability and reusability for your application software. control and regulation tasks. since Vector can offer a selection of over 30 different microcontroller platforms and universal tool-supported configurations of the operating system. Training sessions and workshops provide basic information as well as in-depth knowledge for working with the software. In addition.
OPERATING SYSTEMS 4/1 >> CONTENTS osCAN High Resolution Timer TimingAnalyzer 4/2 4/4 4/6 .
Functions As a fully preemptive multitasking operating system. without simultaneously increasing interrupt load. fast and resource-saving operating system core > Short boot times > Stack monitoring at runtime (deactivatable) > Internal fault trace (deactivatable) > Component management for integration of sub-projects > Supplied as source code > Quality process fulfills SPICE Level 3 > Graphic configuration tool for easy configuration of the operating system > Simplified execution time analysis of osCAN applications by supplied TimingAnalyzer > Available for many 8. osCAN is especially ideal when extremely short boot times are necessary. This open standard of the automotive industry provides a foundation for long-term stability and availability. osCAN offers priority-driven task management and a wide variety of synchronization mechanisms. resolutions in the microseconds range are possible. you can implement resolutions higher than 1ms for the timers. It can generate cyclic and singular time intervals as well as behave in an event-driven way. Vector’s many years of experience in developing operating systems and drivers has made osCAN a small and robust operating system core. It is certified to OSEK/VDX specification 2. Application Areas Due to its static operating system architecture. 4/2 .osCAN The real-time operating system based on the OSEK/VDX standard Overview of advantages > Small. In addition to functions defined in the standard. osCAN offers: > Monitoring of stack utilization at runtime > Internal tracing of system calls > Extended error checking at runtime > Clear and concise documentation of the configuration in HTML With the optional High Resolution Timer. Its flexible interrupt strategy makes it possible to use system services even within interrupt service routines. 16. osCAN is small and fast.2. 32 and 64 bit microcontrollers osCAN is a preemptive real-time multitasking operating system with properties optimized for use on microcontrollers. Depending on the controller. and its use is beneficial wherever resources such as memory and processing time are in short supply.
CCCB) > Size: 1–10 kB ROM. This allows the application to be tested even before the availability of first hardware prototypes.vector. execution time and deadline. For more detailed information. Along with the operating system. The analysis is performed for each task and each interrupt with the following parameters: Priority. Many emulators already offer the option of observing application behavior on the operating system services level (OSEK Awareness). ECC1. the sub-applications are integrate into a total application. Some UML and SDL modeling tools give you the option of configuring models for use with an OSEK/VDX operating system. which lets you implement sub-applications simultaneously in parallel processes.com/oscan Additional Services Vector offers you worldwide support related to OSEK/VDX: > Training courses > Design consultation > Customer-specific implementations > Hotline > Software maintenance The scope and form of all services are aligned to your wishes and needs. we offer various training events and workshops for osCAN in our classrooms as well as at the business sites of our customers. your application can be compiled into a DLL and integrated in a network simulation under CANoe. period.vector-academy. LIN or FlexRay. for example.OPERATING SYSTEMS Training In the framework of our training program. the configuration is saved in the standardized OIL format (OSEK Implementation Language). Properties: > Easy to operate graphic user interface > Automatic checking for completeness and consistency > Convenient system scaling > Component management > ORTI support Supporting Tools The TimingAnalyzer design assistant simulates and computes task execution times for you.2 > All conformity classes (BCC1. 16 and 32 bit microcontrollers. please refer to the relevant datasheets. To assure portability. Next. with: > MATLAB/Simulink from Mathworks > TargetLink from dSPACE Related Vector products: > CANoe osCAN Library > TimingAnalyzer > High Resolution Timer ◆ 4/3 Scope of Delivery > Operating system core as source code > Graphic configuration tool (OIL) for Windows NT/2000/XP/ Vista/Windows 7 > Instruction line based generator > Documentation > Sample programs > TimingAnalyzer osCAN conforms to OSEK/VDX specifications > OSEK/VDX-OS 2. For more information on individual training events and dates please visit: www.3 > OSEK/VDX-COM 2.2. CCCA. The configuration tool offers component management. This enables short development times and spatially separate developments. Configuration An easy-to-use graphic configuration tool lets you define all operating system resources before compiling. depending on platform and configuration Availability The real-time operating system osCAN from Vector is available for many commonly used 8.2 > OSEK/VDX-OIL 2. This is possible. . ECC2. you get protocols and drivers for CAN.com Complete solution from Vector Vector provides you a completely tuned solution for developing ECUs. For more information on the Internet go to: www. osCAN supports the ORTI interface required for this. BCC2. With the help of the CANoe osCAN Library. The graphic user interface offers clear and concise visualization of system behavior.
◆ 4/4 Alarms and Tasks . It may range from 100 ns to 100 μs depending on the microcontroller.High Resolution Timer Improve performance with high-precision timers for operating systems An important property of operating systems is the precision of alarms. If timer resolutions with a higher precision than 1 ms are required. Hardware requirements The High Resolution Timer can be used on all microcontrollers which have a free-running timer. Functions “Collective” processing of several consecutive alarms can be controlled by defining a minimum interval between timer interrupts. The clock speed at which the hardware timer is operated should be adjustable so that the desired level of accuracy is achieved. When a counter reaches a preset alarm value. this in turn affects the resulting interrupt load. Resolutions in the microsecond range are possible depending on the controller used. The alarm mechanism of an OSEK/VDX or AUTOSAR operating system is based on counters which are incremented by either software or hardware timers. especially when several alarms with similar intervals expire almost simultaneously. This reduces interrupt load. Application areas The High Resolution Timer is designed for applications requiring high-precision timers but in which additional interrupt loads are unacceptable. The precision of the alarm time depends only on the resolution and clock frequency of the hardware timer. the High Resolution Timer mechanism can achieve these enhanced precisions without simultaneously increasing interrupt load. a predefined action is executed. Configuration The High Resolution Timer is configured using the configuration tool for the Vector operating systems. The typical time resolution of such timers is 1 ms. An interrupt is only triggered when an alarm actually becomes due. Features and advantages The High Resolution Timer for the osCAN and MICROSAR OS operating systems permits high-precision alarms with low system interrupt load (depending on hardware). This tool is used to adjust the prescalers according to the clock frequency of the microcontroller. The timer must also be able to trigger an interrupt when its value matches a user-definable compare value (compare-match).
OPERATING SYSTEMS 4/5 .
The simulated schedule can be examined by zooming in and measuring time intervals. It gives the application engineer a better understanding of program processing in the ECU. the best algorithm is selected for a given data record. A special algorithm considers mutual interactions resulting from use of the “resource” operating system service. Processor use is computed and output as a percentage. period. Properties and Advantages The TimingAnalyzer simulates scheduling tables and computes schedulability. Functions In the analysis. consist of tasks and interrupt service routines (ISR).TimingAnalyzer Schedulability analysis/Trace visualization The foundation for designing real-time systems is an analysis of the schedulability of tasks (schedulability analysis). the TimingAnalyzer studies the timing of both tasks and ISRs. execution time and deadline. leading to an efficient design that conserves on hardware resources. Special functions > Schedulability analysis > Graphic simulation of schedules > Import and display of emulator traces Analysis example in the TimingAnalyzer . Various algorithms from scheduling theory may be selected. In the default setting. The TimingAnalyzer is a tool for integrating familiar software components into a runnable system. The analysis is performed for each task and ISR with the information: priority. such as the OSEK/VDX operating system or AUTOSAR OS. Schedulability analysis shows whether a task or ISR could miss its deadline when all circumstances are taken into considerations. Processor use is optimized by modifying calibration parameters. The graphic representation simulates a possible task switching sequence. 4/6 By using the TimingAnalyzer you can avoid the difficult and timeconsuming work involved in determining worst case timing situations. which is usually done by testing. It also considerably reduces the risk of creating unreliable systems. Systems that employ a real-time operating system. Bitmaps of the graphic diagram can be saved for documentation purposes. In the TimingAnalyzer you can input the time with which a task or ISR occupies the specific OSEK resource. The time savings in terms of program creation and the test phase translate into cost savings as well. A graphic diagram offers an intuitive overview of the timing.
Availability The TimingAnalyzer is available in combination with the OSEK/VDX-conformant operating system osCAN as well as the AUTOSAR-conformant MICROSAR OS. Application Areas The TimingAnalyzer is an efficient tool for all development departments that use real-time operating systems. since data input and calling of the TimingAnalyzer are performed directly in the configuration tool.OPERATING SYSTEMS Data Import Besides manual data input. the data may also be read-in from the configuration file of the operating system. Special attention was given to supporting OSEK/VDX and AUTOSAR real-time operating systems and their applications. This simplifies handling. 4/7 Scope of Delivery > Graphic analysis tool for Windows NT/2000/XP/ Vista/Windows 7 > Documentation in electronic form > Sample files ◆ .
Green Hills. MPC56x MPC55xx. IAR. Green Hills Green Hills.com/contact . Tasking. Tasking GNU ST10 STR9 Texas Instruments MSP 430 TMS 320 TMS 470 TMS 570 IAR Texas Instruments Texas Instruments. Metrowerks ML665S Renesas Electronics (NEC/Renesas) 78kO H8 tiny H8S H8SX M16C M32C M32R IAR Renesas Renesas Renesas Renesas. Renesas. Metrowerks Keil.EMBEDDED SOFTWARE Wide Availability of osCAN Supported Microcontrollers and Compilers Controller Altera Excalibur NIOS II ARM ARM7-TDMI Cortex M Atmel AT91 AVR32 Freescale 68HC08 68HC12. Metrowerks Cosmic. IAR. IAR OKI Cosmic Cosmic. IAR. Green Hills Texas Instruments Green Hills More Information: www.vector. Renesas Renesas. Green Hills. IAR IAR IAR. GAIO. MPC56xx S12X Fujitsu 16FX 16LX FCR4 FR30. Tasking. Green Hills Green Hills Green Hills IAR SJA20xx OKI ML67 Green Hills.3 2011-12 Compiler Controller Microchip Compiler Green Hills GNU. GAIO Renesas. TaskingVX TaskingVX DIABDATA Wind River. FR60 MB86 Infineon C167 Tricore XC16x XC2000 Intel PXA27x V2. Tasking GAIO. TaskingVX GNU . Green Hills. Metrowerks DIABDATA Wind River. S12 MAC71xx Mcore MPC55x. FR50. Metrowerks Green Hills DIABDATA Wind River DIABDATA Wind River. Tasking Keil. TaskingVX dsPIC30 PIC18 PIC24 Microchip Microchip Microchip Green Hills ARM NXP LPC2XXX SAF7780 Green Hills ARM. IAR Fujitsu Fujitsu Green Hills Fujitsu Green Hills R32C R8C SH2 V850 STmicroelectronics SPC56xx Keil.
com/contact . TX39.vector. TX49 TX19A Vector CANoe osCAN Emulation Compiler Toshiba Green Hills Toshiba Microsoft VisualC More Information: www.EMBEDDED SOFTWARE Controller Toshiba TLCS-900 TX19.
Flashing CANopen ECUs Vector also offers Flash Bootloaders for the special requirements involved in flashing CANopen ECUs. systems for downloading software to ECUs are used in all phases of ECU development. Meanwhile. special cryptographic methods are used in security-critical ECUs. To save on resources. when the ECU is mounted at a hard to access location in the vehicle. EEPROM Emulation Module (EepM) The EEPROM Emulation Module (EepM) lets you efficiently store nonvolatile data of any desired length in program or data flash memory. and so it requires more extensive software. Vector offers optimized solutions for the Flash Bootloader and flash tools. This optional extension of the Flash Bootloader that adds a security component provides maximum security and the flexibility to set the security level required by the automotive OEM. it can also be reprogrammed with ECU software. A special LIN Flash Bootloader is available for LIN Slave ECUs. Since XCP/CCP programming is generally used in the development phase. they reduce transmission times drastically. Since the Request/Response method provides inadequate protection from a technical security perspective. even if it does not originate from the automotive OEM. In particular.Flash Memory Programming Today. Vector can adapt them to your platform in the context of project work. FlexRay. To master the many different data and diagnostic exchange formats. the module can be used by either the application or the Flash Bootloader. 5/0 . Vector offers a number of software solutions to meet various requirements: > Flash Bootloader for CAN. ODX and ODX-F have become established at some automotive OEMs as a standard data format for ECU programming. Suitable data compression methods can be used to transport the increasing amounts of data more quickly on data buses. Programming via XCP/CCP The use of XCP or CCP is an alternative to reprogramming with the Flash Bootloader. MOST or Ethernet utilizing a diagnostic protocol (UDS or KWP2000). Security requirements related to software manipulation pose the greatest challenge to the software. Data compression Automotive electronics is continuously becoming more complex. unlike the Flash Bootloader. security aspects play a subordinate role here. FlexRay. Vector offers authoring and flash tools for specific use cases in its CANdelaFlash and CANditoFlash products. The module is called directly by the application. Security component ECUs can only be reprogrammed if the ECU has been unlocked beforehand with the help of a request/response (Seed/Key) method. the Flash Bootloader offers the advantage of updating ECU software without needing to remove the ECU. MOST and Ethernet > Flashing via CCP/XCP > Option for the Flash Bootloader: Security component > Option for the Flash Bootloader: Data compression > PC-based flash tool Flash Bootloader The Flash Bootloader lets you program ECUs with new software within an in-vehicle network. As soon as the ECU is unlocked. LIN. This results in the following capabilities: > Reprogramming during the development phase > End-of-line programming > Software updating in the Service area (After Sales) Reprogramming is performed via CAN. Flash tools Different data and diagnostic formats are used by different automotive OEMs for programming ECUs. This variant is primarily used to optimize ECU parameters.
FLASHING 5/1 >> CONTENTS Flash Bootloader Option “Security (Crypto)” Data Compression Option EEPROM Emulations Modul (EepM) Flashen with CCP and XCP CANdelaFlash vFlash 5/2 5/4 5/5 5/6 5/8 5/10 5/12 .
LIN. MOST and Ethernet bus systems. the OEM Download Manager loads the flash driver from the bus system to the ECU’s RAM memory if needed. After verifying access authorization. the Bootloader starts reprogramming via the OEM Download Manager. it can be repeated at any time. Then it erases the old ECU software and reprograms the flash memory with the new data it receives over the bus system. The Flash Bootloader consists of these components: > Bootloader including OEM Download Manager and communication stack > Flash driver (HIS device driver) Reprogramming is executed with a flash tool such as vFlash from Vector. The Flash Bootloader is continually coordinated with the OEMs. FlexRay. LIN. Due to its low memory requirement. without having to remove the ECU > Low memory requirement in the ECU > Available for most OEMs and many microcontroller platforms > Security and data compression options available > Proven flash solution based on over 10-years of use in numerous development and production projects Application Areas The Vector Flash Bootloader is a universal and compact solution for quick. and conforms to specifications of automotive OEMs. MOST and Ethernet . Functions The flash download is executed according to OEM requirements using either the KWP2000 or UDS diagnostic protocol. Scripts needed for the Vector flash tools are supplied with the Flash Bootloader. It then checks whether a flash request or valid application software exists. The Flash Bootloader permits reprogramming on single or multiprocessor platforms. It is available for CAN. If the ECU is to be reprogrammed. FlexRay. the Bootloader is stored in a protected ECU memory area.Flash Bootloader ECU reprogramming via CAN. the Bootloader is also well suited for microcontroller platforms that have limited resources. 5/2 Flashing over CAN. FlexRay. it is started as the first software instance in the boot phase. The Bootloader contains the communication stack needed for the specific bus system. LIN. It includes a Multiple Memory Manager for programming different memory types connected either internally or externally. MOST and Ethernet Overview of Advantages > Efficient and reliable reprogramming of ECUs. After a reset. efficient and reliable reprogramming of ECUs during development. > The flash procedure with the OEM Download Manager In the ECU. If the flash procedure is interrupted. while in production or while in service.
vector. adapting it to the specific requirements of your application. > Flash driver The Flash Bootloader includes a flash driver that matches the hardware platform.” Options > Security: For ECUs with sensitive vehicle data that needs to be protected from unauthorized manipulation > Data compression: For quick re-programming of ECUs For detailed information on these options. Version 1.com Telephone: +49 711 80670-400 > Bus-specific communication stack The Bootloader communicates with the flash tool via the busspecific communication stack. please refer to the datasheet in the Diagnostics catalog. AUTOSAR communication modules from Vector are used for FlexRay and Ethernet/DoIP. All Vector flash drivers have low memory requirements. For more information. please refer to the relevant datasheet on the following pages. ◆ 5/3 Configuring flash blocks with GENy . a specially optimized CAN driver with Transport Protocol (ISO-15765) is used to economize on valuable resources. For more information go to: www. Further modifications and extensions are possible using callback functions in the Bootloader Application Layer. It contains system-based routines for reliably erasing and programming nonvolatile memory chips.com/fvd/ or contact us at: E-mail: embedded@de. this also applies to LIN as well. you can obtain the userfriendly vFlash tool from Vector. For the CAN bus. and they conform to the HIS standard “Functional Specification of a Flash Driver. A Network Services Library for MOST is used to flash over MOST.vector. Its flexible approach lets it support various flash specifications for a wide variety of automotive OEMs without requiring modifications by the end user.3.FLASHING Contact and Availability The Flash Bootloader is available for many commonly used microcontrollers and in OEM-specific variants. Configuration You configure the Bootloader with the GENy configuration tool. Scope of Delivery > Bootloader as configurable C source code > Flash driver for your specific hardware platform > GENy configuration tool > Flash scripts for controlling the download process > Documentation Flash Tools To reprogram one or more ECUs.
the Flash Bootloader may use simple or OEM-specific Seed/Key methods. > Validation and authentication of the download process by signatures per security classes C and CCC. in the case of ECUs containing sensitive vehicle data such as an engine immobilizer function or odometer. you can also obtain extended Seed/Key methods for ECU access protection. integrated in the Bootloader > Tool HexView for efficient computation of the signatures > Documentation ◆ 5/4 Generating. Functions Option Security for the Vector Flash Bootloader meets the requirements of HIS “Security Module Specification. In the ECU. During ECU development. symmetrical key.” The following modules are available: > Symmetrical data encryption based on the Advanced Encryption Standard (AES). class AAA > Computation of Hash codes with Hash function SHA-1 (alternatively: RIPEMD-160. it is convenient to use the supplied HexView tool for signature computation.1. and it is verified in the ECU. qualitatively highend cryptographic functions from the company Cryptovision. Class CCC: The signature is generated externally by the RSA method with a confidential private key. Version 1. MD5). Upon request. Class C: The signature is generated in the flash tool by the H-MAC method with a confidential. The Hersteller Initiative Software (HIS. transmitting and verifying a digital signature .Flash Bootloader: Option “Security (Crypto)” Data encryption. The option contains secure. “Manufacturers Software Initiative”) has specified cryptographic routines with standardized interfaces in scalable security classes for this purpose. Application Areas Option Security for the Vector Flash Bootloader lets you efficiently prevent flashing and unauthorized execution of protected software in the ECU. the CANdelaFlash tool would be used to generate the entire ODX-F container. the Option Security (Crypto) modules are needed to implement extended security measures. In production usage. However. validation and authentication during flash programming Overview of Advantages > Protection against unauthorized ECU access > Secure downloads > Efficient program execution monitoring by signature checking The Vector Flash Bootloader lets you program ECUs over a bus system without having to remove the ECU. This is sufficient for most ECUs today. the signature is opened with a public key and is verified. To prevent unauthorized access during this process. SHA-256. Scope of Delivery > Configurable C source code.
where the rate actually attained depends on the flash data itself. Savings are maximized when flashing large quantities of data (e. the Bootloader’s OEM Download Manager calls the decompression function. the flash tool must communicate this via diagnostics to the Bootloader in the ECU. Implementation in the Bootloader’s decompression module is very efficient in terms of execution time and memory. in the Infotainment area). After receiving the flash data. Compression and subsequent decompression of the flash data is recommended to reduce download time. as in end-of-line programming. and then it programs the decompressed data in flash memory via the Multiple Memory Manager. Compression is performed with the supplied tool HexView. Compression also offers many benefits when short cycle times are specified. Functions The compression method used in this module enables a compression rate of 40–60%.FLASHING Flash Bootloader: Data Compression Option Fast Flash Programming Overview of Advantages > Reduced download times in flashing > Efficient decompression module for the ECU > Offers support in data compression > Bus system independent With the Vector Flash Bootloader you can program ECUs via a bus system without having to remove the ECU. Compression of the flash data saves time even for small quantities of data.g. afterwards the flash tool transmits the compressed data. It utilizes an optimized LZ77 method and is especially well suited for use in automotive ECUs. Application Areas Some automotive OEMs specify the use of data compression in their flash procedures to accelerate the flash procedure at a constant baudrate. Scope of Delivery > Configurable C source code. integrated in Bootloader > Tool HexView for compression of the flash data > Documentation ◆ 5/5 Compression and decompression of flash data . If compressed flash data needs to be transmitted. The data compression option of the Vector Flash Bootloader lets you efficiently compress all of your flash data. It is available on all microcontrollers for which a Bootloader is available.
EEPROM Emulation Module (EepM)
EEPROM Emulation in Flash Memory
In recent years, flash memory has become more cost-effective and faster than conventional EEPROMs. New microcontrollers are often offered without EEPROM memory and just have a larger internal flash memory. Since writing to flash memory, unlike EEPROMs, is not by the byte but by the page, it is only possible to achieve optimized utilization of the flash memory with the help of an EEPROM emulation. Overview of Advantages > Usable for external and internal flash > Usable for data and program flash > Conserves resources and optimizes flash lifetime > Possible to use EEPROM emulation module together with the Vector Flash Bootloader
access the stored data by identifiers that are predefined or flexibly defined at runtime. Special Functions The EEPROM Emulation module is configurable and so it can be adapted to the requirements of the application. It enables: > Simultaneous emulation of multiple EEPROMs > Integration of different flash hardware
Application Areas Flash memory cannot be erased or written in the same way as conventional EEPROMs. EEPROM emulation in flash memory makes it possible for an application to store changed nonvolatile data in a flash memory, just as in a conventional EEPROM. Functions The Vector EEPROM Emulation Module (EepM) manages predefined flash areas by taking all hardware-specific constraints into consideration. Reading and writing of changeable nonvolatile data via the EepM is fully transparent to the application. It is easy to
Differences between EEPROMs and Flash Memory Flash memories cannot be written byte-by-byte. Their smallest writing unit, known as a page, extends over a number of bytes. A page cannot be overwritten directly. First, it must be erased together with all of the pages of a sector (smallest erasing unit). The page length and sector length are hardware-dependent, and sector lengths may also vary within a flash memory. Efficient Structuring of Nonvolatile Data Essentially, the use of a flash memory requires that the data to be stored is defined in so-called records. They are addressable by unique identifiers, and besides the stored data they also contain management information. This information assures quick and reliable read access to valid data. The application either defines the length of a record either statically during software configuration or dynamically at runtime, depending on the configuration.
Software architecture of the EepM
Contact and Availability Vector offers EEPROM Emulation Modules for a number of hardware platforms with different internal or external flash memories. You will find additional information on the Internet at: http://www.vector.com/vi_eepm_availability_en or upon request E-mail: firstname.lastname@example.org Telephone: +49 711 80670 400.
Reliable Access In addition to the nonvolatile data, control information is stored in a record and includes a Cyclic Redundancy Checksum (CRC). This information assures that the data remains consistent with each access. If the application calls up nonexistent data, the EepM generates an error message. Optimizing Resources and Lifespan During configuration the reserved flash area is partitioned into two blocks. The EepM sequentially writes new or updated records into the currently active block. When this block is full, the EepM completely erases the inactive block fully before it copies the still valid records of the active block into it. After an integrity check, the inactive block becomes the active block. This alternating and consistent use of two blocks optimizes the lifespan of the flash memory. The EepM can emulate multiple EEPROMs within a flash simultaneously using predefined context pointers. If a Vector Flash Bootloader is integrated into the ECU, the context pointers make it possible to use the EEPROM Emulation module from the Flash Bootloader. Since all interrupts are blocked during access to flash memory, EEPROM management tasks should be performed at a non-critical time for the application. We would be glad to offer you consultation in system design.
Configuration The EepM is configured via a header file. Scope of Delivery > C header files and source code > Makefiles and sample programs > Documentation/operating instructions/Readme file Optional Services > Consultation in system design and integration in the ECU > We supply HIS flash drivers > We will extend standard modules according to your needs > Hotline, special workshops and training courses on the topic of embedded software ◆
Resource optimization by use of EepM from the Vector Flash Bootloader
Flashing with CCP and XCP
Using the CCP/XCP protocol for flash programming
Advantages > Calibration and reprogramming with the same software component > Use CANape as a flash tool > Reset-safe solutions are available The CAN Calibration Protocol (CCP) – and its successor, the Universal Measurement and Calibration Protocol (XCP) – are ASAM Standards that are used to measure and calibrate internal ECU parameters. XCP offers several different physical interfaces such as CAN, FlexRay, Ethernet, USB and SPI/SCI. The calibration tool CANape from Vector supports all of these interfaces. Application areas Flashing via CCP and XCP is primarily used to update calibration data and parameter data in the calibration process. After a change has been made to the data in the calibration tool, the new data is written to the ECU’s flash memory via the bus system. First, a flash kernel (see illustration, left) is transferred to the ECU, is written into RAM and is started by the application. Besides containing the CCP and XCP protocols for communication, it also contains routines for erasing and programming flash memory. The subsequent download of ECU data is handled by the kernel, and the data is transferred to the flash chip. This achieves an especially space-saving solution.
Less widely used but technically feasible is the option of replacing the entire application by flashing via CCP and XCP. Failsafe reprogramming Unfortunately, the use of a flash kernel has one disadvantage: If the data transfer is interrupted during programming, this might lead to a catastrophic failure of the ECU. This can be remedied by using a CCP or XCP bootloader (see illustration, right). It is permanently stored in a protected memory area. The bootloader is always called after the start, and it checks the application. The application is not started unless it is valid and complete. A flash abort always causes the bootloader to assume control, and the flash process can be resumed at any time. Tool support The flash download is executed by CANape.
Flashing via XCP using a flash kernel
Flashing via an XCP bootloader
FLASHING 5/9 .
Star12. In general CAN. IAR CAN. LIN CAN CAN CAN CAN CAN. IAR DIABDATA Wind River. Star12x. 56x. LIN. IAR Renesas Renesas (NEC). LIN. Tasking Tasking CAN CAN. FlexRay M32R R32C R8C SH2 V85x STmicroelectronics ST9 ST10 STM8a Fujitsu Fujitsu Fujitsu GNU CAN CAN CAN CAN Texas Instruments TI OMAP 59xx TMS320 TMS470 TMS570 Tasking GNU. LIN CAN H8S M16C M32C Metrowerks Cosmic.1 2010-10 Compiler Available for  Controller Compiler Available for  Renesas Electronics (NEC/Renesas) VisualDSP CAN 78k0 78K0R IAR IAR CAN.MX25 MAC71xx.com/contact . Metrowerks (Hiware) Cosmic. FlexRay. 5200 MPC 55xx. MAC72xx MPC 55x. Tasking Keil. FlexRay Microchip C30 Microchip C30 Microchip. Metrowerks (Hiware) GNU ARM. ARM CAN CAN CAN CAN. LIN CAN CAN CAN CAN CAN CAN CAN CAN CAN. FlexRay GNU Tasking Cosmic CAN CAN CAN IAR IAR Renesas Renesas. Green Hills. Please find the list of supported OEMs in the separate datasheet. MCS12xE i.EMBEDDED SOFTWARE Wide Availability of Flash Bootloader and EepM Supported Microcontrollers and Compilers Controller AnalogDevices BlackFin Atmel AVR AVR32 Freescale DSP56F83xx HC08. The Flash Bootloader is available for a great variety of OEM-specific flash processes. Metrowerks DIABDATA Wind River CAN CAN. 56xx Fujitsu 16FX 16LX FR60 Jade Infineon C16x (external AMD-Flash) Tricore XC16x XC2000 Microchip dsPIC24 dsPIC33 PIC18 National CR16 V2. FlexRay CAN CAN Toshiba TLCS900 TX19 TX49 Toshiba Green Hills Green Hills CAN CAN CAN Texas Instruments Texas Instruments Texas Instruments. IAR Renesas IAR Renesas.com) if your controller is not on the list or if you need additional support for a not listed bus system. IAR CAN More Information: www.vector. Hi-Tech CAN CAN CAN. MCS08 HC12. IAR. Ethernet and MOST can be supported. IAR Renesas. LIN  Please contact Vector (embedded@vector. ARM Texas Instruments.
EMBEDDED SOFTWARE More Information: www.com/contact .vector.
g. Checking whether the session is valid for the ECU that has to be programmed. CANdelaFlash is a software tool designed to manage these requirements. idle-speed control. For example.0 Management of Flash Data and Generation of ODX Flash Containers for an Assured Process Properties Overview > Import and Export of ODX Flash Containers > Modularization of flash data > Management of software revision levels and part numbers > Administration of data for Flash ROMs > Reuse of diagnostic descriptions from CANdelaStudio > Can be used by both vehicle manufacturers and suppliers > Comfortable user interface Application Areas Today the development process for an ECU is very complex. the organization of a CANdelaFlash document is shown in a tree view. In the future the flashing of ECU sub-functionalities will also come to the forefront. The large number of ECUs that are networked together in the vehicle. Functions CANdelaFlash supports the import and export to the standardized ODX format completely. In particular it supports the development process with other Vector products such as CANdelaStudio. in future all ECUs will have a flash capability. country variants. > User-friendly acquisition and management of binary and hexadecimal data for Flash ROMs (e. ODX Flash Containers can thereby be prepared at an early stage in the development process.CANdelaFlash 2. CANdelaFlash should be used wherever process-assured flashing of ECU functionalities (full or partial) is required. import of source files in “Intel Hex” and “Motorola S-Record” formats) 5/10 New Functions of Version 2. While previously just a few ECUs were “flashable” in the vehicle.0 Data Extraction Plugin Interface > Interface for automatic extraction of data out of hex files at import time or interactively using the menu via OEM specific plug-in Base Session > Optional definition of session defaults for a project Session Wizard > Simple creation of flash sessions through configurable Session Wizard > Mask out unused or read only elements in the user interface Process-assured generation of ODX Flash Container . and their growing complexity and amount of programmable data will require management of the flash data for an assured process. These ODX Flash Containers have become a standard for modern flash tools used in development and production. Another advantage of CANdelaFlash is that it supports modularization of flash data.g. post-flashing of individual ECU functionalities (gear shift programs. and most entries are made via easy-to-use tables with intuitive input masks. etc. e. Functions at a Glance: > Assignment of software revision levels and part numbers > Assignment of the various software revision levels to specific ECUs in the vehicle > Identification of valid target ECUs. CANdelaFlash offers a simple and easy-to-use interface. It can be implemented in both ECU development at a supplier and in test vehicle or preproduction development at the vehicle OEM. CANdelaFlash fits seamlessly into existing tool chains.).
The data blocks reference the flash data (reusable in different sessions) and they specify the segments of flash data for upload/download. > Memory layouts: Description of the memory layouts of several ECUs > Flash classes: User-defined organization of sessions in any desired number of flash classes > Flash data: Database of reusable flash data ◆ 5/11 Flash data management with CANdela Flash: Structure of the CANdelaFlash data . copy.FLASHING > Use of templates for new CANdelaFlash documents > Creation and editing of sessions and data blocks > User-friendly editing of the segments of a data block including extensive consistency checks > Grouping of sessions into so-called Flash Classes > Cut.1 data format > Import/export of embedded flash data from/to ODX > Creation and editing by authors.cdd files) > Base Session: Optional definition of session defaults for a project > Sessions: Session with list of data blocks. This is a list of jobs for upload/ download (initial programming. and brief descriptions > Interfacing to external tools by user-defined actions > Plug-In interface for linking customer-specific security DLLs for CRC and signature calculation > Support of customized user settings > Reuse of diagnostic data (from CANdelaStudio) > Detailed recording of program sequences (Output Window) > Read and write of PDX archives (Packaged ODX) > Expanded format checking in attribute masks via specification of regular expressions in the template Structure of the CANdelaFlash Data The management and the acquisition of flash data are done comfortably via the user interface in the following structure: > Flash description: Reference to multiple ECUs (CANdelaStudio ECU-specific descriptions. reprogramming. revision entries. *. and paste functions for objects of the CANdelaFlash document > Searching of the CANdelaFlash database for objects by their names > Import and Export of the CANdelaFlash document into ODX 2. partial reprogramming).0 and ODX 2.
Flash projects contain all relevant settings and reference the data files to be programmed. If the focus is on a process-safe exchanging of flash configurations.g.vFlash 1. vFlash may be used either interactively or by remote control. either individually or in an ECU network group. In this case. the flash projects may be exchanged in the Pack&Go format. at a laboratory vehicle or in the vehicle. e. Because of its flexible approach. If the focus is on flexibility in changing the flash data. the user loads a project and starts programming by the push of a button. Last but not least. the vFlash tool’s very fast transmission rate significantly reduces flash times in the case of large amounts of data. vFlash is designed to process very large quantities of data. In this case. vFlash lets users flash in the laboratory. vFlash can be executed from the command line or controlled via a C programming interface. at programming stations. You can transmit 4 GB or more – or segments of very large binary data sets – quite easily. In remote control mode. Motorola-S and binary format > Flash programming based on ODX-F > Flashing of compressed data > Supports interactive flashing (GUI) as well as batch processing (C API) > Interacts perfectly with Vector Flash Bootloader vFlash is a very easy-to-use tool for programming one or more ECUs. as part of an automated software build process. it can support the different flash specifications of a wide variety of automotive OEMs without requiring modifications by the end user. vFlash is very simple and does not require any expert knowledge to use – the user interface is tailored for flashing tasks. Application Areas vFlash is designed for all users at automotive OEMs and suppliers whose tasks include (re-)programming of ECUs. the flash project remains unchanged. In the interactive mode.1 (Re-)Programming easily and quickly – over CAN or Ethernet (DoIP) Overview of Advantages > Extremely easy to reprogram ECUs over CAN or Ethernet (DoIP) > Preconfigured flash projects can be exchanged readily – all relevant data is packed in one file > Flash projects are easy to create using templates > Supports different protocols and flash sequences (based on the specifications of many different automotive OEMs) > Direct “native” programming of data in Intel hex. the referenced data files can simply be exchanged in background. It supports ECU programming over CAN and over Ethernet (DoIP). all relevant settings together with the data files are packed in an archive file. Functions vFlash utilizes flash projects to save and exchange the configuration to program individual ECUs. 5/12 Flash process with vFlash .
The user creates flash projects based on flash templates. A flash template defines the diagnostic services and presettings that are relevant to the flash process for a group of ECUs of a specific automotive OEM (e.g. for a vehicle platform). In practice, the flash specifications of automotive OEMs differ enormously, not least of all due to the differences in diagnostic protocols and in-house flash standards. The advantage of flash templates concept is that the differences described above remain largely hidden from the user. The reference flash process from Vector is also available as source code (C#). This lets end users modify the flash sequence themselves as necessary. All that is needed for this is Microsoft Visual Studio for C#; the Express Edition can be obtained from Microsoft free-of-charge. Transfer rate Programming of 100 kByte data in 6.3 s (16.3 kByte/s) into an idealized reference ECU over CAN at 500 kBit/s with STmin = 0, BS = 0
OEM-specific flash templates Vector offers prepared flash templates for a number of different automotive OEMs. Please contact us at: www.vector.com/contact System Requirements
Windows XP (32-bit) Processor RAM PC with min. 1.6 GHz 1 GB Windows Vista (32 bit) Windows 7 (32/64 bit) PC with min. 1.6 GHz 2 GB
5/13 Supported Hardware > XL interface product family (e.g. CANcardXL, CANcardXLe, CANcaseXL)
vFlash User Interface
Seminar or Workshop? Vector offers seminars and workshops on Vector software tools as well as the latest bus technologies and protocols at Vector Group locations worldwide. VectorAcademy seminars serve to communicate theoretical basics, while workshops distinguish themselves through their applicability, practical examples, and exercises. Modularity Trainings are partly constructed of several independent, one-day modules designed to follow one another. Beginners and advanced users can adjust their individual training program to suit their own needs. You will find the latest information on current dates, additions to the training offerings, and information about registration of the Vector Group at www.vector-academy.com.
Customer-Specific Trainings Additionally, we offer customized training courses, where we combine or expand the contents according to your needs. If desired we can also conduct all training courses at your company site. We would be glad to provide you with a quotation based on your specific needs. Please contact our training consultants: Vector Informatik: email@example.com Vector Consulting Services: firstname.lastname@example.org Vector CANtech: email@example.com Vector Scandinavia: firstname.lastname@example.org Vector France: email@example.com Vector Japan: firstname.lastname@example.org Vector Great Britain: email@example.com Vector Korea: firstname.lastname@example.org The Training Team Our training team consists of experienced engineers, who enjoy sharing their experience and knowledge base. A continuous flow of information between trainers and development departments ensures that the training courses we offer reflect current trends and developments. Premises We conduct our trainings in generously appointed and modern classrooms, equipped with state-of-the-art training technology and powerful workstations, running the latest development, analysis, measurement, and diagnostics software. Excercise hardware and demonstration objects complete the working environment.
Germany 6/8 .
.DIRECTIONS TO VECTOR USA and Great Britain Subsidiaries: Vector CANtech Inc. Vector GB Limited 6/9 .
VecScan AB 6/10 .S..France and Sweden Subsidiaries: Vector France S.A.
.DIRECTIONS TO VECTOR Japan and Korea Subsidiaries: Vector Japan Co. Ltd. 6/11 . Vector Korea IT Inc..
. Ltd. Vector Informatik China 6/12 .India and China Subsidiaries: Vector Informatik India Pvt.
DIRECTIONS TO VECTOR 6/13 .
Luxembourg Vector France 168.: +91 20 2587 2023 Fax: +91 20 2587 2025 Sweden. Denmark.com F Get Price Quote . Mexico Vector CANtech.: +46 31 764 7600 Fax: +46 31 764 7619 United Kingdom & Ireland Vector GB Limited Rhodium. Sutar Icon Sus Road Pashan Pune 411021 INDIA Tel. CHINA Tel. Sunyoung Center No. Inc. B90 8AS UNITED KINGDoM Tel. Belgium. MI 48375 USA Tel. Suite 550 39500 orchard Hill Place Novi.: +49 711 80670-0 Fax: +49 711 80670-111 France. 3rd floor. Canada.R.: +86 21 6432 53530 Fax: +86 21 6432 5308 F www. Finland. Guro-gu Seoul 152-848 REPUBLIC oF KoREA Tel. 1406 Mario Tower 222-12 Guro-dong. Shinagawa-ku Tokyo 140-0002 JAPAN Tel.: +81 3 5769 7800 Fax: +81 3 5769 6975 Korea Vector Korea IT Inc. 18F 2-3-12 Higashi-shinagawa. Ltd. 24 70499 Stuttgart GERMANY Tel. 398 Jiangsu Road Changning District Shanghai 200050 P.: +1 248 449 9290 Fax: +1 248 449 9704 Japan Vector Japan Co. Central Boulevard Blythe Valley Park Solihull. Ltd. Seafort Square Center Bld. 4/1/1/1. Iceland VecScan AB Theres Svenssons Gata 9 41755 Göteborg SWEDEN Tel.: +44 121 50681-50 Fax: +44 121 50681-69 China Vector Informatik GmbH Shanghai Representative Office Unit 1701.vector.Your contact Germany and all countries not named below Vector Informatik GmbH Vector Consulting Services GmbH Ingersheimer Str.: +33 1 4231 4000 Fax: +33 1 4231 4009 USA. Birmingham West Midlands. Norway.: +82 2 8070 600 Fax: +82 2 8070 601 India Vector Informatik India Prv. Boulevard Camélinat 92240 Malakoff FRANCE Tel..