Yahoo Groups archive

Lpc2000

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

Thread

MAM and how to get the most from the LPC2106

MAM and how to get the most from the LPC2106

2005-02-11 by acetoel

Hello

I would like to know how to get the most of the LPC in Speed and
Performance... Now I'm using a 10MHz crystal PLLed to 60MHZ for PCLK
and CCLK, and 240Mhz Fcco (what is this?).
But set MAM or other optimization parameter... well, how can I do it,
and which is the most powerful configuration (it doesn't care that the
MCU consumes more current, my supply is a 12V 7.4Ah Gel Battery)

Thanks

Kimi

Re: MAM and how to get the most from the LPC2106

2005-02-11 by acetoel

Also, now I'm using Thumb Mode, as I'm compiling with -mthumb. 
To run it in ARM mode it should be -marm ?

Thanks

Kimi

--- In lpc2000@yahoogroups.com, "acetoel" <acetoel@y...> wrote:
Show quoted textHide quoted text
> 
> Hello
> 
> I would like to know how to get the most of the LPC in Speed and
> Performance... Now I'm using a 10MHz crystal PLLed to 60MHZ for PCLK
> and CCLK, and 240Mhz Fcco (what is this?).
> But set MAM or other optimization parameter... well, how can I do it,
> and which is the most powerful configuration (it doesn't care that the
> MCU consumes more current, my supply is a 12V 7.4Ah Gel Battery)
> 
> Thanks
> 
> Kimi

Re: [lpc2000] Re: MAM and how to get the most from the LPC2106

2005-02-11 by k b shah (lascaux)

I think, you can look at user guide for PC2292/2294    

UM_LPC21XX_LPC22XX_2_FULLDATA.pdf

 on page 90 to 94 describe abour MAM and the control registers. the copy is provided here for reference... from the manual.
Memory Accelerator Module (MAM) 93 May 03, 2004

MAM CONFIGURATION

After reset the MAM defaults to the disabled state. Software can turn memory access acceleration on or off at any time. This

allows most of an application to be run at the highest possible performance, while certain functions can be run at a somewhat

slower but more predictable rate if more precise timing is required.

REGISTER DESCRIPTION

All registers, regardless of size, are on word address boundaries. Details of the registers appear in the description of each

function.

*Reset Value refers to the data stored in used bits only. It does not include reserved bits content.

Table 37: Summary of System Control Registers

Name Description Access

Reset

Value*

Address

MAM

MAMCR

Memory Accelerator Module Control Register. Determines the MAM

functional mode, that is, to what extent the MAM performance

enhancements are enabled. See Table 38.

R/W 0 0xE01FC000

MAMTIM

Memory Accelerator Module Timing control. Determines the number of

clocks used for Flash memory fetches (1 to 7 processor clocks).

R/W 0x07 0xE01FC004

Memory Accelerator Module (MAM) 94 May 03, 2004

Philips Semiconductors Preliminary User Manual

LPC2119/2129/2194/2292/2294 ARM-based Microcontroller

MAM Control Register (MAMCR - 0xE01FC000)

Two configuration bits select the three MAM operating modes, as shown in Table 38. Following Reset, MAM functions are

disabled. Changing the MAM operating mode causes the MAM to invalidate all of the holding latches, resulting in new reads of

Flash information as required.

MAM Timing Register (MAMTIM - 0xE01FC004)

The MAM Timing register determines how many cclk cycles are used to access the Flash memory. This allows tuning MAM timing

to match the processor operating frequency. Flash access times from 1 clock to 7 clocks are possible. Single clock Flash

accesses would essentially remove the MAM from timing calculations. In this case the MAM mode may be selected to optimize

power usage.

MAM USAGE NOTES

When changing MAM timing, the MAM must first be turned off by writing a zero to MAMCR. A new value may then be written to

MAMTIM. Finally, the MAM may be turned on again by writing a value (1 or 2) corresponding to the desired operating mode to

MAMCR.

For system clock slower than 20 MHz, MAMTIM can be 001. For system clock between 20 MHz and 40 MHz, Flash access time

