Yes it should work. Embrio writes Arduino programs then uses the command line for the Arduino to compile and upload them.

There's a text file that tells Embrio about the different boards and how to call them, C:\Users\<UserName>\AppData\Roaming\Embrio\pininfo.txt. Before you get started, download this version to that location: http://embrio.io/uploads/pininfo.txt

Then open the file and make a new Info entry. The only tricky part might be the value for Tag. I think the best way to figure out what that value needs to be is compile and upload something to the Teensy through the Arduino IDE with verbose mode on and see what it uses.

If you get it working, could you please paste the Info entry here for reference for others?

I'll check it out. It shouldn't be a problem but might require some fiddling.

There's a installed version of pininfo.txt in c:/Program Files/Embrio. On startup, if its Version Number (the first tag in the file) is greater than the one in C:\Users\<UserName>\AppData\Roaming\Embrio it makes a backup of the local one and copies the installed one. Could the one in your local path be older than the installed one?

Anyway I added a workaround in the last version which might be easier to use. In View -> Options, check "Upload to last board set in Arduino IDE" . Then upload to the board in the Arduino IDE, close the IDE so its settings are saved, then upload via Embrio. It should work, Embrio will compile then tell Arduino to upload using its last settings.

Let me know if that works. I haven't used those 2 boards, but this workaround should work for anything you can upload to via Arduino.

Are you saying that the pininfo.txt file in the installed directory is being copied into the local directory, even if the version numbers match? If so your pin info should be copied as a backup in the local folder with the current date. Is that happening? It's working as expected for me but I could have missed something.

Eventually I'll make it so you can edit this stuff in the software or something so we don't have to manually edit the text file.

Everything works great so far since the last update 1.2.8.. I can now finally simulate the DUE using the Embrio environment. The only thing I was wondering, is how to utilize the Analog Output DAC0 and DAC0. Are we just supposed to use Custom node? The options for Analog Outputs are only for the Pulse width modulating type.

Thanks
Greg

That's something I haven't learned about yet. For now use a custom Arduino node, it shouldn't be too hard to make but if you run into trouble let me know. If you make one, please consider posting it to the library so others can use it.

I haven't tested a Teensy myself yet. I thought I bought one but can't seem to find it... I'll keep looking.

You should be fine using the "Upload to last board set in Arduino IDE" check box in the options form after you successfully upload via the Arduino IDE. I'll need to add an entry to pininfo.txt for it to show up as a selection in Embrio. I'll try to do that soon.

I tried this just now, and it doesn't quite work. I successfully created a Teensy entry in pininfo.txt, using tag teensy:avr:teensy31.

When attempting to connect (and, I assume, upload the connection program) I get the error

invalid conversion from 'byte*' {aka unsigned char*} to 'char*' [-fpermissive]
initializing argument 1 of size_t usb_serial_class::readBytes(char*, size_t) [-fpermissive]

For anyone else who wants to follow in my footsteps, I used the following section for my pininfo.txt, which is the furthest I got:

<Info>
<BoardName>Teensy 3.1</BoardName>
<Tag>teensy:avr:teensy31</Tag>
<DigitalPins>
<Pin>
<Name>D0</Name>
<Code>0</Code>
</Pin>
<Pin>
<Name>D1</Name>
<Code>1</Code>
</Pin>
<Pin>
<Name>D2</Name>
<Code>2</Code>
</Pin>
<Pin>
<Name>D3</Name>
<Code>3</Code>
</Pin>
<Pin>
<Name>D4</Name>
<Code>4</Code>
</Pin>
<Pin>
<Name>D5</Name>
<Code>5</Code>
</Pin>
<Pin>
<Name>D6</Name>
<Code>6</Code>
</Pin>
<Pin>
<Name>D7</Name>
<Code>7</Code>
</Pin>
<Pin>
<Name>D8</Name>
<Code>8</Code>
</Pin>
<Pin>
<Name>D9</Name>
<Code>9</Code>
</Pin>
<Pin>
<Name>D10</Name>
<Code>10</Code>
</Pin>
<Pin>
<Name>D11</Name>
<Code>11</Code>
</Pin>
<Pin>
<Name>D12</Name>
<Code>12</Code>
</Pin>
<Pin>
<Name>D13</Name>
<Code>13</Code>
</Pin>
</DigitalPins>
<AnalogInputPins>
<Pin>
<Name>A0</Name>
<Code>0</Code>
</Pin>
<Pin>
<Name>A1</Name>
<Code>1</Code>
</Pin>
<Pin>
<Name>A2</Name>
<Code>2</Code>
</Pin>
<Pin>
<Name>A3</Name>
<Code>3</Code>
</Pin>
<Pin>
<Name>A4</Name>
<Code>4</Code>
</Pin>
<Pin>
<Name>A5</Name>
<Code>5</Code>
</Pin>
</AnalogInputPins>
<PWMOutputPins>
<Pin>
<Name>D3</Name>
<Code>3</Code>
</Pin>
<Pin>
<Name>D4</Name>
<Code>4</Code>
</Pin>
<Pin>
<Name>D5</Name>
<Code>5</Code>
</Pin>
<Pin>
<Name>D6</Name>
<Code>6</Code>
</Pin>
<Pin>
<Name>D9</Name>
<Code>9</Code>
</Pin>
<Pin>
<Name>D10</Name>
<Code>10</Code>
</Pin>
</PWMOutputPins>
</Info>

