Announcements

Help us improve the Power & Sensing Selection Guide. Share feedback

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
Chaabane
Level 3
Level 3
First solution authored First like received 10 replies posted

Hello all 🙂

I'm trying to use the miniwiggler v3 on my dev board TC275 Lite

I'm using also Aurix Development Studio

Chaabane_1-1711275339834.png

 

But it shows me the following error

Chaabane_2-1711275474388.png

 

I reversed the connected but got the same error !

 

Is there a documentation that explain how to use it ?

 

Thx to all

0 Likes
1 Solution
MoD
Employee
Employee
10 likes given 50 likes received 500 replies posted

The miniWiggler can communicate via JTAG and DAP dependent of the used cable. The on board  miniWiggler can only communicate in DAP mode. DAP is always the better choice because it is faster and secure.

View solution in original post

0 Likes
9 Replies
Basil_Mathai
Moderator
Moderator
Moderator
50 replies posted 10 solutions authored 25 replies posted

Hi,

Is your board brand new?
Were you able to connect with Memtool?
Also please close any other open DAS clients as it will cause above error.


0 Likes

Hello,

 

Yes, my board is brand new.

I can't connect with memtool and I restarted my computer to make sure no DAS clients are running.

Below is the logs from memtool

----------------------------------------------------------

Connection Failed Report from
Infineon Memtool Target Interface, Version: 1.19.11
created: 03/27/24, 09:00:37

----------------------------------------------------------

Windows version:
Win8 ()
Admin: yes

IMT version:
Release: 2021.08
Build: 5012
Path: C:\Program Files\Infineon\Memtool 2021

Target configuration file:
C:\Users\userAAA\Documents\Infineon\IMT 2021\Targets\TriBoard_TC27xD_das.cfg

Error messages:
Controller0.Core0.Tc2CoreTargIntf: Can't connect target !
Controller0.Core0.Tc2CoreTargIntf: Can't connect target device via DAS !

Settings:
PortType: DAS
CommDevSel:
TargetPort: Default
TargetPortId: 553582592
DasIsDefault: n
MaxJtagClk: 5000
CheckJtagId: y
ScanJTAG: n
Ocds1ViaPod: n
EtksArbiterMode: None
EtksWaitAfterArbitrationTime: 0
RefreshJtag: n
RefreshHarr: n
ReenableOcds: y
ReduceJtagClock: n
UseDap: n
DapMode: 2PIN
JtagMuxPort: -1
UseNewJtagEngine: y
ConnOption: Reset
SetDebugEnableAb1DisablePin: n
ResetWaitTime: 500
ResetMode: Default
OpenDrainReset: n
DiswdtOnReset: y
ExecInitCmds: y
InitScript Script:
SET 0xF80020A8 0x8000
SET 0xF80020AC 0x8000

ExecOnConnectCmds: n
OnConnectScript Script:
Script is empty
ExecOnExtRstCmds: n
ResetPulseLen: 10
AddResetDelay: 0
UseTrstOnReset: n
ExecEmemInitOnReset: 0x00000000
SimHsmBootEnabled: n
UnlockInterface: n
BootPasswd0: 0x00000000
BootPasswd1: 0x00000000
BootPasswd2: 0x00000000
BootPasswd3: 0x00000000
BootPasswd4: 0x00000000
BootPasswd5: 0x00000000
BootPasswd6: 0x00000000
BootPasswd7: 0x00000000
PasswordFile:
UnlockInterfaceDelay: -1
HandleBmiHeader: n
SetAutOkOnConnect: n
DontUseWdtSusp: n
InitCore0RamOnConnect: n
IgnoreFailedHaltAfterResetOnConnect: n
TrySystemResetAfterFailedHardwareReset: n
RunStabilityTestOnConnect: n
RunStabilityTestCycles: 10
IgnoreFailedEnableOcdsOnConnect: n
UseLbistAwareConnect: n
BlockResetBeforeGo: n
TC4SpecialConnect: n
TC4InitCore0Ram: n
EnableAutomaticCsrmStart: n
EnableAutomaticCsrmRunControl: n
MaxTry: 1
ForceEdMode: -1
UseDflashAccessFilter: y
DetectResetWhileHalted: y
UseTranslateAddr: y
DownloadToAllRams: n
HaltAfterReset: n
HaltAfterHardwareReset: n
TargetAppHandshakeMode: None
TargetAppHandshakeTimeout: 100
TargetAppHandshakeParameter0: 0x00000000
TargetAppHandshakeParameter1: 0x00000000
TargetAppHandshakeParameter2: 0x00000000
TargetAppHandshakeParameter3: 0x00000000
ConvertSuspendSignalToPulse: n
SimioAddr: g_JtagSimioAccess
UseStmForPtm: 1
ExecOnStartCmds: n
OnStartScript Script:

