7.5.1 Configuration

Configuration takes place before or during a session is active by using the Query, Set, and Get commands. The following configuration elements are required:

  • CONFIG/VARIANT: the host must specify which AVR 8-bit target type is being used. Note that the target type refers to the OCD/interface type rather than the marketing name. (E.g.: mega48 has the debugWIRE module.)

    Available variants are: AVR debugWIRE (0x01), megaAVR JTAG (0x02), XMEGA (0x03), and AVR devices with UPDI (0x05).

  • CONFIG/FUNCTION: the host must specify what the purpose of the session is. Programming sessions do not require OCD access, and typically release the target to run freely upon completion, whereas debugging sessions may hold the target in reset when required in order to prevent runaway code.

    Available functions are: programming (0x01) and debugging (0x02).

  • PHYSICAL: the physical context must be configured with the correct physical interface as well as the necessary clock information. Stored values may be read out, if required. Only the clocks for the relevant interface need be set.

    Available interfaces are: JTAG (0x04), debugWIRE (0x05), PDI (0x06), and UPDI (0x08).

  • DEVICE: the device context provides the tool with an array of device-specific data, which will be needed during the session. It can be typically read from XML files deployed with the front-end, and can be changed on the fly in case the incorrect device is detected.

  • OPTIONS: any relevant options can be set in this context

Note: Before continuing with activation of physical the CMD_HOUSEKEEPING_START_SESSION must be called, see Start Session.