Hello,

I have got an LPC2124 evaluation board and self made Wiggler clone (according
to http://jtag-arm9.sourceforge.net/circuit.txt). When I use it with Rowley's
CrossWorks (eval. ver.), program downloading and debugging work just perfectly.
But when I start OCD Commander[*] an "Internal Error 43" message box appears
and main window is displayed with a message that the software cannot connect
itself to the Wiggler/target system. The strange thing is that some functions
work more or less properly - eg. target system reset (nSRST signal). When I press
the reset button in OCD Commander, the EVB is resetted, OCD Commander stalls
for several seconds and then "cannot enter debug mode" message is displayed.
What may be the cause of such a behaviour?
1. Parallel port mode? Macraigor documentation mentions EPP, but my good old
BX motherboard supports only SPP, SPP+ECP, ECP and ECP+EPP modes. Although
CrossWorks works very well.
2. "Magic" connections inside original Wiggler? I.e some lines on parellel
port side of an original Wiggler are connected in order to OCD commander
or other Macraigor's software could sense if proper hardware is connected
to the parallel port - just like it is done in Xilinx DLC5 cable or Altera
ByteBlasterMV.

[*] I get the same message when I use ocdremote (-c ARM7TDMI-S -d WIGGLER).

Regards,
/J.D.
--
Jan Dubiec We're all living in Amerika
jdx#slackware.pl Coca Cola
+48 506 790442 Sometimes war
Amerika by Rammstein

From:	Anton Erasmus
Subject:	Re: Macraigor OCD Commander and Wiggler clones
Date:	Sat, 15 Jan 2005 13:28:53 +0200

On 15 Jan 2005 11:33:04 +0100, Jan Dubiec
wrote:

>Hello,
>
>I have got an LPC2124 evaluation board and self made Wiggler clone (according
>to http://jtag-arm9.sourceforge.net/circuit.txt). When I use it with Rowley's
>CrossWorks (eval. ver.), program downloading and debugging work just perfectly.
>But when I start OCD Commander[*] an "Internal Error 43" message box appears
>and main window is displayed with a message that the software cannot connect
>itself to the Wiggler/target system. The strange thing is that some functions
>work more or less properly - eg. target system reset (nSRST signal). When I press
[Snipped]

I would not be surprised if Macgraigor have not added an extra link
between an unused input/output pair on the parallel port in their
wiggler. Their new software can the check for this link and report an
error if it does not find it. They probably hope to sell you one of
their wigglers.
Apparently their older version (2.06 ) does not have any problems with
home made wigglers.
Anyone have a newish wiggler from macgraigor they can check ?

--
Anton Erasmus
antone _at_ sentechsa com

From:	Jan Dubiec
Subject:	Re: Macraigor OCD Commander and Wiggler clones
Date:	15 Jan 2005 15:02:17 +0100

On Sat, 15 Jan 2005 13:28:53 +0200, Anton Erasmus wrote:
[.....]
> Apparently their older version (2.06 ) does not have any problems with
> home made wigglers.
Perhaps that's the point. Does anybody know where could I download Macraigor's
older software? I have just done a quick search on Google and found nothig
interesting. :-(

Regards,
/J.D.
--
Jan Dubiec We're all living in Amerika
jdx#slackware.pl Coca Cola
+48 506 790442 Sometimes war
Amerika by Rammstein

From:	Spen
Subject:	Re: Macraigor OCD Commander and Wiggler clones
Date:	Sat, 15 Jan 2005 17:20:10 -0000

v2.05 can be found here:
ftp://stimpy.nuked.org/rod/arm/macraigor/

I have a copy of v2.06 if it is really needed.

Regards
sjo
"Jan Dubiec" wrote in message
news:87r7kmg592.fsf@hs001.slackware.pl...
> On Sat, 15 Jan 2005 13:28:53 +0200, Anton Erasmus
wrote:
> [.....]
> > Apparently their older version (2.06 ) does not have any problems with
> > home made wigglers.
> Perhaps that's the point. Does anybody know where could I download
Macraigor's
> older software? I have just done a quick search on Google and found nothig
> interesting. :-(
>
> Regards,
> /J.D.
> --
> Jan Dubiec We're all living in
Amerika
> jdx#slackware.pl Coca Cola
> +48 506 790442 Sometimes war
> Amerika by
Rammstein

From:	Jan Dubiec
Subject:	Re: Macraigor OCD Commander and Wiggler clones
Date:	16 Jan 2005 11:39:14 +0100

On Sat, 15 Jan 2005 17:20:10 -0000, "Spen" wrote:
> v2.05 can be found here:
> ftp://stimpy.nuked.org/rod/arm/macraigor/
Thanks. This version works well - tested with GDB/Insight from the
latest Macraigor's GNU tools. The strange thing is that the name of
installation package (hwsupport-2.05.exe) says that this is version
2.05, but ocdremote reports that it is 2.06. :-O I have not tested OCD
Commander yet but I am sure that it will work as it is expected. ;-)

> I have a copy of v2.06 if it is really needed.
Actually I do not need it. Although I would like to know which ARM7
families does it support. Ver. 2.05 (2.06???) mentions only ARM7, but
2.08 differentiates between ARM7TDMI and ARM7TDMI-S. Maybe new Wigglers
use RTCK signal?

Regards,
/J.D.
--
Jan Dubiec We're all living in Amerika
jdx#slackware.pl Coca Cola
+48 506 790442 Sometimes war
Amerika by Rammstein

From:	Leon Heller
Subject:	Re: Macraigor OCD Commander and Wiggler clones
Date:	Sat, 15 Jan 2005 17:18:29 -0000

"Anton Erasmus" wrote in message
news:1105788246.4473482a4c8375daa98c3214f98ec201@teranews...
> On 15 Jan 2005 11:33:04 +0100, Jan Dubiec
> wrote:
>
>>Hello,
>>
>>I have got an LPC2124 evaluation board and self made Wiggler clone
>>(according
>>to http://jtag-arm9.sourceforge.net/circuit.txt). When I use it with
>>Rowley's
>>CrossWorks (eval. ver.), program downloading and debugging work just
>>perfectly.
>>But when I start OCD Commander[*] an "Internal Error 43" message box
>>appears
>>and main window is displayed with a message that the software cannot
>>connect
>>itself to the Wiggler/target system. The strange thing is that some
>>functions
>>work more or less properly - eg. target system reset (nSRST signal). When
>>I press
> [Snipped]
>
> I would not be surprised if Macgraigor have not added an extra link
> between an unused input/output pair on the parallel port in their
> wiggler. Their new software can the check for this link and report an
> error if it does not find it. They probably hope to sell you one of
> their wigglers.
> Apparently their older version (2.06 ) does not have any problems with
> home made wigglers.
> Anyone have a newish wiggler from macgraigor they can check ?

I tried it with my genuine Wiggler (a few years old), and it was OK, but it
won't work with my 'Wiggler-alike' either. The previous version was OK.

Leon

From:	Leon Heller
Subject:	Re: Macraigor OCD Commander and Wiggler clones (Problem solved!!!)
Date:	Sun, 16 Jan 2005 11:50:42 -0000

Arie de Munck sent me a schematic of an interface that had a link between
pins 8 and 15 on the DB-25 connector. I added this link to my interface and
it works OK with the current version of OCD Commander. It looks as though
the software wasn't checking this link, previously. I've added the link to
my interface schematic and PCB.

My thanks to Arie.

Leon
--
Leon Heller, G1HSM
http://www.geocities.com/leon_heller

From:	Jan Dubiec
Subject:	Re: Macraigor OCD Commander and Wiggler clones (Problem solved!!!)
Date:	16 Jan 2005 18:23:47 +0100

On Sun, 16 Jan 2005 11:50:42 -0000, "Leon Heller" wrote:
> Arie de Munck sent me a schematic of an interface that had a link between
> pins 8 and 15 on the DB-25 connector. I added this link to my interface and
> it works OK with the current version of OCD Commander.
I confirm. Many thanks.

BTW. What "OCD speed" are you using? I have got two "wigglers": the first
one is HC244 mounted on universal board + flying wires and connectors; the
second is small Xilinx CPLD (XC9536XL) mounted on dedicated, doublesided PCB
- something like Amontec's Chameleon POD but not so small and beautiful. ;-)
I connect them to my PC using 1.5m standard parallel cable and to the EVB
using 20cm long, 20-wire ribbon (28 AWG).

Both devices seem to work very well with CrossWorks with "JTAG clock divider"
set to 1 or "none". With OCD Commander, the first works reliable with "OCD
speed" set to 3, the second with 2. Ocdremote is *very* strange - both "wigglers"
work *reliable* only with speed set to 3, 6, 7 or 8. :-) Reliable in this
context means that a software successfully estabilishes connection to a "wiggler"
every time it is started.

Regards,
/J.D.
--
Jan Dubiec We're all living in Amerika
jdx#slackware.pl Coca Cola
+48 506 790442 Sometimes war
Amerika by Rammstein

From:	Leon Heller
Subject:	Re: Macraigor OCD Commander and Wiggler clones (Problem solved!!!)
Date:	Sun, 16 Jan 2005 20:38:30 -0000

"Jan Dubiec" wrote in message
news:87d5w52spo.fsf@hs001.slackware.pl...
> On Sun, 16 Jan 2005 11:50:42 -0000, "Leon Heller"
> wrote:
>> Arie de Munck sent me a schematic of an interface that had a link between
>> pins 8 and 15 on the DB-25 connector. I added this link to my interface
>> and
>> it works OK with the current version of OCD Commander.
> I confirm. Many thanks.
>
> BTW. What "OCD speed" are you using? I have got two "wigglers": the first
> one is HC244 mounted on universal board + flying wires and connectors; the
> second is small Xilinx CPLD (XC9536XL) mounted on dedicated, doublesided
> PCB
> - something like Amontec's Chameleon POD but not so small and beautiful.
> ;-)
> I connect them to my PC using 1.5m standard parallel cable and to the EVB
> using 20cm long, 20-wire ribbon (28 AWG).
>
> Both devices seem to work very well with CrossWorks with "JTAG clock
> divider"
> set to 1 or "none". With OCD Commander, the first works reliable with "OCD
> speed" set to 3, the second with 2. Ocdremote is *very* strange - both
> "wigglers"
> work *reliable* only with speed set to 3, 6, 7 or 8. :-) Reliable in this
> context means that a software successfully estabilishes connection to a
> "wiggler"
> every time it is started.

My interface works OK at setting 1 with OCD Commander. The real Wiggler will
only work at 3.

Leon

From:	Jan Dubiec
Subject:	Re: Macraigor OCD Commander and Wiggler clones
Date:	16 Jan 2005 12:20:15 +0100

On Sat, 15 Jan 2005 17:18:29 -0000, "Leon Heller" wrote:
[.....]
> I tried it with my genuine Wiggler (a few years old), and it was OK, but it
> won't work with my 'Wiggler-alike' either. The previous version was OK.
So the conclusion is that in genuine Wigglers some of (or all) unused pins of
the DB25 socket are in some way connected to each other or pulled up/down.
It would be nice to know exactly in which way. ;-)

