Vector VN8970 User Manual download pdf (Page 30)

Solution approach

In order to analyse data extracted from the ECU via the JTAG debugger in the regu-

lar testing environment, CANoe, the data has to be shifted from the JTAG debugger

software, Trace32, to CANoe. Two main approaches where considered trying to

achieve this, see Sections 5.1 and 5.2.

Common for the two approaches are that the JTAG debugger is connected to the

user PC via USB.

5.1 RS232 approach

Serial communication (in this case RS-232) ports are available to use with the Vector

hardware in the form of USB-to-Serial adaptors and furthermore CAPL has func-

tions deﬁned to handle serial communication. When the data has been extracted

from the serial port it is trivial to write it to speciﬁc system variables from which

it can be used during testing. So how do we provide the Vector hardware with the

serial data?

Trace32 is provided with an API so that one can write an application controlling

the software and the debugger. With the API functions it is possible to extract data

from the ECU to your application, process it and send it on the computer’s serial

port.

This is a ”straight forward” approach that is easy to understand and overview,

see Figure 5.1. The drawback is that RS-232 is only capable of quite slow trans-

mission speeds - in test cases where timing is important a high bandwidth is of

essence - and that it introduces new hardware in terms of a cable from the PC to the

Vector hardware. Furthermore the application extracting the data from Trace32 and

sending it on the serial port has to be started and operated by the tester, hence this

approach is not as transparent from the tester’s point of view as wished. Therefore

this approach is here after considered as secondary.

1 2 ... 25 26 27 28 29 30 31 32 33 34 35 ... 66 67

No comments

Vector VN8970 User Manual Page 30