ReleaseNotesforDeviceAccessServer(DAS)

20130809

GeneralHints:

1. UpgradingDAS:IfyouupgradefromanolderDASversion,pleasecheckyoursetup
withtheoldversiondirectlybeforetheinstallationofthenewversion.
ThisallowstodistinguishclearlybetweentherareproblemscausedbyanewDAS
versionandallkindofproblemscompletelyunrelatedtotheinstallation.

2. DurationoftheInstallation:DependingonthestatusofyourWindowsregistry(in
particularincaselotsofsoftwareisinstalled),theinstallationmaytakeseveral
minutes,duetotheUSBdriverinstallation.Thereisnodefinedlimit,installation
timesof10minuteshavebeenobserved,inparticularon64bitWindowsversions.If
possiblepleaseavoidterminatingtheinstallation.
Hint:Youcancheckthestatusofdpinst.exewiththeWindowstaskmanager.

3. UseUSB3.0orhighspeedUSB2.0:PleaseusealwayshighspeedUSB2.0ports,hubs
andqualitycables.Thispreventsallkindofproblems,inparticularalsoverysporadic
failures.
SPD:AnSPDdeviceconnectionisonlyestablishedifthereisahighspeedUSB2.0
connection.
USBpowersupply:PleaseuseadedicatedpowersupplyforUSBhubswhenseveral
USBdevicesareconnected.

4. Resetpullup:Afterreleasingresetonthetargetboard,theresethastobe
deactivatedwithin200safterthetoolreleasesthepin.Thereforeensurethatthe
resetpinpulluponthetargetboardhasalowenoughvaluetodeactivatethereset.
OtherwisetheDAShaltafterresetfunctionmaynotworkorthedeviceisnoteven
recognized.

5. ConflictswithotherUSBdevices:ThereisageneralissuewiththeUSBinfrastructure
anditsimplementations,thatnotallcomponentsfulfillhighestqualityrequirements.
IthasbeenobservedinrarecasesthatthecombinationofminiWiggler(s)andother
USBHW,connectedoverUSBhubscanresultincrashesofthePC.Thisishighly
dependentontheusedUSBHWanddrivers.
UsuallytheseproblemsdisappeariftheUSBhub(possiblyalsoaspartofanotebook
dockingstation)isremovedoradifferenttypeofhubisused.
ItmayalsobenecessarytouseanotherUSBportofyourcomputer.
AnothergeneralrootcauseforsuchcrashesaregroundloopsvialongUSBandother
cables.ThiscanevendamagetheUSBportofaPC.Pleasecheckifthereisariskin
yoursetup.

6. FT2232HandFT2232Dchips:TheUSBdriveroftheFTDIUSBtoserialchips,usedfor
theminiWigglerandonboardwigglers,willsporadicallyfail(afterhoursordays)ifa
mixtureofFT2232HandFT2232Dchipsisused.FT2232HandFT2232Dchipscanbe
easilydistinguishedbytheirpackagesize.
AllnewevaluationboardsandminiWigglersusethefasterFT2232Hchip.

7. Firewall:Pleaseensurethatyourfirewallsettingsallowthesocketbased
communicationbetweentheDAScomponents.ItmustbepossibletostartaDAS
ServerwiththeDASServerControlPanel.

8. IndicatingJTAGusage:TheminiWigglerhasasignalwithapullupconnectedtopin
12(GND)oftheOCDSL1connector.ThisisusedbytheUDASservertocheck
whetherthetargetisconnectedwithJTAGornot.
PleaseensurethatthisOCDSL1pinisconnectedtoGNDincaseofJTAG.

9. Noparalleloperationof"JTAGoverUSBChip"ServerandUDASServer:"JTAGover
USBChip"ServerandUDASServerwillnotruninparallel.Runningserversarevisible
inthe"DASServerControlPanel"tool.

10. Uninstallation:DAScannotbeautomaticallyuninstalledbyanapplication.Reasonis
thatDASispossiblyusedbyseveralapplicationslikedebuggers,flashprogrammer
tools,etc.
PleaseusetheregularWindowsprocedurestouninstallDAS.Forinstanceon
Windows7:
Start>ControlPanel>Uninstallorchangeaprogram>SelectDAS

11. Virtualmachines:ItisdiscouragedtorunDASonavirtualmachinewhentheAccess
HW(miniWiggleretc.)isconnectedviaUSB.Theperformanceofsuchasetupisvery
low.Withvirtualmachines,areliableSPDconnection(ifpossibleatall)cannotbe
guaranteed.(Seealsotopoint3.)

=======DASV4.4=======
Date:20130809
Customers:Internal,toolpartnersandcustomers

Changes:

UDASServer(V3.4)
1. SupportoflatestdevicesoftheAURIXfamily
2. ImprovedrobustnessagainstUSBfailures
3. AURIX:OCDSisnotanymoreenabledincaseofresetwithouthalt
4. AURIXJTAG:WorkaroundforOCDS_TC.040added
5. SupportofgalvanicisolationandDXCPLfrontendboardsofminiWigglerV3.1

