RE: Advanced debugging an image

You can use S/W reset + KITL + "Target\Release Directory Modules" to debug
the codes you modified. S/W reset will not cause loading image from PB5, and
KITL + "Target\Release Directory Modules" load the driver you select from
host release directory to the target when system boot up.

"Maarten" wrote:

Dear,

Is it possible to modify code during an active (connected) debug session in
PB5 without reloading the whole image again and again?
--
Maarten
.

Loading