As mentioned here recently --
Using Arduino 1.06 (not 1.6), Teensyduino libraries at beta7, I can compile and run using the (bleah) Arduino IDE.

But in Atmel Studio 6.2 w/Visual Micro, there's an error when compiling - complaint by asm that a command line argument is invalid.

The LC's core is a different but same family MCU; slower clock, smaller memory, not as many on-chip peripherals. GCC with AS 6.2 does compile for it correctly, using Arduino 1.06.  Arduino 1.6 is future TBD.

What's needed and can I help, get VM to do as AS 6.2 with VM can do, for the Teensy LC? Or better, VS 2013/Community.

you used Arduino 1.6?
I am trying to use 1.06 because Teensy and Arduino 1.6 is still in early beta.

OK, thanks.
Prior to Arduino 1.6, I put 2 or 3 board-specific settings in the boards.txt file, and not in the project properties - because this avoiding have to setup custom properties for each project.

I did add those same properties to the boards.txt file for Teensy 3.1 and LC but got the error for an invalid asm command line.

Could you please tell us what property settings are required for T3.1? And if possible, the beta Teensy LC which uses a different MCU and clock speed.

Perhaps easiest is to post or send a simple blinky or some such working VS/VM project for these two MCUs with the properties set, rather than using the boards.txt approach.

F_CPU is 24MHz? It's 48MHz. There's a PLL but I though F_CPU was always the result of clocks and dividers yielding the CPU clock.

Almost... but... here's what I've done, in time order

• Install Arduino 1.6 replacing older 1.06
• Install Teensyduino beta (latest)
• Install latest Visual Micro
• Run Arduino 1.6. Teensy 3.x and Teensy LC are in the tools list. Built and ran blinky for the LC.
• Run AS 6.2.  The VM toolbar has Teensy 1.0 but no boards.
  No other Teensy choices. Arduino/AVR boards are there.

The instruction, earlier in this thread confuses me:
Quote:

Does the highlighted part, above, mean choose Arduino 1.6 from the VM toolbar where I do find Teensy 1.0, Arduino 1.0+ and 1.05+ but no Arduino 1.6?

Or is all this assuming I'm using VS 2013-Community and not AS 6.2?
Run VS 2013 community and I get the same VM menu choices as listed above.

I appreciate you patience with me.

thanks. I used the msi installer rather than the zip simply because I didn't know the zip should have been used.

So now... using VS 2013 and VM I tried a hello world build for Teens 3.1 then Teensy LC. Both fail, for different reasons:

Compiling 'Teensy_helloWorld' for 'Teensy LC'
Build folder: file:///C:/Users/steve/AppData/Local/V.Micro/Arduino/Builds/Teensy_helloWorld/te
ensyLC
Summary: Header=1 Prototypes=3 Imports=0
Additional Defines:
Architecture Tools: c:\arduino/
Sketchbook: file:///C:/Users/steve/Documents/Arduino
Core Include Paths
Include Path 'c:\arduino\hardware\teensy\avr\cores\teensy3'
"c:\arduino/hardware/tools/arm/bin/arm-none-eabi-g++" -c {build.flags.optimize} -g -Wall -ffunction-sections -fdata-sections -MMD -nostdlib -fno-exceptions -felide-constructors -std=gnu++0x -fno-rtti -mthumb -mcpu=cortex-m0plus -D__MKL26Z64__ -DTEENSYDUINO=121 -DARDUINO=160 -DF_CPU={build.fcpu} -DARDUINO_ARCH_AVR -D{build.usbtype} -DLAYOUT_{build.keylayout} -I"c:\arduino\hardware\teensy\avr\cores\teensy3" "C:\Users\steve\AppData\Local\V.Micro\Arduino\Builds\Teensy_helloWorld\teensyLC\
Teensy_helloWorld.cpp" -o "C:\Users\steve\AppData\Local\V.Micro\Arduino\Builds\Teensy_helloWorld\teensyLC\
Teensy_helloWorld.cpp.o"

Error compiling



and for Teensy 3.1 something is wrong with the properties
Build folder: file:///C:/Users/steve/AppData/Local/V.Micro/Arduino/Builds/Teensy_helloWorld/te
ensy31
Summary: Header=1 Prototypes=3 Imports=0
Additional Defines:
Architecture Tools: c:\arduino/
Sketchbook: file:///C:/Users/steve/Documents/Arduino
Core Include Paths
Include Path 'c:\arduino\hardware\teensy\avr\cores\teensy3'
"c:\arduino/hardware/tools/arm/bin/arm-none-eabi-g++" -c -Os -g -Wall -ffunction-sections -fdata-sections -MMD -nostdlib -fno-exceptions -felide-constructors -std=gnu++0x -fno-rtti -mthumb -mcpu=cortex-m4 -D__MK20DX256__ -DTEENSYDUINO=121 -DARDUINO=160 -DF_CPU={build.fcpu} -DARDUINO_ARCH_AVR -D{build.usbtype} -DLAYOUT_{build.keylayout} -I"c:\arduino\hardware\teensy\avr\cores\teensy3" "C:\Users\steve\AppData\Local\V.Micro\Arduino\Builds\Teensy_helloWorld\teensy31\
Teensy_helloWorld.cpp" -o "C:\Users\steve\AppData\Local\V.Micro\Arduino\Builds\Teensy_helloWorld\teensy31\
Teensy_helloWorld.cpp.o"
:macro names must be identifiers
:ISO C99 requires whitespace after the macro name [enabled by default]
:token "{" is not valid in preprocessor expressions

Can you first try with the project properties so that you replicate the testing here

F_CPU=48000000;USB_SERIAL_HID;LAYOUT_US_ENGLISH

Thanks

Well Paul at pjrc does say it is beta

I just installed the latest version, my teensy was from last week.

In the latest version paul has added {build.flags.optimize}. You can see that in platform.txt

In the boards.txt he has added "build.flags.optimize=-Os" for all boards apart from Teensy LC which has the setting per speed 24/48

You can simply add the following to boards.txt

Code:

teensyLC.build.flags.optimize=-Os 

Not your decision, but compiler optimization choice should be a project property, NOT a board property.

Quote:


Agreed, in Visual Micro it will be project or configuration, in the same way that defines are at the moment.

When using a "debug" configuration you might want a different optimization level.