Before logging an issue, please update to the latest release of Visual Micro from the Downloads Page.

When Logging a Support Issue in the Forum, please ensure you have also:-

  • Enabled vMicro > Compiler > Show Build Properties
  • Re-Compile your program with these settings enabled
 
Save the new Output to a Text File and....
  • Click the Reply button and attach as .txt file OR
  • Click here to Email us with the file attached, and a link to your post
Support requests without the output above may be impossible to answer, so please help us to help you
 
Page Index Toggle Pages: 1 Send TopicPrint
Normal Topic Erratic compile errors with Atmel 7 and beta plugin using library that previously worked. (Read 4627 times)
jimf
Junior Member
**
Offline


Posts: 18
Joined: May 30th, 2015
Erratic compile errors with Atmel 7 and beta plugin using library that previously worked.
Jan 4th, 2016 at 2:46pm
Print Post  
I've been using Atmel 7 + beta plugin and started to have problems with an open source library that previously worked with 6.2.  Moreover, the compile results are seemingly erratic (to my relatively untrained eye Smiley)

The output below is based on example code that comes with the Dallas Temperature library.  I've gotten the same results with the MAX31850_Dallas Temp library. Seeing this with other code that previously compiled/ran, thought using examples provided by library would take my coding errors out of the equation. 

I greatly appreciate any help.  Please lemmi know what other information is needed to get this resolved.  Many thanks.....jim

Dallas Temperature library
Tester example program
Compiler warnings on, 
Off: auto debug, tutorial mode, verbose messaging
Build completes with one warning:
Compiling 'Tester' for 'Arduino/Genuino Mega w/ ATmega2560 (Mega 2560)'
DallasTemperature.cpp:In member function 'float DallasTemperature::calculateTemperature(uint8_t*, uint8_t*)
DallasTemperature.cpp:456:1: warning: control reaches end of non-void function [-Wreturn-type]
Binary sketch size: 8,466 bytes (used 3% of a 253,952 byte maximum) (0.66 secs)
Minimum Memory Usage: 585 bytes (7% of a 8192 byte maximum)

Turned on auto debug and build has errors:
Compiling debug version of 'Tester' for 'Arduino/Genuino Mega w/ ATmega2560 (Mega 2560)'
DallasTemperature.cpp:In member function 'float DallasTemperature::calculateTemperature(uint8_t*, uint8_t*)
DallasTemperature.cpp:456:1: warning: control reaches end of non-void function [-Wreturn-type]
Tester.pde:5:23: error: variable or field 'printTemperature' declared void
:void printTemperature(DeviceAddress deviceAddress)
Tester.pde:5:23: error: 'DeviceAddress' was not declared in this scope
Tester.pde:7:19: error: variable or field 'printAddress' declared void
:void printAddress(DeviceAddress deviceAddress)
Tester.pde:7:19: error: 'DeviceAddress' was not declared in this scope
Tester.pde:In function 'void setup()
Tester.pde:51:31: error: 'printAddress' was not declared in this scope
:printAddress(tempDeviceAddress)
Error compiling project sources
Note: solution cleaned between tests above.  Also, isn’t always consistent. E.g. sometimes turning on tutorial mode produces the same issue.
  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12163
Location: United Kingdom
Joined: Apr 10th, 2010
Re: Erratic compile errors with Atmel 7 and beta plugin using library that previously worked.
Reply #1 - Jan 4th, 2016 at 3:33pm
Print Post  
Hi,

First off there have been many changes within arduino during the past months. The VS version of Visual Micro is more up to date.

First question is which version of Arduino are you using? The atmel version of Visual Micro currently only supports up to arduino 1.6.5 ide.

Also please switch on the Visual Micro>Verbose build and post or email the output to info[at]visualmicro.com

Errors in debug mode are usually to do with breakpoint placement or the values supplied to the breakpoint properties. 
The tutorial mode simply auto creates a breakpoint for you as an example.

Thanks

ps: Microsoft released Visual Studio for free last year so you an move away from atmel studio
« Last Edit: Jan 4th, 2016 at 4:48pm by Tim@Visual Micro »  
Back to top
IP Logged
 
jimf
Junior Member
**
Offline


Posts: 18
Joined: May 30th, 2015
Re: Erratic compile errors with Atmel 7 and beta plugin using library that previously worked.
Reply #2 - Jan 6th, 2016 at 6:35am
Print Post  
thanks for the reply. 
1)  I checked the IDE version and it was newer than 1.6.5, so I installed that.  The 'manage boards' tab of the VM explorer showed 1.6.5 installed
2) issue persisted, build with verbose messages attached.  Still erratic....sometimes with errors, sometimes without.  I clean build between builds.
3) I'm not sure what you mean by the VS version of Visual Micro, it looks like the beta is the only version to use with Atmel.  Please point me to different version if that is what you mean
4) sounds like you think I should transition to the free Visual Studio + Visual Micro.  Makes sense if Visual Studio is now free....after all, how long will Atmel want to make their own now that Visual Studio is free.  Please comment if you can or email directly Smiley

thx again....jim
  

Please Register or Login to the Forum to see File Attachments
Back to top
 
IP Logged
 
jimf
Junior Member
**
Offline


Posts: 18
Joined: May 30th, 2015
Re: Erratic compile errors with Atmel 7 and beta plugin using library that previously worked.
Reply #3 - Jan 11th, 2016 at 1:45am
Print Post  
I decided to switch to Visual Studio and installed Visual Micro plug in.  The example code that was causing errors builds fine in VS.  There will be a bit of a learning curve.  I've been using the Atmel IDE with Visual Micro for debugging for about a year.  My thinking is that now that VS is 'free', 3rd party software vendors like Visualmicro will provide better support for VS.
  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12163
Location: United Kingdom
Joined: Apr 10th, 2010
Re: Erratic compile errors with Atmel 7 and beta plugin using library that previously worked.
Reply #4 - Jan 11th, 2016 at 2:21am
Print Post  
Great to hear that thanks
  
Back to top
IP Logged
 
Page Index Toggle Pages: 1
Send TopicPrint