-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Help error program cc2652p via esp32 bridge (EUB-47) #11
Comments
Can you share the log from the esp-usb-bridge as well? It would be interesting to see if there are any error reported prior to the error coming from openocd. Are you able to debug the same device by any other means that the esp-usb-bridge (same device, same openocd)? |
I would love to, but how do I get a log with esp?
unfortunately I don't have another programmer |
The native USB connected to D+, D- is used by the bridge communication (JTAG) in your case. But you can connect to the UART (RxD, TxD) a terminal program. You will see the log there. |
I would recommend to try find one. Because you can loose a lot of time try to debug the bridge if the issue is not there. |
do you mean that when I connect the esp, I have two devices, one jtag and the second com port? I tried to connect to com port speed 9600 and 115200, but there was nothing on the termen |
Two connections are needed, not one.
|
ok, which pin should I connect to the esp |
I (21) boot: ESP-IDF v5.0.1 2nd stage bootloader |
@newsy5 Can you run openocd with -d3 option to see the verbose debug logs? Until now, I didn't connect any arm chip to the bridge. I will try to test it soon. We use esp_usb_jtag protocol for the jtag communication, maybe it requires some adjustment. |
C:\my\openocd-esp32\bin>openocd.exe -d3 |
i test openocd version v0.12.0-esp32-20230419, v0.12.0-esp32-20230313, v0.11.0-esp32-20221026 and v0.12.0 oficial |
please tell me |
Sorry, couldn't test it yet with the arm board. Can I ask for one more debug? Please add the below lines to your config file and send me the log.txt
|
conole with config openocd.cfg adapter driver esp_usb_jtag the problem is in the line adapter driver esp_usb_jtag C:\my\openocd-esp32\bin>openocd |
Ok. You can run OpenOCD with -c parameter like below.
|
have you looked at the log, is there a misunderstanding why it doesn't work? |
Hi, @newsy5 I am sorry, couldn't figure out why the ARM board disappears during communication. I need to test it but still don't have a board with the Jtag pins exported. |
Finally, I found a board with a Texas arm chip. It couldn't be able to complete the first examination process. I am on it. Will let you know when I have a progress.
|
tnx, i im wait |
@newsy5 After replicating the issue and conducting further investigation, it appears that we encounter a problem when OpenOCD requests a large amount of flash data for read/write operations, particularly on ARM chips. Considering other priorities at the moment, I will address this issue when I have sufficient time available. |
maybe who knows what the problem might be, I want to download the firmware to cc2652p via esp bridge.
connected it seems to be correct, I use esp32s2
everything connects normally , but the firmware is not upload
config openocd:
adapter driver esp_usb_jtag
espusbjtag vid_pid 0x303a 0x1002
espusbjtag caps_descriptor 0x030A
adapter speed 1000
source [find target/ti_cc26x2.cfg]
set remotetimeout 100
reset_config trst_only
program ptvo.switch-zr02.hex
log openocd:
C:\my\openocd-esp32\bin>openocd
Open On-Chip Debugger v0.12.0-esp32-20230419 (2023-04-18-22:02)
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 0x1002
Info : esp_usb_jtag: capabilities descriptor set to 0x30a
Info : esp_usb_jtag: serial (4827E24B37E4)
Info : esp_usb_jtag: Device found. Base speed 480KHz, div range 1 to 1
Info : clock speed 480 kHz
Info : JTAG tap: cc26x2.jrc tap/device found: 0x3bb4102f (mfg: 0x017 (Texas Instruments), part: 0xbb41, ver: 0x3)
Info : JTAG tap: cc26x2.cpu enabled
Info : [cc26x2.cpu] Cortex-M4 r0p1 processor detected
Info : [cc26x2.cpu] target has 6 breakpoints, 4 watchpoints
Info : starting gdb server for cc26x2.cpu on 3333
Info : Listening on port 3333 for gdb connections
Info : JTAG tap: cc26x2.jrc tap/device found: 0x3bb4102f (mfg: 0x017 (Texas Instruments), part: 0xbb41, ver: 0x3)
Info : JTAG tap: cc26x2.cpu enabled
Warn : [cc26x2.cpu] Only resetting the Cortex-M core, use a reset-init event handler to reset any peripherals or configure hardware srst support.
[cc26x2.cpu] halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0xfffffffe msp: 0xfffffffc
** Programming Started **
Info : Padding image section 0 at 0x0000003c with 4036 bytes
Info : Padding image section 1 at 0x000013b8 with 8 bytes
Info : Flash write discontinued at 0x00037b86, next section at 0x00057fa8
Error: libusb_bulk_read error: LIBUSB_ERROR_TIMEOUT
Error: libusb_open() failed with LIBUSB_ERROR_ACCESS
Error: libusb_open() failed with LIBUSB_ERROR_ACCESS
Error: libusb_open() failed with LIBUSB_ERROR_ACCESS
Error: libusb_open() failed with LIBUSB_ERROR_ACCESS
Error: libusb_open() failed with LIBUSB_ERROR_ACCESS
Error: libusb_open() failed with LIBUSB_ERROR_ACCESS
Error: esp_usb_jtag: device not found!
Error: esp_usb_jtag: failed to revive USB device!
any ideas what you can try???
The text was updated successfully, but these errors were encountered: