FIRE, ICE and ICD : Three Number 1 Hits!

Size: px

Start display at page:

Download "FIRE, ICE and ICD : Three Number 1 Hits!"

Hugo Osborne
5 years ago
Views:

TRACE NEWS Spring 1999 FIRE, ICE and ICD : Three Number 1 Hits! Lauterbach ended the 1998 business year with sales 60% up on the previous year.

product lines TRACE-ICE, TRACE-ICD and TRACE-FIRE. The classic TRACE-ICE, the in-circuit emulator for 8- to -bit architectures, emerged as the top-selling member of the TRACE family.

The product launch of the TRACE- FIRE was also a success. An unexpectedly high number of orders made this product the most successful RISC emulator for the PowerPC family MPC860 in Germany.

1 TRACE NEWS Spring 1999 FIRE, ICE and ICD : Three Number 1 Hits! Lauterbach ended the 1998 business year with sales 60% up on the previous year. Lauterbach thus retained its position as the most successful manufacturer of microprocessor development systems in Europe, filling the number 1 spot in three different categories with its three product lines TRACE-ICE, TRACE-ICD and TRACE-FIRE. The classic TRACE-ICE, the in-circuit emulator for 8- to -bit architectures, emerged as the top-selling member of the TRACE family. A large number of new processor probes have contributed to this success. The most successful processor families used with this product are the SIEMENS C166 family and the 68HC12 from Motorola. The product launch of the TRACE- FIRE was also a success. An unexpectedly high number of orders made this product the most successful RISC emulator for the PowerPC family MPC860 in Germany. The TRACE-FIRE is currently available for MOTOROLA PowerPC, Hitachi SH-2 and H8-S. Further promising processor architectures will be following shortly, such as the NEC V850, ARM7, ARM9 and Siemens TriCore. Lauterbach entered the debugger business a few years ago with mixed feelings since TRACE was originally positioned more as a sophisticated high-end development tool. Now TRACE-ICD is firmly established in the Lauterbach product array showing that high-end by no means rules out debuggers. After all, debuggers can also be made better than those of the competition and high-end is not necessarily synonymous with highprice. TRACE-ICD has doubled its sales in each of the past few years and in 1998 emerged as one of the most popular debuggers of all. In Germany it was the most successful debugger in both the automotive and telecommunications industries, especially for the processor architectures ARM, PowerPC and 68HC12. There is now also a brand new version of TRACE-ICD for SIEMENS TriCore and C166CBC, for Motorola M-Core and MPC8260. All in all TRACE has made enormous progress over the past few years and Lauterbach has become one of the world s leading companies for microprocessor development tools. After this short look back over the past business year we will now turn our attention to the future - and there s plenty in the development pipeline for this year. What new products you can expect in 1999 can be seen on the following pages. Context Tracking System 2 ICD Trace Extension 3 Current Information 6 New Supported ICD Debuggers 3 Supported Trace Modules 4 Supported RTOS 6 Supported Debuggers 6

2 CTS - Context Tracking System for TRACE 1.) Switch on the Context Tracking System 2.) Select the recording point for which the state of the target system is to be recreated 3.

) During the trace-based debugging the changes of memories, variables and registers can be watched In order to find out which instructions, data or system states had caused malfunctioning of the

The context tracking system - CTS for short - now allows to recreate the state of the target system at a selected point based on the information sampled in the trace buffer.

2 2 CTS - Context Tracking System for TRACE 1.) Switch on the Context Tracking System 2.) Select the recording point for which the state of the target system is to be recreated 3.) The PC will be set automatically to the recording point 4.) During the trace-based debugging the changes of memories, variables and registers can be watched In order to find out which instructions, data or system states had caused malfunctioning of the target system it was necessary to spend a lot of time analysing the trace listing. The context tracking system - CTS for short - now allows to recreate the state of the target system at a selected point based on the information sampled in the trace buffer. From this starting point the program steps previously recorded in real time in the trace memory can be debugged again. How does context tracking function? After switching on the context tracking system you first select a recording point in the trace for which the target system state is to be recreated in the emulator. The program counter is then automatically set in the source listing to how it was at the selected time. All debug commands such as Single Step, Step Over Call, Go Return, etc. can now be used. The commands are processed as they were recorded in the trace Hll Analysis of the Trace Contents memory. The debug functionality has been further extended so that it is now also possible to step backwards. At the same time it is also desirable to be able to track the changes of variables, memories and registers. There are various strategies available for this. The changes can be followed relatively easily by using the write and read cycles recorded in the trace memory. However, this only functions for internal memories if the CPU shows complete information about these accesses. Even then information about register transfers is not usually available. An exception to this is the C166 family which makes all information about internal operations visible externally via the bondout busses. Another alternative is to use an instruction set simulator which effectively allows the individual instructions to be executed again. This enables registers and memory states to be recreated more easily. Instruction set simulators are available for the PowerPC, the 68K family, the SH2 family and the ARM7.

