Microchip Studio 7.0.2542

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

Microchip Studio for AVR® and SAM Devices | New and Noteworthy | Microchip Studio Release Note

Microchip Studio for AVR® and SAM Devices 7.0.2542

  • Renaming of Atmel Studio to Microchip Studio for AVR and SAM Devices
  • Microchip Studio installer bundles with the AVR GCC Toolchain, Arm GCC Toolchain, and the MPLAB XC8 Compiler with AVR devices support. To unlock all optimization options of MPLAB XC8 Compiler, try or get a PRO license.
  • Default optimization for debug configuration is -Og, previous it was -O1
  • Improved scrolling performance on large projects/files
  • AVR Macro assembler version 2.2.8
  • Advanced Software Framework 3.49.1, including previous version back to 3.42
  • Updated kit recognition

 

This topic has a solution.

"Dare to be naïve." - Buckminster Fuller

Last Edited: Tue. Mar 23, 2021 - 11:18 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

gchapman wrote:
Renaming of Atmel Studio to Microchip Studio for AVR and SAM Devices

That'll never catch on - there's still people calling it "AVR Studio" ...

 

laugh

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

Google can find AS7.0 v2397 and and prior Releases.
None of the Microchip websites know anything about 7.0.2542
.
I don't care what name they use.
It seems sensible to emphasise the ownership e.g. logos, splash screen, ...
.
MS7.0.2542 seems to be confusing. Likewise any mix of Mxxx and Studio
.
David.

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

" Microchip Studio for AVR® and SAM Devices" does seem rather long-winded ...

 

 

and why doesn't SAM get an  ®    ?

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

logic movement to change name but atmel studio is EOL, MPLAB  will be the only one updated with new devices very very soon

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

Yes Atmel Studio is EOL but seems like Microchip Studio for AVR® and SAM Devices 7.0.2542 is not.

Renaming of Atmel Studio to Microchip Studio for AVR and SAM Devices.

 

Has anybody found a link to it yet?

 

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

plouf wrote:

logic movement to change name but atmel studio is EOL, MPLAB  will be the only one updated with new devices very very soon

 

Christ I hope not.  MPLAB is hideous to work with, and having to use a separate software to program out of the IDE is a  pai in the a$$.

 

but I shall be out of business soon enough so I guess whatever.

 

jim

I would rather attempt something great and fail, than attempt nothing and succeed - Fortune Cookie

 

"The critical shortage here is not stuff, but time." - Johan Ekdahl

 

"Step N is required before you can do step N+1!" - ka7ehk

 

"If you want a career with a known path - become an undertaker. Dead people don't sue!" - Kartman

"Why is there a "Highway to Hell" and only a "Stairway to Heaven"? A prediction of the expected traffic load?"  - Lee "theusch"

 

Speak sweetly. It makes your words easier to digest when at a later date you have to eat them ;-)  - Source Unknown

Please Read: Code-of-Conduct

Atmel Studio6.2/AS7, DipTrace, Quartus, MPLAB, RSLogix user

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

having to use a separate software to program out of the IDE

I've programmed devices from within MPLABX without any problems.  Admittedly, I did shell out the nearly $80 for ... three SNAPs and a PicKit4.

 

I have to admit that MPLABX (well, Netbeans itself, probably) looks somewhat "amateurish" next to AS7 (well, Visual Studio.)  There always seems to be some window that I can't find, or something that resizes itself inappropriately, or ... something.  It doesn't seem THAT awful, though.  Mostly stuff that "I guess I could get used to that.  If I used it enough."

 

The Arduino IDE is looking better all the time.  (I've decided that I'm very amused that the two biggest complaints I see are "the programming environment does too much hand-holding", and "the IDE doesn't do completion."  :-) )

 

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

Atmel Studio is a mature product, and I don’t feel the urgent need for updates. No matter if it is EOL or not, we can still use it.

To me, the real problem is the toolchain. Avr-gcc wasn’t updated for a long long time. Does it mean avr-gcc is dead? As an amateur I don’t really want to spend some many for their MPLAB XC8 Compiler. I will rather switch to another vendor, like STM and arm-gcc.

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

but XC compilers are Free, except some "optimization levels", which is no matter to "Amateurs" anyway

 

additionally if you feel OK for non updated STUDIO because its mature, why you feel avr-gcc is not mature ? its mature enough no need any update expect adding support for new devices

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

gchapman wrote:
Default optimization for debug configuration is -Og, previous it was -O1

 

more wondering how much impact this is going to have on existing programs and new ones.

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

meslomp wrote:
wondering how much impact this is going to have on existing programs

If the setting gets stored in the Project file, it should make no difference.

 

and new ones

hopefully, it should be the "best" (sic?) debugging experience - that is its raison d'etre ...

 

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

Studio can now be updated via "Check for Updates" ...

 

Last Edited: Mon. Nov 9, 2020 - 11:55 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

So the bug is still a key character ?

 

laugh 

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

GermanFranz wrote:

Studio can now be updated via "Check for Updates" ...

Hey-ho.   That did not happen when I tried in #3.

 

Sure enough.   Check for Update now finds the new Release.    I will attempt to download and install it.

 

David.

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

Here's the release notification.

 

It will be available on microchip.com soon (whatever soon means wink)

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

Last Edited: Mon. Nov 9, 2020 - 12:59 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

meolsen wrote:
Here's the release notification

That topic is locked - and yet it has a 'reply' button!?!

 

Purchase link for the XC8 Pro licence: https://www.microchipdirect.com/...

 

It's  £843.94  (workstation) - clearly a great deal of thought has gone into that number!

 

 

 

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

meolsen wrote:
Here's the release notification.

 

Wheres the link to the video mentioned?

 

Also, your posting mentions only the XC8 compiler and not the one that studio now uses.  I am no expert on these things, but are we to assume that whatever compiler that Studio now uses will no longer be available in the 'new and improved' studio? 

 

Will the CodeVision extension still work?

 

 

We've got questions, hopefully someone has answers cheeky

 

Jim

I would rather attempt something great and fail, than attempt nothing and succeed - Fortune Cookie

 

"The critical shortage here is not stuff, but time." - Johan Ekdahl

 

"Step N is required before you can do step N+1!" - ka7ehk

 

"If you want a career with a known path - become an undertaker. Dead people don't sue!" - Kartman

"Why is there a "Highway to Hell" and only a "Stairway to Heaven"? A prediction of the expected traffic load?"  - Lee "theusch"

 

Speak sweetly. It makes your words easier to digest when at a later date you have to eat them ;-)  - Source Unknown

Please Read: Code-of-Conduct

Atmel Studio6.2/AS7, DipTrace, Quartus, MPLAB, RSLogix user

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

... bundles with the AVR GCC Toolchain, Arm GCC Toolchain, and the MPLAB XC8 Compiler with AVR devices support.

What is questionable about this?

 

Of course CV and other third party plugins will work as they always have...

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

Last Edited: Mon. Nov 9, 2020 - 02:40 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

He says it comes with both GCC[1] and XC8 compilers

 

[1] in both AVR & ARM flavours.

 

EDIT

 

He beat me to it

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...
Last Edited: Mon. Nov 9, 2020 - 02:11 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

From AS7.0 you can click Help->Check for Updates

This will download the web installer.

 

Close AS7.0.   Run the Installer.   Two hours later you have Microchip Studio 7.0.2542

It will install the XC8 Free version (unless you want to buy the Pro version and Activation code)

 

You can convert an existing GCC C project to XC8.   This will enable you to cripple your existing project if that is what you would like.

You can create a new XC8 project.

You can create regular GCC (C) and G++ (C++) projects

You can create regular Codevision C projects

You can import Arduino sketches (G++)

 

It does not look as if you can create XC8 C++ projects.

 

I am sure that we will get some user feedback fairly swiftly.

 

Of course I was updating an existing AS7.0.2397 installation.

A virgin installation may offer less project types.   (obviously CV does not come with MS7.0.2542)

 

David.

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

It does not look as if you can create XC8 C++ projects

XC8 does not support C++ (I know, I know...)

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

meolsen wrote:
What is questionable about this?

Most likely I am the most questionable!   Sorry about that.

 

awneil wrote:
He says it comes with both GCC[1] and XC8 compilers

 

Yeah yeah yeah....I see that....

 

awneil wrote:
He beat me to it

You can't always be first to use the exclamation point!!

 

Ok, I have been kicked enough....back under my rock I go......

 

 

Oh wait!  What about the video! wink

 

Jim

I would rather attempt something great and fail, than attempt nothing and succeed - Fortune Cookie

 

"The critical shortage here is not stuff, but time." - Johan Ekdahl

 

"Step N is required before you can do step N+1!" - ka7ehk

 

"If you want a career with a known path - become an undertaker. Dead people don't sue!" - Kartman

"Why is there a "Highway to Hell" and only a "Stairway to Heaven"? A prediction of the expected traffic load?"  - Lee "theusch"

 

Speak sweetly. It makes your words easier to digest when at a later date you have to eat them ;-)  - Source Unknown

Please Read: Code-of-Conduct

Atmel Studio6.2/AS7, DipTrace, Quartus, MPLAB, RSLogix user

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

Oh wait!  What about the video! wink

Do I look like a marketing person to you? wink

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

meolsen wrote:
Do I look like a marketing person to you? 

No idea what you look like so I reserve opinion.....but personality says most likely ~Marketing.

 

JIm

I would rather attempt something great and fail, than attempt nothing and succeed - Fortune Cookie

 

"The critical shortage here is not stuff, but time." - Johan Ekdahl

 

"Step N is required before you can do step N+1!" - ka7ehk

 

"If you want a career with a known path - become an undertaker. Dead people don't sue!" - Kartman

"Why is there a "Highway to Hell" and only a "Stairway to Heaven"? A prediction of the expected traffic load?"  - Lee "theusch"

 

Speak sweetly. It makes your words easier to digest when at a later date you have to eat them ;-)  - Source Unknown

Please Read: Code-of-Conduct

Atmel Studio6.2/AS7, DipTrace, Quartus, MPLAB, RSLogix user

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

meolsen wrote:

It does not look as if you can create XC8 C++ projects

XC8 does not support C++ (I know, I know...)

Well,  that avoids wasting any more time.    Unless you think that X++8 is imminent.

 

I can understand IAR,  ARM,  ... developing and selling their own Compilers.

 

I find it difficult to see how Microchip can sell licences for AVR-GCC and ARM-GCC.   Surely GCC and G++ are Open Source.    You can sell licences for a commercial IDE.    You can make the commercial IDE "difficult" to use Open Source Tools.

I have no problem with buying licences for good Tools.     But as a hobbyist I look at the price.    They ask a LOT of money for a non-C++ compiler.

 

David.

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


   --> 

 

  

 

After a while, it starts a separate installer for XC8:

 

 

 

 

 

and, when it's all done:

 

 

 

 

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

jgmdesign wrote:

meolsen wrote:
Do I look like a marketing person to you? 

No idea what you look like so I reserve opinion.....but personality says most likely ~Marketing.

 

JIm

 

Go on, Jim.   You know exactly who Morten is.

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

david.prentice wrote:
I find it difficult to see how Microchip can sell licences for AVR-GCC and ARM-GCC

Where does it mention selling licences for them?

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


meolsen wrote:
XC8 does not support C++

and yet:

 

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

Yeah... Who would have imagined when we integrated with Visual Studio that that would not be true wink

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

May have been difficult to trademark SAM.

 

"Dare to be naïve." - Buckminster Fuller

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

awneil wrote:

david.prentice wrote:
I find it difficult to see how Microchip can sell licences for AVR-GCC and ARM-GCC

Where does it mention selling licences for them?

I phrased it wrong.   As far as I know,   AVR-XC8  is a Microchip branch from AVR-GCC.   A restricted XC8 comes free with v2542

 

Whereas AVR-GCC and AVR-G++ permit -Os and -O3 you have to buy an XC8-PRO licence to use -Os and -O3

Microchip will continue development of the XC8 Compiler.   Microchip will provide support to XC8-PRO users.

 

David.

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

plouf wrote:
... but atmel studio is EOL,
7-series must expire ... I have hope for an 8-series.

Fill Me In: Is Atmel a dead horse? | AVR Freaks

 

"Dare to be naïve." - Buckminster Fuller

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

For XC8, I cannot stress this enough:

In addition, XC8 PRO provides a path for customers wanting to tackle Functional Safety, to ease the burden of your functional safety qualification. The MPLAB XC8 Functional Safety Compiler License - a TÜV SÜD certified compiler package that supports 8-bit PIC® and AVR® microcontrollers

 

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

TFrancuz wrote:
Atmel Studio is a mature product, ...
legacy ... mature implies nearly "kicking the bucket"wink

