From a quick read, the changes from 4.15 to 4.20 :
Compilers - removal of AVR GNU
SAM E70 and SAM S70
Readme for MPLAB X IDE.htm
...
11 What's New in v4.20
...
Support for SAM E70 using MPLAB ICD 4 or MPLAB PICkit 4 (using AC102015) - Selected SAM devices supported. No support for EDBG, e.g. Xplained boards not supported.
So what does all this mean? That instead of the free Atmel Studio Suite that works with ALL Atmel components.....and that many complain about, we are going to be forced to PURCHASE compilers for each device family we want to work with? And maintenance fees as well?
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
If you are building a legacy project or would prefer to use the old command-line driver you may instead run the avr-gcc driver application and use appropriate command-line options for that driver. Those options may differ to those described in this guide.
#5 "If you think you need floating point to solve the problem then you don't understand the problem. If you really do need floating point then you have a problem you do not understand."
Presumably they PAY Microsoft for the core of Studio? Perhaps someone at Mchip has been asked to sign a cheque and was surprised to see how big it was?
MPLAB X IDE v5.0 Now Provides Beta Support For AVR® MCUs
...
Getting started with AVR in MPLAB X IDE
...
(Downloads tab, Release Notes, unzip, Readme for MPLAB X IDE.htm)
11 What's New in v5.00
· New Project format – Projects created in or updated to v5.00 are not backward compatible! However, there is a plugin you can use to revert projects (Tools>Plugins>Available Plugins>Save As v4.xx Project).
MPLAB X IDE projects now support packs, found under <MPLAB X IDE install directory>\v5.00\packs. Packs contain versioned device information.
· Support for AVR devices using Atmel-ICE (EDBG) or PICkit 4 (UPDI) – Selected AVR devices supported only on stated tools.
· Support for Atmel-ICE (EDBG) – Atmel embedded debugger (EDBG) support using Atmel-ICE.
· MPLAB XC8 AVR support – Support for AVR devices in MPLAB XC8 v2.00.
· AVR Language tool support – Support for AVR GCC and AVRASM2.
· Support for some Dual Core Devices – Support added for some dual core (dsPIC33C) devices.
#5 "If you think you need floating point to solve the problem then you don't understand the problem. If you really do need floating point then you have a problem you do not understand."
MPLAB is (currently) lumping Power Debugger, EDBG, mEDBG and Atmel-ICE into the same 'device support matrix', i.e the same device support level applies to all...
:: 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.
Did you use debugWIRE or ISP? How big an executable?
AFAIK I used debugWIRE. At the end of programming a dialog box pops up and asks whether to keep debugWIRE enabled or revert to ISP (program-only) mode. The file was small, about 2.5kB. I didn't time it, but it seemed similar to AS7.
EDIT: forgot to answer the first question:
Not painful at all. I imported an AS7 project into MPLABX and, while the three configurations were imported, the symbols defined in Project -> Properties -> Toolchain were lost. But after correcting that the project built without incident.
I think Joey Morin started a thread about this LOCALE thing elsewhere. Clearly something has crept into later avr-gcc that has maybe only been tested in one locale.
Hints about future programming/debugging hardware are starting to appear.
AC102015
Microchip Technology ICD4 RJ45 Debugger Adapter Board
Microchip ICD4 RJ45 Debugger Adapter Board is designed for debugging SAM Xplained and legacy AVR® demonstration boards with MPLAB ICD4 and PICkit 4 debuggers. This debugger adapter board supports SWD, JTAG, and ICSP protocols in various connector formats. The debugger adapter board is compatible with MPLAB PICkit 4 ICSP, SEGGER J-link JTAG SWD, SEGGER J-link EJTAG, Atmel-ICE, and power debugger JTAG SWD/AVR JTAG.
FEATURES
Debugs legacy AVR and SAM Xplained demonstration boards
Protocols supported:
JTAG
SWD
ICSP
Compatible with:
MPLAB ICD 4 ICSP/JTAG
MPLAB PICkit 4 ICSP
SEGGER J-link JTAG SWD
SEGGER J-link EJTAG
Atmel-ICE and Power Debugger JTAG SWD
Atmel-ICE and Power Debugger AVR JTAG
#5 "If you think you need floating point to solve the problem then you don't understand the problem. If you really do need floating point then you have a problem you do not understand."
I think Joey Morin started a thread about this LOCALE thing elsewhere. Clearly something has crept into later avr-gcc that has maybe only been tested in one locale.
Anybody figured out how to wire up the Pickit 4 to an AVR ICSP header?
I tried that ICD4/PICkit 4 Target Adapter Board with an Atmel-ICE adapter cable and traced back the pins, somethin' aint right. Target voltage was a No-Connect, and MOSI was shorted to SCK. Also, MISO was a no connect.
I guess I should have been more specific... does this "debugger adapter board" have any logic of its own, or is it simply re-routing contacts? If the latter, then I can just design a header on my PCBs, so that the PICKIT 4 can work directly with the AVR or SAM, without "adapters" in between.
From what I've experienced there is zero documentation on the pinout of that AVR ICSP header. I know pin 2 is VTarg, pin 3 is Ground... After that I'm at a loss. I don't actually need that adapter board, I can squid cable with the best of them, just looking for support on the pinout.
I guess I should have been more specific... does this "debugger adapter board" have any logic of its own, or is it simply re-routing contacts? If the latter, then I can just design a header on my PCBs, so that the PICKIT 4 can work directly with the AVR or SAM, without "adapters" in between.
It's just a pinout adapter/rerouter, gives convenience factor for having an ICD4 adapter and Pickit 4 adapter, especially if your targets have 50mil headers.
If you have 0.1" headers making a quick harness/adapter is easy, if you know the specifics on your guzintas and gozoutas.
Selected popular parts have been added to the IDE, and the IDE features the ability to request support for parts not currently featured within the IDE.
...
One other development, Microchip’s newly released, low-cost PICkit™ 4 In-Circuit programming and debugging development tool also currently provides Beta support for AVRs.
I imported an AS7 project into MPLABX and, while the three configurations were imported, the symbols defined in Project -> Properties -> Toolchain were lost. But after correcting that the project built without incident.
Turns out this was user error, not an issue with MPLABX.
via https://plus.google.com/+MicrochipTech/posts/A5fNnaJ2aPu
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Topvia https://plus.google.com/+MicrochipTech/posts/FAGFecSzkfv
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopA new arrival at
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopCurrently out-of-stock at microchipDIRECT though with an ETA of 02-Apr'18.
IIRC, the sales price on an invoice is honored on restock.
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopI wish they would lower the AtmelICE prices back down to the same level.
- Log in or register to post comments
TopFrom a quick read, the changes from 4.15 to 4.20 :
http://www.microchip.com/mplab/mplab-x-ide
http://www.microchip.com/development-tools/pic-and-dspic-downloads-archive
http://www.microchip.com/design-centers/32-bit/sam-32-bit-mcus/sam-e-mcus
http://www.microchip.com/design-centers/32-bit/sam-32-bit-mcus/sam-s-mcus
http://www.microchip.com/developmenttools/ProductDetails/PartNO/DV164045 (MPLAB ICD 4)
http://www.microchip.com/developmenttools/ProductDetails/PartNO/PG164140 (MPLAB PICkit 4)
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopSo that didn't last long, then!
Top Tips:
- Log in or register to post comments
Top250USD minus 75USD (Jul'18 dev tool sale)
via
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopMaybe wait for MPLAB X 5.0?
http://ww1.microchip.com/downloads/en/DeviceDoc/MPLAB_XC8_C_Compiler_User_Guide_for_AVR.pdf
http://ww1.microchip.com/downloads/en/DeviceDoc/Readme_XC8_for_AVR.pdf
- Log in or register to post comments
TopEither wow or oh no ... at least the current XC8 pro is on sale so a reasonable price may be reached.
Compiler invocations per http://ww1.microchip.com/downloads/en/DeviceDoc/MPLAB_XC8_C_Compiler_User_Guide_for_AVR.pdf :
Atmel did not compete with second parties; Microchip will compete with IAR, HP InfoTech, and Imagecraft Creations.
via https://www.microchipdirect.com/product/DevToolDeals
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopSo what does all this mean? That instead of the free Atmel Studio Suite that works with ALL Atmel components.....and that many complain about, we are going to be forced to PURCHASE compilers for each device family we want to work with? And maintenance fees as well?
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
- Log in or register to post comments
TopFor me it means to just use chips supported by whatever the latest free version of AS7 (or even AS4??) is. But I'm in a fortunate position I guess.
John Samperi
Ampertronics Pty. Ltd.
www.ampertronics.com.au
* Electronic Design * Custom Products * Contract Assembly
- Log in or register to post comments
Top- Log in or register to post comments
TopThank you for your post.
http://www.microchip.com/images/default-source/default-album/180622-dvtl-bnr-avrinxide-1170x360.jpg
or
Edits: URL, JPG
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Top</WAG>
It's the end of an epoch ... it's the beginning of the next epoch.
http://llvm.org/docs/ReleaseNotes.html#changes-to-the-avr-target (AVR LLVM 7)
http://releases.llvm.org/6.0.0/LICENSE.TXT (7's ETA is 2018-Sep-05)
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopHmmm - so what will that mean for Arduino ... ?
Top Tips:
- Log in or register to post comments
TopWhat was that thing about Microchip never discontinuing a product while you're still using it ... ?
Top Tips:
- Log in or register to post comments
TopThey won't discontinue Studio; they might stop future development on it though which is a different thing.
Although, how much of Studio is their's?
#1 Hardware Problem? https://www.avrfreaks.net/forum/...
#2 Hardware Problem? Read AVR042.
#3 All grounds are not created equal
#4 Have you proved your chip is running at xxMHz?
#5 "If you think you need floating point to solve the problem then you don't understand the problem. If you really do need floating point then you have a problem you do not understand."
- Log in or register to post comments
TopPresumably they PAY Microsoft for the core of Studio? Perhaps someone at Mchip has been asked to sign a cheque and was surprised to see how big it was?
- Log in or register to post comments
TopFSF AVR GCC is complete "enough".
xc8-gcc may have a dual license (GPL, commercial); another GCC contributor has dual licensing with GCC patches once per year.
Edit:
XC8-GCC release periods may be similar to XC16.
XC16 version, source code date
1.31, 2017-Feb-20
1.32B, 2017-Aug-23
1.33, 2017-Oct-18
1.34, 2018-Apr-02
1.35, 2018-Jun-12
current XC16 is 1.35 (6/20/18)
http://www.microchip.com/mplab/compilers (Downloads tab)
Edit1 : XC16 : 1.34, 1.35
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopOne or an entity joins the Visual Studio Partner Program at some level.
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Topwith thanks to Greg_Muth and his https://www.avrfreaks.net/forum/hint-thing-come#comment-2516531
http://www.microchip.com/mplab/compilers
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
Toprestored in MPLAB X v5.00
http://www.microchip.com/mplab/mplab-x-ide
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopI've cut down the device support list to just show AVR parts...
PK4 is the Microchip Pickit4
ICD4 is the Microchip ICD4
AICE is the Atmel ICE
P means program
D means debug
[EDIT]
Formatting in PDF tidied.
Attachment(s):
#1 Hardware Problem? https://www.avrfreaks.net/forum/...
#2 Hardware Problem? Read AVR042.
#3 All grounds are not created equal
#4 Have you proved your chip is running at xxMHz?
#5 "If you think you need floating point to solve the problem then you don't understand the problem. If you really do need floating point then you have a problem you do not understand."
- Log in or register to post comments
TopVery useful chart. Hope you are able to maintain it until there is something comparable from "the front office".
Jim
Until Black Lives Matter, we do not have "All Lives Matter"!
- Log in or register to post comments
Top@Brian Fairchild wrote:
The device support provided by Microchip appears to be inaccurate. A number of "Alternate Tools" are available:
And I just programmed a MEGA328PB X-Mini through its mEDBG:
Greg Muth
Portland, OR, US
Xplained/Pro/Mini Boards mostly
Make Xmega Great Again!
- Log in or register to post comments
TopHow painful was that?
Did you use debugWIRE or ISP? How big an executable?
A 30kB executable file takes over two minutes on AS7 over debugWIRE with XMINI-328PA (and times out).
I would assume that any debugging session is going to involve exactly the same traffic over mEDBG on both IDEs.
Fortunately the new UPDI works very nicely with EDBG on its XPRO. And my Tiny817-XMINI works reasonably fast on its mEDBG.
It will be interesting to see how MPLAB compares with AS7.
David.
- Log in or register to post comments
TopMPLAB is (currently) lumping Power Debugger, EDBG, mEDBG and Atmel-ICE into the same 'device support matrix', i.e the same device support level applies to all...
:: 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.
- Log in or register to post comments
Top@david.prentice wrote:
AFAIK I used debugWIRE. At the end of programming a dialog box pops up and asks whether to keep debugWIRE enabled or revert to ISP (program-only) mode. The file was small, about 2.5kB. I didn't time it, but it seemed similar to AS7.
EDIT: forgot to answer the first question:
Not painful at all. I imported an AS7 project into MPLABX and, while the three configurations were imported, the symbols defined in Project -> Properties -> Toolchain were lost. But after correcting that the project built without incident.
Greg Muth
Portland, OR, US
Xplained/Pro/Mini Boards mostly
Make Xmega Great Again!
- Log in or register to post comments
TopThere's trouble in (beta) paradise. Seems as likes to crash:
as: loadlocale.c:130: _nl_intern_locale_data: Assertion `cnt < (sizeof (_nl_value_type_LC_TIME) / sizeof (_nl_value_type_LC_TIME[0]))' failed.
avr-gcc: internal compiler error: Aborted (program as)
I opened a support ticket.
Should I be posting this in the Microchip MPLABX forum rather than here..?
Greg Muth
Portland, OR, US
Xplained/Pro/Mini Boards mostly
Make Xmega Great Again!
- Log in or register to post comments
Top- Log in or register to post comments
TopHints about future programming/debugging hardware are starting to appear.
AC102015
Microchip Technology ICD4 RJ45 Debugger Adapter Board
Microchip ICD4 RJ45 Debugger Adapter Board is designed for debugging SAM Xplained and legacy AVR® demonstration boards with MPLAB ICD4 and PICkit 4 debuggers. This debugger adapter board supports SWD, JTAG, and ICSP protocols in various connector formats. The debugger adapter board is compatible with MPLAB PICkit 4 ICSP, SEGGER J-link JTAG SWD, SEGGER J-link EJTAG, Atmel-ICE, and power debugger JTAG SWD/AVR JTAG.
FEATURES
Debugs legacy AVR and SAM Xplained demonstration boards
Protocols supported:
JTAG
SWD
ICSP
Compatible with:
MPLAB ICD 4 ICSP/JTAG
MPLAB PICkit 4 ICSP
SEGGER J-link JTAG SWD
SEGGER J-link EJTAG
Atmel-ICE and Power Debugger JTAG SWD
Atmel-ICE and Power Debugger AVR JTAG
#1 Hardware Problem? https://www.avrfreaks.net/forum/...
#2 Hardware Problem? Read AVR042.
#3 All grounds are not created equal
#4 Have you proved your chip is running at xxMHz?
#5 "If you think you need floating point to solve the problem then you don't understand the problem. If you really do need floating point then you have a problem you do not understand."
- Log in or register to post comments
Tophttps://www.avrfreaks.net/forum/ubuntu-mate-1804-lts-issue-atmel-toolchains
Not sure the issue lies with the Atmel Toolchain, although that is certainly possible, perhaps even likely.
"Experience is what enables you to recognise a mistake the second time you make it."
"Good judgement comes from experience. Experience comes from bad judgement."
"Wisdom is always wont to arrive late, and to be a little approximate on first possession."
"When you hear hoofbeats, think horses, not unicorns."
"Fast. Cheap. Good. Pick two."
"We see a lot of arses on handlebars around here." - [J Ekdahl]
- Log in or register to post comments
TopYes and no... See my response over there for a quick workaround.
:: 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.
- Log in or register to post comments
Top@meolsen wrote:
How about a quick workaround for MPLABX? I've the following pre-build commands:
None of those worked. If I prepend the actual compiler commands from the build output with LANG=C, they compile:
Is there a way to tell MPLABX to do that?
Greg Muth
Portland, OR, US
Xplained/Pro/Mini Boards mostly
Make Xmega Great Again!
- Log in or register to post comments
TopFor mplab it should be enough to export that before launching mplab_ide from the same shell ( so that mplab inherits that variable)
:: 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.
- Log in or register to post comments
Top@meolsen wrote:
I thought I had tried that, but apparently I did not, because it just worked.
Thanks!
Greg Muth
Portland, OR, US
Xplained/Pro/Mini Boards mostly
Make Xmega Great Again!
- Log in or register to post comments
TopAnybody figured out how to wire up the Pickit 4 to an AVR ICSP header?
I tried that ICD4/PICkit 4 Target Adapter Board with an Atmel-ICE adapter cable and traced back the pins, somethin' aint right. Target voltage was a No-Connect, and MOSI was shorted to SCK. Also, MISO was a no connect.
- Log in or register to post comments
TopWhich header on the adapter board did you use? It should be the bottom one one top side (the ICSP one is on the bottom side)
:: 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.
- Log in or register to post comments
TopThe one furthest from the PICkit on the top side.
So, I should be able to ring out the circuit on the bottom header to figure out how to bring this out to the AVR 100mil 2x3 header?
- Log in or register to post comments
TopJoining for updates; I'd like to know if and how the PICKIT 4 can interface with AVRs.
- Log in or register to post comments
TopEdit : PNG
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopI guess I should have been more specific... does this "debugger adapter board" have any logic of its own, or is it simply re-routing contacts? If the latter, then I can just design a header on my PCBs, so that the PICKIT 4 can work directly with the AVR or SAM, without "adapters" in between.
- Log in or register to post comments
TopThank you for the link.
I have that adapter board.
I'm wondering what to do with it.
From what I've experienced there is zero documentation on the pinout of that AVR ICSP header. I know pin 2 is VTarg, pin 3 is Ground... After that I'm at a loss. I don't actually need that adapter board, I can squid cable with the best of them, just looking for support on the pinout.
- Log in or register to post comments
TopIt's just a pinout adapter/rerouter, gives convenience factor for having an ICD4 adapter and Pickit 4 adapter, especially if your targets have 50mil headers.
If you have 0.1" headers making a quick harness/adapter is easy, if you know the specifics on your guzintas and gozoutas.
- Log in or register to post comments
TopThat is exactly what I want to know...
- Log in or register to post comments
Topvia https://plus.google.com/u/0/+digikey/posts/iQcJokqiBHu
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopThe thread that this is quoting has been edited. It appears they were working with MPLAB X 4.2 at the time.
- Log in or register to post comments
TopI wrote:
Turns out this was user error, not an issue with MPLABX.
Greg Muth
Portland, OR, US
Xplained/Pro/Mini Boards mostly
Make Xmega Great Again!
- Log in or register to post comments
Topdue to https://plus.google.com/+MicrochipTech/posts/htrPiHywn8w
"Dare to be naïve." - Buckminster Fuller
- Log in or register to post comments
TopPages