Known Issues

Below is a list of known issues in the 3.22 version of AVR Studio.

• The current version of AVR Studio does not read the UBROF8 object file format generated by the IAR ICC Compiler. Force the compiler to generate UBROF6 output.
• If an IAR Assembler file contains tabs, the source code marking during debugging in AVR Studio is wrong.
• If you load an object file in AVR Studio, and the reset address is beyond the highest program address (e.g. if the BOOTRST fuses are accidentally set to the wrong vector), no dissassembly window appear. This is mainly a problem for the ICE30.
• AVR Studio handles the timer "Clear on Compare Match" feature equally for all devices. When using the prescaler, there are some differences in how the actual devices handle this feature.
• External Interrupt on "Logical Change on Pin" is not simulated correctly for the devices which supports it.
• In the actual devices, several 16- bit IO register pairs share a temporary high-byte register. This is not handled by the AVR Studio simulator.
• When printing, the font sizes on the the printed copy is to small.
• Double clicking on an apr file, or on an object file in the Windows Explorer, may issue an error messaage when AVR Studio is started.
• When an emulator or the simulator is configured with "Device ATXXXXX with 64K internal SRAM", the XRAM is accessible even if the SRE bit in MCUCR is not enabled.
• The EEPROM write operation in AVR Studio does not halt the processor. The real devices are halted for two cycles when a write operation is issued.
• The port stimuli files are locked during execution.
• The port logging output files are only updated when the project is closed or when the port logging feature is unchecked.
• By definition, coff file text (code) segment sizes are rounded up to the nearest 4 byte boundary, possibly filling in 0-3 extra 0xFF bytes at the end of the code. This can be critical for CRC checking.
• There is no way to initialize unused program memory to a specific value.
• When the object file parser cannot locate source files referenced in the object files, it asks for an alternative location. Next time a source file is not found, it does not check this location automatically.
• From version 3.10, the object files must contain the full path of the source files to be able to corrrectly map breakpoints between the source code and the program memory. This may be a problem when using the IAR command line compiler, which refers to source files in the object file the same way as the user did on the command line, i.e. with or without the full path. The EWB uses the full path of the source files, thus it is not affected by this issue.

Reporting problems

August 31th, 2000

See Also

AVR What's New?