restricted
AppNote Number
TAS for DAS users
Using DAS tools and libraries with a TAS installation
About this document
Scope and purpose
TAS (Tool Access Sockets) is a standardized lightweight interface for tools. It provides the device connect, reset
and access functionality of DAS. It supports in addition a session concept, channels, and continuous tracing.
The TAS installation includes a new das_api.dll which translates between DAS and TAS.
Intended audience
DAS tool users and developer of software and tools.
Table of contents
About this document ....................................................................................................................... 1
Table of contents ............................................................................................................................ 1
1 Introduction .......................................................................................................................... 2
2 Comparison of DAS with TAS.................................................................................................... 3
3 Trouble shooting .................................................................................................................... 4
3.1.1 Device not visible for DAS tool ........................................................................................................... 4
3.1.2 TAS client error: session name or password ..................................................................................... 4
3.1.3 Problem: DAS remote access does not work .................................................................................... 4
3.1.4 UDAS stops when a native TAS tool is started .................................................................................. 4
3.1.5 Legacy DAS tool does not work ......................................................................................................... 5
4 Emulator access with TAS ....................................................................................................... 6
5 DAS changes for TAS implementation ....................................................................................... 7
Revision history.............................................................................................................................. 8
Disclaimer...................................................................................................................................... 9
Please read the Important Notice and Warnings at the end of this document V1.0
www.infineon.com 2023-05-04
restricted
TAS for DAS users
Using DAS tools and libraries with a TAS installation
Table of contents
1 Introduction
The TAS installation includes a das_api.dll which translates between DAS and TAS requests. This means that
the usage of TAS will be transparent for DAS users.
Note: DAS V8.0 (or higher) is based on TAS and so it is considered as a TAS installation.
Figure 1 DAS tools layering on top of TAS infrastructure
TAS was designed from the beginning for different host types (Windows, Linux) and for minimum installation
requirements. For a typical scenario, only the USB drivers for the miniWiggler HW need to be installed to be
able to connect to a device.
2 of 9 V1.0
2023-05-04
restricted
TAS for DAS users
Using DAS tools and libraries with a TAS installation
Table of contents
2 Comparison of DAS with TAS
DAS has a subset of TAS features. TAS has in addition a session concept, channels, and continuous tracing.
DAS is standardized by the DAS API (das_api.h). TAS is standardized by the client server socket protocol.
DAS tools use the the DAS API DLL (das_api.dll). TAS tools are compiled with the TasClient source code library.
The UDAS server of DAS is single threaded, the TasServer uses own threads for each client connection. For a
single connected device this makes no significant difference but if several devices are accessed by several
clients in parallel, the multi threading improves performance and reduces interference.
The TasServer has a fixed port number, there is no DAS_HOME system variable anymore and there is no need
for a running DASHPAS server. The TasServer can be started from any directory.
The following screenshot shows the information provided by DAS, MCD API (library on top of DAS) and TAS for
two boards connected to a host computer.
Figure 2 Screenshot of TAS, DAS and MCD scanner and info windows
3 of 9 V1.0
2023-05-04
restricted
TAS for DAS users
Using DAS tools and libraries with a TAS installation
Table of contents
3 Trouble shooting
The following recommendations assume that a TAS installer (or DAS V8.0) was used. In this case a previous DAS
installation is automatically removed. The TAS installation will provide DAS backward compatibility as
described in this document.
3.1.1 Device not visible for DAS tool
Target visible in TAS Basic Client target select window but not by DAS tool
This will happen when the TAS session name is neither unnamed nor the username. The solution is to
terminate the TAS session by closing all involved clients and start a new unnamed session.
Target neither visible in TAS Basic Client nor by DAS tool
Firstly, investigate please HW related issues like cables, power supply and try with USB unplug, wait 2 seconds,
and plug again.
Another possibility it that the TasServer is hanging. In this case kill the Tool Access Socket (TAS) server
(tas_server.exe) with the Windows task manager. On Windows it is automatically started again by the next
client, trying to connect.
Please note that there is no DAS dashpas server anymore which could have been crashed and that the
TasServer is displayed as “UDAS” server by DAS tools (Figure 2).
Only access HW (miniWiggler or on-board) visible
This means that the layers from tool to access HW are working properly. Hints for resolving this situation are
not in the scope of this appnote.
3.1.2 TAS client error: session name or password
This will happen for instance when a DAS tool was started first and the TAS Basic Client afterwards. The DAS
tool will start an unnamed session and the TAS Basic Client is setting the username as default session name
(Figure 2). In this situation the user just needs to delete the username from the session name entry in the GUI.
3.1.3 Problem: DAS remote access does not work
TAS and DAS use different protocols for the socket-based communication between client and server (Figure 1).
This means that remote access will only work when all clients use a DAS API DLL which matches the protocol
the server is using.
3.1.4 UDAS stops when a native TAS tool is started
This can only happen when a legacy DAS installation is active, which means that TAS was not installed in a
regular way, because it would uninstall this legacy DAS installation. In this situation the TAS Server, started
manually from any directory, will automatically kill the legacy UDAS server. When just using regular DAS and
TAS installers this situation can never happen.
4 of 9 V1.0
2023-05-04
restricted
TAS for DAS users
Using DAS tools and libraries with a TAS installation
Table of contents
3.1.5 Legacy DAS tool does not work
Tool uses a local das_api.dll
Since the local DLL will use the old DAS socket protocol (Figure 1), this setup cannot work. The simplest
workaround is to delete the das_api.dll in the legacy tool directory. The DLL loading will use then usually the
DLL search path and find the new installed version. However, this may not work if the DLL loading path is
hardcoded in the tool. The option for this case is to replace the DLL by the version from the TAS installation
directory. Please note that for TAS the default DLL is 64-bit, but also a 32-bit variant is provided, which might be
needed by older tools.
5 of 9 V1.0
2023-05-04
restricted
TAS for DAS users
Using DAS tools and libraries with a TAS installation
Table of contents
4 Emulator access with TAS
The emulator access with TAS does not require a specific server, it is established with the regular TasServer.
The TasServer needs to know the IP address of the active emulator. It is provided as target identifier with the
keyword edas or EDAS in front.
Figure 3 Screenshot of an established emulator access
Steps for establishing emulator access:
• Open a TAS tool like a TAS Basic Client.
• Enter “edas <emulator IP address>” as target identifier in the target select window.
If the port number is not 7745 it must be provided as well after the IP address.
Example: edas vihlazebu11.vih.infineon.com:1234
• After a few seconds the connection is established, and the device is listed.
• At this point the device is visible for any DAS tool.
6 of 9 V1.0
2023-05-04
restricted
TAS for DAS users
Using DAS tools and libraries with a TAS installation
Table of contents
5 DAS changes for TAS implementation
The following key words from the DAS source code represent features which are not supported or have a
different behavior for the TAS based implementation.
Not supported:
• DAE_AR_GET_LAST_ERROR
• DAE_AW_DAP_UART_MODE_xxx
• DAE_AW_DAP_TELEGRAM, DAE_AR_DAP_REPLY
• DAE_AW_DAPCON_PIN_CNTRL
• DAE_ARW_ECF_SERVER_ADDRESS
• DAE_AR_ECF_SOFTWARE_UPDATE_WWW_ADDRESS
• DAS_TS_RW_UNCHANGED
Different behavior:
• cancel_lists() has no effect
• DAS_LC_WILL_NOT_WAIT has no impact on wait_list() behavior if used
• DAS_ERROR_DEVICE_RESET notification:
− If the reset was before the DAS list execution, it is notified with the list error code
and the first transaction, if the address map of this transaction is 0 or 1.
− If it is during the list execution it will be only notified with the list error code
• TasServer automatically disables Native JTAG Mode when the last client disconnects from this target
7 of 9 V1.0
2023-05-04
restricted
TAS for DAS users
Using DAS tools and libraries with a TAS installation
Revision history
Revision history
Document Date of release Description of changes
version
V0.1 2022-09-01 Initial DRAFT version
V0.6 2023-03-02 First version
V1.0 2023-05-04 Version for DAS V8.0 release
8 of 9 V1.0
2023-05-04
Disclaim er
Trademarks
All referenced product or service names and trademarks are the property of their respective owners.
IMPORTANT NOTICE
Edition 2023-05-04 The information contained in this application note is For further information on the product, technology,
given as a hint for the implementation of the product delivery terms and conditions and prices please
Published by only and shall in no event be regarded as a contact your nearest Infineon Technologies office
description or warranty of a certain functionality, (www.infineon.com).
Infineon Technologies AG condition or quality of the product. Before
81726 Munich, Germany implementation of the product, the recipient of this
application note must verify any function and other WARNINGS
technical information given herein in the real Due to technical requirements products may contain
© 2023 Infineon Technologies AG. application. Infineon Technologies hereby disclaims dangerous substances. For information on the types
any and all warranties and liabilities of any kind in question please contact your nearest Infineon
All Rights Reserved. (including without limitation warranties of non- Technologies office.
infringement of intellectual property rights of any
Do you have a question about this third party) with respect to any and all information
given in this application note. Except as otherwise explicitly approved by Infineon
document? Technologies in a written document signed by
authorized representatives of Infineon
Email: [email protected] The data contained in this document is exclusively Technologies, Infineon Technologies’ products may
intended for technically trained staff. It is the not be used in any applications where a failure of the
responsibility of customer’s technical departments product or any consequences of the use thereof can
Document reference to evaluate the suitability of the product for the reasonably be expected to result in personal injury.
AppNote Number intended application and the completeness of the
product information given in this document with
respect to such application.
