Hi,

> > Thats exactly what I had to do!
> > I needed to install ALL the S/W on the Olimex disk (inc
> > GCC/Eclipse/etc...) just to get at the drvers.
> > I then copied these driver elsewhere and then uninstalled all the
> > Olimex stuff.
> > Then installed the drivers again so that CrossWorks could see them.
> > It would've been nice if these could be extracted from the CD or as
> > seperate download from the Olimex site.
> >
> > Thanks
> > Mark
>
> OK, so now I find myself in this same position. How did you get it to
> go?
>
> My CrossStudio see's the tiny but not the device (micrcontroller).
> The message is "Cannot identify target...". The target is IAR
> LPC2148, it's powered (5v source set to EXT), DBG jumper is on,
> bootloader DIPs are both off).
>
> My arm-usb-timy shows up as COM8 and I don't see any process that
> looks like OpenOCD. Does one need to "run" OpenOCD?

There is no OpenOCD in CrossWorks. You may need to set TRST Open Drain = No
and set the JTAG divider low, e.g. to 10 or 20 to get it slow enough.

--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3 processors

--- In l..., "armdev65" wrote:
>
> Thats exactly what I had to do!
> I needed to install ALL the S/W on the Olimex disk (inc
> GCC/Eclipse/etc...) just to get at the drvers.
> I then copied these driver elsewhere and then uninstalled all the
> Olimex stuff.
> Then installed the drivers again so that CrossWorks could see them.
> It would've been nice if these could be extracted from the CD or as
> seperate download from the Olimex site.
>
> Thanks
> Mark

OK, so now I find myself in this same position. How did you get it to
go?

My CrossStudio see's the tiny but not the device (micrcontroller).
The message is "Cannot identify target...". The target is IAR
LPC2148, it's powered (5v source set to EXT), DBG jumper is on,
bootloader DIPs are both off).

My arm-usb-timy shows up as COM8 and I don't see any process that
looks like OpenOCD. Does one need to "run" OpenOCD?

Thats exactly what I had to do!
I needed to install ALL the S/W on the Olimex disk (inc
GCC/Eclipse/etc...) just to get at the drvers.
I then copied these driver elsewhere and then uninstalled all the
Olimex stuff.
Then installed the drivers again so that CrossWorks could see them.
It would've been nice if these could be extracted from the CD or as
seperate download from the Olimex site.

Thanks
Mark

--- In l..., "Leon" wrote:
>
> ----- Original Message -----
> From: "armdev65"
> To:
> Sent: Saturday, August 04, 2007 2:46 AM
> Subject: [lpc2000] CrossWorks and Olimex ARM-USB-TINY
> > Hi,
> > I running CrossWorks 1.7 with an Olimex ARM-USB-TINY.
> > And the JTAG is connected to a OLIMEX LPC-P2148.
> >
> > I get the following error message when I select the ARM-USB-TINY
from
> > the Targets:
> > "cannot find USB device (vid=0x15BA, pid=0x0004,
serial=,channel=0)"
> >
> > what does this mean? is it no seeing the board or the ARM-USB-
TINY??
> >
> > I've also created a Generic FT2232 Device with the same vid/pid
> > values, and get the same error. (So aleast its consistent)
> >
> > Reading the web, suggests pid = 0x0004 is correct, not 0x0003.
But it
> > makes no differene.
> > If I disconnet the ARM-USB-TINY, I get a different error saying
no
> > ARM-USB-TINY attached, which is good, as I'm sure its seeing the
> > dongle.
> >
> > I Cannot find instructions anywhere on how to set this all up.
From
> > what I found I think all I needed to do was copy the FTD2xx.dll
to
> > the Crossworks bin directory. (A least it can see the ARM-USB-
TINY
> > when this dll is there)
> >
> >
> > Q. Can someone indicate if this is a problem with set up, or is
the
> > ARM-USB-TINY not seeing the LPC-P2148 dev board for some reason.
> >
> > I've just moved from AVRs to ARMs, and great fun but a bit
frustating
> > at the moment.
> Have you followed the installation details on the Olimex web site?
>
> Leon
> --
> Leon Heller
> Amateur radio call-sign G1HSM
> Yaesu FT-817ND and FT-857D transceivers
> Suzuki SV1000S motorcycle
> leon355@...
> http://webspace.webring.com/people/jl/leon_heller/
>

----- Original Message -----
From: "armdev65"
To:
Sent: Saturday, August 04, 2007 2:46 AM
Subject: [lpc2000] CrossWorks and Olimex ARM-USB-TINY
> Hi,
> I running CrossWorks 1.7 with an Olimex ARM-USB-TINY.
> And the JTAG is connected to a OLIMEX LPC-P2148.
>
> I get the following error message when I select the ARM-USB-TINY from
> the Targets:
> "cannot find USB device (vid=0x15BA, pid=0x0004, serial=,channel=0)"
>
> what does this mean? is it no seeing the board or the ARM-USB-TINY??
>
> I've also created a Generic FT2232 Device with the same vid/pid
> values, and get the same error. (So aleast its consistent)
>
> Reading the web, suggests pid = 0x0004 is correct, not 0x0003. But it
> makes no differene.
> If I disconnet the ARM-USB-TINY, I get a different error saying no
> ARM-USB-TINY attached, which is good, as I'm sure its seeing the
> dongle.
>
> I Cannot find instructions anywhere on how to set this all up. From
> what I found I think all I needed to do was copy the FTD2xx.dll to
> the Crossworks bin directory. (A least it can see the ARM-USB-TINY
> when this dll is there)
> Q. Can someone indicate if this is a problem with set up, or is the
> ARM-USB-TINY not seeing the LPC-P2148 dev board for some reason.
>
> I've just moved from AVRs to ARMs, and great fun but a bit frustating
> at the moment.
Have you followed the installation details on the Olimex web site?

Leon
--
Leon Heller
Amateur radio call-sign G1HSM
Yaesu FT-817ND and FT-857D transceivers
Suzuki SV1000S motorcycle
l...@btinternet.com
http://webspace.webring.com/people/jl/leon_heller/

Hi,
I running CrossWorks 1.7 with an Olimex ARM-USB-TINY.
And the JTAG is connected to a OLIMEX LPC-P2148.

I get the following error message when I select the ARM-USB-TINY from
the Targets:
"cannot find USB device (vid=0x15BA, pid=0x0004, serial=,channel=0)"

what does this mean? is it no seeing the board or the ARM-USB-TINY??

I've also created a Generic FT2232 Device with the same vid/pid
values, and get the same error. (So aleast its consistent)

Reading the web, suggests pid = 0x0004 is correct, not 0x0003. But it
makes no differene.
If I disconnet the ARM-USB-TINY, I get a different error saying no
ARM-USB-TINY attached, which is good, as I'm sure its seeing the
dongle.

I Cannot find instructions anywhere on how to set this all up. From
what I found I think all I needed to do was copy the FTD2xx.dll to
the Crossworks bin directory. (A least it can see the ARM-USB-TINY
when this dll is there)
Q. Can someone indicate if this is a problem with set up, or is the
ARM-USB-TINY not seeing the LPC-P2148 dev board for some reason.

I've just moved from AVRs to ARMs, and great fun but a bit frustating
at the moment.

Thanks

An Engineer's Guide to the LPC2100 Series