I have another nucleo-429zi that I purchased in the same order as the one that 
was updated. This unupdated board has firmware V2J28M18, and does not show the 
same libusb_bulk_transfer timeouts as the board updated to V2J30M19 (I get ITM 
output as expected).

I'm using the following commands via gdb to initialize the cpu, tpiu, and itm:

```
monitor reset halt
monitor tpiu config internal itm.fifo uart off 16000000
monitor itm port 0 on
c
```

ITM output is observed via an external device in the case where 
libusb_bulk_transfer timeouts are observed.




---

** [tickets:#174] stlink-v2-1 with firmware V2J30M19 timeouts in bulk transfer 
reads of trace endpoint**

**Status:** new
**Milestone:** 0.9.0
**Created:** Thu Jan 25, 2018 08:39 PM UTC by Cody Schafer
**Last Updated:** Thu Jan 25, 2018 10:42 PM UTC
**Owner:** nobody


Immediately after updating the firmware on a stlink-v2-1 (on a nucleo-f429zi 
board) to V2J30M19 (from STSW-LINK007 version 2.30.19 ), I've started to see 
libusb bulk transfer timeouts when openocd tried to read the trace endpoint. 
"bulk trace read failed" is printed. I've tried increasing the timeout 10x, but 
it still times out.

This is on current master (64f1f7b1c179dcce4e008bef6bf9515c47ae4100) with a few 
changes to print details about the libusb_bulk_transfer failures (return values 
from those functions are typically ignored.

I unfortunately didn't note the previous (non-erroring for this case) firmware 
version.


---

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.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to