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

cross mob
lock attach
Attachments are accessible only for community members.
SunshineQAQ
Level 4
Level 4
50 replies posted 100 sign-ins First like received
Hi, I use xmc-link can not give xmc7100 chip emulation, and after burning the program once, the program then burned in there is no reaction, why? Best Regards
0 Likes
20 Replies
Pradeep_PN
Moderator
Moderator
Moderator
250 sign-ins 100 solutions authored 25 likes received

Hi @SunshineQAQ ,

Can you please confirm whether you are able to program the boar using XMC Link , You ca try simple Blink LED program to test it.

Best Regards
Pradeep.

0 Likes

Hi,

I had no problem burning and emulating the xmc4200 chip using xmc-link. Not with the xmc7100 chip, not even the burn simulation, the program won't burn and the lights won't be controlled.

Best Regards

0 Likes
Pradeep_PN
Moderator
Moderator
Moderator
250 sign-ins 100 solutions authored 25 likes received

Hi @SunshineQAQ ,

Can you please try using miniprog 4 Which supports XMC 7000 series controllers instead of XMC link.

Best Regards
Pradeep.

 

0 Likes

Hi, Miniprog 4 is supported, xmc-link is not, is it because xmc-link cannot burn the xmc7000 series? Best Regards

0 Likes
Pradeep_PN
Moderator
Moderator
Moderator
250 sign-ins 100 solutions authored 25 likes received

Hi @SunshineQAQ ,

Yes, Miniprog4 supports XMC 7000 series .As per XMC Link board user manual there is support for XMC 1000 and XMC 4000 but the latest version of segger J-Link is released with a support of XMC 7000 so installing the latest version of Segger J-Link with XMC Link support XMC 7000.

Best Regards
Pradeep.

 

Best Regards
Pradeep.

0 Likes

Hi,

The xmc-link in my hand is this one, can it be burned and emulated to the xmc7100 chip?

SunshineQAQ_0-1703037068108.jpeg

 

Best Regards

0 Likes
Pradeep_PN
Moderator
Moderator
Moderator
250 sign-ins 100 solutions authored 25 likes received

Hi @SunshineQAQ ,

Please refer to the below response.

Best Regards
Pradeep.

0 Likes

Hi,

xmc-link can give xmc7200 development board burn program ah, this does not show that XMC-Link can give xmc7000 burn program, but can not give xmc7100 burn program, I do not know why?

Best Regards

0 Likes
Pradeep_PN
Moderator
Moderator
Moderator
250 sign-ins 100 solutions authored 25 likes received

Hi @SunshineQAQ ,

Are you able to successfully program the XMC 7200 with XMC link ?If yes can you please show me the setup you made ?

What do you mean by XMC 7200 development board, are you pointing to XMC 72 EVK or your own custom board ?

Can you please elaborate the question ?

Best Regards
Pradeep.

 

0 Likes

Hi,

I use the XMC72 EVK, I plug the XMC-Link directly into the jlink interface of the XMC72 EVK, and then switch to jlink in the MTB can burn simulation.

Best Regards

0 Likes
Pradeep_PN
Moderator
Moderator
Moderator
250 sign-ins 100 solutions authored 25 likes received

Hi @SunshineQAQ ,

The XMC 72 EVK has an on board debugger , so we suspect you are connecting the XMC 72 EVK and the XMC link to the USB ports of same PC so it is using on board debugger of XMC 72 EVK to burn the program instead of XMC link.

To test the above point power the board externally or connect the board to USB port of a different PC and XMC Link to your PC and try burning the program.

Best Regards
Pradeep.

0 Likes

Hi,

So xmc-link does not support xmc7000, miniprog4 supports xmc7000, right?

Best Regards

0 Likes
Pradeep_PN
Moderator
Moderator
Moderator
250 sign-ins 100 solutions authored 25 likes received

Hi @SunshineQAQ ,

Due to some conflicts in my understanding, I took some time to dig in and it came to my knowledge that XMC Link is supported with XMC 7000 with the latest version of Segger J-Link. Apologies for my earlier response. But you can go ahead with XMC Link and XMC 7000. Thanks for your understanding!

Best Regards
Pradeep.

 

 

0 Likes

Hi,

    I read in another post that XMC-Link does not support the xmc7000 series, so do we support it or not?

Best Regards

0 Likes
Pradeep_PN
Moderator
Moderator
Moderator
250 sign-ins 100 solutions authored 25 likes received

Hi @SunshineQAQ ,

Please update the J-Link driver to the latest version and try again with XMC -Link.