The downloading of Teensy does work, but using connection to simulate the program will not. This is the one of the errors that transpires when trying to compile the application from ArduinoCompile program created by Embrio:

Arduino: 1.6.5 (Windows 8.1), TD: 1.24, Board: "Teensy++ 2.0, Serial, 16 MHz, US English"

C:\Program Files (x86)\Arduino/hardware/tools/avrteensy/bin/avr-g++ -c -Os -g -Wall -ffunction-sections -fdata-sections -MMD -fno-exceptions -felide-constructors -std=c++0x -mmcu=at90usb1286 -DTEENSYDUINO=124 -DARDUINO=10605 -DF_CPU=16000000L -DARDUINO_ARCH_AVR -DUSB_SERIAL -DLAYOUT_US_ENGLISH -IC:\Program Files (x86)\Arduino\hardware\teensy\avr\cores\teensy C:\Users\Greg\AppData\Local\Temp\build2018557039945896630.tmp\ArduinoCompile.cpp -o C:\Users\Greg\AppData\Local\Temp\build2018557039945896630.tmp\ArduinoCompile.cpp.o

ArduinoCompile.ino: In function 'float ReadFloat()':
ArduinoCompile.ino:18:28: error: invalid conversion from 'byte* {aka unsigned char*}' to 'char*' [-fpermissive]
In file included from C:\Program Files (x86)\Arduino\hardware\teensy\avr\cores\teensy/usb_api.h:2:0,
from C:\Program Files (x86)\Arduino\hardware\teensy\avr\cores\teensy/WProgram.h:22,
from C:\Program Files (x86)\Arduino\hardware\teensy\avr\cores\teensy/Arduino.h:1,
from ArduinoCompile.ino:1:
C:\Program Files (x86)\Arduino\hardware\teensy\avr\cores\teensy/../usb_serial/usb_api.h:37:9: error: initializing argument 1 of 'size_t usb_serial_class::readBytes(char*, size_t)' [-fpermissive]
size_t readBytes(char *buffer, size_t length);
^
ArduinoCompile.ino:19:21: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
ArduinoCompile.ino: In function 'long int ReadLong()':
ArduinoCompile.ino:25:28: error: invalid conversion from 'byte* {aka unsigned char*}' to 'char*' [-fpermissive]
In file included from C:\Program Files (x86)\Arduino\hardware\teensy\avr\cores\teensy/usb_api.h:2:0,
from C:\Program Files (x86)\Arduino\hardware\teensy\avr\cores\teensy/WProgram.h:22,
from C:\Program Files (x86)\Arduino\hardware\teensy\avr\cores\teensy/Arduino.h:1,
from ArduinoCompile.ino:1:
C:\Program Files (x86)\Arduino\hardware\teensy\avr\cores\teensy/../usb_serial/usb_api.h:37:9: error: initializing argument 1 of 'size_t usb_serial_class::readBytes(char*, size_t)' [-fpermissive]
size_t readBytes(char *buffer, size_t length);
^
ArduinoCompile.ino:26:20: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
ArduinoCompile.ino: In function 'boolean StartRead()':
ArduinoCompile.ino:79:20: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
ArduinoCompile.ino: In function 'void HandleSerial()':
ArduinoCompile.ino:116:26: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
invalid conversion from 'byte* {aka unsigned char*}' to 'char*' [-fpermissive]

Great. Paul from Teensy might be able to help, he seems super engaged and helpful.