is suggested to be 2 CCLKs, while in systems with system clock faster than 40 MHz, 3 CCLKs are proposed.

Table 38: MAM Control Register (MAMCR - 0xE01FC000)

MAMCR Function Description

Reset

Value

1:0

MAM mode

control

These bits determine the operating mode of the MAM as follows:

0 0 - MAM functions disabled.

0 1 - MAM functions partially enabled.

1 0 - MAM functions fully enabled.   use this to take full advantage 

1 1 - reserved

0

7:2 Reserved

Reserved, user software should not write ones to reserved bits. The value read from a

reserved bit is not defined.

NA

Table 39: MAM Timing Register (MAMTIM - 0xE01FC004)

MAMTIM Function Description

Reset

Value

2:0

MAM Fetch

Cycle timing

These bits set the duration of MAM Flash fetch operations as follows:

0 0 0 = 0 - Reserved.

0 0 1 = 1 - MAM fetch cycles are 1 processor clock (cclk) in duration.

0 1 0 = 2 - MAM fetch cycles are 2 processor clocks (cclks) in duration.

0 1 1 = 3 - MAM fetch cycles are 3 processor clocks (cclks) in duration.

1 0 0 = 4 - MAM fetch cycles are 4 processor clocks (cclks) in duration.

1 0 1 = 5 - MAM fetch cycles are 5 processor clocks (cclks) in duration.

1 1 0 = 6 - MAM fetch cycles are 6 processor clocks (cclks) in duration.

1 1 1 = 7 - MAM fetch cycles are 7 processor clocks (cclks) in duration.

Warning: Improper setting of this value may result in incorrect operation of the device.

0x07

7:3 Reserved

Reserved, user software should not write ones to reserved bits. The value read from a

reserved bit is not defined.

NA

Philips Semiconductors Preliminary User Manual

LPC2119/2129/2194/2292/2294 ARM-based Microcontroller





k b shah
Show quoted textHide quoted text
  ----- Original Message ----- 
  From: acetoel 
  To: lpc2000@yahoogroups.com 
  Sent: Friday, February 11, 2005 6:37 AM
  Subject: [lpc2000] Re: MAM and how to get the most from the LPC2106



  Also, now I'm using Thumb Mode, as I'm compiling with -mthumb. 
  To run it in ARM mode it should be -marm ?

  Thanks

  Kimi

  --- In lpc2000@yahoogroups.com, "acetoel" <acetoel@y...> wrote:
  > 
  > Hello
  > 
  > I would like to know how to get the most of the LPC in Speed and
  > Performance... Now I'm using a 10MHz crystal PLLed to 60MHZ for PCLK
  > and CCLK, and 240Mhz Fcco (what is this?).
  > But set MAM or other optimization parameter... well, how can I do it,
  > and which is the most powerful configuration (it doesn't care that the
  > MCU consumes more current, my supply is a 12V 7.4Ah Gel Battery)
  > 
  > Thanks
  > 
  > Kimi




        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]

RE: [lpc2000] MAM and how to get the most from the LPC2106

2005-03-08 by Dan Beadle

I have been using Segger JLink JTAG with IAR.  I frequenly get Blue Screen
of Death.  I am running Vsn 32 of the dll.

 

Is anyone else running JLink/IAR?  Similar problems?   I have found that
enumerating another USB device during Debug really screws up JLink.  

 

I have tried two machines with similar results.  I am about to install a new
PC just to rule that out as a factor



[Non-text portions of this message have been removed]

Re: [lpc2000] MAM and how to get the most from the LPC2106

2005-03-08 by microbit

> I have been using Segger JLink JTAG with IAR.  I frequenly get Blue Screen
> of Death.  I am running Vsn 32 of the dll.
> Is anyone else running JLink/IAR?  Similar problems?   I have found that
> enumerating another USB device during Debug really screws up JLink.  
> I have tried two machines with similar results.  I am about to install a new
> PC just to rule that out as a factor
> 

