Closed lure23 closed 6 months ago
lure23
commented
8 months ago How OpenOCD is installed: https://github.com/lure23/EmbeddedRover/blob/main/mp-prime/manual/openocd.sh
The device is revision 0.4 - thus should have the built-in USB/JTAG.
I tried on two devices: one where a Rust-made code is running; another straight from the packaging. Both act the same.
erhankur
commented
8 months ago @lure23 What do you see on the client side when you try to attach a USB device? I gave it a try and saw the below error on my macOS host.
[2024-01-13T14:20:14Z WARN usbip::device] unknown desc type: SetupPacket { request_type: 80, request: 6, value: 2000, index: 0, length: ff }I think this definitely can be solved on the rust side.
Another workaround solution is to skip requesting device descriptors from the esp32c3 and fill the parameters manually on the OpenOCD side. This will require building from the source.
https://github.com/espressif/openocd-esp32/blob/master/src/jtag/drivers/esp_usb_jtag.c#L677
This is an interesting setup. Let me know if you need help while building the OpenOCD.
lure23
commented
8 months ago This is an interesting setup. Let me know if you need help while building the OpenOCD.
Thanks!
I'll try to get the connection working on macOS, natively. If that succeeds, I have added confidence and knowledge of the state of JTAG-over-USB. In reality though, it looks like probe-rs might be a better alternative for my needs since it's Rust native and doesn't need the gdb layer.
Steps today:
Tried OpenOCD-ESP release 0.12, but it doesn't have boards/esp32-jtag-builtin.cfg.
Cloned the master.
Prepared dependencies (with HomeBrew).
! Do I need the optional hidapi and/or libftdi for the C3 JTAG-over-USB?
$ ./bootstrap
[...]
$ ./configure
[...]
OpenOCD configuration summary
--------------------------------------------------
MPSSE mode of FTDI based devices yes (auto)
ST-Link Programmer yes (auto)
TI ICDI JTAG Programmer yes (auto)
Keil ULINK JTAG Programmer yes (auto)
ANGIE Adapter yes (auto)
Altera USB-Blaster II Compatible yes (auto)
Bitbang mode of FT232R based devices yes (auto)
Versaloon-Link JTAG Programmer yes (auto)
TI XDS110 Debug Probe yes (auto)
CMSIS-DAP v2 Compliant Debugger yes (auto)
OSBDM (JTAG only) Programmer yes (auto)
eStick/opendous JTAG Programmer yes (auto)
Olimex ARM-JTAG-EW Programmer yes (auto)
Raisonance RLink JTAG Programmer yes (auto)
USBProg JTAG Programmer yes (auto)
Espressif JTAG Programmer yes (auto)
CMSIS-DAP Compliant Debugger no
Nu-Link Programmer no
Cypress KitProg Programmer no
Altera USB-Blaster Compatible no
ASIX Presto Adapter no
OpenJTAG Adapter no
Linux GPIO bitbang through libgpiod no
SEGGER J-Link Programmer no
Bus Pirate yes (auto)
Use Capstone disassembly framework no
Observation: Expected to see "JTAG-over-USB"-something, but (looking at the source) "Espressif JTAG Programmer" seems to be it?
(installed locally)
With the ESP32-C3-DevKitC-02 connected:
$ openocd -f /usr/local/share/openocd/scripts/board/esp32c3-builtin.cfg
Open On-Chip Debugger v0.12.0-36eab91e (2024-01-14-12:09)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : only one transport option; autoselecting 'jtag'
Info : esp_usb_jtag: VID set to 0x303a and PID to 0x1001
Info : esp_usb_jtag: capabilities descriptor set to 0x2000
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Error: esp_usb_jtag: could not find or open device!
/usr/local/bin/../share/openocd/scripts/target/esp_common.cfg:9: Error:
at file "/usr/local/bin/../share/openocd/scripts/target/esp_common.cfg", line 9
Error: [esp32c3] Unsupported DTM version: -1
Error: [esp32c3] Could not identify target type.This is expected.
Looking at System Profiler, the device is (only) seen as:
$ system_profiler SPUSBDataType
2024-01-14 11:11:06.791 system_profiler[13252:392083] SPUSBDevice: IOCreatePlugInInterfaceForService failed 0xe00002be
2024-01-14 11:11:06.792 system_profiler[13252:392083] SPUSBDevice: IOCreatePlugInInterfaceForService failed 0xe00002be
USB:
[...]
CP2102N USB to UART Bridge Controller:
Product ID: 0xea60
Vendor ID: 0x10c4 (Silicon Laboratories, Inc.)
Version: 1.00
Serial Number: bc2f214f809ded11aafa5f84e259fb3e
Speed: Up to 12 Mb/s
Manufacturer: Silicon Labs
Location ID: 0x14600000 / 15
Current Available (mA): 500
Current Required (mA): 100
Extra Operating Current (mA): 0
[...]! Should I set it to bootloader mode, somehow? Would that change the VID:PID?
Reading README.macOS:
brew install libtool automake libusb [hidapi] [libftdi]
! Do I need the optional hidapi and/or libftdi for the C3 JTAG-over-USB?
erhankur
commented
8 months ago It should be fine as long as you see this in the config summary.
Espressif JTAG Programmer yes (auto)esp_usb_jtag is dependent on libusb and looks like it is installed.
The board config file is board/esp32c3-builtin.cfg
Unfortunately, I have no idea why your macOS couldn't enumerate the Jtag device. I don't remember if I installed something special on my mac. You should see something like this;
system_profiler SPUSBDataType
USB:
...
USB JTAG/serial debug unit:
Product ID: 0x1001
Vendor ID: 0x303a
Version: 1.01
Serial Number: 7C:DF:A1:A2:8F:38
Speed: Up to 12 Mb/s
Manufacturer: Espressif
Location ID: 0x14400000 / 1
Current Available (mA): 500
Current Required (mA): 500
Extra Operating Current (mA): 0@lure23 I don't see an issue related to OpenOCD here. Feel free to re-open if you need something from our side.
Development Kit
ESP32-C3-DevKitC-02
Module or chip used
ESP32-C3-WROOM-02
Debug Adapter
built-in
OpenOCD version
v0.12.0-esp32-20230921
Operating System
Windows + Ubuntu Linux
Using an IDE ?
no
OpenOCD command line
openocd -f board/esp32c3-builtin.cfg
JTAG Clock Speed
don't know - please advice
ESP-IDF version
5.3.0
Problem Description
My situation is a bit ... different.
I'm running ESP32 development on a Multipass VM (Ubuntu Linux), under macOS, and primarily (=only) interested in setting up a nice, embedded Rust development environment.
Access to the development board is via USB/IP, because ... Multipass doesn't allow normal USB pass-throughs.
This works. :)
What doesn't work is OpenOCD. I would like eventually to be able to develop using Rust Rover (from JetBrains), but I know they currently don't support OpenOCD in that product. Yet, I have hopes. So wanted to see how far I can get.
Where am I now?
"Everything" works; I can do Rust development on the VM, and flash my code (over USB/IP) to the device.
I installed OpenOCD via the Linux guidance - all the steps are visible in the repo below - and it seems healthy. When reaching for the device, it gives:
That doesn't tell much. Since the documentation here mentions:
..I thought that might be it, and installed such a driver on the Windows 10 that deals with the device.
I disconnected the device; no change.
Decided to take the other (PowerShell) approach of installing as well:
Does the "Exit code: 0x2a" mean it failed? I did grant it elevated rights when asked.
So...
The internal ticket for this in my repo is https://github.com/lure23/EmbeddedRover/issues/5 - it has some more details.
Debug Logs
Expected behavior
OpenOCD will be able to connect with the device, via built-in JTAG/USB.
Screenshots
No response