Environment
Attempting to build on Windows 10/MSYS2
- Development Kit: ESP32-C3 mini Devkit
- Module or chip used: ESP32-C3 mini
- Debug Adapter: Built it
- OpenOCD version: Current master branch
- Operating System: Windows
- Using an IDE?: MSYS2
- OpenOCD command line: na
- ESP-IDF version: current master branch
Problem Description
I posted this to the espressif forum but did not get any suggestions. I had previously posted a similar issue but I was not following the most recent instructions.
I have been trying to build a current version of openocd on Windows using the instructions here https://docs.espressif.com/projects/esp-idf/en/latest/esp32c3/api-guides/jtag-debugging/index.html#jtag-debugging-configuring-target
I have tried it multiple times but it fails with
configure: error: libusb-1.x is required for the MPSSE mode of FTDI based devices
even though I downloaded and unzipped libusb-1.x as per the instructions and when I ls I see it is were I think it should be
$ echo $CPPFLAGS
-I/c/Users/bjpic/esp/libusb/include/libusb-1.0 -D__USE_MINGW_ANSI_STDIO=1 -Wno-error
bjpic@LAPTOP-70Q5CT1Q MSYS ~/esp
$ echo $LDFLAGS
-L/c/Users/bjpic/esp/libusb/MinGW32/.libs/dll
bjpic@LAPTOP-70Q5CT1Q MSYS ~/esp
$ ls
buildsetup.bat config.bat examples install.bat libusb-1.0.22.7z openocd-esp32 sdkconfig.ci
CMakeLists.txt example_test.py export.bat libusb Makefile README.md sdkconfig.defaults
Because configure fails I cannot run make. If I run configure without the options (i.e. —disable-doxygen-pdf —enable-ftdi —enable-jlink —enable-ulink —build=i686-w64-mingw32 —host=i686-w64-mingw32) It give me errors because libusb is not found.
I have attached a fill trace of the problem.
I am trying to build the most recent version of openocd because when I try to run it as per https://docs.espressif.com/projects/esp-idf/en/latest/esp32c3/api-guides/jtag-debugging/index.html#jtag-debugging-configuring-target
I get the following
C:UsersbjpicDesktopesp-idf>openocd -f board/esp32c3-builtin.cfg
Open On-Chip Debugger v0.10.0-esp32-20210401 (2021-04-01-15:46)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : only one transport option; autoselect ‘jtag’
Warn : Transport «jtag» was already selected
force hard breakpoints
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Info : esp_usb_jtag: Device found. Base speed 40000KHz, div range 1 to 255
Info : clock speed 40000 kHz
Info : JTAG tap: esp32c3.cpu tap/device found: 0x00005c25 (mfg: 0x612 (Espressif Systems), part: 0x0005, ver: 0x0)
Info : datacount=2 progbufsize=16
Info : Examined RISC-V core; found 1 harts
Info : hart 0: XLEN=32, misa=0x40101104
Info : Listening on port 3333 for gdb connections
Note the Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
This occurs even though I have tried all the permutations of drivers for the USB port. When I try actual debugging in Eclipse I get a register dump and numerous lines like
Info : [0] Found 8 triggers
Error: esp_usb_jtag: usb sent only 0 out of 17 bytes.
Error: missing data from bitq interface
Error: dmi_scan failed jtag scan
…
Error: dmi_scan failed jtag scan
Error: failed read at 0x11, status=2
Error: esp_usb_jtag: usb sent only 0 out of 2601 bytes.
It seemed that since ESP32-C3 is new it makes more sense to use the most recent version of Openocd before trying to figure out the GDB issue.
Debug Logs
See attached for full dump of build output
Expected behavior
I would expect to be able to build openocd following the provided instructions.
Screenshots
na
openocdfails.txt
Reported by: Cyril Brulebois <kibi@debian.org>
Date: Sun, 13 Jul 2014 12:33:17 UTC
Severity: serious
Tags: patch
Found in versions openocd/0.8.0-1, 0.8-1, openocd/0.8.0-3
Fixed in version openocd/0.8.0-4
Done: Luca Bruno <lucab@debian.org>
Bug is archived. No further changes may be made.
Toggle useless messages
Report forwarded
to debian-bugs-dist@lists.debian.org, kibi@debian.org, Uwe Hermann <uwe@debian.org>
:
Bug#754678
; Package src:openocd
.
(Sun, 13 Jul 2014 12:33:21 GMT) (full text, mbox, link).
Acknowledgement sent
to Cyril Brulebois <kibi@debian.org>
:
New Bug report received and forwarded. Copy sent to kibi@debian.org, Uwe Hermann <uwe@debian.org>
.
(Sun, 13 Jul 2014 12:33:21 GMT) (full text, mbox, link).
Message #5 received at submit@bugs.debian.org (full text, mbox, reply):
Source: openocd Version: 0.8.0-1 Severity: serious Justification: FTBFS Hi, your package no longer builds on kfreebsd-* due to a configure error: | checking whether to enable malloc free space logging... no | checking whether to enable ZY1000 minidriver... no | checking whether to enable dummy minidriver... no | checking whether standard drivers can be built... yes | checking for LIBUSB1... no | configure: WARNING: libusb-1.x not found, trying legacy libusb-0.1 as a fallback; consider installing libusb-1.x instead | checking for LIBUSB0... yes | checking for HIDAPI... yes | configure: error: libusb-1.x is required for the MPSSE mode of FTDI based devices | make: *** [debian/stamp-autotools] Error 1 Full build logs: https://buildd.debian.org/status/fetch.php?pkg=openocd&arch=kfreebsd-amd64&ver=0.8.0-1&stamp=1399747252 https://buildd.debian.org/status/fetch.php?pkg=openocd&arch=kfreebsd-i386&ver=0.8.0-1&stamp=1399750843 Mraw, KiBi.
Information forwarded
to debian-bugs-dist@lists.debian.org, Uwe Hermann <uwe@debian.org>
:
Bug#754678
; Package src:openocd
.
(Sun, 17 Aug 2014 08:57:05 GMT) (full text, mbox, link).
Acknowledgement sent
to Luca Bruno <lucab@debian.org>
:
Extra info received and forwarded to list. Copy sent to Uwe Hermann <uwe@debian.org>
.
(Sun, 17 Aug 2014 08:57:05 GMT) (full text, mbox, link).
Message #10 received at 754678@bugs.debian.org (full text, mbox, reply):
Package: openocd Version: 0.8-1 Followup-For: Bug #754678 This is because openocd needs libusb-1.0 >= 1.0.9, while the one provided by libusb2-dev on kfreebsd-* reports itself as 1.0.6 in pkg-config. I've filled a bug asking kfreebsd porters to sync lib version with upstream. Cheers, Luca -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash
Added blocking bug(s) of 754678: 758405
Request was from Luca Bruno <lucab@debian.org>
to control@bugs.debian.org
.
(Sun, 17 Aug 2014 09:21:12 GMT) (full text, mbox, link).
Reply sent
to Luca Bruno <lucab@debian.org>
:
You have taken responsibility.
(Sun, 19 Oct 2014 19:09:19 GMT) (full text, mbox, link).
Notification sent
to Cyril Brulebois <kibi@debian.org>
:
Bug acknowledged by developer.
(Sun, 19 Oct 2014 19:09:19 GMT) (full text, mbox, link).
Message #17 received at 754678-close@bugs.debian.org (full text, mbox, reply):
Source: openocd Source-Version: 0.8.0-3 We believe that the bug you reported is fixed in the latest version of openocd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 754678@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luca Bruno <lucab@debian.org> (supplier of updated openocd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Sun, 19 Oct 2014 19:12:49 +0200 Source: openocd Binary: openocd Architecture: source Version: 0.8.0-3 Distribution: unstable Urgency: high Maintainer: Uwe Hermann <uwe@debian.org> Changed-By: Luca Bruno <lucab@debian.org> Description: openocd - Open on-chip JTAG debug solution for ARM and MIPS systems Closes: 754678 Changes: openocd (0.8.0-3) unstable; urgency=high . * Require libusb-dev from freebsd-libs 10 snapshot (Closes: #754678) Checksums-Sha1: 39cac649ac58e5d02304c72766274438cb1fcd37 1913 openocd_0.8.0-3.dsc d4bc5906d87977b0ac35919bf307ff43e899db9b 11504 openocd_0.8.0-3.debian.tar.xz Checksums-Sha256: f4d09f786176810ff4d6c3628f108393e6ee997150c934e06205c7563c7cb0e0 1913 openocd_0.8.0-3.dsc 11b91219d18f6b5996e5fa5af1ce75fd052614c9f00759f86f645d5e7963edbf 11504 openocd_0.8.0-3.debian.tar.xz Files: a803da6d5096f2ba8ad083901c9eab15 1913 embedded extra openocd_0.8.0-3.dsc ed8bd2672d822cd7ce329ee69d510049 11504 embedded extra openocd_0.8.0-3.debian.tar.xz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJUQ/QsAAoJEKmDSiJSB45Od4gP/AgxhYakKrUL1mCJLLa7TPkY zuSw6K4icETNLFfDo8/B9BtUPNXj7I5efCDDrTT0gvsWb4CFKv8khpteWjxY2V5a Jkt6p+mlywplzcwCkfvKyHhwgL1bRZgL/wkLyeKkUXS+sQuu0W2YOWpA/SlMuKud 9YKyDma+wbBFbLlijr6Pv6dW4pK3y+qoC1AJ6/31KiGEk1w2xCBZaCkM9dpmcZ5a 4QL5cwKiYOuz6eP6wflSnHSMZ4QVuUlHEycjR87nCCpWCKvfu53ueZLWdytEyMw/ af2barcn6OIR346Hp35qE4eJO4dww/VJ6Ur5lL3tgQZRwszBb00sc7u2X5I7lq6+ QmFnOBK+yDUy3Qo2WiDtOOWY+2BQifMdhLi5OFP5/zX/sn4a+sXny9t+/f13qnWe BZS70k5Xrw/XTq3C/usiNZQ1a8U2wjSHoGyDeS0+LVCWp+uTEZwyz6XwGHzPRRz4 kr1WN+6rplte3061O2e4Kzpk9ziptII3QJmyaQ+vBLgOJBjsWRerik5c42cly/cV YYBry1USfx69Q8roVZA7xEtvXwHj4VzoSKCgBzCIGNClKAMtaukZEmYSYvJtuyZR IEPldkuqFs8qX3FU5Brbj3qgFUJBHGx1Jv6DbLosljO46zJ0xgtCnkcp2Yvdt/q8 Poo0K/raHOzl02200Bi8 =y4kW -----END PGP SIGNATURE-----
Information forwarded
to debian-bugs-dist@lists.debian.org, Uwe Hermann <uwe@debian.org>
:
Bug#754678
; Package src:openocd
.
(Sun, 19 Oct 2014 21:48:05 GMT) (full text, mbox, link).
Acknowledgement sent
to Steven Chamberlain <steven@pyro.eu.org>
:
Extra info received and forwarded to list. Copy sent to Uwe Hermann <uwe@debian.org>
.
(Sun, 19 Oct 2014 21:48:05 GMT) (full text, mbox, link).
Message #22 received at 754678@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
found 754678 0.8.0-3 tags 754678 + patch thanks Hi, openocd still FTBFS on kfreebsd-*: https://buildd.debian.org/status/fetch.php?pkg=openocd&arch=kfreebsd-amd64&ver=0.8.0-3&stamp=1413746707 If you want something equivalent to Linux libusb 1.0 API, I think you need to Build-Depend on libusb2-dev [kfreebsd-any] rather than libusb-dev. The next problem is, libftdi-dev was built against the older libusb-dev and they cannot be used together here. Dropping libftdi-dev from Build-Depends on kfreebsd-amd64, I actually get a successful build; how does that work? Does MPSSE mode not need ftdi.h any more? If so, libftdi-dev can be dropped from Build-Depends on linux, too. But I have no way of testing openocd. I've attached my build log, as well as a patch for the Build-Depends I used to build it. Thanks, Regards, -- Steven Chamberlain steven@pyro.eu.org
[openocd.log.gz (application/x-gzip, attachment)]
[openocd.diff (text/x-diff, attachment)]
[signature.asc (application/pgp-signature, attachment)]
Marked as found in versions openocd/0.8.0-3; no longer marked as fixed in versions openocd/0.8.0-3 and reopened.
Request was from Steven Chamberlain <steven@pyro.eu.org>
to control@bugs.debian.org
.
(Sun, 19 Oct 2014 21:48:08 GMT) (full text, mbox, link).
Added tag(s) patch.
Request was from Steven Chamberlain <steven@pyro.eu.org>
to control@bugs.debian.org
.
(Sun, 19 Oct 2014 21:48:08 GMT) (full text, mbox, link).
Information forwarded
to debian-bugs-dist@lists.debian.org, Uwe Hermann <uwe@debian.org>
:
Bug#754678
; Package src:openocd
.
(Mon, 20 Oct 2014 03:30:09 GMT) (full text, mbox, link).
Acknowledgement sent
to Paul Fertser <fercerpav@gmail.com>
:
Extra info received and forwarded to list. Copy sent to Uwe Hermann <uwe@debian.org>
.
(Mon, 20 Oct 2014 03:30:09 GMT) (full text, mbox, link).
Message #31 received at 754678@bugs.debian.org (full text, mbox, reply):
Hi, On Sun, Oct 19, 2014 at 10:45:17PM +0100, Steven Chamberlain wrote: > If you want something equivalent to Linux libusb 1.0 API, I think you > need to Build-Depend on libusb2-dev [kfreebsd-any] rather than libusb-dev. Right, libusb-0.1 API is still needed for some older drivers, but it is provided by libusb2-dev on kfreebsd, libusb-dev shouldn't be used there. > Dropping libftdi-dev from Build-Depends on kfreebsd-amd64, I actually > get a successful build; how does that work? Does MPSSE mode not need > ftdi.h any more? If so, libftdi-dev can be dropped from Build-Depends > on linux, too. But I have no way of testing openocd. MPSSE mode depends only on libusb-1, however, there're three other drivers (USB Blaster, ASIX Presto, OpenJTAG; USB Blaster being really important here) plus legacy ft2232 implementation that need libftdi-dev.
Information forwarded
to debian-bugs-dist@lists.debian.org, Uwe Hermann <uwe@debian.org>
:
Bug#754678
; Package src:openocd
.
(Mon, 20 Oct 2014 11:48:05 GMT) (full text, mbox, link).
Acknowledgement sent
to Luca Bruno <luca.bruno@rocket-internet.de>
:
Extra info received and forwarded to list. Copy sent to Uwe Hermann <uwe@debian.org>
.
(Mon, 20 Oct 2014 11:48:05 GMT) (full text, mbox, link).
Message #36 received at 754678@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
On Mon, 20 Oct 2014 07:26:20 +0400 Paul Fertser <fercerpav@gmail.com> wrote: > On Sun, Oct 19, 2014 at 10:45:17PM +0100, Steven Chamberlain wrote: > > If you want something equivalent to Linux libusb 1.0 API, I think you > > need to Build-Depend on libusb2-dev [kfreebsd-any] rather than libusb-dev. > > Right, libusb-0.1 API is still needed for some older drivers, but it > is provided by libusb2-dev on kfreebsd, libusb-dev shouldn't be used > there. My fault, I got really confused in all this libusb* mess. I will apply your patch as-is and upload a -4. > > Dropping libftdi-dev from Build-Depends on kfreebsd-amd64, I actually > > get a successful build; how does that work? Does MPSSE mode not need > > ftdi.h any more? If so, libftdi-dev can be dropped from Build-Depends > > on linux, too. But I have no way of testing openocd. > > MPSSE mode depends only on libusb-1, however, there're three other > drivers (USB Blaster, ASIX Presto, OpenJTAG; USB Blaster being really > important here) plus legacy ft2232 implementation that need > libftdi-dev. If I'm not wrong: * usb-blaster support is autodetected * presto and openjtag should be explicitely enabled (currently aren't) * we don't currently explicitly enable any legacy ft2232 So the above patch should be ok. I'm just slightly confused about usb-blaster on kfreebsd, which seems to have been autoenabled even though libftdi-dev was missing. Cheers, Luca
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to debian-bugs-dist@lists.debian.org, Uwe Hermann <uwe@debian.org>
:
Bug#754678
; Package src:openocd
.
(Mon, 20 Oct 2014 12:03:05 GMT) (full text, mbox, link).
Acknowledgement sent
to Paul Fertser <fercerpav@gmail.com>
:
Extra info received and forwarded to list. Copy sent to Uwe Hermann <uwe@debian.org>
.
(Mon, 20 Oct 2014 12:03:05 GMT) (full text, mbox, link).
Message #41 received at 754678@bugs.debian.org (full text, mbox, reply):
On Mon, Oct 20, 2014 at 01:45:15PM +0200, Luca Bruno wrote: > > MPSSE mode depends only on libusb-1, however, there're three other > > drivers (USB Blaster, ASIX Presto, OpenJTAG; USB Blaster being really > > important here) plus legacy ft2232 implementation that need > > libftdi-dev. > > If I'm not wrong: > * usb-blaster support is autodetected No, it's currently not. > * presto and openjtag should be explicitely enabled (currently aren't) > * we don't currently explicitly enable any legacy ft2232 Right. > So the above patch should be ok. USB Blaster support would be nice to have... > I'm just slightly confused about usb-blaster on kfreebsd, which seems to have > been autoenabled even though libftdi-dev was missing. How do you tell it was?
Information forwarded
to debian-bugs-dist@lists.debian.org, Uwe Hermann <uwe@debian.org>
:
Bug#754678
; Package src:openocd
.
(Mon, 20 Oct 2014 13:27:07 GMT) (full text, mbox, link).
Acknowledgement sent
to Steven Chamberlain <steven@pyro.eu.org>
:
Extra info received and forwarded to list. Copy sent to Uwe Hermann <uwe@debian.org>
.
(Mon, 20 Oct 2014 13:27:07 GMT) (full text, mbox, link).
Message #46 received at 754678@bugs.debian.org (full text, mbox, reply):
Hi, On 20/10/14 13:01, Paul Fertser wrote: > On Mon, Oct 20, 2014 at 01:45:15PM +0200, Luca Bruno wrote: >> I'm just slightly confused about usb-blaster on kfreebsd, which seems to have >> been autoenabled even though libftdi-dev was missing. > > How do you tell it was? In the build log I attached (with libftdi-dev not installed) : https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=22;filename=openocd.log.gz;att=1;bug=754678 | Altera USB-Blaster II Compatible yes (auto) > Making all in usb_blaster > make[8]: Entering directory `«BUILDDIR»/src/jtag/drivers/usb_blaster' > /bin/bash ../../../../libtool --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../../../.. -I../../../../src -I../../../../src -I../../../../src/helper -DPKGDATADIR="/usr/share/openocd" -DBINDIR="/usr/bin" -I../../../../jimtcl -I../../../../jimtcl -I../../../../src/jtag/drivers -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wall -Wstrict-prototypes -Wformat-security -Wshadow -Wextra -Wno-unused-parameter -Wbad-function-cast -Wcast-align -Wredundant-decls -c -o usb_blaster.lo usb_blaster.c > libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../../../.. -I../../../../src -I../../../../src -I../../../../src/helper -DPKGDATADIR="/usr/share/openocd" -DBINDIR="/usr/bin" -I../../../../jimtcl -I../../../../jimtcl -I../../../../src/jtag/drivers -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wall -Wstrict-prototypes -Wformat-security -Wshadow -Wextra -Wno-unused-parameter -Wbad-function-cast -Wcast-align -Wredundant-decls -c usb_blaster.c -o usb_blaster.o > /bin/bash ../../../../libtool --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../../../.. -I../../../../src -I../../../../src -I../../../../src/helper -DPKGDATADIR="/usr/share/openocd" -DBINDIR="/usr/bin" -I../../../../jimtcl -I../../../../jimtcl -I../../../../src/jtag/drivers -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wall -Wstrict-prototypes -Wformat-security -Wshadow -Wextra -Wno-unused-parameter -Wbad-function-cast -Wcast-align -Wredundant-decls -c -o ublast2_access_libusb.lo ublast2_access_libusb.c > libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../../../.. -I../../../../src -I../../../../src -I../../../../src/helper -DPKGDATADIR="/usr/share/openocd" -DBINDIR="/usr/bin" -I../../../../jimtcl -I../../../../jimtcl -I../../../../src/jtag/drivers -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wall -Wstrict-prototypes -Wformat-security -Wshadow -Wextra -Wno-unused-parameter -Wbad-function-cast -Wcast-align -Wredundant-decls -c ublast2_access_libusb.c -o ublast2_access_libusb.o > /bin/bash ../../../../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wall -Wstrict-prototypes -Wformat-security -Wshadow -Wextra -Wno-unused-parameter -Wbad-function-cast -Wcast-align -Wredundant-decls -Wl,-z,relro -o libocdusbblaster.la usb_blaster.lo ublast2_access_libusb.lo -ldl > libtool: link: ar cru .libs/libocdusbblaster.a usb_blaster.o ublast2_access_libusb.o > libtool: link: ranlib .libs/libocdusbblaster.a > libtool: link: ( cd ".libs" && rm -f "libocdusbblaster.la" && ln -s "../libocdusbblaster.la" "libocdusbblaster.la" ) > make[8]: Leaving directory `«BUILDDIR»/src/jtag/drivers/usb_blaster' In usb_blaster/Makefile, I think _libusb.c replaced _ftdi.c ? > #am__append_2 = ublast_access_ftdi.c > #am__append_3 = ublast_access_ftd2xx.c > am__append_4 = ublast2_access_libusb.c Regards, -- Steven Chamberlain steven@pyro.eu.org
Information forwarded
to debian-bugs-dist@lists.debian.org, Uwe Hermann <uwe@debian.org>
:
Bug#754678
; Package src:openocd
.
(Mon, 20 Oct 2014 13:33:05 GMT) (full text, mbox, link).
Acknowledgement sent
to Paul Fertser <fercerpav@gmail.com>
:
Extra info received and forwarded to list. Copy sent to Uwe Hermann <uwe@debian.org>
.
(Mon, 20 Oct 2014 13:33:05 GMT) (full text, mbox, link).
Message #51 received at 754678@bugs.debian.org (full text, mbox, reply):
On Mon, Oct 20, 2014 at 02:24:36PM +0100, Steven Chamberlain wrote: > On 20/10/14 13:01, Paul Fertser wrote: > > On Mon, Oct 20, 2014 at 01:45:15PM +0200, Luca Bruno wrote: > >> I'm just slightly confused about usb-blaster on kfreebsd, which seems to have > >> been autoenabled even though libftdi-dev was missing. > > > > How do you tell it was? > > In the build log I attached (with libftdi-dev not installed) : > > https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=22;filename=openocd.log.gz;att=1;bug=754678 > > | Altera USB-Blaster II Compatible yes (auto) I see the source of the confusion now. There're two versions of USB Blaster, the first one is still widely available (and requires libftdi), the second (depends onl libusb) is slowly gaining popularity (clk frequency control is yet to be implemented, currently it might be too high for many targets). -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercerpav@gmail.com
Information forwarded
to debian-bugs-dist@lists.debian.org, Uwe Hermann <uwe@debian.org>
:
Bug#754678
; Package src:openocd
.
(Mon, 20 Oct 2014 13:54:10 GMT) (full text, mbox, link).
Acknowledgement sent
to Luca Bruno <lucab@debian.org>
:
Extra info received and forwarded to list. Copy sent to Uwe Hermann <uwe@debian.org>
.
(Mon, 20 Oct 2014 13:54:10 GMT) (full text, mbox, link).
Message #56 received at 754678@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/plain, inline)]
On Monday 20 October 2014 17:31:48 Paul Fertser wrote: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=22;filename=openocd.log. > > gz;att=1;bug=754678> > > | Altera USB-Blaster II Compatible yes (auto) > > I see the source of the confusion now. There're two versions of USB > Blaster, the first one is still widely available (and requires > libftdi), the second (depends onl libusb) is slowly gaining popularity > (clk frequency control is yet to be implemented, currently it might be > too high for many targets). I see. So in the end, let's keep: * libusb autodetection for kfreebsd * --enable-usb_blaster_libftdi for linux Cheers, Luca
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to debian-bugs-dist@lists.debian.org, Uwe Hermann <uwe@debian.org>
:
Bug#754678
; Package src:openocd
.
(Mon, 20 Oct 2014 16:21:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Paul Fertser <fercerpav@gmail.com>
:
Extra info received and forwarded to list. Copy sent to Uwe Hermann <uwe@debian.org>
.
(Mon, 20 Oct 2014 16:21:04 GMT) (full text, mbox, link).
Message #61 received at 754678@bugs.debian.org (full text, mbox, reply):
On Mon, Oct 20, 2014 at 03:43:43PM +0200, Luca Bruno wrote: > On Monday 20 October 2014 17:31:48 Paul Fertser wrote: > I see. So in the end, let's keep: > * libusb autodetection for kfreebsd > * --enable-usb_blaster_libftdi for linux My proposal is to have libusb autodetection and usb_blaster_libftdi for all the supported systems. What exactly does kfreebsd lack that's necessary for libftdi? OpenOCD works with both libftdi-0 and libftdi-1, and kfreebsd supports both libusb-0.1 and libusb-1 APIs equally well libusb2-dev package.
Information forwarded
to debian-bugs-dist@lists.debian.org, Uwe Hermann <uwe@debian.org>
:
Bug#754678
; Package src:openocd
.
(Mon, 20 Oct 2014 19:27:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Steven Chamberlain <steven@pyro.eu.org>
:
Extra info received and forwarded to list. Copy sent to Uwe Hermann <uwe@debian.org>
.
(Mon, 20 Oct 2014 19:27:04 GMT) (full text, mbox, link).
Message #66 received at 754678@bugs.debian.org (full text, mbox, reply):
> On Mon, Oct 20, 2014 at 03:43:43PM +0200, Luca Bruno wrote: >> On Monday 20 October 2014 17:31:48 Paul Fertser wrote: >> I see. So in the end, let's keep: >> * libusb autodetection for kfreebsd >> * --enable-usb_blaster_libftdi for linux That sounds great, and I think is exactly what we get using my patch to build-depends? On 20/10/14 17:19, Paul Fertser wrote: > My proposal is to have libusb autodetection and usb_blaster_libftdi > for all the supported systems. What exactly does kfreebsd lack that's > necessary for libftdi? OpenOCD works with both libftdi-0 and > libftdi-1, and kfreebsd supports both libusb-0.1 and libusb-1 APIs > equally well libusb2-dev package. The problem is libftdi: it was compiled against legacy libusb on kfreebsd (libftdi-dev depends on libusb-dev); and libusb-dev and libusb2-dev are not co-installable as build-depends of openocd. libftdi may need to go through a transition to libusb2-dev on kfreebsd to avoid this, but would have to wait for the next Debian release I guess... Thanks! Regards, -- Steven Chamberlain steven@pyro.eu.org
Reply sent
to Luca Bruno <lucab@debian.org>
:
You have taken responsibility.
(Mon, 20 Oct 2014 21:30:06 GMT) (full text, mbox, link).
Notification sent
to Cyril Brulebois <kibi@debian.org>
:
Bug acknowledged by developer.
(Mon, 20 Oct 2014 21:30:06 GMT) (full text, mbox, link).
Message #71 received at 754678-close@bugs.debian.org (full text, mbox, reply):
Source: openocd Source-Version: 0.8.0-4 We believe that the bug you reported is fixed in the latest version of openocd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 754678@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luca Bruno <lucab@debian.org> (supplier of updated openocd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Mon, 20 Oct 2014 22:11:28 +0200 Source: openocd Binary: openocd Architecture: source Version: 0.8.0-4 Distribution: unstable Urgency: medium Maintainer: Uwe Hermann <uwe@debian.org> Changed-By: Luca Bruno <lucab@debian.org> Description: openocd - Open on-chip JTAG debug solution for ARM and MIPS systems Closes: 754678 Changes: openocd (0.8.0-4) unstable; urgency=medium . * Enable usb_blaster_libftdi on linux * Build-dep on libusb2-dev on kfreebsd (Closes: #754678) Checksums-Sha1: 252bb848da5e0890d18efa9e9995f0487bf95289 1944 openocd_0.8.0-4.dsc b0b05bfeaf25aefdd6500e6e81ea6e6423bd848d 11556 openocd_0.8.0-4.debian.tar.xz Checksums-Sha256: 76d370f5cbf5be9d9d5717549940a67acd224ba23ba5359020de35cad4ac571d 1944 openocd_0.8.0-4.dsc a5a395901dad0f0149fbd0ae4954ca098e63e23ce7ab83a16512335fec584504 11556 openocd_0.8.0-4.debian.tar.xz Files: 3bb3a4f84dafd8ae44e32625ad05fc6e 1944 embedded extra openocd_0.8.0-4.dsc 75c326d4cab243898d89bc539019e6e8 11556 embedded extra openocd_0.8.0-4.debian.tar.xz -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJURW5KAAoJEKmDSiJSB45OCGEP/1BYpYLLphApbxzfJEvzUhc5 gAzxkPj8GnEAYg4k00MfFZB6zHK+ADciyDvM5IArd49SCCE1yfU1IBWOFNg6vN1v qgiErB4Ejywy60DA++UcXX9ez2HDVPBE3EQfD0XFLIe6r0MynVopgVkIuyfBi/7j 3Ncob7qJwQpM3q6OlmllzpQ4fuMyYGkIBgqi5k6r9W1TXxyt550Jcyl2BSpuRvt4 gEl6WcnVh2ZyEFGNlmabjfyAKOJYhrWsC8BfApScqThTTdNu93mQr/JXWKoOtf8G 8p/MtGr5NnAxwR6NZ63qrBFvxG5pXE44JCl45QMGae7hdt6Vz4yPkW4Pw+sxt57w x4vfIYWcRecXSCu+DoPHsi/vEduh3FxVpEcJXXDeYNPCIMTZPT5Qk2bRTUvKAn+h M0M8V0KH42E520WO94ttpTSLScH2z5pH8EW9lk7itq7Q4aaD7XdIHzwthGyzgeme q9yXjc+4mJuvXygo8brEQwry1X1R38XeYgbSL5ULleJYQdaqGrNfbmIt0hu1wF+d cOyVbiKzdSvjZWsqJbpDiWEPbsghLO6oCB1EJAGVh1iUWL41/GAGT0uSnLdYvI3a VJ34H9jPoe77582UuuAam1ZtC86jswuhudUbPFz7lkdevRitu3NzEa++ymmpJlnR N5C73obEuTUFhXzSkfT/ =Hf06 -----END PGP SIGNATURE-----
Bug archived.
Request was from Debbugs Internal Request <owner@bugs.debian.org>
to internal_control@bugs.debian.org
.
(Tue, 18 Nov 2014 07:36:28 GMT) (full text, mbox, link).
Send a report that this bug log contains spam.
Debian bug tracking system administrator <owner@bugs.debian.org>.
Last modified:
Thu Feb 9 09:14:06 2023;
Machine Name:
bembo
Debian Bug tracking system
Debbugs is free software and licensed under the terms of the GNU
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.
Copyright © 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson,
2005-2017 Don Armstrong, and many other contributors.
Bug
201721
Summary: | devel/openocd: Update to 0.9.0 | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Kenji Rikitake <kenji> | ||||||||
Component: | Individual Port(s) | Assignee: | Steven Kreuzer <skreuzer> | ||||||||
Status: | Closed FIXED |
||||||||||
Severity: | Affects Many People | CC: | ardovm, kenji.rikitake | ||||||||
Priority: | — | Flags: | bugzilla: maintainer-feedback? (skreuzer) |
||||||||
Version: | Latest | ||||||||||
Hardware: | Any | ||||||||||
OS: | Any | ||||||||||
Attachments: |
|
I’ve built a fairly complete distro for the STM32F4. It is build around a modified Buildroot distro and a modified Nuttx kernel. I wanted to try and build the easiest possible development system for Cortex-M processors.
Instructions here: http://www.vxmdesign.com/STM32.html
I would still consider it very ‘alpha’ stage work, but it works on the STM32F407 Discovery board with that attached Discovery backbone board.
The distro will automatically build the toolchain, kernel, and icsp programming/debugging programs.
This distro will also automatically link in a romfs generated from buildroot which Nuttx will mount at boot time. This way you can easily add in files to Nuttx’s psuedo filesystem.
Building everything requires:
git clone https://github.com/vxmdesign/prjpluto.git
cd prjpluto
make vdsc_defconfig
make
It will do everything from there. All of the build files are placed in the prjpluto/output directory so there is no need for root permissions and there will be no conflicts with other cross compilers. (Though, don’t try and built it if you have an identically named cross compiler in your default paths).
There is still lots of work to be done, but the basic functionality should be there.
Happy programming!