XSpy on XM4500 Hexagon Application kit and J-LINK LITE

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

cross mob
Not applicable
Hello,

We are trying to implement XSpy on the XM4500 Hexagon with J-Link LITE. We are using the manual : http://www.infineon.com/dgdl/xSPY_Getting_Started_v1.pdf?folderId=db3a3043134dde6001134ef5f8ff0281&f...


On the page 6 there is XMC4400 and serial port asigment. We have X203 connector for USB, and no J-link CDC UART port, we installed the segger drivers at http://www.segger.com/jlink‐software.html*.

What we are doing wrong?

Using Windows 7 64bit.

App is included and configured, but states the error at main at the line in main

../EasyMain.c:36:1: error: unknown type name 'DBG002_VariableDescriptionType

Which include is missing to get the definition of the app.

Dave V.3.1.6
Installer build : 2013-02-25

Best regards, Evgen
0 Likes
4 Replies
Not applicable
Hi Evgen,

DBG002 is using UART communication interface to the PC host. As for XMC4500 Hexagon board, there is no UART channel available in debug connector. Perhaps you need to make your own connection?!

Best regards,
Zain
0 Likes
Not applicable
Hi Zain,

Thank you for your reply. XMC4500 has USB connection X203 USB OTG. In the xSPY Getting started manual is described pin selection for XMC4500 Hexagon Kit.
What do you mean by making own connection?
Is xSPY system not supported for XMC4500 on PC side?

Best regards, Evgen
0 Likes
Not applicable
Hi Evgen,

As I mentioned before, the communication protocol is UART for xSPY. XMC4400 Hexagon kit has the "On-board Debugger" which acts as USB/serial converter. However, there is no "On-board Debugger" on XMC4500 Hexagon kit. So that you need to connect P1.4 & P1.5 to the PC via RS232 or USB with FTDI driver.

Best regards,
Zain
0 Likes
Not applicable
Hi Both,

Unfortunately we do not have an official, nice plug&play-solution for xSPY with the existing XMC4500 Hexagon kit (CPU_45A-V2). There will be a new design (CPU_45A-V3) with OBD (on-board debugger) which should be available in about 4 weeks time.

Best regards,
Sophia
0 Likes