simulator for tricore - lauterbach

Simulator for TriCore

TRACE32 Online Help

TRACE32 Directory

TRACE32 Index

TRACE32 Documents ......................................................................................................................

TRACE32 Instruction Set Simulators ..........................................................................................

Simulator for TriCore ................................................................................................................. 1

TRACE32 Simulator License .................................................................................................. 5

Brief Overview of Documents for New Users ....................................................................... 5

Example Scripts ...................................................................................................................... 5

Quick Start ............................................................................................................................... 6

1. Select the Device Prompt B: for the ICD Debugger 6

2. Select the CPU Type to load the CPU specific Settings 6

3. Enter Debug Mode 6

4. Load your Application Program 6

5. Write a Start-up Script 7

OCDS-L1 Debugger ................................................................................................................. 8

Troubleshooting 8

Memory Classes 9

Breakpoints 10

Examples for Breakpoints 10

Trace ......................................................................................................................................... 11

FAQ ........................................................................................................................................... 12

CPU specific Trace Commands ............................................................................................. 13

Analyzer.Mode PCP Select PCP trace 13

SYStem.Option DataTrace Enable data tracing 13

SYStem.Option INTSTART Start address of interrupt routines 13

SYStem.Option INTUSE Number of implemented interrupts 13

SYStem.Option MCDSKeyHigh Key (high part) for unlocking MCDS 13

SYStem.OptionMCDSKeyLow Key (low part) for unlocking MCDS 13

SYStem.Option TRAPSTART Start address of trap vectors 13

CPU specific SYStem Commands ......................................................................................... 14

SYStem.CONFIG Configure debugger according to target topology 14

SYStem.CONFIG.DAP.BreakPINS Define mapping of break pins 14

SYStem.CONFIG.DAP.DAPENable Enable DAP mode on PORST 14

SYStem.CONFIG.DAP.USERn Configure and set USER pins 14

Simulator for TriCore 1 ©1989-2018 Lauterbach GmbH

SYStem.CONFIG.Interface Set debug cable interface mode 14

SYStem.CPU Select CPU 15

SYStem.CpuAccess Run-time CPU access (intrusive) 15

SYStem.JtagClock Set the JTAG frequency 16

SYStem.LOCK Tristate the JTAG port 16

SYStem.MemAccess Run-time memory access (non-intrusive) 17

SYStem.Mode Establish the communication with the CPU 18

SYStem.Option CPU specific commands 19

SYStem.Option DCFREEZE Do not invalidate cache 19

SYStem.Option DIAG Diagnosis function 19

SYStem.Option DUALPORT Run-time memory access for all windows 19

SYStem.Option ETK Debugging together with ETK from ETAS 19

SYStem.Option HeartBeat Bug fix to avoid FPI bus conflict 20

SYStem.Option ICFLUSH Flush instruction cache at “Go” or “Step” 20

SYStem.Option IMASKASM Disable interrupts while single stepping 20

SYStem.Option IMASKHLL Disable interrupts while HLL single stepping 20

SYStem.Option PERSTOP Enable global peripheral suspend 20

SYStem.Option SOFTLONG Set 32 bit software breakpoints 20

SYStem.Option STEPSOFT Step with software breakpoints 20

SYStem.Option TB1766FIX Bug fix for some TC1766 TriBoards 20

SYStem.Option TC1796FIX Bug fix for disabling the watchdog 21

SYStem.Option TC19XXFIX Bug fix required for some TC19XX derivatives 21

SYStem.RESetOut Assert nRESET/nSRST on JTAG connector 21

SYStem.Option WATCHDOGFIX Disables the watchdog on SYStem.Up 21

SYStem.state Open SYStem.state window 21

CPU specific TrOnchip Commands ....................................................................................... 22

TrOnchip.BreakBusN.BreakIN Configure break pin of BreakBus N 22

TrOnchip.BreakBusN.BreakOUT Configure break pin of BreakBus N 22

TrOnchip.BreakIN.<target> Connect break target to BreakBus 22

TrOnchip.BreakOUT.<source> Connect break source to BreakBus 22

TrOnchip.CONVert Not relevant for the TRICORE architecture 22

TrOnchip.CountX Event X counter value 22

TrOnchip.CountY Event Y counter value 22

TrOnchip.EXTernal Configure TriCore break on BreakBus event 23

TrOnchip.RESet Reset settings for the on-chip trigger unit 23

