Spotted in another forum...
The newly released MPLAB X 4.00 now integrates Atmel's ARM and AVR compilers. No mention in the release notes of programming or debugging tough.
And indeed in the release notes it says...
To paraphrase Kent Brockman...
One thing is for certain: there is no stopping them; the PICs will soon be here. And I for one welcome our new silicon overlords. I’d like to remind them that as a trusted forum member, I can be helpful in rounding up others to toil in their underground support centres.
Very interesting.
I used MPLAB recently on a little project that I was asked to do and it has a few nice features, but is a bit of a confusing map to read and follow. On the other hand it's been 10+ years since I last used it for development, and I am sure if teh table was turned I would feel the same way about Studio.
No mention in the release notes of programming or debugging tough.
If they integrated programming and debugging this could be the death knoll for Studio as MPLAB is MAC and I believe LINUX compatible.
Wait and see kiddies.....wait and see.
JIm
Brian,
.
But it's not just about compilers does this mean it has a (better?) debugger and how about a simulator? Most of all is it Windows only or is there a Linux variant?
Brian, . But it's not just about compilers does this mean it has a (better?) debugger and how about a simulator? Most of all is it Windows only or is there a Linux variant?
At the moment I can't find an all encompassing announcement about this. What I've found so far is scattered among various release notes.
It would be a bit strange if it didn't have simulation and debugging.
Maybe the release of a new version of the Microchip ICD hardware debugger at the same time is somehow related.
Interesting times.
If they once again had a $49 rather than $99 entry debugger it would be good. Better yet if it does all of PIC, AVR8, AV32, ARM.
If they once again had a $49 rather than $99 entry debugger it would be good. Better yet if it does all of PIC, AVR8, AV32, ARM.
That would be nice.
It looks as thought the ICD4 does JTAG so that's an entry in ARM based chips.
this could be the death knoll for Studio as MPLAB is MAC and I believe LINUX compatible.
It would certainly seem pointless to maintain the two ...
Is MPLAB based on any "standard" framework - VS, Eclipse, ... ?
Is MPLAB based on any "standard" framework - VS, Eclipse, ... ?
IIRC it's Netbeans.
obviously an expected move !
on the positive side you have one Enviroment for MORE chip's, on the negative side you mess with PIC's complexity
also positive the MAC/LINUX build's (for the few needed it :))
a bit worried about AVR's losing their identity inside all these families and PIC's mess in there...
It would certainly seem pointless to maintain the two ...
"wonder why Morten moved to Texas?"
KAW
If I read it right, the Microchip Texas site is in Austin; the current jobs there :
http://careers.microchip.com/jobsearch/#All~Job~Categories|US+TX+Austin||d-ASC|1
Why is a good question especially on medical insurance :
Microchip
US Benefits
http://www.microchip.com/about-us/careers/us-benefits
...
Medical Coverage
Four plans are offered: three PPO plans with in-network and out-of-network coverage and an exclusive provider plan. These plans utilize the Blue Cross Blue Shield of AZ network in AZ. All sites outside of AZ utilize the Cigna network.
...
BCBS is one of the better or best USA medical insurance corporations; Cigna may be a concern (one would likely do some research)
http://www.keepaustinweird.com/
Morten went to Arizona, not Texas. THats where Mchip HQ is/was IIRC
Jim
I wonder what the (1) after Atmel Compiler means. 
Anyway I still have AS4.18, if I can't do a job with that then I'm not interested. hmmm did I ever mention "it's good to be a pensioner"? 
So John, when was your 65th?
Almost a year ago! 
Almost time to add another candle so you will be just 2 behind me. 
I wonder what the (1) after Atmel Compiler means.
It's just a note about where to install the compilers (it uses the default locations) so that the IDE can find them.
js wrote:I wonder what the (1) after Atmel Compiler means.
It's just a note about where to install the compilers (it uses the default locations) so that the IDE can find them.
And the note says:
- Install these compilers in the same location as MPLAB XC compilers so MPLAB X IDE can find them, e.g.;
C:\Program Files\microchip\ARM_GCC
C:\Program Files\microchip\AVR_GCC
No note on where MPLABS puts its compilers on a GNU/Linux system. Time to go hunting for if there where any compilers coming with the MPLABX install and where they went..
In one of the menus in MPLABX there is an entry "Xplained". Choosing it yields a message box "There are no Xplained boards connected". I'll go get the SAM D20 Xplained board right away..
If this whole thing turns out the "way it hints" then I have a long thread elsewhere here a 'freaks that can just die peacefully.. (-:
If this whole thing turns out the "way it hints" then I have a long thread elsewhere here a 'freaks that can just die peacefully.. (-:
Don't start counting your chickens.... I've installed it but it doesn't work well for me. I cannot create new Makefile projects because it complains that the file already exists no matter what I do. Also when selecting a device, the drop list for the AVR MCU's is empty.
When creating a new project there is an option for the AVR (Tiny/Mega/Xmega) family, but the device list is empty. Could be because of no compiler installed in a place where MPLABX can find it.
To know where MPLABX has it's PIC compilers I started a PIC PIC compiler isn't installed with MPLABX but installs separately when creating the first project. On my Mint the XC16 compiler ended up in /opt/microchip/xc16.
Next, I extracted the AVR Toolchain for Linux into /opt/microchip/avr8-gnu-toolchain-linux_x86_64, trying to follow the advice from the release notes.
Still no devices to pick.
About to restart...
Hi, TT_ZX. Long time.. (-:
There was an "if" in the beginning of my sentence. I still have my chicken in tucked away in another thread, as you know ;-)
Well, I cant create a makefile project because I don't get further than to here:
No matter how much I click the Next button, nothing happens. The above step in the wizard just stays put.
Now for that SAM D20 Xplained board....
Why are you picking "user makefile"? Isn't that going to be something like "external Makefile" in Studio?
MPLABX detected my SAM D20 Xplained board. (Screen shot on demand). Can't seem to do anything with it, though..
Generally it seems MPLABX on Linux is buggy at a basic UI level:
If this is what Morten is going towork on then
MPLabX for windows also has difficulties to even detect AVR toolchain , even if it mentioned in help file that it does...
i dont have experience with MPLABX but i do steps exactly as manual says.. installed toolchain from "microchip.com" site and select it in tools->options-> embeded -> toolchain
selecting avr8 toolchain says "no toolchian in this directory"
and as johan spoted, new porject -> select device list is complety empty
i believe we have to wait at least for MPLabX 4.1 to have avr working there..
as for UI level.... i believe that ANY java based program has UI and other problems, in addition to be slower by far by native compiled apps :)
I don't even have a "avr8 toolchain" to select..
as for UI level.... i believe that ANY java based program has UI and other problems, in addition to be slower by far by native compiled apps :)
I disagree. There is nothing intrinsic in Java to make the UI bad, as far as I know. It's up to the coders.
As for performance, it depends on what you mean by "by far". I'd expect and accept 5 to 20 % slower. With JIT in place most everything should perform close to native level. Is this a claim re some specific software package/library (e.g. some UI library) etc rather than Java, the abstract machine and the run-time?
Now, the UI that Microchip has put on the specific MPLAB stuff isn't the prettiest, at least not on Linux. I'm tempted to switch over to Windows and see what is working there..
selecting avr8 toolchain says "no toolchian in this directory"
Is it installed i the right directory?
well what is the "right" directory?
after your post, i tried c:\program files (86)\Microchip\avr8... seems it is accepting it there "custom toolchain"
yet again avr list is empty, so no "project" can be created..
well what is the "right" directory?
after your post, i tried c:\program files (86)\Microchip\avr8... seems it is accepting it there "custom toolchain"
yet again avr list is empty, so no "project" can be created..
The IDE readme says...
yes but if it is NOT c:program files\microchip
and it is D:\MCU\PIC OR D:\MCU\PIC\MPLABX even if i manually select folder it says "base directory does not conatin a toolchain"
ONLY under c:program files (x86)\microchip accept it, and even the as "custom" (has no AVR toolchain option at all)
And there is no C:, let alone any C:\Program Files, on a Linux system. A PIC compiler was placed in /opt/microchip/xc16 by MPLABX, so I placed the AVR Toolchain in /opt/microchip/avr8-gnu-toolchain-linux_x86_64 which to me seems like the reasonable interpretation of what to do in Linux given the "Windows pattern" given. No dice.
UI looked better on Windows, so it seems Microchip does not care enough about the UI on Linux to ship/select reasonable fonts etc. Also, the "phenomenon" of not being able to take screen shots while a menu is pulled down is not present on Windows.
plouf wrote:
well what is the "right" directory?
after your post, i tried c:\program files (86)\Microchip\avr8... seems it is accepting it there "custom toolchain"
yet again avr list is empty, so no "project" can be created..
The IDE readme says...
- Install these compilers in the same location as MPLAB XC compilers so MPLAB X IDE can find them, e.g.;
C:\Program Files\microchip\ARM_GCC
C:\Program Files\microchip\AVR_GCC
@Brian:
Have you actually tried it (or are you "just" quoting from the readme)?
If you tried and succeeded, can you give a bit of detail on how you did it?
It took about 4 years and 3 versions : studio 5, 6, 7 before that got reasonably OK so does anyone think this transition will be any less painful?
To paraphrase Kent Brockman...
One thing is for certain: there is no stopping them; the PICs will soon be here. And I for one welcome our new silicon overlords. I’d like to remind them that as a trusted forum member, I can be helpful in rounding up others to toil in their underground support centres.
For everyones reference: https://www.youtube.com/watch?v=...
Brilliant!
It took about 4 years and 3 versions : studio 5, 6, 7 before that got reasonably OK so does anyone think this transition will be any less painful?
definitely not, however at this point it does not even install's.
so we can at least create the simplest possible project (hello world ?)
Yeah but that's how AS5 started it was a complete POS that was totally unusable when it first appeared.
.
At least now they know how to build a working C compiler I guess ;-)
At least now they know how to build a working C compiler I guess ;-)
When AS5 appeared, wasn't EW already hired by Atmel? If so, they certainly had the competence to build avr-gcc inside the company..
And, IIRC, the big thing with AS6 was that it incorporated support for the 32-bit AVRs that up until then had their own AVR Studio32.
So, "One to throw away" [1], one for the 32-bitters, and one to get it right.
[1] An old programming maxim: "Prepare to throw one away".
clawson wrote:Brian, . But it's not just about compilers does this mean it has a (better?) debugger and how about a simulator? Most of all is it Windows only or is there a Linux variant?
At the moment I can't find an all encompassing announcement about this. What I've found so far is scattered among various release notes.
It would be a bit strange if it didn't have simulation and debugging.
New Compilers/Targets are relatively easy to add, but Simulation & Debug are a LOT more work.
I'd imagine they start with compilers, then add download/ISP, and eventually bring in Simulation and Debug, as resources allow.
By supporting Compilers, ALL existing MPLAB users can do a quick build-compare of any Atmel parts, as part of a selection choice.
Can't help but think that this should be discussed on the Microchip's MPLAB forum. No one here knows anything about MPLAB
Maybe somewhere here http://www.microchip.com/forums/... after all it's our turn to annoy the MC people now.
And we think this forum is bad! I can't log in the MC site even though I ordered samples a little while ago, my email address is not known but it's the same address I had in February last year when I forgot my password and I have an email confirming the change.
It's good to be... hmm I think I said that before.
When AS5 appeared, wasn't EW already hired by Atmel? If so, they certainly had the competence to build avr-gcc inside the company..
Configuring a general purpose IDE to build a project is fairly straightforward.
You simply set up the paths and parameters for the appropriate Tools. Just like you do with a regular Make command.
Or if you want to use an alternative AVR Toolchain e.g. IAR or CV.
Managing project source files, displaying source trees in a GUI is exactly the same for PIC, ARM, AVR, ...
Likewise. Managing the GUI of a Debug session is much the same for PIC, ARM, AVR, ...
But I would guess that the low level comms between the debugger hardware and the PC might vastly different.
Best use of the debugger intelligent commands requires good knowledge of the commercial products.
I note that Rowley Crossworks have different products for AVR, ARM, MSP430, ...
The "look and feel" of the GUI might be the same but debug hardware is different.
David.
So... This then might just have become a "chicken race" between
- Practical EOL of Windows 7 (the last bearable Windows version, it seems to me), and
- MPLABX becoming close to Atmel Studio 7 in performance and functionality.
If Morten is going to be involved, could we crowdfund for hiring someone to feed him energy bars and coffee 24/7? ;-)
The more seriously interesting question is what status this puts Atmel Studio in?
Spotted in another forum...Quote:
The newly released MPLAB X 4.00 now integrates Atmel's ARM and AVR compilers. No mention in the release notes of programming or debugging tough.
So still nothing for the 8051s, then ?
And so 23.5 hours later I get approval at the MC forum, of course they are not likely to have top moderators around the world and around the clock.
But here registration HAS TO BE instantaneous, can't wait for a moderator to approve the 1st post...and the spammer love it. But that's another story of no value anymore I guess.
Generally it seems MPLABX on Linux is buggy at a basic UI level:
- Radio buttons that are selected have their captions made invisible
I need to correct the above. This is a bug in Linux mint (Cinnamon) and its themes, not specifically in MPLABX.
(For anyone else having the same problem on Mint/Cinnamon, see https://bugs.launchpad.net/linux... )
And so 23.5 hours later I get approval at the MC forum, of course they are not likely to have top moderators around the world and around the clock.
But here registration HAS TO BE instantaneous, can't wait for a moderator to approve the 1st post...and the spammer love it. But that's another story of no value anymore I guess.
THats pretty fast...it took a couple of weeks for me and that was with me asking for a favor from a freak who is a member there to ask an admin to either say yes or no.
For the DipTrace community it took a day for the approval and I had to have two posts approved before I was 'cleared' Total about four days.
Jim
Back after a long week at the Microchip Masters conference here in Phoenix.
So, are you guys actually asking a question, or just stirring the brew (... not sure that one translates as well as I hope...)?
