On Saturday 06 June 2009, Duane Ellis wrote: > FYI - The original idea was to support multi-core targets with different > names, for example: > > mdw - works on the current target, what ever that is... > $TARGETNAME mdw
You'll notice most of the reset-init event handlers can't use that. I don't know that anything sets up $TARGETNAME appropriately for a multi-CPU chip (or multi-CPU board)... > (B) Hidden in C code... effectively enforced, like above, see target.c > - line 3444..3456 That is, the "-chain-position" logic should change? > ie: If it *ENDS* with *TAP* - it is the *TAP* ... Erm, your (2B) says otherwise, since it appends the ".tap" suffix. If we go with your (1) and force a ".tap" suffix on everything, doing anything other than your (2A) would pretty much negate the whole point, since people (and scripts) wouldn't be using those names that end int ".tap". If one were to take your (1) forcing the ".tap" suffix, then IMO the correct route is to take your (2A) and change all scripts, plus (1a) update the TAP naming convention to tell folk not to use "tap" themselves, and (1b) when creating targets, reject any target name with a ".tap" suffix. This seems to me like it'd be much thrash for not much benefit. - Dave _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
