Техническая Спецификация для Atmel ATSTK600 500 Starter Kit and Development System. ATSTK600 ATSTK600
![Atmel](https://files.manualsbrain.com/attachments/0369829915bda09f9c2e00fb805a7753579683b5/common/fit/150/50/8d2bf08978ec3e5bc63f4343ac5e91ce8d0e40045619fa520d910d64af8f/brand_logo.png)
Модели
ATSTK600
AVR079
25
8133A-AVR-04/08
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
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.
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.11 CMD_READ_LOCK_HVSP
See CMD_READ_FUSE_HVSP.
Note: Address is required but ignored.
6.12 CMD_READ_SIGNATURE_HVSP
See CMD_READ_FUSE_HVSP.
6.13 CMD_READ_OSCCAL_HVSP
See CMD_READ_FUSE_HVSP.
7 AVR8 JTAG
All AVR8 jtag commands start with CMD_JTAG_AVR (0x90)
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 mkII message structure and fifo packages, i.e. only the message body is
used in STK600.
mkII (see T0152-0007 JTAGICE mkII Communication Protocol) but without the
JTAGICE mkII message structure and fifo packages, i.e. only the message body is
used in STK600.
Table 7-1. Overall command format.
Field Size
Values
Description
AVR8JTAG id
1 byte
CMD_JTAG_AVR
Command id, “JTAGICE wrapper”
Ice_command
1 byte
CMND_xxxx
JTAG command
Payload
n byte
JTAG command specific
Table 7-2. Overall answer format.
Field Size
Values
Description
Answer ID
1 byte
CMD_JTAG_AVR
Command id
ICE answer msg body
n byte