TrOnchip.SusSWitch Enable or disable suspend switch 23

TrOnchip.SusSWitch.FORCE Force generation of suspend signal 23

TrOnchip.SusSWitch.Mode Set suspend switch mode 23

TrOnchip.SusTarget Connect special targets to the suspend bus 23

TrOnchip.TCompress Trace data compression 23

TrOnchip.TDelay Trace trigger delay (obsolete) 23

TrOnchip.TExtMode Mode for external trigger input 24

TrOnchip.TExtPol Polarity of external trigger input 24


TrOnchip.TMode Trace mode (obsolete) 24

TrOnchip.TR0 Specify trigger event 0 24

TrOnchip.TR1 Specify trigger event 1 24

TrOnchip.state Show on-chip trigger window 24

TrOnchip.X Select trigger source X 24

TrOnchip.Y Select trigger source Y 24

Support ..................................................................................................................................... 25

Available Tools 25

Compilers 28

Target Operating Systems 28

3rd-Party Tool Integrations 29

Products ................................................................................................................................... 30

Product Information 30

Order Information 30


Simulator for TriCore

Version 16-Nov-2018

All general commands are described in the “PowerView Command Reference” (ide_ref.pdf) and “General Commands Reference”.This document describes the processor specific settings and features for the SIM TRICORE.


TRACE32 Simulator License

[build 68859 - DVD 02/2016]

The extensive use of the TRACE32 Instruction Set Simulator requires a TRACE32 Simulator License.

For more information, see www.lauterbach.com/sim_license.html.

Brief Overview of Documents for New Users

Architecture-independent information:

• “Debugger Basics - Training” (training_debugger.pdf): Get familiar with the basic features of a TRACE32 debugger.

• “T32Start” (app_t32start.pdf): T32Start assists you in starting TRACE32 PowerView instances for different configurations of the debugger. T32Start is only available for Windows.

• “General Commands” (general_ref_<x>.pdf): Alphabetic list of debug commands.

Architecture-specific information:

• “Processor Architecture Manuals”: These manuals describe commands that are specific for the processor architecture supported by your debug cable. To access the manual for your processor architecture, proceed as follows:

- Choose Help menu > Processor Architecture Manual.

• “OS Awareness Manuals” (rtos_<os>.pdf): TRACE32 PowerView can be extended for operating system-aware debugging. The appropriate OS Awareness manual informs you how to enable the OS-aware debugging.

Example Scripts

In your TRACE32 installation directory there is a subdirectory ~~/demo/tricore/ where you will find example scripts and demo software:

compiler/ Compiler examples.

hardware/ The demo scripts usually also run in the simulator.

simulator/ Special simulator configuration.


www.lauterbach.com/sim_license.html

Quick Start

This chapter should help you to prepare your Simulator for TriCore. For some applications additional steps might be necessary that are not described in this Quick Start section.

See the Example Scripts for more examples.

1. Select the Device Prompt B: for the ICD Debugger

On all TRACE32 tool configurations except for the emulator device B:: is already selected.

2. Select the CPU Type to load the CPU specific Settings

3. Enter Debug Mode

This command resets the CPU and enters debug mode. After this command is executed, it is possible to access memory and registers.

4. Load your Application Program

The options of the Data.LOAD command depend on the file format generated by the compiler. For information on the compiler options refer to the section Compiler. A detailed description of the Data.LOAD command is given in “General Commands Reference”.

B::

SYStem.CPU TC1766

SYStem.Up

Data.LOAD.Elf myprog.elf ; ELF specifies the format, myprog is the file name


5. Write a Start-up Script

Now the quick start is done. If you were successful you can start to debug, it is recommended to prepare a PRACTICE script (*.cmm, ASCII file format) to be able to do all the necessary actions with only one command.

Here is a typical start sequence:

*) These commands open windows on the screen. The window position can be specified with the WinPOS command.

For information about how to build a PRACTICE script file (*.cmm file), refer to “Debugger Basics - Training” (training_debugger.pdf). There you can also find some information on basic actions with the debugger.

Please keep in mind that only the Processor Architecture Manual (the document you are reading at the moment) is CPU specific, while all other parts of the online help are generic for all CPUs. So if there are questions related to the CPU, the Processor Architecture Manual should be your first choice.

B:: ; Select the ICD device prompt

WinCLEAR ; Clear all windows

SYStem.CPU TC1766 ; Select CPU

