Il 15/06/2016 10:26, Andreas Fritiofson ha scritto:
On Wed, Jun 15, 2016 at 10:15 AM, Lorenzo Corti <[email protected]
<mailto:[email protected]>> wrote:
Hello,
I tried with the GDB debugger and seems to work.
How is possible, instead, that the command write flash of openOCD
doesn't work?
Hi,
When GDB loads, a default hook calls "reset init" to get the target
into a well defined state and prepare clocks for faster programming.
If you flash "manually", you should make sure to have called "reset
init" yourself. Then it should be equivalent.
/Andreas
Hello,
i tried with the stm32f7discovery board with the following command and
unsuccess:
openocd -f board/stm32f7discovery.cfg -c "init; targets; reset init;
wait_halt; poll; flash write_image erase unlock
Debug-MB1191B-0/LCDTest.elf; flash erase_check 0; reset run; shutdown"
Open On-Chip Debugger 0.10.0-dev-00321-gd4b7cbf (2016-05-31-10:18)
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
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 v24 API v2 SWIM v11 VID 0x0483 PID 0x374B
Info : using stlink api v2
Info : Target voltage: 3.219934
Warn : Silicon bug: single stepping will enter pending exception handler!
Info : stm32f7x.cpu: hardware has 8 breakpoints, 4 watchpoints
TargetName Type Endian TapName State
-- ------------------ ---------- ------ ------------------ ------------
0* stm32f7x.cpu hla_target little stm32f7x.cpu halted
stm32f7x.cpu: target state: halted
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0xfffffffe msp: 0xfffffffc
background polling: on
TAP: stm32f7x.cpu (enabled)
stm32f7x.cpu: target state: halted
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0xfffffffe msp: 0xfffffffc
auto erase enabled
auto unlock enabled
Info : device id = 0x10016449
Info : flash size = 1024kbytes
Error: timed out while waiting for target halted
stm32f7x.cpu: target state: halted
target halted due to debug-request, current mode: Handler HardFault
xPSR: 0x01000003 pc: 0xfffffffe msp: 0xffffffd8
Error: error waiting for target flash write algorithm
Error: error writing to flash at address 0x08000000 at offset 0x00000000
--
*Lorenzo Corti* | Ricerca e Sviluppo
*Eurek s.r.l. *Via Celletta 8/b | 40026 Imola (BO) - Italy | +39 *0542
609120*
[email protected] <mailto:[email protected]> | www.eurek.it
<http://www.eurek.it/>
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://pubads.g.doubleclick.net/gampad/clk?id=1444514421&iu=/41014381
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
