paparazzi-devel
[Top][All Lists]
Advanced

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

Re: [Paparazzi-devel] How compile Lisa L


From: Matheus Siqueira Barros
Subject: Re: [Paparazzi-devel] How compile Lisa L
Date: Wed, 4 May 2011 17:50:13 -0300

Hey guys,
In my case, I connect the board (Lisa / L STM 32), USB cable and nothing appears!
Is this correct or is there a specific bootloader?
I tried this steps up and is going wrong!
I typed the following line in Terminal prompt: 
$ sudo cp $ PAPARAZZI_HOME/conf/system/udev/rules/10-paparazzi.rules / etc / udev / rules.d / 
and the following message is returned:
  cp: can not stat 'conf/system/udev/rules/10-paparazzi.rules': No such file or directory
and this is exists!

Other question is:
*I need some peripheral coupled with the autopilot to compiling?
*The commands the which is on webpage(http://paparazzi.enac.fr/wiki/Compiling#USB_flashing) is to digit in terminal prompt  or in the Paparazzi Center?
*I need to change any pre-existing file for this compiling?

Cheers!

2011/5/3 antoine drouin <address@hidden>
Thank you Felix ! you rock !
But I still believe the example airframe should have the simplest
possible configuration and if possible one that matches default
settings of peripherals. So I would think a transparent telemetry
would make sense.
Poine

On Tue, May 3, 2011 at 2:50 PM, Felix Ruess <address@hidden> wrote:
> There were some print macros missing for UARTs other than 0 or 1,
> fixed now. So xbee_api works with UART2 on lisa as well.
>
> On Tue, May 3, 2011 at 2:24 PM, antoine drouin <address@hidden> wrote:
>> equivalent test programs exist for stm32 ( see
>> conf/autopilot/lisa_l_test_progs.xml )
>>
>> the fixedwing and rotorcraft firmwares are not architecture dependent
>> and build for both lpc and stm.
>>
>> the only difference between a lpc and stm airframe should the line
>> describing the board
>>
>>  <target name="ap"                     board="tiny_1.1"/>
>>
>>  <target name="ap"                      board="lisa_ltiny_1.1"/>
>>
>> I tried this on the "microjet_example.xml" airframe. In order to make
>> it build, I have had to change telemetry from api to transparent (
>> there must be a hickup in xbee_api, as it should definitly be arch
>> dependant ) and comment out the "gyro" subsystem (anyway, this
>> subsystem obsolete and should be superseded by IMU )
>>
>> Regards
>>
>> Poine
>>
>>
>>
>> On Tue, May 3, 2011 at 1:41 PM, Felix Ruess <address@hidden> wrote:
>>> Hi guys,
>>>
>>> please note that these demo programs are only for lpc21xx based
>>> autopilots, so they will not work with stm32 based Lisa/L.
>>>
>>> Cheers, Felix
>>>
>>> On Tue, May 3, 2011 at 1:47 AM, Chris Gough
>>> <address@hidden> wrote:
>>>> OK, I'll try :)
>>>>
>>>> Starting with the command "make AIRCRAFT=DEMO demo2.upload":
>>>>
>>>> "make" is the GNU make program, a kind specialized interpreter for
>>>> running a program that builds software. It should be installed on your
>>>> system (it's a paparazzi prerequisite).
>>>>
>>>> make looks for a file called Makefile, which is the actual program
>>>> that tells it how to build the software. In our case, it runs the
>>>> Paparazzi Makefile (which is included part of the paparazzi sysem).
>>>> This Makefile includes other files. "AIRCRAFT=DEMO demo2.upload" are
>>>> arguments that make sense to the Paparazzi Makefile.
>>>>
>>>> AIRCRAFT=DEMO means use the aircraft configuration called "demo".
>>>> There are probably a few aircraft configurations specified in the
>>>> conf/conf.xml. This file specifies a number of default configurations,
>>>> and you will add others as you progress. As it happens I don't have an
>>>> aircraft called demo in my system, I just fixed the typo in the link
>>>> to the page about that.
>>>>
>>>> The second argument "demo2.upload" is the verb, it's what you are
>>>> actually asking make to do.  It means install the software (called
>>>> demo2) onto the paparazzi autopilot hardware, (as per the appropriate
>>>> configuration).
>>>>
>>>> For the demo2.upload command to work, it has to be configured in the
>>>> DEMO aircraft. Also, the autopilot hardware needs to be plugged into
>>>> your computer and powered up in the correct sequence so that it run's
>>>> it's bootloader program (i.e. is ready to have software loaded onto
>>>> it).  This bit of output:
>>>>
>>>>   Found USB device
>>>>   BootROM code: 2.12
>>>>   Part ID: 0x0402FF25 (LPC2148, 512k Flash, 32k+8k RAM)
>>>>   BootLoader version: 1.3
>>>>   #
>>>>
>>>> means your computer can see the autopilot, which is running  the
>>>> bootloader, so if you get this far you are ready for step 3 :)
>>>>
>>>> What output do you get when you run "make AIRCRAFT=DEMO demo2.output"?
>>>> Do you have a "demo" configured?
>>>>
>>>> Hope that helps.
>>>>
>>>> Chris Gough
>>>>
>>>> On Tue, May 3, 2011 at 9:09 AM, pedro andrade <address@hidden> wrote:
>>>>> Hey Chris,
>>>>> I would like for a detailed explanation of all the output.
>>>>> Please which means: DEMO and which means: demo2.upload (this is the file?)
>>>>> Cheers.
>>>>>> Date: Sat, 30 Apr 2011 07:15:30 +1000
>>>>>> From: address@hidden
>>>>>> To: address@hidden
>>>>>> Subject: Re: [Paparazzi-devel] How compile Lisa L
>>>>>>
>>>>>> Hey Pedro,
>>>>>>
>>>>>> which bit don't you get?
>>>>>>
>>>>>> you just type "make AIRCRAFT=DEMO demo2.upload" and check that the
>>>>>> output contains the important text, i.e. something similar to this:
>>>>>>
>>>>>> Found USB device
>>>>>> BootROM code: 2.12
>>>>>> Part ID: 0x0402FF25 (LPC2148, 512k Flash, 32k+8k RAM)
>>>>>> BootLoader version: 1.3
>>>>>> #
>>>>>>
>>>>>> Or are you looking for a detailed explanation of all the output?
>>>>>>
>>>>>> Chris Gough
>>>>>>
>>>>>> On Sat, Apr 30, 2011 at 6:46 AM, pedro andrade <address@hidden>
>>>>>> wrote:
>>>>>> > Hey World!
>>>>>> > Can somebody explain to me the "Step 2"? Link page
>>>>>> > : http://paparazzi.enac.fr/wiki/Compiling#Step_2
>>>>>> > Cheers
>>>>>> >
>>>>>> > _______________________________________________
>>>>>> > Paparazzi-devel mailing list
>>>>>> > address@hidden
>>>>>> > https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>>>>>> >
>>>>>> >
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> .
>>>>>>
>>>>>> _______________________________________________
>>>>>> Paparazzi-devel mailing list
>>>>>> address@hidden
>>>>>> https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>>>>>
>>>>> _______________________________________________
>>>>> Paparazzi-devel mailing list
>>>>> address@hidden
>>>>> https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> .
>>>>
>>>> _______________________________________________
>>>> Paparazzi-devel mailing list
>>>> address@hidden
>>>> https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>>>>
>>>
>>> _______________________________________________
>>> Paparazzi-devel mailing list
>>> address@hidden
>>> https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>>>
>>
>> _______________________________________________
>> Paparazzi-devel mailing list
>> address@hidden
>> https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>>
>
> _______________________________________________
> Paparazzi-devel mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>

_______________________________________________
Paparazzi-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel



--
+----------------------------------------------------------------------------+
               Matheus Siqueira Barros
                3º Period - Computer Engeneering 
               Federal University of Itajubá (UNIFEI)
                    Phone: +55 (35) 9828-0650
+----------------------------------------------------------------------------+


reply via email to

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