Dave, > Hmm...I have not tried the Rowley IDE and would prefer not to > have to change my toolchain at this point; we have lots of > code built around the GNU tools under cygwin and linux and > they work very well (except for this :-) They are also free > and open-source which I am very fond of. For ARM, our IDE uses GCC for compilation but does *not* use GDB for debugging. It has integrated flashing, debug from flash, and so on. Hence you would not need to switch toolchain at all. > I've tried all of the software configurable settings for the > OCD software with no luck. We wrote our own Wiggler driver and do not use the driver from Macraigor--although we are supporting their API so you'll be able to use the Raven and mpDemon in a future version. Most users find our driver faster and more reliable. -- Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk CrossWorks for MSP430, ARM, and (soon) Atmel AVR processors

--- In , "dave_albert" <david_albert@h...> wrote: > > I have 9 or 10 Olimex LPC-P2106. They are great boards. They always > had some problems with the Wiggler (needed speed 5 or above), but they > worked. Recently, I've been unable to get any of them to work with a > wiggler. I believe they are all rev B silicon. I have upgraded to > the latest Philips bootloader (although I don't know why this would > matter). I am running a genuine Wiggler with OCD Commander (I've > tried several versions) on a 2.4GHz P4 (Dell Dimension 4550) running > XP. The same setup works fine with my Olimex LPC-P2124 board. > > I don't think reset is the problem because I see the same problem on > my 2106 based prototypes which have a real reset controller on- board. > > any ideas? Strange, I'd have said it was a problem with the Wiggler hardware, but that is unlikely if it works with the '2124 board. I don't have any problems at all with the earlier '2106 chips on my own boards with both a genuine Wiggler and my own interface. The latter actually works better than the real thing, probably because I took some care with the PCB design; I don't think much of the Wiggler PCB layout. Leon

Can you share the details of your configuration? What rev LPC2106, what OS, SW Revisions, bootloader, CPU speed, etc.? --- In , "Leon Heller" <leon_heller@h...> wrote: > ----- Original Message ----- > From: "dave_albert" <david_albert@h...> > To: <> > Sent: Monday, September 27, 2004 3:14 PM > Subject: [lpc2000] JTAG problems with Olimex LPC2106 > > I'm having trouble getting my JTAG Wiggler to work > > with an Olimex LPC-P1 (2106 based prototype board). > > It works fine with my Olimex LPC2124 based prototype > > board, but always gives me a "cable disconnected" or > > "cannot enter debug mode" error. The board resets > > properly when I start OCD Commander or ocdlibremote, > > but then enters full run mode. I have tried this with > > the DEBUG jumper on and off at all possible speed > > settings for the Wiggler. > > > > Is anyone else having this problem? > > Both my genuine Wiggler and my own version of it work fine with the '2106 on > my boards. > > Leon

Hmm...I have not tried the Rowley IDE and would prefer not to have to change my toolchain at this point; we have lots of code built around the GNU tools under cygwin and linux and they work very well (except for this :-) They are also free and open-source which I am very fond of. I've tried all of the software configurable settings for the OCD software with no luck. Back when it *was* working, I was able to debug LPC flash although it was less fun than RAM debugging...you can set 1-2 hardware breakpoints and they do work with OCD/GDB...I can tell you how if you are interested. Regards, Dave BTW, I love your development boards! --- In , "tsvetanusunov" <tusunov@m...> wrote: > --- In , "dave_albert" <david_albert@h...> > wrote: > > I'm having trouble getting my JTAG Wiggler to work > > with an Olimex LPC-P1 (2106 based prototype board). > > It works fine with my Olimex LPC2124 based prototype > > board, but always gives me a "cable disconnected" or > > "cannot enter debug mode" error. The board resets > > properly when I start OCD Commander or ocdlibremote, > > but then enters full run mode. I have tried this with > > the DEBUG jumper on and off at all possible speed > > settings for the Wiggler. > > > > Is anyone else having this problem? > > there should be no reason ARM-JTAG/Wiggler to work on one and not > work on other board, it may be something with your software settings > if there are any. > BTW did you try Rowley's IDE? This is what we use with our ARM-JTAG > exclusively to test/program our development boards and it works just > fine, we never figured out how to use OCD/GNU tools (I'm definitely > not DOS fan) nor what is more important how to make them > program/debug with LPC flash. > > Best regards > Tsvetan > --- > PCB prototypes for $26 at http://run.to/pcb > (http://www.olimex.com/pcb) > PCB any volume assembly (http://www.olimex.com/pcb/protoa.html) > Development boards for ARM, AVR, PIC, and MSP430 > (http://www.olimex.com/dev)