TFrancuz wrote:
... and I don’t feel the urgent need for updates.
Conversely, I do as the hand that the ones at Microchip are playing will be forced (near future EOL of Microsoft Visual Studio Isolated Shell)

TFrancuz wrote:
Avr-gcc wasn’t updated for a long long time.
Microchip AVR GCC, MPLAB XC8 v2 for AVR

TFrancuz wrote:
Does it mean avr-gcc is dead?
No (FSF AVR GCC) though v11 may be a fork in the road.

TFrancuz wrote:
As an amateur I don’t really want to spend some many for their MPLAB XC8 Compiler.
MPLAB XC8 v2 for AVR source code is available; likewise for FSF AVR GCC.

Some third party GCC are holding at v7 and/or v8 likely due to extensive regression testing (that's somewhat expensive)

 


legacy - Wiktionary

 

Visual Studio Isolated Shell - Visual Studio

Support for older versions of Visual Studio | Visual Studio Product Lifecycle and Servicing | Microsoft Docs

 

avr-gcc and avr-g++ are deprecated now. | AVR Freaks

 

Come Join Us (MPLAB Now Supports AVRs) | Page 7 | AVR Freaks (MPLAB XC8 v2.31 for AVR)

MPLAB Ecosystem Downloads Archive | Microchip Technology

[3/4 page]

Source Archives

Prebuilt GNU toolchain for AVR (Sysprogs)

AVR-GCC 10.1.0 for Windows 32 and 64 bit – Zak's Electronics Blog ~* (Zak Kemble)

MobileChessBoard - Browse /avr-gcc snapshots (Win32) at SourceForge.net (by GJLay, one of the FSF AVR GCC principals)

 

"Dare to be naïve." - Buckminster Fuller

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0
  • AVR Macro assembler version 2.2.8 

What changed?

Reason : maybe the web doc will eventually have that

 

  • Updated kit recognition

Is the following a part of that? (AVR GDB proxy)

MPLAB Snap and atbackend | AVR Freaks

 

... developers may be comforted to know that the well-loved Studio development experience, will remain an IDE option for the foreseeable future.

Thank you and all!

 

The latest version of MPLAB XC8 PRO license includes optimizations to reduce code size and increase efficiency, that rival more expensive compilers in the market.

MPLAB XC8 PRO is a relative value.

 


AVR Assembler (AVRASM2)

 

AVR | Platforms | GNAT Pro Safety-Critical | AdaCore

AdaCore GNAT for AVR is likely based on FSF AVR GCC v4.5 (no XMEGA) though still pertinent wrt avionics and LEO megaAVR.

LEO - Low Earth Orbit

ATmegaS128 - Tolerant Devices

ATmegaS64M1 - Tolerant Devices

 

"Dare to be naïve." - Buckminster Fuller

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

What changed?

Reason : maybe the web doc will eventually have that

Built in support for the new AVR core ISA (remember there's been some noise around a warning that the assembler emits when assembling for ATmega4809 or the AVR-Dx etc. Basically it (finally) enables the  V4 version core pragma:

#pragma AVRPART CORE CORE_VERSION V4
  • Updated kit recognition

Issue with displaying certain links and supporting new kit constructs. Only applies to the Kit Window page that pops up when Xplained PRO kits etc are connected.

Is the following a part of that? (AVR GDB proxy)

MPLAB Snap and atbackend | AVR Freaks

No, but as far as I'm aware it has been enabled 

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

Oh wait!  What about the video! 

I have pinged my mr. video. I'll update with link once I know something smiley

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

"Dare to be naïve." - Buckminster Fuller

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

david.prentice wrote:
I find it difficult to see how Microchip can sell licences for AVR-GCC and ARM-GCC.
value-added

david.prentice wrote:
Surely GCC and G++ are Open Source.
GPL allows for proprietary by certain mechanisms.

david.prentice wrote:
You can sell licences for a commercial IDE.
... and for extensions to zero price IDE.

david.prentice wrote:
But as a hobbyist I look at the price.    They ask a LOT of money for a non-C++ compiler.
Some GCC third parties recognize the price issue.

 


XC8 PRO Compiler | AVR Freaks

 

https://www.gnu.org/licenses/gpl-faq.html#GPLInProprietarySystem

 

VisualGDB - Serious cross-platform support for Visual Studio (Sysprogs)

BSPTools/DebugPackages at master · sysprogs/BSPTools · GitHub

 

AdaCore Launches New GNAT Pro Product Lines - AdaCore

[end of fourth paragraph]

The product [Developer] is especially suited to C and C++ programmers implementing small-footprint embedded systems and looking for a simple transition path to a more reliable language.

GNAT Pro Developer is for Arm and RISC-V.

GNAT Pro Developer - AdaCore

 

"Dare to be naïve." - Buckminster Fuller

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

Functional Safety | Microchip Technology

[mid-page]

TÜV SÜD-Certified Compilers

 

"Dare to be naïve." - Buckminster Fuller

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

meolsen wrote:
Basically it (finally) enables the  V4 version core pragma:

Core Descriptions | AVR® Instruction Set Manual

[AVRxt]

"Dare to be naïve." - Buckminster Fuller

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

avrasm2 core pragma, not a publicly named ISA, unfortunately

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

"Dare to be naïve." - Buckminster Fuller

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

Can't call it MS7 that would just lead to confusion so I am going to call it MCS7 as in MicroChip Studio 7.

 

 

Why is the load time less, it is almost within my 30 second timer (the one where I start looking for other options). I use to be able to walk form a far bedroom to the carport and start my test bench computer (Linux) then walk back, obviously that was insufferable. Maybe it was a glitch in the matrix.

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

meolsen wrote:
Here's the release notification

in that release notification, meolsen wrote:
AVR GCC Toolchain, Arm GCC Toolchain, and the MPLAB XC8 Compiler with AVR devices support

 

Is there not an XC32 for AVR32 ... ?

 

cheeky

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

At least on large projects, there should be noticeable speedups in both load and navigation...

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

Oh, and a point that is not mentioned, Studio should now not crash on a FIPS 140-2 compliant windows system... Hopefully wink

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

Is there any benefit of using Free XC8 version over AVR GCC compiler ? I see optimization level -O3 and -Os are disabled in XC8 compiler but -O1 and -O2 is available. Any reason to switch to XC8 for old ATmega's ?

“Everyone knows that debugging is twice as hard as writing a program in the first place. So if you're as clever as you can be when you write it, how will you ever debug it?” - Brian W. Kernighan
“Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.” - Antoine de Saint-Exupery

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

May the following answer your questions :

XC8 PRO Compiler | AVR Freaks

 

"Dare to be naïve." - Buckminster Fuller

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

The Live Watch function seriously affects The execution of The program, which makes me feel very bad.

 

Expect register ports are as visible as Visual Studio.

 

 

Last Edited: Sun. Nov 15, 2020 - 01:11 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Your point being ..?

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

dongran wrote:
The Live Watch function seriously affects The execution of The program, which makes me feel very bad.

 

Care to explain that in better detail?  THe part about how live watch seriously affecting program execution.  Like what Micro you are debugging, and teh interface being used.  As far as you feeling bad about it....thats on you to resolve.  We can offer no solutions for that.

 

Jim

I would rather attempt something great and fail, than attempt nothing and succeed - Fortune Cookie

 

"The critical shortage here is not stuff, but time." - Johan Ekdahl

 

"Step N is required before you can do step N+1!" - ka7ehk

 

"If you want a career with a known path - become an undertaker. Dead people don't sue!" - Kartman

"Why is there a "Highway to Hell" and only a "Stairway to Heaven"? A prediction of the expected traffic load?"  - Lee "theusch"

 

Speak sweetly. It makes your words easier to digest when at a later date you have to eat them ;-)  - Source Unknown

Please Read: Code-of-Conduct

Atmel Studio6.2/AS7, DipTrace, Quartus, MPLAB, RSLogix user

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

I have tested the latest IDE on UC3C-EK, and as with previous versions, The Live Watch function seriously interfere with the running of the program, and registers and IO ports are still not visible in real time.

 

 

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

When I add 2 variables to the Live Watch window, and then run the program, the program execution becomes significantly slower.

 

When debugging is halt, microchip studio and visual studio 2015 are same. When debugging is running, the peripheral window will be invalid. Can you change it? Just like visual studio 2015, when running, The peripheral window is still valid,we can observe the value of peripheral ? 

Thanks.

Last Edited: Sun. Nov 15, 2020 - 02:04 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

dongran wrote:
The Live Watch function seriously interfere with the running of the program, and registers and IO ports are still not visible in real time.

 

Help me out here....I know of a Watch Window where you can see variables and registers Etc., but they are only viewable when you pause the execution of the program.  Are you referring to that window or something else?  If you are referring to teh Watch window, that has no bearing on your programs execution.

 

JIm

I would rather attempt something great and fail, than attempt nothing and succeed - Fortune Cookie

 

"The critical shortage here is not stuff, but time." - Johan Ekdahl

 

"Step N is required before you can do step N+1!" - ka7ehk

 

"If you want a career with a known path - become an undertaker. Dead people don't sue!" - Kartman

"Why is there a "Highway to Hell" and only a "Stairway to Heaven"? A prediction of the expected traffic load?"  - Lee "theusch"

 

Speak sweetly. It makes your words easier to digest when at a later date you have to eat them ;-)  - Source Unknown

