SOLVED - AS6 bricks SAM3X-EK on first run with SAM-ICE

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

Downloaded Studio 6 last night
Uninstalled Studio 5.1 and 6
Installed Studio 6 without nay problem.
Played around with 8 bit ATmega, seemed OK.

I noticed Studio 6 wanted to do, and did succesfully perform Firmware Update to both AVR ONE and JTAGICE3

Tonight tested with SAM-ICE and SAM3X-EK

Connected SAM-ICE first to see if it would ask to do a Firmware Update, it didn't

Connected SAM-ICE to USB,
Connected SAM-ICE to SAM3X-EK
Connected AC adaptor [with carefully bent USA plug to suit Australian power point] to SAM3X-EK

Tried to compile and debug SAM3X-EK sample application HX8347A example.

Selected SAM-ICE as debug tool

Debug; Start debugging and break

Some 10 seconds later before the compiler finished a Window pops up, must do firmware Update

I agreed, it started to do a Firmware Update to SAM-ICE

Behind that another windows pops up from Studio 6, can't load the application

Firmware update appears to finish - I THINK - as that window went away.

From that point on;

Studio 6 says SAM-ICE is connected but will not enter program mode, I get this error

Unable to enter programming mode.

Please verify device selection, interface settings, target power and connections to the target device.

Timestamp: 2012-05-11 21:59:33.943
Severity: INFO
ComponentId: 20100
StatusCode: 0

Unable to enter programming mode. Verify device selection, interface settings, target power and connections to the target device.

Segger software sees the SAM-ICE but cannot see the ARM MCU on the SAM3x_EK

SAM-ICE
Debug host 127.0.0.1
Debug port 52544
Serial number 000028009921
Connection com.atmel.avrdbg.connection.segger
Firmware Version J-Link ARM V8 compiled May 3 2012 18:36:22.
Hardware Version

J-Link V4.28b Error

SAM-ICE can only be used with Atmel devices
[Yes, I do have the correct device selected]

Connection Fatal
Communication error

connected to SAM3X-EK

J-Link ARM V4.44d

Segger J-Flash ARM V4.44d

Application log started
- J-Flash ARM V4.44d (J-Flash compiled Mar 26 2012 18:47:57)
- JLinkARM.dll V4.44d (DLL compiled Mar 26 2012 18:47:16)
Reading flash device list [C:\Program Files (x86)\SEGGER\JLinkARM_V444d\ETC\JFlash\Flash.csv] ...
- List of flash devices read successfully (1099 Devices)
Reading MCU device list [C:\Program Files (x86)\SEGGER\JLinkARM_V444d\ETC\JFlash\MCU.csv] ...
- List of MCU devices read successfully (1253 Devices)
Opening project file [C:\Program Files (x86)\SEGGER\JLinkARM_V444d\Default.jflash] ...
- Project opened successfully
Reading CFI info ...
- Connecting ...
- ERROR: Failed to connect
- ERROR: Could not read CFI info, not connected

Common Atmel team, what do I do now ?

That message from Segger "SAM-ICE can only be used with Atmel devices"

Does that mean that I should have purchased direct from Segger [no difference in price really] instead of buying a SAM-ICE ?

Exactly what is all that about?

SAM3X-EK which WAS running a sample application no longer runs anything.

I am so HAPPY I tried the RELEASE Version of Studio 6, 2 days away from the 13th I figured it would be safe, I was wrong.

Last Edited: Tue. May 15, 2012 - 05:23 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

More testing

SEGGER J-Link Commander V4.46e ('?' for help)
Compiled May 3 2012 19:15:42
DLL version V4.46e, compiled May 3 2012 19:15:25
Firmware: J-Link ARM V8 compiled May 3 2012 18:36:22
Hardware: V8.00
S/N: 28009921
OEM: SAM-ICE
Feature(s): RDI
VTarget = 3.300V
Info: TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
Info: TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
No devices found on JTAG chain. Trying to find device on SWD.
No device found on SWD.
Did not find any core.
Info: TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
Info: TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
No devices found on JTAG chain. Trying to find device on SWD.
No device found on SWD.
Did not find any core.
J-Link>