3 3 Trace Extension for the ICD Debugger The TRACE-ICD In-Circuit Debugger allows easy debugging at C or C++ level via the on-chip debug interface. The complexity of these interfaces has increased over the past few years and they now include: Additional hardware breakpoints Trigger options The possibility of reading and writing memories while the CPU is executing code These processor-specific expansions are naturally integrated fully in the TRACE debugger. Since 1998 real-time trace modules have also been available for most ICD debuggers. Each trace module contains a trace memory with a capacity of 64K frames. The sampled records are marked with a timestamp with a resolution of 100 ns. Thanks to this trace extension complete information about the program flow is now available also for the In- Circuit Debuggers so that it is easy to follow which instructions or system states have caused a particular program state. To add the trace feature to your TRACE-ICD additional hardware modules in the form of the universal RISC trace module and a CPU-specific preprocessor are connected to the PODBUS. New ICD Debuggers OCDS debugger for C166CBC OCDS debugger for TRICORE ONCE debugger for M-CORE JTAG debugger for MPC8260 ROM monitor for H8S ROM monitor for the SH family ROM monitor for V850 PC or Workstation HUB 10 BASE-T Trace Connector All signals needed for tracing must be made available at a standardized connector in order to be able to connect the preprocessor to the target hardware. Since the trace connector has to be taken into account as early as the target design stage it is recommended that information about the connector layout is obtained early on. A detailed technical description can be found at the Lauterbach web site. / ord_7870.html Two different modes, the bus trace and the program flow trace, are used for the implementation of the trace module. Target PODETH DEBUG TRACE-ICD with trace extension and ethernet connection to the host JTAG/BDM Connector RISC TRACE Preprocessor Bus Trace In the case of a bus trace the data and address bus and certain state lines are recorded for every CPU cycle. As a result complete information is available about the program and data flow. This requires the address and data bus and certain important state lines to be brought out at the trace connector. Program Flow Trace In order to achieve higher speeds the programs on many of the newer processors run from the cache and bus accesses to resources on the CPU such as internal RAM or on-chip flash are no longer visible from the outside. This makes implementation of a bus trace impossible since the information necessary for this is not available. This is where a new development, program flow trace, comes in. The basic idea is to make the program flow completely understandable even though a minimum number of fetched instructions are visible. Instead of the complete instruction

4 address the CPU now feeds information about the program flow, for example next program step executed, direct branch taken, etc. to the outside via additional state lines.

The only problem with this solution approach is posed by indirect branches since in their case the branch address is not usually established until during the run time and cannot therefore be

The software thus provides the correct rerun point for the further reconstruction of the program flow.

4 4 address the CPU now feeds information about the program flow, for example next program step executed, direct branch taken, etc. to the outside via additional state lines. If these state signals are recorded an intelligent software can reconstruct the complete program flow from the start address of the program run, from the state signals and the program listing. The only problem with this solution approach is posed by indirect branches since in their case the branch address is not usually established until during the run time and cannot therefore be determined from the program listing. Most processors that support a program flow trace can, however, be set so that the instruction address of an indirect branch is output in full on the address bus. The software thus provides the correct rerun point for the further reconstruction of the program flow. In the case of the program flow trace the address and state lines and the lines that feed information about the program flow to the outside must therefore be brought out for the trace connector. Conclusion The TRACE-ICD In-Circuit Debugger in conjunction with the trace extension provides a powerful and affordable tool for debugging modern processors. A fully software-compatible In-Circuit Emulator is also available for most processors. Its performance far exceeds the scope of the debugger especially if a separate emulation chip displaying all the internal operations on the CPU is available, which is the case for example with the Siemens TriCore. Lauterbach continues also in 1999 its policy to provide complete tool chains for the most current processor architectures. Operation of the program flow trace with MPC555 as example Directly recorded signal with information of program flow The reconstructed assembler program flow based on the start address, program flow information and the program listing The reconstructed HLL program flow based on the start address, program flow information and the program listing Bus Trace Preprocessor for ARM7 for ARM7TDMI, ARM7TDMI-AMBA Preprocessor for C166CBC PMB2850 E-Gold, C161-C167 Program Flow Trace Preprocessor for TriCore Level2 for TriCore RiderA Preprocessor for ColdFire for MCF5202, MCF5203, MCF5204, MCF5206, MCF5207 Available Trace Modules Program Flow Trace Preprocessor for PPC400 for PPC403GA, PPC403GB, PPC403GC, PPC403GCX Preprocessor for MPC500/800 for MPC505, MPC509, MPC555, MPC821, MPC823, MPC850, MPC860 Preprocessor for MPC801 for MPC801 Preprocessor for PPC603 for PPC603, MPC740, MPC750

