Atmel Studio 7.0 Beta

Go To Last Post
301 posts / 0 new

Pages

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

Hallo..

 

i have try ATMEL STUDIO 6.2 on Windows 10 Home 64Bit and is function now :)

Windows 10 Home 64Bit, ASUS M4A89GTD-PRO/USB3, AMD Phenom II X6 1055T, Ram 2x 4GB, SSD Samsung EVO840 250GB, SATA HD 2.0TB, NVIDIA GeForce GTX 750

Last Edited: Wed. Aug 5, 2015 - 12:11 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

ATMEL Studio 7.0 Beta is not compatible with Win10

It's a known fact. wink 

 

We don't support win 10 as of now due to some shell issues.

https://www.avrfreaks.net/comment...

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Will Subversion give source control problems in a Solution created in 6.2 and opened in 7?

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

Are you asking whether the format of the XML project files has changed?

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

Hi all,
I am new to the forum.

I am using a ATSMA3X8E chip connected through SAM-ICE and have problems in debugging existing (auto-upgraded) projects.
I saw some similar issue in previous comments but not quite the same so I am posting my problem and workaround.

 

In "Device Programming" JTAG connects just fine but when I try to download I get the following error:
"Error updating project settings:Object reference not set to an instance of an object."

 

I tried to create a dummy hello world project and I was able to download&debug without problems.
Then comparing the .cproj with that converted by Atmel Studio I noticed a different configuration in the samice tag.

 

Converted tag

    <com_atmel_avrdbg_tool_samice>
      <ToolType>com.atmel.avrdbg.tool.samice</ToolType>
      <ToolName>SAM-ICE</ToolName>
      <ToolNumber>28010154</ToolNumber>
      <Channel>
        <host>127.0.0.1</host>
        <port>65209</port>
        <ssl>False</ssl>
      </Channel>
      <ToolOptions>
        <InterfaceName>JTAG</InterfaceName>
        <InterfaceProperties>
          <JtagDbgClock>12000000</JtagDbgClock>
          <JtagProgClock>1000000</JtagProgClock>
          <IspClock>150000</IspClock>
          <JtagInChain>false</JtagInChain>
          <JtagEnableExtResetOnStartSession>true</JtagEnableExtResetOnStartSession>
          <JtagDevicesBefore>0</JtagDevicesBefore>
          <JtagDevicesAfter>0</JtagDevicesAfter>
          <JtagInstrBitsBefore>0</JtagInstrBitsBefore>
          <JtagInstrBitsAfter>0</JtagInstrBitsAfter>
          <JtagSelectedDeviceIndexInChain>
          </JtagSelectedDeviceIndexInChain>
          <JtagDaisyChainDevices>
          </JtagDaisyChainDevices>
        </InterfaceProperties>
      </ToolOptions>
    </com_atmel_avrdbg_tool_samice>

Hello world tag

 

    <com_atmel_avrdbg_tool_samice>
      <ToolOptions>
        <InterfaceProperties>
          <JtagDbgClock>4000000</JtagDbgClock>
        </InterfaceProperties>
        <InterfaceName>JTAG</InterfaceName>
      </ToolOptions>
      <ToolType>com.atmel.avrdbg.tool.samice</ToolType>
      <ToolNumber>28018184</ToolNumber>
      <ToolName>SAM-ICE</ToolName>
    </com_atmel_avrdbg_tool_samice>

Replacing the samice configuration made download&debug work.

Then it appears to be a problem with the project upgrade.

Hope it helps

Aldo

----

there are only 10 types of people: those who understand binary and those who don't

Last Edited: Wed. Aug 5, 2015 - 08:35 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

Then it appears to be a problem with the project upgrade.

 

To fix that for my assembler solutions, I just created new solutions in 7.0 and then brought the .asm and .inc files from the older version solutions over to the new and everything works fine.

My main problem was with 6.2 solutions that were created when upgrading from version 4.

 

I did automatically convert some C program solutions when prompted by 7.0 and they seem to work without problem, however, I don't have a debugger to test that function.

 

 

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

Some debugging problems still persist even though I have 0ms SUT...if you still remember that...

 