SAM-BA v2.11
-I- Waiting ...
-I- TCL platform : Windows NT
-I- SAM-BA 2.11 on : windows
-I- Retrieved arguments from command line :
-I- argv 0 : \jlink\ARM0
-I- argv 1 : at91sam3x8-ek
-I- argv 2 : prog_flash_binaries.tcl
0
\jlink\ARM0
-I- Connection : \jlink\ARM0 (target(comType) = 2)
-I- Board : at91sam3x8-ek
-I- Traces Level : 4
-I- target(handle) : 50400744
Read device Chip ID at 0x400e0640 --- get 0xaaaaaaaa
Read device Chip ID at 0x400e0740 --- get 0x77e5e0f2
Read device Chip ID at 0x400E0940 --- get 0x77e5e0f2

And I keep getting the Segger message saying SAM-ICE only works on Atmel devices, it seems the Segger software thinks I am not connected to an ATMEL ARM MCU

Manages to read Target Voltage but that is all it can do now.

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

Honestly it sounds like the Segger update utility screwed up (AS6 doesn't interact with it directly, it uses the Segger provided DLLs and update utility). Is there a way to force a firmware upgrade on the debugger?

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

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

abcminiuser wrote:
Honestly it sounds like the Segger update utility screwed up (AS6 doesn't interact with it directly, it uses the Segger provided DLLs and update utility). Is there a way to force a firmware upgrade on the debugger?

- Dean :twisted:


Dean to be honest, I simply don't know, there is not much on the Segger site about SAM-ICE, I have downloaded the latest J-LINK software which is in my second post, no joy.

Trying Firmware Update in AS6, AS6 says there is no device to upgrade as if it didn't exist.

Sure one can say AS6 did not do do it.

BUT

AS6 is running the compiler

AND

AS6 is doing the firmware Upgrade

It tried to do both at the same time and screwed up big time.

Sure AS6 uses Segger DLL but AS6 is in control and it is AS6 that caused the problem.

You may have misssed the fine point that I did try to do a firmware upgrade BEFORE the compile yet AS6 did not want to do one.

Only after I started the compile did AS6 suddenly want to start a Firmware Upgrade.

I INCORRECTLY THOUGHT AS6 would handle it, well it ddin't and AS6 did cause this problem.

This cannot bee seen as Segger's fault surely.

Unfortunately that is the only SAM-ICE I have so I cannot confirm which device is dead SAM-ICE or SAM3X-EK or both as both no longer work properly and there is absolutely nothing else that I can think to try.

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

Quote:

Trying Firmware Update in AS6, AS6 says there is no device to upgrade as if it didn't exist.

AS6 does not do SAM-ICE upgrades directly - it just spawns the Segger utility silently with the upgrade option. It doesn't show up in the AS6 upgrade list because AS6 can't update the firmware itself.

This is most likely an issue you need to ask Segger support about.

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

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

Dean

AS6

View Available tools

SAM-ICE(000028009921) Connected

Tools
Firmware Upgrade

Firmware Upgrader

No tool is connected, please connect your tool and press the Refresh button

Pressing Refresh

No tool is connected, please connect your tool and press the Refresh button

-------------------------

Using Segger software

SEGGER J-Link Configuration V4.46e
Logging started @ 2012-05-12 02:05

Updating firmware of 1 emulator:
Updating firmware of emulator 1 of 1 via USB (SN: 28009921)... Not updated, emulator firmware is already up to date.
Finished updating 1 emulator!

EDIT:

I am un installing AS6 and will install AS6 Beta and see if it will do an update

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

abcminiuser wrote:
Quote:

Trying Firmware Update in AS6, AS6 says there is no device to upgrade as if it didn't exist.

AS6 does not do SAM-ICE upgrades directly - it just spawns the Segger utility silently with the upgrade option. It doesn't show up in the AS6 upgrade list because AS6 can't update the firmware itself.

This is most likely an issue you need to ask Segger support about.

- Dean :twisted:

Well that is funny.

The way I see it I should have purchased a Segger J-Link in the first place from Segger as from what I see so far SAM-ICE is LIMITED ARTIFICIALLY TO ONLY HANDLE ATMEL ARM !! whereas the Segger J-Link does ALL ARM BRANDS.

And now I should ask SEGGER to fix this mess created by AS6.

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

Quote:

The way I see it I should have purchased a Segger J-Link in the first place from Segger as from what I see so far SAM-ICE is LIMITED ARTIFICIALLY TO ONLY HANDLE ATMEL ARM !! whereas the Segger J-Link does ALL ARM BRANDS.

Indeed, that's due to licensing, and it is the reason the SAM-ICE is much much cheaper (~$150 vs. ~$300). You would have had the exact same experience with a standard Segger unit, except you'd be yelling at Segger directly and be out of pocket twice as much.

I'll be clear: Atmel Studio does not interact with the Segger unit directly. At all. It calls Segger supplied DLLs to perform debugging, and upgrades are handled through the Segger provided utilities. If it broke, it would have broken exactly as much as if you had run the Segger J-Link update utility yourself manually.

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

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

jabram wrote:
Well that is funny.

The way I see it I should have purchased a Segger J-Link in the first place from Segger as from what I see so far SAM-ICE is LIMITED ARTIFICIALLY TO ONLY HANDLE ATMEL ARM !! whereas the Segger J-Link does ALL ARM BRANDS.

Happens all the time.

NXP calls their Segger derivative the J-Link Lite NXP Edition. It cannot be used to debug non-NXP parts.

Analog Devices' J-Link derivative is called the mIDASLink. It cannot be used to debug non-AD parts.

Digi sells one called the JTAG Link. It can only be used to debug products manufactured by Digi.

Freescale calls theirs the J-Link Lite FSL. It cannot be used to debug non-Freescale parts.

IAR sells an OEM version that specifically cannot be used with Kiel toolchains.

All of these are Segger products under the hood, with license restrictions imposed by the silicon vendor in exchange for a significantly reduced price tag.

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

abcminiuser wrote:
Quote:

The way I see it I should have purchased a Segger J-Link in the first place from Segger as from what I see so far SAM-ICE is LIMITED ARTIFICIALLY TO ONLY HANDLE ATMEL ARM !! whereas the Segger J-Link does ALL ARM BRANDS.

Indeed, that's due to licensing, and it is the reason the SAM-ICE is much much cheaper (~$150 vs. ~$300). You would have had the exact same experience with a standard Segger unit, except you'd be yelling at Segger directly and be out of pocket twice as much.

I'll be clear: Atmel Studio does not interact with the Segger unit directly. At all. It calls Segger supplied DLLs to perform debugging, and upgrades are handled through the Segger provided utilities. If it broke, it would have broken exactly as much as if you had run the Segger J-Link update utility yourself manually.

- Dean :twisted:

Ok Dean, hear you loud and clear.

Then you may want to explain your way around this.

I uninstalled AS6

Installed AS6 Beta

And it works, well nearly, it will work if I edit the device file

02:38:03: [ERROR] Unexpected Chip Identifier 0x286e0a60 (expected 0x286e0a30)., ModuleName: TCF (TCF command: Device:startSession failed.)
02:49:02: [ERROR] Unexpected Chip Identifier 0x286e0a60 (expected 0x286e0a30)., ModuleName: TCF (TCF command: Device:startSession failed.)

But it is suddenly working.

So pray tell who exactly would you like me to yell at ?

Seems to me it is indeed an AS6 Release issue.

I will do some more testing to confirm it does indeed work after I edit those pesky AS6 Beta Device files.

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

Back to AS6 Beta

and now even the Segger software works and sees the ARM MCU on the SAM3X-EK

SEGGER J-Link Commander V4.46e ('?' for help)
Compiled May 3 2012 19:15:42
DLL version V4.46e, compiled May 3 2012 19:15:25
Firmware: J-Link ARM V8 compiled May 3 2012 18:36:22
Hardware: V8.00
S/N: 28009921
OEM: SAM-ICE
Feature(s): RDI
VTarget = 3.300V
Info: TotalIRLen = 4, IRPrint = 0x01
Info: Found Cortex-M3 r2p0, Little endian.
Info: TPIU fitted.
Info: FPUnit: 6 code (BP) slots and 2 literal slots
Found 1 JTAG device, Total IRLen = 4:
#0 Id: 0x4BA00477, IRLen: 04, IRPrint: 0x1, CoreSight JTAG-DP (ARM)
Cortex-M3 identified.
JTAG speed: 100 kHz
J-Link>

Amazing, me thinks, Dean, do you still maintain this has nothing to do with AS6 Release version ?

And the irony is that the sole purpose for all this hoopla with AS6 is to support Atmel ARM which clearly it so far fails to do IMHO.

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

AS6 when connected to SAM-ICE when Firmware Update is attempted it says No Tool Connected.

AS6 Beta does the same thing.

I don't care what explanation is dreamt up, that has to be a BUG.

That is what caused my problem which thankfully it is now solved, but it did waste 5 hours of my time and has not endeared me toward ATmel at all.

In other words you CANNOT TEST to see if a Firmware Update is required, it is OUTSIDE OF YOUR CONTROL and it WILL happen without warning in the middle of a program cycle and if you let it go ahead [as I did] it will scramble the SAM MCU to the point it is guesswork as to how to get it to ever respond again, I was simply lucky that I found a way and did not have to return the SAM-ICE and SAM3X-EK to the Atmel Store, all thanks to AS6 Release verison.

Seriously all this is not even close to be let loose in the real world!

I tried to do things properly, having noticed that AS6 Release did a firmware upgrade to AVR ONE, JTAGICE3, DRAGON and JTAGICE MKII, when I connected SAM-ICE I first tried to do a Firmware Upgrade because I did NOT want the upgrade to be done in the middle of a programming session which is what happenned anyway despite all my best efforts.

When I first tried to do a firmware upgrade AS6 must have displayed the "no tool connected" message, I obviously mistook that to mean no Firmware Update was required.

So when I compiled and started to load a sample application to the SAM3X-EK, AS6 invoked the Segger dll and IT WAS THEN that a check was done and a firmware update started at the SAME TIME as the flash in the SAM3X-EK is being programmed.

That seriously locked up the SAM3X-EK.

Using the CLEAR jumper on the SAM3X-EK did NOT make it respond to the now upgraded SAM-ICE.

Power was cycled many times for both SAM-ICE and SAM3X-EK, yet SAM-ICE could not obtain a response from the SAM3X.

Segger's own software could not get a response from the SAM3X I guess because of a weird state SAM3X chip got itself into as a result of the firmware upgrade in the middle of programming session.

It was only when I connected a micro USB cable and ran SAM-BA v2.11 on a USB connection that SAM3X FINALLY started responding normally again.

After that SAM3X responded to SAM-ICE as well. I downlaoded sample applications to it using AS6 Beta and AS6 Release both now work.

I hope this saves some other unpaid Atmel tester from wasting 5 hours like I did.

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

** How to SAFELY avoid this hapenning to you **

First time use of SAM-ICE with AS6 Release version

A firmware upgrade WILL BE PERFORMED, best to have it happen in a safe way with YOU IN CONTROL and NOT in the middle of dowloading code into your AT91SAM EK.

You need to ensure that is done safely to avoid wasting 5 hours and thinking your SAM-ICE and EK have been bricked by AS6 Release Version.

Here is my suggested WORK AROUND

Connect SAM-ICE to USB cable, connect SAM-ICE JTAG cable to AT91SAM board, power the AT91SAM board

DO NOT DOWNLOAD any projects

Tools
Device Programming
Select SAM-ICE
Select Device
Select Interface
Apply

That should SAFELY invoke the Segger dll and inform you that SAM-ICE firmware Upgrade needs to be performed

Switch OFF your AT91SAm board first
Disconnect the JTAG cable

Let the Firmware Ugrade proceed

After that all should work correctly

** Next release of AS6 needs the following FIX **

Clicking on Tools
AVR Tools Firmware Upgrade

Need to change the title to maybe "ATMEL Tools Firmware Upgrade" since AS6 does not ONLY handle AVR and NOT only handle AVR tools !!

If SAM-ICE is connected AS6 needs to invoke Segger dll and check if the CONNECTED SAM-ICE needs firmware Upgrade

AND NOT what it currently does which is to announce "No Tool Connected" !! when in fact SAM-ICE IS CONNECTED but AS6 does not communicate with it to check it's Firmware Status.

It can get even more confusing
If like me you have an AVR Debug Tool connected, for example AVR ONE connected at the same time as you connect SAM-ICE then you will NOT see the "NO Tool Connected" message

You will only see the AVR debug tools listed.

*******************************
IF YOU ARE READING THIS BECAUSE
LIKE ME YOU HAVE FALLEN INTO THIS TRAP
AND YOU NOW THINK YOUR SAM-ICE AND
YOUR SAM3X-EK ARE BRICKED
*******************************
Relax,
Your SAM-ICE is NOT bricked
Your SAM3X-EK has an easily fixed problem.

To fix your SAM3X-EK,
disconnect the JTAG cable,
Header JP6 'ERASE' place the jumper over the header, press 'NRST' button,
remove the jumper from 'JP6, ERASE',
connect a micro USB cable to your SAM3X-EK
run SAM-BA v2.11,
no need to do anything special with SAM-BA,
just running SAM-BA seems to fix the SAM3X-EK JTAG interface.
That fixed it for me.

After running SAM-BA the JTAG interface on SAM3X-EK starts responding to SAM-ICE via the JTAG interface correctly once again.

By the way, only using the 'JP6 ERASE' jumper without running SAM-BA does NOT solve the problem.

Last Edited: Sun. May 13, 2012 - 02:45 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

jabram wrote:

Need to change the title to maybe "ATMEL Tools Firmware Upgrade" since AS6 does not ONLY handle AVR and NOT only handle AVR tools !!

Or, explain quite clearly (perhaps in a pop-up dialog box) that this option only applies to AVR tools -- exactly as current text in the menu option clearly states -- and add some other obvious method (tested first to make sure it works in as many corner cases as possible) which allows the user to directly access SEGGER's SAM-ICE firmware upgrade services.

Clearly, if it was possible for a customer to get this confused by what was, apparently, the deliberate design of the tools, then it follows that there's probably a better way to approach the problem.

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

Quote:

Amazing, me thinks, Dean, do you still maintain this has nothing to do with AS6 Release version ?

Honestly I can't grep the root issue through the wall of text above, but my apologies if I was mistaken and this does turn out to be an issue in the AS6 release. I still maintain that everything to do with the SAM-ICE is complete out of AS6's control and in Segger's code, but I do agree that the AVR upgrade window text should be changed to re-iterate that it is for AVR tools only.

From what I understand:
1) SAM-ICE with AS6 BETA works, with the device XML file patched (this was a bug in either the device header, or the ID burned into the physically manufactured chip)
2) SAM-ICE with AS6 release does not work, as the firmware upgrade did not successfully complete

