Studio 7.0.1417 can't find device in io.h

Log in or register to post comments
Go To Last Post
4 posts / 0 new
Author
Message
steve17
steve17's picture
Level: Raving Lunatic
Joined: Tue. Sep 7, 2004
Posts: 6975 View posts
Location: New York State
#1
Posted by steve17: Sat. Aug 12, 2017 - 11:27 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I just installed the latest Studio (1417).  Can't compile.  The preprocessor seems to find the io.h file but the io.h file can't find the device. 

 

The device I specify in the Build > Device is there but it appears the device doesn't get passed to the preprocessor.

 

I noticed something in the Build > toolchain that doesn't exist in my Studio 6.2.  The field is blank.  Could this be the problem?

 

Here is the device being set:

 

 

Here is the empty field:

 

 

 

Tags:

Tools, Atmel Studio (AVR-related)
Top
Bronze MarkJohanEkdahl
JohanEkdahl's picture
Level: 10k+ Postman
Joined: Wed. Mar 27, 2002
Posts: 26945 View posts
Location: Lund, Sweden
Posted by JohanEkdahl: Sun. Aug 13, 2017 - 11:31 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

steve17 wrote:
I just installed the latest Studio (1417).  Can't compile.  The preprocessor seems to find the io.h file but the io.h file can't find the device. 

Complete build output?

steve17 wrote:
Device is [set in the project properties] but it appears the device doesn't get passed to the preprocessor.

The build system should pass a -mmcu option to the compiler with the actual device name as its value. (Check this looking at the complete build output.) It should result in a preprocessor symbol being defined. You can test it in your main.c, with something like this at the very beginning:

#ifndef defined (__AVR_ATxmega256A3BU__)
#warning "MCU model not defined!"
#endif

 

Have you tried simply "wiggling" the device model in the project settings? (Change to something else, then change back.)

 

Is it the  same when you set up a new empty project with the same device?

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]

Top
steve17
steve17's picture
Level: Raving Lunatic
Joined: Tue. Sep 7, 2004
Posts: 6975 View posts
Location: New York State
Posted by steve17: Sun. Aug 13, 2017 - 12:09 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thanks Johan.  Yes, the problem is the lack of the -mmcu option.  Why does this keep happening to me?   It happened a year ago with an earlier version of Studio 7.0.  Now I remember I have to put -mmcu in 3 places.  Compiler, linker, and assembler.

 

Could it be because I  use the offline installer?  The on-line installer is always recommended.  Why is that?

 

I prefer offline installs because I often install stuff on several OS installations on a couple of computers.  I'm testing this thing now on a Win10 installation I use for testing on my secondary computer.

 

I'm still running Studio 6.2 on my main computer because 7.0 had a bug with links and folders.  Maybe it's fixed in this version.  Hope springs eternal.

 

P.S.  Changing the device didn't help.  I feed Studio with a 6.2 project which it upgrades.  I haven't tried a new project.  Studio should come with a warning:  THIS SOFTWARE CAN BE HAZARDOUS TO YOUR HEALTH.

Last Edited: Sun. Aug 13, 2017 - 12:12 PM
Top
steve17
steve17's picture
Level: Raving Lunatic
Joined: Tue. Sep 7, 2004
Posts: 6975 View posts
Location: New York State
Posted by steve17: Sun. Aug 13, 2017 - 12:19 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Okay, it looks like the bug in earlier versions of 7.0 has been fixed.  It was worth the torment.  I was doubtful because I saw no mention of this fix in the version release notes.

Top