paparazzi-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Paparazzi-devel] olimex stm32f405 bootloader strange behaviour


From: Chris
Subject: Re: [Paparazzi-devel] olimex stm32f405 bootloader strange behaviour
Date: Tue, 04 Nov 2014 21:23:50 +0200
User-agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.2.0

Hi Heinrich.
That is correct.
I will make some more pcbs with the new layout so i can avoid the problem by not powering the modem and the gps from the usb power line but from the servo bec (after the modems and gps i use are all 5v), there are not many ways the 64 pin packaged stm32f405 can be wired....
Chris


On 11/04/2014 07:18 PM, Prof. Dr.-Ing. Heinrich Warmers wrote:
Hi Chris,
i have the olimex stm32f405 with apogee software  the running.
First you have to make  changes for the other  oscillator frequency the get the correct baud rate of the UARTs.
Without this changes the time base has an error of the factor 2.
The resonator frequency is 8 MHz. the apogee has an 16 MHz one.
in apogee_1.0.h EXT_CLK  8 000 000.
I add a  push button switch  which set 3.3V to right (in the layout)  pad of  R1  BOOT0  and the pad below R1  (3.3V).
By pressing the push button  the ollimex boot with the DFU-USB.
I made my test without a connection of the GPS-Module and used TX6 and RX6 for telemetry.
Also the paparazzi discovery software was running .


Regards
Heinrich





 

push button switch


Chris schrieb:
Hi.
I came across a strange problem while experimenting with the olimex stm32f405 board.
When nothing is connected to the board everything works fine and the dfu-util uploads the code.
As soon as i try to upload the code but with the gps connected (obviously powered from the usb +5v)
dfu-util cannot find  the bootloader and more importand the dmesg command shows that the usb device cannot be enumerated.
Now either the gps (ublox NEO7) with active antenna and superb sensitivity is jamming the usb signals via
the usb power line or something else is happening.
I will try with another gps also but i thought that maybe someone has encountered this behaviour also.
The discovery board does not have this problem with the same gps but i will test it again just to be sure
as i haven't seen anything like this before (i also changed the gps uart in the airframe file and it still does it)
Chris


_______________________________________________
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


reply via email to

[Prev in Thread] Current Thread [Next in Thread]