Do we have a grip on current status of AS5?

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

For some time I've had massive problems getting AS4 working on my primary PC. (Can not run the simulator - as soon as I stop debugging AS4 crashes violently).

So I decided to take AS5 for another spin, without installing the AVR Toolchain but instead using my WinAVR-20100110 installation.

After adjusting two paths (to the tool chain and to Make) things seems to work like a charm.

As I recall we've seen several reports here on flaws in AS5, but I wonder how many of these are "substantial, proven and original", and how many are "repeats" (or even just hearsay).

I have two questions related to this:

- Do we have, or can we get, something like a comprehensive list of known bugs etc for AVR Toolchain?

- Do we have, or can we get, something like a comprehensive list of known bugs etc for AVR Studio 5 (the IDE, excluding the tool chain, but including programming and debugging functionality, ICE drivers etc)?

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

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

I too would like to see a round-up of known, acknowledged issues. I've been using it heavily, and so far have not noticed any of harsh problems reported here. It does seem to me more issues have been reported when using 32bit AVRs- by far. But I would say my work recently with XMegas (and only XMegas at the moment with AS5) has been rock solid.

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

JohanEkdahl wrote:
For some time I've had massive problems getting AS4 working on my primary PC. (Can not run the simulator - as soon as I stop debugging AS4 crashes violently).

Can you share some more info on this? like device(s) affected, AVR Studio version (4.18.SP3 or 4.19beta), which simulator (1 or 2)? Have you observed this on more than one PC? Windows version(s)?

(Unfortunately I cannot answer your questions about AVR Studio 5)

- roland

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

The ATmega48/88/168/328 family at least.

Right now I have AS4 4.18(715), but might well have been at a higher version earlier. Because of system corruptions I have re-installed both Windows and e.g. AS4 several times during the last six months. I have no firm records on what versions has crashed for me.

Simulator 2.

Computer is a HP8710p laptop running Windows XP, that I try to keep up to date re Windows Update.

Personally, my first guess would be some kind of driver incompatibility. Or MSSE messing up. Or Some MFC version incompatibility.

What's the deal, Roland. I thought AS4 was abandoned and dead in the water?

ASIDE: While I am actually talking to an Atmel employee. Could you please drop the word up the food chain that requiring registering every time doing a download is pathetic and makes Atmel look ridiculous? Please?

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

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

JohanEkdahl wrote:
The ATmega48/88/168/328 family at least.

Right now I have AS4 4.18(715), but might well have been at a higher version earlier. Because of system corruptions I have re-installed both Windows and e.g. AS4 several times during the last six months. I have no firm records on what versions has crashed for me.

Simulator 2.

Computer is a HP8710p laptop running Windows XP, that I try to keep up to date re Windows Update.

Personally, my first guess would be some kind of driver incompatibility. Or MSSE messing up. Or Some MFC version incompatibility.


THank you, Johan. The reason I ask is that AS4 and AS5 basically share the same simulator models, and we have had an issue with some of our simulator models giving the symptoms you describe. This issue is in a 3rd party library and we had to work around it in a manner that I am not convinced is 100% robust (this was several years ago). And yes, the models for ATmega48/88/168/328 were affected by this issue. If you still have AS4 installed on the affected computer, I would be very grateful if you could try to start a simulator2 debug session with a few other devices: ATxmega32A4, ATtiny10, ATmega32HVB, and ATmega1284, and report which ones of these causes the crash
(You don't have to create new projects or load a real application, just use Debug->Select Platform and Device).
Quote:

What's the deal, Roland. I thought AS4 was abandoned and dead in the water?

Not quite, there will be an AS4.19, with support for new devices (there was a 4.19beta some months ago). But that will be the last one.

Also, because AS4 simulatot2 and AS5 use the same simulator model technology, what is bad for AS4 may be bad for AS5 as well.

Quote:
ASIDE: While I am actually talking to an Atmel employee. Could you please drop the word up the food chain that requiring registering every time doing a download is pathetic and makes Atmel look ridiculous? Please?

Believe me, I totally agree, and we have tried. This will be fixed, but I cannot say when. We (as developers of AVR Studio) don't have much influence on the design of the atmel.com website.

- roland