2013/11/5 Franck Jullien <[email protected]>: > Ok, it works with the old USB-Blaster. > >> Debug: 227 210 arm_adi_v5.c:665 dap_syssec_kinetis_mdmap(): id doesn't >> match 24770002 != 0x001C0000 > > I was worried about this but it seems normal. > >> Debug: 228 257 adi_v5_jtag.c:271 jtagdp_transaction_endcheck(): jtag-dp: >> CTRL/STAT error, 0xf0000003 >> Debug: 229 257 adi_v5_jtag.c:291 jtagdp_transaction_endcheck(): MEM-AP >> Cached values: ap_bank 0x0, ap_csw 0xa2000020, ap_tar 0x0 >> Error: 230 257 adi_v5_jtag.c:295 jtagdp_transaction_endcheck(): JTAG-DP >> OVERRUN - check clock, memaccess, or reduce jtag speed >> Debug: 231 278 adi_v5_jtag.c:315 jtagdp_transaction_endcheck(): jtag-dp: >> CTRL/STAT 0xf0000001 >> Error: 232 324 adi_v5_jtag.c:331 jtagdp_transaction_endcheck(): MEM_AP_CSW >> 0x2800060, MEM_AP_TAR 0x0 >> Debug: 233 324 openocd.c:147 handle_init_command(): target examination failed > > This is my problem. The USB-Blaster II JTAG clock is much higher than > the old one (25MHz vs 6MHz). > I'll try to slow it down (it's not that easy bec
Oups... ...because of the USB Blaster protocol. I'll keep you informed. Franck. ------------------------------------------------------------------------------ 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
