On Sun, Aug 12, 2012 at 11:09 AM, Bill Traynor <[email protected]> wrote: > Hi there, > I'm looking into the sticky errors that I get when starting up OpenOCD > with a Flyswatter interface and BeagleBoard-XM. The code comments > indicate that "If the current transaction has not finished by the time > the next one must begin, and the ORUNDETECT bit is set in the > DP_CTRL_STAT register, the SSTICKYORUN status is set and further AP > operations will fail". > > Googling returns numerous instances of this error for various > interfaces and board combinations. Some solutions I've seen are to > increase/decrease the JTAG speed in the target config using the > adapter_khz setting. > > I'm trying to understand these errors better and have the following questions: > > 1. Are these errors spurious, in that they don't seem to effect > debugging after they occur? > 2. If question 1 answer is No, where should I look next? Do I need > to read the applicable specs referenced in the code and debug it's > implementation in OpenOCD? Do I just play with JTAG speeds until I > find what works? > > Here's the setup I'm using to test: > Open On-Chip Debugger 0.6.0-dev-00528-g63e5386 (2012-04-24-16:11) > Board: BeagleBoard-xm (v.A2) (ti_beagleboard_xm.cfg) > Interface: Flyswatter (flyswatter.cfg) > > StartUp results in the following: > > wmat@ayr ~/openocd-bin $ sudo openocd -f interface/flyswatter.cfg -f > board/ti_beagleboard_xm.cfg -c 'init' > Open On-Chip Debugger 0.6.0-dev-00528-g63e5386 (2012-04-24-16:11) > Licensed under GNU GPL v2 > For bug reports, read > http://openocd.sourceforge.net/doc/doxygen/bugs.html > Info : only one transport option; autoselect 'jtag' > 10 kHz > Warn : dm37x.dsp: huge IR length 38 > trst_only separate trst_push_pull > Info : clock speed 10 kHz > Info : JTAG tap: dm37x.jrc tap/device found: 0x0b89102f (mfg: 0x017, > part: 0xb891, ver: 0x0) > Info : JTAG tap: dm37x.dap enabled > Info : dm37x.cpu: hardware has 6 breakpoints, 2 watchpoints > Error: JTAG-DP STICKY ERROR > Error: MEM_AP_CSW 0x80000042, MEM_AP_TAR 0x54011140 > Error: JTAG-DP STICKY ERROR > Error: MEM_AP_CSW 0x80000042, MEM_AP_TAR 0x54011140 > Error: JTAG-DP STICKY ERROR > Error: MEM_AP_CSW 0x80000042, MEM_AP_TAR 0x54011140 > Error: JTAG-DP STICKY ERROR > Error: MEM_AP_CSW 0x80000042, MEM_AP_TAR 0x54011140 > Error: JTAG-DP STICKY ERROR > Error: MEM_AP_CSW 0x80000042, MEM_AP_TAR 0x54011150 > Error: JTAG-DP STICKY ERROR > Error: MEM_AP_CSW 0x80000042, MEM_AP_TAR 0x54011150 > Error: JTAG-DP STICKY ERROR > Error: MEM_AP_CSW 0x80000042, MEM_AP_TAR 0x540111c0 > Error: JTAG-DP STICKY ERROR > Error: MEM_AP_CSW 0x80000042, MEM_AP_TAR 0x540111c0
The first error in the -d3 output is: Debug: 327 706 cortex_a.c:704 cortex_a8_bpwp_disable(): A8: bpwp disable, cr 54011140 Debug: 328 746 adi_v5_jtag.c:268 jtagdp_transaction_endcheck(): jtag-dp: CTRL/STAT error, 0xf0000021 Debug: 329 746 adi_v5_jtag.c:288 jtagdp_transaction_endcheck(): MEM-AP Cached values: ap_bank 0x10, ap_csw 0xa2000002, ap_tar 0x54011140 Error: 330 746 adi_v5_jtag.c:295 jtagdp_transaction_endcheck(): JTAG-DP STICKY ERROR ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
