Vector Informatik GmbH
Ingersheimer Straße 24
D-70499 Stuttgart
The information and data given in this user manual can be changed without prior notice. No part of this manual may be reproduced in any
form or by any means without the written permission of the publisher, regardless of which method or which instruments, electronic or
mechanical, are used. Alltechnicalinformation, drafts, etc. are liable to law of copyright protection.
4.5.11.4 Channel in TAP Mode215
TAP Initialization216
I2C Architecture217
Detection of TAP by ECU Firmware for Measurement Mode218
GPIO Interconnect218
4.5.11.5 Channel in RX Mode219
Initialization220
I2C Architecture221
GPIO interconnect221
4.5.11.6 Required Serializer and Deserializer Settings222
CSI Continuous Clock on CH1 and CH3222
CSI Continuous Clock on CH2 and CH4222
CSI Clock Lane Speed223
CSI Signal Settings223
4.5.11.7 POC Supply223
4.5.11.8 Technical Data224
4.5.12 VX1161.51B 4xRX FPDLINK3 TI954/TI954225
4.5.12.1 Connectors225
4.5.12.2 LEDs226
4.5.12.3 Boot and Link-up-Time227
4.5.12.4 Channel in RX Mode228
Initialization228
I2C Architecture229
GPIO Interconnect230
4.5.12.5 Required Serializer and Deserializer Settings231
CSI Continuous Clock on CH1 and CH3231
CSI Clock Lane Speed231
CSI Signal Settings231
VX1000 ManualVersion 4.36
Contents
4.5.12.6 POC Supply231
4.5.12.7 Technical Data232
4.5.13 VX1161.51C 2xTAP GMSL2 MX9296A/MX9295A233
4.5.13.1 Connectors234
4.5.13.2 LEDs234
4.5.13.3 Boot and Link-up-Time235
4.5.13.4 Channel in TAP Mode236
TAP Initialization237
I2C Architecture238
Detection of TAP by ECU Firmware for Measurement Mode239
MFP Interconnect240
4.5.13.5 Channel in RX Mode242
Initialization242
I2C Architecture243
MFP Interconnect244
4.5.13.6 Sensor Trigger Generator246
4.5.13.7 Required Serializer and Deserializer Settings247
CSI Continuous Clock on CH1 and CH3247
CSI Continuous Clock on CH2 and CH4247
CSI Clock Lane Speed247
CSI Lock Signals on MFP Pins247
CSI Signal Settings247
4.5.13.8 POC Supply248
4.5.13.9 Technical Data248
4.5.14 VX1161.51D 4xRX GMSL2 MX9296249
4.5.14.1 Connectors250
4.5.14.2 LEDs250
4.5.14.3 Boot and Link-up-Time251
4.5.14.4 Channel in RX Mode252
Initialization252
I2C Architecture253
MFP Interconnect254
4.5.14.5 Sensor Trigger Generator257
4.5.14.6 Required Serializer and Deserializer Settings258
CSI Continuous Clock on CH1 and CH3258
CSI Continuous Clock on CH2 and CH4258
CSI Clock Lane Speed258
CSI Lock Signals on MFP Pins258
CSI Signal Settings258
4.5.14.7 POC Supply259
4.5.14.8 Technical Data259
4.5.15 Inserting or Removing VX1161 Cards260
4.5.15.1 General Notes260
4.5.15.2 Removing VX1161 Cards260
4.5.15.3 Removing Slot Covers261
4.5.15.4 Installing VX1161 Cards261
4.5.15.5 Installing Slot Covers261
4.5.16 Calculation and Scripting Language (CASL)262
9.3.1 Grounds and Shield inside VX Base Modules434
9.3.2 Grounds inside a POD435
9.3.3 Disconnecting an ECU from its Power Supply436
9.3.3.1 #1: Normal Operation437
9.3.3.2 #2: Disconnection437
VX1000 ManualVersion 4.312
Contents
9.3.3.3 #3: Short437
9.3.3.4 #4: Current in VX Base Module438
9.3.3.5 #5: Current in POD Housing438
9.3.3.6 #6: Current through POD Housing439
9.3.3.7 Conclusion439
9.4 Environmental Aspects440
9.5 Cabling441
VX1000 ManualVersion 4.313
1Introduction
In this chapter you find the following information:
1.1 About this User Manual15
1.1.1 Warranty16
1.1.2 Registered Trademarks16
1.2 Important Notes17
1.2.1 Safety Instructions and Hazard Warnings17
1.2.2 Disclaimer18
VX1000 ManualVersion 4.314
1.1 About this User Manual
1.1About this User Manual
ConventionsIn the two following charts you will find the conventions used in the user manual
regarding utilized spellings and symbols.
StyleUtilization
boldBlocks, surface elements, window- and dialog names of the soft-
ware. Accentuation of warnings and advices.
[OK]
File|Save
Source Code
HyperlinkHyperlinks and references.
<CTRL>+<S>Notation for shortcuts.
SymbolUtilization
File name and source code.
This symbol calls your attention to warnings.
Push buttons in brackets
Notation for menus and menu entries
Here you can obtain supplemental information.
Here you can find additional information.
Here is an example that has been prepared for you.
Step-by-step instructions provide assistance at these points.
Instructions on editing files are found at these points.
This symbol warns you not to edit the specified file.
VX1000 ManualVersion 4.315
1.1.1 Warranty
1.1 About this User Manual
Restriction
of warranty
We reserve the right to change the contents of the documentation and the software
without notice. Vector Informatik GmbH assumes no liability for correct contents or
damages which are resulted from the usage of the documentation. We are grateful for
references to mistakes or for suggestions for improvement to be able to offer you
even more efficient products in the future.
1.1.2 Registered Trademarks
Registered
trademarks
All trademarks mentioned in this documentation and if necessary third party
registered are absolutely subject to the conditions of each valid label right and the
rights of particular registered proprietor. All trademarks, trade names or company
names are or can be trademarks or registered trademarks of their particular proprietors. All rights which are not expressly allowed are reserved. If an explicit label of
trademarks, which are used in this documentation, fails, should not mean that a name
is free of third party rights.
► Windows, Windows 7, Windows 8.1, Windows 10
are trademarks of the Microsoft Corporation.
VX1000 ManualVersion 4.316
1.2Important Notes
1.2.1 Safety Instructions and Hazard Warnings
Caution!
In order to avoid personal injuries and damage to property, you have to read and
understand the following safety instructions and hazard warnings prior to installation and use of this hardware. Keep this documentation (manual) always near the
hardware.
1.2.1.1 Proper Use and Intended Purpose
Caution!
The hardware is designed for analyzing, controlling and otherwise influencing control systems and electronic control units. This includes bus systems like CAN,
FlexRay, Ethernet and/or BroadR-Reach.
1.2 Important Notes
The hardware may only be operated (i) according to the instructions and descriptions of this manual; (ii) with the electric power supply designed for the hardware,
e.g. USB-powered power supply; and (iii) with accessories manufactured or
approved by Vector.
The hardware is exclusively designed for use by skilled personnel as its operation
may result in serious personal injuries and damage to property. Therefore, only
those persons may operate the hardware who (i) have understood the possible
effects of the actions which may be caused by the hardware; (ii) are specifically
trained in the handling with the hardware, bus systems and the system intended to
be influenced; and (iii) have sufficient experience in using the hardware safely.
The knowledge necessary for the operation of the hardware can be acquired in
work-shops and internal or external seminars offered by Vector. Additional and
hardware specific information, such as „Known Issues“, are available in the „Vector
KnowledgeBase“on Vector´s website at www.vector.com. Please consult the
„Vector KnowledgeBase“for updated information prior to the operation of the hardware.
VX1000 ManualVersion 4.317
1.2.1.2 Hazards
1.2 Important Notes
Caution!
The hardware may control and/or otherwise influence the behavior of control systems and electronic control units. Serious hazards for life, body and property may
arise, in particular, without limitation, by interventions in safety relevant systems
(e.g. by deactivating or otherwise manipulating the engine management, steering,
airbag and/or braking system) and/or if the hardware is operated in public areas
(e.g. public traffic, airspace). Therefore, you must always ensure that the hardware
is used in a safe manner. This includes, inter alia, the ability to put the system in
which the hardware is used into a safe state at any time (e.g. by „emergency shutdown“), in particular, without limitation, in the event of errors or hazards.
Comply with all safety standards and public regulations which are relevant for the
operation of the system. Before you operate the system in public areas, it should
be tested on a site which is not accessible to the public and specifically prepared
for performing test drives in order to reduce hazards.
1.2.2 Disclaimer
Caution!
Claims based on defects and liability claims against Vector are excluded to the
extent damages or errors are caused by improper use of the hardware or use not
according to its intended purpose. The same applies to damages or errors arising
from insufficient training or lack of experience of personnel using the hardware.
VX1000 ManualVersion 4.318
2VX1000 System Overview
In this chapter you find the following information:
2.1 Overview20
2.2 VX1000 System Components21
2.3 Supported Microcontrollers22
2.4 Features23
2.5 VX1000 Application Driver and VX1000If24
VX1000 ManualVersion 4.319
2.1 Overview
Target µCPODBase Module
MC Tool
e. g. CANape
HSSL/Serial CableXCP on
Ethernet
VX0312
CANape
BroadR-ReachUSB 2.0
ECU
XPOD
2.1Overview
At a glanceThe VX1000 System is a scalable solution with top performance for your mea-
surement and calibration tasks. It can be used in the vehicle – both in the interior and
in the engine compartment – on test benches and in the laboratory.Especially when
developing ADAS ECUs, this allows you to control raw data captured by high-resolution radar sensors in combination with XCP data, e.g. object/tracking lists.
The system forms the interface between the ECU and a measurement and calibration
tool such as CANape.For high data throughput with minimal impact on ECU run-time,
data is accessed over the microcontroller-specific data trace and debug ports.
The VX1000 Base Module is connected to the PC over XCP on Ethernet, an OEMindependent ASAM standard (www.asam.net) that is widely used in the automotive
industry. The VX1000 measurement hardware is connected to the ECU via a POD
(Plug-On device).Depending on the available microcontroller interface, either the data
trace or a copying method can be used to acquire measurement data.
Figure 1: Modular concept
Modular conceptThe modular concept of the VX1000 System allows connecting to different micro-
controllers and consists of the following components:
► VX1000 Base Modules
► VX1300 Cables (HSSL/Serial Cable)
► VX1400/VX1500 Plug-On Devices (POD)
To support longer distances between the VX1000 Base Module and the target ECU,
e.g. under the hood in a car, the Base Module is connected to the ECU via a POD and
a cable that is available in different lengths.PODs and cables are designed to withstand rough automotive environmental conditions.
XPODWith the XPOD, the VX1000 System also offers a standalone measurement and cal-
ibration interface without the need of a VX1000 Base Module.
Figure 2: Example with XPOD
AdvantagesAdvantages of the VX1000 System are:
► Powerful measurement and calibration access to internal ECU data with max-
imum transmission rates
► Very small POD to connect to the ECU debug interface
► Easy and quick integration into the ECU software
► No impact on ECU run-time with data trace measurement method
► Interface to numerous development tools by third-party suppliers via the stand-
ardized ASAM protocol XCP on Ethernet
► Special functions for engine controllers such as Calibration Wake-Up and Cal-
ibration RAM Supply
VX1000 ManualVersion 4.320
2.2VX1000 System Components
Base Modules► VX1060 Serial Base Module (page 55)
► VX1132 Base Module (page 71)
► VX1134 Base Module (page 110)
► VX1135 Base Module (page 128)
► VX1161 Multi Base Module (page 175)
2.2 VX1000 System Components
Plug-On Devices
(PODs)
Cables► VX1311 Serial2 Cables for VX1544 Serial PODs (page 418)
► VX1544A/B Serial POD (DAP/DAP2, JTAG, HSCT, Zipwire) (page 344)
► VX134x Serial Cables and Cable Pigtails for VX154x Serial PODs (page 418)
► VX136x CAN Cables for Base Modules (page 410)
► VX137x HSSL Cables and Cable Pigtails for VX145x HSSL PODs (page 414)
► VX1381 HSSL2 Cables and Cable Pigtails for VX1453 HSSL PODs
► VX0312 Ethernet/CAN Interface
Figure 3: VX1000 Familyexamples
VX1000 ManualVersion 4.321
2.3Supported Microcontrollers
This section contains a list of all currently supported microcontroller families. Please
contact Vector VX support (VXsupport@vector.com) for further information on supported microcontrollers and implemented features.
PowerPC xPC5xxxJTAG Class 2+/ ZipwireAuroraPowerPC MPC57xx-Aurora-
Renesas
RH850JTAG Class 2+AuroraV850E2JTAG Class 2+--
Texas Instruments
TMSx70-RTP/DMM-
VX154x
Serial PODs
VX145x
HSSL PODs
VX1621A
XPOD
VX1000 ManualVersion 4.322
2.4 Features
2.4Features
Overview► Very high measurement data throughput of more than 100 MByte/s for XCP data
and radar raw data with data trace measurement method and up to 3 MByte/s with
the copying method
► Measurement of fast signal cycles (>10 μs for data trace, 40 μs for copying
method)
► Measurement configurations with up to 100,000 signals can be processed
► Precise generation of DAQ time stamps in the ECU
► ECU cold start measurement (First Loop DAQ)
► Calibration of ECU parameters without address range limitations
► Calibration memory page switching
► Automatic overlays when calibrating parameters in flash memory
► Stimulation or bypassing with short latency times
► 100Mbps/1Gbps/10Gbps Ethernet connection to the PC
► Galvanically isolated power supply with wide input voltage range
► POD power supply via the VX1000 Base Module
► Optional: Flash programming, even for “brain-dead” ECUs
► Optional: FlexRay and CAN channels via XL Driver Library for CANape/CANa-
lyzer/CANoe and custom applications
► PC tools for easy configuration and for software updates
► Target debugging over XCP
VX1000 ManualVersion 4.323
2.5 VX1000 Application Driver and VX1000If
2.5VX1000 Application Driver and VX1000If
VX1000 Measurement and Calibration access to the ECU requires not only the appropriate VX1000 hardware but also the target-specific VX1000 Application Driver (in
short: VX1000 AppDriver) which must be integrated into the ECU software.
The VX1000 AppDriver has been developed for test and development purposes but
not for use in production software. However, the VX1000 AppDriver is always used in
conjunction with the module VX1000If which encapsulates access from the application to the VX1000 AppDriver.
Figure 4: Application components
VX1000If provides an API through which, during runtime, the VX1000 AppDriver can
be activated for test and development purposes. Through this API the VX1000
AppDriver can also be put into a deactivated state in which it can potentially remain in
production software. Vector can only grant permission to use VX1000If and a thereover deactivated VX1000 AppDriver in production software, if VX1000If is delivered
through a MICROSAR SIP.
The VX1000 AppDriver is delivered through VXsupport@vector.com free of charge.
This delivery also contains a version of VX1000If and the technical reference required
for a complete and safe integration into the ECU software. This enables an integration
for test and development purposes, or an early prototype integration with exchanging
VX1000If later. Both the VX1000 AppDriver and VX1000If delivered this way, are subject to the attached terms and conditions which must be accepted on a per-project
base. These terms and conditions do not grant permission for usage in production
ECUs.
By means of a MICROSAR SIP, only VX1000If is delivered. Depending on the delivery, clearance for the usage in safety-critical ECUs up to ASIL-D can be granted. For
safe usage in a production ECU, the VX1000If version delivered through the
MICROSAR SIP must be used, including its technical specification.
Regarding VX1000If, usually there is no difference between the source code and technical reference of the MICROSAR SIP, or the version that is part of the VX1000
AppDriver. So, the effort for exchanging this component is usually very low. However,
care must be taken to diligently examine potential differences.
VX1000 ManualVersion 4.324
3VXtools
In this chapter you find the following information:
3.1 VXupdate26
3.1.1 General Information26
3.1.2 Menu Bar26
3.1.3 Toolbar28
3.1.4 VX Device List29
3.1.5 VX Configuration Selector30
3.1.6 Image List31
3.1.7 Flash Update31
3.1.8 Status Bar32
3.2 VXconfig33
3.2.1 General Information33
3.2.2 Menu Bar34
3.2.3 Toolbar37
3.2.4 Device List38
3.2.5 Status Bar39
3.3 VXconsole40
3.3.1 General Information40
3.3.2 Toolbar41
3.3.3 LEDs42
3.3.4 Message Window42
3.3.5 Command Bar42
3.3.6 Status Bar43
3.4 HowTo44
3.4.1 VXtools Setup44
3.4.2 VX Device First Steps45
3.4.3 VX device IP Address Configuration46
3.4.4 FPGA and Firmware Update49
3.4.5 Write VXparameter File to VX device50
VX1000 ManualVersion 4.325
3.1 VXupdate
3.1VXupdate
3.1.1 General Information
VXupdateVXupdate is the tool for updating VX1000 Systems by flashing VXimage files and
VXparameter files. It can be found in Start | Programs | Vector VXtools | VXup-
date after installation.
3.1.2 Menu Bar
File menu
► Select VXcontainer or VXimage or VXconfigurationSet…
This dialog allows selecting an individual .vxi VXimage, a .vxc VXcontainer or a
.vxp VXconfigurationSet. The VXimages and the parameter sets, which are
found and apply to the selected VX device, will be displayed in the Image List
view. If a VXconfigurationSet is selected the available VXconfigurations will be
listed in the VX Configuration Selector (see section VXconfiguration Selector).
Note
File types for the VX1000 System are:
.vxp VXconfigurationSet containing one or more VXconfigurations consisting of
VXimages and VXparameter files - can also be used to modify the IPaddress of a
VX device.
.vxc VXcontainer with a set of VXimage files for the VX1000 System.
.vxi VXimage file for the VX1000 System containing an FPGA or Firmware image
for a Base Module or a POD.
VX1000 ManualVersion 4.326
Options menu
Commands menu
3.1 VXupdate
► Last used VXcontainer
Lists already used VXcontainers or VXconfigurationSets. The user can select and
load one of them.
► Load VXparameter file
Loads a VXparameter set into the selected VX device.
► Exit
Closes VXupdate.
► Minimize to System tray
If this option is enabled, an icon will be added to the System tray.
When VXupdate is minimized, it will be removed from the Taskbar and can be
restored via the System tray icon.
► Scan for VX devices
Scans the network for VX devices. Found devices are shown in the Device List
view.
► Change IP address…
Changes the IP address of the selected VX device.
► Open VXconsole…
Opens VXconsole to display VX1000 System debug messages of the selected VX
device. This information is helpful for Vector support requests.
► Flash files…
Starts the flash update process (see section Flash Update)
VX1000 ManualVersion 4.327
Help menu
3.1 VXupdate
► Screenshot | Complete Desktop
Takes a screenshot of the whole Desktop and shows the location of the created
png file.
► Screenshot | VXupdate
Takes a screenshot of the VXupdate window and shows the location of the created png file.
► Support mail…
Creates a debug information file and opens a new E-Mail window in your default EMail client addressed to the Vector VX support (VXsupport@vector.com). Please
also include an issue description in the message body.
► Folders | User Data
Opens the Windows Explorer with the VXupdate User Data folder.
► Folders | Program Data
Opens the Windows Explorer with the VXupdate program folder.
► Manual | Manuals
Displays the installed VX1000 System Manuals and also offers a dialog to download further manuals.
► Manual | Application Notes
Displays the installed VX1000 Application Notes and also offers a dialog to download further VX1000 Application Notes.
► About…
Shows details of the VXupdate version.
3.1.3 Toolbar
Toolbar
► Scan
Scans the network for VX devices. Found devices are shown in the Device List
view.
► Broadcast
Sets the broadcast address for VX device scans. This parameter limits the scan to
a subnet (e.g. to a single network adapter) or covers all network adapters when a
value of 255.255.255.255 is used. Reasonable values can be found in the dropdown menu. If only one specific device should be found, its IP address can be
entered.
VX1000 ManualVersion 4.328
3.1.4VX Device List
General informationThe Device List view displays all found VX devices in the network:
Device Status► Status
The following device states are possible, after a scan has been executed:
3.1 VXupdate
StatusDescription / Possible problems
Device Info► System
Displays the type of the found VX device.
► SN
Displays the serial number of the found VX device.
► IP
Displays the IP address of the found VX device.
► Project
Displays the Project ID of the POD connected to the VX device.
► VX device in normal operation.
► VX device contains valid VXimages for all of its hardware components.
► VX device contains an incompatible or outdated Firmware or FPGA
Image for at least one of its hardware components.
► Update the FPGA and Firmware Images (see section
FPGA and Firmware Update).
► VX1000 Fallback Firmware is active.
► Update the FPGA and Firmware Images (see section
FPGA and Firmware Update).
► VX device has invalid network settings.
► Correct the network settings of the VX1000 System (see
section VX1000 System IP Configuration).
► XCP slave is already in use by another XCP master (Measurement
tool).
ECU Info► ECU µC
Displays the detected microcontroller type of the ECU connected to the selected
VX device.
VX1000 ManualVersion 4.329
► ECU ID
Displays the ECU-ID string defined in the VX1000 AppDriver of the ECU connected to the selected VX device.
3.1.5 VX Configuration Selector
3.1 VXupdate
Configuration
Selector
When a VXconfigurationSet (.vxp) is loaded – via the File menu or via drag and drop –
the available configurations and their descriptions are shown in this view. By clicking
on one of the configuration sets the corresponding images and parameters are loaded
into the Image List view (update version column) and are available for flash programming into the VX device.
VX1000 ManualVersion 4.330
Loading...
+ 412 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.