社区
Qt
帖子详情
exited with code -1073741511mn什么原因啊?
NicholasDong
2009-12-03 11:25:35
exited with code -1073741511
...全文
216
1
打赏
收藏
exited with code -1073741511mn什么原因啊?
exited with code -1073741511
复制链接
扫一扫
分享
转发到动态
举报
写回复
配置赞助广告
用AI写文章
1 条
回复
切换为时间正序
请发表友善的回复…
发表回复
打赏红包
dext
2009-12-03
打赏
举报
回复
贴代码
JLink_Windows_V648.zip
Version V6.48 (2019-07-26) Add
ed
flash programming support for AmbiqMicro's AMA2B1KK (Apollo2 Blue; AMA2BEVB). Add
ed
flash programming support for AmbiqMicro's AMA2B1KK (Apollo2 Blue; AMA2BEVB). Add
ed
unlocking support for Microchip SAML10 series devices. Add
ed
unlocking support for Microchip SAML10 series devices. Analog Devices ADUCM355: Reset could not be overwritten using a J-Link script file. Fix
ed
. CCS plugin: Add
ed
a new option which allows configuring a J-Link script file (project dependent). Commander: "erase" did not use the EraseChip command to erase the entire flash but the EraseSector command. Chang
ed
. Commander: "erase" did not use the EraseChip command to erase the entire flash but the EraseSector command. Chang
ed
. DLL Updater (internal): Add
ed
Infineons Micro Inspector. DLL Updater (internal): Add
ed
Infineons Micro Inspector. DLL: STM32WB55 add
ed
support for Co-Processor Wireless stack upgrade. DLL: Add
ed
Flash programming support for CYT2B9 series devices. DLL: Add
ed
Flash programming support for CYT2B9 series devices. DLL: Add
ed
Flash programming support for Cypress Traveo2 CYT2B and CYT4B series devices. DLL: Add
ed
Flash programming support for Cypress Traveo2 CYT2B and CYT4B series devices. DLL: Add
ed
OTP flash programming support for TI's RM42L device family. DLL: Add
ed
OTP flash programming support for TI's RM44L device family. DLL: Add
ed
OTP flash programming support for TI's RM46L device family. DLL: Add
ed
OTP flash programming support for TI's RM48L device family. DLL: Add
ed
flash programming support for Panasonic MN1M7BFxx and MN1M7AFxx series devices. DLL: Add
ed
flash programming support for Panasonic MN1M7BFxx and MN1M7AFxx series devices. DLL: Add
ed
flash programming support for ST STM32G47xx series devices. DLL: Add
ed
flash programming support for ST STM32G4xx series devices. DLL: Add
ed
flash programming support for ST STM32G4xx series devices. DLL: Add
ed
flash programming support for STM32H745, STM32H755, STM32H747 and STM32H757 series devices. DLL: Add
ed
flash programming support for STM32H745, STM32H755, STM32H747 and STM32H757 series devices. DLL: Add
ed
flash programming support for WIZnet W7500 series device. DLL: Add
ed
flash programming support for WIZnet W7500 series device. DLL: Add
ed
native trace buffer support for Renesas RZ/A2M series. DLL: Add
ed
support for Cypress CYT2B series devices Cortex-M4. DLL: Add
ed
support for Cypress CYT4B series devices Cortex-M7_0 and Cortex-M7_1. DLL: Add
ed
support for Cypress MB9DF / MB9EF series (FCR4) devices. DLL: Add
ed
support for RISC-V behind a DAP as setup. DLL: Add
ed
support for RISC-V via SWD for RISC-V behind a DAP setups. DLL: Add
ed
support for SPI FLash Adesto ATXP128/ATXP128R to SPIFI-Lib for indirect flash programming. DLL: Add
ed
support for SPI FLash Adesto ATXP128/ATXP128R to SPIFI-Lib for indirect flash programming. DLL: Add
ed
support for command string "CORESIGHT_SetCoreBaseAddr" DLL: Cypress PSoC4 family: Under special circumstances, unlock did not work. Fix
ed
. DLL: Cypress PSoC4 family: Under special circumstances, unlock did not work. Fix
ed
. DLL: Flash programming sector sizes correct
ed
for Traveo2 CYT4B series devices. DLL: Flash programming sector sizes correct
ed
for Traveo2 CYT4B series devices. DLL: For the MPC560xx devices, the ECC SRAM was not initializ
ed
after connect. Fix
ed
. DLL: Hilscher NetX90 flash bank size, fix
ed
. DLL: Infineon TLE98xx: Some J-Link LITEs could not connect establish a successful target connection due to missing firmware functionality. Fix
ed
. DLL: JTAG: When only having 1 TAP in the JTAG chain and its matches the one for the configur
ed
CPU core but the TAP-ID was unknown, connect did not work. Fix
ed
. DLL: Linux: Delay
ed
/ slow
ed
execution of certain API functions when using J-Link via USB (e.g. on Close()). Introduc
ed
in V6.46. Fix
ed
. DLL: Linux: When calling a J-Link application via the global symlink (e.g. "JLinkExe" instead of "./JLinkExe"), sometimes the JLinkDevices.xml file was not found. Fix
ed
. DLL: Linux: When calling a J-Link application via the global symlink (e.g. "JLinkExe" instead of "./JLinkExe"), sometimes the libjlink* shar
ed
library was not found. Fix
ed
. DLL: Microchip J-32 OEM probes could not support legacy Atmel devices. Fix
ed
. DLL: Minor bug in flash programming algorithm for STM32G0xx series devices, fix
ed
. DLL: NXP KW34: Add
ed
flash programming support for the program and data flash area. DLL: NXP KW34: Add
ed
flash programming support for the program and data flash area. DLL: NXP KW35 / KW36 / KW38 / KW39: Add
ed
flash programming support for the data flash area. DLL: NXP KW35 / KW36 / KW38 / KW39: Add
ed
flash programming support for the data flash area. DLL: NXP KW38: Correct
ed
device names showen in the device selection dialog. DLL: NXP KW38: Correct
ed
device names showen in the device selection dialog. DLL: NXP KW3x family: Improv
ed
flash programming spe
ed
significantly. DLL: NXP KW3x family: Improv
ed
flash programming spe
ed
significantly. DLL: NXP LPC18xx / LPC43xx: After QSPI flash programming, the QSPI flash memory was no longer memory mapp
ed
accessible. Introduc
ed
in V6.41. Fix
ed
. DLL: Open flash loaders for RISC-V did not work properly anymore (introduc
ed
with V6.46). Fix
ed
. DLL: Programming issue while another application is already running on Hilscher NetX90, fix
ed
. DLL: QSPI flash programming: When the QE bit was set before flash programming, it has been clear
ed
but not restor
ed
by the DLL. Introduc
ed
in V6.46h. Fix
ed
. DLL: Qorvo GP570 / UE878 / QPG6 family: Flash programming did not work in recent silicon revisions. Fix
ed
. DLL: Qorvo GPxxx: Under special circumstances, flash programming did not work. Fix
ed
. DLL: RAM size of ST STM32F412 series devices, fix
ed
. DLL: RISC-V behind a DAP: Setting system variables , , from J-Link script files did not have any effect for RISC-V behind a DAP. Fix
ed
. DLL: RISC-V behind a DAP: Setting system variables , , from J-Link script files did not have any effect for RISC-V behind a DAP. Fix
ed
. DLL: RISC-V: Add
ed
reset type "Reset Pin" to explicitly allow resetting the target via the reset pin, instead of the bit DLL: RISC-V: Chang
ed
default reset type from reset pin to to support reset on almost all systems, also ones that do not populate a reset pin DLL: RISC-V: Interrupts were not disabl
ed
correctly during flash programming for built-in flash algos (works well for open flash loaders). Fix
ed
. DLL: RISC-V: Reset could fail with "core did not halt after reset" even if the core halt
ed
correctly. Fix
ed
. DLL: Re-attaching to existing debug session after connecting and disconnecting once via TELNET (e.g. us
ed
by RTTClient and RTTViewer) did not work properly. Fix
ed
. DLL: Renesas R5F51306 (RX130) devices were not detect
ed
by the J-Link DLL. Fix
ed
. DLL: Renesas RX231: OFS1 could not be modifi
ed
. Fix
ed
. DLL: Renesas RX: Add
ed
support for RX66N series devices DLL: Renesas RX: Add
ed
support for RX72M series devices DLL: Renesas RX: Add
ed
support for RX72M series devices DLL: Renesas RX: Add
ed
support for RX72N series devices DLL: Renesas RX: Add
ed
support for RX72T series devices DLL: Renesas RX: Add
ed
support for RX72T series devices DLL: Renesas RX: RX66T: Programming of option-setting memory (OSIS) did not work properly. Fix
ed
. DLL: Renesas RX: When connecting to lock
ed
RX devices via JTAG (does not affect FINE!), 16-byte ID
CODE
(OSIS) could be reject
ed
even though the correct
code
was given. Fix
ed
. DLL: Renesas S7G2: QSPI flash programming did not work for QSPI flashes >= 16MB. Fix
ed
. DLL: Resets during halt of TI RM57L843ZWT device, due to running watchdog, fix
ed
. Enabl
ed
cross trigger interfaces to forward debug acknowl
ed
ge signal to Watchdog. DLL: SPI-Flash programming for Spansion S25FL256L, fix
ed
. DLL: STM32L031K6 secure chip did not work. Fix
ed
. DLL: STM32WB55 add
ed
support for Co-Processor Wireless stack upgrade. DLL: TI RM42L420 add
ed
EEPROM support. DLL: TI RM44L520/RM44L920 add
ed
flash and EEPROM support DLL: TI RM57L843ZWT add
ed
EEPROM support. DLL: TI RM57L843ZWT add
ed
EEPROM support. DLL: Under some circumstances Flash Cache was not clean
ed
after erase operations. DLL: Unsecure read protection for STM32L151xx series devices, fix
ed
. DLL: Unsecure write protection for STM32L151xxx series devices, fix
ed
. DLL: When using J-Trace PRO with IAR EWARM a "fail
ed
to allocate x bytes of memory" error could occur. Fix
ed
. DLL: Windows: Renesas RX: When using FINE interface and disabling ongoining debug mode on debug session close, it could happen that a thread was not
exit
ed
gracefully, causing handle leaks. Fix
ed
. DLL: macOS: When calling a J-Link application via the global symlink (e.g. "JLinkExe" instead of "./JLinkExe"), sometimes the libjlink* shar
ed
library was not found. Fix
ed
. Firmware: Flasher ARM / PRO / Portable PLUS: Chip erase could fail in stand-alone mode. Fix
ed
. Firmware: Flasher ARM / PRO / Portable PLUS: Parallel CFI NOR Flash memory programming could fail under special circumstances. Fix
ed
. Firmware: Flasher ARM / PRO / Portable PLUS: Stand-alone mode did not work for some devices from Analog Devices (e.g. ADuCM7023). Fix
ed
. Firmware: Flasher ARM / PRO: FWrite command was unable to receive 512 bytes via UART at once. Fix
ed
. Firmware: Flasher ARM V4: Warning "J-Link low on memory" could occur after using SPI functionality of J-Link. Fix
ed
. Firmware: Flasher ARM/PPC/RX/PRO: Target power supply monitoring could erroneously detect an over-current. Fix
ed
. Firmware: Flasher PRO: Open flash loaders for RISC-V did not work properly anymore (introduc
ed
with V6.46). Fix
ed
. Firmware: Flasher PRO: Universal Flash Loader mode detection in batch mode did not work. Fix
ed
. Firmware: Flasher PRO: Warning "J-Link low on memory" could occur after using SPI functionality of J-Link. Fix
ed
. Firmware: Flasher Portable PLUS did not show the correct status under special circumstances. Fix
ed
. Firmware: Flasher Portable PLUS did not work in J-Link Mode while showing "OK" message. Fix
ed
. Firmware: Flasher Portable PLUS: Universal Flash Loader mode detection in batch mode did not work. Fix
ed
. Firmware: Flasher Portable PLUS: Number of bytes to program was not calculate correctly, progress bar show
ed
wrong percentage. Fix
ed
. Firmware: Flasher Portable PLUS: Open flash loaders for RISC-V did not work properly anymore (introduc
ed
with V6.46). Fix
ed
. Firmware: Flasher Portable PLUS: Warning "J-Link low on memory" could occur after using SPI functionality of J-Link. Fix
ed
. Firmware: J-Link
ED
U Mini: RISC-V: On implementations that do not populate a "program buffer" CSRs could not be access
ed
correctly, resulting in non-functional debug sessions. Fix
ed
. Firmware: J-Link
ED
U Mini: RISC-V: Reset on SiFive FE310 device (mount
ed
on HiFive1 boards) could fail with timeout error. Fix
ed
. Firmware: J-Link
ED
U/BASE/PLUS V10: Add
ed
support for RISC-V behind a DAP as setup. Firmware: J-Link
ED
U/BASE/PLUS V10: Increas
ed
heap size of firmware (Add
ed
support for heap over multiple memory ranges with gaps between them) Firmware: J-Link
ED
U/BASE/PLUS V10: RISC-V: On implementations that do not populate a "program buffer" CSRs could not be access
ed
correctly, resulting in non-functional debug sessions. Fix
ed
. Firmware: J-Link
ED
U/BASE/PLUS V10: RISC-V: Reset on SiFive FE310 device (mount
ed
on HiFive1 boards) could fail with timeout error. Fix
ed
. Firmware: J-Link
ED
U/BASE/PLUS V10: SWO: Under very special circumstances it could happen that the 1st byte receiv
ed
on SWO was swallow
ed
. Only happen
ed
, if SWO pin was us
ed
for something else between SWO_Stop() and SWO_Start(). Fix
ed
. Firmware: J-Link
ED
U/BASE/PLUS V10: Warning "J-Link low on memory" could occur after using SPI functionality of J-Link. Fix
ed
. Firmware: J-Link OB-K22-SiFive: RISC-V: Reset on SiFive FE310 device (mount
ed
on HiFive1 boards) could fail with timeout error. Fix
ed
. Firmware: J-Link PRO V4: Add
ed
support for RISC-V behind a DAP as setup. Firmware: J-Link PRO V4: RISC-V: On implementations that do not populate a "program buffer" CSRs could not be access
ed
correctly, resulting in non-functional debug sessions. Fix
ed
. Firmware: J-Link PRO V4: RISC-V: Reset on SiFive FE310 device (mount
ed
on HiFive1 boards) could fail with timeout error. Fix
ed
. Firmware: J-Link PRO V4: Warning "J-Link low on memory" could occur after using SPI functionality of J-Link. Fix
ed
. Firmware: J-Link PRO V4: When connecting via IP and using RTT it could happen that J-Link FW crash
ed
and reboot
ed
if the PC did not
exit
the controlling process in a clean way. Fix
ed
. Firmware: J-Link ULTRA+ V4: Add
ed
support for RISC-V behind a DAP as setup. Firmware: J-Link ULTRA+ V4: RISC-V: On implementations that do not populate a "program buffer" CSRs could not be access
ed
correctly, resulting in non-functional debug sessions. Fix
ed
. Firmware: J-Link ULTRA+ V4: RISC-V: Reset on SiFive FE310 device (mount
ed
on HiFive1 boards) could fail with timeout error. Fix
ed
. Firmware: J-Link ULTRA+ V4: Warning "J-Link low on memory" could occur after using SPI functionality of J-Link. Fix
ed
. Firmware: J-Link ULTRA+ V4: When connecting via IP and using RTT it could happen that J-Link FW crash
ed
and reboot
ed
if the PC did not
exit
the controlling process in a clean way. Fix
ed
. Firmware: J-Link-OB-K22-SiFive: Linux: When using both VCOM ports extensively under special circumstances it could happen that the USB communication lock
ed
up. Fix
ed
. Firmware: J-Trace PRO V1 Cortex-M: When connecting via IP and using RTT it could happen that J-Link FW crash
ed
and reboot
ed
if the PC did not
exit
the controlling process in a clean way. Fix
ed
. Firmware: J-Trace PRO V2 Cortex-M: Correct
ed
typo on th webserver trace configuration page. Firmware: J-Trace PRO V2 Cortex-M: When connecting via IP and using RTT it could happen that J-Link FW crash
ed
and reboot
ed
if the PC did not
exit
the controlling process in a clean way. Fix
ed
. Firmware: J-Trace PRO V2 Cortex: Correct
ed
typo on th webserver trace configuration page. Firmware: J-Trace PRO V2 Cortex: When connecting via IP and using RTT it could happen that J-Link FW crash
ed
and reboot
ed
if the PC did not
exit
the controlling process in a clean way. Fix
ed
. Flasher ARM / PRO / Portable PLUS: Init/
Exit
step BNE and BEQ could jump to #step + 1. Fix
ed
. Flasher ARM / PRO / Portable PLUS: Open Flashloader RAM
Code
s in stand-alone-mode can be >12kB now. Flasher ARM / PRO / Portable PLUS: Stand-alone mode did not work for some ARM devices. Introduc
ed
in V6.47b. Fix
ed
. Flasher ARM / PRO: Reading or writing memory in J-Link mode via JTAG caus
ed
the firmware to hang and report a USB timeout. Fix
ed
. Flasher: Add
ed
stand-alone mode support for Traveo2 CYT2B and CYT4B devices. Flasher: Add
ed
stand-alone mode support for Traveo2 CYT2B and CYT4B devices. GDBServer: Under special circumstances, a remote "g" packet error popp
ed
up when using the GDBServer with Cortex-AR or MIPS. Fix
ed
. GUI applications (Linux): The directory the application was execut
ed
from affect
ed
the behavior of the application. Fix
ed
. J-Flash Lite: Updat
ed
to select the flash base address of the select
ed
device by default as "Prog. Addr." instead of always 0x00000000. J-Flash Lite: Updat
ed
to select the flash base address of the select
ed
device by default as "Prog. Addr." instead of always 0x00000000. J-Flash SPI: Add
ed
flash programming support for ISSI IS25LP016D SPI Flash. J-Flash SPI: Add
ed
flash programming support for ISSI IS25LP016D SPI Flash. J-Flash SPI: Add
ed
flash programming support for ISSI IS25LP080D SPI Flash. J-Flash SPI: Add
ed
flash programming support for ISSI IS25LP080D SPI Flash. J-Flash SPI: Add
ed
flash programming support for ISSI IS25WP016D SPI Flash. J-Flash SPI: Add
ed
flash programming support for ISSI IS25WP016D SPI Flash. J-Flash SPI: Add
ed
flash programming support for ISSI IS25WP080D SPI Flash. J-Flash SPI: Add
ed
flash programming support for ISSI IS25WP080D SPI Flash. J-Flash SPI: Add
ed
flash programming support for ISSI IS25WP128D SPI Flash. J-Flash SPI: Add
ed
flash programming support for ISSI IS25WP128D SPI Flash. J-Flash SPI: Licenses that have been burn
ed
into J-Link via J-Link Commander "license add" command were not detect
ed
properly. Fix
ed
. J-Flash: Generat
ed
data files could be unnecessarily big. Fix
ed
. J-Flash: Generat
ed
data files could be unnecessarily big. Fix
ed
. J-Flash: Improv
ed
error messages during the check, if the data fits into the flash memory. J-Flash: Improv
ed
error messages during the check, if the data fits into the flash memory. J-Flash: Licenses that have been burn
ed
into J-Link via J-Link Commander "license add" command were not detect
ed
properly. Fix
ed
. J-Link BASE/
ED
U/PLUS: SPI flash programming with J-Flash SPI was very slow. Fix
ed
. J-Link Commander: RISC-V: Add
ed
to the list of suggest
ed
/available interfaces JFlash: Add
ed
command line parameter "?" (Same functionality as "-?"). JFlash: Add
ed
command line parameter "?" (Same functionality as "-?"). JFlashSPI: Add
ed
SPI flash programming support for ISSI IS25LP016D SPI flash. JFlashSPI: Add
ed
SPI flash programming support for ISSI IS25LP016D SPI flash. JFlashSPI_CL: Add
ed
command line parameter "?" (Same functionality as "-?"). JFlashSPI_CL: Add
ed
command line parameter "?" (Same functionality as "-?"). JLinkRTTClient: Add
ed
command line parameter "?" (Same functionality as "-?"). JLinkRTTClient: Add
ed
command line parameter "?" (Same functionality as "-?"). JLinkRTTLogger: Add
ed
command line parameter "?" (Same functionality as "-?"). JLinkRTTLogger: Add
ed
command line parameter "?" (Same functionality as "-?"). JLinkSTR91x: Add
ed
command line parameter "?" (Same functionality as "-?") and implement
ed
"help" functionality which returns the available command line parameters. JLinkSTR91x: Add
ed
command line parameter "?" (Same functionality as "-?") and implement
ed
"help" functionality which returns the available command line parameters. JTAGLoad: Add
ed
command line parameters "?" and "-?" (Same functionality as "/?"). JTAGLoad: Add
ed
command line parameters "?" and "-?" (Same functionality as "/?"). P
Code
s: Chang
ed
an ambiguous J-Link report output. P
Code
s: Resolv
ed
an issue where some Cypress PSoC4 devices would not unlock automatically when connecting to them. Fix
ed
. Package: USB driver for VCOM: Under very special circumstances bluescreens could occur when using VCOM. Fix
ed
. (Driver update only applies to Windows Vista and later. Windows XP still uses the old driver as the new one is not compatible to Windows XP anymore) RTTClient: Connecting to existing session did not work correctly on MacOS. Fix
ed
. RTTClient: Linux: Ubuntu: Attaching to existing debug session did not work properly. Fix
ed
. RTTLogger (Linux): Using logrotate lead to null characters being print
ed
before RTT data. Fix
ed
., RTTViewer: Add
ed
'All terminals' message in case of connection loss. RTTViewer: Add
ed
information display on how to correctly enter RTT control block search range. RTTViewer: Echo to Terminal 0 / 'All terminals' was not working correctly. Fix
ed
. RTTViewer: Fix
ed
'Attach to existing session' mode for Windows, MacOS and Linux. RTTViewer: Fix
ed
typo. RTTViewer: Improv
ed
J-Link connect/ disconnect sequence. RTTViewer: Improv
ed
handling for data logging. RTTViewer: Improv
ed
handling for terminal logging. RTTViewer: Improv
ed
log messages when connecting to J-Link. RTTViewer: Improv
ed
log output. RTTViewer: Improv
ed
reconnecting for attach mode. RTTViewer: Improv
ed
the handling in case reading of RTT data fail
ed
. RTTViewer: In some occasions, the CL option '--autoconnect' did not work. Fix
ed
. RTTViewer: In some rare occasions, clearing a terminal could crash the application. Fix
ed
. RTTViewer: Linux: Ubuntu: Option "Attaching to existing debug session" did not work properly. Fix
ed
. RTTViewer: Some ANSI CSI sequences caus
ed
the application to crash. Fix
ed
. RTTViewer: The '--autoconnect' CL option caus
ed
the application to crash. Fix
ed
. RemoteServer: Command line options '-select USB=' and '-SelectEmuBySN ' did not work correctly. Fix
ed
. SDK (Windows): Linking against the *.lib files with MinGW did throw errors reg. undefin
ed
references to "__security_check_cookie" and "__GSHandlerCheck". Fix
ed
. SDK: JLINKARM_EraseChip() did not use the EraseChip command to erase the entire flash but the EraseSector command. Chang
ed
. SDK: JLINKARM_EraseChip() did not use the EraseChip command to erase the entire flash but the EraseSector command. Chang
ed
. Trace: Under certain circumstances backtrace was not showing for targets with PTM. Fix
ed
. UM08002: Chapter "Python support" add
ed
. UM08002: Chapter "Python support" updat
ed
. Section "API Functions": Add
ed
"FlashDownload" description
BUS Hound
Bus Hound 5.0
Copyright (C) Perisoft 2000-2003. All rights reserv
ed
worldwide.
Bus Hound is a powerful software bus analyzer for capturing I/O and protocol from devices. Features include:
Supports every version of IDE, SCSI, USB, 1394
Supports all devices such as hard drives, DVD, mice, scanners, web cams, and everything else
Supports Windows 95, 98, Me, NT 4.0, 2000, 2003, XP and XP Emb
ed
d
ed
Capture megabytes of I/O limit
ed
only by available memory
Automatically stop the capture upon a trigger condition
Measure individual read, write, and isochronous device performance
Captures device driver packets such as IRP’s
Filter what type of phases are captur
ed
Run on an unlimit
ed
number of machines at the same time
Capture any number of devices in parallel, regardless of bus type
Fits on a diskette for easy transportability and quick downloads
Drag and drop captur
ed
data to other products in html format
Save captur
ed
data to a text file or zip file
Simple device selection from a graphical tree of devices
Capture the system startup process
Arrange captur
ed
data to user preferences such as the byte width per line
View low level protocol including SCSI sense data and USB setup packets
View microsecond resolution timing of each phase
Watch I/O on screen in real time as it happens
Pure software solution--no extra hardware or system changes ne
ed
ed
The Capture Window
Commands sent to devices consist of one or more phases. Examples of phases are command bytes, data bytes, and status bytes. Bus hound logs each phase complete with timing information and a description of the content.
Capture columns
Below are descriptions of information in each column of the Capture Window:
Device
Device ID. Each device is assign
ed
a number which can be match
ed
up with devices in the Devices Window. The first detect
ed
device on the system is Device ID 0, the second is Device ID 1, and so on. This field is useful in the event multiple devices are being captur
ed
in parallel.
For USB devices, the endpoint is also display
ed
(eg: 4.1 = device 4, endpoint 1).
Phase
Phase type. Please refer to the table for details of each phase type.
Phase Description
ADDR 8 byte 1394 transfer address
ATI 7 byte ATA task file return
ed
from an IDE device
ATO 7 byte ATA task file sent to an IDE device
ATP Windows ATA_PASS_THROUGH data structure
CDB SCSI command descriptor block
(Known as a packet command for ATAPI devices)
CTL 8 byte setup packet of a USB control transfer
DI Data In (Device to PC transfer)
DO Data Out (PC to device transfer)
IOR Windows VXD I/O Request data structure
IRB Windows 1394 I/O Request Block data structure
IRP Windows I/O Request Packet data structure
ISOC Isochronous transfer data bytes
LEN Data transfer length of a DI,DO, or ISOC phase in
decimal units. This field is off by default and can be
turn
ed
on from the settings Window
LOCK 1394 lock transaction
NSTS Windows 4 byte kernel mode NTSTATUS field
RSET Bus or device reset
RSTS Windows VXD IOR status
SNS SCSI request sense data
SPT Windows SCSI Pass Through data structure
SRB Windows SCSI Request Block (SRB) data structure
SSTS Windows 1 byte SCSI Request Block (SRB) status
STAK Windows IO_STACK_LOCATION data structure
URB Windows USB Request Block (URB) data structure
USTS Windows 4 byte USBD_STATUS
code
Data
Data bytes associat
ed
with the phase. Examples are command bytes, data transfer bytes, and status bytes.
Description
A text description of this phase provid
ed
for your convenience.
Delta
Elaps
ed
time from the previous phase to the current phase. The following table describes the units of the time format.
Name Units
us Microseconds
ms Milliseconds
sc Seconds
mn Minutes
hr Hours
dy Days
Cmd.Phase.Ofs(rep)
This unique tag identifies the exact position within the captur
ed
data. All values are in decimal.
Cmd is the command number. Commands start at 1 and increment for each new command sent to a device.
Phase is the phase number within this command. A command is usually compos
ed
of multiple phases such as data transfer and status. This value starts at 1 and increments for each new phase within the command.
Ofs is the byte offset of the data within this phase. This value starts at 0 and increments for each byte of data in the data transfer.
Rep is the number of identical commands issu
ed
back to back. The repeat count feature can be turn
ed
off by deselecting the “Merge Repeat
ed
Commands” check box in the settings Window.
Date
Date the phase occurr
ed
in year/month/day format.
Time
Time the phase occurr
ed
in hour:minute:second.millisecond format. The hour ranges from 0 to 23 (military time).
Capturing the system startup process
If the Bus Hound application is
exit
ed
while the Run button is press
ed
, the device driver portion of Bus Hound continues capturing data. In the event the system is restart
ed
, it will start capturing data early in the system startup process.
If Bus Hound is
exit
ed
while stopp
ed
, no capture will occur until returning to the product and pressing Run.
Customizing the capture display
The column order can be modifi
ed
by dragging the column headers to the desir
ed
position. The byte width per line can be 1, 2, 4, 8, 16, or 32 bytes and is bas
ed
on the width of the window. These settings are respect
ed
for Saving and drag & drop.
Searching
Searching can be perform
ed
from the capture window in either the up or down direction by typing the search string in the lower left
ed
it box follow
ed
by pressing the up or down arrow to search up or down respectively. If the search string is not found, the trace position is not chang
ed
. Searching is not case sensitive.
Drag and Drop
To use drag and drop, first select the desir
ed
range of lines by clicking on the starting line, then hold down shift and click the ending line. The data can now be dragg
ed
using the mouse to another product.
Pressing control-c copies the select
ed
lines to the clipboard.
Command Overlap
Overlapp
ed
commands are identifi
ed
when a command starts before previous commands to the same device have complet
ed
. It is possible for Commands to be overlapp
ed
at the I/O subsystem level (which Bus Hound displays), but not at the hardware level.
Multiple DI/DO phases
Windows 9x only: if multiple DI/DO phases are list
ed
for the same command, it indicates the transfer was split across multiple memory address ranges
PS2 Mouse data format
Below is the format of the data return
ed
in the data in phase for PS/2 mice. This is known as the MOUSE_INPUT_DATA structure in the Windows DDK:
Offset Length Content
0 2 Not us
ed
2 2 Position type:
0000h = relative position
0001h = absolute position
4 2 Button flags:
0001h = left button down
0002h = left button up
0004h = right button down
0008h = right button up
0010h = middle button down
0020h = middle button up
0040h = button 4 down
0080h = button 4 up
0100h = button 5 down
0200h = button 5 up
0400h = mouse wheel
6 2 Mouse wheel data
8 4 Not us
ed
12 4 X position
16 4 Y position
20 4 Device specific information
PS2 Keyboard data format
Below is the format of the data return
ed
in the data in phase for PS/2 keyboards. This is known as the KEYBOARD_INPUT_DATA structure in the Windows DDK:
Offset Length Content
0 2 Not us
ed
2 2 Scan
code
of key
4 2 Flags:
0000h = key press
ed
0001h = key releas
ed
0002h = extend
ed
scan
code
E0
0004h = extend
ed
scan
code
E1
6 2 Not us
ed
8 4 Device specific information
The Save Window
The Save button saves all captur
ed
data to the specifi
ed
file. The format of the file can be either a text file containing standard ASCII characters or a Zip file. The data will be sav
ed
in the same column order and byte width as seen on the screen.
A comment can be provid
ed
that will be plac
ed
into the header of the captur
ed
data. The current date and time can be includ
ed
in the comment by inserting %c anywhere inside the comment. If saving to a zip file, the comment is also us
ed
for the zip file comment.
The Settings Window
This Window allows you to customize the capture process. Checkbox options in this window are appli
ed
instantly. Numeric entries are appli
ed
by pressing the apply button, switching to another window, or
exit
ing Bus Hound.
Buffer Size
Specifies the number of kilobytes of RAM to use for capturing data. The size is limit
ed
only by system RAM. If not enough RAM is available to satisfy the request
ed
size, the size is r
ed
uc
ed
to available RAM. If you ne
ed
to get as much space as possible, besides adding more RAM to a system you can also try setting the buffer size before starting other applications. Note: allocating a very large buffer size under Windows 95/98/Me can take a minute.
Max Phase
Specifies the maximum number of bytes that will be captur
ed
on each phase. Example: if Max Phase is set to 32 bytes and a 64K read operation occurs, only the first 32 bytes of the read will be captur
ed
. This option is useful for keeping the size of the captur
ed
data to a minimum.
Stop When...
These are triggers that allow the capture to automatically stop when the specifi
ed
condition is met. Any combination of triggers may be select
ed
. When a trigger condition is met, the capture stops and the trigger text is highlight
ed
in r
ed
.
Any Other Error stops the capture when an error occurs that does not fall into any of the other categories.
Buffer Full stops the capture when Bus Hound's buffer is full. If Buffer Full is deselect
ed
, capturing continues after the buffer is full, keeping the most recently captur
ed
data.
Bus Reset stops the capture when a bus reset occurs.
Data Overrun stops the capture when a data overrun or data underrun occurs.
Hardware Error stops the capture when a hardware error occurs.
Invalid Command stops the capture when an invalid command is issu
ed
.
M
ed
ia Error stops the capture when a device reports a m
ed
ia error such as a bad sector.
No M
ed
ia stops the capture when a device reports no m
ed
ia is present.
Not Ready stops the capture upon a not ready, timeout, or busy condition.
Text Pattern / Hex Pattern stops the capture when the specifi
ed
data pattern is detect
ed
in the captur
ed
data. For text patterns, the match is case sensitive. The pattern is check
ed
against the data transferr
ed
in any phase including commands, data, and status.
Vendor Error stops the capture when a vendor unique error occurs.
Windows Error stops the capture when an operating system type error occurs.
Phases to Capture
Contains a list of all the phase types Bus Hound can capture. Placing a check mark next to a phase allows it to be captur
ed
. Removing a check mark next to a phase results in the phase not being captur
ed
. This option is useful for filtering out phases that are not of interest or including special operating system phases that are off by default.
To the right of the check box, a white circle may appear. This indicates the phase has been detect
ed
and exists in the captur
ed
data. If the circle blinks bright green, it is a real time activity light indicating the phase has occurr
ed
and has been captur
ed
.
Merge Repeat
ed
Commands
When select
ed
, if a command occurs that is identical to the previous command, the new command will not be logg
ed
separately. Instead, the repeat count of the previous command is increment
ed
. This option is useful for compacting the captur
ed
data when a device is being continually poll
ed
with the same command.
Enable Sounds
If this option is enabl
ed
, Bus Hound will make an audible "ping" if the capture, settings, or devices window is up and a trigger condition is met.
Columns to Display
Place a checkmark in the boxes to include the desir
ed
columns in the Capture Window. The select
ed
columns will also be includ
ed
in drag & drop and save operations. See the section “The Capture Window” for more details about each column.
The Devices Window
The list of devices represents every device on the system which Bus Hound supports. The list automatically refreshes to reflect new or remov
ed
devices. To select/deselect a device to capture, click in the check box next to the device. The selection will be appli
ed
instantly.
Each device is assign
ed
a number which is in parenthesis before the name of the device. This number is display
ed
in the capture window under the "Device" column. The number reflects the order in which the device was add
ed
to the system.
If a device is display
ed
in a light font, it indicates the device is not currently present on the system.
Capture new devices
Selecting this checkbox will automatically capture data for new devices that are detect
ed
. This feature is useful for capturing the first commands sent to hot plugg
ed
devices.
Device Properties
This window pane displays details about the device such as the performance. The performance is calculat
ed
by summing the total bytes transferr
ed
divid
ed
by the total elaps
ed
time of the commands. The performance statistics are clear
ed
when the run button is press
ed
in the Capture window.
Send Commands
You can send your own custom commands to a device using Bus Commander. To start Bus Commander, highlight a device with the mouse and click the “Send Commands” button or simply double click the device. Bus Commander is a very powerful complementary tool that lets you submit USB, 1394, ATA and SCSI commands to devices. You can also perform operations like bus resets and hardware port i/o.
Files Install
ed
BUSHOUND.EXE - Bus Hound application
BUSCMDR.EXE - Bus Commander application
BHUNINST.EXE - uninstaller
BHLOG.EXE - capture to disk tool (site license version only)
BHOUND3.VXD - device driver for Windows 95, 98, Me
BHOUND4.SYS - device driver for Windows NT 4.0
BHOUND5.SYS - device driver for Windows 98, Me, 2000, 2003, XP
HELP.RTF - product help file (this file)
Site License
The site license version of Bus Hound includes the bhlog.exe command line tool in the folder where Bus Hound is install
ed
. bhlog spools captur
ed
data to a disk file in real time. This tool raises the maximum capture size from available RAM to available disk space. bhlog also has the ability to retain captur
ed
data in the event a system freezes or reboots by directing captur
ed
data to a file on a network drive.
FAQ
1. What type of I/O is captur
ed
?
Bus Hound takes a snap shot of packets sent across the bus. This includes commands, data, status, and timing of each command. Bus Hound does not monitor individual hardware signals.
2. Will Bus Hound change the behavior of my devices?
No. Bus Hound simply “listens” for packets. Bus Hound does not alter commands, does not send its own commands, does not replace any system drivers, and does not access the hardware. The system and devices will operate identically whether Bus Hound is install
ed
or not.
3. Will Bus Hound degrade system performance?
Customers capturing data from extremely fast devices in parallel have been impress
ed
by Bus Hound’s ability not to effect performance. Bus Hound is even more innocuous when in the stopp
ed
state.
4. Which devices are support
ed
?
All IDE, SCSI, USB and 1394 devices are support
ed
including disk drives, mice, scanners, web cams, and everything else. Devices that emulate one of these buses are also support
ed
such as certain parallel port devices.
5. Why are there duplicate devices?
For some devices, Windows first forms high level packets that are then translat
ed
into low level packets which are in turn sent to the hardware. Bus Hound shows several devices so you can choose which level of I/O you wish to capture.
6. What does capturing I/O for a controller do?
Some controllers receive commands and some do not. You can experiment capturing data for a controller to see if the packets are of interest.
7. What if Bus Hound does not show a device?
No devices are display
ed
when the system is start
ed
in safe mode. This is a safety feature to keep safe mode as clean as possible.
Devices which are mark
ed
with a problem in device manager are not display
ed
.
SCSI adapters are not display
ed
under Windows 95/98/Me unless they have one or more devices attach
ed
.
8. Why are some devices gray
ed
out?
A gray
ed
out device indicates it is currently not attach
ed
to the system.
9. Windows 95/98/Me crashes when pressing run. What do I do?
Due to limitations in the Windows 9x architecture, if too many device drivers ask to receive notification of I/O completion, the system will crash. Microsoft device drivers and other install
ed
software such as Bus Hound ne
ed
such notifications. To resolve this, remove software likely to have additional device drivers install
ed
for the device. For CD/DVD drives, an easy solution is to rename the legacy scsi1hlp.vxd to scsi1hlp.bak which is in the windows/system/iosubsys folder.
10. Why am I not able to capture all 1394 events?
Some 1394 devices Bus Hound displays are logical devices such as AV/VHS devices. Select devices further up the tree to capture bus activity for such devices.
While Bus Hound logs every isochronous transaction, there is no practical way for Bus Hound to see every asynchronous transaction. If you ne
ed
to see more 1394 activity, note Bus Hound can capture a great deal more in operating systems prior to XP, particularly for SBP-2 devices.
11. Why am I not seeing task file (ATA) commands for IDE hard drives?
Bus Hound captures ATA commands only when an application or driver explicitly sends an ATA command (eg: SMART, IDENTIFY). For normal file system requests, Bus Hound captures SCSI CDB's instead of ATA commands due to the monolithic nature of the Windows IDE device driver. Note the CDB's captur
ed
have a one to one relationship with ATA commands and can be easily translat
ed
to their native ATA equivalent. Also note the data captur
ed
with the CDB is identical to the ATA data transfer.
12. Where can I get more detail
ed
information on the captur
ed
data?
For your convenience, please visit www.perisoft.net/engineer for handy reference data and specifications. Also please note the following resources:
Specification Location
USB www.usb.org
SCSI www.t10.org
IDE, ATA, ATAPI www.t13.org
1394, Firewire www.1394ta.org or www.ieee.org
Windows DDK www.microsoft.com/ddk
14. Where do I get support?
Visit www.perisoft.net. Any questions, comments, or problem reports on the free or full version are welcome.
Microsoft.CppCommon.targets(209,5): error MSB6006: “cmd.exe“
exit
ed
with
code
3.
解决办法: 找到对应的vcxproj, 查找CustomBuild,看里面的cmd.exe配置和当前环境变量设置的是否一致,如果不一致改回一致就OK
dev-stack安装openstack
虚拟机桥接网络的问题总结 关于VirtualBox在桥接模式下无法联网 解决方案 VirtualBox虚拟机几种网络连接方式介绍 Ubuntu输入ifconfig找不到IP地址,只有lo问题 详细Ubuntu桥接模式网络配置过程 永久设置DNS: sudo apt install resolvconf sudo apt install openresolv https://blog.csdn.net/weixin_44773984/article/details/113252269 https://bl
qt 部署 错误_在Android应用程序上部署Qt时出错
我正在尝试运行我的第一个Qt Android应用程序,并且遵循了本教程:但是,在我运行它之后,我得到了这个错误:i686-linux-android-g++: error: unrecogniz
ed
command line option '-marm' make: ***[main.o] Error 1 21:33:42: The process "make"
exit
ed
with
code
...
Qt
16,175
社区成员
26,581
社区内容
发帖
与我相关
我的任务
Qt
Qt 是一个跨平台应用程序框架。通过使用 Qt,您可以一次性开发应用程序和用户界面,然后将其部署到多个桌面和嵌入式操作系统,而无需重复编写源代码。
复制链接
扫一扫
分享
社区描述
Qt 是一个跨平台应用程序框架。通过使用 Qt,您可以一次性开发应用程序和用户界面,然后将其部署到多个桌面和嵌入式操作系统,而无需重复编写源代码。
社区管理员
加入社区
获取链接或二维码
近7日
近30日
至今
加载中
查看更多榜单
社区公告
暂无公告
试试用AI创作助手写篇文章吧
+ 用AI写文章