DASTools
1. Informationaboutdeviceconnectionimproved(DASDeviceInfowindow)

=======DASV4.3=======
Date:20130312
Customers:Internal,toolpartnersandcustomers

Changes:

UDASServer(V3.3)
6. SupportoflatestdevicesoftheAURIX,XMC4000andXMC1000families
7. MaximumnumberofconnectedAccessHWs(miniWiggleretc.)increasedfrom4to16
8. USBconnectionsetuptoAccessHWsimproved(responsiveness,robustness)
9. AutomaticadaptationofSPDsamplerate
10. TriCore:UniquedeviceIDfromCOMDATAshownasdeviceID1afterDASinitiatedreset
11. TriCore:DirectCOMDATAaccesswithautomaticCOM/RWModeswitching
12. AURIX:init_device()supportsnow256bitkeys
13. AURIX:R/Waccessesoptionalwithlowestbusmasterpriorityand/ornotinSupervisor
Mode
14. AURIX:IncreasedDAPperformancetoread2MByte/s,write1.2MByte/s
15. LeavingNativeJTAGmodedoesnottriggeraJTAGresetanymore
16. SET_DEVICEcanbeusednowbeforeconnect_to_device().Useonlywhenabsolutely
needed!
17. BareOnBoardWiggler(BOBW)supported
18. LatestUSBdriversforFTDIchip(V2.8.24)used

mcdxdas.dll
2. SupportoflatestdevicesoftheAURIX,XMC4000andXMC1000families
3. TriCore:Cansetnowgenericbreakpointsinflash(beforeonlypossiblewithHW
breakpoints)

=======DASV4.0=======
Date:20120305
Customers:Internal,toolpartnersandcustomers

Changes:

General
1. Robustnessandresponsivenessimproved
2. DASDeviceScannershowsAccessHWnameifnodeviceisresponding
3. Supportforlatestdevicesadded,inparticularXMC4000family
4. SupportsWindows7,VistaandXP
Windows2000isnotsupportedanymore
WindowsXPandVistawillshowwarningsduringtheUSBdriverinstallation
5. LatestUSBdriversandlibsforFTDIchipareusedinUDASserver

=======DASV3.3=======
Date:20110217
Customers:Internal,toolpartnersandcustomers

Changes:

General
1. Supportforlatestdevicesadded
2. mcdxdas.dllimproved(latestdevices,breakpointimplementation,etc.)
3. MCDBasicClientselectwindowshowsnowalsoaccessHWwithoutaconnecteddevice

UDASServer
1. XE166/XC2000BSLprogrammingsupportforlatestdevicesadded

=======DASV3.2.3=======
Date:20101011
Customers:Internal,toolpartnersandcustomer

Changes:

General
1. Supportforlatestdevicesaddeddas_dad.dlladdedagainininstallationforsupporting
legacytools
2. mcdxdas.dllcontrolsnowrunledofminiWiggler(usedbyMCDBasicClient)
3. MCDBasicClienthasnowacoreselectwindowandloadsmcdxdas.dlldynamically

UDASServer
4. XE166/XC2000supportforlatestdevicesadded

Limitations
1. mcdxdas.dllanddas_dad.dlldon'tfullysupportverylatestXE166/XC2000devices

=======DASV3.1.0=======
Date:20100820
Customers:Internal,toolpartners

Changes:

General
1. Supportforlatestdevicesadded
2. das_dad.dllremovedfrominstallation(usemcdxdas.dllinstead)

UDASServer
1. USERPINS_GETdoesn'treturnerroranymoreincaseofminiWigglerinJTAGmode
2. TRIGGERPINS_GETdoesn'treturnerroranymoreincaseofminiWigglerinDAPmode
3. MinorbugfixedinSET_DEVICEimplementation
4. RESETpin:Nospikeanymore,whichoccurredduringdisconnectoftheECFHW
5. TriCore:Improvedrobustnessoferrornotificatione.g.foraccesstounimplemented
addresses
6. XE166/XC2000connectedoverJTAG:Bugfixedforresetwithouthalt
7. miniWigglerJTAG/DAP/SPD:USR8pin(notonconnector)defaultvaluechangedfrom0
to1
8. ToolscanchecknowavailabilityofSPDfeature(dependsonUSB2.0connection)

=======DASV3.0.0=======
Date:20100412
Customers:Internal,toolpartnersandcustomers

Changes:

General
1. SupportofnewTriCore,XC2000,XE166andXC800derivatives
2. MCDAPIsupportaddedforTriCore,XC2000,XE166andXC800(mcdxdas.dll)
3. MCDBasicClientreplacesDAD(das_dad.dll)basedDASBasicClient
4. WHQLcertifiedUSBDriverwillbeinstalledautomatically.
miniWiggler,onboardWiggler:Windows2000;WinXP32+64bit;Vista32+64bit;
Win732+64bit
USBWiggler(darkgraybox):Windows2000;XP;Vista;7(all32bitonly)
5. Generalminorchangesforimprovedrobustness

Previousreleasesomitted.