I have a SAM-ICE at work so if you can give me clear reproduction steps I can try to re-create it, and if this isn't just a fluke I can file a critical/blocker bug for it so that it is fixed ASAP.

Quote:

And the irony is that the sole purpose for all this hoopla with AS6 is to support Atmel ARM which clearly it so far fails to do IMHO.

It is extremely unfortunate that you are experiencing issues, but we are using SAM-ICE devices and AS6 regularly on many different systems without issues. I don't doubt you are having problems, but one problematic instance does not a failed product make.

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

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

abcminiuser wrote:
... but one problematic instance does not a failed product make.

- Dean :twisted:


I know a company that was arogant enough to say that and blame the customer for the "one problematic instance" they were having. Ever experience a blue screen? :?

I do like AS6 though. :)

"I may make you feel but I can't make you think" - Jethro Tull - Thick As A Brick

"void transmigratus(void) {transmigratus();} // recursio infinitus" - larryvc

"It's much more practical to rely on the processing powers of the real debugger, i.e. the one between the keyboard and chair." - JW wek3

"When you arise in the morning think of what a privilege it is to be alive: to breathe, to think, to enjoy, to love." -  Marcus Aurelius

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

Quote:

I know a company that was arogant enough to say that and blame the customer for the "one problematic instance" they were having. Ever experience a blue screen? Confused

