- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I have two FX3 chips in a JTAG chain connected to OpenOCD. I use FT2232H module and OpenOCD 0.10.0. Cypress SDK 1.3.4.
...\OpenOCD-20181130\bin>openocd -f myftdi.cfg -f board.cfg
Open On-Chip Debugger 0.10.0 (2018-11-30) [https://github.com/sysprogs/openocd]
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
trst_only separate trst_push_pull
jtag_ntrst_assert_width: 200
jtag_ntrst_delay: 200
RCLK - adaptive
adapter speed: 8000 kHz
fx3_1.cpu
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : clock speed 8000 kHz
Info : JTAG tap: fx3_0.cpu tap/device found: 0x07926069 (mfg: 0x034 (Cypress), part: 0x7926, ver: 0x0)
Info : JTAG tap: fx3_1.cpu tap/device found: 0x07926069 (mfg: 0x034 (Cypress), part: 0x7926, ver: 0x0)
Info : Embedded ICE version 6
Info : fx3_0.cpu: hardware has 2 breakpoint/watchpoint units
Info : Embedded ICE version 6
Info : fx3_1.cpu: hardware has 2 breakpoint/watchpoint units
Info : Listening on port 3333 for gdb connections
Info : Listening on port 3334 for gdb connections
As you can see we have two ports 3333 and 3334 for gdb connection. I can debug first FX3 at 3333 port without any errors at all. But I can't access second FX3 at 3334.
OpenOCD hangs. I'm sure there is no signal integrity troubles at JTAG lines. Configuration files are attached.
Regards
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
Thank you for answer!
Previously I tried to run GDB OpenOCD Debugging (in Debug Configuration menu). For 3333 port it workes, but 3334 hangs.
Now I tried GDB Hardware Debugging with options:
GDB Command: arm-none-eabi-gdb
Use remote target - checked
JTAG Device: GNU ARM OpenOCD
Host name or IP address: localhost
Port number: 3333 (or 3334 for second device)
Force threread list update on suspend - checked
Both port debug works fine!
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Openocd can communicate with GDB in two ways:
1.A socket(TCP/IP) conncetion is typically started as follows:
target remote localhost:3333
2.A pipe connection is typically started as follows.
target remote | openocd -c "gdb_port pipe; log_output openocd.log".
For more details,please refer to following link"OpenOCD User’s Guide: GDB and OpenOCD ".
Regards,
Anil Srinivas.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
Thank you for answer!
Previously I tried to run GDB OpenOCD Debugging (in Debug Configuration menu). For 3333 port it workes, but 3334 hangs.
Now I tried GDB Hardware Debugging with options:
GDB Command: arm-none-eabi-gdb
Use remote target - checked
JTAG Device: GNU ARM OpenOCD
Host name or IP address: localhost
Port number: 3333 (or 3334 for second device)
Force threread list update on suspend - checked
Both port debug works fine!
Regards