Rick, Thanks for your speedy response! The device under test proper does seem to work well enough with EJTAG to the extent that the USBJTAGNT hack from www.usbjtag.com can talk to its CFI flash, get data from the flash, and reset it, as well as somehow talk to the internal boot ROM on the embedded M4kc core to the point where it can read it. Of course, I want to go further and do a little bit of debugging...
One of the problems is that I don't have a board-level schematic, so I don't know the order of the chips on the scan chain, nor do I have a .bsdl for the embedded cable modem controller chip. It would be nice to figure out how to do discovery of the scan chain order by hand. On Fri, Feb 6, 2009 at 8:15 AM, Rick Altherr <kc8...@kc8apf.net> wrote: > > On Feb 6, 2009, at 1:08 AM, Martin Haeberli wrote: ... >> v[4]=0x1e > > This looks like an old-style jtag_device command. You'll want to convert it > to the new-style jtag newtap command. > Thanks for the suggestion - I'll give that a try today. >> ... >> n big -chain-position 0 > > And then the argument to -chain-position will change. > To what? Candidly, I'd like to figure out a way to explore the available scan chain to see what is there. >> Debug: 76 266 openocd.c:150 handle_init_command(): jtag interface init ... >> Debug: 88 281 openocd.c:156 handle_init_command(): jtag init complete > > Looks like the JTAG hardware failed to communicate at all. Both the examine > and validate failed which means OpenOCD cannot talk to anything on the JTAG > chain. I'm not sure why we bothered to continued after this point. > Something is wrong with either the JTAG chain configuration or the JTAG > hardware. > >> ---- ... >> jtag_device 5 0x1 0x1 0x1e > > Change this to a jtag newtap command. > OK >> > Thanks, de W9MPH - Martin _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
