Drivers Thales E-transactions USB Devices

Safenet usb device driver version 11i v2 revision b. The world relies on thales to protect and secure access to your most sensitive data and software wherever it is created, shared or stored. 20 protection interfaces for that allows your own setup process.
As 2G and 3G networks phase out around the world, the Cinterion DGL61-W USB Device Gateway offers a simple and powerful solution for retrofitting existing IoT applications while providing seamless evolution to LTE Cat 1. The innovative USB 2.0 dongle provides out-of-the-box 4G connectivity with 2G/3G fallback for global coverage from a single SKU.

Vendor: Thales E-Transactions / Device: medCompact. Sorry, no drivers found for this device. The nShield Edge hardware security module (HSM) is a full-featured, portable USB HSM designed for low-volume transaction environments. It’s capable of encryption and key protection and is ideally suited for off-line key generation for certificate authorities (CAs) as well as development and Bring Your Own Key (BYOK) environments.

Just reinstalled
ehsx_rev03.001_arn0000014_install-cd
and it showed all the usb-devices.
But when I reset the ***** it all wanished.
Reconnecting now, only give me this:
Unknown Device
(Standard USB Host Controller)
Port_#0002.Hub_#0004
Windows has stopped this device because it has reported problems. (Code 43)
Cinterion
EHS6
REVISION 03.001
^SYSLOADING
^SYSSTART
+PBREADY
^SCFG: 'Call/Ecall/Pull****','0't','20000'
^SCFG: 'Call/Ecall/SessionTimeout','20000'
^SCFG: 'Call/Ecall/StartTimeout','5000'
^SCFG: 'Call/Speech/Codec','0'led'
^SCFG: 'GPRS/AutoAttach','enabled'
^SCFG: 'Gpio/****/ASC1','std'
^SCFG: 'Gpio/****/DAI','gpio'
^SCFG: 'Gpio/****/DCD0','std'
^SCFG: 'Gpio/****/DSR0','std'
^SCFG: 'Gpio/****/DTR0','std'
^SCFG: 'Gpio/****/FSR','gpio'
^SCFG: 'Gpio/****/HSIC','rsv'o'
^SCFG: 'Gpio/****/PULSE','gpio'
^SCFG: 'Gpio/****/PWM','gpio'
^SCFG: 'Gpio/****/RING0','std'
^SCFG: 'Gpio/****/SPI','rsv'
^SCFG: 'Gpio/****/SYNC','std'
^SCFG: 'Ident/Manufacturer','Cinterion'
^SCFG: 'Ident/Product','EHS6'
^SCFG: 'MEShutdown/Fso','0'
^SCFG: 'MEShutdown/sVsup/threshold','0','0'
^SCFG: 'MEopMode/CFUN','0','1'
^SCFG: 'MEopMode/Dormancy','0','0'
^SCFG: 'MEopMode/SoR','off'
^SCFG: 'Radio/Band','511'
^SCFG: 'Radio/Mtpl','0'
^SCFG: 'Radio/OutputPowerReduction','4'
^SCFG: 'Serial/Interface/Allocation','1','1'
^SCFG: 'Serial/USB/DDD','0','0','0409','1E2D','0058','Cinterion Wireless Modules','EHx','
^SCFG: 'Tcp/IRT','3'
^SCFG: 'Tcp/MR','10'
^SCFG: 'Tcp/OT','6000'
^SCFG: 'Tcp/WithURCs','on'
^SCFG: 'Trace/Syslog/OTAP','0'
^SCFG: 'URC/Ringline','local'
^SCFG: 'URC/Ringline/ActiveTime','2'
^SCFG: 'Userware/Autostart','1'
^SCFG: 'Userware/Autostart/Delay','80'
^SCFG: 'Userware/DebugInterface','0.0.0.0','0.0.0.0','0'
^SCFG: 'Userware/DebugMode','off'
^SCFG: 'Userware/Passwd',
^SCFG: 'Userware/Stdout','usb1','off'
^SCFG: 'Userware/Watchdog','0'
The module work fine using
at^SCFG='Userware/Stdout','asc1','off'
but not
at^SCFG='Userware/Stdout','usb1','off'
at^SCFG='Userware/Stdout','null','off'
Setting stdout to usb1, the answer is: not recognized
Br morten

-->

This topic provides information for client driver developers about the tracing and logging features for Universal Serial Bus (USB). This information is provided for the benefit of those who develop and debug USB devices. It includes information on how to install the tools, create trace files, and analyze the events in a USB trace file. The topic assumes that you have a comprehensive understanding of the USB ecosystem and hardware that is required to successfully use the USB tracing and logging features.

To interpret the event traces, you must also understand the Windows USB host-side drivers in Windows, the official USB Specifications, and the USB Device Class Specifications.

About Event Tracing for Windows

Event Tracing for Windows (ETW) is a general-purpose, high-speed tracing facility that is provided by the operating system. It uses a buffering and logging mechanism that is implemented in the kernel to provide a tracing mechanism for events that are raised by both user-mode applications and kernel-mode device drivers. Additionally, ETW provides the ability to dynamically enable and disable logging, which makes it easy to perform detailed tracing in production environments without requiring reboots or application restarts. The logging mechanism uses per-processor buffers that are written to disk by an asynchronous writer thread. This buffering allows large-scale server applications to write events with minimum disturbance.

ETW was introduced in Windows 2000. Since then, various core operating system and server components have adopted ETW to instrument their activities. ETW is now one of the key instrumentation technologies on Windows platforms. A growing number of third-party applications use ETW for instrumentation, and some take advantage of the events that Windows provides. ETW has also been abstracted into the Windows preprocessor (WPP) software tracing technology, which provides a set of easy-to-use macros for tracing printf-style messages for debugging during development.

