>> And yes, every target should get its own gdb port and gdb context, and that >> is already implemented.
yea, it seems to support this. It’s just a giant super loop. >> if that target smp line is commented out. I think current ‘target amp’ is wrong headed, in that it marks every target as member of the SMP list. Think of: smp( ARM + ARM) + DSP Or - perhaps two amp groups, smp_group_A( ARM + ARM ), and amp_group_B( ARM + ARM ) -Duane. ==== Another aspect can occur if one of the CPUs goes “off-line” (i.e.: powers down) On Mar 28, 2014, at 3:16 AM, Paul Fertser <[email protected]> wrote: > Hi, > > Please see my follow-up comments inline; it would be interesting to > hear your opinion regarding this topic. > > On Mon, Mar 24, 2014 at 10:15:58AM +0400, Paul Fertser wrote: >>> The example would be to debug an M3 and an A7 at the same time via the same >>> DAP, on an SOC. >>> With two instances of GDB - one for the M3, and one for the A7 >>> Perhaps on two different GDB port numbers. >> >> Absolutely not possible, the framework doesn't account for such odd >> cases at all currently. You can switch between debugging different >> cores runtime, I think. > > I'm not so sure of this anymore, probably different targets can > actually coexist just fine sharing DAP access. And yes, every target > should get its own gdb port and gdb context, and that is already > implemented. > >>> Another example would be to debug two A7s, in SMP mode. >>> Again - with two different instances of GDB >> >> See "target smp" commands and other mentions of "smp" in the >> manual. Should be possible, but not the way you describe it, >> unfortunately. > > Default configs for SMP targets use “target smp" to group cores > together for using a single gdb instance. Reading the manual gives an > impression that it's the preferred (and most comfortable) method of > working with SMP. But I think your method with multiple independent > gdb ports can currently work too, if that target smp line is commented > out. > > -- > Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! > mAnd yes, every target > should get its own gdb port and gdb context, and that is already > implemented.ailto:[email protected] > ------------------------------------------------------------------------------ _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
