|
From: Craig Y. <cyo...@gm...> - 2015-12-29 19:29:08
|
Ron, Use pastebin or gist to show output with -d3 flag to openocd and lsusb -vvv. I am unfamiliar with your device but this will help others. Craig Younkins On Tue, Dec 29, 2015 at 2:21 PM, Ron Garret <ro...@fl...> wrote: > I got openocd 0.9.0-rc1 to build on ubuntu (14.04) thanks to Craig > Younkins. AFAICT the build went smoothly. Unfortunately, it doesn’t > actually work. > > For the record, the reason I even tried to build 0.9.0 is that 0.7.0 (the > standard Ubuntu package) fails as follows: > > ron@ubuntu1:~$ /usr/bin/openocd -f stm32f3x.cfg > Open On-Chip Debugger 0.7.0 (2013-10-22-08:31) > Licensed under GNU GPL v2 > For bug reports, read > http://openocd.sourceforge.net/doc/doxygen/bugs.html > Warn : Interface already configured, ignoring > Error: already specified hl_layout stlink > Error: session's transport is already selected. > Runtime Error: embedded:startup.tcl:20: > in procedure 'script' > at file "embedded:startup.tcl", line 58 > at file "stm32f3x.cfg", line 5 > in procedure 'transport' called at file "stm32f3x.cfg", line 4 > in procedure 'ocd_bouncer' > at file "embedded:startup.tcl", line 20 > > 0.9.0 fails in a similar but more spectacular fashion. It produces 7962 > lines of error messages, starting with: > > Open On-Chip Debugger 0.9.0-rc1 (2015-12-29-11:05) > Licensed under GNU GPL v2 > For bug reports, read > http://openocd.org/doc/doxygen/bugs.html > Warn : Interface already configured, ignoring > Error: already specified hl_layout stlink > Warn : Transport "hla_swd" was already selected > Warn : Interface already configured, ignoring > Error: already specified hl_layout stlink > Warn : Transport "hla_swd" was already selected > > That repeats a few thousand times. It then transitions: > > Warn : Transport "hla_swd" was already selected > Warn : Interface already configured, ignoring > Error: already specified hl_layout stlink > Warn : Transport "hla_swd" was already selected > interface/stlink-v2.cfg:5: Error: > in procedure 'script' > at file "embedded:startup.tcl", line 60 > at file "stm32f3x.cfg", line 5 > at file "stm32f3x.cfg", line 5 > > That repeats a few thousand more times, and then it finally ends with: > > at file "stm32f3x.cfg", line 3 > in procedure 'interface' called at file "interface/stlink-v2.cfg", line 5 > > The config files look like this: > > ron@ubuntu1:~$ more stm32f3x.cfg > #transport select hla_swd > > source [find interface/stlink-v2.cfg] > transport select hla_swd > source [find stm32f3x.cfg] > > #reset_config srst_only > ron@ubuntu1:~$ more interface/stlink-v2.cfg > # > # STMicroelectronics ST-LINK/V2 in-circuit debugger/programmer > # > > interface hla > hla_layout stlink > hla_device_desc "ST-LINK/V2" > hla_vid_pid 0x0483 0x3748 > > # Optionally specify the serial number of ST-LINK/V2 usb device. > ST-LINK/V2 > # devices seem to have serial numbers with unreadable characters. > ST-LINK/V2 > # firmware version >= V2.J21.S4 recommended to avoid issues with adapter > serial > # number reset issues. > # eg. > #hla_serial "\xaa\xbc\x6e\x06\x50\x75\xff\x55\x17\x42\x19\x3f” > > FWIW, the hardware seems to be working: > > ron@ubuntu1:~$ lsusb > ... > Bus 002 Device 008: ID 0483:3748 STMicroelectronics ST-LINK/V2 > > Again, suggestions on how to proceed would be much appreciated. > > Thanks, > rg > > |