ETW was significantly upgraded for Windows Vista and Windows 7. One of the most significant new features is the unified event provider model and APIs. In short, the new unified APIs combine logging traces and writing to the Event Viewer into one consistent, easy-to-use mechanism for event providers. At the same time, several new features have been added to ETW to improve the developer and end-user experiences.

For more information about ETW and WPP, see Event Tracing and Event Tracing for Windows (ETW).

USB Support for ETW Logging

USB is one of the most prevalent means of connecting an ever-increasing variety of peripheral devices to PCs. There is a very large installed base of USB host PCs and USB peripheral devices, and system vendors, device vendors, and end users expect and demand that USB devices operate flawlessly at the system and device level.

The large installed base and proliferation of USB devices have uncovered compatibility issues between the Windows USB software stack, the USB host controller, and USB devices. These compatibility issues cause problems for customers such as device operation failures, system hangs, and system crashes.

It has been difficult or impossible to investigate and debug USB device issues without direct access to the system, and/or devices, or in some cases a system crash dump. Even with full access to the hardware and a crash dump, extracting the relevant information has been a time-intensive technique that is known only by a few core USB driver developers. You can debug USB problems by using hardware or software analyzers, but they are very expensive and are available to only a small percentage of professionals.

Drivers Thales E-transactions USB Devices

USB ETW Support in Windows 7

In Windows 7, ETW provides an event logging mechanism that the USB driver stack can exploit to aid in investigating, diagnosing, and debugging USB-related issues. USB driver stack ETW event logging supports most or all debugging capabilities that are provided by the existing ad hoc logging mechanism in the USB driver stack, without any of its limitations. This translates into ease of debugging USB-related issues, which should provide a more robust USB driver stack in the long term.

We added ETW logging to the USB host controller drivers and to the USB hub driver in Windows 7. The USB host controller driver layer includes the host controller port driver (usbport.sys) and the miniport drivers (usbehci.sys, usbohci.sys, and usbuhci.sys). The USB hub driver layer consists of the USB hub driver (usbhub.sys). The USB driver ETW event providers are included in all editions and SKUs of Windows 7.

USB Hub Events
While USB event collection is enabled, the USB hub event provider reports the addition and removal of USB hubs, the device summary events of all hubs, and port status changes. You can use these events to determine the root cause of most device enumeration failures.
USB Port Events
While USB event collection is enabled, the USB port event provider reports I/O from client drivers, opening and closing of device endpoints, and miniport state transitions such as miniport start and stop. Logged I/O includes requests for the state of physical USB ports. State transitions on physical USB ports are one of the key initiators of activity in the core USB driver stack.

USB ETW Support in Windows 8

Windows 8 provides a USB driver stack to support USB 3.0 devices. The Microsoft-provided USB 3.0 driver stack consists of three drivers: Usbxhci.sys, Ucx01000.sys, and Usbhub3.sys. All three drivers work together to add native support to Windows for most USB 3.0 host controllers. The new driver stack supports SuperSpeed, high-speed, full-speed, and low-speed devices. The USB 2.0 driver stack is supported on Windows 8. Through event traces, the USB 3.0 driver stack provides a view into the fine-grained activity of the host controller and all devices connected to it.

USB Hub3 Events
While USB event collection is enabled, the USB Hub3 event provider reports the addition and removal of USB hubs, the device summary events of all hubs, port status changes, and power states of USB devices and hubs. Port status changes are state transitions on physical USB ports and are one of the key initiators of activity in the core USB driver stack. Hub3 reports the stages of the enumeration process, which point to the root cause most device enumeration failures. With the StateMachine keyword enabled, Hub3 reports the internal state machine activity for software device, hub, and port objects, which provide deeper visibility into the logic of the driver.
USB UCX Events
While USB event collection is enabled, the USB UCX event provider reports I/O from client drivers and opening and closing of device endpoints and endpoint streams. With the StateMachine keyword enabled, UCX reports internal state machine activity for host controller and endpoint objects, which provide deeper visibility into the logic of the driver.
USB xHCI Events
While USB event collection is enabled, the USB xHCI event provider reports the properties of the system's xHCI controllers and low-level details of xHCI operation. xHCI reports command requests sent to and completed by the xHCI hardware, including xHCI-specific completion codes.

In this section

Topic	Description
How to capture a USB event trace with Logman	This topic provides information about using the Logman tool to capture a USB ETW event trace. Logman is a tracing tool that is built into Windows. You can use Logman to capture events into an event trace log file.
Using activity ID GUIDs in USB ETW traces	This topic provides information about Activity ID GUIDs, how to add those GUIDs in the event trace providers, and view them in Netmon.
USB ETW traces in Netmon	You can view USB ETW event traces using Microsoft Network Monitor, also referred to as Netmon. Netmon does not parse the trace automatically. It requires USB ETW parsers. USB ETW parsers are text files, written in Network Monitor Parser Language (NPL), that describe the structure of USB ETW event traces. The parsers also define USB-specific columns and filters. These parsers make Netmon the best tool for analyzing USB ETW traces.
Using Xperf with USB ETW	This topic describes how to use Xperf with Netmon to analyze USB trace data.
USB ETW and Power Management	This topic provides a brief overview about using ETW to examine USB selective suspend state and identifying system energy efficiency problems by using the Windows PowerCfg utility.

Hunterconsultant635