I'm not being arrogant, as I really do feel for you - I too know how much it sucks to have issues with software (ever used SVN?). I was just responding to your comment that AS6 was bad as a whole because of one unfortunate incident.

If you can give problem replication steps, I can file a report to the Atmel Studio development team. Issues like this if repeatable are considered pretty darn major issues and I'm sure it would be corrected very quickly.

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

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

That was me Dean, not the OP. Overall you guys are doing a good job.

"I may make you feel but I can't make you think" - Jethro Tull - Thick As A Brick

"void transmigratus(void) {transmigratus();} // recursio infinitus" - larryvc

"It's much more practical to rely on the processing powers of the real debugger, i.e. the one between the keyboard and chair." - JW wek3

"When you arise in the morning think of what a privilege it is to be alive: to breathe, to think, to enjoy, to love." -  Marcus Aurelius

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

Quote:
ever used SVN?

Yes. Extensively. In serious projects involving many users. With very few and rare major problems.

Since we're obviously moving into FUDding now, how about these?:

Ever used FLIP?
Ever used AVR Studio 4.18?
Ever used AVR Studio 4.19?

I've had serous problems with all of those.

Especially FLIP which, when I tested it was an utter load of *, written by incompetent programmers that didn't even care to capture exceptions thrown by the Java run-time. It is on the same level as enabling an AVR interrupt w/o supplying an ISR.

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

