Thank you for giving feedback to the stlink project.
NOTE: In order to offer sufficient and the best possible support, please read /CONTRIBUTING.md and follow the given instructions before submitting a ticket.
Bug reports and/or feature requests will be deleted, if they violate our contribution guidelines and if no issue-template is used! Thank you for your support.
In order to allow developers to isolate and target your respective issue, please take some time to select the check boxes below and fill out each of the following items appropriate to your specific problem.
st-trace]Further we kindly ask you to describe the detected problem as detailed as possible and to add debug output if available, by using the following template:
Step 1:
Begin reading a trace and then end the application using Ctrl+C
C:\STLink Tests>st-trace.exe
libusb: info [winusb_get_device_list] The following device has no driver: 'USB\VID_8087&PID_0025\6&1143EA6&0&4'
libusb: info [winusb_get_device_list] libusb will not be able to access it
2022-09-28T17:42:11 INFO common.c: F4xx: 192 KiB SRAM, 1024 KiB flash in at least 16 KiB pages.
2022-09-28T17:42:11 INFO trace.c: Trace Port Interface configured to expect a 982 MHz system clock.
2022-09-28T17:42:11 INFO trace.c: Trace frequency set to 2000000 Hz.
2022-09-28T17:42:11 INFO trace.c: Reading Trace
Application is starting
^C
Step 2:
Reconnect. Sometimes st-trace is able to get through and it will reconnect correctly, usually I will end up with LIBUSB_ERROR_TIMEOUT error and then LIBUSB_ERROR_PIPE when I will pull USB cable out of ST-Link device
C:\STLink Tests>st-trace.exe
libusb: info [winusb_get_device_list] The following device has no driver: 'USB\VID_8087&PID_0025\6&1143EA6&0&4'
libusb: info [winusb_get_device_list] libusb will not be able to access it
[!] send_recv send request failed: LIBUSB_ERROR_TIMEOUT
[!] send_recv STLINK_GET_VERSION
[!] send_recv send request failed: LIBUSB_ERROR_TIMEOUT
[!] send_recv STLINK_GET_CURRENT_MODE
[!] send_recv send request failed: LIBUSB_ERROR_PIPE
[!] send_recv STLINK_GET_CURRENT_MODE
libusb: error [winusbx_submit_bulk_transfer] ReadPipe/WritePipe failed: [22] The device does not recognize the command.
[!] send_recv send request failed: LIBUSB_ERROR_IO
[!] send_recv STLINK_DEBUG_ENTER
libusb: error [winusbx_submit_bulk_transfer] ReadPipe/WritePipe failed: [22] The device does not recognize the command.
[!] send_recv send request failed: LIBUSB_ERROR_IO
[!] send_recv STLINK_DEBUG_READCOREID
2022-09-28T17:42:24 ERROR common.c: Failed to read core_id
libusb: error [winusbx_submit_bulk_transfer] ReadPipe/WritePipe failed: [22] The device does not recognize the command.
[!] send_recv send request failed: LIBUSB_ERROR_IO
[!] send_recv STLINK_JTAG_READDEBUG_32BIT
2022-09-28T17:42:24 ERROR common.c: Can not connect to target. Please use 'connect under reset' and try again
2022-09-28T17:42:24 ERROR trace.c: Your stlink is not connected to a device
By sending termination signal using ctrl+c the st-trace.exe will be left hanging in the memory or it won't send ST-Link itself a signal to stop logging. This means that st-trace is unable to reconnect to the busy ST-Link. Pulling USB out of ST-Link and connecting it back will cause that it is possible to reconnect and log again.
Expected action: Some cleanup code, which would close / stop ST-Link logging before exiting the st-trace.exe program.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4