Replies: 5 comments 1 reply
-
I realised of course, I can run in debug mode...
|
Beta Was this translation helpful? Give feedback.
-
These seem to be the bad lines:
|
Beta Was this translation helpful? Give feedback.
-
Pete, I have currently no idea, but will have a closer look at this later today. |
Beta Was this translation helpful? Give feedback.
-
Many thanks Rene! I tried lots of things this evening. I installed OpenOCD from brew (I had built it from source), to make sure it had all the required dependencies, I tried running with sudo and without, I tried lowering the adapter speed, disabling TRST. I also booted into Linux to check alt4 was selected on all the required pins. I also checked libusb was installed and working etc. I even checked the brew formula. I can see that it finds the device, because if I change the name of the device, it fails to find it. At this point I think I will probably give up, and order a second JTAG device, and see if I can get it to work. Another thing I could try is using a different host computer. Anyway, thanks very much for trying to help, and no worries, I'm sure I'll be able to resolve it with a different JTAG device, and they are pretty cheap these days. :-) |
Beta Was this translation helpful? Give feedback.
-
I came across of a similar problem - my FT232H-based probe doesn't work on latest macOS. I believe the issue is it being locked by Apple's own driver, which was moved from kernel into userspace (DriverKit). This far I'm failing to unload the extension miserably -
|
Beta Was this translation helpful? Give feedback.
-
Hi. I'm having difficulties setting up JTAG debugging. I have the FTDI C232HM DDHSL-0 USB 2.0 Hi-Speed to MPSSE Cable.
I've built openocd from source with two additional fixes for macOS (8653 and 8660).
I've triple checked my wiring, and it looks correct to me:
The mapping from wire colour to JTAG function is was found in the file
tcl/interface/ftdi/c232hm.cfg
below, and also matches the official datasheet linked above.My openocd version seems correct (the version I built today):
The output I am getting:
The configs I reference are the patched rpi4.cfg file documented in
doc/debug-jtag.txt
file, plus thetcl/interface/ftdi/c232hm.cfg
found in the latest source version of openocd... I also tried withopenocd -f tcl/interface/ftdi/c232hm.cfg -f ./tcl/board/rpi4b.cfg
(i.e. using therpi4b.cfg
in openocd itself now, rather than the patched version indoc/debug-jtag.txt
) but that gave the same result.I have
enable_jtag_gpio=1
in myconfig.txt
:Finally, I'm running the bootloader from the
bootloader-pl011
branch:At this point, I don't know if it is a macOS issue, or if my JTAG device is broken, or I have misconfigured something. Any help appreciated! I'm not really sure how to debug further.
Many thanks
Pete
Beta Was this translation helpful? Give feedback.
All reactions