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 jamesasteres

What are you trying to do - Program via ISP (Philips utility) and 
then trying to debug with JLINK?  Is that valid?  Also, there is a 
checkbox in the IAR setup for JLINK to reset the micro.  The 
problems do seem to be something like you gents are describing, 
though.
James


--- In lpc2000@yahoogroups.com, "k b shah \(lascaux\)" <kbshah@l...> 
wrote:
> I think issue with JLINk is ---> it does not provide good reset 
signal to processor.
> After download it does not provide Reset to CPU --> This in turn 
doe not provide default reset condition of CPU when you start 
debugging.
> --Result is --- > you can  not break in the interrupts at all when 
you are reloading program or restart debugging before cycling power 
to main board  every time.
> Also if you turn of power in the middle of debug and start  
debugging again, it provides you blue screen well come messge..... 
wow...crash... I am using windows 2000 with SP4 installed ..
> k b shah
> 
>   ----- Original Message ----- 
>   From: Mark Butcher 
>   To: lpc2000@yahoogroups.com 
>   Sent: Monday, March 14, 2005 6:49 AM
>   Subject: [lpc2000] Re: Segger / IAR J-Link JTAG and Blue Screen 
of Death
> 
> 
> 
>   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
>   > > 
>   > >  
> 
> 
> 
> 
> 
>         Yahoo! Groups Sponsor 
>               ADVERTISEMENT
>              
>        
>        
> 
> 
> -------------------------------------------------------------------
-----------
>   Yahoo! Groups Links
> 
>     a.. To visit your group on the web, go to:
>     http://groups.yahoo.com/group/lpc2000/
>       
>     b.. To unsubscribe from this group, send an email to:
>     lpc2000-unsubscribe@yahoogroups.com
>       
>     c.. Your use of Yahoo! Groups is subject to the Yahoo! Terms 
of Service. 
> 
> 
> 
> [Non-text portions of this message have been removed]

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.