no disassembly after a fresh install of Studio6 beta

Go To Last Post
32 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hello,

I have just installed the latest version of studio 6 beta see herafter.

If I go to the disassembly windows in debug mode, there is no code to be seen, except NOP for all instructions.

What shall I do ?

Pierre

Atmel Studio 6 (Version: 6.2.993 - Beta)
© 2013 Atmel Corp.
All rights reserved.

OS Version: Microsoft Windows NT 6.0.6002 Service Pack 2
Platform: Win32NT

Installed Packages: Shell VSIX manifest - 6.2
Shell VSIX manifest
Version: 6.2
Package GUID: 5aa6ea3e-da7b-48c1-9b2a-cab2329d32ac
Company: Atmel Corporation

Installed Packages: Atmel ARM GNU Toolchain - 4.7.4.1416
ARM Toolchain
Version: ARM_Toolchain_Version:4.7.4.230 GCC_VERSION:4.7.4
Package GUID: D83C9208-1D2D-4665-9760-EB9EE264CF8F
Company: Atmel
HelpUrl:
Release Description: ARM Toolchain

CMSIS
Version: 3.20
Package GUID: D83C9208-1D2D-4665-9760-EB9EE264CF8F
Company: Atmel
HelpUrl:
Release Description: ARM Support File Version

Installed Packages: AVR macro Assembler - 2.1.39.1103
AVR Assembler
Version: 2.1.39.232
Package GUID: 03CB4AE1-80EA-40C7-B561-98CC87EA539C
Company: Atmel
HelpUrl:
Release Description: AVR Assembler For 8-Bit Devices

Installed Packages: Atmel AVR (32 bit) GNU Toolchain - 3.4.2.1052
AVR Toolchain 32
Version: AVR32_Toolchain_Version:3.4.2.489 GCC_VERSION:4.4.7
Package GUID: DB6D383F-C5D9-4E7E-BBF9-F37C6EEB59FD
Company: Atmel
HelpUrl:
Release Description: AVR Toolchain For 32-Bit Devices

Installed Packages: Atmel AVR (8 bit) GNU Toolchain - 3.4.4.1051
AVR Toolchain 8 Bit
Version: AVR8_Toolchain_Version:3.4.4.1162 GCC_VERSION:4.8.1
Package GUID: 2C7AA7CF-94C6-463C-81DA-4AA03B613C3B
Company: Atmel
HelpUrl:
Release Description: AVR Toolchain For 8-Bit Devices

Installed Packages: Atmel Gallery - 1.3.1
Atmel Gallery
Version: 1.3.1
Package GUID: AtmelStudioExtensionManager
Company: Atmel

Installed Packages: Atmel Kits - 1.7.267
Atmel Kits
Version: 1.7.267
Package GUID: bea809ab-462e-4535-99f1-3f9ced2f09ff
Company: Atmel

Installed Packages: Atmel Software Framework - 3.15.0.1281
ASF
Version: 3.15.0
Package GUID: 1E567EA3-6E83-4C11-8734-684F4581B25D
Company: Atmel
HelpUrl: http://asf.atmel.com/3.15.0
Release Description: ASF - 3.15.0 Release

ASF
Version: 3.14.0
Package GUID: 1E567EA3-6E83-4C11-8734-684F4581B25D
Company: Atmel
HelpUrl: http://asf.atmel.com/3.14.0
Release Description: ASF - 3.14.0 Release

ASF
Version: 3.13.1
Package GUID: 1E567EA3-6E83-4C11-8734-684F4581B25D
Company: Atmel
HelpUrl: http://asf.atmel.com/3.13.1
Release Description: ASF - 3.13.1 Release

ASF
Version: 3.12.1
Package GUID: 1E567EA3-6E83-4C11-8734-684F4581B25D
Company: Atmel
HelpUrl: http://asf.atmel.com/3.12.1
Release Description: ASF - 3.12.1 Release

ASF
Version: 3.11.0
Package GUID: 1E567EA3-6E83-4C11-8734-684F4581B25D
Company: Atmel
HelpUrl: http://asf.atmel.com/3.11.0
Release Description: ASF - 3.11.0 Release

ASF
Version: 3.10.1
Package GUID: 1E567EA3-6E83-4C11-8734-684F4581B25D
Company: Atmel
HelpUrl: http://asf.atmel.com/3.10.1
Release Description: ASF - 3.10.1 Release

