ETAS Virtual ECU V2.0 VRTA Device User Guide

Transcription

1 Virtual ECU V2.0 VRTA Device User Guide

2 Copyright The data in this document may not be altered or amended without special notification from ETAS GmbH. ETAS GmbH undertakes no further obligation in relation to this document. The software described in it can only be used if the customer is in possession of a general license agreement or single license. Using and copying is only allowed in concurrence with the specifications stipulated in the contract. Under no circumstances may any part of this document be copied, reproduced, transmitted, stored in a retrieval system or translated into another language without the express written permission of ETAS GmbH. Copyright 2011 ETAS GmbH, Stuttgart The names and designations used in this document are trademarks or brands belonging to the respective owners. Document V1.1 R03 EN

3 Contents Contents 1 Introduction Definitions and Abbreviations Conventions Sending / Receiving the values through VRTA Monitor Connecting the VRTA Monitor Running the Virtual ECU using ISOLAR-EVE Sending the s (s) Receiving the values through polling / hooking (Events) VRTA PORT Device VRTA Port Overview Access Synchronizable VRTA Port Using C++ Methods s InjectedPortpinDirection InjectedSetPinMode Events CurrentJob DETErrors VRTA DIO Device VRTA DIO Overview s Write Channel Flip Channel Write Port Write Channel Group Events Read Channel Channel Written DET Errors Port Written Channel Group Written VRTA PWM Device VRTA Pwm Overview Access Synchronizable VRTA Pwm Using C++ Methods s ETAS Virtual ECU V2.0 VRTA Device User Guide 3

4 Contents InjectedDutyCycle InjectedOutputToIdle InjectedOutputState InjectedEnableNotification InjectedDisableNotification Events Result CurrentJob DETErrors InjectedResult VRTA ICU Device VRTA ICU Overview Access Synchronizable VRTA ICU Using C++ Methods s Init De-Init SetMode DisableWakeup EnableWakeup SetActivationCondition DisableNotification EnableNotification ResetEdgeCount EnableEdgeCount EnableEdgeDetection DisableEdgeDetection DisableEdgeCount StartSignalMeasurement StopSignalMeasurement Events DETErrors InputState Mode EdgeNumbers TimeElapsed DutyCycles CheckWakeupStatus VRTA ADC Device VRTA ADC Overview Access Synchronizable VRTA Adc Using C++ Methods s InjectedSetupResultBuffer InjectedStartGroupConversion InjectedStopGroupConversion InjectedEnableHardwareTrigger InjectedDisableHardwareTrigger InjectedEnableGroupNotification InjectedDisableGroupNotification InjectedReadGroup InjectedGetStreamLastPointer InjectedGetGroupStatus Events ETAS Virtual ECU V2.0 VRTA Device User Guide 4

5 Contents Result ValidSample Status CurrentJob DETErrors InjectedResult InjectedValidSample InjectedStatus VRTA CAN Device VRTA Can Overview s CanInit Can_InitController Can_SetControllerMode CanDisableControllerInterrupts CanEnableControllerInterrupts CanCheckWakeup CanWrite CanMainFunction_Write CanMainFunction_Read CanMainFunction_BusOff CanMainFunction_Wakeup CanMainFunction_Mode Events CanControllerStatus CanWriteStatus Status CurrentJob DETErrors DriverState VRTA CanTrcv Device VRTA CanTrcv Overview s SetOpMode GetOpMode GetBusWuReason SetWakeupMode CheckWakeup Events Result CurrentJob DETErrors CurrentStatus WakeupMode VRTA FLASH Device VRTA Flash Overview Access VRTA Flash Using C++ Methods s Inject Write Inject Read ETAS Virtual ECU V2.0 VRTA Device User Guide 5

6 Contents Inject Erase Inject Compare Inject Cancel Inject Set Mode Events Result Status DETErrors CurrentJob InjectedRead InjectedResult InjectedStatus Synchronization Clock Device(vrtaSyncClock) VrtaSynchClock Overview Timer Hierarchy Access Synchronizable Clock Features Using C++ Methods s Interval Scale Start Stop Adaptive FreeRunning TickLimit Events Interval Scale Running TicksRemaining ETAS Contact Addresses ETAS Virtual ECU V2.0 VRTA Device User Guide 6

7 Figures Figures Fig 1 Fig 2 Fig 3 Fig 4 Fig 5 Fig 6 Fig 7 Fig 8 Fig 9 Fig 10 Fig 11 Fig 12 Virtual Device / s / Events. Snapshot showing that VECU is running successfully. Showing the sys log that VECU is running successfully General snapshot of VRTA Monitor VRTA Monitor to add the host name. VRTA Monitor about where to add the host name. VRTA Monitor showing the VECU name VRTA Monitor displaying the devices inside the VECU VRTA CAN Driver Device in VECU Sending the values through VRTA Monitor Receiving the values through VRTA Monitor Polling Receiving the values through VRTA Monitor Hooking ETAS Virtual ECU V2.0 VRTA Device User Guide 7

