AS7 thinks that AtXmega128A1 has 55 KB of SRAM [SOLVED]

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

I work with AtmelStudio 7 and I can't get what is going on with it.

It allows me overflow sram and my code doesn't work properly. Anyone knows how to fix this?

 

 

and that's how the memory looks like

 

Last Edited: Wed. May 24, 2017 - 08:09 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

There was a somewhat recent change to the XMEGA A pack file :

http://packs.download.atmel.com/#collapse-Atmel-XMEGAA-DFP-pdsc

...

1.0.39  ... Add external SRAM to list of address spaces.

...

 

"Dare to be naïve." - Buckminster Fuller

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

gchapman wrote:

There was a somewhat recent change to the XMEGA A pack file :

http://packs.download.atmel.com/#collapse-Atmel-XMEGAA-DFP-pdsc

...

1.0.39  ... Add external SRAM to list of address spaces.

...

 

 

Thank you, you are right, I forgot about packs, but how turn it off?

Last Edited: Wed. May 24, 2017 - 01:05 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I don't know.

IIRC there was one thread that mentioned XMEGA external RAM and the address spaces issue; Morten, meolsen, may have posted in that thread.

 

"Dare to be naïve." - Buckminster Fuller

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

The problem is solved here is the solution

 

http://www.avrfreaks.net/comment...

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

So, the problem with external SRAM is that we can only describe the maximum value allowed by the chip. This is what changed in a DFP not that long ago, which makes it possible to inspect the content of SRAM etc.

 

(also, the more 'correct' fix is here, a couple of comments down, but I don't think that will help directly on the overflow issue... )

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

Last Edited: Wed. May 24, 2017 - 04:15 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

meolsen wrote:

So, the problem with external SRAM is that we can only describe the maximum value allowed by the chip. This is what changed in a DFP not that long ago, which makes it possible to inspect the content of SRAM etc. You still have to know what size YOUR SRAM has, and correct for overflow (or, if you want to live dangerously, change the size in the xml to whatever fits your setup smiley ).

 

The XML entry was added after a lot of feedback (both from here and from other channels), so I don't think we'll remove it anytime soon...

 

Thank you for the reply, I agree with you but I've been working with xmega32A4so much time and I didn't even think that there is smth different with 128A1, anyway if there were some options or just a note about this feature in AS it would be nice.