ASF
Version: 3.9.1
Package GUID: 1E567EA3-6E83-4C11-8734-684F4581B25D
Company: Atmel
HelpUrl: http://asf.atmel.com/3.9.1
Release Description: ASF - 3.9.1 Release

ASF
Version: 3.8.1
Package GUID: 1E567EA3-6E83-4C11-8734-684F4581B25D
Company: Atmel
HelpUrl: http://asf.atmel.com/3.8.1
Release Description: ASF - 3.8.1 Release

ASF
Version: 3.7.3
Package GUID: 1E567EA3-6E83-4C11-8734-684F4581B25D
Company: Atmel
HelpUrl: http://asf.atmel.com/3.7.3
Release Description: ASF - 3.7.3 Release

ASF
Version: 3.6.0
Package GUID: 1E567EA3-6E83-4C11-8734-684F4581B25D
Company: Atmel
HelpUrl: http://asf.atmel.com/3.6.0
Release Description: ASF - 3.6.0 Release

Installed Packages: AtmelToolchainProvider - 6.2.654
AtmelToolchainProvider
Version: 6.2.654
Package GUID: AtmelToolchainProvider.Atmel.0780A430-065B-4EFD-B0D1-FC957262E6DF
Company: Atmel

Installed Packages: LiveWatch - 1.4.266
LiveWatch
Version: 1.4.266
Package GUID: 07290e21-75bd-4363-8d07-a5fa8e32876e
Company: Atmel

Installed Packages: Percepio Trace for Atmel Studio - 1.0
Percepio Trace for Atmel Studio
Version: 1.0
Package GUID: fe274744-c496-42fc-9e52-f77b92d669b1
Company: Percepio AB

Installed Packages: Visual Assist for Atmel Studio - 10.8.2023.1
Visual Assist for Atmel Studio
Version: 10.8.2023.1
Package GUID: 7997A33C-B154-4b75-B2AC658CD58C9510
Company: Whole Tomato Software

Installed Packages: GdbConsole - 1.0
GdbConsole
Version: 1.0
Package GUID: d616f47a-811f-4a7e-bcb8-8fe696222d92
Company: Atmel

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I have no intention of comparing every component version!

Surely, what you see is what you have built in your project. e.g. the C statements and corresponding disassembly.

Try a trivial project, and report back.

I suspect that you are building something you did not know!

David.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

David,

I'm not so sure - there's clearly something going on here. This is the third or fourth thread I've read recently where people are seeing 0xFFFF NOPs where they were expecting to see some disassembled code. So I think something is up. Hopefully the Norway Gnomes are onto the case!

Cliff

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

david.prentice wrote:
I have no intention of comparing every component version!

Surely, what you see is what you have built in your project. e.g. the C statements and corresponding disassembly.

David.

I have given you all the info that might be needed!
The disassembly was working, with the same C statements in previous version!
Debug works ... etc ...;

Pierre

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Pierre,

Atmel will likely want you to .zip up a project that demonstrates this. It would be good (if it's not proprietary) if you could actually post it as an attachment here then we can all load it and try it and see if we see the same effect.

Cliff

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I only installed AS6.2B on this VISTA-32 laptop yesterday (or the day before)

I can see Disassembly in both a GCC and a CV project.
The target is a ATmega328P on a UNO clone board.
The debugger is a Dragon in debugWIRE mode.

I followed all the defaults in the AS6.2B installation.

Yes, the long list of AS6 components is important information. However, I would start from Basics.

e.g. check very carefully that I am building and debuugging the intended project / target.

e.g. if this shows a problem, I would create a new trivial project from scratch.

If this is ok, I would create a new project that duplicates the original problem project.

Yes, of course, most Atmel releases introduce new "features". It helps Atmel and the rest of the community if we can duplicate a problem.

For a start, it helps Atmel to concentrate on a solution. i.e. I am sure that it gets priority in the Bugzilla system.

Having said that, I must confess to building / programming / debugging wrong targets. And I bet that I am not the only one!

David.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

David,

Like you, after reading reports of this happening here, I have tried the same experiments and I simply cannot make it misbehave. I think one of the threads that mentioned it said that they are imported an old project and seen this happen but that when they recreated the project using the same source files everything behaved normally. So there's clearly more to it than:

int main(void) {
}

build, debug.

That's why I'd be interested to see a zipped project that demonstrates it - if it travels with the .zip then it's clearly something hidden in the XML or something like that. If it doesn't travel then it's an environmental thing affecting that person's installation alone.

I do hope Atmel are investigating ;-)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

