On Monday 28 December 2009, Yegor Yefremov wrote:
> On Mon, Dec 28, 2009 at 2:45 AM, David Brownell wrote:
> > On Monday 21 December 2009, Yegor Yefremov wrote:
> >> My board rev: LMWLV-B
> >
> > Could you forward the USB IDs and device string of your
> > board? I notice that tcl/interface/lumina
On Mon, Dec 28, 2009 at 2:45 AM, David Brownell wrote:
> On Monday 21 December 2009, Yegor Yefremov wrote:
>> My board rev: LMWLV-B
>
> Could you forward the USB IDs and device string of your
> board? I notice that tcl/interface/luminary-lm3s811.cfg
> doesn't include the USB IDs, so it's at least
Yegor,
On Monday 21 December 2009, Yegor Yefremov wrote:
> My board rev: LMWLV-B
Could you forward the USB IDs and device string of your
board? I notice that tcl/interface/luminary-lm3s811.cfg
doesn't include the USB IDs, so it's at least partially
broken. Also its device string doesn't match t
On Monday 21 December 2009, Yegor Yefremov wrote:
> On Fri, Dec 18, 2009 at 3:58 PM, Charles Vaughn wrote:
> > What revision is your board? The title is a bit out of sync with the issue,
> > as in June it appears TI multiplexed SWO and JTAG. My board rev is LMWLV-C.
>
> My board rev: LMWLV-B
(
On Fri, Dec 18, 2009 at 3:58 PM, Charles Vaughn wrote:
> What revision is your board? The title is a bit out of sync with the issue,
> as in June it appears TI multiplexed SWO and JTAG. My board rev is LMWLV-C.
My board rev: LMWLV-B
Yegor
___
Openocd
What revision is your board? The title is a bit out of sync with the issue,
as in June it appears TI multiplexed SWO and JTAG. My board rev is LMWLV-C.
On Fri, Dec 18, 2009 at 3:13 AM, Yegor Yefremov
wrote:
> On Thu, Dec 17, 2009 at 7:52 PM, Charles Vaughn wrote:
> > I've recently purchased an
On Thu, Dec 17, 2009 at 7:52 PM, Charles Vaughn wrote:
> I've recently purchased an LM3S811 evaluation board. I've tried to connect
> to it with OpenOCD, but I've met very little success even initiating a
> connection.
>
> When I use the version of OpenOCD available from Ubuntu repositories
> (r2
So I've done a little more scope probing, and I can see a TCK out of the
FT2232, but not on the TCK pin, so that backs that up. I'll take a closer
look at the schematics and try to find out what drives that.
On Thu, Dec 17, 2009 at 10:35 PM, David Brownell wrote:
> On Thursday 17 December 2009,
On Thursday 17 December 2009, Charles Vaughn wrote:
> revision notes mention SWO support being added, which uses TDO and TMS.
Your problem signal is TDO (that's giving "all ones" output), so
this looks like the right track...
Looks to me like the way they added SWO support involved adding
an addi
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
seem
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 wrote:
> On Thursday 17 December 2009, Charles Vaughn wrote:
> > Error: 409 14198 core.c:905 jtag_examine_chain_check(): JTAG scan chain
> > interrogation f
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
12 matches
Mail list logo