SYStem.Up ; Reset the target and enter debug; mode

Data.LOAD.Elf myprog.elf ; Load the application

Data.List ; Open disassembly window *)

Register /SpotLight ; Open register window *)

Frame.view /Locals /Caller ; Open the stack frame with ; local variables *)

Var.Watch %Spotlight flags ast ; Open watch window for variables *)

PER.view ; open window with peripheral register; *)

Break.Set main ; Set breakpoint to function main

Break.Set 0xD0000200 ; Set breakpoint to address; 0xD0000200


OCDS-L1 Debugger

Troubleshooting

No information available.


Memory Classes

The following memory classes are available:

P: and D: display the same memory, the difference is in handling the symbols.

Prepending an E as attribute to the memory class will make memory accesses possible even when the CPU is running. See SYStem.MemAccess and SYStem.CpuAccess for more information.

In the Simulator, all memories are dual-port capable by default.

Memory Class Description

P Program

D Data

EEC Emulation Memory on EECOnly available on TriCore Emulation Devices for accessing the Emulation Extension Chip


Breakpoints

There are two types of breakpoints available: Software breakpoints and On-chip breakpoints.

The simulator does not differ between software- and on-chip breakpoints.

Examples for Breakpoints

• Examples for instruction breakpoints:

• Examples for breakpoints on data:

Breakpoint on write access to 0xAFE10200.

Breakpoint on read access to 0xAFE10400.

Break.Set 0xD4001FD0 /Program ; breakpoint on instruction

Break.Set 0xAFE10200 /Write ; data write access breakpoint

Break.Set 0xAFE10400 /Read ; data read access breakpoint


Trace

The Simulator offers a complete Instruction and Data trace. Use Trace.List to display.


FAQ

No information available


CPU specific Trace Commands

Analyzer.Mode PCP Select PCP trace

Command has no effect in Simulator.

SYStem.Option DataTrace Enable data tracing


SYStem.Option INTSTART Start address of interrupt routines


SYStem.Option INTUSE Number of implemented interrupts


SYStem.Option MCDSKeyHigh Key (high part) for unlocking MCDS


SYStem.OptionMCDSKeyLow Key (low part) for unlocking MCDS


SYStem.Option TRAPSTART Start address of trap vectors



CPU specific SYStem Commands

SYStem.CONFIG Configure debugger according to target topology

The SYStem.CONFIG commands have no effect in Simulator. These commands describe the physical configuration at the JTAG port and the trace port of a multi-core hardware target. Since the simulator normally just simulates the instruction set, these commands will be ignored. Refer to the relevant Processor Architecture Manual in case you want to know the effect of these commands on a debugger.

SYStem.CONFIG.DAP.BreakPINS Define mapping of break pins


SYStem.CONFIG.DAP.DAPENable Enable DAP mode on PORST


SYStem.CONFIG.DAP.USERn Configure and set USER pins


SYStem.CONFIG.Interface Set debug cable interface mode



SYStem.CPU Select CPU

Default: TC1796.

Selects the processor type.

SYStem.CpuAccess Run-time CPU access (intrusive)

Default: Denied.

This option declares if an intrusive memory access can take place while the CPU is executing code. To perform this access, the debugger stops the CPU shortly, performs the access and then restarts the CPU.

The run-time memory access has to be activated for each window by using the memory class E: (e.g. Data.dump ED:0xA1000000) or by using the format option %E (e.g. Var.View %E var1).

Format: SYStem.CPU <cpu>

<cpu>: RIDERD | TC10GP | TC11IB |TC1100 | TC1115 | TC1130 |TC1161 | TC1162 | TC1163 | TC1164 | TC1165 | TC1166 TC1762 | TC1764 | TC1765 | TC1766 | TC1766ED | TC1775 | TC1775B | TC1736 | TC1767 | TC1767ED TC1792 | TC1796 | TC1796ED | TC1797 | TC1797ED TC1910 | TC1912 | TC1920A | TC1920B | PXB4260 | CARMEL | CERBERUS | CERBERUS2

Format: SYStem.CpuAccess <mode>

<mode>: Enable | Denied | Nonstop

Enable Stop the CPU shortly to perform a memory read or write while the program execution is running.Each short stop takes 1 … 100 ms depending on the speed of the debug interface and on the size of the read/write accesses required.


SYStem.JtagClock Set the JTAG frequency


SYStem.LOCK Tristate the JTAG port