Quote:

That was me Dean, not the OP. Overall you guys are doing a good job.

Whoops, my mistake - poor reading comprehension on my part.

Quote:

Since we're obviously moving into FUDding now, how about these?:

I retract my comment, I don't want to start another flame war here.

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

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

abcminiuser wrote:
From what I understand:
1) SAM-ICE with AS6 BETA works, with the device XML file patched (this was a bug in either the device header, or the ID burned into the physically manufactured chip)
2) SAM-ICE with AS6 release does not work, as the firmware upgrade did not successfully complete

I have a SAM-ICE at work so if you can give me clear reproduction steps I can try to re-create it, and if this isn't just a fluke I can file a critical/blocker bug for it so that it is fixed ASAP.


Dean, no need for any war :-)

Your assumptions 1. and 2. above are both incorrect.

Neither AS6 Beta nor AS6 allow one to SAFELY check if a SAM-ICE firmware Upgrade is required.

They both report "No tool connected" if one tries to check for firmware upgrade and SAM-ICE is the ONLY tool connected.

The problem surfaced ONLY because AS6 insists on doing a Firmware Upgrade and THAT ONLY happens the first time it starts to program code into a device.

AS6 Beta works EXACTLY the same way, except it did not try to perform a Firmware Upgrade when first used.

The BUG is in BOTH AS6 Beta and AS6.

