Products / DDS / Download

Download


DDS V7.2
Software
Demo Version
Get a demo version of DDS V7.2.
The DDS demo version is limited to max. 85 instrumentation and calibration entities. Apart from that limitation, the demo version is fully functional and contains all DDS filters and components.

Documentation
DataSheet
Get the DataSheet of DDS V7.2

DDS V5.9.R0
Software
Hotfix 1
Download Hotfix 1 of DDS V5.9.R0.
Toleration of Tasking TriCoreVX V3.4.x
The ELF file generated from the compiler TriCoreVX V3.4.x is tolerated (but not officially supported) now.

Note: This Hotfix must be installed manually by copying the file 'ImpELF.dll' into the DDS main directory. The file 'Hotfix1.pdf' should be copied into the DDS subdirectory 'Docu'. (the files are contained in the Hotfix 1 zip file)

Hotfix 2
Download Hotfix 2 of DDS V5.9.R0.
(1) Toleration of Tasking TriCoreVX V3.4.x
Support of multiple "0"-entries in symbol table also for codeSymbols
(2) Bugfix related to Compiler DIAB 5.8.0.0
Support of new OpCode

Note: This Hotfix must be installed manually by copying the file 'ImpELF.dll' into the DDS main directory. The file 'Hotfix2.pdf' should be copied into the DDS subdirectory 'Docu'. (the files are contained in the Hotfix 2 zip file)

DDS V4.2.0
Software
Hotfix 1
Download Hotfix 1 of DDS V4.2.0.
The current version of the Tasking TriCore compiler places definitions -even for simple types (like 'signed int') - at the place of their first usage.
This means, that much more information needs to be processed (like (inlined) subroutines or formal parameter lists) to be able to reference
to such types in the according cases. The processing has been omitted before to avoid possible higher memory pressure during address import.

Note: This Hotfix must be installed manually by copying the file 'ImpELF.dll' into the DDS main directory. The file 'Hotfix1.pdf' should be copied into the DDS subdirectory 'Docu'. (the files are contained in the Hotfix 1 zip file)

Hotfix 2
Download Hotfix 2 of DDS V4.2.0.
In case of bitfield members with a data type > 1, the new Tasking TriCore compiler version V2.2r3p1 may refer to a smaller data type within the ELF file. Referring to a data type with a byte size of 1 allows the compiler to use any address (e.g. uneven addresses).
When an ASAP2 export is performed, DDS is looking at the data type as defined within DDS. Even if the address/bit mask combination generated in the ASAP2 file may logically be correct, there is the problem, that application systems will have problems to access the data. This is due to the fact, that there is an uneven address but a data type with a size of e.g 2 or 4 bytes that actually would require an alignment of at least 2 in case of TriCore.
This problem is fixed by an extension in the ASAP2 export filter.

Note: This Hotfix must be installed manually by copying the file 'ExpA2.dll' into the DDS main directory. The file 'Hotfix2.pdf' should be copied into the DDS subdirectory 'Docu'. (the files are contained in the Hotfix 2 zip file)

DDS V4.1.0
Software
Hotfix 1
Download Hotfix 1 of DDS V4.1.0.
The current DServer version doesn't support online array elements:
In case of online data, there are two kinds of (local) members possible:
1. array elements
2. onlineUnion members
The current DServer version always creates onlineUnion members when creating a (local) member. This hotfix solves this problem:
-> When the name of the member, which has to be created, contains square brackets, an array member will be created. Otherwise, an onlineUnion member will be created.

Note: This Hotfix must be installed manually by copying the file 'Seml.dll' into the DDS main directory. The file 'Hotfix1.pdf' should be copied into the DDS subdirectory 'Docu'. (the files are contained in the Hotfix 1 zip file)

Hotfix 2
Download Hotfix 2 of DDS V4.1.0.
The current version of the Tasking TriCore compiler places definitions -even for simple types (like 'signed int') - at the place of their first usage.
This means, that much more information needs to be processed (like (inlined) subroutines or formal parameter lists) to be able to reference
to such types in the according cases. The processing has been omitted before to avoid possible higher memory pressure during address import.

Note: This Hotfix must be installed manually by copying the file 'ImpELF.dll' into the DDS main directory. The file 'Hotfix2.pdf' should be copied into the DDS subdirectory 'Docu'. (the files are contained in the Hotfix 2 zip file)

Hotfix 3
Download Hotfix 3 of DDS V4.1.0.
In case of bitfield members with a data type > 1, the new Tasking TriCore compiler version V2.2r3p1 may refer to a smaller data type within the ELF file. Referring to a data type with a byte size of 1 allows the compiler to use any address (e.g. uneven addresses).
When an ASAP2 export is performed, DDS is looking at the data type as defined within DDS. Even if the address/bit mask combination generated in the ASAP2 file may logically be correct, there is the problem, that application systems will have problems to access the data. This is due to the fact, that there is an uneven address but a data type with a size of e.g 2 or 4 bytes that actually would require an alignment of at least 2 in case of TriCore.
This problem is fixed by an extension in the ASAP2 export filter.

Note: This Hotfix must be installed manually by copying the file 'ExpA2.dll' into the DDS main directory. The file 'Hotfix3.pdf' should be copied into the DDS subdirectory 'Docu'. (the files are contained in the Hotfix 3 zip file)

DDS V4.0.1
Software
Update 1
Download Update 1 of DDS V4.0.1.
With this update, DDS supports the Compiler Tasking TriCoreVX v2.1.

Hotfix 1
Download Hotfix 1 of DDS V4.0.1.
DDS doesn't yet support the ASAP2 "GROUP" keyword directly (there is no corresponding 'group'-Entity in DDS).
However, there is/was a workaround:
  • The ASAP2 export filter creates "GROUP" objects based on the DDS component- and/or software grouping.
  • The ASAP2 import filter creates component- and/or software grouping based on ASAP2 "GROUP" objects.
This workaround is not supported in DDS version 3.0, 3.1 and 4.0.1. The version 2.3 is the last DDS version supporting this workaround.
The workaround is now re-activated in Hotfix 1 of DDS 4.0.1.

Note: This Hotfix must be installed manually by copying the files 'ImpA2.dll' and 'DDS.ini' into the DDS main directory. The file 'Hotfix1.pdf' should be copied into the DDS subdirectory 'Docu'. (the files are contained in the Hotfix 1 zip file).

DDS Tools
The following tools are provided "as is". They are not supported and there will be no warranty.

Calibration Data Converter V1.6
The program CalConv converts a DCM- or a CVX Vx.y file into a CVX1.0 file. To run this program you need the .NET Runtime V1.1 and the DDS ASAP2 Parser (which is contained in all DDS installations).

Calibration Data Converter V2.12
The program CalConv converts a DCM- or a CVX Vx.y file into a CVX Vx.y file. To run this program you need the .NET Runtime V2.0 and the DDS ASAP2 Parser (which is contained in all DDS installations).

Infobox