Welcome to the AVR studio 4 forum! This forum will be monitored by the devteam, and so should provide a useful source of support for this release.
*** Eivind, webmaster ***
Hi Eivind, and all,
This is a great idea. I hope the close contact with the devteam will push forward updates and fixes faster that it was done with 3.x and that it can help us all get the best of AVRStudio4.
Both as a hobbyist and professional developer, I mostly use the old chips. They're proven, and they're available. Also, I use GCC in many other project for other processors, and would like to stay with it.
I'm sure the same is true for MANY other people here.
So, I'd really like to get answers to these questions :
1. WHEN can we expect support for AVR-GCC. ?
2. WHEN can we expect support for "old" classics as 8515, 2313 e.t.c. ?
3. WHEN do we get the specifications for making plugin's for Studio ?
Furthermore, I'd like to know WHY AVRStudio4 was no beta tested on the AVR community. Testing it on a few large companies with similar routines and $3000 ICE boxes, does NOT give a good test result.
After just two days of AVRStudio4, we've found several bugs and omissions, not to mention lacking features (at least seen from our perspective).
Keep up the good work. The new GUI looks promising, but the looks is not all, you know.
The quick black AVR jumped over the lazy PIC.
What boots up, must come down.
To your questions, I will make some general remarks. As an AVR development department we have many responsibilities, both for open communities like this, but also for big selected customers using LARGE amounts of parts. The latter category will usually receive fixed timeframes for when things can be expected to be released. A general policy we will not make such statements in a forum like this, things are available when they are released. So to your questions:
1: Yes, we are working on GCC compiler support (along with support for other compilers)
2: Quite soon.
3: I’ll have to come back on this one.
The reason the AVR Studio was not beta tested on the AVR community is simple: Our competitors as well would know what we were up to months ago. Generally we do not pre-release, we release.
As I stated, this release is targeted against new part and ICE50 and JTAG users. For the ICE50 users the system is rather complete. All other users has a working environment in the AVR Studio 3.X. We released to the community at the earliest possible date, and we are working hard to get all the parts up and running.
admin's test signature
I appreciate the answers.
Regarding the openness of AVRStudio4. The possibility for 3'rd party add-ons seems to be one of the MAIN points used in marketing of this release.
Still, you can't give me an answer on when it will be available.
Your answer make me suspect that it may not even BE available to other that paying 3'rd party developers.
I've been fighting the closed AVRStudio 3.53 to add features like automatical makefile generation e.t.c.
If the documentation for the much advertised "open" API of AVRStudio4 was available, I could do the same for AVRStudio4.
I could make the AVR-GCC integration.
I could add many other nice features.
All without you moving a finger. Or spending a $.
Why don't you use the power of the AVR community ?
PS. Is "Quite Soon" more or less that a year ?
Quite soon is less than a year. Much less.
For some of the other issues we simply have not decided what to do, but we appreciate the views of this forum and will take them into consideration. For the further progress; AVR Studio 4 has been on the web for less than a week. You all have to show a little bit of patience. This is a free software, we have devoted a substantial amount of resources to take it this far and that is a policy we will maintain. I think the history of AVR shows Atmels dedication to support the entire user community with tools, not only those on a high budget.
The AVR Studio 4 API is currently not documented to a point where it can be released.
Stay tuned :-)
Personally I think that AVR Studio 4 look like a GREAT platform! Although there isn't a huge amount there yet, it looks like it will be a force to be reckoned with!
Are you planning on supporting the ICE200? Its a nice little emulator!
Another feature request I have is Linux support. Recently companies are starting to use Linux, and a port would be useful! You could probably get outside people to do it for free too. Some companies have done that where they get Linux programmers to sign an NDA, and they port it!
Looks good overall though! Be nice when more things come out for it (old chip support, plugins, etc).
PS: Hey has anyone else noticed that the new Studio is skinnable?
Thanks for your feedback on Studio 4. May I ask what your role is at Atmel?
I noticed the skin dll's, but don't know how to us the skins. If you know, please let us know.
Wow, skinnable !
Cool, but I'd rather have that the resources had been used for the 8515 or avr-gcc support.
But well, I'm sure the big multimillion $ companies think skins is an important and necessary feature :-O
Dag, don't get me wrong. I appreciate the free tools very much. I have had much benefit of AVRStudio 3.5x.
I guess I just expected a more complete product after all the hype.
I will just have to be patient (not one of my strong sides ;-)
I would hazard a guess that skinning was quite probably a "free" feature of the UI toolkit used to write the software, rather than something upon which great effort was lavished.
Sean: I am the manager of the Atmel AVR Tools department. We develop and manufacture stuff like the AVR Studio 3 and 4, the ICE200, the STK500, the ICE50 .. JTAGICE ... AVRISP ...
So if anyone is to blame, it's me!
I am going away for a few days, I'll be back on this forum on Monday next week.
Jesper: Skins are important! Just wait until you figure out how you can customize the icons in the I/O view ... (yes, you can ...)
Colin: ICE200 will be supported. It the is next one out, including the parts.
Skins are, as sellis correctly suspected, a feature with the excellent library we have used in S4. This is BCGControlBar from BCGSoft. See www.bcgsoft.com for information on that toolkit witch we highly recommend.
GUI-developer Avr Studio 4
skins are accessed from tools->customize->Options->Visualizations..
It is very rare to get this level of access to software developers. Thanks for taking the time to monitor this forum and give responses to our questions.
Yeah, its nice to see the "head" guys over here! You've answered / replied to a LOT of our questions, thanks for taking the time!!!
Hi AVRFreaks and Developers !
What a great Day !
Me and my small team we are currently developing a own complete multitasking-OS with network support for the 8515/Mega128. As one of those guys working 8h a day with AVR Studio, it's GREEEAAAT to see that the new Version 4 is out !!! I couldn't test the whole enviroment in depth, because I cannot use the ICE200 with it. But some of the new features i could discover are what I've been waiting for so long. I can't wait to start working with Version 4 :-)
How long do I have to wait for the ICE200/8515 implementation ? Weeks?
Months ? Quarters ? I know this isn't a easy question, but I just wanna know the approx. duration if it is possible yet.
Hi developers !
All my questions were asked by my collegues, especially ICE200, gcc, "normal" AVR
I think we all will like the new product - after all the problems with version 3.x -
and because we are eagerly awaiting a nice software production environment, we - after having seen the pictures of the dinner - would like to eat, naturally today and all of it.
Anyway, thanks for your efforts. From own experience I know that documentation is time consuming - only once in my life I had a project with "documentation first" and I am not one of the young ones.
As far as I have understood, the parts are described in xml-notation - looks like I could figure out how to make one for e.g. 8535. But I would not appreciate to go into that, if the part description will be available within the next couple of weeks (4-6). So I would be thankful for some kind of a time schedule for the "add-ons".
And naturally the answer to the question: is it sufficient to produce the xml-based description in order to integrate the part.
And: gratulation on the idea for a special forum
the parts are described in xml-notation
I just had a look at these, and the whole device's capabilities are described in there - all the interrupt vectors, memory space, peripherals, IO register descriptions, everything.
Congratulations to the Studio 4 team for making this choice. It can't have been easy to code, but it makes the whole thing much more "hackable", both for early support of new devices, and for legacy support of old devices.
Oh, and the XML tag names make the whole thing more-or-less self-documenting. Excellent job!
Hi to you all,
yes, we have described the devices capabilities in XML notation. We thought that was a good idea. The AVR Studio 4 configures both resource views, simulator and emulators from the scripts. XML scripts for all the “old” parts are completed and are currently under test. As Sean implies, it takes a fair amount of work to complete them all, so I want recommend you to start writing your own. Some goodies should be released in a not to distant future (we are talking weeks)
© 2020 Microchip Technology Inc.