Hi everybody. I've been developing for the Arduino Mega for about a year, and now I need to run some code on the Arduino 101. I needed a board that had the same footprint as an Uno, but with more memory.

So I got into the Visual Micro board manager and installed V 1.0.7 of the Intel Curie board. I was not able to do this in the native Arduino IDE though, since my company's internet settings seem to result in the error message "Error downloading http://downloads.arduino.cc/packages/package_index.json" I don't know if this matters, or if I even need to do this in the Arduino IDE, but so far I haven't found a way. 

Anyway, the board seemed to install just fine in Visual Micro, and I was able to select Arduino 101 from the drop down. My 101 shows up in the port selection drop down as "COM9 - Arduino 101 serial monitor". 

I had to modify some of my code once I did this, since one of my libraries (TFTv2.h) did not have definitions for the 101, and also since I was using memset(), which apparently is too close to the hardware level to be compatible with the 101.

So I got rid of those errors, but I was still not able to compile. I'll post the whole micro build output in a text attachment to this post. It contains a lot of warnings that I never saw during my development with the Mega. I don't know if they matter or not, or what's causing the "Error compiling libraries" at the end. 

One more thing- when I plug the 101 board into the PC, it shows up under "Other Devices" as "Arduino 101", but only for like 8 seconds before the device manager refreshes and it then appears under "Ports (COM & LTP)" as "Arduino 101 Serial Monitor"

Guys, thanks for taking the time to read this and thanks for any advice you might be able to lend. 

Output is attached at .txt file

Thanks, Tim.

   I did that, and the output looked the same. Lots of warnings  I think it has something to do with my library for my touch screen. I got the latest version of that library from github that's supposed to work with the 101, but TFTv2.h shows several errors in it. I think that the library had trouble with some of the 101-specific definitions included in the .h file, specifically these ones:

#elif defined(__arc__) /* Arduino101/Genuino101 specifics */

#define TFT_DC_LOW      digitalWrite(6, LOW)
#define TFT_DC_HIGH     digitalWrite(6, HIGH)
#define TFT_CS_LOW      digitalWrite(5, LOW)
#define TFT_CS_HIGH     digitalWrite(5, HIGH)
#define TFT_BL_OFF      digitalWrite(7, LOW)
#define TFT_BL_ON       digitalWrite(7, HIGH)
 

So that wherever those parts were called out in the class part of the file, they were in error. So I tried taking those definitions and replacing them wherever they occurred, like this:

class TFT
{

public:

    inline void sendCMD(INT8U index)
    {
		digitalWrite(6, LOW); //TFT_DC_LOW;        /////////////////////////////////////////////////////////////////////
		digitalWrite(5, LOW);  ////////
        SPI.transfer(index);
		digitalWrite(5, HIGH);  //TFT_CS_HIGH;/////////////////////////////////////////////////////////////////
    }

 

...and so on.

But I'm still getting what appears to be the same kind of compiling errors that I was getting before.

And further, now that I'm opening up some of my other .h files that appear in my solution, I'm seeing some more errors show up. Specifically, SPI.h is showing errors under the "beginTransaction" function, and Xbee.h is showing an error where it includes #include <inttypes.h>. 

Am I totally missing some critical information on the compatibility of different libraries and the 101? Because it doesn't seem like anything works on this board.

I'm attaching the latest output in a .txt file.

Hi again, I was finally able to upload a simple program to the 101. I tried installing different versions of the Arduino IDE, and it was finally version 1.6.11 that successfully installed the curie board drivers. I didn't have to use the board manager in Visual Micro at all.

But I still seem to be having a problem compiling with some of my libraries. I've attached the latest verbose output in .txt format. 

The libraries that are throwing errors don't have any red in them with the 101 board selected. I don't see any problems with them when I open them up. 

On the contrary, it's still SPI.h that has a couple errors in it when the 101 board is selected.

The libraries I'm calling out in my sketch are:

#include <stdint.h>//For Seedstudio Touch
#include <TFTv2.h>//For Seedstudio Touch
#include <SPI.h>
#include <SeeedTouchScreen.h>   //Seedstudio LCD touch screen Library File
#include <SD.h>//For Seedstudio Touch
#include <XBee.h>   //Zigbee Wireless transciever Library File
#include <Printers.h>   //Zigbee Wireless transciever Library File
 

But according to the verbose output, other (standard) libraries are implicated in the issue. Should I somehow be calling out a whole different set of standard libraries for the 101?

as far as the libraries I'm using, here's a list:

https://github.com/Seeed-Studio/Touch_Screen_Driver

https://github.com/Seeed-Studio/TFT_Touch_Shield_V2 (This one I've Frankensteined together with someone's code for text direction for my touchscreen.)

https://github.com/andrewrapp/xbee-arduino

And all the other ones are standard libraries that I didn't have to add myself. They just came with Visual Micro.

Thanks for your advice!

No, it doesn't. It compiles and loads just fine for the Mega 2560 using either IDE, but if I plug in and select the 101, it looks like I get the same result.

sorry I was't clear. here is a better question...

do you know for sure the libraries are compatible with the 101?

The libs look okay for the 101 except the touchscreen

Switch on "vmicro>compiler>verbose" then build that should show more clearly the error source

Sorry, to be honest I really only get time to support the plugin, not specific code or libraries. Each library usually has a git issues/questions area but I think seedstudio also have a forum.

The #include "avr\ can often signify atmel avr processors (such as atmega and uno) not other hardware such as intel