JTAG Mk3 seems to always start at 4MHz and the start debug fails in PDI mode. Resetting the PDI clock at 1MHz gets things working again. Thank goodness a I really need the debugger in the next few days.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Would love to try Atmel Studio 7 but the installer tells me that it is not compatible with Windows 10? Will there be an update sometime soon?

 

Thanks

Amanda

 

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

Define "soon" please. devil

 

And sure... there will be an update to W10... probably also soon.

 

 

 

 

 

 

 

 

 

Please forgive me... I am feeling cheeky this morning.

 

Ross McKenzie ValuSoft Melbourne Australia

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

10.1 10.2, 10.3 all within a day..... then Win20, they are even giving it away and no one wants it.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

I don't know if I'm ready for W10, free or not. I spent loads of time and smashing my mouse getting W8.1 the way I like it. I can't even remember all the hacks I went through to get some programs to not crash, etc., etc., etc., etc.
 

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

This is bug AVRSV-6791

:: Morten

 

(yes, I work for Atmel, 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

And while you are there it seems that the chip (Xmega32E5) is not erase before programming so the received 0xc0 or something similar error appears and the chip is not programmed.

 

It all works if the chip is manually erased first.

 

All lock bits are set when this happens. I will show a bit more info once I get back to this later on today.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Works fine on my end... What specific steps do you do when this happens? 

 

0xC0 is a generic 'tool/debugger failed to execute command' error, so can stem from everything between underpowered USB ports to noise on the PDI lines. If it is not erased and then programmed, the tool should not really care, the only issue that you might see is that the verification fails since we might not have been able to write all data correctly depending on the memory that you are writing to.

 

EDIT; however setting lockbits means that verification fails (since we don't do a chiperase on xmega before programming, on a flash erase)...

:: Morten

 

(yes, I work for Atmel, 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.

Last Edited: Tue. Aug 11, 2015 - 06:10 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I simply hit the program button. It all works after a manual erase.

 

No problem with programming new chips, I did about 100 last week, it only happens with programmed chips. I'll set one up shortly.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

Last Edited: Tue. Aug 11, 2015 - 06:26 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

since we don't do a chiperase on xmega before programming,

So shall we call it a bug or a feature? cheeky

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

It by design at least :) The checkbox clearly says erase flash, not chiperase...

 

let's just say that from previous experience, running implicit chip erase can cause users to get somewhat angry..

:: Morten

 

(yes, I work for Atmel, 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

Now I'm confused, this is different to how the programming worked before. It did a device erase INCLUDING lock bits etc.

 

 

So how do I do an automatic CHIP erase before programming?

running implicit chip erase can cause users to get somewhat angry..

WHY!?? If you have a check box which allows you to do a chip erase then that's what it should happen.

 

As it is you will get users angry (ie me wink) if I have to push the " Erase now" button every time I want to reprogram a chip.

 

I didn't even notice that the check box said "erase flash" only.

 

As it is it's not useful.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

on mega, we do a chiperase since that is the only thing we can do. On xmega however we do not (since that would erase the user signature). 

 

On Xmega, we present it like this:

 

On mega, we present it like this:

 

The reasoning here is that instead of us 'mimicking' what we think the user wants/expects, we just show how the chip works. The studio 4 version had another approach, which caused us at least a small mountain of support...

:: Morten

 

(yes, I work for Atmel, 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

So ALL you need to do........is provide the user with check boxes with all the stuff that the user wants erased before programming....

 

Maybe under the ADVANCED menu?? which is not available in my version of AS7 yet? Default all check boxes to off so that the user need to check which bits he/she want to erase before programming, then if the stuff up it's all their fault. devil

 

 

Or maybe provide a master "Program all" and use the existing check boxes.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

I see another programming option under "Production file" but the assembler does not produce these?? I tried (and failed) to generate one like I used to do with AS4.

Maybe I need to read the fabulous manual.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Production file is meant as a all-in-one thing, so there we do have a chiperase... 

:: Morten

 

(yes, I work for Atmel, 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

js wrote:

ATMEL Studio 7.0 Beta is not compatible with Win10

It's a known fact. wink 

 

We don't support win 10 as of now due to some shell issues.

https://www.avrfreaks.net/comment...

 

Looking forward to when it is compatible...

Last Edited: Tue. Aug 11, 2015 - 06:44 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

meolsen wrote:

On xmega however we do not (since that would erase the user signature). 

Is that right?

 

 

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

Hi,

 

I would like to add that on the current AS6.2, I have the same problem as John, EVEN for production files (that is what I'm always using) with the lock bits set.

So first I manually do a chip erase (in order to clear the lock bits), then I can use the production file dialog normally.

 

And like Steve, I would also like to know who is right between Morten or the Xmega manual ?

Have a nice day,
Kraal

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

Hmh, apparently not for that family :) 

:: Morten

 

(yes, I work for Atmel, 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

There is no THE xmega manual :) Also I have a feeling that the comment in the code was not for the user data but for the boot segment...

 

We have had the discussion about doing erases for you, and the feedback we have got from most is that they want to control erases. What would the expectation if you are changing the lockbits from locked to unlocked? Should we fail to do that for you, or should we erase the chip for you? 

 

Just skimming the Production file page, it looks like that does a 'per address space' erase on xmega and a chiperase on tiny and mega if the erase checkbox is checked...

:: Morten

 

(yes, I work for Atmel, 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

Since "changing the lock bits from locked to unlocked" would expose users to software piracy I would expect that ALL code bits be erased, including flash, EEPROM and boot loader section before they are changed . But then again a set of check boxes as above would give the user the option of selecting the necessary steps of erasing before programming...well like a normal AVR.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Improvement AVRSV-6803 it is. I can guarantee that it won't be in studio 7 though :)

:: Morten

 

(yes, I work for Atmel, 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

it won't be in studio 7 though

Lemme guess, you are taking a leaf form M$ and it will jump directly to AS10.......devil

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Hi sysoph,

 

I see that the error "Error updating project settings: *" would happen while opening the project.

I am afraid that it could be a coincidence that this occurred while starting debugging.

 

Thanks,

Deena

 

Regards,
Deena

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

I'm trying to build and debug an existing program with Studio 7.

 

I ran into a snag.  Maybe I got this problem because it is a C++ program. 

 

I wanted to add an existing file into the project and the way I've done it for decades in VS and for almost that long in Atmel Studio isn't an option.  Normally I right click on a project folder, or as Microsoft calls it, project filter.  Then I get a menu that allows me to select "Existing Item".  All I get with Studio 7 is "Add New Class".   It worked okay in Studio 6.2.

 

EDIT:  Okay I figured out what was happening.  I had the debugger running.  If I exit the debugger, it works okay.  I can live with that.

 

 

 

Last Edited: Mon. Aug 17, 2015 - 12:27 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I have the same problem, I am using Windows 7 64 bit, and I disabled AVG during install but still not working. But then it is Beta, and I would not buy a car that said Beta!

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

leroy157 wrote:

 I would not buy a car that said Beta!

They don't call them beta.  They call them 2016. wink

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

AVG is supposedly aware now that AS7 is from the "good guys" so it should not threat it as a virus. (debatable of course.... devil )

 

For me it is "working" reasonably well, at least in the narrow scope I'm using it with the XmegaE5 chips and assembler.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

I figured out what my problem was.  The "add existing files" isn't available when using the debugger.  I can do it if I exit the debugger.

 

I haven't detected any viruses either.  Your computer should be safe.  smiley 

Last Edited: Mon. Aug 17, 2015 - 01:49 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Was about to ask for your project, since we're not able to reproduce this one... Guess the issue is more 'why is Add->Class' there in debug mode...

:: Morten

 

(yes, I work for Atmel, 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

meolsen wrote:

Was about to ask for your project, since we're not able to reproduce this one... Guess the issue is more 'why is Add->Class' there in debug mode...

A good question.  On the other hand, they are all there in Visual Studio whether in debug mode or not.

 

 

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

Not on my machine... 

:: Morten

 

(yes, I work for Atmel, 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

Weird.  They are on my machine. 

 

 

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

Hmh, maybe in 2010 then..? I'm on 2013 at the moment, and there I'm not able to add file while in debug (they are inactive menu options though, not removed from the menu).

:: Morten

 

(yes, I work for Atmel, 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

Hmmm.