Thanks, but it is not in ECP mode. --- In , "lynchzilla" <lynchzilla@a...> wrote: > Buried in the Macraigor web site's FAQ is the following important > advice: > > "What mode must my parallel port be in? > > As far as the parallel port is concerned, a Wiggler is a simple uni- > directional device. It will work with the parallel port in any mode > EXCEPT "ECP". It will NOT work in ECP mode at all. > > Remember, the mode is set in the CMOS bios of your computer." > > Boot your desktop PC and get it into "setup" mode. On my computer, > you hit the DEL key just as it boots up to do this. Make sure that > the parallel port is NOT in ECP mode (the default for modern PCs). I > found that ECP mode gave me the "cable disconnected" message. > > Good luck. > Jim Lynch

I have 9 or 10 Olimex LPC-P2106. They are great boards. They always had some problems with the Wiggler (needed speed 5 or above), but they worked. Recently, I've been unable to get any of them to work with a wiggler. I believe they are all rev B silicon. I have upgraded to the latest Philips bootloader (although I don't know why this would matter). I am running a genuine Wiggler with OCD Commander (I've tried several versions) on a 2.4GHz P4 (Dell Dimension 4550) running XP. The same setup works fine with my Olimex LPC-P2124 board. I don't think reset is the problem because I see the same problem on my 2106 based prototypes which have a real reset controller on-board. any ideas? --- In , "tsvetanusunov" <tusunov@m...> wrote: > > I once encunterd the same problem with the Olimex bord & wiggler > > and the OCD and it dosen't worked well (only reset work via the > software) the same problem encunterd with the IAR C compiler when > used with the Olimex LPC2106 board & wiggler > > IAR doesn't work correctly with Wiggler, this have nothing to do with > our boards > > > As I recall the problem can be divided in to 2 categoris > > > > 1) Reset problem : the Olimex board use simple RC type to reset the > CPU > > I don't remember the chip (LPC2106)revision but as i can recall > the first chip revision > > use to have reset problem couse the chip to hang up. > > how did you solved this? can you check if LPC2106 is REV.B? this may > be due to the famous LPC Flash latchup in the first lot we received > from Philips, this is nothing to do with the reset schematic but with > silicon revision bug on LPC chip > > > 2) Speed the computer speed is too high to handel the wiggler data > transfer > > which software this is related to? we have noticed IAR C-SPY works > well on slow computers and don't work on faster one, but this is > problem in IAR IDE not in our boards > > > I manage to overcame the problem using the qudravox C compiler as I > can recall it work well with the Olimex wiggler and LPC2106 board ! > > you are confusing something, Quadravox have no ARM compiler to the > best of my knowledge > > the bottom line is: > our boards works only with compilers/IDEs which work too ;) > - never experienced any problems with Rowley's IDE > - never experienced any problems with OCD when working in RAM > - from time to time working with IAR C-SPY (after number of retries > etc). IAR are aware of this problem, but they just refuse to support > our low cost JTAG to may sell their 300 EUR Segger's J-LINK with > their compiler > > Best regards > Tsvetan

