paparazzi-devel
[Top][All Lists]
Advanced

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

Re: [Paparazzi-devel] Stm32f4 discovery dfu problem


From: Chris
Subject: Re: [Paparazzi-devel] Stm32f4 discovery dfu problem
Date: Thu, 13 Mar 2014 15:37:58 +0200
User-agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.3.0

That was what  i was afraid of because they used a lcd without internal ram and controller.
In my earlier life i became proficient with character lcd screens i may try to interface a light unit to the discovery board for general on the fly  paparazzi config options, all i need are 4 io pins.
Chris

On 03/13/2014 02:11 PM, Marius Pfeffer wrote:

Hello

I bought the stm32f429 discovery (I finally donated it to a guy from the mailing list). The problem ist that most pins are used for the lcd and external ram.
If we want to use this, we would need to remove both (lcd and external ram)

Best regards
Marius

Am 13.03.2014 13:02 schrieb "Chris" <address@hidden>:
Hi Heinrich.
Yes i knew that but i had not tried it until now.
The discovery board is really very good.
What about the newer discovery board with the display is it better for our use or not?
Chris


On 03/13/2014 10:15 AM, Prof. Dr.-Ing. Heinrich Warmers wrote:
Hi Chris,
you need only 3 wires to connect  the 2 wire interface of you discovery  PCB  to other  STM 32 processors and open two bridges.
With the discovery pcb you get a debug interface for all stm32  controllers for only 15 euros.
We have tested this also and it works perfect.


Heinrich


Chris schrieb:
I just uploaded the ap firmware using both the dfu-util and the stlink.
I must say that for the discovery board stlink is so much better but the dfu-util is the only way when you have a lonely stm32f4 chip.
Chris


On 03/12/2014 05:21 PM, Felix Ruess wrote:
Hi Chris,

you are trying to use stm32_mem.py to flash the discovery board. It currently doesn't have the stm bootloader in it's recognized devices, since to my knowledge no one tested it with that.
You could either try to specify the "--product any" option or simply use dfu-util instead of stm32_mem.

In latest master STLlink is the default (which should also be more convenient, as you don't have to enter bootloader mode manually first). Otherwise just select DFU-UTIL from the flash mode drop down menu.
See also http://wiki.paparazziuav.org/wiki/STM32F4_Discovery#Firmware_Flashing

Cheers, Felix


On Wed, Mar 12, 2014 at 4:16 PM, Marius Pfeffer <address@hidden> wrote:

What does dfu-util --list output ? You should see the stm32 boards since it is also listed in lsusb.

Am 12.03.2014 16:12 schrieb "Chris" <address@hidden>:

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

Could not find STM32 (autopilot) device.
make[1]: *** [upload] Error 1
make[1]: Leaving directory `/home/hendrix/paparazzi/sw/airborne'
make: *** [ap.upload] Error 2
make: Leaving directory `/home/hendrix/paparazzi'

FAILED 'make -C /home/hendrix/paparazzi -f Makefile.ac AIRCRAFT=x8_discovery  ap.upload' with code 2



On 03/12/2014 04:47 PM, Marius Pfeffer wrote:

Hello

Get well soon ! :)

copied from the wiki:

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

Best regards
Marius

Am 12.03.2014 15:42 schrieb "Chris" <address@hidden>:
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

Could not find STM32 (autopilot) device.
make[1]: *** [upload] Error 1
make[1]: Leaving directory `/home/hendrix/paparazzi/sw/airborne'
make: *** [ap.upload] Error 2
make: Leaving directory `/home/hendrix/paparazzi'

FAILED 'make -C /home/hendrix/paparazzi -f Makefile.ac AIRCRAFT=x8_discovery  ap.upload' with code 2

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$



_______________________________________________
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
          


_______________________________________________
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




_______________________________________________
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


_______________________________________________
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



_______________________________________________
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]