Hi Brandon. On Fri, 8 Nov 2013 17:31:01 -0500, Brandon Warhurst wrote: > I suspected that an incorrectly pulled NTRST was screwing me up. It > appears that I still get the same bogus IDCODE however. I expected > to see the TI icepick, but instead I'm getting 0xfe3ff81f, which > MIGHT be a correct value, but I suspect it's bogus.
I've seen incorrect ID values whenever I had ~RESET wired up incorrectly. (and for that matter, whenever I forgot to turn on target power). Sometimes I checked the connections, re-checked them, re-checked them a third time... I couldn't see anything wrong, everything looked fine. But in fact, my ~RESET /was/ connected incorrectly, which is why I often speak about checking the connections. ...Sometimes checking a different way might be a good idea: disconnect the JTAG, then use a multimeter to check the voltage levels on the JTAG pins to see if the pull-up resistors are connected correctly. (And don't always trust that a board you've bought will be usable. I bought one which can never be flashed, due to incorrect JTAG wiring!) ...But it's good to hear that you're on the right track. Love Jens ------------------------------------------------------------------------------ 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 OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
