Re: [Paparazzi-devel] How compile Lisa L

[Chris Gough]

Hi Matheus,

> I typed the cmd "env | grep PAPARAZZI" and and nothing returned in
> the output !
> Is it good or no?

The env command prints out every environment variable that is
currently set, one per line. Just try it now :) There's usually a lot
of output, so piping it through "grep PAPARAZZI" to filter out the
non-PAPARAZZI lines makes it a bit easier to see what you are looking
for.

In your case, what you found was no lines, you don't have any
environment variables set with PAPARAZZI in their name (or value).
It's only an issue if you want to run paparazzi tools from the command
line.

> And I typed the comand in Paparazzi Center "make AIRCRAFT=myplane clean_ac
> ap.upload"
> But the target has to be on that item?
> And how will I know if the command entered was interpreted correctly!
> I need pressed the button "upload" after this?

See the picture on this page:

http://paparazzi.enac.fr/wiki/Paparazzi_Center

Did you type it into the "Console"? that won't work, it's just for
displaying output. Typing there doesn't do anything.

The section labeled "Running Agents" shows all the programs that have
been started by the Paparazzi Center. These are the programs which
have their Environment Variables set by the Paparazzi Center. These
programs are started by the bits labeled "Execution" or "Building",
you can stop/restart them with those buttons on the right.

The section labeled "Execution" starts (or stops) a collection of
agents. The section labeled "Building" starts the make program (with
the appropriate arguments). You have full control of what is defined
in the Building and Execution sections by editing xml files, and can
make some changes from directly within the Paparazzi Center. The
defaults are probably everything you need for now.

So, there is no need to type at the command line. Using the Paparazzi
Center, you just:

 * select the appropriate configuration files (and save them together
as an "Aircraft" definition)
 * build that aircraft's software (for whatever target, e.g. an
autopilot or local simulation)
 * if you built it for the AP, then you can upload it to the AP with
the upload button.
 * use the software you built in a Executed session, either in
simulation or real life.

Everything the wiki says about output from make on the command line is
also true for the "Console" within the Paparazzi Center.

I suggest you familiarize yourself with building and executing
sessions with the simulator, then move onto programming your
autopilot.

Good Luck :)
Chris Gough