8 1 Introduction This Document will guide the user to use VRTA devices in the VECU. The VRTA devices explained here are ADC, FLASH, ICU, PORT, PWM, CAN, CANTrcv, DIO, SynchronizableClock. It will also provide information on connecting the device with external applications and send/receive messages with the VRTA virtual device. This feature will also allow monitoring the behavior of the MCAL from an external world. Targeted Users: It is intended to those who want to develop Virtual Devices for EVE MCAL Modules. It is also intended to those who want to monitor the behavior of the MCAL in the VECU using external Applications like VRTA Monitor. Reference Manual: Detailed Information on VRTA Virtual ECU is provided in the RTA-OS VRTA Virtual ECU User Guide. For a default installation of VRTA, this will be found in C:\ETAS\RTA-OS\Targets\VRTA. This guide does not tell you how to configure and use RTA-OS. That information is provided in the RTA-OS User Guide. A complete technical reference to RTA-OS can be found in the RTA-OS Reference Guide. Both of these documents can be found in the Documents folder of your RTA-OS installation. For a default installation, this will be found in C:\ETAS\RTA-OS\Documents. Pre-requisites: Users should be aware of how to create a VECU, compile and run in ISOLAR-EVE. Users should aware of some basic VRTA APIs like On, AsyncGetState etc. Good Knowledge of C, C++ is required. 1.2 Definitions and Abbreviations API AUTOSAR BSW VECU VRTA MCAL ADC CAN CANTrcv DIO ICU PWM Application Programming Interface Automotive Open System Architecture Basic Software Virtual Electronic Control Unit Virtual RTA Microcontroller Abstraction Layer Analogue Digital Converter Controller Area Network CAN Transceiver Digital Input Output Input Capture Unit Pulse Width Modulation RTA-OS It is a statically configurable, preemptive, real-time operating system (RTOS) for use in high-performance, resource-constrained applications. VRTA It is nothing but Virtual RTA-OS. It does not need any real hardware, other than the host PC that you run it on. Instead, you create a Virtual ECU (VECU) in software that simulates the real-life devices such as switches or sensors that will be present in your physical ECU. ETAS Virtual ECU V2.0 VRTA Device User Guide 8

9 Vitual Devices, s and Events VECUs use virtual devices to get things done. Virtual Devices have actions and events. One can pass values to the virtual device from an external application like vrtamonitor or a 3rd party application to the VECU using s and get values from the VECU to an external application using Events. Fig 1 Virtual Device / s / Events 1.3 Conventions The following typographical conventions are used in this document: OCI_CANTxMessage msg0 = Choose File Open. Click OK. Press <ENTER>. The "Open File" dialog box is displayed. Select the file setup.exe A distribution is always a onedimensional table of sample points. Code snippets are presented on a gray background and in the Courier font. Meaning and usage of each command are explained by means of comments. The comments are enclosed by the usual syntax for comments. Menu commands are shown in boldface. Buttons are shown in boldface. Keyboard commands are shown in angled brackets. Names of program windows, dialog boxes, fields, etc. are shown in quotation marks. Text in drop-down lists on the screen, program code, as well as path- and file names are shown in the Courier font. General emphasis and new terms are set in italics. ETAS Virtual ECU V2.0 VRTA Device User Guide 9

10 2 Sending / Receiving the values through VRTA Monitor Fig 9 VRTA CAN Driver device in VECU The above diagram shows the available actions and events in the device CAN Device. The actions and events were explained before in section 2.3 and Connecting the VRTA Monitor Assume that, Your VECU is compiled and running successfully. By clicking the VrtaMonitor.exe, you will see the VRTA Monitor window as shown below. ETAS Virtual ECU V2.0 VRTA Device User Guide 10

11 Fig 4 General snapshot of VRTA Monitor Add a new host name/ip address by clicking the File->Add New Host option as shown below. Fig 5 VRTA Monitor to add the host name. Then add the new host / IP Address by clicking the host option as shown in the below snapshot. ETAS Virtual ECU V2.0 VRTA Device User Guide 11

12 Fig 6 VRTA Monitor about where to add the host name. Right click on the host name appears at the left side and connect it. Then it will automatically request the VRTA server in the background and displays the available VECU s in the host machine assuming that VECU must be running in order for the VRTA Monitor to detect the VECU. You should be seeing the VECU name in the VRTA Monitor as shown below. ETAS Virtual ECU V2.0 VRTA Device User Guide 12

13 Fig 7 VRTA Monitor showing the VECU name Expand the VECU listed to view the available devices in it as shown below. Fig 8 VRTA Monitor displaying the devices inside the VECU 2.2 Running the Virtual ECU using ISOLAR-EVE It is like a normal VECU Build where we can debug the VRTA code as well. Before Connecting to the Vrta, make sure that the VECU is built, deployed and running successfully. If you are running through the ISOLAR, You will see the ISOLAR Window as shown below. ETAS Virtual ECU V2.0 VRTA Device User Guide 13

14 Fig 2 Snapshot showing that VECU is running successfully. Below, Internal Web Browser window of ISOLAR-EVE shows that the VECU is started and running successfully. ETAS Virtual ECU V2.0 VRTA Device User Guide 14

15 Fig 3 log showing that VECU is running successfully Note: CAN Device is used here as an example. The procedure shall be the same across all other virtual devices. 2.3 Sending the s (s) User can send values from the VECU to an external Application like vrtamonitor or a 3 rd party ETAS Virtual ECU V2.0 VRTA Device User Guide 15

16 Fig 10 Sending values through VrtaMonitor Right click on the each action available below the CAN DriverDevice device to enter the parameters and use Send option to send the values through VrtaMonitor. 2.4 Receiving the values through polling / hooking (Events) User can get values from the VECU to an external Application like vrtamonitor or a 3 rd party Event Polling Right click on an event available below the CAN DriverDevice device, enter the parameters (if available) and use Read option for receiving the values through VRTA. ETAS Virtual ECU V2.0 VRTA Device User Guide 16

17 Fig 11 Receiving the values through VrtaMonitor Polling Event Hooking Right click on event available below the CAN DriverDevice device and enable the Monitor option. Once enabled you can switch to Monitor option on the bottom of the Screen. While executing the CAN DriverIdlehandler, it will raise the RaiseInjectedEvents () method. In that, you can see the Event being raised through hooking to update result and status. That would be displayed on the Monitor screen. ETAS Virtual ECU V2.0 VRTA Device User Guide 17

