I use Imagecraft to compile my code.
Then I open the cof file with studio 7.
Some of my code is in C and some is in assembly.
I can set breakpoints on the C portion and studio 7 breaks on them, but if I try to set a breakpoint on the asssembly code I see the red dot near the code, but studio 7 doen not break on it.
Any idea?
I can set breakpoints on assembly instructions in main.asm but for assembly code that is .included the breakpoints disappear as soon as debugging is started.
I can paste my code to main.asm to solve it, not sure if that method will help you? Studio 7 isn't really assembly friendly.
I solved by simply not using studio 7.
Fond an old Windows XP cd, set up a virtual machine and installed Studio 4.
It's so dumb that Studio 7 can't debug assembly that I think we'll move to another micro for future projects.
I can barely tollerate the drop of studio 4 on windows 10, the behemoth studio 7, but being unable to debug assembly code in a IDE aimed to debug microporcessors is plain stupid.
js 
Studio 7 isn't really assembly friendly.
hmm I have done a ~8K ASM project 
just as friendly as C projects.
Studio 7 is slow to download/update memory locations (close the memory view and it's OK) and then there is the breakpoint and step-out (Shift-F11) issues, but it does ignore timer interrupts.
Studio 4 was only annoying when step-over (F10) debugging if you forgot to disable the timer interrupts, but thats irrelevant because it no longer works. 
Studio 4 works OK in windows 10 but you have to uninstall Studio 4 & 7 and manually delete the driver files then re-install studio 4.
Studio 4 works OK in windows 10 but you have to uninstall Studio 4 & 7 and manually delete the driver files then re-install studio 4.
Studio 4 doesn't work on Windows 10.
I spoke with my local distributor and he told me that Atmel does not support Studio 4 with Windows 10.
I had issues on my pc so I get a brand new pc with just Windows 10 on it and tried to install Studio 4 and it doesn't work with my Jtag MK II.
