Re: [Paparazzi-devel] Stm32f4 discovery dfu problem
From:
Chris
Subject:
Re: [Paparazzi-devel] Stm32f4 discovery dfu problem
Date:
Wed, 12 Mar 2014 21:12:46 +0200
User-agent:
Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
I just finished testing the max7456 osd integration with the
discovery board and everything works fine he he he
Here is a photo with the discovery as a complete autopilot and a
photo of the daughter board.
I used spi3 for the osd so spi1 is also available.
Marius i tried as hard as i could with my freeware eagle and i think
that now the board is acceptable as it has the same dimensions as
the discovery board, i will send you the files later today.
My head is spinning a bit but overall i am happy.
Chris
On 03/12/2014 05:16 PM, Marius Pfeffer
wrote:
What does dfu-util --list output ? You should see the
stm32 boards since it is also listed in lsusb.
I can get the mcu in
dfu mode but paparazzi center keeps saying :
make[1]: Leaving directory
`/home/hendrix/paparazzi/sw/airborne'
cd sw/airborne; make TARGET=ap upload
Using "arch/stm32/apogee.ld" as ldscript for target "ap".
make[1]: Entering directory
`/home/hendrix/paparazzi/sw/airborne'
Using stm32 mem dfu loader
/usr/bin/python
/home/hendrix/paparazzi/sw/tools/dfu/stm32_mem.py
/home/hendrix/paparazzi/var/x8_discovery/ap/ap.bin
push MCU in DFU mode: connect mini and micro
USB to PC, connect pin BOOT0 with 3V (if it doesnt work
also BOOT1 (PB2) with GND), press reset button(LED LD7
should light up now), disconnect BOOT0 to 3V
I
was a little sick and now i either forgot how to enter
the bootloader mode (upload the ap firmware)
on my stm32f4 discovery board or something is wrong.
The discovery board enters the bootloader mode but
paparazzi center does not see it.
To enter the dfu bootloader i just connect boot1 with
vdd (3v) and the udev rules are copied.
Any ideas?
Here is the Paparazzi center's output in sudo mode
(run as an administrator)
make[1]: Leaving directory
`/home/hendrix/paparazzi/sw/airborne'
cd sw/airborne; make TARGET=ap upload
Using "arch/stm32/apogee.ld" as ldscript for target
"ap".
make[1]: Entering directory
`/home/hendrix/paparazzi/sw/airborne'
Using stm32 mem dfu loader
/usr/bin/python
/home/hendrix/paparazzi/sw/tools/dfu/stm32_mem.py
/home/hendrix/paparazzi/var/x8_discovery/ap/ap.bin
Here is the lsusb output (everything in sudo mode)
address@hidden:~/paparazzi$ sudo lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0
root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0
root hub
Bus 002 Device 036: ID 0483:3748 SGS Thomson
Microelectronics ST-LINK/V2
Bus 001 Device 002: ID 8087:0020 Intel Corp.
Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0020 Intel Corp.
Integrated Rate Matching Hub
Bus 002 Device 003: ID 064e:c107 Suyin Corp. HP webcam
[dv6-1190en]
Bus 002 Device 004: ID 03f0:231d Hewlett-Packard
Bus 002 Device 037: ID 0483:df11 SGS Thomson
Microelectronics STM Device in DFU Mode
here is the dfu-util version
address@hidden:~/paparazzi$ dfu-util -V
dfu-util 0.7
Copyright 2005-2008 Weston Schmidt, Harald Welte and
OpenMoko Inc.
Copyright 2010-2012 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO
WARRANTY
Please report bugs to address@hidden
address@hidden:~/paparazzi$
SDC11121.JPG
final.png