clawson wrote:
David,

I think one of the threads that mentioned it said that they are imported an old project

I do hope Atmel are investigating ;-)

I have indeed "imported" an existing project, just launched by clicking on: "my_name.cproj"

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

, just launched by clicking on: "my_name.cproj"

But that's wrong - it's the .atsln file you should click on?

(this rings a bell - I think this was mentioned in another thread where the problem had been observed!).

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

From memory, AS6.1 introduced a very different set of project files to AS6.0 and AS5.
Hence the IDE trying to put new stuff in an AS6.1 or AS6.2 folder.

You often find that the new "Parser" will cope with older format project files. But perhaps not with the more unusual parts.

IAR seem worst for this. At least I have more sense than to ever buy an IAR licence!

Yes, I agree with Cliff. Please post a ZIP so that we can try it for ourselves.

David.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

david.prentice wrote:
From memory, AS6.1 introduced a very different set of project files to AS6.0 and AS5.

David.

Just for info, the first time I launched Studio 6 beta the debugger refuses to work, claming for a debbug tool which was there (simulator).
I managed to get it working just by launching the ASF wizard. Strange but that's it!

Pierre

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

david.prentice wrote:

Yes, I agree with Cliff. Please post a ZIP so that we can try it for ourselves.

David.

Attachment(s): 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I can see plenty of dissasembly using this project. Could you start by Going to Tools|Options|Tools and enable diagnostic logging? This should be saved in \Atmel\AtmelStudio\6.2\ApplicationStatus.log

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I downloade the ZIP file. It would not "open" with Windows. However, I could extract the project folder with 7-Zip.

I "Opened" the .ATSLN file.
I presume that I could have "Opened" the .CPROJ file instead.

The Project built ok with a few Wanings.
I had selected Tool->Simulator but AS6.2 would not start Debugging.

So I changed Tool to Dragon and back to Simulator.

Then it started Debug ok.
I could see the Disassembly window.

Obviously, I have no idea what the program does. So I have made no attempt to "run" it.

David.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

david.prentice wrote:
....the project folder with 7-Zip.

The Project built ok with a few Wanings.
I had selected Tool->Simulator but AS6.2 would not start Debugging.

So I changed Tool to Dragon and back to Simulator.

Then it started Debug ok.
I could see the Disassembly window.

Obviously, I have no idea what the program does. So I have made no attempt to "run" it.

David.


Thanks for info
zip file is made with 7Zip since the zip are not allowed in attachment.
Warning are reminder for me, normal!
would not start debugging: As said I had myself to start the ASF wizard to get out of this situation.
I can see the disassembly window: but full of NOP or with the proper code.
I don't have any hardware tool. Can't for Dragon,

Pierre

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

meolsen wrote:
enable diagnostic logging?

First attachement, just after studio opening.
Found in C:\Users\pierre\AppData\Roaming\Atmel\AtmelStudio\6.2

Attachment(s): 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

peter_moulin wrote:
meolsen wrote:
enable diagnostic logging?

First attachement, just after studio opening.
Found in C:\Users\pierre\AppData\Roaming\Atmel\AtmelStudio\6.2

And next in disassembly screen while debugguing.

Attachment(s): 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

What does the .lss show for location 0x23FA?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Do you start debugging at main() ?
What is the Program Counter value when you flip to Disassembly ?

Quote:
I can see the disassembly window: but full of NOP or with the proper code.

Do you mean "proper C statements" ?

I note that you use |= when disabling JTAG with JTD.
It happens to create 'good enough' instructions.
It seems more foolproof to use =

I often find that my 'Tool' gets disconnected by AS6.
This is generally solved by unplugging and re-plugging the Dragon.

Quite honestly, I can't see why the Simulator would ever disconnect.

I would be terrified of touching anything to do with "ASF Wizard". This laptop is slow enough already!

Perhaps Morten has a better suggestion for forcing a 're-connect' of Simulator.

David.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

clawson wrote:
What does the .lss show for location 0x23FA?

