Error Flashing Custom Firmware

Discussion related to "under the hood" OpenMV topics.
SP097
Posts: 17
Joined: Fri Jan 26, 2018 12:09 am

Error Flashing Custom Firmware

Postby SP097 » Sat Feb 03, 2018 6:36 am

Hi,
I wanted to play around with the firmware on my OpenMV CAM M7 board and also learn more about STM32 through it.
I have a simple test project that I created on the System Workbench for STM32 that builds fine. I have also created custom board settings
to match the OpenMV I have so that I can flash it through SWD using an ST-Link programmer. Following are the connections I made
STLINKV2----OpenMV 5 Pin Header
GND--------GND
3.3V--------3.3V
SWDIO------SWD
SWCLK------SWC

I have tried programming it with Boot and RST both shorted and un-shorted.
When I attempt to program/debug it I get the following list of errors:

Code: Select all

Open On-Chip Debugger 0.10.0-dev-00007-g58350bc-dirty (2018-01-12-12:21)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
srst_only separate srst_nogate srst_open_drain connect_assert_srst
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
adapter_nsrst_delay: 100
adapter speed: 1800 kHz
Info : tcl server disabled
Info : telnet server disabled
Info : clock speed 1800 kHz
Info : STLINK v2 JTAG v17 API v2 SWIM v4 VID 0x0483 PID 0x3748
Info : vid/pid are not identical: 0x0483/0x374B 0x0483/0x3748
Info : using stlink api v2
Info : Target voltage: 3.226877
Info : STM32F765VITx.cpu: hardware has 8 breakpoints, 4 watchpoints
Info : accepting 'gdb' connection on tcp/3333
adapter speed: 1800 kHz
Error: timed out while waiting for target halted
TARGET: STM32F765VITx.cpu - Not halted
in procedure 'reset' 
in procedure 'ocd_bouncer'



Info : flash size probed value 2048
Info : flash size probed value 2048
adapter speed: 1800 kHz
Error: timed out while waiting for target halted
TARGET: STM32F765VITx.cpu - Not halted
in procedure 'reset' 
in procedure 'ocd_bouncer'


adapter speed: 1800 kHz
Error: timed out while waiting for target halted
TARGET: STM32F765VITx.cpu - Not halted
in procedure 'reset' 
in procedure 'ocd_bouncer'



Error: failed erasing sectors 0 to 0
Error: flash_erase returned -304
shutdown command invoked
User avatar
iabdalkader
Posts: 526
Joined: Sun May 24, 2015 3:53 pm

Re: Error Flashing Custom Firmware

Postby iabdalkader » Sat Feb 03, 2018 7:20 am

Hi, try connecting NRST to RST pin.
fred
Posts: 3
Joined: Fri Mar 09, 2018 10:55 am

Re: Error Flashing Custom Firmware

Postby fred » Fri Mar 09, 2018 11:01 am

Hi,
did you get it to work?
I'm trying to do the same thing. Did you create a special openocd config file? This is where I'm stuck:

Code: Select all

GNU MCU Eclipse 64-bits Open On-Chip Debugger 0.10.0+dev-00404-g20463c28 (2018-01-23-12:30)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
adapter speed: 2000 kHz
adapter_nsrst_delay: 100
srst_only separate srst_nogate srst_open_drain connect_deassert_srst
Started by GNU MCU Eclipse
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : Unable to match requested speed 2000 kHz, using 1800 kHz
Info : Unable to match requested speed 2000 kHz, using 1800 kHz
Info : clock speed 1800 kHz
Info : STLINK v2 JTAG v30 API v2 SWIM v7 VID 0x0483 PID 0x3748
Info : using stlink api v2
Info : Target voltage: 3.253616
Info : stm32f7x.cpu: hardware has 127 breakpoints, 15 watchpoints
Info : Listening on port 3333 for gdb connections
Info : accepting 'gdb' connection on tcp/3333
Info : device id = 0xffffffff
Warn : Cannot identify target as a STM32 family.
Error: auto_probe failed
Error: Connect failed. Consider setting up a gdb-attach event for the target to prepare target for GDB connect, or use 'gdb_memory_map disable'.
Error: attempted 'gdb' connection rejected
User avatar
kwagyeman
Posts: 2205
Joined: Sun May 24, 2015 2:10 pm

Re: Error Flashing Custom Firmware

Postby kwagyeman » Fri Mar 09, 2018 11:15 am

Does the debugger support the F7 MCU series? We wrote our own custom SWD programming firmware to load the STM32F7 chips. I have to go used the jlink.
Nyamekye,
fred
Posts: 3
Joined: Fri Mar 09, 2018 10:55 am

Re: Error Flashing Custom Firmware

Postby fred » Fri Mar 09, 2018 12:15 pm

I dont have a jlink segger, so I'm using a cheap st-link v2 usb debugger.
I am able to connect to the board using the st-link utility. But so far no luck with openocd.
fred
Posts: 3
Joined: Fri Mar 09, 2018 10:55 am

Re: Error Flashing Custom Firmware

Postby fred » Tue Mar 13, 2018 1:49 pm

I got it to work by flashing the blackmagic firmware onto my ST-Link V2 clone debugger (which essentially converts it into a black magic probe). No OpenOCD or texane needed.

Return to “Technical Discussion”

Who is online

Users browsing this forum: Bing [Bot] and 6 guests