invalid dfuse address for Black magic probe

Post Reply
dev
Posts: 62
Joined: Sun Feb 19, 2017 8:41 am

invalid dfuse address for Black magic probe

Post by dev » Wed Sep 20, 2017 6:55 pm

Hi,
I was trying to flash flash magic probe to stm32f103c8t6. i succeed till some point. I was able to falsh dfu binary. But later dfu is not accepting black magic probe's firmware. I refered http://www.stm32duino.com/viewtopic.php?f=37&t=122 and https://medium.com/@paramaggarwal/conve ... 13cf2cc38c

Here dfu flashed successfully.

Code: Select all

phob@ubuntu:~/blackmagic$ python stm32loader.py -p /dev/ttyUSB0 -e -w -v src/blackmagic_dfu.bin
Bootloader version 22
Chip id: 0x410 (STM32 Medium-density)
Write 256 bytes at 0x8000000
Write 256 bytes at 0x8000100
Write 256 bytes at 0x8000200
Write 256 bytes at 0x8000300
Write 256 bytes at 0x8000400
Write 256 bytes at 0x8000500
Write 256 bytes at 0x8000600
Write 256 bytes at 0x8000700
Write 256 bytes at 0x8000800
Write 256 bytes at 0x8000900
Write 256 bytes at 0x8000A00
Write 256 bytes at 0x8000B00
Write 256 bytes at 0x8000C00
Write 256 bytes at 0x8000D00
Write 256 bytes at 0x8000E00
Write 256 bytes at 0x8000F00
Write 256 bytes at 0x8001000
Write 256 bytes at 0x8001100
Write 256 bytes at 0x8001200
Write 256 bytes at 0x8001300
Write 256 bytes at 0x8001400
Write 256 bytes at 0x8001500
Write 256 bytes at 0x8001600
Write 256 bytes at 0x8001700
Write 256 bytes at 0x8001800
Write 256 bytes at 0x8001900
Write 256 bytes at 0x8001A00
Read 256 bytes at 0x8000000
Read 256 bytes at 0x8000100
Read 256 bytes at 0x8000200
Read 256 bytes at 0x8000300
Read 256 bytes at 0x8000400
Read 256 bytes at 0x8000500
Read 256 bytes at 0x8000600
Read 256 bytes at 0x8000700
Read 256 bytes at 0x8000800
Read 256 bytes at 0x8000900
Read 256 bytes at 0x8000A00
Read 256 bytes at 0x8000B00
Read 256 bytes at 0x8000C00
Read 256 bytes at 0x8000D00
Read 256 bytes at 0x8000E00
Read 256 bytes at 0x8000F00
Read 256 bytes at 0x8001000
Read 256 bytes at 0x8001100
Read 256 bytes at 0x8001200
Read 256 bytes at 0x8001300
Read 256 bytes at 0x8001400
Read 256 bytes at 0x8001500
Read 256 bytes at 0x8001600
Read 256 bytes at 0x8001700
Read 256 bytes at 0x8001800
Read 256 bytes at 0x8001900
Read 256 bytes at 0x8001A00
Verification OK
Windows recognized as follows.
Capture.JPG
Capture.JPG (22.71 KiB) Viewed 263 times
later i tried to flash probe's binary i got error as invalid dfuse address: 0x08002000:leave

here some steps i followed

Code: Select all

phob@ubuntu:~/blackmagic$ dfu-util -d 1d50:6018,:6017 -s 0x08002000:leave -D blackmagic.bin
invalid dfuse address: 0x08002000:leave

phob@ubuntu:~/blackmagic/src$ sudo dfu-util -d 1d50:6018,:6017 -s 0x08002000 -D blackmagic.bin
dfu-util 0.5

(C) 2005-2008 by Weston Schmidt, Harald Welte and OpenMoko Inc.
(C) 2010-2011 Tormod Volden (DfuSe support)
This program is Free Software and has ABSOLUTELY NO WARRANTY