I have a great dislike to that device. IMO it's a piece of crap.
Admittedly, for a big part because it's just about the only commercial USB device I've
come across so far that doesn't support WIN98SE.
It seems it works woefully on XP anyway, given many others' feedback.

I think Segger should pull their finger out and write a more decent driver for it, or somesuch.
I've used numerous USB devices so far on WIN98SE - and none have ever played up or 
crashed the PC.
( Laser printer / Networked, HP DeskJet / Scanner / Copier / Networked, Rowley CrossConnect, 
AVR JTAG-ICE MKII, RFWaves 2.4 GHz Eval/app 1 MBps w/ imaging streams, Silicon Labs CP210X 
drivers & eval/app HW, .... and the list of Eval w/ USB goes on ...)

If I were IAR, I'd be ashamed to have my logo on that half-cooked excuse for a USB JTAG.

-- Kris



[Non-text portions of this message have been removed]

Re: [lpc2000] MAM and how to get the most from the LPC2106

2005-03-08 by Onestone

Now Kris, tell us what you really think about it.

Al

microbit wrote:
Show quoted textHide quoted text
> > I have been using Segger JLink JTAG with IAR.  I frequenly get Blue 
> Screen
> > of Death.  I am running Vsn 32 of the dll.
> > Is anyone else running JLink/IAR?  Similar problems?   I have found that
> > enumerating another USB device during Debug really screws up JLink. 
> > I have tried two machines with similar results.  I am about to 
> install a new
> > PC just to rule that out as a factor
> >
>
> I have a great dislike to that device. IMO it's a piece of crap.
> Admittedly, for a big part because it's just about the only commercial 
> USB device I've
> come across so far that doesn't support WIN98SE.
> It seems it works woefully on XP anyway, given many others' feedback.
>
> I think Segger should pull their finger out and write a more decent 
> driver for it, or somesuch.
> I've used numerous USB devices so far on WIN98SE - and none have ever 
> played up or
> crashed the PC.
> ( Laser printer / Networked, HP DeskJet / Scanner / Copier / 
> Networked, Rowley CrossConnect,
> AVR JTAG-ICE MKII, RFWaves 2.4 GHz Eval/app 1 MBps w/ imaging streams, 
> Silicon Labs CP210X
> drivers & eval/app HW, .... and the list of Eval w/ USB goes on ...)
>
> If I were IAR, I'd be ashamed to have my logo on that half-cooked 
> excuse for a USB JTAG.
>
> -- Kris
>
>
>
> [Non-text portions of this message have been removed]
>
>
> Yahoo! Groups Sponsor
> ADVERTISEMENT
> <http://us.ard.yahoo.com/SIG=129751dki/M=298184.6018725.7038619.3001176/D=groups/S=1706554205:HM/EXP=1110368562/A=2593423/R=0/SIG=11el9gslf/*http://www.netflix.com/Default?mqso=60190075> 
>
>
>
> ------------------------------------------------------------------------
> Yahoo! Groups Links
>
>     * To visit your group on the web, go to:
>       http://groups.yahoo.com/group/lpc2000/
>        
>     * To unsubscribe from this group, send an email to:
>       lpc2000-unsubscribe@yahoogroups.com
>       <mailto:lpc2000-unsubscribe@yahoogroups.com?subject=Unsubscribe>
>        
>     * Your use of Yahoo! Groups is subject to the Yahoo! Terms of
>       Service <http://docs.yahoo.com/info/terms/>.
>
>
>------------------------------------------------------------------------
>
>No virus found in this incoming message.
>Checked by AVG Anti-Virus.
>Version: 7.0.308 / Virus Database: 266.6.4 - Release Date: 7/03/2005
>  
>

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

2005-03-08 by Dan Beadle

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)







[Non-text portions of this message have been removed]

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

2005-03-08 by jamesasteres

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 lpc2000@yahoogroups.com, "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
Show quoted textHide quoted text
> are supported by IAR (RDI interface)
> 
> 
> 
> 
> 
> 
> 
> [Non-text portions of this message have been removed]

