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 [2]  Send TopicPrint
Hot Topic (More than 8 Replies) VM needs to do a "clean" when changing MCU types (Read 24269 times)
stevech
Member
***
Offline


Posts: 147
Location: So. Calif. US
Joined: Jun 16th, 2013
Re: VM needs to do a "clean" when changing MCU types
Reply #20 - May 13th, 2014 at 8:53pm
Print Post  
It's working very well.
  
Back to top
 
IP Logged
 
stevech
Member
***
Offline


Posts: 147
Location: So. Calif. US
Joined: Jun 16th, 2013
Re: VM needs to do a "clean" when changing MCU types
Reply #21 - May 23rd, 2014 at 4:50am
Print Post  
sorry to have to ask again...
The prior dialog got me to where I can build for either AVR or Teensy3.1 with the same project file and source. I just choose the desired target MCU and serial port.  I was able to remove the -Defines from the project settings and put them in the Teensy boards.txt (like the CPU speed). This done, I can compile for the AVR or Teensy 3.1.

On to the problem. When I choose Teensy 3.0 as the target, I get the numerous errors as happened originally when the -D's were not in the project file. The boards.txt file for both Teensy 3.0 and 3.1 have the same added build options 5,6,7 to eliminate need for them in the project properties. I just can't get a build for 3.0 to work as does 3.1 or AVR.

If, when choosing Teensy 3.0 I put the -D's back in the project -D's as was originally done, then it compiles. I exit and restart VS/CM of course.

Stumped.
I feel like a blind man at a NASCAR race - just don't understand this complex house of cards IDE. But then, when I did a big project with Eclipse it was much worse!
  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12187
Location: United Kingdom
Joined: Apr 10th, 2010
Re: VM needs to do a "clean" when changing MCU types
Reply #22 - May 23rd, 2014 at 11:57am
Print Post  
Well that reminds me that VM needs to pull the compiler options from the teensy config and force them into the intellisense system. This would remove the intellisense errors. There is a workaround for this that I will try to post over the weekend.

However I am concerned I am confused about one point you have made. 

I don't understand this statement?

Quote:
I just can't get a build for 3.0 to work as does 3.1 or AVR



  
Back to top
IP Logged
 
stevech
Member
***
Offline


Posts: 147
Location: So. Calif. US
Joined: Jun 16th, 2013
Re: VM needs to do a "clean" when changing MCU types
Reply #23 - May 23rd, 2014 at 7:44pm
Print Post  
I apologize.. my "bad". I thought I had deleted that post, above. the problem was simply that the boards.txt file was edited wrong by me. I had copy/paste from Teensy 3.1 but it should have been done with removal of the ".1" for Teensy 3.0.

It's working perfectly now, toggling between T3.0, T3.1, AVR with just a choice of target. No changes to project properties, no need for new additions to the Debug/Release folder. I love it!
  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12187
Location: United Kingdom
Joined: Apr 10th, 2010
Re: VM needs to do a "clean" when changing MCU types
Reply #24 - May 24th, 2014 at 8:38pm
Print Post  
Great, thanks for the update
  
Back to top
IP Logged
 
Page Index Toggle Pages: 1 [2] 
Send TopicPrint