I am using KileMDK 2.85 with Jlink to connect to LPC55S69 M33 board. I can download the code and debug but if I enable the "Trace" in the Trace Tab, the debug session fails with "Cannot Access Memory" dialog box. I contacted JLink and they responded with
"This is most likely due to an incorrect SWO init.
As that sequence is issued by Keil uVision which is not our product we can't assist you here. We suggest contacting Keil support in this case."
What is the solution?
Naveed said:I am using KileMDK 2.85
That's very old!
Current version is 5.28: http://www2.keil.com/mdk5
my mistake in typing, I am using 5.28.
Naveed said:suggest contacting Keil support in this case
Ok, so open a support case. The forum is more a user-to-user interface.
This is either some scripting issue (settings to DLL, or packs), or one accessing the ROM tables which usually describe the location/availability of assorted debug units instantiated in the core.