RE: [lpc2000] Re: Segger / IAR J-Link JTAG and Blue Screen of Death

2005-03-10 by Dan Beadle

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

 

  _____  
Show quoted textHide quoted text
From: jamesasteres [mailto:jamesasteres@...] 
Sent: Tuesday, March 08, 2005 8:26 AM
To: lpc2000@yahoogroups.com
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 lpc2000@yahoogroups.com, "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)
> 
> 
> 
> 
> 
> 
> 
> [Non-text portions of this message have been removed]








Yahoo! Groups Sponsor



ADVERTISEMENT
 
<http://us.ard.yahoo.com/SIG=12942e75v/M=298184.6018725.7038619.3001176/D=gr
oups/S=1706554205:HM/EXP=1110385628/A=2593423/R=0/SIG=11el9gslf/*http:/www.n
etflix.com/Default?mqso=60190075> click here


 
<http://us.adserver.yahoo.com/l?M=298184.6018725.7038619.3001176/D=groups/S=
:HM/A=2593423/rand=668239353> 

 

  _____  

Yahoo! Groups Links

*	To visit your group on the web, go to:
http://groups.yahoo.com/group/lpc2000/
  
*	To unsubscribe from this group, send an email to:
lpc2000-unsubscribe@yahoogroups.com
<mailto:lpc2000-unsubscribe@yahoogroups.com?subject=Unsubscribe> 
  
*	Your use of Yahoo! Groups is subject to the Yahoo!
<http://docs.yahoo.com/info/terms/>  Terms of Service. 



[Non-text portions of this message have been removed]

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

2005-03-10 by jamesasteres

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
> 
>  
> 
>   _____  
> 
> From: jamesasteres [mailto:jamesasteres@y...] 
> Sent: Tuesday, March 08, 2005 8:26 AM
> To: lpc2000@yahoogroups.com
> 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 lpc2000@yahoogroups.com, "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)
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > [Non-text portions of this message have been removed]
> 
> 
> 
> 
> 
> 
> 
> 
> Yahoo! Groups Sponsor
> 
> 
> 
> ADVERTISEMENT
>  
> 
<http://us.ard.yahoo.com/SIG=12942e75v/M=298184.6018725.7038619.30011
76/D=gr
> 
oups/S=1706554205:HM/EXP=1110385628/A=2593423/R=0/SIG=11el9gslf/*http
:/www.n
> etflix.com/Default?mqso=60190075> click here
> 
> 
>  
> <http://us.adserver.yahoo.com/l?
M=298184.6018725.7038619.3001176/D=groups/S=
Show quoted textHide quoted text
> :HM/A=2593423/rand=668239353> 
> 
>  
> 
>   _____  
> 
> Yahoo! Groups Links
> 
> *	To visit your group on the web, go to:
> http://groups.yahoo.com/group/lpc2000/
>   
> *	To unsubscribe from this group, send an email to:
> lpc2000-unsubscribe@yahoogroups.com
> <mailto:lpc2000-unsubscribe@yahoogroups.com?subject=Unsubscribe> 
>   
> *	Your use of Yahoo! Groups is subject to the Yahoo!
> <http://docs.yahoo.com/info/terms/>  Terms of Service. 
> 
> 
> 
> [Non-text portions of this message have been removed]

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 
Show quoted textHide quoted text
> JLink,
> > hoping that it was hardware, but the driver failures are still 
> happening too
> > often.
> > 
> >  
> > 
> > Dan
> > 
> >

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

2005-03-14 by k b shah (lascaux)

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
Show quoted textHide quoted text
  ----- 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]

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. 
Show quoted textHide quoted text
> 
> 
> 
> [Non-text portions of this message have been removed]

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

2005-03-14 by k b shah (lascaux)

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
Show quoted textHide quoted text
  ----- Original Message ----- 
  From: jamesasteres 
  To: lpc2000@yahoogroups.com 
  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 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]




        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]

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

2005-03-15 by Robert Adsett

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/

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.