Please Read: Code-of-Conduct

Atmel Studio6.2/AS7, DipTrace, Quartus, MPLAB, RSLogix user

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

When debugging is halt, microchip studio and visual studio 2015 are same. When debugging is running, the peripheral window will be invalid. Can you change it? Just like visual studio 2015, when running, The peripheral window is still valid,we can observe the value of peripheral ? 

Thanks.

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

Post a screenshot of what you are referring to.  If it' teh peripheral window I am thinking of the answer is no.  During runtime the peripheral watch window is inactive.  When you halt the program execution the window is updated with the latest contents of the peripherals.  It has NO bearing on program execution.

 

Jim

I would rather attempt something great and fail, than attempt nothing and succeed - Fortune Cookie

 

"The critical shortage here is not stuff, but time." - Johan Ekdahl

 

"Step N is required before you can do step N+1!" - ka7ehk

 

"If you want a career with a known path - become an undertaker. Dead people don't sue!" - Kartman

"Why is there a "Highway to Hell" and only a "Stairway to Heaven"? A prediction of the expected traffic load?"  - Lee "theusch"

 

Speak sweetly. It makes your words easier to digest when at a later date you have to eat them ;-)  - Source Unknown

Please Read: Code-of-Conduct

Atmel Studio6.2/AS7, DipTrace, Quartus, MPLAB, RSLogix user

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

Any form of "live watch" involves the code not running at full speed but running one step, stopping, reading/updating the state of the variable then continuing. It's bound to be slow, what were you expecting? (To be honest such a function is a bit of a toy and of little practical use anyway).

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

Actually, the UPDI unit can read some parts of memory, including SRAM and most I/O registers, without pausing execution (i.e. not using any debug commands, which are proprietary anyway...).

Probably if the CPU unit and UPDI unit try to read at the same time, a delay will happen, but still, true live monitoring seems to be possible for UPDI devices, in theory.

 

note: only for variables that the updi can read atomically, that is, 8 and possibly 16 bit in size.

Last Edited: Sun. Nov 15, 2020 - 05:05 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Don't know how much of UC3 OCD is implemented in Microchip Studio.

UC3C-EK has a NEXUS connector for AVR ONE!; the data is into AVR ONE! though I don't know where the data goes (hope a UC3 operator follows this thread)

IIRC, UC3 NanoTraceTM is in Atmel-ICE.

 

AVR® UC3 On-Chip Debug System | Atmel-ICE

...

  • Real-time Program Counter branch tracing, data trace, process trace (supported only by debuggers with parallel trace capture port)

...

Auxiliary (AUX) Physical (including JTAG) | AVR ONE!

Atmel Studio 6.2 Service Pack 1 | Microchip Studio Release Note

...

  • Support for trace buffers for Arm (MTB) and 32-bit AVR UC3 (NanoTrace)

...

 


UC3C-EK

AVR ONE!

 

"Dare to be naïve." - Buckminster Fuller

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

El Tangas wrote:
... without pausing execution ...
to elaborate, arbitration between UPDI and CPU is a part of the instruction timing.

