After looking at what was going on I found a few things I didn't know:

1) When openocd starts, it releases the reset lines... probably a good idea, 
but I mistook this for attempting an actual initial reset (which isn't really 
what you would want if you just startup openocd now that I think about it.  You 
might not want to reset your target right away)...

2) It only appeared that the width value wasn't being used because of 1.  
Issuing a jtag arp_init-reset produces the correct results.

3) If you use push_pull for your reset type, the value associated with data is 
what gets used.  when open_drain is used, the OE value is used.  Good to know, 
and now that the picture becomes clearer, makes sense.  In my case, I really 
don't have an OE, but using the same value for both will let me use either 
open_drain or push_pull in my config files, even though it won't change 
anything.

4) The length of time that ntrst stays low is the jtag_ntrst_width + 
adapter_nsrst_width, mainly because the ntrst is issued first, then the nsrst 
is issued.  Good to know.

At any rate, I see what I need to do to get things working most likely.  A 
scope and debug output really clear things up.

Jens, no, as a matter of fact, I was looking into why my jtag dongle wasn't 
seeing the beagle board correctly.  I suspected that an incorrectly pulled 
NTRST was screwing me up.  It appears that I still get the same bogus IDCODE 
however.  I expected to see the TI icepick, but instead I'm getting 0xfe3ff81f, 
which MIGHT be a correct value, but I suspect it's bogus.


------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most 
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to