Yahoo Groups archive

Lpc2000

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

Message

Re: Segger / IAR J-Link JTAG and Blue Screen of Death

2005-03-14 by Mark Butcher

Hi

I use the J-Link and sometimes there are quite a lot of problems 
with it and sometimes it works quite well.

What I have found is that it is deadly to have programmed an 
operating code via ISP. I can't explain why but the debugger hangs 
and crashes and often doesn't want to do anything sensible.

When I delete the code form FLASH (using ISP again - ie. Philips 
upload uitility) all is very stable again.

Could this help?

Regards

Mark Butcher

www.mjbc.ch


--- In lpc2000@yahoogroups.com, "jamesasteres" <jamesasteres@y...> 
wrote:
> 
> I agree that the BSOD shouldn't be caused by a too-fast CPU.  
Sorry, 
> I can't help more.  But, one of the engineers here using that same 
> IAR/JLINK combo has BSODs also.  Please post if you find out 
> anything.
> Tahn
> 
> --- In lpc2000@yahoogroups.com, "Dan Beadle" <dan.beadle@i...> 
wrote:
> > Thanks for the tip.  I do turn on PLL very early - in first dozen
> > instructions or so.  
> > 
> >  
> > 
> > I do sometimes have trouble gaining control - get illegal CPU 
ID.  
> Power
> > cycling the board (and resetting the CPU)  does seem to help 
> that.  But I
> > don't see how it would cause BSOD.  
> > 
> >  
> > 
> > IAR has been pretty good on compiler issues.  They swapped out 
the 
> JLink,
> > hoping that it was hardware, but the driver failures are still 
> happening too
> > often.
> > 
> >  
> > 
> > Dan
> > 
> >

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.