[evla-sw-discuss] TASKING tool set
Bill Sahr
bsahr at cv3.cv.nrao.edu
Wed Apr 24 17:13:52 EDT 2002
Two emails from Richard Cannock of Altium re
info on the TASKING tool set plus my original
email to him.
Bill
-------------- next part --------------
Received: from RCannock (unverified [10.1.1.79]) by omicron.pcad.com
Tue, 23 Apr 2002 11:51:02 -0700
Message-ID: <00ad01c1eaf6$40541070$4f01010a at RCannock>
Reply-To: "Richard Cannock" <richard.cannock at altium.com>
From: "Richard Cannock" <richard.cannock at altium.com>
To: "Bill Sahr" <bsahr at cv3.cv.nrao.edu>
Subject: Re: Tasking Tool Set
Date: Tue, 23 Apr 2002 11:39:50 -0700
Organization: Altium, Inc.
Hello Bill:
Thank you for your inquiry. We apologize for the delay in our response.
We had to do a bit of research to be able to answer some of your
questions.
1) We have tools for the Tricore family for use under Microsoft Windows
(Windows 98, ME, XP, NT, and 2000), Linux, HP Unix, and Sun Solaris.
The one I quoted was the Microsoft Windows version.
2) Our licenses are sold either as Node Locked or Floating at this time.
The Node Locked alternative is limited to operation in one machine.
This is enforced through the use of a license file that has, among other
things, the System ID encoded into it. Typically, we don't have a
problem issuing a couple of license files so that you may operate the
software, for example, at home and at the office. There is an
understanding, of course, that the software cannot be use in both
computers at the same time.
The floating option allows you to install the software in as many
clients in the network as you want. The license file in this case
resides in a server, or in any other computer in the network actually,
in this case, the license manager running in that server administers the
number of licenses that are being used at any one time and it will not
allow operation of more instances than the number of licenses you own.
This gives you the flexibility of having the software available in many
machines. It works really well if you know that not all developers will
be working in the project at the same time. Like, for example, if you
have two shifts.
We don't have any hardware dongles for copyright protection.
3) The RADM (Rtos Aware Debugging Module) is typically developed by the
RTOS vendor/manufacturer using the KDI Interface standard. They would
be the ones that would know if any modifications are required and they
would be the ones that implement these modifications. Therefore, any
questions on this matter should be directed to Accelerated Technology.20
4) We don't offer Kernel Aware debugging for ThreadX. Again, this is
something the RTOS manufacturer would implement. Unlike, Accelerated
Technology (Nucleus) I don't believe Express Logic has developed this
module to communicate with our debugger. I am not sure if a user could
develop a RADM. It may be that you would need to know some internal
information about the RTOS that may not be published. Thus, I believe
this would be better handled by Express Logic.
5) Tool Features
a) Our Assembler, PCP assembler, and C/C++/EC++ compilers support all
TriCore family members. This provides you with one tool chain for all as
well as all necessary settings are made automatically for the selected
TriCore Derivative
b) Our assembler provides powerful Macro facilities which allows for
configurable assembly and conditional inclusion of code.
c) The compilers allow for flexible allocation of data objects in
memory. This permits, for example, to represent your I/O ports with
C-Language data objects.
d) We provide for configurable optimization methods to allow you to
select the optimization method most suitable for your application. If
necessary, at source line level.
f) Tools include SAFER C enhanced error checking. This provides
guidance towards writing better C code that conform to MISRA guidelines.
g) Our compilers include fully ANSI C/C++ compliant libraries. This
enables you to include and write fully portable code.
h) Embedded C++ compliance checks. Provides you with the benefits of C++
functionality without excessive code-size build-up.=20
i) In-Line Assembly support. Allows you to implement your own optimized
functions.
j) Our linker/locator allows for flexible, yet powerful allocation of
data objects and code. This enables you to efficiently arrange for
sections and segments of data and/or code.
k) Also, our Linker/Locator supports IEEE695, ELF/Dwarf, Intel HEX and
Motorola SREC Symbolic Debug Object formats. This allows you to
interface with any TriCore In-Circuit Emulator, (E)PROM programmer, or
Co-Simulation/Co-Verification environments.
l) Our CrossView Debugger provides you with a Graphical User interface
with Icon Buttons for frequently used functions. This allows for a
familiar, easy-to-learn-and-use environment. Also permits full
customization and a personalized working environment.to increase
productivity.
m) Crossview debugger allows for High Level, Assembly, or "mixed"
debugging providing the right focus for each type of bug...C++, C or ASM
n) The debugger allows for multiple execution environments which allows
you to use one debugger throughout the entire development process.
o) Tools include instruction set simulator on development PC/Workstation
that permits first stage verification of your application without target
hardware.
p) On Target debugging with ROM Monitor via Serial or CAN connection.
Also via JTAG/OCDS via parallel port (in this particular case [Tricore])
This allows for second stage debugging using actual target hardware.
q) Configurable Register Windows. Allows you to create windows with your
own set(s) of registers and focus on the information relevant to your
current debugging session.
r) Data Watch Window. Permits you to display and keep track of your data
objects in any format you like.
s) Call Stack Depth Window...Easy overview on function call depth allows
quick navigation to called/calling function and placing breakpoints at
function entry or exit.
t) Code/Data coverage provides easy identification of unused code/data.
This assures that all code is thoroughly tested.
u) Profiling/Performance Analysis provides easy identification of time
critical code helps produce code with optimal performance.
v) Programmable Graphical Data Analysis. Allows easy identification of
errors in signal processing algorithms. Graphical Data Analysis is fully
programmable and can therefore include any pre-processing of data before
being displayed.
Regarding the TC11IB, without going into specific details, I can inform
you that the original company upon whose specifications Infineon created
the TC11IB, is a long standing, and quite satisfied, Tasking TriCore
tool user. The TC11IB has been fully supported in the Tasking TriCore
tools for over a year now.. All of its Special Function Registers are
pre-defined in C and assembly header files. The configurable C-startup
code is defined for the TC11IB and the CrossView debugger can establish
a flawless connection with the TC11IB boards(Your own or Infineon
Triboard) using the parallel port/JTAG/OCDS drivers.
6) Our tool set include capabilities for source code management/version
control. However, this cannot be integrated it CVS specifically. There
are a few version managers to select from like PVCS but, unfortunately,
not CVS.
7) The JTAG/OCDS connection is indeed via parallel port interface. We
do support the Infineon JTAG interface.
8) Yes, the debugger can be used to debug software running in a Target
board. You may use two interfaces the JTAG/OCDS parallel port connection
or by using the ROM monitor and a serial interface.=20
9) Both PCP and PCP2 are supported by the debugger.
10) On-Chip Support (OCDS) is basically the same as JTAG . They both
interface to the chip's test pins. I have already touched on our support
for these above. However, if you have a specific questions please let me
know and I will make sure to get you the appropriate answers.20
11) We provide single-precision floating point libraries.
12) All the runtime libraries are thread safe.
13) The Source code for the runtime libraries is not available.
Hopefully, I did not miss anything. Please let me know if you have
further questions or concerns. It will be a pleasure to be of service..
Kind regards,
Richard Cannock
Consultant
Altium - Think it, Design it, Build It
Phone: +1 858 485 4632
Fax: +1 858 485 4611 / +1 858 521-4282
E-Mail: richard.cannock at altium.com
URL: http://www.altium.com
--------------------------------------------------------------------------------
Tue, 23 Apr 2002 12:38:24 -0700
Message-ID: <00d501c1eafc$de5b2d20$4f01010a at RCannock>
Reply-To: "Richard Cannock" <richard.cannock at altium.com>
From: "Richard Cannock" <richard.cannock at altium.com>
To: "Bill Sahr" <bsahr at cv3.cv.nrao.edu>
Subject: Fw: Tasking Tool Set
Date: Tue, 23 Apr 2002 12:27:12 -0700
Organization: Altium, Inc.
Hello Bill,
I forgot to mention. Infineon benchmarked the TC11IB using our tools.
Please check the EEMBC benchmark results recently published by Infineon.
http://www.eembc.org/benchmark (no need to login, just click the option
to look without registering)
In the section 'Production silicon' / 'Automotive/Industrial' you will
find the TriCore TC11IB benchmarks, which were produced with the TASKING
tools v1.4. Needless to say that Infineon selected TASKING for their
performance
Kind regards,
Richard Cannock
Consultant
Altium - Think it, Design it, Build It
Phone: +1 858 485 4632
Fax: +1 858 485 4611 / +1 858 521-4282
E-Mail: richard.cannock at altium.com
URL: http://www.altium.com
-------------------------------------------------------------------------------
----- Original Message -----
From: "Bill Sahr" <bsahr at cv3.cv.nrao.edu>
To: "Richard Cannock" <richard.cannock at altium.com>
Sent: Friday, April 19, 2002 8:41 PM
Subject: Tasking Tool Set
> Richard,
>
> I mentioned that I would develop an email containing our questions
> concerning the TASKING tool set.
>
> First, just to confirm my contact info:
>
> Bill Sahr
> National Radio Astronomy Observatory
> P.O. Box O ("oh", not zero)
> Socorro, NM
> 87801
>
> physical address:
> 1003 Lopezville Road
> Socorro, NM
> 87801
>
> phone: 505-835-7285, Mountain Time
> fax: 505-835-70727
>
> email: bsahr at nrao.edu
>
>
> The quote I received is for a node-locked license, for PC/Windows.
>
> Q1. The systems we run here at NRAO include Sun Solaris (V5.8),
> Windows NT 4.0 SP6a, Windows 2000 Professional SP2 and
> SP3 when it is released, and Red Hat Linux (on PC hardware).
> Specifically, which of these systems can host your tool set ?
>
> Q2. Do you offer floating and dongle licenses as well as node-
> locked licenses ?
>
>
> As just stated we plan to use either Nucleus PLUS or ThreadX
> as our RTOS. Nucleus PLUS is ported to the TriCore architecture,
> but not to the TC11IB chip/development board. ThreadX is not
> ported to either the TriCore architecture or the TC11IB chip/
> development board. We are obtaining quotes from both ATI
> (Nucleus PLUS) and Express Logic (ThreadX) for the needed port
> to the TC11IB development board. In your company's product
> literature, there is a discussion of the "Kernel aware Debugging
> Interface" (KDI), and an RTOS-Aware Debug Module (RADM) to
> achieve kernel aware debugging.
>
> Q1. If we use Nucleus PLUS, I assume that some modifications
> will be needed to the RADM to account for the port to the
> TC11IB development board. Is this assumption correct ? If yes,
> will there be a charge for this modification ? If yes,
> approximately how much would it cost, and how long will it take?
>
> Q2. Do you offer kernel aware debugging for ThreadX ? Am I
> correct in assuming that if you do, it is equivalent to saying
> that you have developed an RADM for ThreadX ? If no, is it
> possible for a user to develop a RADM for ThreadX ? If yes,
> how much time would be involved? Would Altium be interested
> in developing a debugger integration for ThreadX on the TC11IB
> chip ?
>
> TriCore & TC11IB chip
> Can you describe the salient features of your support for the
> TriCore architecture, especially any features that relate
> specifically to the TC11IB chip ? Information that you supply
> in answer to this question could have a significant effect
> on our decision of which tool set to use.
>
> Toolset issues
> Does your toolset include capabilities for source code
> management & version control ? Is your approach proprietary ?
> Can it be integrated with CVS ?
>
> Please describe the nature of the connection between the host
> system and the target, hardware & software. I am speaking of
> the connection used to download binaries to the target, and
> to perform host-based debugging of software running in the
> target.
>
> Q1. Is it a parallel port to JTAG connection ?
>
> Q2. Do you support the Infineon JTAG interface for which the
> "wiggler" is basically a part of the board ?
>
> Q3. Can the debugger be used to debug software that is running
> in a target board, specifically for the case of the
> TriCore architecture and the TC11IB chip, or is it limited
> to debugging code which is run via Infineon SimTri Tricore
> emulator ? If the latter, does that mean we cannot use the
> debugger with code that makes OS calls. (We plan to use
> either Nucleus PLUS or ThreadX as our rtos.)
>
> Q4. Are the PCP and PCP2 supported by the debugger ?
>
> On-Chip Debug Support (OCDS) is a capability that is unfamiliar
> to me. Can you supply a brief description of OCDS as it relates
> to the TriCore/TC11IB ? What support for OCDS is offered by
> the TASKING tool set ? Is there an inter-relationship between
> OCDS and JTAG ?
>
>
> Compiler & Library Issues
> The TC11IB does not appear to include a floating point processor.
> Is a floating point library for the TriCore V1.3 architecture
> &/or the TC11IB include in your runtime libraries for C,
> C++, EC++?
>
> For technical reasons we are limited to running our code entirely
> from the on-chip RAM in the TC11IB chip. We are very interested
> in any information which will give us a sense of the size of
> applications developed in C, C++, and EC++. Can you give us some
> figures on the size of your runtime libraries for these languages?
>
> Are you compilers GNU-based ? If yes, what version or versions ?
>
> Are the runtime libraries for C, C++, and EC++ thread safe ?
> If no, can they be made thread safe, and what is involved in
> doing so ?
>
> Is source code available for your runtime libraries - C,
> C++, EC++ ?
>
>
> Well, Richard, I think I've exhausted my list of questions
> for now. Thank you for your time and attention.
>
> Bill Sahr
> NRAO/VLA
>
More information about the evla-sw-discuss
mailing list