dfu-util does currently only support DFU version 1.0

Filter on vendor = 0x1d50 product = 0x6018
No DFU capable USB device found
For other USB CDC code USB is detecting properly. So, i think USB is working properly.

User avatar
RogerClark
Posts: 7179
Joined: Mon Apr 27, 2015 10:36 am
Location: Melbourne, Australia
Contact:

Re: invalid dfuse address for Black magic probe

Post by RogerClark » Wed Sep 20, 2017 9:13 pm

Blacksphere do support via their Gitter chatroom, and via github issues.

You should post your question there

dev
Posts: 62
Joined: Sun Feb 19, 2017 8:41 am

Re: invalid dfuse address for Black magic probe

Post by dev » Thu Sep 21, 2017 4:29 am

Thanks. Now, I have posted there also.
I searched on web but look like i am the only one who got this DFU's error state. :(

I am not sure what i did wrong.
I install toolchain and properly veriosn is

Code: Select all

arm-none-eabi-gcc (GNU Tools for ARM Embedded Processors 6-2017-q2-update) 6.3.1 20170620 (release) [ARM/embedded-6-branch revision 249437]
Copyright (C) 2016 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
.

I am trying to figure out where i am wrong while compiling or while flashing pill.

User avatar
RogerClark
Posts: 7179
Joined: Mon Apr 27, 2015 10:36 am
Location: Melbourne, Australia
Contact:

Re: invalid dfuse address for Black magic probe

Post by RogerClark » Thu Sep 21, 2017 4:36 am

DFU has nothing to do with the ARM toolchain

Its to do with the version of DFU and Windows driver you have installed and associated with the device (BMP DFU USB device)

dev
Posts: 62
Joined: Sun Feb 19, 2017 8:41 am

Re: invalid dfuse address for Black magic probe

Post by dev » Thu Sep 21, 2017 4:43 am

okay. Is that mean i should use older DFU's source code?

I am using windows 10 host and ubuntu 14 in vmware.

User avatar
RogerClark
Posts: 7179
Joined: Mon Apr 27, 2015 10:36 am
Location: Melbourne, Australia
Contact:

Re: invalid dfuse address for Black magic probe

Post by RogerClark » Thu Sep 21, 2017 6:18 am

Umm

You mean you recompiled and DFU no longer works ?

If you had a really old version of BMP then upgraded it, they totally changed the way the DFU works. But AFIK they changed it ages ago (perhaps a year ago)

I think you'll need Gareth @ Blacksphere to help you with this.

flodejr
Posts: 29
Joined: Sat Sep 16, 2017 2:46 pm

Re: invalid dfuse address for Black magic probe

Post by flodejr » Mon Sep 25, 2017 5:58 am

Install Zadig, http://zadig.akeo.ie/ and change your driver to libk.

dev
Posts: 62
Joined: Sun Feb 19, 2017 8:41 am

Re: invalid dfuse address for Black magic probe

Post by dev » Mon Sep 25, 2017 3:55 pm

I flashed successfully. But target is not getting detect now. Here are few things i tried.

Code: Select all

(gdb) 
(gdb) monitor
Black Magic Probe (Firmware v1.6-rc0-213-gdf7ad91) (Hardware Version 0)
Copyright (C) 2015  Black Sphere Technologies Ltd.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>

monitor swdp_scan
Target voltage: unknown
SW-DP scan failed!
(gdb) monitor jtag_scan
Target voltage: unknown
JTAG device scan failed!
I tried PINS as PB13 and PB14 for target SWCLK and SWDIO respectively.

Code: Select all

pins         Function            Result
PB13        SWCLK               Fail
PB14        SWDIO               Fail
PA4          SWDIO               Fail
PA5          SWCLK               Fail
I could use the serial functionality on PA2/PA3 pins. that means controller and gdb is working.

Is there other pins config's which can be used to connect target.

Post Reply