Hi I meant to write CROSSWORKS and insted i wrote quadravox ! regards Bobi Message: 5 Date: Thu, 30 Sep 2004 12:49:31 +0100 From: "Paul Curtis" Subject: RE: Re: JTAG problems with Olimex LPC2106 Hi Bobi, > I once encunterd the same problem with the Olimex bord & > wiggler and the OCD and it dosen't worked well (only reset > work via the software) the same problem encunterd with the > IAR C compiler when used with the Olimex LPC2106 board & wiggler > > As I recall the problem can be divided in to 2 categoris > > 1) Reset problem : the Olimex board use simple RC type to > reset the CPU > I don't remember the chip (LPC2106)revision but as i can > recall the first chip revision > use to have reset problem couse the chip to hang up. > > 2) Speed the computer speed is too high to handel the wiggler > data transfer > > I manage to overcame the problem using the qudravox C > compiler as I can recall it work well with the Olimex wiggler > and LPC2106 board ! That's amazing! You got an MSP430 compiler working with an ARM and wiggler? ;-) -- Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk CrossWorks for MSP430, ARM, and (soon) Atmel AVR processors ________________________________________________________________________ ---------------------------------

> I once encunterd the same problem with the Olimex bord & wiggler > and the OCD and it dosen't worked well (only reset work via the software) the same problem encunterd with the IAR C compiler when used with the Olimex LPC2106 board & wiggler IAR doesn't work correctly with Wiggler, this have nothing to do with our boards > As I recall the problem can be divided in to 2 categoris > > 1) Reset problem : the Olimex board use simple RC type to reset the CPU > I don't remember the chip (LPC2106)revision but as i can recall the first chip revision > use to have reset problem couse the chip to hang up. how did you solved this? can you check if LPC2106 is REV.B? this may be due to the famous LPC Flash latchup in the first lot we received from Philips, this is nothing to do with the reset schematic but with silicon revision bug on LPC chip > 2) Speed the computer speed is too high to handel the wiggler data transfer which software this is related to? we have noticed IAR C-SPY works well on slow computers and don't work on faster one, but this is problem in IAR IDE not in our boards > I manage to overcame the problem using the qudravox C compiler as I can recall it work well with the Olimex wiggler and LPC2106 board ! you are confusing something, Quadravox have no ARM compiler to the best of my knowledge the bottom line is: our boards works only with compilers/IDEs which work too ;) - never experienced any problems with Rowley's IDE - never experienced any problems with OCD when working in RAM - from time to time working with IAR C-SPY (after number of retries etc). IAR are aware of this problem, but they just refuse to support our low cost JTAG to may sell their 300 EUR Segger's J-LINK with their compiler Best regards Tsvetan

--- bobi catorski <> wrote: > Hi > > I once encunterd the same problem with the Olimex > bord & wiggler > and the OCD and it dosen't worked well (only reset > work via the software) the same problem encunterd > with the IAR C compiler when used with the Olimex > LPC2106 board & wiggler > > As I recall the problem can be divided in to 2 > categoris > > 1) Reset problem : the Olimex board use simple RC > type to reset the CPU > I don't remember the chip (LPC2106)revision but > as i can recall the first chip revision > use to have reset problem couse the chip to hang > up. > > 2) Speed the computer speed is too high to handel > the wiggler data transfer > > I manage to overcame the problem using the qudravox > C compiler as I can recall it work well with the > Olimex wiggler and LPC2106 board ! > > Regards > > Bobi > > Message: 8 > Date: Mon, 27 Sep 2004 14:14:41 -0000 > From: "dave_albert" > Subject: JTAG problems with Olimex LPC2106 > > I'm having trouble getting my JTAG Wiggler to work > with an Olimex LPC-P1 (2106 based prototype board). > It works fine with my Olimex LPC2124 based prototype > > board, but always gives me a "cable disconnected" or > "cannot enter debug mode" error. The board resets > properly when I start OCD Commander or ocdlibremote, > > but then enters full run mode. I have tried this > with > the DEBUG jumper on and off at all possible speed > settings for the Wiggler. > > Is anyone else having this problem? > > --------------------------------- >

An Engineer's Guide to the LPC2100 Series