Difference between revisions of "Compiling"

From PaparazziUAV
Jump to navigation Jump to search
(Redirected page to FirmwareFlashing)
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
== Introduction ==
#REDIRECT [[FirmwareFlashing]]
 
The goal of this part of the documentation is to give you insight in how to give your Autopilot board a ''Brain''. Airborne autopilot code, flight plans and configuration settings are compiled into a single file, sometimes referred to as a ''binary image''. After compilation this file is transferred to the Autopilot board micro-controller flash ROM through use of an USB cable. Note that most tuning and flight plan parameters can be changed in-flight but after each power cycle, the autopilot reverts to the original settings. Permanent changes are made by recompiling the airborne code and it's new configurations settings, and re-upload this to the autopilot board. It may sound complicated but in fact it is quite simple if you follow the steps below.
 
== Flashing ==
 
=== USB flashing ===
[[Image:Tiny_test_wiring.jpg|thumb|Example wiring for programming and telemetry]]
If the autopilot senses a connected USB cable during power-on, it will wait to receive a firmware image rather than booting normally.  The firmware can be compiled and flashed by several means, '''the simplest way using the [[Paparazzi_Center|Paparazzi Center]]''', the traditional way being:
make AIRCRAFT=''myplane'' clean_ac ap.upload
(where ''myplane'' is the name of your airframe as defined in <tt>conf/conf.xml</tt>)
 
This command erases any compiled autopilot code from the PC, recompiles everything from scratch, and then sends it to the autopilot. 
Variations include:
* make AIRCRAFT=''myplane'' sim
*: Compiles your code for use in the simulator - note that "clean_ac" will remove this code, so the simulator code must be rebuilt each time a clean has been performed.
* make AIRCRAFT=''myplane'' fbw.upload
*: This is needed when configuring the separate "fly by wire" MCU on the [[Classix]] autopilot.
* make AIRCRAFT=''myplane'' ap
*: This will simply build the portions of autopilot code that have changed since the last compile without attempting to flash.  Note: this method may not detect certain changes (i.e. changes to the airframe makefile section or CVS updated code).
* make AIRCRAFT=''myplane'' ap.upload FLASH_MODE=IAP
*: Specifies USB flashing.  This should be specified at the top of the makefile section of your airframe file but can be overridden here.  Use FLASH_MODE=IAS for serial flashing.
 
=== Serial Flashing ===
You can also flash via serial cable or modem, but it takes a longer time.
You can't just consider the baud rate to estimate the duration of the operation are there are many exchanges in the flashing protocol and the com latency over RF becomes significant.
* make AIRCRAFT=''myplane'' ap.upload FLASH_MODE=ISP
Or add <configure name="FLASH_MODE" value="ISP"/> to the firmware section of your [[Airframe_Configuration|airframe file]].
 
Example: make AIRCRAFT=NAVGOV3 ap.upload FLASH_MODE=ISP
 
NOTES:
- Make sure you connect your serial device to UART0
- Make sure you pull P0.14 boot pin low on power on to enable the LPC ISP mode
 
=== JTAG Flashing ===
 
I will be adding more info here as I compile and upload to the Lisa/M board. The info I placed here is directly from the mailing list. - cwozny
 
Ensure that the paparazzi-dev, paparazzi-arm-multilib and openocd packages are installed in your distro via:
 
sudo apt-get install paparazzi-dev paparazzi-arm-multilib openocd
 
