Hi,
I realise that some of you guys are working on limited budgets, however,
"professional tools" can save time and do offer a return on investment. Ashling
supply *all* the components of the Windows based development environment from
the ÙSB based JTAG probe, the IDE, the Compiler (GNU), the
Source-level Debugger and the Evaluation boards. We ensure all of these
seamlessly work together. In addition, we have our own LPC2xxx Development
Tools Engineers in-house to support our customers when things go wrong.
For
GNU heads, our debugger offers full source-level 'C' and 'Assembler' debug
support, full ARM/THUMB/Interworked debug support, full semihosting support
(printf to a debugger window, fread from your PCs hard-disk),
RealMonitor support (rd/wr memory on-the-fly) and seamless flash
programming/debug support.
Contact me for further details.
-----Original Message-----
From: Robert Adsett [mailto:subscriptions@...]
Sent: 04 February 2004 14:51
To: lpc2100@...m
Subject: Re: [lpc2100] JTAG Connect Problems
From: Robert Adsett [mailto:subscriptions@...]
Sent: 04 February 2004 14:51
To: lpc2100@...m
Subject: Re: [lpc2100] JTAG Connect Problems
At 01:13 PM 2/4/04 +0000, you wrote:
>----- Original Message -----
>From: "Bill Knight"
>To: >Sent: Wednesday, February 04, 2004 12:56 PM
>Subject: [lpc2100] JTAG Connect Problems
>
>
> > I've been ignoring this problem for too long. It's time to
> > determine if everyone has experienced it or if it is something I'm
> > doing.
> > I'm using gcc, gdb/Insight, and Macraigor's Wiggler & OcdLibRemote
> > to build and debug programs running from RAM on a Nohau LPC210x TESTER
> > Board. A majority of times when I try to connect to the LPC via
> > OcdLibRemote from gdb/Insight, OcdLibRemote reports "Cable
> > Disconnected" and gdb/ Insight does not connect. Additional attempts
> > to connect to the same OcdLibRemote session fail within gdb/Insight
> > even though OcdLibRemote reports success. The whole thing will
> > eventually connect after multiple attempts of exiting both
> > OcdLibRemote & gdb/Insight, and various pressings of the RESET button
> > on the Nohau board.
This is the same problem I had. Check the parallel port mode. It should
be EPP. The wiggler doesn't like the other high speed modes.
> > Another issue I remember while writing this is that once connected
> > and debugging with Insight, it is possible to step through and debug C
> >; source code but not possible to view the underlying assembly code.
I had more or less the reverse problem. I can't get it to step through C
code. I keep getting complaints about not being able to write
breakpoints. I can single step through assembly just fine though. Mind
you, I'm doing that in a GDB monitor window, not in Insight.
What are the options you are using on OcdLibRemote? I'd like to step
through C rather than wade through all the underlying assembly.
Robert
" 'Freedom' has no meaning of itself. There are always restrictions,
be they legal, genetic, or physical. If you don't believe me, try to
chew a radio signal. "
; Kelvin Throop, III
Yahoo! Groups Links
- To visit your group on the web, go to:
http://groups.yahoo.com/group/lpc2100/
- To unsubscribe from this group, send an email to:
lpc2100-unsubscribe@yahoogroups.com
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.