On 9/6/11 5:31 PM, Eric Sandeen wrote: > Matt Hsu <matt@...> writes: > >> >> Hi all,I tried to use AM3517evm's config on AM3517 Craneboard. But it seems > that no luck to get openOCD work.sudo openocd -f interface/flyswatter.cfg -f > board/am3517evm.cfgOpen On-Chip Debugger 0.5.0 (2011-08-31-15:54) >> Licensed under GNU GPL v2For bug reports, read > http://openocd.berlios.de/doc/doxygen/bugs.htmlInfo : only one transport > option; > autoselect 'jtag' >> 10 kHztrst_only separate trst_push_pullInfo : clock speed 10 kHzInfo : JTAG > tap: am35x.jrc tap/device found: 0x0b86802f (mfg: 0x017, part: 0xb868, ver: > 0x0)Warn : JTAG tap: am35x.jrc UNEXPECTED: 0x0b86802f (mfg: 0x017, part: > 0xb868, ver: 0x0) >> Error: JTAG tap: am35x.jrc expected 1 of 1: 0x0b7ae02f (mfg: 0x017, part: > 0xb7ae, ver: 0x0)Error: Trying to use configured scan chain anyway...Warn : > Bypassing JTAG setup events due to errors >> I'm curious that anyone try to get openOCD work on craneboard?Thanks,-- - >> Matt > > I have an embedded board which behaves similarly... also, Øyvind started out > about the same way with an AM3517 board, see for example > > http://lists.berlios.de/pipermail/openocd-development/2010-June/015867.html > >> Info : JTAG tap: am3517.jrc tap/device found: 0x0b86802f (mfg: 0x017, part: > 0xb868, ver: 0x0) > > But that ID doesn't exist in the cfg files later checked into openocd. I'm > not > quite sure how he got from point A to point B ... :)
(BTW sorry for the horrendous formatting of the original fwd'd message, not sure how that happened) I did get a config working with my board, with that tapid. It seems that something got lost in commit 60501bb0fb0cb69f66ebb3ce3b64b69f3cadf4ff AM/DM37x: Unify configuration scripts and add support for TI Beagleboard xM. # git show 60501bb0fb0cb69f66ebb3ce3b64b69f3cadf4ff | grep 0x0b86802f -set DAP_TAPID 0x0b86802f That tapid was removed, and not moved elsewhere. I'll try to look over that commit and my working config file, and see how this should have gone... -Eric _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
