my problem occurs in a debug session of a correctly compiled C project running on a real controller hardware (connected via AvrDragon and JTAG).
When choose the "data IRAM" scope within the memory view, the difference between every two addresses is always one byte (8bit):
data 0x0100 70 72 65 73 73 20 3c 53 50 41 43 45 3e 20 74 6f data 0x0110 20 63 6f 6e 74 69 6e 75 65 00 .. .. .. .. .. ..
This corresponds to the address increment usage for the .data section within the project's map file. When I choose the "prog FLASH" scope within the memory view, the addresses increment in the same way (corresponding to the .text section of the map file.
But in the disassembly window ("Show addresses" is enabled), the addresses increment every WORD (16bit), which creates some extra calculation to match the addresses between "prog FLASH" memory view and disassembly window.
Does anybody know the place for this kind of disassembly window settings? Or is this a program bug?