cancel
Showing results for 
Search instead for 
Did you mean: 

DAVE™

User5327
New Contributor
Hi all,
can someone help me how to use external j-link....?

I want use J-Link EDU from SEGGER: http://www.segger.com/j-link-edu.html to debug MCU in relax kit.

I have connected "Cortex Debug" pins according to manual: 89.attach

connection:
nTRST: I did not use
TDI: I used pin 8 at X5 (cortex debug - on relax kit board)
TMS: I used pin 2 at X5 (cortex debug - on relax kit board)
TCK: I used pin 4 at X5 (cortex debug - on relax kit board)
RTCK: I did not use
TDO: I used pin 6 at X5 (cortex debug - on relax kit board)
nRST: I used pin 10 at X5 (cortex debug - on relax kit board)


But I had problem with connection...

I tried to use Dave3 ... in config debug a chose Target: Relax kit; connection: j-link over USB(JTAG)
... error log from dave3:

Using Debug Target Configuration:
Target: Infineon XMC4500 Relax kit
Selected CPU type: ARMv7EM
Register file: C:/DAVE-3.1.6/DAVE-3.1/Debugger/etc/sfr/CM4/DeviceSupport/Infineon/XMC4500_series/XMC4500.xml
Communication: J-Link over USB (JTAG)
Debug Instrument Module: dijlinkarm
Using Flash Configuration:
Monitor : fARMv7M.sre
Workspace address : 0x20000000
Number of devices : 1
Device 0:
Address : 0xC000000,0x8000000
Vendor : Infineon
Chip : XMC4XXX/1024K
Width : 32
Size : 1048576
Number of chips : 1
Unused address line : 0
Configuration: Default
Using Java Link Version 1.113
Starting Debugger...
TASKING VX-toolset for ARM: debugger, Build 188
Copyright 2006-2013 Altium BV

The debug instrument IO could not be initialized.
The GDI debug instrument provided the following error message.
An error occurred while connecting to the target. The exact cause is unknown, but possibly, the J-Link is not connected to the target properly.


Does someone know what is wrong?

Regards
0 Likes
6 Replies
Not applicable
Hi Koumak,

Is the on-board debugger of the relax kit is still connected?

Regards,
Jackson
0 Likes
User5327
New Contributor
I already split relax kit into two boards - debugger and alone MCU => on-board debbuger is disconnected
(as same as in video here:
http://www.infineon.com/cms/en/product/microcontrollers/32-bit-industrial-microcontrollers-based-on-...)

Note: I already tried SWD debugging - and it is OK ... So I dont know what is wrong with JTAG debbuging...

Regards
0 Likes
Not applicable
Let me check for you and I ill get back to you as soon as possible.
0 Likes
Marillion
Employee
Hi Koumak,

the JTAG Interface of the XMC4000 must be enabled by pulling up the TRST# pin of the XMC4000 with a resistor. After a system reset P0.8 is working asTRST# with a
weak pull-down active. So, tie pin 24 (P0.8=TRST#) of pin header X2 to pin 38 (VDD3.3)
Does this help?

Regards
Marillion
0 Likes
User2235
New Contributor
Dave-3 is now supporting the segger jlink? Or only the EDU version.

Ari.
0 Likes
Not applicable
Hi Ari,

You still can use segger J-Link h/w. However you can only get limited debug features since we are using Tasking debugger s/w.

Best regards,
Sophia
0 Likes
Top labels