Re: Flashing nRF with stlink V3

Hi, > On 21 Jun 2023, at 13:59, Aleksandar Rodzevski wrote: > > Wonder if there are any patches available for flashing an nRF using the > ST-Link V3. Just tried what's available on mainline and it doesn't seem to be > supported there. Any tips or info would be highly appreciated. I’ve tried

cmsis_dap_usb_bulk vid/pid matching

Hi, The cmsis_dap_usb_bulk driver’s vid/pid matching has the undocumented quirk that vid or pid zero acts as a wildcard, i.e. specifying “cmsis_dap_vid_pid 0x0 0x1234” will match any adapter with a pid of 0x1234. Is this wanted behavior, or could the driver use jtag_libusb_match_ids() from lib

Re: Debugger dongle project

Hi, > On 11 Oct 2021, at 18:29, Andreas Fritiofson > wrote: > > On Mon, Oct 11, 2021 at 4:46 PM Michael McCormack > wrote: > While there are plenty of schematics for FTDI based dongles, the FTDI drivers > cannot be included with OpenOCD right out of the box which is a

Re: [OpenOCD-devel] Adapters on libusb0

On 28 Dec 2020, at 12:40, Antonio Borneo wrote: > > In OpenOCD there are three adapter's drivers that use libusb0: > - USBProg JTAG Programmer > - Raisonance RLink JTAG Programmer > - Olimex ARM-JTAG-EW Programmer > > I would like to convert them to libusb1 and drop the dependency from > the old

Re: [OpenOCD-devel] To Zadig or not to Zadig?

> On 8 Jun 2017, at 13:51, Liviu Ionescu wrote: > > there are many other FTDI applications out there (I have and use some) which > rely on this standard behaviour. what do you think will happen to all these > devices if I unload the FTDI kext? If your other devices aren’t using specifically 2

Re: [OpenOCD-devel] To Zadig or not to Zadig?

> On 7 Jun 2017, at 23:44, Liviu Ionescu wrote: > > if I connect the board to my macOS 10.12, with the default FTDI drivers > installed in the system, I automatically get two 'Dual RS232-HS' interfaces: A kernel mode driver has grabbed the device, either Apple’s AppleUSBFTDI or FTDI’s own. T

Re: [OpenOCD-devel] OpenOCD-BOX

On Jun 5, 2012, at 14:16, Peter Stuge wrote: > These benefits result in excellent usability, and in practice I think > the IP address conflict can be solved rather easily - by allowing the > device's IP address and subnet to be reconfigured manually, e.g. > through type=vendor recipient=device co

Re: [OpenOCD-devel] Remote 'g' packet reply is too long

On Mar 12, 2012, at 17:09, Justin Drake wrote: > I am using OpenOCD and DGB to talk with my ARM Cortex 3M chip. When I > load my .elf file onto GDB, the moment I connect to my board (target > remote localhost:) I get the error message: > > Remote 'g' packet reply is too long: See