Need to FIX AS6 interface when checking for firmware update to ACTUALLY communicate with Segger DLL and actually check if a firmware upgrade is required instead off what it currently does, which is, it does NOTHING and displays a FALSE message "No Tool Connected"

Now that my SAM-ICE did successfully have it's firmware upgraded I can no longer reproduce what occurred.

****** IMPORTANT ****************
To test this you need to start out with a SAM-ICE that has not had the firmware upgrade version that is applied when first used with AS6 Release to start either debug or programming session.
*********************************

Connect SAM-ICE JTAG to SAM3X-EK

Start a AS6 debug session using any of the Sample SAM3X-EK solutions.

At the point when compiling is finished and AS6 starts programming code into the SAM3X-EK

A window will pop up [from Segger dll I guess] saying a Firmware Upgrade must be performed - click yes or OK or whatever it wants to do it.

Then another window pops up [from AS6] which at the SAME TIME has started to load the sample firmware and it cant continue.

It is AT THIS POINT that the problem occurs which places the SAM3X-EK JTAG interface into a strange locked state which does not reset with power cycling, it ONLY resets after SAM-BA is run via the Micro USB connector on SAM3X-EK.

I am guessing Segger dll is doing a Firmware Upgrade.

At the same time AS6 is trying to program the sample firmware into to the SAM3X-EK

Remember the JTAG cable is connected because I THOUGHT I had already made sure NO FIRMWRE UPGRADE was required. Normally one would make sure the JTAG cable is not connected during a Firmware Upgrade.

The issue is;
Not being able to safely determine if a Firmware Upgrade is required BEFORE one starts to load sample firmware into the EK.

My suggested workaround in my previous post tries to solve that by starting a programming session to see if Segger dll will want to do a Firmware Upgrade - which it certainly will do the FIRST TIME AS6 starts either a debug or programming session.

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

jabram wrote:
abcminiuser wrote:
From what I understand:
1) SAM-ICE with AS6 BETA works, with the device XML file patched (this was a bug in either the device header, or the ID burned into the physically manufactured chip)
2) SAM-ICE with AS6 release does not work, as the firmware upgrade did not successfully complete

I have a SAM-ICE at work so if you can give me clear reproduction steps I can try to re-create it, and if this isn't just a fluke I can file a critical/blocker bug for it so that it is fixed ASAP.


Dean, no need for any war :-)

