AVR Studio 4.06, build 223 is now available as a RELEASE CANDIDATE.
You can find it here.
*** Eivind, webmaster ***
this time they have chosen to provide a "Release CANDIDATE"
I am sorry to be so dense but what does the above phrase mean referring to the Studio 4 4.06 just released.
admin's test signature
Well it normally means that they are considering releasing it as a "full version", although in some contex it doesn't make sense. Normally, the release of software goes:
1) Beta Version
2) Release Canidate
3) Full version
So I guess that means earlier AVR Studio 4's were beta's...
PS: Here is an example of a software cycle
ProductX Beta1 - normally not many features, full of bugs
ProductX Beta2 - more features added, bugs fixed
ProductX Beta3 - more features added, bugs fixed
ProductX Release Candidate - most features that will be in the final version are in this one
ProductX Version 1.0 - full release, bugs identified in release canidate fixed
Of course i just made that up, but you get the idea ;)
In the AVRStudio case, it was a little different :
AVRStudio 4.00 Release - no bugs, all shining fantastic new program.
AVRStudio 4.01 Release - fixed a few bug after all, now all works perfectly.
AVRStudio 4.02 Release - fixed a few bug after all, now all works perfectly.
AVRStudio 4.03 Release - fixed a few bug after all, now all works perfectly.
AVRStudio 4.04 Release - fixed a few bug after all, now all works perfectly.
AVRStudio 4.05 Release - fixed a few bug after all, now all works perfectly.
AVRStudio 4.06 Release - fixed a few bug after all, now all works perfectly.
And soon -
AVRStudio 4.87 Release - finally added 3rd-party C compiler support and documented the "open" interface.
The quick black AVR jumped over the lazy PIC.
What boots up, must come down.
Bug or feature?
With this new version I can not found the Extended SRAM in the Memory window. Under the
AVR Simulator it was there, but not with the ICE 200. I use here a S8515.
I think i remeber you are a GNU user.
If you like to have support for c-structure, C-arrays, c-pointers with struct
and so on you can buy the ICCAVR PROF version
it's working ok now, have not test everything but i have test some struct:s.
I have used the ICCAVR for a 6 months now and it's working ok.
But i know what you mean this debuger @!#$ bugs problem,.
Problem with ICE50, JTAG, STK500, ICE200 and so on. and all the versions
with avr-studio from atmel.
And i'm a litle bit tired about this with total IDE problem when you are using
I Have following license:
FLASH Debugger for imagecraft C
The ISUE when different companies should working together are that
i takes a lot of time before it's working, and if you made some changes in one software it can be new bugs (And i take more time again).
I'm going leave the C-Compiler:s for a while now, and use AVRCo profi version.
I don't say that Pascal are better than C. But the compiler with Multi-tasking, Multi Process, allready built in functions for lot of things(I2C, TCP/IPC, PWM,STEPPER....), Simulator, High level source code debuger for JTAG, ICE200 and so on. form same company are nice.
Should that have read,
In the AVRStudio case, it's a little different :
AVRStudio 4.00 Release - sod the testing it's late, aha give am a beta.
AVRStudio 4.01 Release - aha we really pissed em off, lets go to the pub.
AVRStudio 4.02 Release - hehehehe we've made it even worse, lets go to the pub.
AVRStudio 4.03 Release - fixed bugs in skins. lets have a party, in the pub.
Finally someone read the bug reports.
AVRStudio 4.04 Release - Oh @!#$,look at all these. I'm off down the pub.
>lets go to the pub.
>lets go to the pub.
>lets have a party, in the pub
>I'm off down the pub.
Hmm, are you a part of the development team ?
Merry Christmas from all the development team, hick!
Lets hope next year is a good one and those pesky microsoft guys write a good development tool that stops putting bugs in our software.
It ain't our fault the compiler dosen't understand what where telling it.....
This message was sent to ATMEL product support:
Here is a bug report for ATMEL AVR Studio 4.06 build 223 which I downloaded recently from AVRFreaks.com.
When simulating the AT90S8535 with this software I inadvertantly tried to add register USR to the watch window I had set up. The entire line in the watch window blanked out. I guess this is because USR was not being used in the program and was not in the MAP file.
Anyway, when I tried to delete this line in the watch window using the right click menu the program became unstable. The monitor flashed and the computer froze up.
Restarting the computer did not work. The welcome applet would appear but AVR Studio would not run. I tried the repair option in re-install and it still didn't work. Finally, I un-installed Studio 4 and the did a full re-install.
I was finally able to get it going again.
I think something is 'bumpty-clunk' in the release candidate AVR Studio 4.06, but it is nice to be able to use the watch window now.
Note that I was using the simulator mode and no hardware was connected.
I am a beginner and this software is very challenging to use.
In my opinion the Studio 4 underdevelopment team have had a year to iron out this software but major bugs still remain that render it useless. Just what the hell are they doing allowing beginners to download Ver 4. Do they want the platform to penetrate new markets or are they happy just supplying the large manufacturers?
A few months ago Atmel sent me samples of the new Mega series after a long discussion with a sales rep where I vented my frustration after wasting a week on Studio 4 (see my previous posts). I had vowed not to use Atmel again but the performance of the new mega's should not be taken lightly. The mega8 is just about the right price point (1000 off) and is a great processor for smaller applications and the platform is scalable right up to the Mega128 with all its bells and whistles. It does make me wonder what the silicon guys make of the disgraceful Studio package? What is really more difficult designing the chips themselves or writing an assembler / simulator.
Come on Atmel, stop pissing your users off. Your supply chains are much much better, you have a great product (mega's) and folks really want to use them.
Stop wasting people’s time with studio 4, your competition must be laughing at you by now. Withdraw it and start again.
BTW Dag are you reading this?
when installing 4.06 and upgrading the firmware (STK500 goes to version 0x0E), you can not return to previous versions (not even 4.05, which uses 0x0A).
I found it when using the STK500 when somone had already upgraded it.
I've noticed that the "set extended device parameters" has an extra argument.
Release Candidate !
=> release to the masses for them to find the bugs while we go down the pub
come back next year or two.
i am sick of wasting time on Junk
sticking with companys that know how to program AVR'S
they knock the socks off atmels attempt after only a few months
and because they have to produce good software to stay alive
why don't atmel support one of the software vendors more and request them to produce it , but their again i suppose atmel staff code in their lunch breaks
and then go to the pub !
Happy new year all !
© 2019 Microchip Technology Inc.