Hello friends,
I'm with the same problem.
After uploading of a test software using H-JTAG, parallel j-tag (from Olimex) and LPC-E2294, the microcontroller seems to be damaged.

When in the internal flash operation (boot0 and boot1 selected) the messages displayed is "can't halt target and make it enter DEBUG state".
Curiously, when I change to 32-bit external memory (changing boot0 and boot 1 jumpers) the message is "Memory read/write error - Can't re-enter debug state".

Somebody can explain me what is happening and if the uController is really damaged? If no, how can i recover it?

Thanks in advance,
Eduardo Garcia

> Hy Jaya,
>
>I have the same problem with an LPC2103 but I use a parallel j-tag from Olimex (http://www.olimex.com/dev/arm-jtag.html) so I can�t use SILL.
>
>It worked fine until a tried to change the fervency ( I did PLLCFG_bit.MSEL = 10 instead of PLLCFG_bit.MSEL = 4, the crystal fervency is ~14Mhz) from that moment I recived this error message from IAR:
>
>FATAL ERROR
>WinRDI OpenProc failed
>[RDI Error: 602] Can�t halt target and make it enter DEBUG state
>Session aborted!
>
>Sat Apr 28 14:41:32 2007: Failed to load flash loader: C:\Program Files\IAR Systems\Embedded Workbench 4.0 Kickstart\ARM\config\flashloader\NXP\FlashNXPLPC32k.d79
>Is the controller damaged ?
>
>--- In l..., "varuzhandanielyan" wrote:
>> >
>> > Today I unsuccessfully tried to program LPC2378 with
>> > FlashMagic and H-JTAG.
>> >
>> ...
>>
>> > Questions:
>> > 1. Is anybody familiar with the same problem?
>> > 2. Does anybody succeed to program the LPC2378 chip in
>> > similar conditions?
>> > 3. Is it possible to damage permanently the chip by
>> > wrong programming.
>> >
>> > Great thanks in advance,
>> > Varuzhan
>>
>> Hi Varuzhan,
>>
>> Another user here reported identically the same problem. This user
>> was able to recover from the problem using a version of SILL I sent
>> privately.
>>
>> I have incorporate these changes (for LPC2378) to free version you can
>> get from here or in the FILEs page under "BootImages" director:
>>
>> http://www.cse.unsw.edu.au/~jayas/esdk/sill.html
>>
>> Running it as "sill -r comX" should erase your part and get it going
>> again.
>>
>> If it does not work, please drop me an email as I may have missed out
>> propagating all the changes. I know for a fact the diagnostic I sent
>> this other user worked on MCB2300? board with LPC2378.
>>
>> Regards,
>>
>> Jaya
>> Start a New Thread

--- In l..., egnascimento@... wrote:
>
> Hello friends,
> I'm with the same problem.
> After uploading of a test software using H-JTAG, parallel j-tag
(from Olimex) and LPC-E2294, the microcontroller seems to be damaged.
>
> When in the internal flash operation (boot0 and boot1 selected) the
messages displayed is "can't halt target and make it enter DEBUG state".
> Curiously, when I change to 32-bit external memory (changing boot0
and boot 1 jumpers) the message is "Memory read/write error - Can't
re-enter debug state".
>
> Somebody can explain me what is happening and if the uController is
really damaged? If no, how can i recover it?
>
> Thanks in advance,
> Eduardo Garcia
>
Are you sure that the ARM clock is running? Because of the
synchronous clock switchover to the debug clock, ARM cannot enter
debug state, where it runs on the JTAG clock, unless there is a clock
available for ARM.

--Dave Start a New Thread

Hello All,

I have had this problem a few times were my code messed up the jtag
functionality and I was able to recover my part every time by
putting it into ISP mode. In ISP mode the boot code runs and not
the user code. This way what ever I did to mess up JTAG
communication never runs. The only thing is you have to be able to
ground the ISP pin on reset. In case of the LPC2103 this is pin
P0.14.

This has always worked for me.

All the best

Bobby
--- In l..., "derbaier" wrote:
>
> --- In l..., egnascimento@ wrote:
> >
> > Hello friends,
> > I'm with the same problem.
> > After uploading of a test software using H-JTAG, parallel j-tag
> (from Olimex) and LPC-E2294, the microcontroller seems to be
damaged.
> >
> > When in the internal flash operation (boot0 and boot1 selected)
the
> messages displayed is "can't halt target and make it enter DEBUG
state".
> > Curiously, when I change to 32-bit external memory (changing
boot0
> and boot 1 jumpers) the message is "Memory read/write error - Can't
> re-enter debug state".
> >
> > Somebody can explain me what is happening and if the uController
is
> really damaged? If no, how can i recover it?
> >
> > Thanks in advance,
> > Eduardo Garcia
> >
> Are you sure that the ARM clock is running? Because of the
> synchronous clock switchover to the debug clock, ARM cannot enter
> debug state, where it runs on the JTAG clock, unless there is a
clock
> available for ARM.
>
> --Dave
> Start a New Thread