atbackend

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

I've been hit by a trouble I know I have seen others have - or at least similar. Still I can find only one thread about it, probably due to the absolute CRAP search function here at AVRfreaks. That thread does not seem to apply to me, since the problem is described differently.

 

Here's what I do:

1. On a newly started Atmel Studio I create a boilerplate C executable project, with an ATmega328P as the device.

2. I build.

3. Start a debugging session with Start debugging and break

4. I perhaps do some debugging (step, step, step). I perhaps don't. Does not matter.

5. I end the debugging session with Stop Debugging

 

 

 

The problem details are:

Problem signature:
  Problem Event Name:    BEX
  Application Name:    atbackend.exe
  Application Version:    0.0.0.0
  Application Timestamp:    56050e9b
  Fault Module Name:    libatmega328p.dll_unloaded
  Fault Module Version:    0.0.0.0
  Fault Module Timestamp:    55bf4c18
  Exception Offset:    0f64a460
  Exception Code:    c0000005
  Exception Data:    00000008
  OS Version:    6.1.7601.2.1.0.256.48
  Locale ID:    1053
  Additional Information 1:    fa66
  Additional Information 2:    fa6696398de2b9f98383d7a3bf5c3ea1
  Additional Information 3:    fa66
  Additional Information 4:    fa6696398de2b9f98383d7a3bf5c3ea1

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?...

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

Clicking Close the program, I get the a similar message with details:

Problem signature:
  Problem Event Name:    BEX
  Application Name:    atbackend.exe
  Application Version:    0.0.0.0
  Application Timestamp:    56050e9b
  Fault Module Name:    libatmega328p.dll_unloaded
  Fault Module Version:    0.0.0.0
  Fault Module Timestamp:    55bf4c18
  Exception Offset:    0f5685a0
  Exception Code:    c0000005
  Exception Data:    00000008
  OS Version:    6.1.7601.2.1.0.256.48
  Locale ID:    1053
  Additional Information 1:    d41d
  Additional Information 2:    d41d8cd98f00b204e9800998ecf8427e
  Additional Information 3:    11ab
  Additional Information 4:    11ab312391bf1f977a0472bbb4147be9

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?...

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

 

Things done with this computer lately, as far as I can recall:

 

  • Installed GreenShot

 

That's about it.

 

Any ideas?

Pointers to threads that I failed to locate?

Morten?

 

Please do note that I have this problem upon exiting a debug session. After that everything re debugging is fubar. I can have four "Simulator" in the Tool drop-down, or I can have none. Restarting Studio it opens an arbitrary memory window floating when I open the project.

 

I think I was able to open up a two week old project and debug there without the crash but I could be wrong. Anyway, that project now also displays the dreaded message.

This topic has a solution.

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]

Last Edited: Fri. Dec 4, 2015 - 12:33 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Greetings JohanEkdahl,

 

astudio62betareadme.pdf says following:

 

2. FAQ:

 

8. Atmel Studio cannot find any debuggers or programmers when Norton AntiVirus is running
Atmel Studio might not show any connected tools if Norton AntiVirus is running. To make it work make
sure Norton AntiVirus allows atprogram.exe to communicate with the Atmel Studio front-end by adding
atbackend.exe as an exception in the Norton AntiVirus allowed programs. This is the same with any
anti-virus program that by default blocks ports.

That all I want to come up with for now. Hope you can fix your issue soon. By

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

Thanks, but that's not it as far as I can see. Specifically I do not run Norton, and I have had my antiviral programs turned off, just to make sure.

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

Hmh, c00....5 is access violation, and it came from one of the simulator models... I'll ping Jan-Egil...

:: Morten

 

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

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

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

Morten! If you by "simulator model" hint at "libatmega328p.dll" then I believe it comes from all of them. I've changed device models and get the same error.

 

EDIT: I didn't recognize c00...05 as "access violation". IIRC it was just 0x00000005 back in the days.

 

Do you know where atbackend reads and writes?

Why would it read or write anything at all (to disk, assuming, yes I know, sad person..)?

Apart from loading the device DLL that is..

And why wwhen I exit the debug session?

Why read or write anything at that stage?

 

All these questions for you to orate over so that I can make meaningful investigations at my end?

 

Is it really about the DLL?

Is it the DLL trying to write something, e.g. in the project tree somewhere?

 

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]

Last Edited: Thu. Dec 3, 2015 - 01:00 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

My hunch is that the dll has been unloaded a tad early (access here is in the vmen of atbackend, not to disk).

You were using the simulator for this? (if not, then it's well weird since this dll is only loaded when starting up the simulator on that device).

:: Morten

 

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

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

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

Yes, the Simulator.

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]

This reply has been marked as the solution. 
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

It's an old problem with a runaway process that has submerged. It should only affect the old models that uses the vtoc runtime dll. It needed a fix in the backend so it won't go away until the next studio release. Try the PB variant. That device uses a different model dll that doesn't use the vtoc runtime dll.

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

Lovely, Jan-Egil! Thank you!

 

(I was afraid it had something to do with a Windows update that apparently sneaked in the other day although I thought I had WU set to "ask before...". That took quite a toll on my data quota for the month on the phone... )-:  )

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]

Last Edited: Fri. Dec 4, 2015 - 12:33 PM