Denied No intrusive memory read or write is possible while the CPU is executing the program.

Nonstop The program execution can not be stopped and the real-time behavior of the CPU is not affected.Nonstop reduces the functionality of the debugger to:• run-time access to memory and variables• trace displayThe debugger inhibits the following:• to stop the program execution• all features of the debugger that are intrusive (e.g. spot breakpoints, per-

formance analysis via StopAndGo, conditional breakpoints etc.)


SYStem.MemAccess Run-time memory access (non-intrusive)

Default: CPU.

This option declares if and how a non-intrusive memory access can take place while the CPU is executing code. Although the CPU is not halted, run-time memory access creates an additional load on the processor’s internal data bus. The MemAccess mode is printed in the state line.

The run-time memory access has to be activated for each window by using the memory class E: (e.g. Data.dump ED:0xA1000000) or by using the format option %E (e.g. Var.View %E var1). It is also possible to enable non-intrusive memory access for all memory areas displayed by setting SYStem.Option DUALPORT ON.

SYStem.ACCESS is an alias for this command.

Format: SYStem.MemAccess <mode>SYStem.ACCESS (deprecated)

<mode>: CPU | Denied

CPU The debugger performs non-intrusive memory accesses via the CPU internal buses (FPI Bus).

Denied Non-intrusive memory access is disabled while the CPU is executing code. Instead intrusive accesses can be configured with SYStem.CpuAccess.


SYStem.Mode Establish the communication with the CPU

Initial Mode: Down.

The SYStem Modes are not only commands to bring the debugger in a certain debug state, they also reflect the current debug state of the target. SYStem Modes Attach and Go are only transitional states which will result in an Up state on success. Any critical failure will transition the debug state to SYStem Mode Down immediately

The “Emulate” LED on the debug module is ON when the debug mode is active and the CPU is running.

Format: SYStem.Mode <mode>

<mode>: DownNoDebugGoAttachUp

Down The CPU is held in reset, debug mode is not active. Default state and state after fatal errors.

NoDebug The CPU is running. Debug mode is not active, debug port is tristate. In this mode the target behaves as if the debugger is not connected.

Attach User program remains running (no reset) and the debug mode is activated. After this command the user program can be stopped with the break command or if any break condition occurs. The debugger should be in NoDebug mode when performing an Attach.

Go The CPU is running. Debug mode is active. After this command the CPU can be stopped with the break command or if any break condition occurs.

Up The CPU is not in reset but halted. Debug mode is active. In this mode the CPU can be started and stopped. This is the most typical way to activate debugging.


SYStem.Option CPU specific commands

The SYStem.Option command group provides architecture and CPU specific commands.

SYStem.Option DCFREEZE Do not invalidate cache


SYStem.Option DIAG Diagnosis function

System Diagnosis functions. Please execute only when demanded by LAUTERBACH support engineer. Functionality is undocumented, can change without any notice and may bring the debugger software into an unstable state. Do not use in script files.

SYStem.Option DUALPORT Run-time memory access for all windows

Default: OFF.

Enable permanent non-intrusive memory access for all windows and memory accesses. Memory class E: does not have to be specified any more. This only works when SYStem.MemAccess is set to CPU.

SYStem.Option ETK Debugging together with ETK from ETAS


Format: SYStem.Option DIAG [<value>] [<param>] [<param>] [<param>]

Format: SYStem.Option DUALPORT [ON | OFF]

When this option is enabled, no Data.dump or Data.List windows must be opened while programming the on-chip flash. Otherwise flash operation will fail.


SYStem.Option HeartBeat Bug fix to avoid FPI bus conflict


SYStem.Option ICFLUSH Flush instruction cache at “Go” or “Step”


SYStem.Option IMASKASM Disable interrupts while single stepping


SYStem.Option IMASKHLL Disable interrupts while HLL single stepping


SYStem.Option PERSTOP Enable global peripheral suspend


SYStem.Option SOFTLONG Set 32 bit software breakpoints


SYStem.Option STEPSOFT Step with software breakpoints


SYStem.Option TB1766FIX Bug fix for some TC1766 TriBoards



SYStem.Option TC1796FIX Bug fix for disabling the watchdog


SYStem.Option TC19XXFIX Bug fix required for some TC19XX derivatives


SYStem.RESetOut Assert nRESET/nSRST on JTAG connector

