Jon, this issue has already been reported by Karl in https://lists.berlios.de/pipermail/openocd-development/2010-November/017056.html
the issue is linked with patch in https://lists.berlios.de/pipermail/openocd-development/2010-November/016854.html Best Regards Antonio Borneo On Thu, Nov 25, 2010 at 1:10 PM, Jon Masters <jonat...@jonmasters.org> wrote: > Hello, > > Anyone here have suggestions? > > Thanks! > > Jon. > > > > ---------- Forwarded message ---------- > From: Jon Masters <jonat...@jonmasters.org> > To: beagleboard <beaglebo...@googlegroups.com> > Date: Wed, 24 Nov 2010 23:59:20 -0500 > Subject: [beagleboard] Flyswatter with XM > Hello, > > Has anyone managed to get the TinCanTools Flyswatter working with the > XM? I did with the original Beagle, but upstream OCD does this with XM: > > [...@constitution openocd]$ sudo /usr/local/bin/openocd > -s /usr/local/lib/openocd > -f /usr/local/share/openocd/scripts/interface/flyswatter.cfg > -f /usr/local/share/openocd/scripts/board/ti_beagleboard_xm.cfg > Open On-Chip Debugger 0.5.0-dev-00620-g1892a2b (2010-11-24-13:01) > Licensed under GNU GPL v2 > For bug reports, read > http://openocd.berlios.de/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 > Warn : Found broken CPU (imx51), trying to fixup ROM Table location from > 0x80000000 to 0x60000000 > Error: JTAG-DP STICKY ERROR > Error: MEM_AP_CSW 0x80000042, MEM_AP_TAR 0x60000000 > Polling target failed, GDB will be halted. Polling again in 100ms > Polling target failed, GDB will be halted. Polling again in 300ms > Polling target failed, GDB will be halted. Polling again in 700ms > Polling target failed, GDB will be halted. Polling again in 1500ms > Polling target failed, GDB will be halted. Polling again in 3100ms > Polling target failed, GDB will be halted. Polling again in 6300ms > etc. > > I haven't had chance to look at the code yet, but I think some of the > broken CPU detection/fixup stuff has changed recently. Still, the > warning about the IMX51 is concerning. What ROM table is it referring to > exactly? Is this something on the Flyswatter board? Does anyone happen > to know these things before I go digging? (I used to use BDI2000s but > they're a little expensive for home...not a huge OCD user yet). > > Jon. > > > -- > You received this message because you are subscribed to the Google Groups > "Beagle Board" group. > To post to this group, send email to beaglebo...@googlegroups.com. > To unsubscribe from this group, send email to > beagleboard+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/beagleboard?hl=en. > > > > _______________________________________________ > Openocd-development mailing list > Openocd-development@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/openocd-development > > _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