El Tangas wrote:
(i.e. not using any debug commands, ...
iow, uses the UPDI instructions per the datasheet.

El Tangas wrote:
... true live monitoring seems to be possible for UPDI devices, in theory.
Would be useful when actualized (UPDI PDY is akin to a 1-wire UART, PDI PHY is akin to a USART)

 


Instruction Set Summary | AVR® Instruction Set Manual

[mid-page, AVRxt]

Table 4. Data Transfer Instructions

Instruction Set Summary | AVR® Instruction Set Manual

[bottom]

2.Cycle time for data memory access assumes internal RAM access, and are not valid for access to NVM. A minimum of one extra cycle must be added when accessing NVM. The additional time varies dependent on the NVM module implementation. See the NVMCTRL section in the specific devices data sheet for more information.

 

AVR - Calibration & Daq toolchain? | AVR Freaks

 

"Dare to be naïve." - Buckminster Fuller

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

In the 'Release of Microchip Studio 7.0.2542' anouncement, meolsen wrote:

One of the major new features associated with the Microchip Studio release, is that it is now bundled with the free version of Microchip’s XC8 compiler. This is installed and ready for use with the IDE.

 

This high-quality C/C++ compiler supports all of Microchips 8-bit PIC and AVR devices, with the Studio version supporting AVR architecture. In addition, there is an upgrade path to the XC8 PRO compiler for AVR.

 

https://www.avrfreaks.net/forum/...

 

But, in #22 here, meolsen wrote:
XC8 does not support C++ (I know, I know...)

 

https://www.avrfreaks.net/commen...

 

EDIT

 

Correct post number

 

See also: #30

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...
Last Edited: Wed. Jan 6, 2021 - 09:41 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0


I have a ATMega 2560 board with external RAM. I map data to the the XRAM (along with Stack) and all has been fine with Atmel Studio 7.0.2389 (for years) until installing the new Microchip Studio. Now I get an error:

 

address 0x80300a of xxx.elf section `.data' is not within region `data'

I get the same error several times for .data, .bss

 

Nothing has changed but the studio install. I map the memory in the Linker Misc section like so:

 

 

I uninstalled Microchip Studio and reinstalled the previous Atmel Studio and all is good.

 

 

Any suggestions?

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

Don't you mean 

-Wl,--section-start=.data=0x802500

 It looks to me like you have a comma after "section-start" ?

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

Wow - good catch! I looked at that no telling how many times and didn't see it. Funny thing is this version doesn't care. It builds and maps the same either way. Gonna see if the new version is just less tolerant of such stuff.

Thanks.

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

"Dare to be naïve." - Buckminster Fuller

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

I could not make it work with SEGGER J-Link (tool is simply not visible) for some Cortex-M3 development. I had to go back to Atmel Studio.

Is it just me?

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

rrrrgggg wrote:
I could not make it work with SEGGER J-Link (tool is simply not visible) for some Cortex-M3 development. I had to go back to Atmel Studio.

You need to give more details on what, exactly, you did and what problem(s), exactly, you are facing.

 

Sounds like you had the Segger stuff already installed, then updated Studio - yes?

 

So can you do an update/refresh of Segger after the Studio update? Perhaps Segger could help with that...

 

https://forum.segger.com/index.php/Board/3-J-Link-Flasher-related/

 

Is the J-Link a genuine Segger? or one of the Atmel/Microchip "OEM" versions? or an ebay "knock-off"? or ... ?

 

for some Cortex-M3 development

You mean its OK for some other Cortex-M3? What about other Cortex-M?

 

etc, etc, ...

 

 

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

First of all, thank you for trying to help!

 

Sounds like you had the Segger stuff already installed, then updated Studio - yes?

Yup. All installed and working properly. I could successfully flash the hex file using the JFlash-Lite.exe (last version 6.94).

 

| So can you do an update/refresh of Segger after the Studio update? 

Done that. Did not work. I tried also some older versions of J-Link.

 

Is the J-Link a genuine Segger?  

Yes. J-Link-EDU. Working properly with Keil and other STM32 Dev. tools.

 

| You mean its OK for some other Cortex-M3?    

I only tried with ATSAM3X8E because I had to modify/recompile an old project.

But the tool is not shown in the IDE (device programming / tool selection).

 

As I said, I reinstalled the last Atmel Studio version (7.0.2389) and J-Link was 'discovered' and I could use it to debug/flash the application.

  

 

 

 

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

rrrrgggg wrote:
... I reinstalled the last Atmel Studio version (7.0.2389) and J-Link was 'discovered' ...
Possibly an instance of "DLL Hell" (IIRC, by Cliff)

Issues with Arm Compatible Tools | Microchip Studio Release Note

Microchip Studio for AVR® and SAM Devices | New and Noteworthy | Microchip Studio Release Note

...

 

Atmel Studio 7.0.2389

...

  • AVRSV-8130: Studio picks up old JLinkArm.dll instead of the installed one

...

 

"Dare to be naïve." - Buckminster Fuller

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

gchapman wrote:

Possibly an instance of "DLL Hell" (IIRC, by Cliff)

"DLL hell" is usually reserved for instances of Windows "Side by Side" problems. All EXE and DLL have a "manifest" embedded within them (actually a chunk of XML) and it's basically a "shopping list" so it may say it links to msvcrt.dll but the manifest will possibly say "msvcrt.dll 11.7.21865" or something. Then every time you install a program on your Windows machine that happens to deliver a copy of what on the outside just looks like "msvcrt.dll" it will put the 15 or 20 different copies of msvcrt.dll it has received over time in the \Windows\WinSxS\ repository so that when a program does a LoadModule("msvcrt.dll") (either explicitly or implicitly through the linking) the windows loader will take a look at the manifest, find exactly which version of the file it is and see if it can find a copy in the WinSxS repository.

 

Actually perhaps msvcrt is a bad example? On my machine I actually have very few of those:

C:\Windows\WinSxS>dir | grep msvcrt
12/06/2019  01:20    <DIR>          amd64_microsoft-windows-msvcrt_31bf3856ad364e35_10.0.17763.1_none_c21b2005f70f89a9
12/06/2019  01:03    <DIR>          amd64_microsoft-windows-msvcrt_31bf3856ad364e35_10.0.17763.475_none_45fd552524a859da
12/06/2019  01:37    <DIR>          wow64_microsoft-windows-msvcrt_31bf3856ad364e35_10.0.17763.1_none_cc6fca582b704ba4
12/06/2019  01:03    <DIR>          wow64_microsoft-windows-msvcrt_31bf3856ad364e35_10.0.17763.475_none_5051ff7759091bd5
15/09/2018  07:29    <DIR>          x86_microsoft-windows-msvcrt20_31bf3856ad364e35_10.0.17763.1_none_82cb2ad1109df481
15/09/2018  07:29    <DIR>          x86_microsoft-windows-msvcrt40_31bf3856ad364e35_10.0.17763.1_none_83ae392d100bfd8f

C:\Windows\WinSxS>

However looking at \windows\winsxs I sure have a few DLL duplicates...

           19570 Dir(s)  164,045,635,584 bytes free

"DLL hell" occurs when you have 15 different msvcrt's or something but none of them is actually the manifest version a program you are trying to run needs to find!

 

(when DLL Hell occurs you can get some very mysterious messages out of Windows almost all of which give no real idea of what the problem actually is - and that's really the main part of the problem).

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

rrrrgggg wrote:
Working properly with Keil and other STM32 Dev. tools

could it be that one of the "other tools" has "grabbed" the J-Link, so that Studio can't see it ... ?

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

 

could it be that one of the "other tools" has "grabbed" the J-Link, so that Studio can't see it ... ?

I'm not so sure about that !

If I'm not mistaken there is a file indicating the fully qualified path to the J-Link installation (eg C:\Program Files (x86)\SEGGER\JLink_V694\) and that location contains also the correct MS DLLs (msvcr100.dll, msvcp100.dll). JLinkARM.dll has no other dependencies!

 

While reinstalling Segger's software I noticed that Microchip Studio is not detected (Keil uVision is always detected!!!) so the JLinkARM.dll is not copied to the directory '../Studio/7.0/atbackend/'.

I tried to copy the file(s) manually but without any luck.

It is also worth mentioning that Atmel Studio only works with a specific JLinkARM.dll (v6.48A from 2019).

 

Last Edited: Mon. Jan 18, 2021 - 03:35 PM
This reply has been marked as the solution. 
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

"Dare to be naïve." - Buckminster Fuller

Last Edited: Wed. May 18, 2022 - 01:13 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I feel uncomfortable in this moment of Atmel Studio/MicroChip Studio history.
Microchip was released sam D series, where errata is near long as datasheet, he released SAM E5x series with ethernet port but without ethernet (media acces controller) and he released new tinny avr uC but semantics and programming interface is not backward compatybile with "real" AVR's - i can not copy/paste code from repos to new uC (ofc on register logic level) - any way i feel bad with all this things.
An my SAM E70 with it cost around $15 have I2S only on paper.
One hour later i thinking about instal "new" ide but not so quiclky. I will wait one year, in this time you will find all bugs and this ide should grow up.
Merde.
I will miss the atmel documentation and nomenclature  style.

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

Hullala you spoke French.

John Samperi

Ampertronics Pty. Ltd.

https://www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

analityk wrote:
I feel uncomfortable in this moment of Atmel Studio/MicroChip Studio history.
Concern here (sword of Damocles?)

analityk wrote:
... released SAM E5x series with ethernet port but without ethernet (media acces controller) ...
Source code?  If yes that's in MPLAB Harmony and Atmel START.

analityk wrote:
An my SAM E70 with it cost around $15 have I2S only on paper.
indecision

analityk wrote:
... and this ide should grow up.
... or transform (hope)

analityk wrote:
I will miss the atmel documentation and nomenclature  style.
Change is always present.

 


https://github.com/Microchip-MPLAB-Harmony/net/blob/master/driver/gmac/config/drv_intmac_gmac.py#L87

 

What is SSC? How to Configure SSC for Audio Applications

https://github.com/atmelcorp/atmel-software-package/blob/master/target/samv71/board_same70-xplained.h

SAM E70 Xplained Evaluation Kit

 

"Dare to be naïve." - Buckminster Fuller

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

errata https://ww1.microchip.com/downlo...

page 27, point 2.11.1

This is not ide issue but still microchip product.

https://ww1.microchip.com/downlo...
page 16. point 9

I would like to have two IDEs on a PC and compare them myself. As long as I have projects running in AS and I won't change the IDE, it's suicide.

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

Thanks for the errata.

analityk wrote:
I would like to have two IDEs on a PC and compare them myself.
One way is by Linux containers as Windows containers don't have USB (may be in Windows 10X)

analityk wrote:
As long as I have projects running in AS and I won't change the IDE, it's suicide.
Hyper-V to savewink

edit :

and KVM

 


Bench Talk | Containers: Similar To Virtual Machines For Embedded (Mouser Electronics)

What Devices are Supported | Devices in Containers on Windows | Microsoft Docs

Bringing Device Support to Windows Containers - Microsoft Tech Community - 270913

 

Visual Studio 2015 Update 1 incapacitates Atmel Studio 7 | AVR Freaks (Hyper-V)

Importing Virtual Machines and disk images | Qemu/KVM Virtual Machines - Proxmox VE

...

 

Step-by-step example of a Windows OVF import

Microsoft provides Virtual Machines downloads to get started with Windows development.

...

"Dare to be naïve." - Buckminster Fuller

Last Edited: Fri. Apr 23, 2021 - 12:24 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I made the mistake of trying to upgrade from Atmel Studio. Now it crashes every time I try to tear off a file to go side-by-side. Re-installing again to try to fix it.

 

I noticed you can simply decline to install XC8. Hopefully that is not what is causing the problem as I don't want it, it's GCC or revert back to the last version of Atmel Studio.

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

maybe akin to

Microchip Studio 7.0.2542 crashes at start | AVR Freaks

via #76 but

mojo-chan wrote:
Now it crashes every time I try to tear off a file to go side-by-side.
may be a defective .NET update in WPF :

Atmel Studio 7.0.1931 crashing when docking windows in GUI | AVR Freaks

 

edit : issued solved in Microchip Studio crashes when trying to display files side-by-side | AVR Freaks

 

"Dare to be naïve." - Buckminster Fuller

Last Edited: Mon. Apr 26, 2021 - 12:28 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I've been away from AVR work since before MicroChip bought Atmel. Can't say I am encouraged by this thread. 

 

My number one question is whether to install MicroChip Studio, or Atmel Studio 5, which I have here. I am not a candidate for a commercial license, so I would only look at the free version of MicroChip Studio. But I am concerned with the issues reported here. I am not interested in battling tool defects, as my available time for the AVR projects is limited, and hobby level, so I want enjoyment, not frustration!

 

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


wmeyer wrote:
or Atmel Studio 5,
Whatever you do, do NOT use AS5. It was a steaming pile of dung riddled with the most outrageous bugs imaginable. The only really "good" version is AS7 which was recently remarketed as Microchip Studio 7.

 

The actual choice of IDEs these days is not so much between the various historical versions of Studio 4..7 but whether you use MCS7 (the latest in that line) or Microchip's "other IDE" called MPLABX. The latter has the advantage that there is a Linux as well as Windows version but other than that I cannot think of another advantage.

 

Oh and the other "decision choice" you are going to face somewhere along the journey is "gcc" or "xc8". Given that the future of AVR in "gcc" is in a state of flux right now (no guarantee it will be in GCC 10+) one might consider XC8 but the problem there is that it is no longer a "free" compiler....

Sure, there is a free version but if you want proper optimization they charge astronomically stupid money.

 

To be honest I don't know what "tool defects" you are talking about in MCS7 anyway. It's true that M$ recently released a Win10 that caused window docking in MCS7 (and many other apps) to crash. But M$ then issued a KB update to Windows that fixed the issues - so that was short term and not something Atmel/Microchip really had much control over anyway. Other than that MCS7 (aka AS7) is pretty solid.

Last Edited: Thu. Apr 29, 2021 - 02:48 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I'm not even going to install xc8 on principal. I'll stick with GCC even if newer versions drop AVR support. The older ones will work just fine unless they make some breaking architectural changes, and even then it can probably be patched. It's not like the current version is bad.

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

"Dare to be naïve." - Buckminster Fuller

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

clawson wrote:
Sure, there is a free version ...
up to optimization level 2 inclusive (iow not O3, not Os)

clawson wrote:
... but if you want proper optimization they charge astronomically stupid money.
If one can, wait for when MPLAB XC8 goes on sale; the dongle version is perpetual.

MPLAB XC8 Functional Safety is expensive though not when compared with some other commercial GCC.

clawson wrote:
But M$ then issued a KB update to Windows that fixed the issues ...
.NET (may you pardon this pedantic)

.NET was separated by later feature updates of Windows 10; work around exists for Windows 7 and Windows 8.1 (.NET is tied into these)

 

P.S.

clawson wrote:
The latter has the advantage that there is a Linux as well as Windows version but other than that I cannot think of another advantage.
MPLAB X can be in a Linux container which is an end run around the lack of VM capability; Windows 10 containers don't have USB so VM it is for Microchip Studio.

MPLAB X packs contain tool firmware.

 


Come Join Us (MPLAB Now Supports AVRs) | Page 6 | AVR Freaks

...

Standard for free ...

...

https://www.microchipdirect.com/dev-tools/Cat10_SubCat4?8-bit%20PIC%C2%AE%20MCUs&treeid=6&allDevTools=true

 

Dockerfile for MPLAB X IDE/IPE and toolchains | Microchip

 

"Dare to be naïve." - Buckminster Fuller

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


gchapman wrote:

clawson wrote:
Sure, there is a free version ...
up to optimization level 2 inclusive (iow not O3, not Os)

 

No -Og?

 

 

Very handy for debugging.

 

How compatible is XC8 with GCC? I'm just thinking that often for testing I create a "test harness" that lets me run the firmware on a Linux system (WSL2) for automated testing.

 

I don't even know why I'm asking, I won't use it on principal. Charging for compilers is a sure-fire way to guarantee I won't use your parts. Aside from the pain of licence management, especially on decade old projects I just need to make small changes to with the old version of the compiler and IDE, I just wont take the risk that you will jack up prices one day. Also I like being able to have the compiler installed on multiple machines without licence issues, rather than having to use the one system it's on every time.

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

mojo-chan wrote:
How compatible is XC8 with GCC?
Mostly though one goal of MPLAB XC is portability within MPLAB XC (XC8 to XC16 to XC32, Common C Interface [CCI])

One context for CCI is porting an AVR XMEGA B application to PIC24 (XMEGA is mature, PIC24 has an updated segment LCD controller)

mojo-chan wrote:
... often for testing I create a "test harness" that lets me run the firmware on a Linux system (WSL2) for automated testing.
Valgrind is then available on macOS, Linux, Android, and BSD for dynamic analysis.

mojo-chan wrote:
Charging for compilers is a sure-fire way to guarantee I won't use your parts.
Whereas some commercial GCC is of high quality and some value; likewise with Clang/LLVM (MPLAB XC8 v2 for PIC)

Ideally the ecosystem aids in selecting a CPU though sometimes it's the other way round (very high temperature, high radiation, ...) (ecosystem - toolchain, framework, RTOS, fora, etc)

mojo-chan wrote:
... especially on decade old projects I just need to make small changes to with the old version of the compiler and IDE, ...
Typically once a license expires the toolchain doesn't expire (iow only updates cease)

Old compilers and IDE are fine until one is fed up with defects then one pays up (license renewal) though EOS of such may force one's hand (risk of being sawed off)

mojo-chan wrote:
Also I like being able to have the compiler installed on multiple machines without licence issues, rather than having to use the one system it's on every time.
Very recent video about that :

MPLAB® XC Compiler Licenses - YouTube (5m2s)

 


Learn about the Windows Subsystem for Linux | Microsoft Docs (WSL)

 

Common C Interface Standard | MPLAB® XC8 C Compiler User’s Guide for AVR® MCU

New PIC24F MCUs Feature Low-power Animated Display Driver for Battery-powered Devices | Microchip Technology | Microchip Technology

 

Hardware and software tools for embedded developers | Static Analysis and Metrics Tools by Jack Ganssle

...

 

Matthew MacClary uses these checkers:

[1. GCC (fyi, now has an internal linter), 2. a linter, 3. Valgrind]

 

...

 

"Dare to be naïve." - Buckminster Fuller

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

gchapman wrote:

Valgrind is then available on macOS, Linux, Android, and BSD for dynamic analysis.

 

I know, Valgrind isn't really suited to the kind of thing I usually end up doing. Last one I did could simulate a 64 node RS485 network with 64 firmwares all running on a Linux host.

 

Quote:
Ideally the ecosystem aids in selecting a CPU though sometimes it's the other way round (very high temperature, high radiation, ...) (ecosystem - toolchain, framework, RTOS, fora, etc)

 

Sure, sometimes. But for most projects there is a choice, even if it's just between different ARM parts. In that case the tools make a big difference. Compare Atmel Studio to STM32 Cube IDE or whatever it's called, for example.

 

PICs have mostly been a non-starter due to the crappy nature of the tools, at least for me.

 

Quote:
Typically once a license expires the toolchain doesn't expire (iow only updates cease)

 

I wish Keil knew that... And even so, it's the hassle of digging out the licence, or transferring it to someone else. If it can be transferred.

 

Quote:
Old compilers and IDE are fine until one is fed up with defects then one pays up (license renewal) though EOS of such may force one's hand (risk of being sawed off)

 

When a project is complete I make sure I have a VM with all the development tools in it that I can spool up later if needed. When it's some minor change I can just fire it up. Had some going back to Windows 2000, more on XP. Actually I did have a couple of VMs for old PIC based projects. The compiler was... Hisoft? I think theirs became the official Microchip one later. Anyway that saved me a lot of pain more than once when I needed to make changes and that ancient version of the compiler wouldn't run on Windows 7.

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

mojo-chan wrote:
Compare Atmel Studio to STM32 Cube IDE or whatever it's called, for example.
STM32CubeIDE

The embedded systems software IDE based on Microsoft Visual Studio :

  • VisualGDB
  • Microchip Studio

Any more?

Microchip Technology stands out in the crowd in a very good way (Microsoft Visual Studio ecosystem)

mojo-chan wrote:
PICs have mostly been a non-starter due to the crappy nature of the tools, at least for me.
Can do a lot outside of MPLAB X other than debugging.

Microchip Technology seems to have a significant number of third parties for tools.

mojo-chan wrote:
When a project is complete I make sure I have a VM with all the development tools in it that I can spool up later if needed.
Less in weight than VM are containers though no USB in Windows containers (probably corrected in Windows 10X); conversely, there are a number of VM managers.

mojo-chan wrote:
The compiler was... Hisoft? I think theirs became the official Microchip one later.
HI-TECH Software

Superseded by a variant of Clang (MPLAB XC8 v2 for PIC, up to C99 inclusive)

 


Supported IDEs - SEGGER Wiki

Announcing VisualGDB 5.4 Preview 3 with Segger J-Trace support | Sysprogs

Diagnosing Complex Memory Corruption Problems with Segger J-Trace – VisualGDB Tutorials

 

Working Outside of MPLAB® X IDE - Developer Help

BoostC++ | SourceBoost Technologies (PIC)

Myths and legends of PIC microcontrollers | jaromir.sukuba | Hackaday.io

 

Bench Talk | Containers: Similar To Virtual Machines For Embedded

 

Microchip Technology Acquires HI-TECH Software

 

"Dare to be naïve." - Buckminster Fuller

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

Microchip Technology stands out in the crowd in a very good way (Microsoft Visual Studio ecosystem)

While Visual Studio is very "polished", there are several things to dislike about it: windows only and "installs gigabytes of stuff scattered all over the filesystem" is another.

Trying to use MPLABX and associated tools, I am frequently frustrated "what is that THERE?", "Why did it do THAT?", "Seems amateurish."  (I don't know whether those are MPLABX specific or Netbeans generic issuws.)

 

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

westfw wrote:
While Visual Studio is very "polished", there are several things to dislike about it: windows only ...
Visual Studio Code may be the future.

westfw wrote:
... and "installs gigabytes of stuff scattered all over the filesystem" is another.
Swing a VM?

 


AVR Studio On Mac & Linux? | AVR Freaks

AVR Helper - Visual Studio Marketplace

 

Download a Windows 10 virtual machine - Windows app development

 

"Dare to be naïve." - Buckminster Fuller

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

gchapman wrote:

Visual Studio Code may be the future.

 

smiley But let's keep in mind that VSCode is an editor; it is only lightweight when compared with a monolithic IDE, which it is not. VSCode has modules that can add many of the features of those bloated beasts, but they are optional; it is acceptably fast as an editor. The downside is the AVR developer will need to learn how to role a Makefile (or equivalent). The upside is, as an editor, the coverage is deep; I have used it with Python, Markdown, Javascript, Jupiter notebooks, JSON, CSV.

 

 

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

So, I recently opened Atmel Studio 7 after several years of no programming to modify a file for a project.  I made the changes and hit the start button to upload the code to the device, only to be hit with the dreaded error:  "There were build errors. Would you like to continue and run the last successful build?"  Needless to say I was not happy. 

 

I could build and upload the code successfully right after opening and loading my files into AS7, but if I made even ONE tweak to the code and tried to build the file I would get this error.  I did online research and found this was a fairly common occurrence with a few suggested fixes; none of which worked.  I then downloaded and installed Microchip Studio thinking it would help.  It didn't.  I still have exactly the same problem. 

 

So, where does this stand now?  Did Microchip ever truly fix this bug after taking over AS7 and if so, what is the answer?  I am tearing my hair out trying to figure this out.  Does anybody have any pertinent information on how to solve this?  If not, what are recommendations for a good IDE that is not the Microchip solution?  TIA

 

Hahnsolo

Last Edited: Wed. Apr 20, 2022 - 04:01 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Schlepper wrote:
"There were build errors.

So what "build errors" did you get, look in the output tab, not the error tab, and copy paste the results here.

Jim

 

 

FF = PI > S.E.T

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0
------ Build started: Project: CO2 Laser Tube Test Box Rev-B, Configuration: Debug AVR ------
Build started.
Project "CO2 Laser Tube Test Box Rev-B.cproj" (default targets):
Target "PreBuildEvent" skipped, due to false condition; ('$(PreBuildEvent)'!='') was evaluated as (''!='').
Target "CoreBuild" in file "C:\Program Files (x86)\Atmel\Studio\7.0\Vs\Compiler.targets" from project "K:\Chahn\Software Projects\CO2 Laser Tube Test Box - No LINX\CO2 Laser Tube Test Box - No LINX\CO2 Laser Tube Test Box Rev-B.cproj" (target "Build" depends on it):
	Task "RunCompilerTask"
		Shell Utils Path C:\Program Files (x86)\Atmel\Studio\7.0\shellUtils
		C:\Program Files (x86)\Atmel\Studio\7.0\shellUtils\make.exe all --jobs 8 --output-sync
		make: stat: .././main.c: Invalid argument
		make: *** No rule to make target '.././main.c', needed by 'main.o'.  Stop.
	Done executing task "RunCompilerTask" -- FAILED.
Done building target "CoreBuild" in project "CO2 Laser Tube Test Box Rev-B.cproj" -- FAILED.
Done building project "CO2 Laser Tube Test Box Rev-B.cproj" -- FAILED.

Build FAILED.
========== Build: 0 succeeded or up-to-date, 1 failed, 0 skipped ==========

Here is the entirety of the output window after a failed attempt at building the file. . .

 

Last Edited: Wed. Apr 20, 2022 - 06:43 PM