Another issue with downloading/debugging:
What I want to do in a makefile is something like that:
debug: out.hex
jtag.py -e out.hex
msp430-insight out.elf
This leads to a one-button make-download-debug cycle.
The jtag.py part works quite well (besides my problem with
multiple downloads). If no connection is possible, jtag.py
isues an error code and make stops without invoking
insight. If download is successful, insight starts. Cute, so
far.
The problem is, i have to invoke gdbproxy in another process,
shortly before or while insight is starting. To my knowlegde,
this can oly be done manually. This is not very comfortable.
Leaving gdbproxy open in the background is no option, because
there is some interference with jtag.py. The script works well
without giving a damn about gdbproxy, but afterwards insight
cannot connect to the proxy anymore.
Two possible solutions:
- starting gdbproxy in a seperate thread/process right before
insight, and preferably shut it down after debug session. How
can this be automated?
or
- finding a way to eliminate the disruption of gdbproxy by jtag.py
or
- increase the download speed within insight (!) and eliminate the
need of jtag.py (at least in the devolpment cycle)
Regards,
Ralf
