On Wed, Oct 15, 2008 at 1:16 AM, Duane Ellis <[EMAIL PROTECTED]> wrote: > Attention Beagle Guys,
Hello Duane. I am sure there must be exceptions to your rules but I guess that having this 3rd state will make it very easy to implement what we need right now Why are those assumptions important? Why is is hard to "insert" an element in the chain? greetings > > Can we get confirmation about how the JRC works in OMAP? > > Is the following assertion true? > > When a TAP is enabled, it is always enabled at a FIXED position within > the chain? > > To describe it another way - Assume there are 3 taps. > > (1) ICE Pick - the JRC > (2) An ARM CPU Tap > (3) A DSP CPU Tap > > The ARM CPU - if it is enabled is ALWAYS after the JRC and ALWAYS before > the DSP (if it is enabled). > > The JRC can *NEVER* swap the order of any two taps. > > It sure seems like this is true. > > Today - OpenOCD - and most other JTAG programs assume the following: > > 1) The tap is IN BYPASS (and has length 1) > or > 2) The tap is *NOT* in BYPASS (and has length N) > > It seems, all we must do is introduce a 3rd state. > > 3) The tap is Disabled and has Length 0. > > -Duane. > > > _______________________________________________ > Openocd-development mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/openocd-development > _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
