On 06/16/2016 03:42 PM, Andreas Fritiofson wrote: > > > On Thu, Jun 16, 2016 at 3:24 PM, Lorenzo Corti <[email protected] > <mailto:[email protected]>> wrote: > > > > Now, the biggest issue is: *how the hell is the jtag programming > procedure is not working? WTF*? > > > The corrupted option bytes? Fix them and then avoid the write-protect > features. Or better, fix the write-protection to not destroy the option > bytes. >
But I am using the same command as in stlink, i.e.: -c "program ...." so I suppose that writing flash using stlink or using jtag has different approaches or they do not call the same functions in sequence. Is there a way, a command, just to avoid the changing of the option bytes??? Maybe the jtag function sequence with the 'program' command due differently if using stlink and the option byte there are not corrupted at all. Thank you, -- Eurek s.r.l. | Electronic Engineering | http://www.eurek.it via Celletta 8/B, 40026 Imola, Italy | Phone: +39-(0)542-609120 p.iva 00690621206 - c.f. 04020030377 | Fax: +39-(0)542-609212 ------------------------------------------------------------------------------ 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
