Hi all, I want to debug my SoCKit with OpenOCD. Do you achieved any progress with the USB Blaster II? If I try to connect with GDB, I get the following error log: Error: JTAG-DP OVERRUN - check clock, memaccess, or reduce jtag speed Error: MEM_AP_CSW 0x2800060, MEM_AP_TAR 0x0 Info : accepting 'gdb' connection from 3333 Error: Target not examined yet in procedure 'halt' Error: Register map is not available yet, the target is not fully initialised
Is the error related to the USB Blaster II driver/JTAG speed? Could someone outline what someone needs to do to get it work properly? I maybe give it a try. Thanks! > Hi Frank, sorry I didn't see this go by in November. Testing was very > > limited, I was basically introducing what I knew at the time for further > development by the community. But I'm sure you know that by now. I'm just > now getting back to altera SoC work, and decided to try out your usb > blaster II support. Looks like good progress, but I am getting JTAG-DP > overrun errors. > Have you been able to do a debugging session with this driver yet? Maybe > you have a few pointers on how to get started. > Regards, > Brad > > > > > On Tue, Nov 5, 2013 at 2:10 PM, Franck Jullien <franck.jullien@...>wrote: > > 2013/11/5 Franck Jullien <franck.jullien@...>: > > > 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. > > ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