If you are facing any problems please let me know, Please share the snap shot of the problem if possible .

Best Regards
Pradeep.

0 Likes
lock attach
Attachments are accessible only for community members.

Hi,

My jlink is version 7.92a. When I used xmclink to burn xmc72_evk, the console was like the one shown in Figure 1. Then I burned the board of my xmc7100 chip once and it could not be burned in Figure 2.

Best Regards

0 Likes
Pradeep_PN
Moderator
Moderator
Moderator
250 sign-ins 100 solutions authored 25 likes received

Hi @SkyZhang ,

XMC Link supports XMC 7000 series.

You can program and debug the XMC 7000 series controllers using XMC Link.

Steps you nee follow while using XMC Link with MTB .

1)Create on project on XMC 7000 series in MTB(Modus Tool Box)

2)Install the latest version of Segger J-Link .

3)Open the make file of the project and add the below two lines.

            BSP_PROGRAM_INTERFACE=JLink
            MTB_JLINK_DIR=<Path to Segger JLink directory >

Note : While giving the path please make sure you are giving the path in Forward slashes( / ).

Note : If you want to use XMC Link for all your project then add the above two lines in bsp.mk file instead of application make file.

4)Then generate launches for the project and you start using XMC-Link with XMC 7000 series.

Hope this helps and let me know if you have any further queries.

Best Regards
Pradeep.

0 Likes

Hi,

    I have tried according to your method, but it still doesn't work. After I click program, an error will be reported. The content in notepad is my console information.

SunshineQAQ_0-1706152686708.png

 

SEGGER J-Link GDB Server V7.94d Command Line Version

JLinkARM.dll V7.94d (DLL compiled Jan 11 2024 10:52:52)

Command line: -if swd -device XMC7100-4160_CM7_0_tm -endian little -speed auto -port 2337 -swoport 2338 -telnetport 2339 -vd -ir -localhostonly 1 -singlerun -strict -timeout 0 -nogui
-----GDB Server start settings-----
GDBInit file: none
GDB Server Listening port: 2337
SWO raw output listening port: 2338
Terminal I/O port: 2339
Accept remote connection: localhost only
Generate logfile: off
Verify download: on
Init regs on start: on
Silent mode: off
Single run mode: on
Target connection timeout: 0 ms
------J-Link related settings------
J-Link Host interface: USB
J-Link script: none
J-Link settings file: none
------Target related settings------
Target device: XMC7100-4160_CM7_0_tm
Target device parameters: none
Target interface: SWD
Target interface speed: auto
Target endian: little

Connecting to J-Link...
J-Link is connected.
Firmware: J-Link Lite-XMC4200 Rev.1 compiled Sep 13 2023 14:48:00
Hardware: V1.00
S/N: 599015474
Checking target voltage...
Target voltage: 3.30 V
Listening on TCP/IP port 2337
Connecting to target...
Halting core...
Initializing CPU registers...Connected to target
Waiting for GDB connection...Connected to 0000:0000:0000:0000:0000:0000:0000:0001
GDB client (conn. 944) requested target.xml from GDB Server
Reading common registers: Read register 'r0' (4 bytes) from hardware: 0x00000000
Read register 'r1' (4 bytes) from hardware: 0x00000000
Read register 'r2' (4 bytes) from hardware: 0x00000000
Read register 'r3' (4 bytes) from hardware: 0x00000000
Read register 'r4' (4 bytes) from hardware: 0x00000000
Read register 'r5' (4 bytes) from hardware: 0x00000000
Read register 'r6' (4 bytes) from hardware: 0x00000000
Read register 'r7' (4 bytes) from hardware: 0x00000000
Read register 'r8' (4 bytes) from hardware: 0x00000000
Read register 'r9' (4 bytes) from hardware: 0x00000000
Read register 'r10' (4 bytes) from hardware: 0x00000000
Read register 'r11' (4 bytes) from hardware: 0x00000000
Read register 'r12' (4 bytes) from hardware: 0x00000000
Read register 'sp' (4 bytes) from hardware: 0x00000000
Read register 'lr' (4 bytes) from hardware: 0x00000000
Read register 'pc' (4 bytes) from hardware: 0x00000000
Read register 'xpsr' (4 bytes) from hardware: 0x00000001
Read 4 bytes @ address 0x00000000 (Data = 0x2000B508)
Read 2 bytes @ address 0x00000000 (Data = 0xB508)
Received monitor command: speed 1000
Target interface speed set to 1000 kHz
Received monitor command: clrbp
Received monitor command: reset 0
Resets core & peripherals via SYSRESETREQ & VECTRESET bit.
Received monitor command: halt
Halting target CPU...
...Target halted (PC = 0x100801D0)
Received monitor command: regs
R0 = 40310600, R1 = 00000003, R2 = 00000001, R3 = 00000008
R4 = 00000000, R5 = 00000000, R6 = 00000FC8, R7 = 00000000
R8 = 90900004, R9 = 28003E34, R10= 280B0000, R11= 00000000
R12= 00000800, R13= 280C0000, MSP= 280C0000, PSP= 80010044
R14(LR) = FFFFFFFF, R15(PC) = 100801D0
XPSR 01000000, APSR 00000000, EPSR 01000000, IPSR 00000000
CFBP 00000000, CONTROL 00, FAULTMASK 00, BASEPRI 00, PRIMASK 00

