Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Message

Re: [lpc2000] Re: IAR and Wiggler JTAG emulator

2006-04-10 by Leon Heller

----- Original Message ----- 
From: "pberna2003" <pberna2003@...>
To: <lpc2000@yahoogroups.com>
Sent: Monday, April 10, 2006 10:48 AM
Subject: [lpc2000] Re: IAR and Wiggler JTAG emulator


> --- In lpc2000@yahoogroups.com, "Leon Heller" <leon.heller@...>
> wrote:
>>
>> ----- Original Message ----- 
>> From: "pberna2003" <pberna2003@...>
>> To: <lpc2000@yahoogroups.com>
>> Sent: Thursday, April 06, 2006 2:10 PM
>> Subject: [lpc2000] IAR and Wiggler JTAG emulator
>>
>>
>> > Dear all
>> >
>> > I'm training to use IAR V4.31A for ARM with wiggler. After
>> > downloading and installing the MAC_MOT.SYS driver (I got it from
>> > Macraigor at http://www.macraigor.com/downloads/ocd_dbgr.exe)
>> >
>> > I installed the driver. Then I have started the IAR C-SPY. Now
> it
>> > recognized the new driver but it sends the error message OCDemon
>> > Error, Internal error 43, and the debugging process doesn't start
>> >
>> > For your info, if I try to use the same Wiggler emulator with
> the
>> > Rowley IDE, all work properly.
>> >
>> > 1) Any idea about the reason of this error using IAR ?
>> > 2) Do anyone know if IAR really support Wiggler ?
>>
>> Are you using a genuine Wiggler or a clone?
>>
>> Leon
>> --
>> Leon Heller, G1HSM
>> leon.heller@...
>> http://www.geocities.com/leon_heller
>>
> Dear Leon
>
> I'm using the Hitex Hitop-link ARM. It is regognized as wiggler
> emulator by Rowley Crosswork and by HI-JTAG V0.2 too without any
> problem. I try also to connect pin 8 to pin 15 of the parallel port
> without any success. It seams the OCD commander doesn't recognize
> the dongle.
>
> Thank you in advance for any additional idea

Sorry, I can't think of anything. My home-made JTAG works OK with OCD 
Commander and CrossWorks. Contact IAR and see what they say.

Leon

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.