RawNotes.txt Driver File Contents (tiglusbsrc.zip)

Link cable characteristics:
---------------------------

- Name: 'TI-GRAPH LINK USB'
- Manufacturer: 'Texas Instruments Corporated'


Link cable and/or driver behaviour:
-----------------------------------

- about write: we can send any number of bytes we want: from 1 to 32 bytes. 
Theoritically, it is better to send a block of bytes rather than byte per
byte. This is less power consuming for USB layers & OS.
Practically, transfers are more reliable if we send byte per byte because the
calc have enough time for replying.

- about read: we have to read systematically a 32 bytes block
(BULKUSB_MAX_TRANSFER_SIZE) (even if we know that we need to receive 4 bytes)
and process this block. If we try to read 2 bytes, the others will be lost.
Thus, we need to bufferize reading.

- it's better to close and reopen driver after each transfer or do a
RESET_PIPE (since the Close operation do a RESET_PIPE...).

- the ReadFile function (in non overlapped mode) can sometimes returns but
without any bytes. This strange case may appear, it's a quirk which appears
on some other platforms (Linux & Mac OS-X). In this case, simply retry a
ReadFile access.


Ti-Connect behaviour:
---------------------

- it seems that TI-Connect software systematically do a
URB_FUNCTION_RESET_PIPE on the IN & OUT pipes before attempting any transfer
but without closing the device.

- OUT packet are sent with the USBD_SHORT_TRANSFER_OK flag disabled (for
short packets such as 88 56 00 00).

- TI's driver does not use Power Management

- before attempting a transfer, TI-Connect reset both pipes (IN & OUT), try to
read 1024 bytes (probably for flushing IN pipe) and reset the pipes again.


Misc:
-----

- you can use regedit for increasing/decreasing the verbosity level in debug
mode,

- in the .INF file and/or the registry, MaxTransferSize MUST be equal to 32
(due to TIGL-USB),


- resetDevice (or IOCTL_BULKUSB_RESET_DEVICE) is dangerous: system becomes
unstable (reboot) !!!

- IOCTL_BULKUSB_RESET_PIPE: use it on a pipe handle, not on the device handle,

- the link cable seems not to work when my USB HP DeskJet is plugged,

- the USB sniffer/snoopy does not work under Windows XP. There is a way for
circumventing the problem but it requires 2 Windows XP machine. One is the
target machine (booted in debug mode), the other is the host machine. These
machines are connected together thru a NULL modem cable (see the WinDDK).



- some VC's .odl files (exdisp.odl, vidsvr.odl) have been fixed for compiling samples properly:
	- commented/removed in exdisp.odl: importlib(STDOLE_TLB);
	- commentedin vdisvr.odl: importlib(STDOLE_TLB); and importlib(STDTYPE_TLB);

- some DDK's .h files (ntverp.h and wdm.h) have been fixed for the same reason as above:
	- added in wdm.h: #define DBG 1 (enable debug mode)
	- commented/removed in wdm.h: #include "alpharef.h"
Download Driver Pack

How To Update Drivers Manually

After your driver has been downloaded, follow these simple steps to install it.

  • Expand the archive file (if the download file is in zip or rar format).

  • If the expanded file has an .exe extension, double click it and follow the installation instructions.

  • Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.

  • Find the device and model you want to update in the device list.

  • Double-click on it to open the Properties dialog box.

  • From the Properties dialog box, select the Driver tab.

  • Click the Update Driver button, then follow the instructions.

Very important: You must reboot your system to ensure that any driver updates have taken effect.

For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.

server: ftp, load: 1.03