5 Please return by fax or in a window envelope! To Lauterbach Datentechnik GmbH Fichtenstr. 27 D Hofolding Fax: Sender Name Company Address Phone Fax We use the following processors: Please send me product information for the following tools: ICD Debugger Trace Extension for ICD-Debugger In-Circuit Emulator TRACE-ICE Fully Integrated RISC Emulator TRACE-FIRE We use the following compilers: We use the following RTOS: I am interested in a demonstration. We no longer use any development tools. Please delete us from your mailing list. TRACE International Representatives Australia Electro Optics Pty. Ltd, Mr. Philip Montgomery philmo@electro.oz.au WWW Benelux Tritec Benelux B.V., Mr. Robbert de Voogt development-tools@tritec.nl WWW China Watertek Inc., Mr. J. Chen xjwater@public.bta.net.cn Denmark Nohau Denmark A/S, Mr. Flemming Jensen info@nohau.dk Finland Nohau Elektronik AB, Mr. Mikael Johnsson info@nohau.se France Logic Instrument, Mr. Denis Morand d.morand@logic-instrument.com India Electro Systems, Mr. G. V. Gurunatham guru.esa@axcess.net.in Ireland Noral Micrologics Ltd., Mr. Phil Johnson info@noral.co.uk WWW Israel Itec Ltd., Mr. Mauri Gottlieb itec@netvision.net.il Italy Delo Systems, Mr. Giuseppe Egoriti sales@delo.it Japan NPS Inc., Mr. Seiji Kimura sk@nps.venture-web.or.jp WWW Norway Nohau Elektronik AB, Mr. Mikael Johnsson info@nohau.se South Africa Eagle Technology, Mr. Karni asher@eagle.co.za South Korea Hankook MDS, Mr. Kim Hyunchul hkmds@hitel.net Spain Captura Electronica, SCCL, Mr. Juan Martinez capel01@ibm.net Sweden Nohau Elektronik AB, Mr. Mikael Johnsson info@nohau.se Switzerland Iberg Datentechnik, Mr. Andreas Iberg Andreas.Jberg@jdt.ch WWW Taiwan Superlink Technology Corp., Mr. Tony Wu stc@tpts1.seed.net.tw Turkey Bildem Bilgisayar Ltd. Sti., Mr. Hakan Yavuz bildem@ada.com.tr UK Noral Micrologics Ltd., Mr. Phil Johnson info@noral.co.uk WWW USA East Lauterbach Inc., Mr Udo Zoettler infousa@gte.net WWW USA West Lauterbach Inc., Jerry Flake jerry.flake@lauterbach.com

6 Current Information ++ New System Controller Unit ++ The new System Controller Unit based on the MPC860 has been on the market since the end of 1998.

6 6 Current Information ++ New System Controller Unit ++ The new System Controller Unit based on the MPC860 has been on the market since the end of This new SCU offers considerably improved download performance: LPT ( KB/s) USB (1MB/s) Twisted pair connection for Ethernet (up to 1MB/s) AUI connection for Ethernet (up to 1MB/s) From March 1999 a System Controller Unit allowing direct connection to a 100 MBit Ethernet will also be available. The new SCU also has an interface that allows several emulators to be synchronized. This includes start/stop synchronization, time synchronization, and inter trigger options. ++ Multiprocessor Debugging with TRACE-ICD ++ Up to 4 TRACE-ICD In-Circuit Debuggers can be driven simultaneously via the PODBUS interface. This makes it possible to create a debug environment in which various processors can 68K RTXC, Embedded System Programming (planned) C166 CMX-RTXS, CMX Company RTXC, Embedded System Programming psos (protected mode), Integrated Systems Inc. be started and stopped simultaneously. The delay times for start and stop depend on the processors used. Multiprocessor debugging is conditional upon the Intercom system being configured on the host. + + TRACE Support for Java ++ As of now the TRACE debugger also supports the Java programming language. FastJ from DiabData for the PowerPC family is the first compiler to be supported. ++ New EPROM Simulator ++ From February we are also offering a 16 MBit EPROM simulator with 40 ns access time. The EPROM simulator will be available in a 5 V and a 3.3 V version. ++ PCP Debugger for TriCore ++ New Supported RTOS Lauterbach is expanding its ICD PowerPC MQX, Precise Software RTXC, Embedded System Programming Chorus, Chorus Systems (planned) ARM7 VxWorks, Wind River Systems SH2 VxWorks, Wind River Systems (planned) New Supported Third Party Debugger Xtools/X Blue River Software RistanCASE DA-C RistanCASE GmbH (Integration by RistanCASE GmbH) HIWARE HI-WAVE HIWARE AG (Integration by HIWARE) OSE Illuminator ENEA OSE SYSTEMS INC. IAR Embedded Workbench IAR Systems GmbH (planned) (Integration by IAR) DIAB DATA RTA Suite DIAB DATA Inc. (Integration by DIABDATA) SNIFF Take Five Software (planned) debuggers for the TRICORE with the addition of a debugger for the PCP subcontroller. This will also make it possible to debug the programs stored in the PCP. The performance of the PCP debugger includes: Display and modification of PCP registers, PCP memories and PCP special function registers Display of the PCP code Starting and stopping of the PCP, single steps and setting of breakpoints ++ ICD Debugger for MPC8260 and MPC The TRACE-ICD In-Circuit Debugger for the PPC603 now also supports the MPC8260 and the MPC8240. A Power Debug Module must be used for debugging these two processors.

TRACE32 News Spring 96

TRACE32 News Spring 96 Exhibitions Embedded Systems Show at Wembley Conference Centre in London April, 2, 3, 1996 Represented by Noral Micrologics Limited Embedded Systems Conference 96 in Boston April,