BTW. Reading JTAG Tools docs I have found out how to connect nTRST signal
(JTAG TAP reset): DB25 pin 6 -> a buffer -> IDC20 pin 3.

Regards,
/J.D.
--
Jan Dubiec We're all living in Amerika
jdx#slackware.pl Coca Cola
+48 506 790442 Sometimes war
Amerika by Rammstein

From:	Anton Erasmus
Subject:	Re: Macraigor OCD Commander and Wiggler clones
Date:	Sat, 15 Jan 2005 22:58:59 +0200

On Sat, 15 Jan 2005 17:18:29 -0000, "Leon Heller"
wrote:

>"Anton Erasmus" wrote in message
>news:1105788246.4473482a4c8375daa98c3214f98ec201@teranews...
>> On 15 Jan 2005 11:33:04 +0100, Jan Dubiec
>> wrote:
>>
>>>Hello,
>>>
>>>I have got an LPC2124 evaluation board and self made Wiggler clone
>>>(according
>>>to http://jtag-arm9.sourceforge.net/circuit.txt). When I use it with
>>>Rowley's
>>>CrossWorks (eval. ver.), program downloading and debugging work just
>>>perfectly.
>>>But when I start OCD Commander[*] an "Internal Error 43" message box
>>>appears
>>>and main window is displayed with a message that the software cannot
>>>connect
>>>itself to the Wiggler/target system. The strange thing is that some
>>>functions
>>>work more or less properly - eg. target system reset (nSRST signal). When
>>>I press
>> [Snipped]
>>
>> I would not be surprised if Macgraigor have not added an extra link
>> between an unused input/output pair on the parallel port in their
>> wiggler. Their new software can the check for this link and report an
>> error if it does not find it. They probably hope to sell you one of
>> their wigglers.
>> Apparently their older version (2.06 ) does not have any problems with
>> home made wigglers.
>> Anyone have a newish wiggler from macgraigor they can check ?
>
>I tried it with my genuine Wiggler (a few years old), and it was OK, but it
>won't work with my 'Wiggler-alike' either. The previous version was OK.
>

So can you check what the difference is ? An updated wiggler diagram
would be quite nice.

Regards
Anton Erasmus

From:	Peter Dickerson
Subject:	Re: Macraigor OCD Commander and Wiggler clones
Date:	Sun, 16 Jan 2005 10:11:28 GMT

"Anton Erasmus" wrote in message
news:1105822502.7801f354634d4f6af91b8d72360a8d4c@teranews...
> On Sat, 15 Jan 2005 17:18:29 -0000, "Leon Heller"
> wrote:
>
> >"Anton Erasmus" wrote in message
> >news:1105788246.4473482a4c8375daa98c3214f98ec201@teranews...
> >> On 15 Jan 2005 11:33:04 +0100, Jan Dubiec
> >> wrote:
> >>
> >>>Hello,
> >>>
> >>>I have got an LPC2124 evaluation board and self made Wiggler clone
> >>>(according
> >>>to http://jtag-arm9.sourceforge.net/circuit.txt). When I use it with
> >>>Rowley's
> >>>CrossWorks (eval. ver.), program downloading and debugging work just
> >>>perfectly.
> >>>But when I start OCD Commander[*] an "Internal Error 43" message box
> >>>appears
> >>>and main window is displayed with a message that the software cannot
> >>>connect
> >>>itself to the Wiggler/target system. The strange thing is that some
> >>>functions
> >>>work more or less properly - eg. target system reset (nSRST signal).
When
> >>>I press
> >> [Snipped]
> >>
> >> I would not be surprised if Macgraigor have not added an extra link
> >> between an unused input/output pair on the parallel port in their
> >> wiggler. Their new software can the check for this link and report an
> >> error if it does not find it. They probably hope to sell you one of
> >> their wigglers.
> >> Apparently their older version (2.06 ) does not have any problems with
> >> home made wigglers.
> >> Anyone have a newish wiggler from macgraigor they can check ?
> >
> >I tried it with my genuine Wiggler (a few years old), and it was OK, but
it
> >won't work with my 'Wiggler-alike' either. The previous version was OK.
> >
>
> So can you check what the difference is ? An updated wiggler diagram
> would be quite nice.
>
> Regards
> Anton Erasmus

I get the "Internal Error 43" with a RAVEN-alike using 2.08 but ONLY if the
target power is off when starting ocdremote (and a cable not connected
message at the command-line window). If the target power is on then all is
well.

Peter

From:	Leon Heller
Subject:	Re: Macraigor OCD Commander and Wiggler clones
Date:	Sun, 16 Jan 2005 06:28:37 -0000

"Anton Erasmus" wrote in message
news:1105822502.7801f354634d4f6af91b8d72360a8d4c@teranews...
> On Sat, 15 Jan 2005 17:18:29 -0000, "Leon Heller"
> wrote:
>
>>"Anton Erasmus" wrote in message
>>news:1105788246.4473482a4c8375daa98c3214f98ec201@teranews...
>>> On 15 Jan 2005 11:33:04 +0100, Jan Dubiec
>>> wrote:
>>>
>>>>Hello,
>>>>
>>>>I have got an LPC2124 evaluation board and self made Wiggler clone
>>>>(according
>>>>to http://jtag-arm9.sourceforge.net/circuit.txt). When I use it with
>>>>Rowley's
>>>>CrossWorks (eval. ver.), program downloading and debugging work just
>>>>perfectly.
>>>>But when I start OCD Commander[*] an "Internal Error 43" message box
>>>>appears
>>>>and main window is displayed with a message that the software cannot
>>>>connect
>>>>itself to the Wiggler/target system. The strange thing is that some
>>>>functions
>>>>work more or less properly - eg. target system reset (nSRST signal).
>>>>When
>>>>I press
>>> [Snipped]
>>>
>>> I would not be surprised if Macgraigor have not added an extra link
>>> between an unused input/output pair on the parallel port in their
>>> wiggler. Their new software can the check for this link and report an
>>> error if it does not find it. They probably hope to sell you one of
>>> their wigglers.
>>> Apparently their older version (2.06 ) does not have any problems with
>>> home made wigglers.
>>> Anyone have a newish wiggler from macgraigor they can check ?
>>
>>I tried it with my genuine Wiggler (a few years old), and it was OK, but
>>it
>>won't work with my 'Wiggler-alike' either. The previous version was OK.
>>
>
> So can you check what the difference is ? An updated wiggler diagram
> would be quite nice.

Some time ago I was working out the Wiggler schematic, but have misplaced my
notes. My I/F is quite different from the Wiggler, and is based on the ASCII
art schematic that is floating around. For instance, I only use one '244
buffer and one transistor.

Leon

From:	Anton Erasmus
Subject:	Re: Macraigor OCD Commander and Wiggler clones
Date:	Sun, 16 Jan 2005 22:02:17 +0200

On Sun, 16 Jan 2005 06:28:37 -0000, "Leon Heller"
wrote:

>"Anton Erasmus" wrote in message
>news:1105822502.7801f354634d4f6af91b8d72360a8d4c@teranews...
>> On Sat, 15 Jan 2005 17:18:29 -0000, "Leon Heller"
>> wrote:
>>
>>>"Anton Erasmus" wrote in message
>>>news:1105788246.4473482a4c8375daa98c3214f98ec201@teranews...
>>>> On 15 Jan 2005 11:33:04 +0100, Jan Dubiec
>>>> wrote:
>>>>
>>>>>Hello,
>>>>>
>>>>>I have got an LPC2124 evaluation board and self made Wiggler clone
>>>>>(according
>>>>>to http://jtag-arm9.sourceforge.net/circuit.txt). When I use it with
>>>>>Rowley's
>>>>>CrossWorks (eval. ver.), program downloading and debugging work just
>>>>>perfectly.
>>>>>But when I start OCD Commander[*] an "Internal Error 43" message box
>>>>>appears
>>>>>and main window is displayed with a message that the software cannot
>>>>>connect
>>>>>itself to the Wiggler/target system. The strange thing is that some
>>>>>functions
>>>>>work more or less properly - eg. target system reset (nSRST signal).
>>>>>When
>>>>>I press
>>>> [Snipped]
>>>>
>>>> I would not be surprised if Macgraigor have not added an extra link
>>>> between an unused input/output pair on the parallel port in their
>>>> wiggler. Their new software can the check for this link and report an
>>>> error if it does not find it. They probably hope to sell you one of
>>>> their wigglers.
>>>> Apparently their older version (2.06 ) does not have any problems with
>>>> home made wigglers.
>>>> Anyone have a newish wiggler from macgraigor they can check ?
>>>
>>>I tried it with my genuine Wiggler (a few years old), and it was OK, but
>>>it
>>>won't work with my 'Wiggler-alike' either. The previous version was OK.
>>>
>>
>> So can you check what the difference is ? An updated wiggler diagram
>> would be quite nice.
>
>Some time ago I was working out the Wiggler schematic, but have misplaced my
>notes. My I/F is quite different from the Wiggler, and is based on the ASCII
>art schematic that is floating around. For instance, I only use one '244
>buffer and one transistor.

Hi,

I see on the avr-gcc list you mentioned that the missing piece in the
current ASCII Wiggler schematic floating around is a link between pin
8 and pin 15 on the DB25 connector.

Regards
Anton Erasmus

From:	Leon Heller
Subject:	Re: Macraigor OCD Commander and Wiggler clones
Date:	Sun, 16 Jan 2005 20:36:47 -0000

"Anton Erasmus" wrote in message
news:1105905511.ecf1e8b0b0b1d2231f5d24260f808950@teranews...
> On Sun, 16 Jan 2005 06:28:37 -0000, "Leon Heller"
> wrote:
>
>>"Anton Erasmus" wrote in message
>>news:1105822502.7801f354634d4f6af91b8d72360a8d4c@teranews...
>>> On Sat, 15 Jan 2005 17:18:29 -0000, "Leon Heller"
>>> wrote:
>>>
>>>>"Anton Erasmus" wrote in message
>>>>news:1105788246.4473482a4c8375daa98c3214f98ec201@teranews...
>>>>> On 15 Jan 2005 11:33:04 +0100, Jan Dubiec
>>>>> wrote:
>>>>>
>>>>>>Hello,
>>>>>>
>>>>>>I have got an LPC2124 evaluation board and self made Wiggler clone
>>>>>>(according
>>>>>>to http://jtag-arm9.sourceforge.net/circuit.txt). When I use it with
>>>>>>Rowley's
>>>>>>CrossWorks (eval. ver.), program downloading and debugging work just
>>>>>>perfectly.
>>>>>>But when I start OCD Commander[*] an "Internal Error 43" message box
>>>>>>appears
>>>>>>and main window is displayed with a message that the software cannot
>>>>>>connect
>>>>>>itself to the Wiggler/target system. The strange thing is that some
>>>>>>functions
>>>>>>work more or less properly - eg. target system reset (nSRST signal).
>>>>>>When
>>>>>>I press
>>>>> [Snipped]
>>>>>
>>>>> I would not be surprised if Macgraigor have not added an extra link
>>>>> between an unused input/output pair on the parallel port in their
>>>>> wiggler. Their new software can the check for this link and report an
>>>>> error if it does not find it. They probably hope to sell you one of
>>>>> their wigglers.
>>>>> Apparently their older version (2.06 ) does not have any problems with
>>>>> home made wigglers.
>>>>> Anyone have a newish wiggler from macgraigor they can check ?
>>>>
>>>>I tried it with my genuine Wiggler (a few years old), and it was OK, but
>>>>it
>>>>won't work with my 'Wiggler-alike' either. The previous version was OK.
>>>>
>>>
>>> So can you check what the difference is ? An updated wiggler diagram
>>> would be quite nice.
>>
>>Some time ago I was working out the Wiggler schematic, but have misplaced
>>my
>>notes. My I/F is quite different from the Wiggler, and is based on the
>>ASCII
>>art schematic that is floating around. For instance, I only use one '244
>>buffer and one transistor.
>
> Hi,
>
> I see on the avr-gcc list you mentioned that the missing piece in the
> current ASCII Wiggler schematic floating around is a link between pin
> 8 and pin 15 on the DB25 connector.

I've mentioned it on this thread, as well. It solves the problem.

Leon

From:	Arie de Muynck
Subject:	Re: Macraigor OCD Commander and Wiggler clones
Date:	Sun, 16 Jan 2005 16:35:06 +0100

There should be a link on the D-connector connecting pin 8 to 15, it is used
to find the Wiggler when the port is unknown. It could be used to ignore a
homebrew Wiggler.

Regards,
Arie de Muynck

From:	Peter Dickerson
Subject:	Re: Macraigor OCD Commander and Wiggler clones
Date:	Sat, 15 Jan 2005 11:10:21 GMT

"Jan Dubiec" wrote in message
news:87zmzbf0db.fsf@hs001.slackware.pl...
> Hello,
>
> I have got an LPC2124 evaluation board and self made Wiggler clone
(according
> to http://jtag-arm9.sourceforge.net/circuit.txt). When I use it with
Rowley's
> CrossWorks (eval. ver.), program downloading and debugging work just
perfectly.
> But when I start OCD Commander[*] an "Internal Error 43" message box
appears
> and main window is displayed with a message that the software cannot
connect
> itself to the Wiggler/target system. The strange thing is that some
functions
> work more or less properly - eg. target system reset (nSRST signal). When
I press
> the reset button in OCD Commander, the EVB is resetted, OCD Commander
stalls
> for several seconds and then "cannot enter debug mode" message is
displayed.
> What may be the cause of such a behaviour?
> 1. Parallel port mode? Macraigor documentation mentions EPP, but my good
old
> BX motherboard supports only SPP, SPP+ECP, ECP and ECP+EPP modes.
Although
> CrossWorks works very well.
> 2. "Magic" connections inside original Wiggler? I.e some lines on
parellel
> port side of an original Wiggler are connected in order to OCD
commander
> or other Macraigor's software could sense if proper hardware is
connected
> to the parallel port - just like it is done in Xilinx DLC5 cable or
Altera
> ByteBlasterMV.
>
> [*] I get the same message when I use ocdremote (-c ARM7TDMI-S -d
WIGGLER).

?? when I try this with ocdlibremote I get
ocdlibremote -c ARM7TDMI-S -d WIGGLER
ERROR: unknown cpu type: ARM7TDMI-S.

and ARM7TDMI-S is exactly what I want.

> Regards,
> /J.D.
> --
> Jan Dubiec We're all living in
Amerika
> jdx#slackware.pl Coca Cola
> +48 506 790442 Sometimes war
> Amerika by
Rammstein

Peter

From:	Jan Dubiec
Subject:	Re: Macraigor OCD Commander and Wiggler clones
Date:	15 Jan 2005 14:21:45 +0100

On Sat, 15 Jan 2005 11:10:21 GMT, "Peter Dickerson" wrote:
[.....]
> ?? when I try this with ocdlibremote I get
> ocdlibremote -c ARM7TDMI-S -d WIGGLER
> ERROR: unknown cpu type: ARM7TDMI-S.
>
> and ARM7TDMI-S is exactly what I want.
Try this: http://www.macraigor.com/gnu/hwsupport-2.08.exe

Regards,
/J.D.
--
Jan Dubiec We're all living in Amerika
jdx#slackware.pl Coca Cola
+48 506 790442 Sometimes war
Amerika by Rammstein

From:	Peter Dickerson
Subject:	Re: Macraigor OCD Commander and Wiggler clones
Date:	Sat, 15 Jan 2005 16:20:07 GMT

"Jan Dubiec" wrote in message
news:87vf9yg74m.fsf@hs001.slackware.pl...
> On Sat, 15 Jan 2005 11:10:21 GMT, "Peter Dickerson"
wrote:
> [.....]
> > ?? when I try this with ocdlibremote I get
> > ocdlibremote -c ARM7TDMI-S -d WIGGLER
> > ERROR: unknown cpu type: ARM7TDMI-S.
> >
> > and ARM7TDMI-S is exactly what I want.
> Try this: http://www.macraigor.com/gnu/hwsupport-2.08.exe
>
> Regards,
> /J.D.
> --
> Jan Dubiec We're all living in
Amerika
> jdx#slackware.pl Coca Cola
> +48 506 790442 Sometimes war
> Amerika by
Rammstein

Thanks!

Peter