4.7.4
Answers from the Device to a Blank Check Command
The Host controller sends a GET_STATUS request to the device. Once internal blank check has
been completed, the device sends its status.
• If the device status is “OK”:
the device memory is then blank and the device waits for the next Host request.
• If the device status is “errCHECK_ERASED”:
the device memory is not blank. The device waits for an DFU_UPLOAD request to send the
first address where the byte is not 0xFF.
4.8
Reading Configuration Information or Manufacturer Information
The flow described hereafter allows the user to read the configuration or manufacturer
information.
4.8.1
Requests From Host
To start the programming operation, the Host sends DFU_DNLOAD request with the Read com-
mand in the data field (2 bytes).
DFU_DNLOAD
SETUP
OUT
IN
Read_command (2 bytes)
ZLP
Command Identifier
data[0]
data[1]
00h
data[2]
data[3]
data[4]
Description
Read Bootloader Version
Read Device boot ID1
Read Device boot ID2
Read Manufacturer Code
Read Family Code
00h
01h
01h
02h
Id_read_command
05h
30h
31h
60h
Read Product Name
Read Product Revision
61h
4.8.2
Answers from Bootloader
The device has two possible answers to a DFU_GETSTATUS request:
• If the chip is protected from program access, an “err_VENDOR” status is returned to the
Host.
• Otherwise, the device status is “OK“. The Host can send a DFU_UPLOAD request to the
device in order to get the value of the requested field.
12
7618C–AVR–07/08
ATMEL [ ATMEL ]
