DB Directive in Studio 3.51

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

Hi Guys,
Well Atmel have finally addressed the problem with odd bytes in the db directive causing labels to be wrong. However, according to the release notes this should only happen in the cseg (flash) as they are 16 bits per address. Adding the extra extra zero byte and issuing a warning should work like a charm.
However...........Guess what you get warnings in an ESEG when the eeprom is 8 bits per address and I have never heard of a wrong eeprom address label ever. I hope Atmel will fix this ASAP as you end up with a ton a warnings that are totally unnecessary. Thank God the assembler doesn't try to add the extra bytes to go along with the warnings in the ESEG or a lot a programs would quickly run out of eeprom.
Shaun

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

Hi

Of course, a warning: A .db segment with an odd number of bytes is detected. A zero byte is added. in an ESEG when the eeprom is 8 bits per address is a NEW bug from Atmel.

Yuri G. Salov

admin's test signature