Hi,

  I'm getting STICKY ERROR's when I startup, just wondered if this is
normal or not?

  My setup:

1. Beagleboard Rev B4
2. Flyswatter (new May 2010) with EMUL0, EMUL1 not pulled down,
   SRST not connected.
3. Debian

  When I do:
sudo openocd -s /home/rick/in/openocd/tcl -f interface/flyswatter.cfg -f 
board/ti_beagleboard.cfg -d3 -lin/openocd.log.txt

  I get:

---snip----
Debug: 253 122 openocd.c:133 handle_init_command(): Examining targets...
Debug: 254 122 cortex_a8.c:1518 cortex_a8_examine_first(): TODO - autoconfigure
Debug: 255 122 arm_adi_v5.c:887 ahbap_debugport_init():  
Debug: 256 132 arm_adi_v5.c:972 ahbap_debugport_init(): MEM-AP #0 ID Register 
0x807f05d, Debug ROM Address 0xbf8901c8
Debug: 257 173 cortex_a8.c:1556 cortex_a8_examine_first(): cpuid = 0x411fc082
Debug: 258 173 cortex_a8.c:1557 cortex_a8_examine_first(): ctypr = 0x80048004
Debug: 259 173 cortex_a8.c:1558 cortex_a8_examine_first(): ttypr = 0x00202001
Debug: 260 173 cortex_a8.c:1559 cortex_a8_examine_first(): didr = 0x15141012
Info : 261 173 arm_dpm.c:963 arm_dpm_setup(): omap3530.cpu: hardware has 6 
breakpoints, 2 watchpoints
Debug: 262 173 cortex_a8.c:530 cortex_a8_bpwp_disable(): A8: bpwp disable, cr 
54011140
Debug: 263 183 adi_v5_jtag.c:259 jtagdp_transaction_endcheck(): jtag-dp: 
CTRL/STAT error, 0xf0000021
Debug: 264 183 adi_v5_jtag.c:278 jtagdp_transaction_endcheck(): MEM-AP Cached 
values: ap_bank 0x10, ap_csw 0xa2000002, ap_tar 0x54011140
Error: 265 183 adi_v5_jtag.c:285 jtagdp_transaction_endcheck(): JTAG-DP STICKY 
ERROR
Debug: 266 190 adi_v5_jtag.c:297 jtagdp_transaction_endcheck(): jtag-dp: 
CTRL/STAT 0xf0000001
---snip----

  For the full log, see http://www.efn.org/~rick/pub/openocd.log.txt

  Also, I seem to have to do the following upon connection:

omap3_dbginit omap3530.cpu

  or not much works...  Is this normal?

  Thanks for any help.

  Rick
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to