[PSA] Do you have issues with ARM debugger tools in 6.2?

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

Hi All.

In the last couple of weeks, we have gotten a couple of people struggeling with accessing tools that support ARM in Atmel Studio. This includes Atmel-ICE, Segger Tools, EDBG and JTAGICE3v3.

Symptoms: None of the above tools are visible inside Atmel Studio, even if all drivers are installed and active.

Reason: Due to the infinite wisdom in windows, sometimes the loader picks up a external JLinkARM.dll (Segger userland driver) provided by another program. If this version is incompatible (older) than the one expected by Atmel Studio, the ARM support subsystem (bundle) crashes when it loads and all ARM capable tools will not be loaded.

I will be pushing a page to the Atmel Studio FAQ on the webdoc, but here's a preview of the page from our staging server. Hope it helps :)

Attachment(s): 

:: Morten

 

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

Last Edited: Wed. Nov 2, 2016 - 07:16 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

This works :]. I just only hope there will be no suprises when i connect my jlink next time i need to.
IS there a way to force Atmel Studio to use the .dll file in atbackend directory instead of seggers one?
Thank you :)

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

We are working on it... The issue is that we actually don't really know what triggers this. We see it on win 7 primarily, but not close to all (for instance, I have the same setup on my machine, but the correct dll loads for me). One way is to force the PATH when we spawn atbackend, but there's both pros and cons in doing that (security priveleges related to exec and path manipulation). So we are open for any imput while we scratch our heads :)

Regarding the 'works' thing, as far as I have seen, the JLinkARM.dll is usually backwards compatible but not forwards compatible. That's why we deem it somewhat safe to use our dll (as it is usually the newest when this issue appears).

:: 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

Quote:

The issue is that we actually don't really know what triggers this

I take it you've heard of Side by Side? What does the manifest say?

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

Quote:

I take it you've heard of Side by Side? What does the manifest say?

I have, but not sure about how it is used (I guess not) in the backend. I think there were issues with using it as part of the bundle system that the backend uses (Poco Bundles for those interested). I'll have to ask our windows expert on it though...

:: 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

Just pointing out that SxS allows you to have ten different foo.dll on your PC. When bar.exe or bar.dll attempts to load foo.dll the one of the 10 it gets is the one for which the side by side manifest within bar* matches.

Having said that, when I look in \windows\winsxs on the virtual machine where I have AS6 installed it looks like the only variant DLLs I have are all M$ ones - nothing there supplied by Atmel or Segger (AFAICS) so perhaps you are not using manifests/SxS to do DLL matching?

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

We are not. There's numerous issues with SxS, especially in XP :( There's also a issue with dll updating once they are registered etc, but I digress :)

The weird thing is that it's only a small subset of windows that shows this behaviour, and we haven't found any common between the systems that we have had sessions on on support. So we're grasping a bit as we don't see any commonalities and we are unable to reproduce it on any system that we have internally.

:: 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

Morten the syllables PSA will have quite a different meaning to you when you get older. :shock:

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Is this thread for any & all issues with ARM debugger tools in 6.2, or just the one specific issue of the OP :?:

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

Morten the syllables PSA will have quite a different meaning to you when you get older. Shocked

Hehe... So either a boring abbreviation or an eye-catcher...

Quote:

Is this thread for any & all issues with ARM debugger tools in 6.2,

It's announcing this issue, nothing more. If the thread derails I will probably lock it :)

:: 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

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I was just about to chuck the d21 xplained out the window until I ran into this thread. Three days wasted involving uninstalls and reinstalls of Atmel Studio.

This is the webdoc I followed:
http://www.atmel.com/webdoc/atme...

- Jm

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

Quote:

This is the webdoc I followed:
http://www.atmel.com/webdoc/atme...

But, that has nothing to do with Xplained Pro cards (or any other edbg based thing)...

:: 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:
Quote:

This is the webdoc I followed:
http://www.atmel.com/webdoc/atme...

But, that has nothing to do with Xplained Pro cards (or any other edbg based thing)...

Then somehow following those directions made it work. Maybe something else happened in the background when I was in the device manager.

Either way, thank you!

The D21 is such a step up from the Atmega line.

- Jm

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

Hello All,

I don´t know if it helps, but I just wanted to note my experience with this problem. I tested it on several machines (Win7 x32, Win8.1 x64) with following results:

1) Installing Atmel SAM-BA 2.12 introduced the error. Removing it solved the problem

2) Installing Percepio AB FreeRTOS+ Trace in Atmel Studio 6.2 introduced the problem. Uninstalling solved it.

3) Having it in parallel with Altium Designer 14.3 does not cause any problem.

Best Regards,
Alex

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

I'm not sure if this is the right place to post this, but I think it might be. I'm having trouble with the debugger in Atmel Studio 6.2, but I've never utilized this function before so I'm not sure if I'm just not using it correctly or if there's a bug.  I'm just trying to test a really basic "Hello_World.c" to get it working but when I run the debugger nothing happens. My code is below. I've got it set up to use the Atmega328P and the tool is set to simulator. When I run it though the memory window comes up with some hex and a bunch of gibberish and the green arrow in the menu labeled as "Continue" becomes clickable. I click it expecting PD5 to blink every 1 second in the IO view window but nothing happens. Any ideas what I'm doing wrong? Thank you for your help.

#define F_CPU 20000000UL // 20MHz

#include <avr/delay.h>
#include <avr/io.h>


int main(void)
{

	//set up pin decelerations here
	DDRD = 0b00100000;
	while(1)
	{
		_delay_ms(1000); //Delay 1s
		PORTD ^= 0b00100000; //bitwise XOR operation //1<<5
	}
}

 

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

Hi Morten,

 

please see this topics:

 

https://www.avrfreaks.net/forum/astudio-62sp1-breaks-project

http://www.at91.com/discussions/viewtopic.php/f,4/t,23427.html

 

Both explain the same problem : no interrupts occur while running in AS, need to power cycle target to re-enable...

 

Thanks,

 

Paul

"As simple as possible, but not simpler"

GUI Framework for Atmel Xplained Pro

Last Edited: Wed. Nov 19, 2014 - 12:38 PM