AVR/STK500 settings and assembler bug

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

Is there a way to 'attach/save' all the settings for the AVR button in studio with the project that is active?

Right now I have to change many of the settings (hex/eeprom filenames, fuse settings, lockbits, osscal settings etc etc) every time I change project.

I 'assume' there's a way to do that, but I've never found how.

Now, the assembler bug. I have found if I have say a .db string of numbers, like

.db 1, 2, 3, 4, 5 6, 7

the missing comma after the 5 above will cause the assembler to not flag an error and to 'swallow up' the 6. i.e. in memory (eeprom area in this case), the contents will be 1,2,3,4,5,7. I assume thisexpression parsing error exists in the other directives etc.

thanks,
george.

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

I'm rather confused by your message since for me all the settings you mention are saved and kept automatically in AVR studio. Can you be more precisely, please?

To the second point: I would not directly call something like that an assembler bug. It is a programmer error and not an assembler error. You may ask how fool-proof an assembler should be before you can work neatly with it though. It would be nice if an assembler would recognize any typo. But that comes at a prize and I'm not sure everybody here likes to pay that prize.

Greets and succes

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

rboek2 wrote:
I'm rather confused by your message since for me all the settings you mention are saved and kept automatically in AVR studio. Can you be more precisely, please?

To the second point: I would not directly call something like that an assembler bug. It is a programmer error and not an assembler error. You may ask how fool-proof an assembler should be before you can work neatly with it though. It would be nice if an assembler would recognize any typo. But that comes at a prize and I'm not sure everybody here likes to pay that prize.

Greets and succes

Well, I DO call it an assembler bug since it did not flag the syntax error. I have written assemblers in the past (sold commercially) and spent considerable time on the parser to ensure it would flag such simple syntax errors. In my opinion the assembler should make coding as foolproof as possible - that IS the whole point of having a tool, it is meant to improve productivity by flagging syntax/format errors.

Studio saves the fuse etc settings, BUT not per project. i.e. if I open a project for an attiny15 and set the filenames for the hex files, eeprom files, fuses, etc and then save and exit that project and then open a DIFFERENT project for say an attiny13, all the settings are still there from the last used project, not the one that was just opened. So, I have to go into the AVR dialog (I use an stk500) and manually set all the options again. What I'm asking is there a way to save all the settings with the project, i.e. per project. Right now it appears that all the settings in the AVR dialog are stored globally, not per project.

george.

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

georges80 wrote:

Now, the assembler bug. I have found if I have say a .db string of numbers, like

.db 1, 2, 3, 4, 5 6, 7

the missing comma after the 5 above will cause the assembler to not flag an error and to 'swallow up' the 6.

Now it would be helpful if you told us what version of Studio and the assembler you are using. This bug was actually discovered and fixed in the assembler version 1.75.5 March last year, which means it has been distributed since Studio 4.09.

Apart from that, I do agree with you that this is (was) a very serious bug.

Please don't report bugs in private forum messages.
--
Roland Kruse
Atmel AVR Tools

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

Quote:
Studio saves the fuse etc settings,

Does it?
I was under the impression that it reads the fuse settings from the target AVR.
Like the OP, I've never found a way to save the fuse or lock-bit settings on a per-project basis.
In fact I've never found a way to save them at all.
That's why I've started using AVRDude in conjunction with the AVRISP for small batch programming. I got fed up with having to check all the fuse and lock-bit setting every time.

Four legs good, two legs bad, three legs stable.

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

Ok, the latest 4.10 studio assembler correctly detects the missing comma. I was running studio 4.08 which I 'assumed' was pretty recent. SIlly me.

But, the question on how to save fuses on a per project basis is still unanswered, and I suppose based on the lack of responses or pointers to other tools that there is no way with Studio to do this.

What I meant when Studio saves the fuses, is that if I set them (and the lockbits), as long as I then stay on the programming tab I can program multiple devices (often 100's at a time in my case), without having to set the things each & every time. The problem is that when I exit the project or Studio, they're gone next time. It would be nice to have a way of 'sticking' them and having to manual 'read' them back from the device if one wanted to see the current ones.

Oh well...