paparazzi-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: RE: [Paparazzi-devel] LPC2148 performance


From: Martin Mueller
Subject: Re: RE: [Paparazzi-devel] LPC2148 performance
Date: Wed, 2 Dec 2009 17:01:55 +0100 (MET)

Hi,

some long time ago a measurement was done for the ATMEGA processor and showed a 
maximum load of around 17% for that "old" 8bit 16MHz processor. Maybe that 
stuff could help to implement a load monitor for the LPC.

http://lists.gnu.org/archive/html/paparazzi-devel/2005-09/msg00001.html

Martin

----- original Nachricht --------

Betreff: RE: [Paparazzi-devel] LPC2148 performance
Gesendet: Mi, 02. Dez 2009
Von: Cédric Marzer<address@hidden>

> Would it be possible to add an extra message that shows a percentage
> telling
> how much of the processing power one has left ? I think there is plenty of
> processing power left for a normal flight but having some feedback would be
> reassuring...
> 
> Cédric
> 
> -----Message d'origine-----
> De : address@hidden
> [mailto:address@hidden De la
> part
> de Steve Joyce
> Envoyé : mardi, 1. décembre 2009 15:52
> À : address@hidden
> Objet : [Paparazzi-devel] LPC2148 performance
> 
> Has anyone ever done any profiling on the airborne code to see how how many
> 
> extra cycles are available in the various loops? I don't really have a good
> 
> feeling for how much extra code you could sqeeze in there.  Are there tools
> 
> available for that type of analysis?
> 
> What would actually happen if you exceeded the available instructions
> within
> 
> a loop?
> 
> /steve 
> 
> 
> 
> _______________________________________________
> Paparazzi-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
> 
> 
> 
> _______________________________________________
> Paparazzi-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
> 

--- original Nachricht Ende ----





reply via email to

[Prev in Thread] Current Thread [Next in Thread]