Is it what you are looking for: last line
// we detected something, but the soft uart failed
if (logging.show_datagram_error)
28ba: 80 91 a3 2b lds r24, 0x2BA3
28be: 88 23 and r24, r24
28c0: e1 f0 breq .+56 ; 0x28fa
{
bidi_log[0] = '0'+received;
28c2: 90 5d subi r25, 0xD0 ; 208
28c4: 90 93 f9 23 sts 0x23F9, r25
bidi_log[1] = pgm_read_byte(&decode_4_8[bdr->ch1[0]]);
28c8: d8 01 movw r26, r16
28ca: 15 96 adiw r26, 0x05 ; 5
28cc: ec 91 ld r30, X
28ce: f0 e0 ldi r31, 0x00 ; 0
28d0: ea 5e subi r30, 0xEA ; 234
28d2: fb 4f sbci r31, 0xFB ; 251
28d4: e4 91 lpm r30, Z
28d6: e0 93 fa 23 sts 0x23FA, r30

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Clif was asking about parts earlier in the .lss file. You show lines around locations 28ba to 28d6. He was asking about location 23fa.

The locations are given leftmost on assembler lines, before the colon.

The reason Cliff asked specifically for 23fa is that it is the (8-bit) byte address of the (16-bit) word at 11fd.

This, in turn, is the word just after the source annotation

temp2 = HIGH8(sin_low) * HIGH8(sin_low);

from your source file.

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

JohanEkdahl wrote:
Clif was asking about parts earlier in the .lss file. The locations are given leftmost on assembler lines, before the colon.

The reason Cliff asked specifically for 23fa is that it is the (8-bit) byte address of the (16-bit) word at 11fd.

.

Is this better:

// does first in int, and the add in int32.
int temp1, temp2;
temp1 = HIGH8(cos_low) * HIGH8(cos_low);
temp2 = HIGH8(sin_low) * HIGH8(sin_low);
23fa: dd 9f mul r29, r29
23fc: a0 01 movw r20, r0
23fe: 11 24 eor r1, r1

Attachment(s): 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I note that your screenshot shows a session called "gbm16t (Debugging)"
My session is called "OpenDCC_BGM(Debugging)"

My word address 0x11F3 has "SBCI R17,0xB6"

David.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

david.prentice wrote:
I note that your screenshot shows a session called "gbm16t (Debugging)"
My session is called "OpenDCC_BGM(Debugging)"
David.

I must have send something wrong somewhere.
Is it the log file or with the project files?

I send you the gbm16t source file attached

Attachment(s): 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Not really sure what is happening. The logs say that you are launching using AVR8 GDB, which is a bad idea in itself as it doesn't work. However the GUI does not reflect this.

I just did a diff between my openend cproj file and you zipped, and I have a slight difference. Could you try the attached cproj file?

Attachment(s): 

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Well, in gbm16t_src.zip, the Programming Settings is set to 'Skip Programming', so no wonder you are not seeing much....

Project|Properties|Tool

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

meolsen wrote:
Not really sure what is happening. The logs say that you are launching using AVR8 GDB, which is a bad idea in itself as it doesn't work. However the GUI does not reflect this.

I have never decided to use the AVR8 GDB. An issue with reinstall?

I am going out now, I will try your attachment soon

Pierre

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

The second project, which is the one we should be talking about I guess, did not have that... Think our messages are crossing each other a bit.

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

meolsen wrote:
Well, in gbm16t_src.zip, the Programming Settings is set to 'Skip Programming', so no wonder you are not seeing much....

Project|Properties|Tool

Ok that's it.

It is new from previous version and as I have been the victim can lead to confusion.

Thanks for help,

Pierre

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

Programming Settings is set to 'Skip Programming', so no wonder you are not seeing much....

I thought he said "simulator"? Can you think of any logical reason on God's green earth that you would ever want the simulator set to "skip programming"?!?! Surely the option should be ignored when the target is the simulator?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hehe, when/if there is ever persistence in the simulator?

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

clawson wrote:
Quote:

Programming Settings is set to 'Skip Programming', so no wonder you are not seeing much....

I thought he said "simulator"? Can you think of any logical reason on God's green earth that you would ever want the simulator set to "skip programming"?!?! Surely the option should be ignored when the target is the simulator?

I can't agree more on that comment!
Or at least set to Erase entire chip by default, when you come from previous studio version.
Which in any case is, in my humble opinion, meaningless when you don't have a hardwired simulator.
Why should you bother about Programming settings when you have nothing to program.

Bien cordialement à tous ceux qui m'ont répondu.
Pierre

Pierre