18 3 VRTA PORT Device 3.1 VRTA Port Overview The VRTA Port is a virtual device that can be used for setting the Port Pin Direction, Port Pin Mode, and to refresh the Port pins. It will support mainly AUTOSAR functionalities as mentioned below. Port_SetPinDirection Port_SetPinMode Port_RefreshPortDirection 3.2 Access Synchronizable VRTA Port Using C++ Methods In the VRTA Port, Each channel is linked to virtual pins available. The current request status (like SetPinDirection, SetPinMode) can be displayed in the vrta Monitor by hooking the proxy APIs in the MCAL. Error notification can be identified by hooking the proxy APIs in the MCAL. Method: evevrtaport () The constructor. evevrtaport::evevrtaport(const vrtatextptr name,vrtauint MaxPins) Name Input The name of the virtual device. MaxPins Input Total Number of Port Pins. This is the constructor used to create an instance of a VRTA Port device. Method: UpdateportDetErrors () Update the DET Errors, if any. Void UpdateportDetErrors(uint8 det) det Input It will update the DET Errors, if any. This method is used to update the DET Errors by raising an event, if any. ETAS Virtual ECU V2.0 VRTA Device User Guide 18

19 Method: UpdateportCurrentJob () Update the current job like Set Pin Direction / Mode / Refresh Port. Void UpdateportCurrentJob(uint8 job) job Input Update the Current job information This method will update the current job information. Method: UpdateCurrentJob () It is used to call the AUTOSAR APIs when the Os is in Idle. Void PortIdleHandler() <None> This method will raise the AUTOSAR APIs when the Os is in Idle. 3.3 s User can pass values to the VRTA Port device from an external application like vrtamonitor or a 3 rd party application to the VECU using s. Each action supported by a VRTA Port device is described by a standard table, as below, followed by text to explain the purpose of the action or event. ETAS Virtual ECU V2.0 VRTA Device User Guide 19

20 XXXX YYYY The table contains the numeric of the action or event (XXXX), and the format of the action or event data (YYYY). Below are the s that are supported by the VRTA Port InjectedPortpinDirection 1 %u, PORT_PIN_IN PORT_PIN_OUT This action buffers the input parameters like port pin number and information about whether the port pin should be IN or OUT. The PortIdleHandler will process the buffered values when the OS is in Idle state. The first number in the action data is the port pin number and the second number is the PORT_PIN_IN or PORT_PIN_OUT InjectedRefreshPortDirection 2 <None> This action will refresh all the port pins to reflect any changes in the pin direction InjectedSetPinMode 3 %u,%u Mode0-PORT_PIN_MODE_ADC 1-PORT_PIN_MODE_CAN 2-PORT_PIN_MODE_FLEXRAY 3-PORT_PIN_MODE_LIN 4-PORT_PIN_MODE_DIO 5-PORT_PIN_MODE_ICU 6-PORT_PIN_MODE_PWM This action buffers the input parameter like Port pin number and mode. The PortIdleHandler will process the buffered values when the OS is in Idle state. The first number in the action data is the Port pin number and the second parameter is the mode. It could be something like above mentioned modes. 3.4 Events User can get values from the VECU to an external Application like vrtamonitor or a 3 rd party application using Events. There are two ways of doing this 1. Event Polling Event Polling External application can poll the events in a vrtadevice to get the value of the event at that particular time. For More information about Event hooking and Event Polling, refer the VRTA User Guide. Below are the Events that are supported by the VRTA Port ETAS Virtual ECU V2.0 VRTA Device User Guide 20

21 3.4.1 CurrentJob Event 1 Macros * Macros None SETPINDIRECTION SETPINMODE REFRESHDIRECTION This event is raised when there is a change in the current request (current job) DETErrors Event 2 Macros *Macros- None PORT_E_PARAM_PIN PORT_E_DIRECTION_UNCHANGEABLE PORT_E_PARAM_CONFIG PORT_E_PARAM_INVAL_MODE PORT_E_MODE_UNCHANGEABLE PORT_E_UNINIT PORT_E_PARAM_POINTER This event is raised when there are any errors (only Development Error Tracer) or there is a change in the previous event value. ETAS Virtual ECU V2.0 VRTA Device User Guide 21

22 4 VRTA DIO Device 4.1 VRTA DIO Overview The DIO driver provides port and channel based read and write access to the internal general purpose Input/Output ports. The read and write behavior is not buffered. The basic behavior of the driver is synchronous. The DIO Driver provides services from reading and writing to and from the following DIO Channel Represents a single general purpose digital I/O pin DIO Port Represents multiple DIO channels that are grouped by hardware and accessible synchronously (controlled by one hardware register) DIO Channel group Represents multiple adjoining DIO channels represented by a logical group. It is a subset of one DIO port. It is also accessed synchronously The behaviors of the DIO services are synchronous. This module works on pins and ports which are configured by the PORT driver for this purpose. DIO Device is the Parent device and has a DIOPort device as its child DIOPort device has a DIOGroup device as its child device Dio port device is generated automatically for each Dio port configuration and DIO Group device is generated automatically for each Channel Group Configuration. This allows users to access the ports without specifying the port Numbers. 4.2 s User can pass values to the VRTA DIO device from an external application like vrtamonitor or a 3 rd party application to the VECU using s. Below are the s that are supported by the VRTA DIO Write Channel Requests to set the level of a channel. Input Parameters %u - Channel Number %u - in the channel (0 or 1) Raised Events: (%u) Channel Written This event is raised number when a new value is written into a Channel. This event returns the Channel Number. ETAS Virtual ECU V2.0 VRTA Device User Guide 22

23 4.2.2 Flip Channel Requests to flip the level of a Channel. Input Parameters %u - Channel Number Raised Events: (%u) Channel Written This event is raised when a new value is written into a Channel. This event returns the Channel Number Write Port Requests to set the value of a Port.This action is provided in the DIO Port device. Input Parameters %x - The value that needs to be written in the port Raised Events: (%u) Port Written This event is raised when a new value is written into a port. This event returns the Port Number Write Channel Group Requests to set the value of a Channel Group. This action is provided in the DIO Group device. Input Parameters %x - The value that needs to be written in the Channel Group Raised Events: (%u) Channel Group Written This event is raised when a new value is written into a Channel Group. This event returns the Channel Group Number. 4.3 Events User can get values from the VECU to an external Application like vrtamonitor or a 3 rd party application using Events. There are two ways of doing this 2. Event Polling 3. Event Hooking ETAS Virtual ECU V2.0 VRTA Device User Guide 23

