Sign in
Search lpc2000
Subscribe to lpc2000
lpc2000 by Keywords
2106 | ADC | ARM7 | Atmel | Bootloader | CAN | CrossStudio | CrossWorks | DDS | ECos | Ethernet | ETM | FIFO | FLASH | FPGA | GCC | GDB | GNU | GNUARM | GPIO | I2C | IAP | IAR | JTAG | Kickstart | LCD | Linux | LPC | LPC-E2294 | LPC2000 | LPC2100 | LPC2104 | Lpc2106 | Lpc210x | LPC2114 | LPC2119 | LPC2124 | LPC2129 | Lpc2138 | LPC213x | LPC21xx | LPC2210 | LPC2212 | LPC2214 | LPC2292 | LPC2294 | LPC2xxx | LPC3128 | MCB2100 | Olimex | Philips | PWM | Rowley | RTC | RTOS | SPI | SSP | UART | UART0 | UART1 | ULINK | USB | Watchdog | Wiggler
Ads
Discussion Groups
Discussion Groups | LPC2000 | Re: JTAG programming
Discussion group dedicated to the Philips LPC2000 family of ARM MCUs
JTAG programming - Mike Harrison - Aug 31 8:22:19 2008
Has anyone had any luck getting decent info out of NXP on JTAG programming?
Reason for asking is I have a 4D systems FISP programmer:
http://www.4d-electronics.co.nz/Business/productsbusiness/productsbusiness.htm
which I've been using for programming AVRs in production, The neat thing is it will work completely
standalone, and so is ideal for use by an assembly subcontractor as part of a program/test procedure
- they just plug it in & turn on - minimal scope for errors!
Although they are working on support for the LPC series, they are being severely hampered by poor
documentation and slow responses from NXP's tech dept..
Has anyone here got any useful info, or helpful contacts at NXP that might help?
It would be really nice to have a decent standalone production programming solution for the LPC
parts - as far as I know there isn't curreently any standalone programmer available at sensible
cost.
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
Reason for asking is I have a 4D systems FISP programmer:
http://www.4d-electronics.co.nz/Business/productsbusiness/productsbusiness.htm
which I've been using for programming AVRs in production, The neat thing is it will work completely
standalone, and so is ideal for use by an assembly subcontractor as part of a program/test procedure
- they just plug it in & turn on - minimal scope for errors!
Although they are working on support for the LPC series, they are being severely hampered by poor
documentation and slow responses from NXP's tech dept..
Has anyone here got any useful info, or helpful contacts at NXP that might help?
It would be really nice to have a decent standalone production programming solution for the LPC
parts - as far as I know there isn't curreently any standalone programmer available at sensible
cost.
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
RE: JTAG programming - Paul Curtis - Aug 31 8:39:45 2008
Hi,
> Has anyone had any luck getting decent info out of NXP on JTAG
programming?
>
> Reason for asking is I have a 4D systems FISP programmer:
> http://www.4d-
> electronics.co.nz/Business/productsbusiness/productsbusiness.htm
> which I've been using for programming AVRs in production, The neat thing
is it
> will work completely
> standalone, and so is ideal for use by an assembly subcontractor as part
of a
> program/test procedure
> - they just plug it in & turn on - minimal scope for errors!
>
> Although they are working on support for the LPC series, they are being
> severely hampered by poor
> documentation and slow responses from NXP's tech dept..
> Has anyone here got any useful info, or helpful contacts at NXP that
might
> help?
Everything you need to know on flashing the LPC2000 is included in NXP's
documentation. Everything. I don't think you can lay a crumb at NXP's
door--the documentation is complete and proof of the pudding is that IDE
providers can flash program the parts from their IDEs.
Regards,
--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3 processors
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
> Has anyone had any luck getting decent info out of NXP on JTAG
programming?
>
> Reason for asking is I have a 4D systems FISP programmer:
> http://www.4d-
> electronics.co.nz/Business/productsbusiness/productsbusiness.htm
> which I've been using for programming AVRs in production, The neat thing
is it
> will work completely
> standalone, and so is ideal for use by an assembly subcontractor as part
of a
> program/test procedure
> - they just plug it in & turn on - minimal scope for errors!
>
> Although they are working on support for the LPC series, they are being
> severely hampered by poor
> documentation and slow responses from NXP's tech dept..
> Has anyone here got any useful info, or helpful contacts at NXP that
might
> help?
Everything you need to know on flashing the LPC2000 is included in NXP's
documentation. Everything. I don't think you can lay a crumb at NXP's
door--the documentation is complete and proof of the pudding is that IDE
providers can flash program the parts from their IDEs.
Regards,
--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3 processors
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
Re: JTAG programming - Mike Harrison - Aug 31 9:11:48 2008
>> Although they are working on support for the LPC series, they are being
>> severely hampered by poor
>> documentation and slow responses from NXP's tech dept..
>> Has anyone here got any useful info, or helpful contacts at NXP that
>might
>> help?
>
>Everything you need to know on flashing the LPC2000 is included in NXP's
>documentation. Everything. I don't think you can lay a crumb at NXP's
>door--the documentation is complete and proof of the pudding is that IDE
>providers can flash program the parts from their IDEs.
Althoug the ISP and IAP interfaces are well documented, I don't think the same can honestly be said
for JTAG.
Commercial IDE providers often get 'inside' help direct from manufacturers, especially in the early
stages of a product, so the fact that they provide solutions is not proof that the generally
available docs are adequate as is quite likely that they will have had additional info, typically
under NDA.
I'm only hearing this second-hand so don't know the details of whether the issue is lack of
documentation, incorrect info or silicon bug issues, however I do know from experience that it can
be very hard to find the right docs (and in particuler the most up to date version of a document)
from NXP , even for simple things - e.g. I just did a search for the LPC2136 User Manual at NXP and
only got an obsolete version. Even the product page only has a link to an out of date version
The JTAG programming interface is not documented in any of the UMs or DSs I've read - if you
could cite some specific docs that cover this, that would be useful.
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
>> severely hampered by poor
>> documentation and slow responses from NXP's tech dept..
>> Has anyone here got any useful info, or helpful contacts at NXP that
>might
>> help?
>
>Everything you need to know on flashing the LPC2000 is included in NXP's
>documentation. Everything. I don't think you can lay a crumb at NXP's
>door--the documentation is complete and proof of the pudding is that IDE
>providers can flash program the parts from their IDEs.
Althoug the ISP and IAP interfaces are well documented, I don't think the same can honestly be said
for JTAG.
Commercial IDE providers often get 'inside' help direct from manufacturers, especially in the early
stages of a product, so the fact that they provide solutions is not proof that the generally
available docs are adequate as is quite likely that they will have had additional info, typically
under NDA.
I'm only hearing this second-hand so don't know the details of whether the issue is lack of
documentation, incorrect info or silicon bug issues, however I do know from experience that it can
be very hard to find the right docs (and in particuler the most up to date version of a document)
from NXP , even for simple things - e.g. I just did a search for the LPC2136 User Manual at NXP and
only got an obsolete version. Even the product page only has a link to an out of date version
The JTAG programming interface is not documented in any of the UMs or DSs I've read - if you
could cite some specific docs that cover this, that would be useful.
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
RE: JTAG programming - Paul Curtis - Aug 31 11:06:29 2008
Hi Mike,
> >> Although they are working on support for the LPC series, they are being
> >> severely hampered by poor
> >> documentation and slow responses from NXP's tech dept..
> >> Has anyone here got any useful info, or helpful contacts at NXP that
> >might
> >> help?
> >
> >Everything you need to know on flashing the LPC2000 is included in NXP's
> >documentation. Everything. I don't think you can lay a crumb at NXP's
> >door--the documentation is complete and proof of the pudding is that IDE
> >providers can flash program the parts from their IDEs.
>
> Althoug the ISP and IAP interfaces are well documented, I don't think the
same
> can honestly be said for JTAG.
LPC2k JTAG is bog standard ARM7. NXP don't need to document it, it's fully
documented by ARM.
> Commercial IDE providers often get 'inside' help direct from
manufacturers,
> especially in the early stages of a product, so the fact that they provide
solutions
> is not proof that the generally available docs are adequate as is quite
likely that
> they will have had additional info, typically under NDA.
I can categorically state we have no NDA with ARM and no NDA with NXP and
can successfully flash all LPC devices. All our flashing code was written
just fine without needing to call on any of their technical personnel. It's
all documented. Fully. And it even works. We can even program external
CFI devices on LPC2k.
> I'm only hearing this second-hand so don't know the details of whether the
> issue is lack of
> documentation, incorrect info or silicon bug issues, however I do know
from
> experience that it can
> be very hard to find the right docs (and in particuler the most up to date
> version of a document)
> from NXP , even for simple things - e.g. I just did a search for the
LPC2136
> User Manual at NXP and
> only got an obsolete version. Even the product page only has a link to an
out
> of date version
The docs are not hard to find. IAP is fully documented in the NXP manuals
and has been forever, sine the first silicon arrived.
> The JTAG programming interface is not documented in any of the UMs or
DSs
> I've read - if you could cite some specific docs that cover this, that
would be useful.
There is no ability to program a device over JTAG without the help of the
CPU. You do what everybody does, you write a program that goes on the
device and talks to the host over the DCC or using breakpoints and uses IAP.
Nothing that complex. Our loader fits on the smallest LPC2101, for
instance. In short, a single JTAG connection is all that's needed to flash
the device. It's really quite simple, I don't see why anybody would make
heavy weather of it. There is NO SECRET SAUCE.
--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3 processors
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
> >> Although they are working on support for the LPC series, they are being
> >> severely hampered by poor
> >> documentation and slow responses from NXP's tech dept..
> >> Has anyone here got any useful info, or helpful contacts at NXP that
> >might
> >> help?
> >
> >Everything you need to know on flashing the LPC2000 is included in NXP's
> >documentation. Everything. I don't think you can lay a crumb at NXP's
> >door--the documentation is complete and proof of the pudding is that IDE
> >providers can flash program the parts from their IDEs.
>
> Althoug the ISP and IAP interfaces are well documented, I don't think the
same
> can honestly be said for JTAG.
LPC2k JTAG is bog standard ARM7. NXP don't need to document it, it's fully
documented by ARM.
> Commercial IDE providers often get 'inside' help direct from
manufacturers,
> especially in the early stages of a product, so the fact that they provide
solutions
> is not proof that the generally available docs are adequate as is quite
likely that
> they will have had additional info, typically under NDA.
I can categorically state we have no NDA with ARM and no NDA with NXP and
can successfully flash all LPC devices. All our flashing code was written
just fine without needing to call on any of their technical personnel. It's
all documented. Fully. And it even works. We can even program external
CFI devices on LPC2k.
> I'm only hearing this second-hand so don't know the details of whether the
> issue is lack of
> documentation, incorrect info or silicon bug issues, however I do know
from
> experience that it can
> be very hard to find the right docs (and in particuler the most up to date
> version of a document)
> from NXP , even for simple things - e.g. I just did a search for the
LPC2136
> User Manual at NXP and
> only got an obsolete version. Even the product page only has a link to an
out
> of date version
The docs are not hard to find. IAP is fully documented in the NXP manuals
and has been forever, sine the first silicon arrived.
> The JTAG programming interface is not documented in any of the UMs or
DSs
> I've read - if you could cite some specific docs that cover this, that
would be useful.
There is no ability to program a device over JTAG without the help of the
CPU. You do what everybody does, you write a program that goes on the
device and talks to the host over the DCC or using breakpoints and uses IAP.
Nothing that complex. Our loader fits on the smallest LPC2101, for
instance. In short, a single JTAG connection is all that's needed to flash
the device. It's really quite simple, I don't see why anybody would make
heavy weather of it. There is NO SECRET SAUCE.
--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3 processors
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
Re: JTAG programming - gguichal - Sep 8 13:34:23 2008
--- In l...@yahoogroups.com, "Paul Curtis" wrote:
>
> Hi,
>
> > Has anyone had any luck getting decent info out of NXP on JTAG
> programming?
> >
> > Reason for asking is I have a 4D systems FISP programmer:
> > http://www.4d-
> > electronics.co.nz/Business/productsbusiness/productsbusiness.htm
> > which I've been using for programming AVRs in production, The neat
thing
> is it
> > will work completely
> > standalone, and so is ideal for use by an assembly subcontractor
as part
> of a
> > program/test procedure
> > - they just plug it in & turn on - minimal scope for errors!
> >
> > Although they are working on support for the LPC series, they are
being
> > severely hampered by poor
> > documentation and slow responses from NXP's tech dept..
> > Has anyone here got any useful info, or helpful contacts at NXP that
> might
> > help?
>
> Everything you need to know on flashing the LPC2000 is included in NXP's
> documentation. Everything. I don't think you can lay a crumb at NXP's
> door--the documentation is complete and proof of the pudding is that IDE
> providers can flash program the parts from their IDEs.
I'm sure the information is there. But it does not seem to be simple
for someone without JTAG experience to come up with the programmer
without some additional info.
We've just started using JTAG to configure several chips, and it was
very simple to program AVR and Actel FPGAs from the info found in
their literature and support files.
NXP does not seem to like supporting JTAG access, at least for the
LPC2129 we are trying to program.
Proof of that is:
* The manual only directs you to commercial tools in the JTAG section.
* Support directs you to ISP programming through the serial port, or
to commercial tools, instead of pointing out how simple it is and
where to access the information needed.
I've seen very simple questions asked to support that are answered
directly, even copying info in manuals and datasheets.
Regards, Guillermo Guichal
> Regards,
>
> --
> Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
> CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3 processors
>
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
>
> Hi,
>
> > Has anyone had any luck getting decent info out of NXP on JTAG
> programming?
> >
> > Reason for asking is I have a 4D systems FISP programmer:
> > http://www.4d-
> > electronics.co.nz/Business/productsbusiness/productsbusiness.htm
> > which I've been using for programming AVRs in production, The neat
thing
> is it
> > will work completely
> > standalone, and so is ideal for use by an assembly subcontractor
as part
> of a
> > program/test procedure
> > - they just plug it in & turn on - minimal scope for errors!
> >
> > Although they are working on support for the LPC series, they are
being
> > severely hampered by poor
> > documentation and slow responses from NXP's tech dept..
> > Has anyone here got any useful info, or helpful contacts at NXP that
> might
> > help?
>
> Everything you need to know on flashing the LPC2000 is included in NXP's
> documentation. Everything. I don't think you can lay a crumb at NXP's
> door--the documentation is complete and proof of the pudding is that IDE
> providers can flash program the parts from their IDEs.
I'm sure the information is there. But it does not seem to be simple
for someone without JTAG experience to come up with the programmer
without some additional info.
We've just started using JTAG to configure several chips, and it was
very simple to program AVR and Actel FPGAs from the info found in
their literature and support files.
NXP does not seem to like supporting JTAG access, at least for the
LPC2129 we are trying to program.
Proof of that is:
* The manual only directs you to commercial tools in the JTAG section.
* Support directs you to ISP programming through the serial port, or
to commercial tools, instead of pointing out how simple it is and
where to access the information needed.
I've seen very simple questions asked to support that are answered
directly, even copying info in manuals and datasheets.
Regards, Guillermo Guichal
> Regards,
>
> --
> Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
> CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3 processors
>
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )