If you can get on irc, #openocd on irc.freenode.org has a few helpful people :) You can even join in on #libopencm3 too!
fwiw, I'm about 99.9% sure you need a newer openocd than 0.8.0 release to get L0 support. I was using openocd with a ~3 days old build from git, which worked fine (some warnings I've spoken to PaulF about, but flashed ok) I've not tried anything on the f0 board yet. Cheers, Karl P On 11/18/2014 09:15 PM, Chuck McManis wrote: > So while I wait for Sparkfun to approve my ability to post on the OpenOCD > forums, a bit more work here on the openocd front. > > If I tweak my config to just this: > > #source [find board/st_nucleo_f030r8.cfg] > > interface hla > hla_layout stlink > hla_device_desc "ST-Link/V2-1" > hla_vid_pid 0x0483 0x374b > transport select hla_swd > > I get the error BUG: current_target out of bounds > > The support in OpenOCD seems to be for the f0 not the l0 and the difference is > that the l0 does *not* support jtag over its hla port. And telling it to pick > hla_swd gets me this error. > > --Chuck > > > > On Tue, Nov 18, 2014 at 8:41 AM, Chuck McManis <[email protected] > <mailto:[email protected]>> wrote: > > This is the issue I see with OpenOCD (and I see it on both the Nucleo > board > and the L0 discovery board) > > cmcmanis@charliehorse:~$ openocd > Open On-Chip Debugger 0.8.0 (2014-11-16-21:54) > Licensed under GNU GPL v2 > For bug reports, read > http://openocd.sourceforge.net/doc/doxygen/bugs.html > srst_only separate srst_nogate srst_open_drain connect_deassert_srst > Info : This adapter doesn't support configurable speed > Info : STLINK v2 JTAG v21 API v2 SWIM v5 VID 0x0483 PID 0x374B > Info : using stlink api v2 > Info : Target voltage: 3.225246 > Error: hl_interface_init_target: target not found: idcode: 0x0bc11477 > in procedure 'transport' > in procedure 'init' > cmcmanis@charliehorse:~$ > > > This is the the latest source built and running, my udev rules identify > the > v2.1-1 boards > *# STlink > ATTRS{idVendor}=="0483", ATTRS{idProduct}=="374b", MODE="666", > GROUP="plugdev" > > * > My openocd.cfg has > > *source [find board/st_nucleo_f030r8.cfg]* > > That does the standard things of > find interface/stlink-v2-1.cfg > find target stm32f0x_stlink.cfg > > And everything reads like that should be "it" but it doesn't work. > > Looking through the long -d3 listing from openocd gives lots of detail > and a > very helpful bit about how successful it is in setting up the hla_swd > interface, I have attached that as well. > > Frankly I would love it or my BMP probe to work on these boards but > neither > do (I expect I could get the BMP to work if I could disable the debug > processor a bit more.) > > --Chuck > > > > On Tue, Nov 18, 2014 at 1:21 AM, Paul Fertser <[email protected] > <mailto:[email protected]>> wrote: > > On Mon, Nov 17, 2014 at 07:53:59PM -0800, Chuck McManis wrote: > > The OpenOCD stuff still doesn't work but I suspect it is also an > > f0/l0 issue. Its possible ST is using the CMSIS-DAP profile for > > these things, I just know they aren't recognized. > > AFAICT, ST never shipped any CMSIS-DAP comliant adapter. Also, OpenOCD > is actually able to work with CMSIS-DAP by other vendors. > > Also, Karl has tested his L0 board yesterday and the only issue > noticed so far was ramping up PLL proc that's specific to L1 parts. > > -- > Be free, use free (http://www.gnu.org/philosophy/free-sw.html) > software! > mailto:[email protected] <mailto:[email protected]> > > > ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk _______________________________________________ libopencm3-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libopencm3-devel
