Difference between revisions of "User:Mcurrie"

From PaparazziUAV
Jump to navigation Jump to search
Line 1: Line 1:
Matthew Currie
Matthew Currie


Located in Nanaimo, B.C. Canada
=== Bio ===


Currently building building Tiny 1.1 hardware. Has hot air reflow, solder paste, smt, linux capabilities and keeps stock of some parts on hand. Let me know if anyone needs any assistance.
Location: Nanaimo, British Columbia, Canada
 
Currently building Tiny 1.1 boards in-house for a few group members, including myself.
 
=== TODO / PROGRESS ===
 
'''COMPLETE'''
 
*Compiled / Installed Paparazzi GCS
*Assembled Tiny 1.1 AP w/o GPS or 5V DC-DC
*Installed USB Bootloader onto AP
*Compiled / Installed Airborne Code
*Tested AP --> GCS communications w/o modem
 
'''TODO'''
 
*Source & Purchase L1/L2 Inductors
*Source & Purchase GPS Antennas
*Purchase Molex 1.25mm Crimper
*Assemble Prototyping Wiring Harnesses
*Assemble flying wiring harnesses
 
=== WIKI Contributions ===


'''Q:''' [Tiny 1.1] My AP begins executing only after downloading code to it and not after a reset.
'''Q:''' [Tiny 1.1] My AP begins executing only after downloading code to it and not after a reset.

Revision as of 23:52, 9 December 2006

Matthew Currie

Bio

Location: Nanaimo, British Columbia, Canada

Currently building Tiny 1.1 boards in-house for a few group members, including myself.

TODO / PROGRESS

COMPLETE

  • Compiled / Installed Paparazzi GCS
  • Assembled Tiny 1.1 AP w/o GPS or 5V DC-DC
  • Installed USB Bootloader onto AP
  • Compiled / Installed Airborne Code
  • Tested AP --> GCS communications w/o modem

TODO

  • Source & Purchase L1/L2 Inductors
  • Source & Purchase GPS Antennas
  • Purchase Molex 1.25mm Crimper
  • Assemble Prototyping Wiring Harnesses
  • Assemble flying wiring harnesses

WIKI Contributions

Q: [Tiny 1.1] My AP begins executing only after downloading code to it and not after a reset.

A: Make sure when you compiled your initial USB Bootloader you selected the right USB enable pin. If using P0.23 add PROC=GENERIC to the make process.

Q: [Tiny 1.1] I get error accessing USB when trying to load code to the Autopilot

A: You need to copy a USB rules file following the instructions below

# cd [paparazzi3 folder]
# cp conf/system/udev/rules/10-paparazzi.rules /etc/udev/rules.d/

Q: [Tiny 0.9-1.1] What is the command to compile the ARM7 code?

A: the two relevent commands are below. Replace [AIRCRAFT] with the name of your aircraft.

# cd [parazzi3 folder]'
# make AIRCRAFT=[AIRCRAFT] ap.compile

to download code that has already been compiled

# cd [parazzi3 folder]'
# make AIRCRAFT=[AIRCRAFT] ap.upload

Q: How do I get GCS to talk to the AP with straight serial and not a modem?

A: Here is an example of a section of my paparazzi3/conf/control_panel.xml

<session name="4 Matt Flight">
  <program name="link">
    <arg flag="-d" constant="/dev/ttyUSB0"/>
    <arg flag="-transport" constant="pprz"/>
    <arg flag="-uplink" constant=""/>
  </program>
  <program name="server"/>
  <program name="gcs"/>
</session>

Q: How do I load the USB Bootloader onto the Tiny?

A: Start by wiring up 3.3V RS232 from the PC to the Tiny.

The serial lines on the ARM7 micro are 5V tolerant so if it helps cut down on complexity/parts you could use 5V RS232 for this. Optional: You could also form a basic resistor voltage divider on the PC TX -> AP RX

  • PC SERIAL_TX -> LPC_RXD_0 (SERIAL_1-7)
  • PC SERIAL_RX -> LPC_TXD_0 (SERIAL_1-8)
  • PC SERIAL_GND -> GND (SERIAL_1-1)
  • LPC_P0.14 (SERIAL_1-5) must be asserted low (held to ground) while the Tiny powers up in order to enter the Serial Boot Loader. (You could also wire this to a pushbutton which ties it to ground, holding this button briefly while you power up the AP. This pin does not need to stay low during the programming or any time afterwards)

once these connections have been made, execute this command in a console

# make PROC=GENERIC upload_bl