Make sure you have openocd-0.5 or higher, if you are on Ubuntu lucid or natty, you can add [https://launchpad.net/~paparazzi-uav/+archive/ppa ppa:paparazzi-uav/ppa] which includes backported openocd packages.
 
This is all you need to build AND flash the STM microprocessor. The reason for this method of flashing is that there is no boot loader for this microprocessor yet which is what is required for USB/Serial flashing. Currently, only the Lisa boards utilize the STM32 microprocessor. Lisa/L has an onboard JTAG while Lisa/M needs an external JTAG. You can now build paparazzi, run the [[Paparazzi_Center|Paparazzi Center]], adapt an airframe (e.g. microjet_example.xml) to board="lisa_m_1.1", compile and upload. During an upload the JTAG RxTx LEDs should blink. Make sure you also configured the paparazzi-rules explained on the installation page.
 
=== Start the usb bootloader on an LPC21xx based board ===
 
Connect an USB cable to the USB port on the autopilot board.
 
<gallery>
Image:Fase2_Insert_Flightplan_A.jpg|Board to mini USB connect
Image:Fase2_Insert_Flightplan_B.jpg|Make sure you have a connector for power ('''Don't''' power up yet!)
Image:Fase2_Insert_Flightplan_C.jpg|Connect USB to PC '''and''' Board
Image:Fase2_Insert_Flightplan_D.jpg|only '''now''', power up the board
</gallery>
 
==== Check if the usb bootloader is installed on an LPC21xx based board ====
Now if you type the following command in your terminal...
 
$ dmesg | tail
 
..you should see messages that look like:
 
[82342.968031] usb 5-1: new high speed USB device using ehci_hcd and address 24
 
Which confirms that your device is powered up and working, and ready to accept new airborne code. In case you do not see this message, check your battery voltage and connections and make sure the cables are not broken.
 
When you upload in the Paparazzi Center it will print out messages. The important bit of output is:
 
    Found USB device
    BootROM code: 2.12
    Part ID: 0x0402FF25 (LPC2148, 512k Flash, 32k+8k RAM)
    BootLoader version: 1.3
 
Which confirms that your device has the bootloader functioning...
 
== Installing the tunnel for direct access to the GPS ==
 
This completely replaces the normal autopilot code (leaving the USB bootloader intact) with a simple serial-to-serial pass-thru that essentially connects the GPS serial port directly to the modem serial port or a USB-to-serial connection that creates a USB serial port that goes to GPS port or modem port. Use this only to gain direct access to the GPS for testing/configuration with [[GPS#GPS_configuration_using_U-Center|U-Center]] or other software.
 
You have to add the tunnel targets to your airframe file if you want to use them:
  <firmware name="setup">
    <target name="tunnel" board="twog_1.0" />
    <target name="usb_tunnel_0" board="twog_1.0" />
  </firmware>
 
==== UART tunnel ====
 
Use this if you have a serial cable to connect. The LEDs will blink when data is transferred. Type the following command from your paparazzi folder, substituting the name of your airframe and paying attention to case sensitivity:
make AIRCRAFT=''myplane'' tunnel.upload
Connect the USB cable and power on the autopilot to receive the code.
 
This can be done without the USB bootloader by appending ''FLASH_MODE=ISP'' to the command line (specifying ISP serial loading).  This will require a serial cable connection (i.e. FTDI USB-to-TTL). '''WARNING!''' Installing tunnel code with the ISP method will erase any USB bootloader code. Make sure you are able to install a bootloader yourself.
 
==== USB tunnel ====
 
This can be done without a serial cable just by having USB. The LEDs will blink when data is transferred. It can connect to either serial port on the autopilot (for Tiny 2.11: uart0=gps, uart1=modem). To connect USB to the gps type the following command from your paparazzi folder, substituting the name of your airframe and paying attention to case sensitivity:
make AIRCRAFT=''myplane'' usb_tunnel_0.upload
Connect the usb cable and power on the autopilot to receive the code. The code will switch the USB to emulate a serial port that you can access at '''/dev/ttyACMx'''. Windows user can extract the usbser.sys file from .cab file in C:\WINDOWS\Driver Cache\i386 and store it somewhere (C:\temp is a good place) along with the [[Media:Usbser.zip|usbser.inf]] file. Windows then creates an extra COMx port that you can use in a terminal program or with ucenter.
To use the USB tunnel make sure you first power the autopilot before connecting USB not to end up in the USB bootloader.
 
== Firmware Architecture ==
More info on the firmware architecture <br>
[[FirmwareArchitecture]]
 
[[Category:Software]] [[Category:User_Documentation]] [[Category:Developer_Documentation]]

Latest revision as of 08:33, 7 February 2013

Redirect to:

Retrieved from "http://wiki.paparazziuav.org/w/index.php?title=Compiling&oldid=14371"