24 Event Polling External application can poll the events in a vrtadevice to get the value of the event at that particular time. Event Hooking External application can also get notified automatically of some change in state/value by raising an event. Below are the Events that are supported by the VRTA DIO Read Channel (%u) ReadChannel (%u) A channel number is passed as an input and the channel pin level is returned. This is a polling event Channel Written (%u) ChannelGroupWritten This Event will be raised with a Channel Group number that was written DET Errors DETErrors (Enum) <INVAL_CHANNEL_ INVAL_PORT_ INVAL_GROUP_ PARAM_CONFIG_ERROR PARAM_POINTER_ERROR > This Event will be raised from the MCAL when it reports an error Port Written (%u) PortWritten This Event will be raised with the port number that was written Channel Group Written (%x) ReadChannelGroup (%u) A Channel Group number is passed as an input and the Channel Group pin levels are returned in hex. This is a polling event. ETAS Virtual ECU V2.0 VRTA Device User Guide 24

25 5 VRTA PWM Device 5.1 VRTA Pwm Overview The VRTA Pwm is a virtual device that can be used for setting the DutyCycle, Period, output to idle, getting the output state, Enable and Disable the Notification. It will support mainly AUTOSAR functionalities as mentioned below. Pwm_SetDutyCycle Pwm_SetPeriodAndDuty Pwm_SetOutputToIdle Pwm_GetOutputState Pwm_DisableNotification Pwm_EnableNotification 5.2 Access Synchronizable VRTA Pwm Using C++ Methods In the VRTA Pwm, Each channel is linked to virtual pins available. The current request status (like SetDutyCycle, SetPeriodandDuty) can be displayed in the vrta Monitor by hooking the proxy APIs in the MCAL. Error notification can be identified by hooking the proxy APIs in the MCAL. Method: evevrtapwm () The constructor. evevrtapwm (const vrtatextptr name, vrtauint NumberofChannels) Name Input The name of the virtual device. NumberofChannels Input Total Number of Channels This is the constructor used to create an instance of a VRTA Pwm device. Method: UpdateJobResult () Update the Job Result. ETAS Virtual ECU V2.0 VRTA Device User Guide 25

26 void UpdateJobResult(uint8 return_val) return_val Input It will update the result of the job, if any. This method is used to update the job result by raising an event, if any. Method: UpdateDetErrors () Update the DET Errors Void UpdateDetErrors(uint8 det) det Input Update the DET Errors, if any This method will update the DET Errors, if any. Method: UpdateCurrentJob () Update the current job Void UpdateCurrentJob(uint8 job) job Input It will update the current job. This method will give the current job information by raising an event. Method: PwmIdleHandler () Used to call the AUTOSAR APIs when the OS is in Idle. ETAS Virtual ECU V2.0 VRTA Device User Guide 26

27 Void PwmIdleHandler(void) This method gets called from software when it is in Idle state. This is used to route the call to Proxy MCAL. 5.3 s User can pass values to the VRTA Pwm device from an external application like vrtamonitor or a 3 rd party application to the VECU using s. Each action supported by a VRTA Pwm device is described by a standard table, as below, followed by text to explain the purpose of the action or event. XXXX YYYY The table contains the numeric of the action or event (XXXX), and the format of the action or event data (YYYY). Below are the s that are supported by the VRTA Pwm InjectedDutyCycle 1 %u,%x:;0;32768 This action buffers the input parameters like channel number and Dutycycle. The PwmIdleHandler will process the buffered values when the OS is in Idle state. The first number in the action data is the channel number and the second number is the Dutycycle InjectedPeriodandDutyCycle 2 %u,%u,%x:;0;32768 This action buffers the input parameters like channel number, Period and Dutycycle. The PwmIdleHandler will process the buffered values when the OS is in Idle state. The first ETAS Virtual ECU V2.0 VRTA Device User Guide 27

28 number in the action data is the channel number, second number is the Period and the third is the Dutycycle InjectedOutputToIdle 3 %u This action buffers the input parameter like channel number. The PwmIdleHandler will process the buffered values when the OS is in Idle state. The first number in the action data is the channel number InjectedOutputState 4 %u This action buffers the input parameter like channel number. The PwmIdleHandler will process the buffered values when the OS is in Idle state. The first number in the action data is the channel number InjectedEnableNotification 5 %u,%u 0-PWM_FALLING_EDGE,1-PWM_RISING_EDGE,2- PWM_BOTH_EDGES This action buffers the input parameter like channel number. The PwmIdleHandler will process the buffered values when the OS is in Idle state. The first number in the action data is the channel number. The Notification parameter could be PWM_FALLING_EDGE, PWM_RISING_EDGE, PWM_BOTH_EDGES InjectedDisableNotification 6 %u This action buffers the input parameter like channel number and Notification Parameter. The PwmIdleHandler will process the buffered values when the OS is in Idle state. The first number in the action data is the channel number. 5.4 Events User can get values from the VECU to an external Application like vrtamonitor or a 3 rd party application using Events. There are two ways of doing this 4. Event Polling 5. Event Hooking Event Polling External application can poll the events in a vrtadevice to get the value of the event at that particular time. ETAS Virtual ECU V2.0 VRTA Device User Guide 28

29 Event Hooking External application can also get notified automatically of some change in state/value by raising an event. Below are the Events that are supported by the VRTA Pwm Result Event 1 Macros *Macros None STD_LOW STD_HIGH This event is raised when there is a change in the result of the action. However, only one result in vrta-pwm. (i.e) GetoutputState CurrentJob Event 2 Macros * Macros None SetDutyCycle SetPeriodandDutyCycle SetOutputToIdle GetOutputState EnableNotification DisableNotification This event is raised when there is a change in the current request (current job) of the actions DETErrors Event 3 Macros *Macros-None PWM_E_UNINIT PWM_E_PARAM_CHANNEL PWM_E_UNCHANGEABLE INVAL PARAM_E_POINTER This event is raised when there are any errors (only Development Error Tracer errors) or there is a change in the previous event value InjectedResult Event 4 None STD_LOW STD_HIGH This event is raised while performing the operation like getoutput state to update the event being performed by the user. ETAS Virtual ECU V2.0 VRTA Device User Guide 29

