
DS2490
12 of 50
Notes:
1. The only valid configuration values are 0 and 1 for the SET_CONFIGURATION request.
Configuration value 0 corresponds to the non-configured state.
2. Only the DEVICE and CONFIGURATION descriptor types are supported for the
GET_DESCRIPTOR request.
3. Interface 0 is the only valid interface value for the DS2490.
4. The only valid feature selector for the command is DEVICE_REMOTE_WAKE-UP.
5. The DS2490 is intended, at a minimum, to be partially bus powered. Remote wake-up can be enabled
or disabled. GET_STATUS requests to the device will return a logic 0 for the self-powered bit field
and the current state value for the remote wake-up bit.
6. There is no USB core level status information defined for interfaces in USB Specification v1.1. The
DS2490 will always return 0 value data for GET_STATUS requests to interfaces.
DS2490 Vendor-Specific USB Commands
Three different vendor-specific command types exist to control and communicate with the DS2490:
Control, Communication, and Mode. Control commands are used to manage various device functions
including the processing of communication commands, buffer clearing, and SW reset. Communication
commands are used for 1-Wire data and command I/O. Mode commands are used to establish the 1-Wire
operational characteristics of the DS2490 such as slew rate, low time, strong pullup, etc. Control,
Communication and Mode commands, like USB core requests, are communicated over the default control
pipe at EP0. With one exception as noted below, each command and any associated parameter data are
individually formatted into the 8-byte control transfer setup packet as follows:
bmRequestType
bRequest
wValue
wIndex
wLength
Request type bit map
(1 byte)
Command Type
(1 byte)
Command
(2 bytes)
See Note 1
Command Parameters
(2 bytes)
See Note 2
Notes:
1. The one exception to wValue formatting is for the READ STRAIGHT Communication command.
This command requires three parameter bytes that exceed the 2-byte parameter encoding space
available in the wIndex field. For this command only, the wValue field will be formatted as 1
command byte and 1 parameter byte. See the command description in Appendix 2 for details.
2. The wLength field is used by the GET COMM CMDS Control command to specify the number of
command/parameter bytes to retrieve from the DS2490 command FIFO; see the command description
for specifics. In all other cases the wLength field is not used and must be set to 0x0000.
The bit-mapped bmRequestType field identifies the characteristics of the USB command per Chapter 9
of the USB Specification. Fields included in this command describe the direction of the transfer, type of
request (core, class, or vendor specific) and the target of the command recipient (device, interface, or
endpoint). The only variation on the bmRequestType field for the different DS2490 vendor-specific
command will be for the transfer direction: host to device, or device to host; the recipient for all
commands will be the device.
The bRequest field contains a 1-byte constant identifying which of the three supported DS2490
command types is being sent. The command constants are defined in Appendix 4 and are summarized as
follows: