AT90USB162 Atmel Corporation, AT90USB162 Datasheet - Page 8

• Manufacturer Part Number: AT90USB162
• Manufacturer: Atmel Corporation

Specifications of AT90USB162

• Flash (kbytes): 16 Kbytes
• Pin Count: 32
• Max. Operating Frequency: 16 MHz
• Cpu: 8-bit AVR
• Hardware Qtouch Acquisition: No
• Max I/o Pins: 22
• Ext Interrupts: 21
• Usb Transceiver: 1
• Usb Speed: Full Speed
• Usb Interface: Device
• Spi: 2
• Uart: 1
• Graphic Lcd: No
• Video Decoder: No
• Camera Interface: No
• Analog Comparators: 1
• Resistive Touch Screen: No
• Temp. Sensor: No
• Crypto Engine: No
• Sram (kbytes): 0.5
• Eeprom (bytes): 512
• Self Program Memory: YES
• Dram Memory: No
• Nand Interface: No
• Picopower: No
• Temp. Range (deg C): -40 to 85
• I/o Supply Class: 2.7 to 5.5
• Operating Voltage (vcc): 2.7 to 5.5
• Fpu: No
• Mpu / Mmu: no / no
• Timers: 2
• Output Compare Channels: 5
• Input Capture Channels: 1
• Pwm Channels: 4
• 32khz Rtc: No
• Calibrated Rc Oscillator: Yes

4.5.3
4.5.4
4.6
8
Programming the Flash or EEPROM Data
Device State
DFU_ABORT request
The state reported is the current state of the device up to transmission of the response. The val-
ues specified in the bState field are identical to those reported in DFU_GETSTATUS.
The DFU_ABORT request forces the device to exit from any other state and return to the
DFU_IDLE state. The device sets the OK status on receipt of this request. For more information,
see the corresponding state transition summary.
The firmware image is downloaded via control-write transfers initiated by the DFU_DNLOAD
class-specific request. The host sends between bMaxPacketSize0 and wTransferSize bytes to
the device in a control-write transfer. Following each downloaded block, the host solicits the
device status with the DFU_GETSTATUS request.
As described in the USB DFU Specification, "Firmware images for specific devices are, by defi-
nition, vendor specific. It is therefore required that target addresses, record sizes, and all other
information relative to supporting an upgrade are encapsulated within the firmware image file. It
is the responsibility of the device manufacturer and the firmware developer to ensure that their
devices can process these encapsulated data. With the exception of the DFU file suffix, the con-
tent of the firmware image file is irrelevant to the host."
Firmware image:
Table 4-7.
• 32 bytes: Command
• X bytes: X is the number of byte (00h) added before the first significant byte of the firmware.
• The firmware
• The DFU Suffix on 16 Bytes.
Offset
bmRequestType
The X number is calculated to align the beginning of the firmware with the flash page. X =
start_address [32]. For example, if the start address is 00AFh (175d), X = 175 [32] = 15.
bmRequestType
-0
-4
-5
-8
1010 0001b
1010 0001b
Field
dwCRC
bLength
ucDfuSignature
bcdDFU
DFU File Suffix
DFU_GETSTATE (5)
DFU_ABORT (6)
bRequest
bRequest
Size
4
1
3
2
Number
5 : 44h
6 : 46h
7 : 55h
Value
0100h
BCD
16
wValue
wValue
Zero
Zero
Description
The CRC of the entire file, excluding dwCRC
The length of this DFU suffix including dwCRC
The unique DFU signature field
DFU specification number
Interface (4)
Interface (4)
wIndex
wIndex
wLength
wLength
1
0
7618C–AVR–07/08
Data
Data
None
State