 |
| Author |
Message |
|
|
Posted: Oct 10, 2011 - 09:36 AM |
|

Joined: Sep 28, 2007
Posts: 3
|
|
Is it possible to start a debug session, using Jtag MkII on a running device (previously programmed via normal debugging session) without reset it ? I need it because I give an alpha version of device to some selected final end users but they are not, unfortunately, able or in possibility of starting firmware from AVR32 studio all times: they need to use the device as soon it is powered up but sometimes it useful to me, in case of bugs, break the firmware and analyze in deepth the internal data strucure and flow execution. I didn't found any working way to do it: even if I tell to debugger to not erase and reflash the device it seems impossible to break executing the code, it seems that debugger can only reset the device or start from a given address. I can write a stub in my application to handle the standard gdb serial comunication protocol but gdb plus gdbproxy appear to not support a direct serial link; patching gdb tools is unfortunately an unacceptable delay at this stage of project.
Have you some solution to propose me ? If it could help I can accept a compromise, renouncing to execution break step by step: having a snapshot of internal data strucure can be acceptable; is it possible to fed AVR32 Studio with a memory dump to watch variables ?
A serial remote debug
Thank you in advance,
Simone Navari |
|
|
| |
|
|
|
|
|
|
|