Your assumptions 1. and 2. above are both incorrect.

Neither AS6 Beta nor AS6 allow one to SAFELY check if a SAM-ICE firmware Upgrade is required.

They both report "No tool connected" if one tries to check for firmware upgrade and SAM-ICE is the ONLY tool connected.

The problem surfaced ONLY because AS6 insists on doing a Firmware Upgrade and THAT ONLY happens the first time it starts to program code into a device.

AS6 Beta works EXACTLY the same way, except it did not try to perform a Firmware Upgrade when first used.

The BUG is in BOTH AS6 Beta and AS6.

Need to FIX AS6 interface when checking for firmware update to ACTUALLY communicate with Segger DLL and actually check if a firmware upgrade is required instead off what it currently does, which is, it does NOTHING and displays a FALSE message "No Tool Connected"


To be absolutely clear, the message is not strictly FALSE, since you specifically clicked on a menu item labeled "AVR Tools", and you were not, in fact, using an AVR tool.

It was prone to accidentally misleading a user; and for this reason alone, some re-working of the user interface is warranted to re-inforce the fact that ARM tools are specifically EXCLUDED from this functionality.

But it was not false.

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

lfmorrison wrote:
To be absolutely clear, the message is not strictly FALSE, since you specifically clicked on a menu item labeled "AVR Tools", and you were not, in fact, using an AVR tool.

It was prone to accidentally misleading a user; and for this reason alone, some re-working of the user interface is warranted to re-inforce the fact that ARM tools are specifically EXCLUDED from this functionality.

But it was not false.


The statement is indeed false - because when the "Atmel Tool" called "SAM-ICE" is connected, Atmel Studio 6 reports "No Tool Connected"

Apparently there is no intention to exclude any "Atmel Tools".

You may not have noticed the word "AVR" is quickly being replaced with the word "Atmel"

AVR Studio 5 -> Atmel Studio 6

AVR Studio 5 is run from -> Atmel AVR Tools - AVR Studio 5

Atmel studio 6 is run from -> Atmel - Atmel Studio 6

This forum is "AVR Studio 5 and Atmel Studio 6 forum"

-----------------
QUOTE FROM Atmel Studio 6 EN-US help file

"Firmware upgrade

Introduction
Atmel tools can be upgraded by the end user as new firmware becomes available to provide support for new parts and families, as well as bugfixes."

Before commencing an upgrade, be sure to terminate any active debug session and disconnect the unit from the application being debugged"
------------------

"Atmel tools", NOT "AVR tools".

The intention IS to support firmware upgrade for "Atmel Tools".

In the rush to have Studio 6 release out there, someone forgot 2 things;

1./ to rename "AVR Tools Firmware Upgrade" - to - "Atmel Tools Firmware Upgrade".

2./ to query Segger dll and perform Firmware Upgrade on SAM-ICE if required.

Question is how long before "AVR Freaks" becomes "Atmel Freaks" ?

[You read it here first]

This is the ONLY forum that covers Atmel Studio 6 and Atmel Studio 6 ARM support. The Atmel ARM forum has nothing that I can find about "Atmel Studio 6".

Since AVR and Atmel both start with the letter A we can continue to use the short version AS6 :-)

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

I guess this issue is resolved now (in SP2 at least)?
Because we still have a bug entry in our internal issue tracker.

Prasad Khare
Atmel Corporation

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

I know this thread is a bit dated, but it seemed the closest thing to the error I've been having.

I am having trouble debugging with SAM-ICE using Atmel studio (6.1). Atmel studio recognizes the device (JTAG mode selected), however when I try to build I run into the error:

"Failed to launch program.
Error:Error connecting to JLink Driver"

I'm looking to program a custom board, just in case this could be the source of error, but it seems to me the nature of this error is between my computer and the SAM-ICE.

I've already downloaded the driver from segger.com, and when using their program jlink.exe, the computer seems to recognize and be able to talk to the SAM-ICE. Poking around online discussions, it seems the issue may be a firmware upgrade from segger is incompatible with AS6, but even attempting to do so I ran into the same error as above. (I'm not sure if I was able to downgrade the firmware successfully). Otherwise I found documentation to be pretty limited.

Tested this on both Windows7 and WindowsXP platforms and ran into same error both times.

All help appreciated.

With thanks,
Ben