VECTOR VX1000 ARM TPIU ٹریس مائکروکنٹرولر
وضاحتیں
- پروڈکٹ کا نام: VX1000 ARM TPIU ٹریس
- ورژن: 1.0
- تاریخ: 2025-08-29
- مصنف: ڈومینک گنریبین
مصنوعات کی معلومات:
- The VX1000 ARM TPIU Trace is a tool used for measurement and calibration setups of microcontrollers. It provides a parallel trace port with single- or multi-pin data paths and a clock pin.
- تمام سگنل سنگل اینڈڈ ہیں۔
TPIU ٹریس اوورview:
- The TPIU Trace Interface consists of a parallel trace port with various pins, including Trace Clock and Data Pins 0-3. The Trace Clock typically operates at frequencies ranging from 25 MHz to 125 MHz, with data pins using DDR signaling for increased data rates.
TPIU ٹریس پروٹوکول:
- To enable the TPIU Trace, configuration within the ECU software is necessary. This includes pin configuration, multiplexer configurations, and trace clock configuration. Detailed instructions for these configurations can be found in the user manual.
مصنوعات کے استعمال کی ہدایات
- Setting up TPIU Trace:
- TPIU ٹریس انٹرفیس استعمال کرنے کے لیے، ان مراحل پر عمل کریں:
- Connect the TPIU Trace pins according to the specified pin assignments.
- Configure the ECU software settings for the Trace Pins interface as per VXconfig settings.
- پن کنفیگریشن:
- Configure the trace data pins and clock pin based on the target controller specifications. Refer to the provided code exampمدد کے لیے
- Multiplexer Configurations:
- If your evaluation board or ECU has multiplexers or DIP switches, ensure they are configured to select the TPIU-Trace. Refer to code exampمختلف تشخیصی بورڈز کے لیے
- Trace Clock Configuration:
- Set up the Trace Clock frequency by selecting the appropriate clock source and setting a divider to achieve the desired frequency. Refer to the user manual for detailed instructions.
VX1000 ARM TPIU ٹریس
- ARM specifies a parallel target interface for its microcontrollers.
- Depending on the frequency and the number of trace pins used, a significant measurement bandwidth can be achieved with the TPIU Trace Interface.
- Sometimes the TPIU trace is also referred to as Trace-Pin-Interface or ETM-Trace-Interface.
- The TPIU Interface is a unidirectional interface from the target controller to the Debugger/Measurement Hardware.
- TPIU انٹرفیس کو اسٹینڈ اکیلا استعمال نہیں کیا جا سکتا بلکہ ایک اضافی ٹارگٹ انٹرفیس جیسا کہ SWD یا JTAG ہدف تک تحریری رسائی کے لیے ضروری ہے۔
TPIU ٹریس اوورview
- The TPIU Trace Interface provides a parallel trace port with a single- or multi-pin data path and a clock pin.
- All signals are single ended.
TraceCLK:
- Trace Clock. Typical frequencies are 25 MHz .. 125 MHz.
- The TraceDx uses DDR signaling, transferring data on both clock edges to double the effective data rate. So, when in this document a Trace Clock frequency of 25 MHz is used, the data rate on each data pin is 50 Mbit/s.
TraceD0-TraceD3:
- Data Pins 0..3. If other target interface connectors are used, even more Trace Data Pins can be used if this is supported by the target controller (see 5.4 Typical connector used for TPIU Trace).
TPIU Trace Protocols
- The protocols used on the interface may differ depending on the target controller and the use cases.
- Typically, the TPIU Protocol is used as a container format for multiple data streams.
- Data streams wrapped in the TPIU protocol can be ARM protocols like Embedded Trace Macrocell (ETM), Instrumentation Trace Macrocell (ITM) or System Trace Macrocell (STM).
- The VX1000 hardware can decode the TPIU and encapsulated protocols on the fly.
- VX1000 and the VX1000 Application Driver use ETM, IT, M and STM to acquire measurement data efficiently.
ECU software configuration
- TPIU ٹریس کو فعال کرنے کے لیے، ECU سافٹ ویئر کے اندر کچھ کنفیگریشن کرنا ضروری ہے۔
اشارہ:
- The VXconfig settings for the Trace Pins interface, which are referenced in the following sections, can be found in VXconfig VX1000 device->POD->Trace Pins
پن کنفیگریشن
- Typically, there are no dedicated trace pins on the target controller, but the trace functionality is multiplexed with other peripheral functionalities on the same pin.
- To reduce the chance that the trace cannot be used as some required pins are blocked by other functionalities, the same trace-pin functionality is often routed redundantly to different pin groups.
- To enable trace, the target controller must be configured to provide pins with trace functionality, and the target PCB must be designed accordingly.
- کوڈ سابقampمختلف ٹارگٹ کنٹرولرز کے لیے پن کنفیگریشن کے لیے les "4. کوڈ Examples TPIU کنفیگریشن کے لیے"۔
- ان ٹریس پنوں میں ٹریس ڈیٹا پن (ٹریس_ڈیٹا) اور کلاک (ٹریس_کلک) پن شامل ہیں۔ مختلف VX1000 ہارڈویئر کے لیے ٹریس ڈیٹا پنوں کی تائید شدہ تعداد 5.8 ممکنہ TPIU سیٹ اپ میں مل سکتی ہے۔
- Multiplexer configurations
- اگر آپ کے ایویلیویشن بورڈ یا ای سی یو کے پاس کنٹرولر کے باہر ملٹی پلیکسرز یا ڈی آئی پی سوئچز ہیں تاکہ مختلف پیریفرل کنکشنز کے درمیان سوئچ کریں، تو ان کو بھی TPIU-Trace کو منتخب کرنے کے لیے کنفیگر کیا جانا چاہیے۔
- دیکھیں "4. کوڈ Examples for TPIU کنفیگریشن" for exampمختلف ایویلیویشن بورڈز۔
Trace Clock configuration - Besides the Trace-Clock pin configuration addressed in “2.1 Pin configuration”, the Trace_Clk must be configured to operate at the desired frequency.
- Typically, the clock tree contains a multiplexer to select from different clock sources, and frequency dividers to decrease the source frequency. Select the clock source and set a divider to achieve the desired frequency.
- To verify the TPIU Clock configuration, the VX1000 system measures the detected Trace_Clk signal and shows the result in VXconfig.
- The values are updated on VX1000 reset or ECU reset. So, there is no need to connect an Oscilloscope to double-check the TPIU frequency.
- The VX1000 provides three ways to configure the TPIU Clock, which are described in the following sections.
- The registers that are configured for TPIU Clock MUX and Divider are explained in “4. Code Examples for TPIU Configuration” for the specific controllers.
- Either the VX1000 hardware can configure the registers from the outside through JTAG/SWD (دیکھیں 2.3.1 اور 2.3.2)، یا رجسٹرز ایپلیکیشن کے ذریعے کنفیگر کیے گئے ہیں (دیکھیں 2.3.3)۔
- Use VX1000 defaults
- When using “VX1000 defaults”, the VX1000 hardware configures the multiplexer and clock divider in the target in an educated guess approach.
- Typically, clock sources are selected that are expected to be in use in the target, like clocks for cores or the system clock.
- The VX1000 uses the divider, which results in the maximum possible Trace_Clk frequency supported by the controller.
- Because the controller and especially the clock tree can be configured in different ways, this setting will not always lead to the expected results.
- Use the “Last detected frequency” information in VXconfig to verify the resulting frequency. If the trace clock is not as expected, see the following sections.
VXconfig settings
- If actual values are provided in VXconfig, the VX1000 hardware will set TPIU Clock MUX and TPIU Clock Divider without the need to modify the ECU software.
- This allows an easy probing of different settings. Use the “Last detected frequency” to verify that the resulting frequency meets your expectations.
Use ECU settings
- While with the previous configuration modes the VX1000 hardware actively configures the TPIU Clock in the target, the VX1000 can also be put in passive mode by selecting “Use ECU Settings”.
- In this case, the ECU software must configure the complete Trace Pin interface, as the VX1000 will not modify the clock configuration.
- Please note that the trace sources like STM500, ETM and ITM are still configured by the VX1000 and must not be accessed by the ECU application.
ٹپ: To verify your settings, boot the target system with the VX1000 disconnected and check with an oscilloscope that the Trace_Clk pin on the target connector is toggling at the expected rate.
VX1000 ایپلیکیشن ڈرائیور کنفیگریشن
- To use the ARM TPIU trace feature, the VX1000 Application Driver must be included into the Target Controller software. This software is delivered as source code and can be integrated easily.
- The required configuration options that are needed for the TPIU Trace are listed here. Target controller-specific settings are listed in “4 Code Examples for TPIU Configuration“ in the “Target Specific Application Driver Configuration” sections.
کارکردگی کے تحفظات
- The measurement methods used with the TPIU Trace interface are all copy-based approaches.
- This means that the data must be copied by the CPU from its original location to a destination where the Trace messages are generated and sent via the TPIU interface.
- The involved trace protocols also consume some bandwidth of the target interface and must be considered.
- Please note that our OLDA copy methods typically consume a CPU runtime of
Target Interface Bandwidth
- Due to the number of different setups, the following table provides an overview اصل ہدف انٹرفیس بینڈوتھ کا۔ بینڈوتھ ExampSTM500 کے لیس
تعطل ۔
- All the trace protocols utilizing the TPIU Interface are configured by the VX1000 in such a way that stalling is enabled. This means that no data can get lost due to target interface bandwidth limitations.
- If the data is copied faster than the interface bandwidth, the CPU is stalled/paused until there is space available on the target interface.
- The trace paths typically include buffers that help smooth out copy bursts, thereby reducing the likelihood of stalling. Please consult the target reference manual of your controller for details.
- نتیجے کے طور پر، TPIU انٹرفیس کو زیادہ سے زیادہ ممکنہ فریکوئنسی کے ساتھ استعمال کیا جانا چاہیے اور زیادہ سے زیادہ ٹریس پنوں کا استعمال کیا جانا چاہیے تاکہ اسٹالنگ کے منفی اثرات کو کم کیا جا سکے۔
کوڈ سابقamples TPIU کنفیگریشن کے لیے
- The pseudo-code exampسیکشن میں les آپ کو DAQ پیمائش اور کیلیبریشن کے استعمال کی تیاری میں TPIU-Subsystem کو کنفیگر کرنے کے طریقے کے بارے میں اشارے دینے چاہئیں۔
ٹیکساس کے آلات
- سیوڈو کوڈ سابقamples use names from the TI-SDK ,which is copyrighted of Texas Instruments. Please refer to the TI-SDK documentation.
AM263
- AM263 TPIU Specification
- AM263 Trace-Pin configuration
اضافی اشارے:
- Pins must be configured with PIN_SLEW_RATE_HIGH
- AM263 Target Specific Application Driver Configuration
Pseudo-Code
J6E
J6E TPIU Specification
J6E Trace-Pin configuration
اضافی اشارے:
- For high clock frequencies, configure the outputs with PORT_DRIVE_STRENGTH_15
J6E Target Specific Application Driver Configuration
VX1000_MEMSYNC_TRIGGER_PTR
- // #define VX1000_MEMSYNC_TRIGGER_PTR <user defined>
- اس چپ کے لیے، VX1000 ETM ٹریس کا استعمال کرتا ہے اور لکھنے کے قابل ایڈریس اسپیس (8 بائٹ الائنڈ) کے کسی بھی صوابدیدی 16 بائٹ بلاک کے ساتھ کام کر سکتا ہے، جسے خصوصی طور پر ایپلی کیشن ڈرائیور استعمال کرتا ہے۔
- اگر آپ VX1000_MEMSYNC_TRIGGER_PTR کی وضاحت نہیں کرتے ہیں، تو یہ بلاک خود بخود gVX1000 میموری کی حد میں مختص ہو جاتا ہے۔
- VX1000_MEMSYNC_TRIGGER_PTR کی وضاحت کرکے اور تیز تر (TCM) یا کیشڈ میموری میں بفر فراہم کرکے پیمائش کے تھروپپٹ کو بہتر بنانا ممکن ہے۔
TDA4M/J721E
- TDA4 TPIU Specification
- TDA4 Trace-Pin configuration
اضافی اشارے:
- Access from MCU cores to STM500 goes through the R5-RAT address translation module. The application driver setting VX1000_MEMSYNC_TRIGGER_PTR is an address in the MCU address space and must translate to address 0x0009000110 in MAIN
- address space (which is a stimulus port of the STM-500 trace unit). In the example below, the RAT is programmed to use the same address in both domains.
- TDA4 Target Specific Application Driver Configuration
- VX1000_MEMSYNC_TRIGGER_PTR
- #define VX1000_MEMSYNC_TRIGGER_PTR (0x09000000 + 0x110)
Pseudo-Code
VX1000 hardware adaptation
- The hardware connection is driven by the number of pins, used trace frequency and the used VX1000 hardware. In the following section, possible target controller connectors are explained alongside a description how a setup with the VX1000 can look like.
- Available VX1000 adapter and Evalboard Evaluation Kit Heads (EEK-Heads) are described, and possible use cases are explained.
والیومtagای سطحیں
- TPIU انٹرفیس کو اسٹینڈ اکیلا استعمال نہیں کیا جا سکتا بلکہ ایک اضافی ٹارگٹ انٹرفیس جیسا کہ SWD یا JTAG ہدف تک تحریری رسائی کے لیے ضروری ہے۔
- In some situations, the voltagSWD/J کی e لیولزTAG انٹرفیس اور TPIU پن مختلف ہیں کیونکہ ٹارگٹ کنٹرولر کے مختلف بینک استعمال کیے جاتے ہیں، اور مختلف I/O بینکوں کا حجم مختلف ہو سکتا ہے۔tagای لیولز
- Setups that can cope with different voltage سطحوں کو واضح طور پر نمایاں کیا گیا ہے۔
Flat Ribbon cables
- Many setups are designed in a way that flat ribbon cables can be used. This ensures an easy, flexible, and cheap way to connect the VX1000 POD with the evaluation board/ECU. The maximum frequency allowing stable communication is limited to 100 Mhz.
- Even though flat ribbon cables can easily be made at any desired length, they should always be kept as short as possible to avoid interference.
- Flex-Ribbon cables are mostly symmetrical, meaning that both ends have the same number of pins/cables.
- An asymmetrical usage is also possibl,e meaning that one side has more pins connected as the other side. This allows the flexible adaptation of e.g., a 44-pin connector to a 20-pin connector.
Customized Flex PCB
- ان منصوبوں کے لیے جن میں فلیٹ ربن کیبلز کافی نہیں ہیں، Vector پروجیکٹ کی ضروریات کو پورا کرنے کے لیے اپنی مرضی کے مطابق Flex-PCBs کو ڈیزائن اور تیار کرنے کے لیے ایک ترقیاتی خدمت فراہم کرتا ہے۔
Typical connector used for TPIU Trace
- پنوں کو خاص معنی کے ساتھ نشان زد کرنے کے لیے یہ رنگ استعمال کیے جاتے ہیں۔
ARM Coresight 20
- Link to ARM specification: https://developer.arm.com/documentation/100893/1-0/Target-interface-connectors/CoreSight-20-connector
ARM Mictor 38
Link to ARM specification: https://developer.arm.com/documentation/100893/1-0/Target-interface-connectors/Mictor-38-connector
VX1000 کے ذریعے استعمال نہیں کیے گئے سگنلز:
- ڈی بی جی آر کیو
- DBGACK
- EXTTRIG
- آر ٹی سی کے
- TRACECTL
ARM MIPI60
- Link to ARM specification: https://developer.arm.com/documentation/100893/1-0/Target-interface-connectors/MIPI-60-connector
Vector “Coresight 44”
- The Coresight 44 connector is a Vector-defined connector. This connector is used as Target Interface Connector on the relevant EEK-Heads and PODs.
Vector Adapter
- VX1000 کے ساتھ مل کر TPIU انٹرفیس کے استعمال کو آسان بنانے کے لیے Vector سب سے اہم ہدف کنیکٹرز کے لیے اڈاپٹر فراہم کرتا ہے۔
VX1940.10: Mipi 60 Adapter
VX1940.11: Mictor 38 Adapter
Vector EEK Heads
VX1902.09 EEK Head
- TPIU/Trace انٹرفیس کے لیے ہارڈویئر موافقت عام طور پر VX1902.09 ہیڈ کے ذریعے حاصل کی جاتی ہے۔
- کوریسائٹ 44
- ویکٹر ملکیتی POD کنیکٹر
Vector Flex Adapter
- POD اور EEK ہیڈز کے درمیان تعلق کو Flex Adapter VX1901.01 کے ساتھ محسوس کیا جاتا ہے۔
Possible TPIU Setups
- Setups for VX1453
نوٹ
- The VX1453 POD supports TPIU trace from hardware revision 7.0 onwards.
Coresight 20 Setup
Asymmetric Flat Ribbon cable
MIPI 60 Setup Flat Ribbon
فلیٹ ربن کیبل 44:44 پن
Customized FlexPCB Setups
مزید معلومات
- رابطے
- دنیا بھر میں ویکٹر کے تمام مقامات اور پتوں کے ساتھ مکمل فہرست کے لیے، براہ کرم ملاحظہ کریں۔ http://vector.com/contact/.
- www.vector.com
اکثر پوچھے گئے سوالات
دستاویزات / وسائل
 |
VECTOR VX1000 ARM TPIU ٹریس مائکروکنٹرولر [پی ڈی ایف] ہدایات دستی VX1000، VX1000 ARM TPIU ٹریس مائیکرو کنٹرولر، ARM TPIU ٹریس مائیکرو کنٹرولر، ٹریس مائیکرو کنٹرولر، مائیکرو کنٹرولر |