When you select the STK500 programmer, BASCOM will run the files named stk500.exe that is installed with AVR Studio.
That is why you have to specify the file location of the stk500.exe
The normal STK500 support will erase, and program the flash.
The STK500.EXE supports a number of Atmel programmers which all use the STK500 V1 or V2 protocol.
For the AVR ISP mkII, you need to supply the serial number of the USB programmer. The USB port will be used then instead of the serial port.
The extended STK500 support will show the following window:

Option |
Description |
Programming mode |
Serial or parallel. Some options require the parallel mode. |
Input Flash File |
The program HEX file. It is loaded automatic |
Input EEPROM File |
The program EEP file. It is loaded automatic when it exists |
Output Flash File |
The name of the output flash file. Only needed when you want to read a device. |
Output EEPROM File |
The name of the output EEPROM file. Only needed when you want to read the EEPROM from a device |
Mode |
Both will work on the FLASH and EEPROM, Flash will only work on the FLASH ROM and EEPROM will only work on the EEPROM.
Use both when you want to program both a program and an EEPROM (EEP) file. |
Erase |
Erase chip. Must be done before programming the chip. |
Program |
Program the chip |
Read device |
Read the flash and or EEPROM content and store in the specified files. |
Verify device |
Verify the chip content with the files. |
Read signature |
Read the signature bytes that identify the chip. |
Read/Write Lock Byte |
Read and write the lock byte. Hex notation! |
Read/Write Fuse Bytes |
Read and write the fuse bytes. Hex notation! |
Read/Write Vtarget |
Read or set the Vtarget voltage |
Read/Write Aref |
Read or set the Aref voltage |
Read/Write oscillator |
Read or write the oscillator settings |
Read/Write frequency |
Read or set the board frequency |
All options will set the command line parameters. A file named stk500.cmd will be created by the compiler with the proper syntax.
This file will be executed and the result is stored in the stk500.log file.