The command is ignored by the simulator. It is an allowed command that you can run scripts which have actually been made for a debugger. See the Processor Architecture Manual for more information about the effect there.

SYStem.Option WATCHDOGFIX Disables the watchdog on SYStem.Up


SYStem.state Open SYStem.state window

Opens the SYStem.state window with settings of CPU specific system commands. Settings can also be changed here.

Format: SYStem.state


CPU specific TrOnchip Commands

TrOnchip.BreakBusN.BreakIN Configure break pin of BreakBus N


TrOnchip.BreakBusN.BreakOUT Configure break pin of BreakBus N


TrOnchip.BreakIN.<target> Connect break target to BreakBus


TrOnchip.BreakOUT.<source> Connect break source to BreakBus


TrOnchip.CONVert Not relevant for the TRICORE architecture


TrOnchip.CountX Event X counter value


TrOnchip.CountY Event Y counter value



TrOnchip.EXTernal Configure TriCore break on BreakBus event


TrOnchip.RESet Reset settings for the on-chip trigger unit


TrOnchip.SusSWitch Enable or disable suspend switch


TrOnchip.SusSWitch.FORCE Force generation of suspend signal


TrOnchip.SusSWitch.Mode Set suspend switch mode


TrOnchip.SusTarget Connect special targets to the suspend bus


TrOnchip.TCompress Trace data compression


TrOnchip.TDelay Trace trigger delay (obsolete)



TrOnchip.TExtMode Mode for external trigger input


TrOnchip.TExtPol Polarity of external trigger input


TrOnchip.TMode Trace mode (obsolete)


TrOnchip.TR0 Specify trigger event 0


TrOnchip.TR1 Specify trigger event 1


TrOnchip.state Show on-chip trigger window


TrOnchip.X Select trigger source X


TrOnchip.Y Select trigger source Y



Support

Available Tools

CP

U

ICE

FIR

E

ICD

DE

BU

G

ICD

MO

NIT

OR

ICD

TR

AC

E

PO

WE

RIN

TE

GR

ATO

R

INS

TR

UC

TIO

NS

IMU

LA

TOR

PXB4260 YES YES YESTC10GP YES YES YESTC1100 YES YES YESTC1115 YES YES YESTC1124 YES YESTC1128 YES YESTC1130 YES YES YESTC1161 YES YES YES YESTC1162 YES YES YES YESTC1163 YES YES YES YESTC1164 YES YES YES YESTC1165 YES YES YES YESTC1166 YES YES YES YESTC1167 YES YESTC1182 YES YESTC1184 YES YESTC1191 YES YESTC1193 YES YESTC1197 YES YESTC1198 YES YESTC11IA YES YES YESTC11IB YES YES YESTC11IC YES YES YESTC1337 YES YESTC1367 YES YESTC1387 YES YESTC1387ED YES YESTC1724 YES YESTC1724ED YES YESTC1728 YES YESTC1728ED YES YESTC1736 YES YESTC1736ED YES YESTC1746 YES YES


TC1762 YES YES YES YESTC1764 YES YES YES YESTC1765 YES YES YESTC1766 YES YES YES YESTC1766ED YES YES YES YESTC1767 YES YESTC1767ED YES YESTC1768 YES YESTC1775 YES YES YESTC1782 YES YESTC1782ED YES YESTC1784 YES YESTC1784ED YES YESTC1791 YES YESTC1791ED YES YESTC1792 YES YES YES YESTC1793 YES YESTC1793ED YES YESTC1796 YES YES YES YESTC1796ED YES YES YES YESTC1796L YES YES YES YESTC1797 YES YESTC1797ED YES YESTC1798 YES YESTC1798ED YES YESTC1910 YES YES YESTC1912 YES YES YESTC1920 YES YES YESTC233LP YES YESTC234LP YES YESTC260D YES YESTC260DU YES YESTC264D YES YESTC264DA YES YES YESTC264DE YES YES YESTC264DU YES YESTC265D YES YESTC265DE YES YES YESTC265DU YES YESTC270T YES YESTC270TP YES YES

CP

U

ICE

FIR

E

ICD

DE

BU

G

ICD

MO

NIT

OR

ICD

TR

AC

E

PO

WE

RIN

TE

GR

ATO

R

INS

TR

UC

TIO

NS

IMU

LA

TOR


