Paul Fertser

On Wed, Nov 05, 2025 at 10:57:53AM -0000, Mark W wrote: How did you route around it if you're talking about the USB hub integrated on RaspberryPi 5 board? First of all, it's not a full speed hub there (so the forum thread doesn't apply), second, as seen in doc/usb_adapters/stlink/0483_3757_stlinkv3pwr.txt it's a high speed device so no translation is needed in any case. Are you connecting it via an additional full speed hub? It's a rPi CM5, with the TI USB hub on the parent PCB. I understand how...

On Wed, Nov 05, 2025 at 04:36:11AM -0000, Mark W wrote: This problem appears to be caused by a TI UBS hub chip. [1]https://forums.raspberrypi.com/viewtopic.php?t=246248 Hm, but this whole forum discussion doesn't seem to be related, and it's all strange. They reference a forum post on TI E2E that confirms that a certain USB hub model is full speed so naturally it doesn't have any TT (transaction translators) from full/low speed to high speed since it doesn't support any high speed connections at...

Hi Mark! On Tue, Nov 04, 2025 at 07:01:00AM -0000, Mark W wrote: I'm attempting to use openocd to connect to a STLink V3Mods using a Raspberry Pi 5 (arm64) host. I've built OpenOCD on the host using the cloned master repo from [2]https://github.com/openocd-org/openocd. As im guessing this could be libusb related, ive tried the os repo version of libusb, and also built libusb from the github master. The errors i see are (libusb also has debug output enabled): ... Debug: 126 4 stlink_usb.c:3744 stlink_open():...

Hi, On Mon, Sep 29, 2025 at 05:21:32PM -0000, Allan Macdonald wrote: [1][tickets:#459] Unable to Access openocd.org from Ubuntu 22.04LTS with Firefox That is a strange one indeed. If it's consistent I suggest you use Firefox "developer tools" network tab and save all the relevant information about what happens with what request. Also you can copy the request as cURL and compare the result by trying it in the command line. In general please keep in mind that openocd.org is hosted by SF.net themselves,...

Looks totally unrelated to me. You're using debug adapter which is not supported in upstream OpenOCD at all and it's unclear what "sdi" transport is. I suggest you ask whomever provides that "Open On-Chip Debugger 0.11.0+dev-02415-gfad123a16-dirty (2023-05-05-13:43)" fork (WCH?), I doubt anyone here in upstream has any idea about it.

Fixed the issue of incorrect detection of JEDEC bank 16 manufacturers

Hello, Thank you for the patch. Please consider sending it using the established procedure to the OpenOCD Gerrit instance as described by HACKING document. OpenOCD maintainers do not normally handle "merge requests" sent via SF.net, sorry.

jep106: update to revision JEP106BM Jun 2025