Hi,

I am new in this group and starting with NXP ARM controllers. My
choice is LPC2366 for use in an embedded vision system for a mobile
robot. The system will be using an Omnivision OV7720 CMOS image sensor.

I plan to use the free GNU tool chain (Yagarto). I intend to rebuild
Joern Kaipf's OOCDlink-s version 04 as an USB - JTAG Interface.
Besides the JTAG interface pins also an additional USB_to_UART (RS232
with TTL level) is available with OOCDlink. see:
http://www.joernonline.de/ -> select projects -> select oocdlink ->
select 2_oocdlinks

Now my (maybe stupid) questions:

- The LPC2366 has an embedded trace module called ETM with associated
trace port (pins P2.0 to P2.9), which works together with the JTAG
interface. Is it possible to use this ETM module and its trace port
(pins P2.0 to P2.9) via the UART interface of OOCDLinks? Is this also
supported by OpenOCD? Or is this only available with costly tool
chains?

- Is EmbeddedICE supported by OpenOCD?

Thx, Dirk.

Start a New Thread

--- In l..., "Dirk Uffmann" wrote:
>
> Hi,
>
> I am new in this group and starting with NXP ARM controllers. My
> choice is LPC2366 for use in an embedded vision system for a mobile
> robot. The system will be using an Omnivision OV7720 CMOS image sensor.
>
> I plan to use the free GNU tool chain (Yagarto). I intend to rebuild
> Joern Kaipf's OOCDlink-s version 04 as an USB - JTAG Interface.
> Besides the JTAG interface pins also an additional USB_to_UART (RS232
> with TTL level) is available with OOCDlink. see:
> http://www.joernonline.de/ -> select projects -> select oocdlink ->
> select 2_oocdlinks
>
> Now my (maybe stupid) questions:
>
> - The LPC2366 has an embedded trace module called ETM with associated
> trace port (pins P2.0 to P2.9), which works together with the JTAG
> interface. Is it possible to use this ETM module and its trace port
> (pins P2.0 to P2.9) via the UART interface of OOCDLinks? Is this also
> supported by OpenOCD? Or is this only available with costly tool
> chains?
>
> - Is EmbeddedICE supported by OpenOCD?
>
> Thx, Dirk.
>
Hi Dirk,

EmbeddedICE is a fancy name for for the JTAG interface with the debug
functions that the ARM implementation provides. By definition of the
EI you are using it when debugging with OpenOCD.

Very different with the ETM. In the end it is all about giving up some
pins in the application, some additional pins to communicate from the
debugging hardware (not included in OpenOCD) and last but definitely
not least several MBs of software, controlling the ETM, extracting the
necessary data, synchronizing your source file with the viewer etc...
There are two reasons why implementations with ETM are only offered by
the more expensive (experienced) companies.
1. You can ask a higher price
2. It needs much more manpower to implement the required software into
a debugger

The lowest cost ETM implmentation I know is using Segger's J-Trace and
the software it works with are from IAR "C-Spy" and probably by now
also from Keil "uVision".

hth, Robert
Start a New Thread

--- In l..., "lpc2100_fan"
wrote:
>
> --- In l..., "Dirk Uffmann"
wrote:
> >
> > Hi,
> >
> > I am new in this group and starting with NXP ARM controllers. My
> > choice is LPC2366 for use in an embedded vision system for a
mobile
> > robot. The system will be using an Omnivision OV7720 CMOS image
sensor.
> >
> > I plan to use the free GNU tool chain (Yagarto). I intend to
rebuild
> > Joern Kaipf's OOCDlink-s version 04 as an USB - JTAG Interface.
> > Besides the JTAG interface pins also an additional USB_to_UART
(RS232
> > with TTL level) is available with OOCDlink. see:
> > http://www.joernonline.de/ -> select projects -> select
oocdlink ->
> > select 2_oocdlinks
> >
> > Now my (maybe stupid) questions:
> >
> > - The LPC2366 has an embedded trace module called ETM with
associated
> > trace port (pins P2.0 to P2.9), which works together with the
JTAG
> > interface. Is it possible to use this ETM module and its trace
port
> > (pins P2.0 to P2.9) via the UART interface of OOCDLinks? Is this
also
> > supported by OpenOCD? Or is this only available with costly tool
> > chains?
> >
> > - Is EmbeddedICE supported by OpenOCD?
> >
> > Thx, Dirk.
> >
> Hi Dirk,
>
> EmbeddedICE is a fancy name for for the JTAG interface with the
debug
> functions that the ARM implementation provides. By definition of
the
> EI you are using it when debugging with OpenOCD.
>
> Very different with the ETM. In the end it is all about giving up
some
> pins in the application, some additional pins to communicate from
the
> debugging hardware (not included in OpenOCD) and last but
definitely
> not least several MBs of software, controlling the ETM, extracting
the
> necessary data, synchronizing your source file with the viewer
etc...
> There are two reasons why implementations with ETM are only
offered by
> the more expensive (experienced) companies.
> 1. You can ask a higher price
> 2. It needs much more manpower to implement the required software
into
> a debugger
>
> The lowest cost ETM implmentation I know is using Segger's J-Trace
and
> the software it works with are from IAR "C-Spy" and probably by now
> also from Keil "uVision".
>
> hth, Robert
>
Thanks a lot, Robert, for your help.
I will skip trying to use ETM and make use of the associated pins
for another purpose.

Do you have experience with the GNU ARM tool chain and OpenOCD via
JTAG interface? Does it work fine for you? What tool chain and
hardware for downloading code and debugging are you using?

Dirk.
Start a New Thread