ExecOnHaltCmds: n
OnHaltScript Script:

ExecOnHaltCmdsWhileHaltedPeriod: 0
UseTriggerToBreak: y
UseTL2OnHalt: y
UseOstateStable: y
AllowJtagResetWhileRunning: y
MaxAccRetry: 1
AccRetryDelay: 10
DefOcdsReserved:
UseRestartWhileRunningHandling: n
DebugResetOnDisconnect: n
IgnoreEmemAccessErrors: n
RemapEmemAccess: n
EnableAutomaticHsmStart: n
EnableAutomaticHsmRunControl: n
ReadPmcsrWhileRunning: y
MultiChipDbgMode: 0
MultiChipDbgInp: 1
MultiChipDbgOut: 6
MultiChipDbgCtl: 7
IgnoreShortHalt: n
HaltOnBreakOnly: n
IvIcacheOnHalt: y
IvPlbOnHalt: y
SuspendSlaveCores: n
FilterMemAcc: y
PtmRefClock: 0
DasDllPath: das_api.dll
DasHost:
DasTryStartSrv: y
DasSrvPath: servers\udas\udas.exe
DasStopSrv: y
DasResetHelperBreakAddr: main
DasResetMode: 2
DasRemoveLogFile: n
DasForwardSerNum: n
DasSrvSel: -1
DasPortType: 0
DasPortSel: 0
DasCmdTimeout: 1000
DasWaitAfterConnect: 0
DasDisconnectSrv: n
DasResetDelay: 0
DasWaitAfterGo: 0
DasApiLogging: n
GoExtOption:
DontUseTriggerLines: n
DontUseSingleStep: n

JTAG target infos:
JTAG-ID: 0x00000000
UsedJtagClk: 0 MHz
ExtVoltage: 0.0 V
IntVoltageUsed: n
CHIPID: 0x00000000
STSTAT: 0x00000000

DAS related information:
DAS DLL Version:
Server started by UDE: C:\Program Files\DAS64\servers\udas\udas.exe
Server name: UDAS
Server manufacturer: Infineon
Server version: V3.10
DAS-API version: V4.1
Server lib version: V3.0
last DAS error: 4
last DAS function: connect_to_device


0 Likes
Chaabane
Level 3
Level 3
First solution authored First like received 10 replies posted

I tired another board and it worked as expected.

 

What might be wrong the first board ? it is also brand new and used only CAN bus on it. ?

0 Likes
Chaabane
Level 3
Level 3
First solution authored First like received 10 replies posted

After few tests it seems that I can't get it work all the time with my board. it works once out of 1000 attempt ?

 

Can you please help ?

 

0 Likes
MoD
Employee
Employee
10 likes given 50 likes received 500 replies posted

You have connected the TC275 lite Kit via USB to your PC?
Additional you have connected a miniWiggler to the TC275 lite Kit and to your PC?

When you can answer both with yes, then remove the miniWiggler from the lite Kit and your PC and test again. 
Most (more or less all) Infineon TCxxx boards haven a miniWiggler already on board and an external miniWiggler is not needed. You should connect always only 1 miniWiggler to a board.

0 Likes
Chaabane
Level 3
Level 3
First solution authored First like received 10 replies posted

Hello MoD,

 

You have connected the TC275 lite Kit via USB to your PC?

YES
Additional you have connected a miniWiggler to the TC275 lite Kit and to your PC?

YES

 

I have this kit

https://www.infineon.com/cms/en/product/evaluation-boards/kit_aurix_tc275_lite/

Are you saying that the onbaord debugger on the mentionned dev kit is the same as the miniwiggler v3 ?

 

If I want to use the JTAG on the miniwiggler v3, should I only plug the miniwiggler and not the USB of the devkit

0 Likes
MoD
Employee
Employee
10 likes given 50 likes received 500 replies posted

Yes, the on board wiggler on the mentioned kit is functional identically to the miniWiggler. For this board no external miniWiggler is needed. 

The USB of the devkit must be connected because it is the also the supply. Therefore it is impossible to not connect the USB of the devkit. 

I don't understand why you will use the external miniWiggler. When needed then connect the USB of the kit e.g. to a mobile charger.

0 Likes
Chaabane
Level 3
Level 3
First solution authored First like received 10 replies posted

Thank you for the clarification.

I though that the miniwiggler is more robust than the onbaord debugger. Now it makes since why I was having unexpected behaviors.

 

I see in the miniwiggler a JTAG port ? is the JTAG available as well in the onboard debugger ?

0 Likes
MoD
Employee
Employee
10 likes given 50 likes received 500 replies posted

The miniWiggler can communicate via JTAG and DAP dependent of the used cable. The on board  miniWiggler can only communicate in DAP mode. DAP is always the better choice because it is faster and secure.

0 Likes