30 6 VRTA ICU Device 6.1 VRTA ICU Overview The VRTA - ICU is a virtual device provides services for demodulation of a PWM signal, counting pulses, measuring of frequency and duty cycle, generating simple interrupts and also wakeup interrupts. It also provides services for Signal notification, Controlling wakeup interrupts, Periodic signal time measurement, Edge time stamping, usable for the acquisition of non-periodic signals, Edge Counting. This ICU module pins have 2 modes: o ICU_MODE_NORMAL o ICU_MODE_SLEEP 6.2 Access Synchronizable VRTA ICU Using C++ Methods The VRTA ICU works on so called ICU Channel. Method: evevrtaicu () The constructor. evevrtaicu (const vrtatextptr name) name Input The name of the virtual device. This is the constructor used to create an instance of a VRTA ICU device. Method: UpdateIcuDetErrors (uint8 det) Update the DET Errors. void UpdateIcuDetErrors (uint8 det) det Input It will update the DET of the job. ETAS Virtual ECU V2.0 VRTA Device User Guide 30

31 This method is used to update the DET value by raising an event. Method: Update_IcuMode (uint8 Mode) Update the ICU Mode Void Update_IcuMode (uint8 Mode) icuchannelmode Input Update the Mode. This method updates the ICU Mode. Method: Update_icuCheckwakeup (EcuM_WakeupSourceType icu_wakeup) Update the wakeup source information Void Update_icuCheckwakeup (EcuM_WakeupSourceType icu_wakeup) icu_wakeup Input Update the wakeup source information. This method will update the wakeup source information. Method: Icu_IdleHandler () Used to call the AUTOSAR functionalities when the OS is in Idle. Void Icu_IdleHandler () <None> This method will call the AUTOSAR functionalities when the OS is in Idle. ETAS Virtual ECU V2.0 VRTA Device User Guide 31

32 6.3 s User can pass values to the VRTA ICU device from an external application like VRTA Monitor or a 3 rd party application to the VECU using s. Each action supported by a VRTA ICU device is described by a standard table, as below, followed by text to explain the purpose of the action or event. XXXX YYYY The table contains the numeric of the action or event (XXXX), and the format of the action or event data (YYYY). Below are the s that are supported by the VRTA ICU Init 1 <None> This action is used to call the Icu_Init() De-Init 2 <None> This action is used to call the Icu_De-Init() SetMode 3 %u 0-Normal 1-Sleep The action will set the ICU Pin modes to either Normal or Sleep. ETAS Virtual ECU V2.0 VRTA Device User Guide 32

33 6.3.4 DisableWakeup 4 %u The action will disable the Wakeup if it is configured as wakeup capable true EnableWakeup 5 %u The action will enable the Wakeup if it is configured as wakeup capable true SetActivationCondition 6 %u, %u 0-Rising Edge 1-Falling Edge 2-Both Edges The action will set the activation parameter for the given ICU channel. The first argument is channel number and the second argument is activation parameter. It could be ICU_RISING_EDGE,ICU_FALLING_EDGE,ICU_BOTH_EDGES DisableNotification 7 %u The action will disable the channel Notification for a channel. The only argument is channel number EnableNotification 8 %u The action will enable the channel Notification for a channel. The only argument is channel number ResetEdgeCount 9 %u The action will reset the edge count of an ICU channel. The only argument is channel number. ETAS Virtual ECU V2.0 VRTA Device User Guide 33

34 EnableEdgeCount 10 %u The action will enable the edge count of an ICU channel. The only argument is channel number EnableEdgeDetection 11 %u The action will enable the edge detection of an ICU channel. The only argument is channel number DisableEdgeDetection 12 %u The action will disable the edge detection of an ICU channel. The only argument is channel number DisableEdgeCount 13 %u The action will disable the edge count of an ICU channel. The only argument is channel number StartSignalMeasurement 14 %u The action will start the signal measurement of an ICU channel. The only argument is channel number StopSignalMeasurement 15 %u The action will stop the signal measurement of an ICU channel. The only argument is channel number. ETAS Virtual ECU V2.0 VRTA Device User Guide 34

35 6.4 Events User can get values from the VECU to an external Application like vrtamonitor or a 3 rd party application using Events. There are two ways of doing this 6. Event Polling 7. Event Hooking Event Polling External application can poll the events in a vrtadevice to get the value of the event at that particular time. Event Hooking External application can also get notified automatically of some change in state/value by raising an event. For more information about the Polling and Hooking, Refer VRTA User Guide. Below are the Events that are supported by the VRTA ICU DETErrors Event 1 %u This event is raised when there is a change in the DET InputState Event 2 None ICU_CHANNEL_ACTIVE ICU_CHANNEL_LE This event is raised to update the ICU channel status. It could be Active or Idle Mode Event 3 None NORMAL SLEEP This event is raised to update the ICU Mode. It could be Normal or Sleep EdgeNumbers Event 4 %u(%u) This event is raised to update the ICU channel Edge Numbers TimeElapsed Event 5 None LOW_TIME HIGH_TIME ACTIVE_TIME PERIOD_TI ME (%u) This event is raised to update the ICU channel Time Elapsed. ETAS Virtual ECU V2.0 VRTA Device User Guide 35

36 6.4.6 DutyCycles Event 6 %u This event is raised to update the ICU channel Duty Cycle values CheckWakeupStatus Event 7 %u This event is raised to update the ICU channel Wakeup source information. ETAS Virtual ECU V2.0 VRTA Device User Guide 36