On Sat, May 7, 2011 at 7:14 AM, Matheus Siqueira Barros
<address@hidden> wrote:
> Dear Cris,
>  I'm with the same problem!
> I typed the cmd "env | grep PAPARAZZI" and and nothing returned in
> the output !
> Is it good or no?
> And I typed the comand in Paparazzi Center "make AIRCRAFT=myplane clean_ac
> ap.upload"
> But the target has to be on that item?
> And how will I know if the command entered was interpreted correctly!
> I need pressed the button "upload" after this?
> Cheers!
>
> 2011/5/5 Chris Gough <address@hidden>
>>
>> Hi Pedro,
>>
>> > Could you explain me what means  "PAPARAZZI_HOME"?
>>
>> PAPARAZZI_HOME is a unix environment variable [1]. The Paparazzi
>> Center [2] uses this environment variable to communicate with the
>> various "software agents" (programs/tools that it runs), specifically
>> to tell them where to find the various files they need. If you run
>> those programs manually (e.g. directly from the command line, rather
>> than using the Paparazzi Center), then you need to set (and export)
>> the PAPARAZZI_HOME variable yourself.  It's explained a bit more here
>> [3]:
>>
>> [1] http://en.wikipedia.org/wiki/Environment_variable
>> [2] http://paparazzi.enac.fr/wiki/Paparazzi_Center
>> [3] http://paparazzi.enac.fr/wiki/Installation#Agents
>>
>> Chris Gough
>>
>>
>> On Fri, May 6, 2011 at 11:23 AM, pedro andrade <address@hidden>
>> wrote:
>> > Hi chris,
>> > Could you explain me what means  "PAPARAZZI_HOME"?
>> > Thank you for your attention.
>> > Cheers!
>> >> Date: Fri, 6 May 2011 09:42:18 +1000
>> >> From: address@hidden
>> >> To: address@hidden
>> >> Subject: Re: [Paparazzi-devel] How compile Lisa L
>> >>
>> >> Hi Pedro,
>> >>
>> >> this message
>> >>
>> >> > cp: can not stat 'conf/system/udev/rules/10-paparazzi.rules': No such
>> >> > file or directory
>> >>
>> >> means that the cp command can not find the file. "stat" is a system
>> >> call (checking a file exists, what it's access settings are, etc) used
>> >> by the cp command and just about everything else that touches the file
>> >> system. "cp" is failing before it even tries to copy the file, so It's
>> >> nothing to do with permissions in the target directory
>> >> (/etc/udev/rules.d/).
>> >>
>> >> Note that stat is complaining about a relative file path (it doesn't
>> >> start with a slash). The reason Chrstophe guessed that your
>> >> PAPARAZZI_HOME variable was not set is that your PAPARAZZI_HOME
>> >> variable should be set to an absolute path (e.g.
>> >> "/home/kingkong/src/paparazzi/" or something like that - starts with a
>> >> slash). If you had PAPARAZZI_HOME set to
>> >> "/home/kingcong/src/paparazzi/", then the error message would say
>> >> this: "cp: can not stat
>> >>
>> >> '/home/kingcong/src/paparazzi/conf/system/udev/rules/10-paparazzi.rules':
>> >> No such file or directory"
>> >>
>> >> What is the output when you enter "env | grep PAPARAZZI" ? if you
>> >> don't get back a line telling you what PAPARAZZI_HOME is then you
>> >> don't have one in your current shell's environment.
>> >>
>> >> You could just manually type the full path to
>> >> udev/rules/10-paparazzi.rules into your cp command instead of
>> >> resolving the PAPARAZZI_HOME issues, but you should probably get on
>> >> top of that or it might cause you issues further down the track.
>> >>
>> >> Chris Gough
>> >>
>> >> On Fri, May 6, 2011 at 2:01 AM, pedro andrade
>> >> <address@hidden>
>> >> wrote:
>> >> > Hi Chrstophe,
>> >> > In my case, this is done.
>> >> > But, I can't copy. And I know that I'm the hoot.
>> >> > This is mensage that returns : cp: can not stat
>> >> > 'conf/system/udev/rules/10-paparazzi.rules': No such file or
>> >> > directory
>> >> >
>> >> > Cheers!
>> >> > ________________________________
>> >> > Date: Thu, 5 May 2011 08:25:34 +0200
>> >> > From: address@hidden
>> >> > To: address@hidden
>> >> > Subject: Re: [Paparazzi-devel] How compile Lisa L
>> >> >
>> >> > Hi,
>> >> > if your environment variable $PAPARAZZI_HOME is not set then you
>> >> > should
>> >> > fill
>> >> > in your paparazzi path manually like:
>> >> > sudo cp
>> >> > /home/pedro/paparazzi/conf/system/udev/rules/10-paparazzi.rules
>> >> > /etc/udev/rules.d/
>> >> > (change to your real paparazzi directory location)
>> >> > When plugging in the usb, nothing visible happens, but with the
>> >> > proper
>> >> > packages installed (paparazzi-stm32) and the rules above you should
>> >> > be
>> >> > able
>> >> > to upload some test programs to lisa.
>> >> >
>> >> > -Christophe
>> >> >
>> >> >
>> >> >
>> >> > On Thu, May 5, 2011 at 5:11 AM, pedro andrade
>> >> > <address@hidden>
>> >> > wrote:
>> >> >
>> >> > Hey Chris,
>> >> > 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!
>> >> > In case I know that the directory is correct. I don't understand the
>> >> > error.
>> >> > Why?
>> >> > 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!
>> >> >> Date: Tue, 3 May 2011 09:47:51 +1000
>> >> >> From: address@hidden
>> >> >> To: address@hidden
>> >> >> Subject: Re: [Paparazzi-devel] How compile Lisa L
>> >> >>
>> >> >> 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
>> >
>> > _______________________________________________
>> > 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
> +----------------------------------------------------------------------------+
>
> _______________________________________________
> Paparazzi-devel mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>
>



-- 
.