Method and driver for detecting glitches

• US 20020110150A1
• Filed: 12/19/2000
• Published: 08/15/2002
• Est. Priority Date: 12/19/2000
• Status: Active Grant

• Current Assignee: Micron Technology, Inc.
• Original Assignee: Intel Corporation
• Inventors: Keys, John S.
• Granted Patent: US 7,212,497 B2
• Time in Patent Office: Days
• US Class Current: 370/493
• CPC Class Codes: H04L 12/40058 Isochronous transmission

Abstract

A driver and methods therefore provide automated testing of USB client devices in real-time. The driver may use the layered driver or filter driver feature in Microsoft® Windows® Driver Model (WDM) layered architecture for the Microsoft Windows operating system. The driver may be inserted between the USB bus driver and the USB client driver stack. The driver may intercept, inspect, and modify the requests between the client drivers and the bus driver.

Claims

1. A method of detecting glitches in an isochronous data transfer, comprising:

determining if transferred data in a packet is silence data; and

reporting a silence fault when the transferred data is silence data.

2. The method of claim 1 further comprising:

determining if a data transfer request corresponding to the packet is an isochronous data transfer request;

determining if the data transfer request is being sent to a predetermined client device when the data transfer request is an isochronous data transfer request; and

attaching a callback notification to the data transfer request when the data transfer request is being sent to the predetermined client device.

3. The method of claim 1 further comprising:

determining a frame number of an expected start frame of the packet;

determining if a data transfer request corresponding to the packet is a first data transfer request;

when the data transfer request is not a first data transfer request,

determining a frame number of an actual start frame of the packet, and

determining if the frame number of the actual start frame is equal to the frame number of the expected start frame; and

reporting a stream fault when the frame number of the actual start frame is not equal to the frame number of the expected start frame.

4. The method of claim 3 further comprising reporting the expected start frame and the actual start frame.

5. The method of claim 1 further comprising reporting a start frame of the packet and a number of frames in the packet.

6. A method of detecting glitches in an isochronous data transfer, comprising:

determining a frame number of an expected start frame of a packet;

determining if a data transfer request corresponding to the packet is a first data transfer request;

when the data transfer request is not a first data transfer request,

determining a frame number of an actual start frame of the packet, and

determining if the frame number of the actual start frame is equal to the frame number of the expected start frame; and

reporting a stream fault when the frame number of the actual start frame is not equal to the frame number of the expected start frame.

7. The method of claim 6 further comprising:

determining if the data transfer request is an isochronous data transfer request;

determining if the data transfer request is being sent to a predetermined client device when the data transfer request is an isochronous data transfer request; and

attaching a callback notification to the data transfer request when the data transfer request is being sent to the predetermined client device.

8. The method of claim 6 further comprising reporting the expected start frame and the actual start frame.

9. A method of detecting glitches in an isochronous data transfer, comprising:

determining if a data transfer request corresponding to a packet is an isochronous data transfer request;

determining if the data transfer request is being sent to a predetermined client device when the data transfer request is an isochronous data transfer request;

attaching a callback notification to the data transfer request when the data transfer request is being sent to the predetermined client device;

determining a frame number of an expected start frame of the packet;

determining if a data transfer request corresponding to the packet is a first data transfer request;

when the data transfer request is not a first data transfer request,

determining a frame number of an actual start frame of the packet, and

determining if the frame number of the actual start frame is equal to the frame number of the expected start frame;

reporting a stream fault when the frame number of the actual start frame is not equal to the frame number of the expected start frame;

determining if the transferred data in the packet is silence data; and

reporting a silence fault when the transferred data is silence data.

10. The method of claim 9 further comprising reporting the expected start frame and the actual start frame along with the stream fault.

11. The method of claim 9 further comprising reporting a start frame of the packet and a number of frames in the packet along with the silence fault.

13. The filter driver of claim 12 wherein the request completion module further for:

determining if transferred data in the packet is silence data; and

reporting a silence fault when the transferred data is silence data.

15. The filter of claim 14 further comprising:

means for determining a frame number of an expected start frame of the packet;

means for determining if a data transfer request corresponding to the packet is a first data transfer request;

means for determining a frame number of an actual start frame of the packet and for determining if the frame number of the actual start frame is equal to the frame number of the expected start frame when the data transfer request is not a first data transfer request; and

means for reporting a stream fault when the frame number of the actual start frame is not equal to the frame number of the expected start frame.

17. The computer program product of claim 16 further comprising executable instructions that enable a computer to:

determine if a data transfer request corresponding to the packet is an isochronous data transfer request;

determine if the data transfer request is being sent to a predetermined client device when the data transfer request is an isochronous data transfer request; and

attach a callback notification to the data transfer request when the data transfer request is being sent to the predetermined client device.

18. The computer program product of claim 16 further comprising executable instructions that enable a computer to:

determine a frame number of an expected start frame of the packet;

determine if a data transfer request corresponding to the packet is a first data transfer request;

when the data transfer request is not a first data transfer request,

determine a frame number of an actual start frame of the packet, and

determine if the frame number of the actual start frame is equal to the frame number of the expected start frame; and

report a stream fault when the frame number of the actual start frame is not equal to the frame number of the expected start frame.

19. The computer program product of claim 18 further comprising executable instructions that enable a computer to report the expected start frame and the actual start frame.

20. The computer program product of claim 16 further comprising executable instructions that enable a computer to report a start frame of the packet and a number of frames in the packet.

12. A filter driver comprising:

a request dispatch module for,

determining if a data transfer request corresponding to a packet is an isochronous data transfer request,

determining if the data transfer request is being sent to a predetermined client device when the data transfer request is an isochronous data transfer request, and

attaching a callback notification to the data transfer request when the data transfer request is being sent to the predetermined client device; and

a request completion module for,

determining a frame number of an expected start frame of the packet,

determining if a data transfer request corresponding to the packet is a first data transfer request, and

when the data transfer request is not a first data transfer request,

determining a frame number of an actual start frame of the packet, and

determining if the frame number of the actual start frame is equal to the frame number of the expected start frame, and

reporting a stream fault when the frame number of the actual start frame is not equal to the frame number of the expected start frame.

14. A filter driver comprising:

means for determining if transferred data in a packet is silence data; and

means for reporting a silence fault when the transferred data is silence data.

16. A computer program product embodied on a tangible storage medium, the program comprising executable instructions that enable a computer to:

determine if transferred data in a packet is silence data; and

report a silence fault when the transferred data is silence data.