So I have the C revision of the board, which was released in June of this year. I confirmed TRST being pulled up, with no external control. The revision notes mention SWO support being added, which uses TDO and TMS. I've tried pulling the SWO_EN pin low, but that doesn't do anything, and it seems to operate fine for the windows flash utility.
I'm also not able to see any activity other than the RST pin on a scope when running it. Any thoughts? On Thu, Dec 17, 2009 at 1:01 PM, Charles Vaughn <cvau...@gmail.com> wrote: > Oh fun. I'll take a look. That hadn't occurred to me, but that would make > the most sense. > > > On Thu, Dec 17, 2009 at 12:42 PM, David Brownell <davi...@pacbell.net>wrote: > >> On Thursday 17 December 2009, Charles Vaughn wrote: >> > Error: 409 14198 core.c:905 jtag_examine_chain_check(): JTAG scan chain >> > interrogation failed: all ones >> >> I vaguely recall that some of the early Stellaris boards >> (like that one!) actually wired up TRST ... other chips >> don't seem to expose that signal, so it's not wired out >> of the JTAG adapters' CPLDs either. >> >> The "all ones" could indicate that the TAP is still being >> held in reset ... perhaps via TRST. I suggest you check >> your reset_config lines against board schematics, and >> maybe the code for that specific adapter. >> >> There are a bunch of Stellaris eval boards, with minor >> differences in JTAG wiring. I'm not sure which config >> is right for that board. I use "interface/luminary.cfg" >> on a different board and it's fine, so I'd expect once >> you sort out this config issue you'll have no problems. >> >> - Dave >> >> p.s. I also add "reset_config srst_nogate" to my >> board's default "reset_config srst_only", but I >> don't recall that anything would care about that. >> > >
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
