Configuring KDS debug connection for Debugging code in RAM

[mjbcswitzerland]

Hi

I am wondering whether there is a guide to configuring a debug connection for code in SRAM?
The K64 has 256k of SRAM and so even quite large code can be run and debugged in it. I used an SRAM debug target in CW10.x for cases where the code was not too large to fit in say the 128k of a K60.

In the KDS debug configuration there are not many options and although I have an SRAM build target I couldn't find way of configuring the debugger to run it.

Any ideas?

Regards

Mark

[BlackNight]

Hi Mark,

The debugger should simply debug a RAM target like a FLASH target (the GDB server should know where is RAM and where is FLASH)

With Processor Expert I use the RAM (instead of FLASH configuration). This maps my code to the RAM space. What did not work for me (I'm using the Segger J-Link) is the source file mapping (Eclipse does not find the source file). Not sure what is causing this, any ideas?

Erich