|
THIS IS A REPOST - Wrong Subject in prior post. I have been using Segger JLink JTAG with IAR. I frequenly get Blue Screen of Death. I have found that enumerating another USB device during Debug really screws up JLink. This often requires exiting IAR, killing the JLink process and re-loading. But at other times, I have to power down the PC and restart. This obviously slows debugging. Worse, from time to time (several times per day), I get BSOD for no explained reason. The windows dump points to JLink dll as the culprit. Is anyone else running JLink/IAR? Similar problems? I am running Vsn 32 of the dll. I have tried newer dlls from Segger. But I reverted to the latest from IAR web site to get their continued support. I have tried two machines with similar results. I am about to install a new PC just to rule that out as a factor. An associate has had similar results on a 3rd machine. Any recommendations for other products, preferably USB or Ethernet, which are supported by IAR (RDI interface) |
Segger / IAR J-Link JTAG and Blue Screen of Death
Started by ●March 8, 2005
Reply by ●March 8, 20052005-03-08
|
What does IAR say? I have found their tech support good. We are using this exact combo with good luck. One question, are you enabling the PLL and when? I found that if enabled at program start up JLINK had trouble gaining control of the CPU. James --- In , "Dan Beadle" <dan.beadle@i...> wrote: > THIS IS A REPOST - Wrong Subject in prior post. > > I have been using Segger JLink JTAG with IAR. I frequenly get Blue Screen > of Death. I have found that enumerating another USB device during Debug > really screws up JLink. This often requires exiting IAR, killing the JLink > process and re-loading. But at other times, I have to power down the PC and > restart. This obviously slows debugging. Worse, from time to time (several > times per day), I get BSOD for no explained reason. The windows dump points > to JLink dll as the culprit. > Is anyone else running JLink/IAR? Similar problems? > > I am running Vsn 32 of the dll. I have tried newer dlls from Segger. But I > reverted to the latest from IAR web site to get their continued support. > > I have tried two machines with similar results. I am about to install a new > PC just to rule that out as a factor. An associate has had similar results > on a 3rd machine. > > Any recommendations for other products, preferably USB or Ethernet, which > are supported by IAR (RDI interface) |
Reply by ●March 10, 20052005-03-10
|
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 _____ From: jamesasteres [mailto:] Sent: Tuesday, March 08, 2005 8:26 AM To: Subject: [lpc2000] Re: Segger / IAR J-Link JTAG and Blue Screen of Death What does IAR say? I have found their tech support good. We are using this exact combo with good luck. One question, are you enabling the PLL and when? I found that if enabled at program start up JLINK had trouble gaining control of the CPU. James --- In , "Dan Beadle" <dan.beadle@i...> wrote: > THIS IS A REPOST - Wrong Subject in prior post. > > I have been using Segger JLink JTAG with IAR. I frequenly get Blue Screen > of Death. I have found that enumerating another USB device during Debug > really screws up JLink. This often requires exiting IAR, killing the JLink > process and re-loading. But at other times, I have to power down the PC and > restart. This obviously slows debugging. Worse, from time to time (several > times per day), I get BSOD for no explained reason. The windows dump points > to JLink dll as the culprit. > Is anyone else running JLink/IAR? Similar problems? > > I am running Vsn 32 of the dll. I have tried newer dlls from Segger. But I > reverted to the latest from IAR web site to get their continued support. > > I have tried two machines with similar results. I am about to install a new > PC just to rule that out as a factor. An associate has had similar results > on a 3rd machine. > > Any recommendations for other products, preferably USB or Ethernet, which > are supported by IAR (RDI interface) <http://us.ard.yahoo.com/SIG942e75v/M)8184.6018725.7038619.3001176/D=gr oups/S06554205:HM/EXP10385628/A%93423/R=0/SIGel9gslf/*http:/www.n etflix.com/Default?mqso`190075> click here <http://us.adserver.yahoo.com/l?M)8184.6018725.7038619.3001176/D=groups/S= :HM/A%93423/randf8239353 _____ > Terms of Service. |
Reply by ●March 10, 20052005-03-10
|
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 , "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 > > _____ > > From: jamesasteres [mailto:jamesasteres@y...] > Sent: Tuesday, March 08, 2005 8:26 AM > To: > Subject: [lpc2000] Re: Segger / IAR J-Link JTAG and Blue Screen of Death > > What does IAR say? I have found their tech support good. We are > using this exact combo with good luck. One question, are you > enabling the PLL and when? I found that if enabled at program start > up JLINK had trouble gaining control of the CPU. > James > --- In , "Dan Beadle" <dan.beadle@i...> wrote: > > THIS IS A REPOST - Wrong Subject in prior post. > > > > I have been using Segger JLink JTAG with IAR. I frequenly get > Blue Screen > > of Death. I have found that enumerating another USB device during > Debug > > really screws up JLink. This often requires exiting IAR, killing > the JLink > > process and re-loading. But at other times, I have to power down > the PC and > > restart. This obviously slows debugging. Worse, from time to > time (several > > times per day), I get BSOD for no explained reason. The windows > dump points > > to JLink dll as the culprit. > > > > > > Is anyone else running JLink/IAR? Similar problems? > > > > I am running Vsn 32 of the dll. I have tried newer dlls from > Segger. But I > > reverted to the latest from IAR web site to get their continued > support. > > > > I have tried two machines with similar results. I am about to > install a new > > PC just to rule that out as a factor. An associate has had > similar results > > on a 3rd machine. > > > > > > > > Any recommendations for other products, preferably USB or > Ethernet, which > > are supported by IAR (RDI interface) > > > > > > > > > > > > > > > <http://us.ard.yahoo.com/SIG942e75v/M)8184.6018725.7038619.30011 76/D=gr > oups/S06554205:HM/EXP10385628/A%93423/R=0/SIGel9gslf/*http :/www.n > etflix.com/Default?mqso`190075> click here > > <http://us.adserver.yahoo.com/l? M)8184.6018725.7038619.3001176/D=groups/S= > :HM/A%93423/randf8239353 > > _____ > > > Terms of Service. > > |
Reply by ●March 14, 20052005-03-14
|
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 , "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 , "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 > > > > |
Reply by ●March 14, 20052005-03-14
|
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: 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 , "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 , "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 Links a.. To |
Reply by ●March 14, 20052005-03-14
|
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 , "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: > 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 , "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 , "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 Links > > a.. To > > |
Reply by ●March 14, 20052005-03-14
|
Gentleman, I am aware of reset checkbox, infact I have a macro written to do same job... for IAR 4.21A... execUserPreload() { __hwReset(0); } execUserReset() { __hwReset(0); } Still I do not get reset condition .I have Phytech development board for LPC2294. As far as programming is concern, I am compiling my code for Internal RAM and running it from internal RAM. (Flash -- internal is erased )... 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... k b shah ----- Original Message ----- From: jamesasteres To: Sent: Monday, March 14, 2005 1:25 PM Subject: [lpc2000] Re: Segger / IAR J-Link JTAG and Blue Screen of Death 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 , "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: > 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 , "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 , "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 Links > > a.. To > > ------ Yahoo! Groups Links a.. To |
Reply by ●March 15, 20052005-03-15
|
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/ |
Reply by ●March 15, 20052005-03-15
|
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: 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 Links a.. To |