37 7 VRTA ADC Device 7.1 VRTA ADC Overview The VRTA Adc is a virtual device that can be used for controlling the internal Analogue Digital Converter of the micro controller. It provides services to start and stop a conversion respectively to enable and disable the trigger source for a conversion. Furthermore, it provides services to enable and disable a notification mechanism and routines to query the status and result of a conversion. It will support mainly AUTOSAR functionalities mentioned below. 1) SetupResultBuffer 2) StartGroupConversion 3) StopGroupConversion 4) ReadGroup 5) EnableHardwareTrigger 6) DisableHardwareTrigger 7) EnableGroupNotification 8) DisableGroupNotification 9) GetGroupStatus 10) GetStreamLastPointer 11) GetVersionInfo 7.2 Access Synchronizable VRTA Adc Using C++ Methods The VRTA Adc works on so called ADC Channel Groups, which are build from so called ADC Channels. An ADC Channel Group combines as analogue input pin (ADC Channel), the needed ADC circuitry itself and conversion result register into an entity that can be individually controller and accessed via ADC Vrta module. Method: evevrtaadc () The constructor. evevrtaadc (const vrtatextptr name, AdcGroup str[]) name Input The name of the virtual device. Str[] Input The structure which contains the information about the streaming samples and channels present in a group. This is the constructor used to create an instance of a VRTA Adc device and to get the information about the streaming samples of an each group channel. ETAS Virtual ECU V2.0 VRTA Device User Guide 37

38 Method: UpdateJobResult () Update the Job Result. void UpdateJobResult(vrtaUInt return_val) return_val Input It will update the result of the job. This method is used to update the job result by raising an event. (It could be either zero or one. If it is success, it will return zero. Otherwise, it would return one) Method: UpdateValidSamples () Update the valid samples Void UpdateValidSamples(uint8 samples) samples Input Update the valid samples of the group channel This method updates the valid samples of the group channel. It may be 0,1,2 depends on the user configuration Method: UpdateadcStatus () Update the adc status Void UpdateadcStatus(Adc_StatusType status) status Input Update the status, if any change in the previous state. ETAS Virtual ECU V2.0 VRTA Device User Guide 38

39 This method will update the status, if any. It could be Busy, Idle, and Conversion Completed like that. Method: UpdateCurrentJob () Update the current job Void UpdateCurrentJob(uint8 job) job Input It will update the current job. This method will give the current job information by raising an event. It could be Start Conversion, Stop Conversion, Enable Notification, and Disable Notification like that. Method: ExecuteJob () Used to update the DET Errors, if any Void UpdateDetErrors(uint8 det) det Input Used to update the DET, if any This method will update the DET Errors. It will be showed as Enumerations type in the Vrta Monitor. Method: printfinfo_readgroup () Used to print the Read Group information Void printfinfo_readgroup() ETAS Virtual ECU V2.0 VRTA Device User Guide 39

40 This method is used to print the read group information s. It would be the conversion values of the group channel. Method: printfinfo_getlastpointer () Used to print the get stream last pointer information s Void printfinfo_getlastpointer(adc_grouptype* ptrsam) ptrsam of type Adc_GroupType* Input Used to print the get stream last pointer information s This method is used to print the get stream last pointer information s. Method: RaiseInjectedEvents () Used to raise the Injected events. Void RaiseInjectedEvents () <None> This method is used to raise the injected events. It could be Injected valid sample, Injected Result, Injected Status. Method: AdcIdleHandler () Used to raise the AUTOSAR API call when the Os is in Idle. ETAS Virtual ECU V2.0 VRTA Device User Guide 40

41 Void AdcIdleHandler () <None> This method is used to raise the AUTOSAR API call when the Os is in Idle. 7.3 s User can pass values to the VRTA Adc device from an external application like vrtamonitor or a 3 rd party application to the VECU using s. Each action supported by a VRTA Adc device is described by a standard table, as below, followed by text to explain the purpose of the action or event. XXXX YYYY The table contains the numeric of the action or event (XXXX), and the format of the action or event data (YYYY). Below are the s that are supported by the VRTA Adc InjectedSetupResultBuffer 1 %u The action sets up the buffer for storing the conversion values. The only argument is group channel number InjectedStartGroupConversion 2 %u The action will start the conversion for a group channel. The only argument is group channel number. ETAS Virtual ECU V2.0 VRTA Device User Guide 41

42 7.3.3 InjectedStopGroupConversion 3 %u The action will stop the conversion for a group channel. The only argument is group channel number InjectedEnableHardwareTrigger 4 %u The action will enable the Hardware Triggger for a group channel. The only argument is group channel number InjectedDisableHardwareTrigger 5 %u The action will disable the Hardware Triggger for a group channel. The only argument is group channel number InjectedEnableGroupNotification 5 %u The action will Enable the Group Notification for a group channel. The only argument is group channel number InjectedDisableGroupNotification 5 %u The action will disable the Group Notification for a group channel. The only argument is group channel number InjectedReadGroup 5 %u The action will read the group values for a group channel. The only argument is group channel number InjectedGetStreamLastPointer 5 %u ETAS Virtual ECU V2.0 VRTA Device User Guide 42

43 The action will get the stream last pointer for a group values for a group channel. The only argument is group channel number InjectedGetGroupStatus 5 The action will get the group status. (It could be idle, busy and stream completed) for a group channel. The only argument is group channel number. 7.4 Events User can get values from the VECU to an external Application like vrtamonitor or a 3 rd party application using Events. There are two ways of doing this 8. Event Polling 9. Event Hooking Event Polling External application can poll the events in a vrtadevice to get the value of the event at that particular time. Event Hooking External application can also get notified automatically of some change in state/value by raising an event. For more information about the Polling and Hooking, Refer VRTA User Guide. Below are the Events that are supported by the VRTA Adc Result Event 1 %u This event is raised when there is a change in the result ValidSample Event 2 %u This event is raised when there is a change in the validsample Status Event ETAS Virtual ECU V2.0 VRTA Device User Guide 43