TC270TU YES YESTC275T YES YESTC275TA YES YES YESTC275TE YES YES YESTC275TF YES YES YESTC275TP YES YESTC275TU YES YESTC277T YES YESTC277TA YES YES YESTC277TE YES YES YESTC277TF YES YES YESTC277TP YES YESTC277TU YES YESTC290T YES YESTC290TP YES YESTC290TU YES YESTC297T YES YESTC297TA YES YES YESTC297TE YES YES YESTC297TF YES YES YESTC297TP YES YESTC297TU YES YESTC298T YES YESTC298TE YES YES YESTC298TF YES YES YESTC298TP YES YESTC298TU YES YESTC299T YES YESTC299TE YES YES YESTC299TF YES YES YESTC299TP YES YESTC299TU YES YESTC2D5T YES YESTC2D5TE YES YES YESTC2D7T YES YESTC2D7TE YES YES YES

CP

U

ICE

FIR

E

ICD

DE

BU

G

ICD

MO

NIT

OR

ICD

TR

AC

E

PO

WE

RIN

TE

GR

ATO

R

INS

TR

UC

TIO

NS

IMU

LA

TOR


Compilers

Target Operating Systems

Language Compiler Company Option Comment

C/C++ GREENHILLS Greenhills Software Inc. ELF/DWARFC/C++ GCC HighTec EDV-Systeme

GmbHELF/DWARF

C/C++ VX-TC TASKING ELF/DWARFC/C++ VX-TC TASKING IEEEC/C++ DIAB Wind River Systems ELF

Company Product Comment

Elektrobit Automotive GmbH

EB tresos AutoCore OS via ORTI

Elektrobit Automotive GmbH

EB tresos Safety OS via ORTI

Evidence Erika via ORTIfreeRTOS FreeRTOS up to v9Vector MICROSAR OS via ORTIMentor Graphics Corporation

Nucleus

Vector osCAN via ORTIEnea OSE Systems OSE Epsilon- OSEK via ORTIElektrobit Automotive GmbH

ProOSEK via ORTI

HighTec EDV-Systeme GmbH

PXROS-HR

ETAS GmbH RTA-OS via ORTIMicrium Inc. uC/OS-II 2.0 to 2.8Wind River Systems VxWorks 5.x and 6.x


3rd-Party Tool Integrations

CPU Tool Company Host

WINDOWS CE PLATF. BUILDER

- Windows

CODE::BLOCKS - -C++TEST - WindowsADENEO -X-TOOLS / X32 blue river software GmbH WindowsCODEWRIGHT Borland Software

CorporationWindows

CODE CONFIDENCE TOOLS

Code Confidence Ltd Windows

CODE CONFIDENCE TOOLS

Code Confidence Ltd Linux

EASYCODE EASYCODE GmbH WindowsECLIPSE Eclipse Foundation, Inc WindowsCHRONVIEW Inchron GmbH WindowsLDRA TOOL SUITE LDRA Technology, Inc. WindowsUML DEBUGGER LieberLieber Software

GmbHWindows

SIMULINK The MathWorks Inc. WindowsATTOL TOOLS MicroMax Inc. WindowsVISUAL BASIC INTERFACE

Microsoft Corporation Windows

LABVIEW NATIONAL INSTRUMENTS Corporation

Windows

TPT PikeTec GmbH WindowsCANTATA QA Systems Ltd WindowsRAPITIME Rapita Systems Ltd. WindowsRHAPSODY IN MICROC IBM Corp. WindowsRHAPSODY IN C++ IBM Corp. WindowsDA-C RistanCASE WindowsTRACEANALYZER Symtavision GmbH WindowsECU-TEST TraceTronic GmbH WindowsUNDODB Undo Software LinuxTA INSPECTOR Vector WindowsVECTORCAST UNIT TESTING

Vector Software Windows

VECTORCAST CODE COVERAGE

Vector Software Windows


Products

Product Information

Order Information

OrderNo Code Text

LA-2800L SIMULATOR-TC-FL

1 User Float. Lic. TRACE32 TriCore SimulatorFloating license to use the TRACE32 Instruction SetSimulator for automated tests via script languagePRACTICE or via the TRACE32 Remote APIsupports TriCorefor Windows32, Windows64, Linux32, Linux64and Solaris, other platforms on requestfloating license via RLM (Reprise License Manager)Please add the RLM HostID of the license serverto your order (please see our FAQ)

Order No. Code Text

LA-2800L SIMULATOR-TC-FL 1 User Float. Lic. TRACE32 TriCore Simulator
