Lpc2000

Guys,
That was my suspect i.e. my board is bad, but I have tried same JLINK with other board from ATMEL -- AT91SAM7 series , result is same. I have same trouble. Infect my colleague who has another JLINK, has same issue ...also . He spent 3 days worth of time to find out this issue.... since every time you cycle power, the program can break in the interrupt, otherwise,  can not break in the interrupt when there is a breakpoint in interrupt routine.
I do not think it is the issue with my phytech or Atmel board from my colleague.
More like a issue with  JLINK.
k b 
  ----- Original Message ----- 
  From: Robert Adsett 
  To: lpc2000@yahoogroups.com 
  Sent: Monday, March 14, 2005 10:20 PM
  Subject: Re: [lpc2000] Re: Segger / IAR J-Link JTAG and Blue Screen of Death


  At 06:51 PM 3/14/05 -0500, k b shah \(lascaux\) wrote:
  >I  have check reset signal going to CPU --- it does not go to '0' state 
  >i.e. it changes its level  from 3V  -- Normally high to 2V and then back 
  >to 3V...

  That sounds like a hardware fault.  Either with the board or the 
  J-link.  It's acting as if the reset from the J-link is trying to pull it 
  down but can't sink enough current.  Either the pullup on the reset is too 
  strong or the reset on the J-Link is not able to sink reasonable current or 
  there's a bad ground connection or ....

  Robert

  " 'Freedom' has no meaning of itself.  There are always restrictions,   be 
  they legal, genetic, or physical.  If you don't believe me, try to chew a 
  radio signal. "  -- Kelvin Throop, III
  http://www.aeolusdevelopment.com/


        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]