Hi,

On Thu, Apr 17, 2014 at 04:30:38PM +1000, Greg Ungerer wrote:
> Attached is "-d 3" logs for a successful run using openocd 0.7.0,
> and a fail with openocd 0.8.0 rc1.

Those are very interesting.

First thing to note is that you're using old deprecated ft2232 driver
with 0.7.0 and the new ftdi driver with 0.8.0. There might be some
subtle difference in how they work, I guess it might make sense to try
ft2232 on 0.8.0 too and compare the results.

Second important thing is where the problems start, on a good run:

Debug: 231 668 arm_adi_v5.c:1227 dap_find_ap(): Found APB-AP at AP index: 1 
(IDR=0x24770002)
Debug: 232 670 arm_adi_v5.c:1227 dap_find_ap(): Found AHB-AP at AP index: 0 
(IDR=0x44770001)
Debug: 233 685 cortex_a.c:2466 cortex_a8_examine_first(): cpuid = 0x561f5811
Debug: 234 685 cortex_a.c:2467 cortex_a8_examine_first(): ctypr = 0x8003c003
Debug: 235 685 cortex_a.c:2468 cortex_a8_examine_first(): ttypr = 0x00000000
Debug: 236 685 cortex_a.c:2469 cortex_a8_examine_first(): didr = 0x15140011
Info : 237 685 arm_dpm.c:986 arm_dpm_setup(): armada370.cpu: hardware has 6 
breakpoints, 2 watchpoints
Debug: 238 685 cortex_a.c:707 cortex_a8_bpwp_disable(): A8: bpwp disable, cr 
c2301140
Debug: 239 687 cortex_a.c:707 cortex_a8_bpwp_disable(): A8: bpwp disable, cr 
c2301144
Debug: 240 689 cortex_a.c:707 cortex_a8_bpwp_disable(): A8: bpwp disable, cr 
c2301148
Debug: 241 691 cortex_a.c:707 cortex_a8_bpwp_disable(): A8: bpwp disable, cr 
c230114c
Debug: 242 693 cortex_a.c:707 cortex_a8_bpwp_disable(): A8: bpwp disable, cr 
c2301150
Debug: 243 696 cortex_a.c:707 cortex_a8_bpwp_disable(): A8: bpwp disable, cr 
c2301154
Debug: 244 698 cortex_a.c:707 cortex_a8_bpwp_disable(): A8: bpwp disable, cr 
c23011c0
Debug: 245 700 cortex_a.c:707 cortex_a8_bpwp_disable(): A8: bpwp disable, cr 
c23011c4
Debug: 246 702 cortex_a.c:2493 cortex_a8_examine_first(): Configured 6 hw 
breakpoints

And on a bad:

Debug: 250 433 arm_adi_v5.c:868 ahbap_debugport_init(): MEM_AP Packed 
Transfers: enabled
Debug: 251 435 arm_adi_v5.c:930 dap_find_ap(): Found APB-AP at AP index: 1 
(IDR=0x24770002)
Debug: 252 436 arm_adi_v5.c:930 dap_find_ap(): Found AHB-AP at AP index: 0 
(IDR=0x44770001)
Debug: 253 444 cortex_a.c:2439 cortex_a8_examine_first(): cpuid = 0x561f5811
Debug: 254 444 cortex_a.c:2440 cortex_a8_examine_first(): ctypr = 0x8003c003
Debug: 255 444 cortex_a.c:2441 cortex_a8_examine_first(): ttypr = 0x00000000
Debug: 256 444 cortex_a.c:2442 cortex_a8_examine_first(): didr = 0x15140011
Info : 257 444 arm_dpm.c:986 arm_dpm_setup(): armada370.cpu: hardware has 6 
breakpoints, 2 watchpoints
Debug: 258 444 cortex_a.c:702 cortex_a8_bpwp_disable(): A8: bpwp disable, cr 
c2301140
Debug: 259 445 adi_v5_jtag.c:271 jtagdp_transaction_endcheck(): jtag-dp: 
CTRL/STAT error, 0xf0000021
Debug: 260 445 adi_v5_jtag.c:291 jtagdp_transaction_endcheck(): MEM-AP Cached 
values: ap_bank 0x10, ap_csw 0xa2000002, ap_tar 0xc2301140
Error: 261 445 adi_v5_jtag.c:298 jtagdp_transaction_endcheck(): JTAG-DP STICKY 
ERROR
Debug: 262 446 adi_v5_jtag.c:315 jtagdp_transaction_endcheck(): jtag-dp: 
CTRL/STAT 0xf0000001
Error: 263 447 adi_v5_jtag.c:331 jtagdp_transaction_endcheck(): MEM_AP_CSW 
0x80000042, MEM_AP_TAR 0xc2301140
... (STICKY ERROR for every transfer)
Debug: 306 468 cortex_a.c:2466 cortex_a8_examine_first(): Configured 6 hw 
breakpoints

It's not related to packed transfers, and I have can hardly imagine
what might be the real reason here, probably ft2232 vs ftdi difference
e.g. the new driver doing something legal but triggering an Armada
quirk or something like that. Further investigation is needed.

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:[email protected]

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to