In the latter case, you use some weird custom scripts containing the
old soft_reset_halt
command. None of the stock cortex_m configs contain that command. Make sure
you're not sourcing some old scripts.
The first case seems to use the stock configs only, good. But it still
fails. Are you saying GDB can load with the same setup but not from command
line?
Didn't you say you had some corrupted option bytes on the target that
failed programming? Have you restored them? Or do they keep getting
corrupt? Especially the HW IWDG option can/will interfere with the flashing
algorithm. I suspect the "unlock" argument if the option bytes get
corrupted by OpenOCD. That step is not performed as part of GDB load.
Perhaps write (un-)protection is not supported for the F7, Uwe?
By the way, for flashing from the command line, use the "program" script.
E.g.
openocd -f board/stm32f7discovery.cfg -c
"program Debug-MB1191B-0/LCDTest.elf verify reset exit"
/Andreas
------------------------------------------------------------------------------
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