Security extension regs:
MSP_S = 00000000, MSPLIM_S = 00000000
PSP_S = 00000000, PSPLIM_S = 00000000
MSP_NS = 280C0000, MSPLIM_NS = 00000000
PSP_NS = 80010044, PSPLIM_NS = 00000000
CONTROL_S 00, FAULTMASK_S 00, BASEPRI_S 00, PRIMASK_S 00
CONTROL_NS 00, FAULTMASK_NS 00, BASEPRI_NS 00, PRIMASK_NS 00

Reading common registers: Read register 'r0' (4 bytes) from hardware: 0x00063140
Read register 'r1' (4 bytes) from hardware: 0x03000000
Read register 'r2' (4 bytes) from hardware: 0x01000000
Read register 'r3' (4 bytes) from hardware: 0x08000000
Read register 'r4' (4 bytes) from hardware: 0x00000000
Read register 'r5' (4 bytes) from hardware: 0x00000000
Read register 'r6' (4 bytes) from hardware: 0xC80F0000
Read register 'r7' (4 bytes) from hardware: 0x00000000
Read register 'r8' (4 bytes) from hardware: 0x04009090
Read register 'r9' (4 bytes) from hardware: 0x343E0028
Read register 'r10' (4 bytes) from hardware: 0x00000B28
Read register 'r11' (4 bytes) from hardware: 0x00000000
Read register 'r12' (4 bytes) from hardware: 0x00080000
Read register 'sp' (4 bytes) from hardware: 0x00000C28
Read register 'lr' (4 bytes) from hardware: 0xFFFFFFFF
Read register 'pc' (4 bytes) from hardware: 0xD0010810
Read register 'xpsr' (4 bytes) from hardware: 0x00000001
Received monitor command: speed auto
Select auto target interface speed (1875 kHz)
Received monitor command: flash breakpoints 0
Flash breakpoints disabled
Downloading 8576 bytes @ address 0x10000000 - Verified OK
Downloading 11156 bytes @ address 0x10080000 - Verified OK
Read 4 bytes @ address 0x100801D0 (Data = 0xB672B510)
Read 2 bytes @ address 0x100801D0 (Data = 0xB510)
ERROR: Timeout while preparing target, core does not stop. (PC = 0x28001666, XPSR = 0x21000000, SP = 0x28004AE0)!
Failed to perform RAMCode-sided Prepare()
WARNING: Failed to read memory @ address 0xFFFFFFFE
WARNING: Failed to read memory @ address 0xFFFFFFFE
Received monitor command: clrbp
Received monitor command: reset 2
Resets core & peripherals using RESET pin.
Received monitor command: halt
Halting target CPU...
...Target halted (PC = 0x100801D0)
Received monitor command: reset 0
Resets core & peripherals via SYSRESETREQ & VECTRESET bit.
Received monitor command: go
Starting target CPU...
GDB closed TCP/IP connection (Socket 944)

Best Regards

0 Likes
Pradeep_PN
Moderator
Moderator
Moderator
250 sign-ins 100 solutions authored 25 likes received

Hi @SunshineQAQ ,

Apologies for the delayed response.

Are you using a custom board or Evaluation Kit from Infineon ?

If you are using a custom board then what is the part number of the controller you are using.

I see that you have selected the APP_KIT_XMC71_EVK_LITE_V2 are you using this board ?

Best Regards
Pradeep.

0 Likes

Hi,

    I use XMC7100D-F100K4160 this chip custom version, I want to know why the use of jlink burning will appear the following error statement?

ERROR: Timeout while preparing target, core does not stop. (PC = 0x28001666, XPSR = 0x21000000, SP = 0x28004AE0)!
Failed to perform RAMCode-sided Prepare()

Best Regards

0 Likes