Re: Re: [Paparazzi-devel] USB Flashing

[Alexis Lussier Desbiens]

That is interesting Anton...

I am now using the "make upload_bl PROC=AP" to program the AP chip on
my Classix. Referring to the file crt.S, it is using P0.03 pin which
is usually used for I2C_SDA. This suck as I was planning to use the
I2C bus... and now that pin need to be connected to ground for the
autopilot to boot... (and if there is a "random reset" during flight
it might not reboot the autopilot software but wait for the code to be
downloaded).

Furthermore I am not sure why, but I am getting the "Broken Pipe"
error message again using this pin...

Is there a version of the Classix PCB that has the P0.23 pin connected?

     Alexis

On 9/18/07, address@hidden <address@hidden> wrote:
>
> if you just used the command make upload_bl then it defaulted the reset pin
> to P0.23,  There is a way to change the pin, by saying PROC=""   This is
> located somewhere in /sw/airborne/arm7/   I think the file is called
> cts.something.
>
> Anton
>
>
>
>
> -------- Original Message --------
> Subject: Re: Re: [Paparazzi-devel] USB Flashing
> From: "Alexis Lussier Desbiens"
> <address@hidden>
> Date: Tue, September 18, 2007 11:00 am
> To: address@hidden
>
> > Yes. The very first lines of the bootloader code need to know if it
> > should run the ap or bootloader software. That is done by a pin. Either
> > P0.23 or any other (if bootloader is changed). You might want to use a
> > voltage divider as seen on the Tiny board - the LPC should be 5V proof
> > but this USB_Vbus voltage is there at least for a short time while the
> > LPC is not powered by 3.3V.
> >
> > > Is it normal that the LED are not always flashing after a
> > > power down? I would expect that once the board is flashed you don't
> > > always need to reprogram it?
> >
> > You need to program only once. But if P0.23 is floating - so is the
> > decision between ap and bootloader. Maybe the "Broken pipe" error
> > message at the end of download is also related to that floating pin.
> >
> > Anyone else using the Classix without P0.23 connected?
>
> Connecting P0.23 to the USB_Vbus solved the "Broken pipe" problem and
> the random bootup... it wasn't easy to access P0.23 (it isn't
> connected to anything on the Classix) and it is a little bit annoying
> not having it in the connector!
>
> You are talking about a version of the board that has the P0.23
> included in the serial connector! I can't find it, could you show me
> where it is?
>
> Would it be possible to use P0.14? I guess not, because it is used to
> program the USB bootloader...
>
> Alexis
>
>
> _______________________________________________
> Paparazzi-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>
> _______________________________________________
> Paparazzi-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>
>


-- 
http://mecano.gme.usherb.ca/~alussierdesbiens
"De' remi facemmo ali"