44 3 None ADC_LE ADC_BUSY ADC_COMPLETED ADC_STR EAM_COMPLETED This event is raised when there is a change in the status. It would be enumeration as mentioned in the above table CurrentJob Event 4 None SETUPRESULTBUFFER STARTGROUPCONVERSION STOPGROUPCONVERSION ENABLEHARDWARETRIGGER DISABLEHARDWARETRIGGER ENABLEGROUPNOTIFICATI ON DISABLEGROUPNOTIFICATION READGROUP GETSTR EAMLASTPOINTER GETGROUPSTATUS This event is raised when there is a change in the current job. It would be enumeration as mentioned in the above table DETErrors Event 5 None ADC_E_UNINIT ADC_E_BUSY ADC_E_LE ADC_E _ALREADY_INITIALIZED ADC_E_PARAM_CONFIG ADC_E _PARAM_POINTER ADC_E_PARAM_GROUP ADC_E_WRO NG_CONV_MODE ADC_E_WRONG_TRIGG_SRC ADC_E_N OTIF_CAPABILITY ADC_E_BUFFER_UNINIT This event is raised when there is any DET Errors. It would be enumeration as mentioned in the above table InjectedResult Event 6 %u This event is raised when there is a change in the result of the Injected actions. It would be enumeration as mentioned in the above table InjectedValidSample Event 7 %u This event is raised when there is a change in the valid sample of an injected action InjectedStatus Event 8 %u This event is raised when there is a change in the status of an injected action. ETAS Virtual ECU V2.0 VRTA Device User Guide 44

45 8 VRTA CAN Device 8.1 VRTA Can Overview The CAN Driver is a virtual device, which adapts the signal levels that are used on the CAN bus to the logical (digital) signal levels recognized by a microcontroller. It will support mainly AUTOSAR functionalities mentioned below. 1) CanInit 2) CanInitController 3) CanSetControllerMode 4) CanDisableControllerInterrupts 5) CanEnableControllerInterrupts 6) CanCheckWakeup 7) CanWrite 8) CanMainFunction_Write 9) CanMainFunction_Read 10) CanMainFunction_BusOff 11) CanMainFunction_Wakeup 12) CanMainFunction_Mode 8.2 s User can pass values to the VRTA CAN Driver device from an external application like vrtamonitor or a 3 rd party application to the VECU using s. Each action supported by a VRTA CAN Driver device is described by a standard table, as below, followed by text to explain the purpose of the action or event. XXXX YYYY The table contains the numeric of the action or event (XXXX), and the format of the action or event data (YYYY) CanInit Acti on 1 <CAN_VAL_ARGUMENTS CAN_ALREADY_INIT_CHECK CAN_NULL_PO INTER_CHECK> The action calls the Can_Init function that initializes the module Can_InitController ETAS Virtual ECU V2.0 VRTA Device User Guide 45

46 2 %u, %u, <CAN_EXT CAN_MIXED CAN_STD,HIGH LOW> The action initializes the bit timing related settings of a CAN controller Can_SetControllerMode 3 %u, <CAN_STOP CAN_START CAN_SLEEP CAN_WAKEUP CAN_EXIT INVAL_MODE> This action performs software triggered state transitions of the CAN controller State machine CanDisableControllerInterrupts 4 %u The action disables all interrupts for this CAN controller CanEnableControllerInterrupts 5 %u The action enables all allowed interrupts CanCheckWakeup 6 %u The action checks if a wakeup has occurred for the given controller CanWrite 7 %u,%u,%u,%a The action Can_Write first checks if the hardware transmit object that is identified by the HTH is free and if another Can_Write is ongoing for the same HTH. It returns CAN_OK if the hardware transmit object is free. It returns CAN_BUSY if the hardware transmit object is busy with other transmit request CanMainFunction_Write 8 No Arguments This action performs the polling of TX confirmation and TX cancellation confirmation when ETAS Virtual ECU V2.0 VRTA Device User Guide 46

47 CAN_TX_PROCESSING is set to POLLING CanMainFunction_Read 9 No Arguments The action performs the polling of RX indications when CAN_RX_PROCESSING is set to POLLING CanMainFunction_BusOff 10 No Arguments The action performs the polling of bus-off events that are configured statically as 'to be polled' CanMainFunction_Wakeup 11 No Arguments The action performs the polling of wake-up events that are configured statically as 'to be polled' CanMainFunction_Mode 12 No Arguments The action performs the polling of CAN controller mode transitions. ETAS Virtual ECU V2.0 VRTA Device User Guide 47

48 8.3 Events User can get values from the VECU to an external Application like vrtamonitor or a 3 rd party application using Events. There are two ways of doing this 10. Event Polling 11. Event Hooking Event Polling External application can poll the events in a vrtadevice to get the value of the event at that particular time. Event Hooking External application can also get notified automatically of some change in state/value by raising an event. For more information about the Polling and Hooking, Refer VRTA User Guide. Below are the Events that are supported by the VRTA Can CanControllerStatus Event 1 %u This event is raised when there is a change in the status. Returns CAN_OK if status change request accepted and returns CAN_NOT_OK if a development error occurred CanWriteStatus Event 2 < CAN_OK CAN_NOT_OK CAN_BUSY> This event is raised when the function Can_Write performs write actions. The event returns the status CAN_OK when write command has been accepted and CAN_NOT_OK if a development error occurred and CAN_BUSY if there is No TX hardware buffer available or pre-emptive call of Can_Write that can't be implemented re-entrant Status Event 3 %u Returns the state of the Can controller mode. ETAS Virtual ECU V2.0 VRTA Device User Guide 48

49 8.3.4 CurrentJob Event 4 <CAN_INT CAN_MAINFUNCTION_WRITE CAN_INITCONTROLL ER CAN_SETCONTROLLERMODE CAN_DISABLECONTROLLERIN TERRUPTS CAN_ENABLECONTROLLERINTERRUPTS CAN_WRIT E CAN_API_GETVERSIONINFO CAN_MAINFUNCTION_READ CAN_MAINFUNCTION_BUSOFF CAN_MAINFUNCTION_WAKEUP > This event is raised when there is a change in the action called. It would be enumeration as seen from the above table DETErrors Event 5 <None CAN_E_PARAM_POINTER CAN_E_PARAM_HANDLE CAN _E_PARAM_DLC CAN_E_PARAM_CONTROLLER CAN_E_UNINIT CAN_E_TRANSITION> This event is raised when there is a change in the DET error status. It would be enumeration as mentioned in the above table DriverState Event 6 < CAN_UNINIT CAN_READY > The event returns the CAN Driver state. Can module have two states CAN_UNINIT and CAN_READY. ETAS Virtual ECU V2.0 VRTA Device User Guide 49

50 9 VRTA CanTrcv Device 9.1 VRTA CanTrcv Overview The CAN Transceiver is a virtual device, which adapts the signal levels that are used on the CAN bus to the logical (digital) signal levels recognized by a microcontroller. It will support mainly AUTOSAR functionalities mentioned below. 13) SetOpMode 14) GetOpMode 15) GetBusWuReason 16) SetWakeupMode 17) CheckWakeup 18) GetVersionInfo Method: evevrtacantrcv () The constructor. evevrtacantrcv (const vrtatextptr name) name Input The name of the virtual device. This is the constructor used to create an instance of a VRTA CanTrcv device Method: CanTrcvIdleHandler () Used to raise the AUTOSAR API call when the Os is in Idle. Void CanTrcvIdleHandler () <None> This method is used to raise the AUTOSAR API call when the Os is in Idle. ETAS Virtual ECU V2.0 VRTA Device User Guide 50

51 Method: UpdateDetErrors () Updates the DET error status of all actions. Void UpdateDetErrors (uint8 det) det input The hex value for the error code This method is used to update the DET status of all actions or API calls in the module Method: UpdateCanTrcvResult () Update the Result of an action Void UpdateCanTrcvResult(vrtaUInt return_val) return_val Input Update the result, returned after the call of an API. This method will update the result of an API call or action. It could be E_OK or E_NOT_OK. Method: UpdateCurrentJob () Update the current job Void UpdateCurrentJob(uint8 job) job Input It will update the current job. This method will give the current job information by raising an event. It could be any of the AUTOSAR APIs defined for this module which are the actions in this design. ETAS Virtual ECU V2.0 VRTA Device User Guide 51

52 Method: UpdateCurrentStatus () Update the current mode a transceiver is operating in. Void UpdateCurrentStatus (CanTrcv_TrcvModeType trcv_status) trcv_status Input The operating mode of the transceiver This method will give the current status information of a transceiver by raising an event. It could be any of the three operating modes i.e. NORMAL, STANDBY, and SLEEP Method: UpdateWakeupMode () Update the wakeup mode a transceiver is currently in. Void UpdateWakeupMode (CanTrcv_TrcvWakeupModeType wu_mode) wu_mode Input The wakeup mode of the transceiver This method will give the current wakeup mode of a transceiver by raising an event. It could be any of the three modes i.e. ENABLE, DISABLE, and CLEAR. 9.2 s User can pass values to the VRTA CanTrcv device from an external application like vrtamonitor or a 3 rd party application to the VECU using s. Each action supported by a VRTA CanTrcv device is described by a standard table, as below, followed by text to explain the purpose of the action or event. ETAS Virtual ECU V2.0 VRTA Device User Guide 52

53 XXXX YYYY The table contains the numeric of the action or event (XXXX), and the format of the action or event data (YYYY) SetOpMode 1 %u,%u The action sets the transceiver to any one of the three operating modes. The arguments are the transceiver number and the Operating mode with values 0,1 and 2. Where, 0 represents CANTRCV_TRCVMODE_NORMAL 1 represents CANTRCV_TRCVMODE_SLEEP 2 represents CANTRCV_TRCVMODE_STANDBY GetOpMode 2 %u The action will get the operating mode of the transceiver. The only argument is the transceiver number GetBusWuReason 3 %u The action will get the reason for the wakeup call detected in a transceiver. The only argument is the transceiver number SetWakeupMode 4 %u,%u The action will set a particular transceiver to a particular wakeup mode. The arguments are the transceiver number and the wakeup mode whose values are 0,1 and 2 Where, 0 represents CANTRCV_WUMODE_ENABLE 0 represents CANTRCV_WUMODE_DISABLE 0 represents CANTRCV_WUMODE_CLEAR CheckWakeup ETAS Virtual ECU V2.0 VRTA Device User Guide 53

54 5 %u The action will be called if a wakeup interrupt is detected. The only argument is the transceiver number. 9.3 Events User can get values from the VECU to an external Application like vrtamonitor or a 3 rd party application using Events. There are two ways of doing this 12. Event Polling 13. Event Hooking Event Polling External application can poll the events in a vrtadevice to get the value of the event at that particular time. Event Hooking External application can also get notified automatically of some change in state/value by raising an event. For more information about the Polling and Hooking, Refer VRTA User Guide. Below are the Events that are supported by the VRTA CanTrcv Result Event 1 %u This event is raised when there is a change in the result CurrentJob Event 2 None SETOPMODE GETOPMODE GETBUSWUREASON SETWAKEUPMODE CHECKWAKEUP This event is raised when there is a change in the action called. It would be enumeration as seen from the above table DETErrors Event 3 None CANTRCV_E_INVAL_TRANSCEIVER CANTRCV_E_ PARAM_POINTER CANTRCV_E_UNINIT CANTRCV_E_TRC V_NOT_STANDBY CANTRCV_E_TRCV_NOT_NORMAL CA NTRCV_E_PARAM_TRCV_WAKEUP_MODE CANTRCV_E_P ARAM_TRCV_OPMODE This event is raised when there is a change in the DET error status. It would be enumeration as mentioned in the above table. ETAS Virtual ECU V2.0 VRTA Device User Guide 54