An irritation in AS5

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

I just did something I thought was obvious in AS5 but it wouldn't let me. I started a new avr-gcc executable project so it created a .c file for me. I then wanted to add a .S file to the project so I use File-New File.. but under "avr-gcc" it only offers to create .c or .h files. What the hell happened to .S ??

And no "AVR assembler" is not an option here (though it could well confuse a beginner) because that's talking about .asm files clearly for Atmel Assembler2, not avr-as.

Attachment(s): 

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

Having problems with this myself, Cliff. Did you find a solution? I found that I can create the file and then "add existing file" to the project, but I'm getting very confused as to what the solution/project tree should look like, as AS5 seems to be fairly abitrary about where it adds these files - I have ended up with shortcut icons being displayed in the project/solution explorer.

John

Quebracho seems to be the hardest wood.

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

John,

Sadly no and see my other recent gripe about this problem where sometimes it cannot find the source to show symbolic debugging which also seems to relate to where files are actually located. It seems almost impossible to determine where it actually wants to "see" stuff located. I'm hoping either (a) Atmel fix it so it doesn't care where files are located or (b) Atmel explain exactly where the program thinks files should be located.

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

OK, let me know if you find anything out, and I'll do likewise.
I'm getting too old for for all this!
I spent hours trying to work out why my XMega256 bootloader wouldn't work, only to eventually realise that the boot section is not part of of the 256K, but an extra section of memory that STARTS at 256K!
Which of course makes a lot of sense, but departs from the Mega32/Mega64/Mega128 system, and thus totally tripped me up!

John

Quebracho seems to be the hardest wood.

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

Quote:
I'm hoping either (a) Atmel fix it so it doesn't care where files are located or (b) Atmel explain exactly where the program thinks files should be located.

To do that they'd first have to recognize the bug/problem/deficiency/akwardness. Do you know of any well-defined place where one can i) report such items and ii) inspect the already reported ones so that one does not flood Atmel with known issues? I don't.

While I understand and respect what seems to be Atmels policy re not talking release dates or features/fixes in an upcoming release, having a list of known bugs (with possible workarounds etc) is a different issue.

It seems to me that the ohe only communication happening is that someone "looking like" an AS5 developer drops something here from time to time, as for example the AS5 C++ plugin. (Nothing wrong with it, but it's interesting that some more or less unknown user here announces it. There seems to be no co-ordinated announcement point re AS5 and related - one of the developers that feel like talking talks. Risk of double-communication, redundance, lack of announcement etc. All very strange..

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

Quote:

I don't.

I've seen mention of a publicly accessible Bugzilla on here but I'm not sure if that's just for ASF or whether it covers AS5.

EDIT: sorry, no, it's only ASF:

http://asf.atmel.com/bugzilla/bu...

(though that does mention Studio 5 and the last one is definitely an IDE problem)

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

I have been reporting AS5 bugs by conitinuing to email the avrbeta@atmel.com (kind of appropriate really ;). But the lack of visibility of reported bugs is a real pain as you end up wasting so much time trying to figure out if you're doing something dumb or its a bug. Being able to see the list of bugs would possibly save a bit/lot of time.

The asf bugzilla is not much better though. In general you only see bugs you report (and strangely some others that I have no idea why I see them, but not all bugs). Another gripe with that is that the developers don't acknowledge them in what would be considered a reasonable timeframe.

It would be nice if Atmel could get there shit together and work with the community.