Re: Re: [Paparazzi-devel] Problems with USB Programmer

[David Conger]

Hello,

Zico, you're in good hands here. Whatever is I am confident it's going  
to be quickly solved. If not I guarantee the boards and will replace it.

A note on "testing" by PPZUAV. I'll use a Tiny2.11 that's purchased  
alone (i.e. not a bundle that includes at  Tiny2.11)

Steps in order (From memory I have done this 100s of times now):
1) I use a micro-deans connector that pushes easily into the holes on  
the PCB and gives me two posts to connect via jumpers to a current  
limited power supply. I can power up the board without risk of damage  
this way and measure the current draw. A new Tiny2.11 should draw a  
specific current at first power up.
2) I connect a "download" connector (7-pin to FTDI cable) to the  
download port (And now connecting the FTDI adapter and computer)
3) I connect a USB programming cable (8-pin to mini-USB) to the USB  
port (leaving open not connected yet to USB on the computer)
4) Connect a serial to FTDI cable to the "serial" connector (leaving  
open not connected to the FTDI adapter yet)
5) Connect a jumper wire from ground to pin4 "boot" pin (P014 on the  
LPC) using a test hole found nearby the download connector
6) Power up the board with 6 to 11v (doesn't seem to matter)
7) make sure the current draw is .04A steady after about 3sec  
(Sometimes it takes a second or two to drop to .04A). That .04A is  
important. It tells me the LCP is in programming mode and ready to  
flash the bootloader code
8) I send the bootloader code command found on the Wiki (takes about 7  
seconds)
9) I remove the jumper and disconnect the "download" connector and  
FTDI adapter board
10) I now connect USB to the USB cable (step 3 above)...
11) I power up again and issue the command to load the "Tunnel" (found  
on the Wiki)
12) I power down
13) I connect the FTDI board to the serial cable in preparation to use  
u-center (in WIndows) to program the GPS Module
14) I power up the board and start u-center
15) I set the speed in u-center to 115k and send it to the GPS module
16) I send the latest firmware from u-blox to the GPS Module
17) I send the GPS configuration file to the GPS module (same one off  
the Wiki for LEA-5H)
18) I wait for a 3D position fix (can take a long time so I let it sit  
until the fix is had)
19) I power down
20) I disconnect the FTDI adapter board from the serial cable
21) I connect the USB to the USB adapter
22) I power up after launching "paparazzi" software
23) I select the Tiny2.11 demo program (variant of funjet1.xml for  
LEA-5H and Tiny2.11)
24) I upload the demo program
25) I verify the board resets and disconnect the USB
26) I now connect the FTDI board again to serial
27) I usually reset the board (power off and back on)
28) I now launch GCS (Execute)
29) I now check GPS is seeing satellites and a 3D fix is made

NOTES: If this is a part of a bundle I now plug in the IR sensors and  
use the "messages" and my finger to test the thermopiles and sensor  
boards are seeing + and - reading in the expected range. I also if you  
have XBee  2.4ghz program one as the CONTROLLER and the other as END  
DEVICE so they are plug and play...there's a bunch more depending on  
the bundle....

So, you may order just a single Tiny2.11 and it comes in a sealed bag  
and no power connector is connected so it looks like it was just  
assembled. However, now you know it has power up and has been run for  
at least 20min - 60min and should be completely ready to go. I have  
never heard of an autopilot "on the edge" they either work or don't  
because of the very simple design. If something is off/on again it's  
usually the setup in the laptop or a faulty cable or something adding  
that bit of uncertainty. Just my experience so far.

If anyone has a cable or board that's faulty and are uncomfortable  
repairing it please, send it back, I just in about 5min replaced a  
customers Power supply on a Tiny2.11 for them (I only charge for parts  
costs if it's clear the board was mis-handled ... in this case power  
reversed and large caps were blown along with the power supply). For  
this person (and anyone) I have soldered for them a polarized micro- 
deans onto the board to avoid this accident in the future. Total cost  
for the caps and deans and power supply will be about 25.00.

I am confident if you got the Tiny2.11 from me it's going to be  
something easily resolved. Feel free to email me directly as well  
anytime.

Best Regards,
David Conger

On Jul 9, 2009, at 2:37 PM, Zico Kolter wrote:

> Hey,
> We just got a Tiny 2.11 board (from PPZUAV), and are having some  
> issues
> right off the bat.  It appears that my computer (and several others  
> I've
> tried) isn't recognizing the USB programming cable.  When we try to
> upload a configuration to the Tiny 2.11, the Paparazzi center program
> outputs "no USB device." It seems like the USB port just isn't being
> recognized; dmesg gives the following output after turning on the Tiny
> with the USB cable connected:
>
> [ 8504.168149] usb 3-1: new full speed USB device using uhci_hcd and
> address 15
> [ 8504.288155] usb 3-1: device descriptor read/64, error -71
> [ 8504.512239] usb 3-1: device descriptor read/64, error -71
> [ 8504.728154] usb 3-1: new full speed USB device using uhci_hcd and
> address 16
> [ 8504.848132] usb 3-1: device descriptor read/64, error -71
> [ 8505.072149] usb 3-1: device descriptor read/64, error -71
> [ 8505.288139] usb 3-1: new full speed USB device using uhci_hcd and
> address 17
> [ 8505.700105] usb 3-1: device not accepting address 17, error -71
> [ 8505.812212] usb 3-1: new full speed USB device using uhci_hcd and
> address 18
> [ 8506.224081] usb 3-1: device not accepting address 18, error -71
> [ 8506.224125] hub 3-0:1.0: unable to enumerate USB device on port 1
>
> Has anyone seen this or something similar?
>
> Thanks!
> Zico
>
>
>
> _______________________________________________
> Paparazzi-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel