- Description has changed:
Diff:
~~~~
~~~~
- **status**: new --> closed
- **Milestone**: --> 1.0
- **Comment**:
Assuming it's fixed now due to lack of feedback.
---
** [tickets:#57] Segger j-Trace gives an error upon jlink info which causes gdb
to fail if opened with pipe**
**Status:** closed
**Milestone:** 1.0
**Labels:** jlink pipe gdb
**Created:** Thu Nov 22, 2012 07:58 AM UTC by Johan
**Last Updated:** Thu Jan 03, 2013 12:12 PM UTC
**Owner:** nobody
We are using Segger j-Trace (jlink) to connect to an STM32F217 target. If we
use gdb and open the openocd (0.6.1) using pipe, gdb will hang. The log shows
the error message "dummy byte read failed". It is possible to recreate that
error just by doing 'jlink info'.
I discovered that if I remove the last code section from the function
jlink_usb_io() that tries to read out a dummy byte, it all seem to work fine.
No error message - no gdb hanging. Is that an ok work-around??
Regards
/Johan
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/openocd/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/openocd/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos. Get
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
