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.