AVR079: STK600 Communication Protocol Features • Supported Commands and Command options • Command and Answer package formats 1 Introduction 8-bit Microcontrollers Application Note This document describes the STK®600 protocol. The firmware is distributed with AVR Studio® 4.14 or later. The definition of all commands, responses, parameters and other defined values can be found in the file “command.h”. This file can be downloaded from the Atmel® web site.
Overview 2.1 USB Communication The STK600 communicates with the PC through its USB interface. The USB interface utilizes two bulk endpoints; one IN and one OUT. The USB descriptors can be found in the Appendix. 2.2 Packet Format The PC sends commands to the STK600, which responds with an answer. Each command will generate an answer. Both commands and answers can be larger than the maximum packet size for the bulk endpoints, so a command or answer can be split into several IN/OUT packets.
AVR079 Table 3-1. Command format. Field Size Values Description Command ID 1 byte CMD_SIGN_ON Command id Size Values Description Answer id Table 3-2. Answer format. Field Answer ID 1 byte CMD_SIGN_ON Status 1 byte STATUS_CMD_OK Signature length 1 byte 6 Length of signature string 8 bytes “STK600” The signature string (not null-terminated) 3.2 CMD_SET_PARAMETER The host can set a multitude of parameters in the STK600. See the 11 Parameters for a description of each parameter.
Table 3-7. Answer format for one byte values if command succeeded. Field Size Values Description Answer ID 1 byte CMD_GET_PARAMETER Answer id Status 1 byte STATUS_CMD_OK A status value indicating success Parameter value 1 byte The parameter value Table 3-8. Answer format for two byte values if command succeeded.
AVR079 Table 3-12. Command format. Field Size Values Description Command ID 1 byte CMD_LOAD_ADDRESS Command id Address 4 byte The address, four bytes, MSB first For word-addressed memories (program flash), the Address parameter is the word address. If bit 31 is set, this indicates that the following read/write operation will be performed on a memory that is larger than 64KBytes. This is an indication to STK600 that a load extended address must be executed.
Table 3-16. Command format. Field Size Values Description Command ID 1 byte CMD_LOAD_RC_ID_TABLE Command id Total number of bytes to send (including the two revision bytes), MSB first NumBytes RC_ID_table 1 byte MSB rev byte ... 1 byte LSB rev byte ... 1 byte ID of a Routing Card ... 1 byte ID of SC allowed to use with the RC ... 1 byte Max VTG for that RC The three last lines above will be repeated until the whole table is sent. Table 3-17. Answer format.
AVR079 3.9 CMD_CHECK_TARGET_CONNECTION Table 3-20. Command format. Field Size Values Description Command ID 1 byte CMD_CHECK_TARGET_CONNECTION Command id Field Size Values Description Answer ID 1 byte CMD_LOAD_EC_ID_TABLE Answer id Answer value 1 byte Se table below. Status of target connection Status 1 byte STATUS_CMD_OK Table 3-21. Answer format. This command runs a target connection check and returns the status of the target connection.
4.1 CMD_ENTER_PROGMODE_ISP This command will make the target device enter programming mode. XML path: /AVRPART/ICE_SETTINGS/STK600/IspEnterProgMode/ Table 4-1. Command format.
AVR079 Table 4-3. Command format. Field Size Values Description Command ID 1 byte CMD_LEAVE_PROGMODE_IS P Command id preDelay 1 byte XML: preDelay Pre-delay (in ms) PostDelay 1 byte XML: postDelay Post-delay (in ms) Field Size Values Description Answer ID 1 byte CMD_LEAVE_PROGMODE_IS P Answer id Status 1 byte STATUS_CMD_OK This command will always return STATUS_CMD_OK Table 4-4. Answer format. 4.3 CMD_CHIP_ERASE_ISP This command will perform a chip erase on the target device.
Table 4-7. Command format.
AVR079 devices with page size bigger than what can be transferred to STK600 in one command, several CMD_PROGRAM_FLASH_ISP commands must be issued. In such a case, only the last command should have the Write Page mode bit set. NOTE: Only bit 0-6 are set in the XML file, because bit 7 is not constant and must be controlled by the PC software. When value polling is used to determine when a programming operation is complete, poll1 must be supplied.
4.6 CMD_PROGRAM_EEPROM_ISP See the CMD_PROGRAM_FLASH_ISP command. XML path: /AVRPART/ICE_SETTINGS/STK600/IspProgramEeprom/ 4.7 CMD_READ_EEPROM_ISP See the CMD_READ_FLASH_ISP command. XML path: /AVRPART/ICE_SETTINGS/STK600/IspReadEeprom/ 4.8 CMD_PROGRAM_FUSE_ISP This command programs the fuses of the target device. Table 4-13. Command format.
AVR079 Field Notes: Size Values Description 1. RetAddr indicates after which of the transmitted bytes on the SPI interface to store the return byte, as the SPI interface is implemented as a ring buffer (one byte out, one byte in). 2. cmd1, cmd2, cmd3 and cmd4 are the instruction bytes found in the SPI Serial Programming Instruction Set found in the device datasheet. Table 4-16. Answer format.
Field Size Values Description NumTx 1 byte 0-255 Number of bytes to transmit NumRx 1 byte 0-255 Number of bytes to receive RxStartAddr 1 byte Start address of returned data. Specifies on what transmitted byte the response is to be stored and returned. TxData 0-255 bytes The data to be transmitted. The size is specified by NumTx If the number of bytes to receive is greater than number of bytes to transmit, then the firmware will pad with the necessary 0x00 bytes.
AVR079 Table 5-2. Answer format (same for all results). Field Size Values Description Answer ID 1 byte CMD_ENTER_PROGMODE_PP Answer id Status 1 byte See table below A Result Value indicating the result of the operation Table 5-3. Valid Result Values for the answer to this command. Value Description STATUS_CMD_OK Operation succeeded STATUS_CMD_ FAILED Operation failed 5.2 CMD_LEAVE_PROGMODE_PP This command will make the target device leave programming mode if it succeeds.
Field Size Values Description Answer ID 1 byte CMD_CHIP_ERASE_PP Answer id Status 1 byte See table below A Result Value indicating the result of the operation Table 5-8. Valid Result Values for the answer to this command. Value Description STATUS_CMD_OK Operation succeeded STATUS_RDY_BSY_TOUT No response from target device within specified timeframe 5.4 CMD_PROGRAM_FLASH_PP This command will program data into the FLASH memory of the target device if it succeeds.
AVR079 Table 5-10. Mode byte description. Pagesize \ bit 3 2 1 256 0 0 0 2 0 0 1 4 0 1 0 8 0 1 1 16 1 0 0 32 1 0 1 64 1 1 0 128 1 1 1 NOTE: that only Bit 0-3 are set in the XML file, cause Bit 6-7 are not static and must be controlled by the PC Frontend. Table 5-11. Answer format /(same for all results).
Field Size Values Status 1 byte STATUS_CMD_OK Data Nmb bytes Status 1 byte Description Data read from device. Will be padded with 0’s if errors occurred during read-out. A Result Value indicating the result of the operation STATUS_CMD_OK 5.6 CMD_PROGRAM_EEPROM_PP This command programs one page the EEPROM memory of the target device if it succeeds. XML PATH: /AVRPART/ICE_SETTINGS/STK600/PpReadEeprom/ Command format: See CMD_PROGRAM_FLASH_PP. 5.
AVR079 Value Description STATUS_RDY_BSY_TOUT No response from target device within specified timeframe 5.9 CMD_READ_FUSE_PP XML PATH: /AVRPART/ICE_SETTINGS/STK600/PpReadFuse/ Table 5-18. Command format. Field Size Values Description Command ID 1 byte CMD_READ_FUSE_PP Command id 1 byte address of fuse byte to read Table 5-19. Answer format if command was executed.
5.14 CMD_SET_CONTROL_STACK This command uploads the control stack to the STK. This is used for both PP and HVSP. Note: The Control stack must always be uploaded before performing any programming commands in high voltage mode if the STK600 has been powered down. To check if the controller PARAM_CONTROLLER_INIT. has a valid control stack: Read Se chapter 11.7: PARAM_CONTROLLER_INIT Table 5-20. Command format.
AVR079 Field Size Values Description PowoffDelay 1 byte XML: powoffDelay Power-off delay. Additional delay (in ms) after Vtg is turned off in order to make sure the Vtg is low enough resetDelay1 1 byte XML: resetDelay1 RSTDELAY #1 (in ms) Additional delay between Vtg is turned on and reset goes high. resetDelay2 1 byte XML: resetDelay2 RSTDELAY #2(in us x 10) Additional delay between Vtg is turned on and reset goes high.
Table 6-5. Command format. Field Size Values Description Command ID 1 byte CMD_CHIP_ERASE_HVSP Command id pollTimeout 1 byte XML: pollTimeout Timeout period (in ms) to wait for RDY/BSY flag to rise. If 0, RDY/BSY flag is NOT used. eraseTime 1 byte XML: eraseTime Delay (in ms) to ensure that the erase of the device is finished. If 0, polling will be used.
AVR079 page buffer of the target device. The transfer data to flash flag should then only be set on the last command. Table 6-8. Mode byte description. Pagesize \ bit 3 2 1 256 0 0 0 2 0 0 1 4 0 1 0 8 0 1 1 16 1 0 0 32 1 0 1 64 1 1 0 128 1 1 1 NOTE: that only Bit 0-3 are set in the XML file, cause Bit 6-7 are not static and must be controlled by the PC Frontend. Table 6-9. Answer format.
6.6 CMD_PROGRAM_EEPROM_HVSP See the CMD_WRITE_FLASH_HVSP command. XML path: /AVRPART/ICE_SETTINGS/STK600/HvspProgramEeprom/ 6.7 CMD_READ_EEPROM_HVSP See the CMD_READ_FLASH_HVSP command. XML path: /AVRPART/ICE_SETTINGS/STK600/HvspReadEeprom/ 6.8 CMD_PROGRAM_FUSE_HVSP This command programs one fuse byte, addressed by the Fuse Address byte. XML path: /AVRPART/ICE_SETTINGS/STK600/HvspProgramFuse/ Table 6-12. Command format.
AVR079 Table 6-15. Answer format. Field Size Values Description Answer ID 1 byte CMD_ READ_FUSE_HVSP Answer id Status 1 byte STATUS_CMD_OK A Result Value indicating the result of the operation. Will always read OK Fuse Byte 1 byte Data read from device. Contains the read low, high or ext fuse byte. Will be padded with 0’s if errors occurred during read-out. 6.10 CMD_PROGRAM_LOCK_HVSP See CMD_PROGRAM_FUSE_HVSP. Note: Address is required but ignored. 6.
Before issuing any AVR8 JTAG commands the following parameters must be set correctly with the CMD_SET_PARAMETER command: • • • • • • • • • PARAM_JTAG_ALLOW_FULL_PAGE_STREAM PARAM_JTAG_EEPROM_PAGE_SIZE PARAM2_JTAG_FLASH_PAGE_SIZE PARAM2_JTAG_FLASH_SIZE_H PARAM2_JTAG_FLASH_SIZE_L PARAM_JTAG_DAISY_BITS_BEFORE PARAM_JTAG_DAISY_BITS_AFTER PARAM_JTAG_DAISY_UNITS_BEFORE PARAM_JTAG_DAISY_UNITS_AFTER 7.1 Memory Read / Write The following memory modes are defined for CMND_WRITE_MEMORY and CMND_READ_MEMORY.
AVR079 Table 7-5. Answer format. Field Size Values Description Answer id 1 byte CMD_JTAG_AVR Answer id Status 1 byte STATUS_CMD_OK STATUS_CMD_FAILED Data n bytes Payload if STATUS_CMD_OK 7.1.2 CMND_WRITE_MEMORY This commands writes a specified amount of bytes to the chosen target MCU memory. The target MCU must be in programming mode (CMND_ENTER_PROGMODE) before issuing this command. Table 7-6. Command format.
7.1.4 CMND_ENTER_PROGMODE This command enables communication between the STK600 and the target MCU and should be the first JTAG command sent to the STK600. After receiving this command the MCU is held in reset state and memory read and write is allowed. Table 7-10. Command format.
AVR079 8 AVR32 JTAG All AVR32 jtag commands except for ENTER_PROGMODE LEAVE_PROGMODE start with CMD_JTAG_AVR32 (0x80) and The implementation of JTAG programming in STK600 is in equal to the JTAGICE mkII (see T0152-0007 JTAGICE mkII Communication Protocol) but without the JTAGICE mk II message structure and fifo packages, i.e. only the message body is used in STK600.
8.3 CMD_RESET_AVR32 This command places the given reset value into the JTAG reset register of the target MCU. Table 8-5. Command format. Field Size Values Description AVR32JTAG id 1 byte CMD_JTAG_AVR32 Command id (0x80) ICE command 1 byte CMND_AVR32_RESET (0x2b) Reset value 1 byte MCU specific Field Size Values Description Answer id 1 byte CMD_JTAG_AVR32 Answer id status 1 byte STATUS_CMD_OK Reset value Table 8-6. Answer format. 8.
AVR079 Table 8-10. Answer format. Field Size Values Description Answer id 1 byte CMD_JTAG_AVR32 Answer id status 1 byte RSP_FAILED RSP_SCAN_CHAIN_READ data 4 bytes If RSP_SCAN_CHAIN_READ 8.6 CMD_BLOCK_WRITE_AVR32 This command writes a block of data starting at the specified SAB address. N should be less than 64 to comply with the maximum data buffer of STK600. Table 8-11. Command format.
Table 8-14. Answer format. Field Size Values Description Answer id 1 byte CMD_JTAG_AVR32 Answer id Status 1 byte RSP_FAILED RSP_ILLEGAL_VALUE RSP_SCAN_CHAIN_READ Data n * 4 bytes If RSP_SCAN_CHAIN_READ 8.8 CMD_NEXUS_WRITE_AVR32 This command writes a word to the specified nexus register. It is equivalent to a SAB write to address OCD_REGISTER + * 4. Table 8-15. Command format.
AVR079 9 XPROG protocol The XPROG programming protocol is used with the ATxmega devices, and can use both JTAG and PDI as the physical interface. All multi-byte values (e.g. address and length fields) are big endian. 9.1 CMD_XPROG_SETMODE Before using any of the XPROG commands, the descried XPROG interface must be selected. This can either be PDI or JTAG. Table 9-1. Command format.
The XPROG commands are described in the following section. The offsets indicated are offsets in the XPROG part of the CMD_XPROG command. To find the absolute offset in the STK600 command, add one. 9.2.1 XPRG_ENTER_PROGMODE This command enables programming mode in the device by enabling the programming interface hardware and sending the programming key. Note: Before using this instruction, the programming interface (PDI or JTAG) must have been set by the programmer specific ‘set mode’ command. Table 9-5.
AVR079 Table 9-9. Command format. Offset Field (1) 0 Command ID 1 Parameter 2 Value(3) Notes: (2) Size Values 1 byte XPRG_ENTER_PROGMODE 1 byte One of the XPRG_PARAM parameters 1-4 Depends on the parameter. 1. The command identifier 2. The parameter to set. See the appendix for the values. 3. The value’s size is depending on which parameter that is to be set. Table 9-10. Answer format.
Table 9-11. Command format. Offset Field (1) 0 Command ID 1 Erase mode 2 Address(3) Notes: (2) Size Values 1 byte XPRG_ERASE 1 byte XPRG_ERASE_CHIP, XPRG_ERASE_APP, XPRG_ERASE_BOOT, XPRG_ERASE_EEPROM, XPRG_ERASE_APP_PAGE, XPRG_ERASE_BOOT_PAGE, XPRG_ERASE_EEPROM_PAGE or XPRG_ERASE_USERSIG 4 bytes Any 1. The command identifier 2.
AVR079 Table 9-13. Command format. Offset Field 0 Size Values (1) 1 byte XPRG_ERASE (2) Command ID 1 Memory type 1 byte Application, Boot, EEPROM, Fuse, Lockbits… 2 PageMode(3) 1 byte Bitfield, see description below 4 bytes Any address 3 Address (4) (5) 7 Length 2 bytes 1 to 512 9 (6) N bytes N data bytes, size is given by the Length parameter Notes: Data 1. The command identifier 2.
Table 9-15. Command format. Offset Field 0 Values 1 byte XPRG_READ_MEM (2) 1 byte Application, Boot, EEPROM, Fuse, Lockbits… Command ID 1 Memory type (3) 2 Address 6 Length(4) Notes: Size (1) 4 bytes Any address 2 bytes 1 to 256 1. The command identifier 2. XPRG_MEM_TYPE_APPL XPRG_MEM_TYPE_BOOT XPRG_MEM_TYPE_EEPROM XPRG_MEM_TYPE_FUSE XPRG_MEM_TYPE_LOCKBITS XPRG_MEM_TYPE_USERSIG XPRG_MEM_TYPE_FACTORY_CALIBRATION 3. The start address of the data to be read.
AVR079 Table 9-18. Answer format. Offset Field (1) 0 Command ID (2) 1 Status 2 Data(3) Notes: Size Values 1 byte XPRG_READ_CRC 1 byte 3 bytes 1. The command identifier. 2. One of the defined error codes. 3. The CRC value calculated by the device itself. CRC value 10 Return Values This section describes all possible return values and their meaning in detail. 10.1 Success Table 10-1. Return values Value Meaning STATUS_CMD_OK Command executed OK 10.
The parameter values are either one or two bytes. For two-byte values, the high byte is read/written first. Table 11-1.
AVR079 11.2 PARAM_SW_MAJOR The PARAM_SW_MAJOR and PARAM_SW_MINOR returns the firmware version of the master mcu. 11.3 PARAM_SW_MINOR See PARAM_SW_MAJOR. 11.4 PARAM_VTARGET The parameter value is voltage in volts x10, i.e. a parameter value of 42 (decimal) corresponds to 4.2V. Note: This parameter cannot be set when the STK600 is in programming mode. The maximum target voltage level is dependant on what target routing/socket board is mounted.
This parameter is intended to be used as a way of telling if the power on STK600 has been lost or turned off and then back again. This way, the host software can tell if the programmer needs to be initialized again before continuing with its operation. If the returned value is 0 the CMD_SET_CONTROL_STACK must be executed before continuing with any high voltage programming commands. 11.
AVR079 Equation 11-2. OCT ⎛ f ⎞ OCT = 3.322 log ⎜ ⎟ ⎝ 1039 ⎠ Equation 11-3. DAC 2078 ⋅ 2 (10 + OCT ) DAC = 2048 − f 11.12 PARAM_SOCKETCARD_ID Returns a byte that identifies the socket card. The file “targetboard.xml” contains a list of the cards with id values. 11.13 PARAM_ROUTINGCARD_ID Returns a byte that identifies the routing card. The file “targetboard.xml” contains a list of the cards with id values. 11.14 PARAM_EXPCARD_ID Returns a byte that identifies the expansion card. The file “targetboard.
11.21 PARAM_BOARD_ID_STATUS 0x00 = OK 0x01 = BoardID mismatch (VTG set to 0V) 0x02 = BoardID changed while power on STK600 (VTG set to 0V) 11.22 PARAM_RESET Used to set the reset line high or low. Will only work when the board is idle. If used when the kit is in programming mode the parameter will be ignored. 11.23 PARAM_RESET_POLARITY For backward compatability with the STK500, this parameter sets the reset polarity. 11.
AVR079 Name Value PARAM_JTAG_DAISY_BITS_BEFORE 2 PARAM_JTAG_DAISY_BITS_AFTER 7 PARAM_JTAG_DAISY_UNITS_BEFORE 1 PARAM_JTAG_DAISY_UNITS_AFTER 2 11.30 PARAM_JTAG_DAISY_BITS_AFTER See PARAM_JTAG_DAISY_BITS_BEFORE. 11.31 PARAM_JTAG_DAISY_UNITS_BEFORE See PARAM_JTAG_DAISY_BITS_BEFORE. 11.32 PARAM_JTAG_DAISY_UNITS_AFTER See PARAM_JTAG_DAISY_BITS_BEFORE. 12 XML Parameter Values A parameter set is specific for a certain AVR device, thus the parameter settings belong in the XML part description file.
Figure 12-1. XML file viewed in XML notepad Open the XML file in xml editor/viewer (e.g XML Notepad or Internet Explorer). All device specific values for STK600 are located under STK600 node. For parameters for the CMD_ENTER_PROGMODE_ISP command, look in /AVRPART/ICE_SETTINGS/STK600/IspEnterProgMode. 13 Command Sequence Example This chapter contains examples of how to connect to the STK600 from the PC frontend and how to read signature from a device. See chapter 2.
AVR079 13.1 Connect The sequence of commands and parameters sent from PC front-end to the STK600 in order to connect is listed below. • • • • • • • • CMD_SIGN_ON CMD_GET_PARAMETER, PARAM_HW_VER CMD_GET_PARAMETER, PARAM_SW_MAJOR CMD_GET_PARAMETER, PARAM_SW_MINOR CMD_GET_PARAMETER, PARAM_SW_MAJOR_S1 CMD_GET_PARAMETER, PARAM_SW_MINOR_S1 CMD_GET_PARAMETER, PARAM_SW_MAJOR_S2 CMD_GET_PARAMETER, PARAM_SW_MINOR_S2 13.
3. Make a new String Value (right-click > New > String Value) named “LogFilePath” 4. Enter Data e.g. ”c:\STK600Com.txt” (right-click ”LogFilePath” > Modify > enter Value Data) Figure 13-2. Adding registry string The communication log for an ISP read signature of an ATmega2560 is shown below. Compare the command and answer data with the format tables in chapter 4.
AVR079 Figure 13-3.
Appendix A.
AVR079 #define CMD_PROGRAM_FUSE_PP 0x27 #define CMD_READ_FUSE_PP 0x28 #define CMD_PROGRAM_LOCK_PP 0x29 #define CMD_READ_LOCK_PP 0x2A #define CMD_READ_SIGNATURE_PP 0x2B #define CMD_READ_OSCCAL_PP 0x2C #define CMD_SET_CONTROL_STACK 0x2D // *** STK HVSP command constants *** #define CMD_ENTER_PROGMODE_HVSP 0x3D #define CMD_LEAVE_PROGMODE_HVSP 0x3E #define CMD_CHIP_ERASE_HVSP 0x32 #define CMD_PROGRAM_FLASH_HVSP 0x33 #define CMD_READ_FLASH_HVSP 0x34 #define CMD_PROGRAM_EEPROM_HVSP 0x35
#define STATUS_CMD_OK 0x00 // Warnings #define STATUS_CMD_TOUT 0x80 #define STATUS_RDY_BSY_TOUT 0x81 #define STATUS_SET_PARAM_MISSING 0x82 // Errors #define STATUS_CMD_FAILED 0xC0 #define STATUS_CMD_UNKNOWN 0xC9 #define STATUS_CMD_ILLEGAL_PARAMETER 0xCA // Status #define STATUS_CONN_FAIL_MOSI 0x01 #define STATUS_CONN_FAIL_RST 0x02 #define STATUS_CONN_FAIL_SCK 0x04 #define STATUS_TGT_NOT_DETECTED 0x00 #define STATUS_ISP_READY 0x10 #define STATUS_TGT_REVERSE_INSERTED 0x20 // hw_status
AVR079 #define PARAM_VTARGET 0x94 #define PARAM_RESET_POLARITY 0x9E #define PARAM_CONTROLLER_INIT 0x9F #define PARAM_STATUS_TGT_CONN 0xA1 #define PARAM_DISCHARGEDELAY 0xA4 #define PARAM_SOCKETCARD_ID 0xA5 #define PARAM_ROUTINGCARD_ID 0xA6 #define PARAM_EXPCARD_ID 0xA7 #define PARAM_SW_MAJOR_SLAVE1 0xA8 #define PARAM_SW_MINOR_SLAVE1 0xA9 #define PARAM_SW_MAJOR_SLAVE2 0xAA #define PARAM_SW_MINOR_SLAVE2 0xAB #define PARAM_BOARD_ID_STATUS 0xAD #define PARAM_RESET 0xB4 #define PARAM_J
A.
AVR079 // 4-byte address #define XPRG_PARAM_NVMBASE 0x01 // 2-byte page size #define XPRG_PARAM_EEPPAGESIZE 0x02 A.3 USB Descriptors Table 13-1. Device descriptor Name Value Hex bLength bDescriptorType bcdUSB bDeviceClass bDeviceSubClass bDeviceProtocol bMaxPacketSize0 idVendor idProduct bcdDevice iManufacturer iProduct iSerialNumber bNumConfigurations Valid DEVICE 2.0 Vendor-specific Vendor-specific None 64 Atmel Corporation 0x2106 2.
Name Value bInterfaceProtocol iInterface None 0 Hex 0x00 0x00 Table 13-4. Endpoint descriptor Name Value bLength bDescriptorType bEndpointAddress bmAttributes wMaxPacketSize bInterval Valid ENDPOINT 3 IN Types - Pkt Size Adjust : No 64 bytes Ignored for Bulk endpoints Hex 0x07 0x05 0x83 0x02 0x0040 0x0A Table 13-5.
AVR079 14 Table of Contents Features ............................................................................................... 1 1 Introduction ...................................................................................... 1 2 Overview ........................................................................................... 2 2.1 USB Communication ........................................................................................... 2 2.2 Packet Format ..................................
5.2 CMD_LEAVE_PROGMODE_PP ...................................................................... 15 5.3 CMD_CHIP_ERASE_PP................................................................................... 15 5.4 CMD_PROGRAM_FLASH_PP ......................................................................... 16 5.5 CMD_READ_FLASH_PP.................................................................................. 17 5.6 CMD_PROGRAM_EEPROM_PP .....................................................................
AVR079 8.3 CMD_RESET_AVR32....................................................................................... 30 8.4 CMD_SAB_WRITE_AVR32 .............................................................................. 30 8.5 CMD_SAB_READ_AVR32................................................................................ 30 8.6 CMD_BLOCK_WRITE_AVR32 ......................................................................... 31 8.7 CMD_ BLOCK_READ_AVR32.......................................................
11.17 PARAM_SW_MAJOR_SLAVE2.................................................................... 43 11.18 PARAM_SW_MINOR_SLAVE2 .................................................................... 43 11.19 PARAM2_RC_ID_TABLE_REV .................................................................... 43 11.20 PARAM2_EC_ID_TABLE_REV .................................................................... 43 11.21 PARAM_BOARD_ID_STATUS ..................................................................... 44 11.
Disclaimer Headquarters International Atmel Corporation 2325 Orchard Parkway San Jose, CA 95131 USA Tel: 1(408) 441-0311 Fax: 1(408) 487-2600 Atmel Asia Room 1219 Chinachem Golden Plaza 77 Mody Road Tsimshatsui East Kowloon Hong Kong Tel: (852) 2721-9778 Fax: (852) 2722-1369 Atmel Europe Le Krebs 8, Rue Jean-Pierre Timbaud BP 309 78054 Saint-Quentin-enYvelines Cedex France Tel: (33) 1-30-60-70-00 Fax: (33) 1-30-60-71-11 Atmel Japan 9F, Tonetsu Shinkawa Bldg.