paparazzi-devel
[Top][All Lists]
Advanced

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

Re: [Paparazzi-devel] Paparazzi on Linux and Lisa design questions


From: Felix Ruess
Subject: Re: [Paparazzi-devel] Paparazzi on Linux and Lisa design questions
Date: Mon, 9 Aug 2010 00:22:11 +0200

Hi,

I think user and dev namespaces on the wiki are a decent and easy way to go...
Not sure how to tame the wiki search function though... the search is
kinda bad anyway.

Cheers, Felix

On Sun, Aug 8, 2010 at 10:25 PM, antoine drouin <address@hidden> wrote:
> a simpler bloc diagram :
>  http://paparazzi.enac.fr/wiki_images/Lisa_l_bloc_diag_simple.png
>
> I have started to split the doc for Lisa between a developer part and
> a user part, but it's still mostly empty for now.
> I think we should do the same for the rest of the wiki : users don't
> want to be overwhelmed with too technical informations, and developers
> don't want to lose time with a bunch of details that may look trivial
> to them.
>
> Now how do we get the search function of the wiki to handle that
> user/developer separation ? tags ? using two wikis ?
> What you guys think ?
>
> Regards
>
> Poine
>
> On Sat, Aug 7, 2010 at 11:52 AM, Tilman Baumann <address@hidden> wrote:
>> Thanks.
>> I'm not sure if anything that complex should be my first contact with
>> paparazzi but it sounds totally awesome.
>> Will see, I have to probably ease myself into this whole thing module by
>> module, it is all happening under tight financial pressure. :)
>>
>> But I guess when I have that board and try some examples, I will find out
>> rather quick how it all fits together...
>>
>> Regards
>>  Tilman
>>
>> On 5 Aug 2010, at 21:51, antoine drouin wrote:
>>
>>> Hello Tilman
>>>
>>> There's a block schematic of Lisa/L on the wiki
>>>
>>> http://paparazzi.enac.fr/wiki/Image:Lisa_bd.png
>>>
>>> As you see, the board contains a STM32 (cortexM3 @ 72Mhz) with all
>>> peripherals exposed ( UARTS, I2C, SPI, ADCs, CAN, input capture, PWMs)
>>> and a socket for a gumstix Overo ( OMAP3 at 600Mhz). The link between
>>> the two processor is done by SPI and served by DMA on both sides (so
>>> alot of bandwith with little CPU overhead).
>>> This architecture is designed to be flexible: the STM32 has the
>>> potential to run all the current Paparazzi software alone ( that would
>>> be one side of the spektrum ) or the STM32 can be used only as IO
>>> processor and you can run your autopilot on the Overo ( that would be
>>> the other end of the spektrum ). Of course anything in between is
>>> possible, like for example running stabilization on the STM32 and
>>> navigation on the Overo.
>>>
>>> I'm not sure if that answers your questions. Sorry for the late answer
>>>
>>> Regards
>>>
>>> Poine
>>>
>>> ps: I know the doc about Lisa sucks. I'm focusing on software those
>>> days but I promise I'll work on documentation as soon as possible
>>>
>>> _______________________________________________
>>> 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
>>
>
> _______________________________________________
> Paparazzi-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>



reply via email to

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