On Thursday 04 June 2009, Spencer Oliver wrote: > > The name evb_lm3s811 is probably a little confusing. > Luminary seem to use the same interface for all their dev boards, the > name should probably be something more generic.
As I suspected. But, for the moment, not on my list of things to change ... though IMO that *would* be a good thing to change for 0.2.0 given that checks out. > The luminary eval boards as you say support two modes, three modes on the > newer ones. > 1. connected to the onboard luminary target > 2. connected to a offboard target using the 20way jtag header. > 3. connect an external jtag tool to the onboard target, eg. jlink. > > All the openocd testing (cfg files) has been with the onboard luminary > target (1) and not passthrough. > So the docs are incorrect in my opinion. That's what I thought. I read the docs from Luminary as "switches automagically between (1) and (2)" so I'll update the docs accordingly. Mode (3) seems like a don't-care from the perspective of the ft2232 glule. > Personally i have not tested the passthrough interface, mainly because there > is no trst, srst - so it is > simpler to connect an amontec dongle for example. Right. I suppose it's good sometimes to verify that OpenOCD works properly without SRST and TRST though. (Mode 1 seems to have only SRST though, say schematics.) _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
