Øyvind Harboe wrote:
I can't answer that question, but I would like to see a model
where each core is a GDB thread. Currently OpenOCD has
"support" for multiple cores by launching two GDB servers,
but it would suck to have two IDE's running just because you
have two cores.
multiple cores GDB debug sessions on the same JTAG Chain ?
I'm not sure what you are asking, could you rephrase?
It would be nice to have a single GDB sessino controlling all
cores of one part. The abstraction mechanism could be GDB
threads. One thread per core.
You said <<OpenOCD has"support" for multiple cores by launching two GDB
servers>>
Do you means
IDE #1 - GDB #1 |
+ OpenOCD - JTAG -> TAP CORE #2 - TAP CORE #1 -
IDE #2 - GDB #2 | |---------------<------------|
Does the actual OpenOCD can support multiple GDB sessions wrapping the
same JTAG chain ?
That's what you are saying not ?
Regards,
Laurent
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
