I'm kinda at the end of my rope here with this project. I think the onboard arduino died

I have a sketch that was executing just fine and now it's not.

Code:

void setup() {
  Serial.begin(9600);

  while (!Serial) { // needed to keep leonardo/micro from starting too fast!
    delay(10);
  }
 
  Serial.println("Adafruit MPR121 Capacitive Touch sensor test");
 
  // Default address is 0x5A, if tied to 3.3V its 0x5B
  // If tied to SDA its 0x5C and if SCL then 0x5D
  if (!cap.begin(0x5A)) {
    Serial.println("MPR121 not found, check wiring?");
    while (1);
  }
  Serial.println("MPR121 found!");
}

This is the test code for the Adafruit mpr121. It will print the first line

"Adafruit MPR121 Capacitive Touch sensor test"

And then not do anything. I thought it was my shield, it is not because I bought another one. If the shield is removed, it does not fire an error message. I think the on board arduino has broken (I have tried the master reset). Does anyone know of some sort of diagnostic test suite I can run on this? My fun weekend project is turning into a real nightmare and money sink.

 

So I tried a simple sketch. To light an LED and it worked. I luckily had an arduino uno laying around, tried the shields on it, they work. So whatever these offsets are:
// Default address is 0x5A, if tied to 3.3V its 0x5B
// If tied to SDA its 0x5C and if SCL then 0x5D
Are fried.

 

You have to check if the cap library you are using is Arduino 101 compatible. There are some I2C issues with the Arduino 101. Please also check the Arduino 101 forum on www.arduino.cc

 

I've managed to fry a Arduino Nano only by making a wrong wiring from 5v to non-5v. There was smoke and smell to tell me I destroyed the Arduino.

The Arduino 101 (and thus Udoo X86) should be 5v tolerant, so I would assume that this would not be so easily possible.

 

It should work with Arduino 101 as this guy got it working: https://create.arduino.cc/projecthub/doncoleman/arduino-101-bluetooth-midi-544b21

@Maurice : Arduino 101 I2C issues see https://github.com/01org/corelibs-arduino101/issues/238

 

It was working. It just stopped. Some sort of bus or offset has died. I had been using it and it was solid. Works on an external board.

 

Did you change anything before it stopped working? For example firmware 103 update? Added extra devices?

To see if there is communication signals you could use an USB logic analyzer. You can buy them cheap.
http://m.ebay.com/itm/USB-Logic-Ana...MHz-8CH-24MHz-for-ARM-FPGA-M434-/401349992819

 

Nope. I know that's the story told around the world. Light on the MPR121 went red as it does from time to time. Idk why it does that. Maybe because this 101 doesn't properly support 5v. But then I guess I'd have to figure out how to wire a shield to use the 3.3. Usually I pull the shield and put it back on and it's fine. I reupload the sketch, it flashes just fine and then hangs at any logic interaction on any of those offsets. So this:

if (!cap.begin(0x5A)) {

At any address. Will hang. It's just weird. It's just a hang. No response, no nothing. It won't pass a logic interaction with those offsets now.

I did however even try an update after the fact. No change. I can print stuff, this works: https://www.udoo.org/tutorial/getting-started-with-arduino-ide-on-udoo/

The shields work on my uno. It just started hanging. It hangs with nothing attached. I can pick up that thing from ebay, but then it's another x amount of days before I get it, and just more money. It's all just time and money adding up.

 

It hangs at the moment the I2C is addressed.
We cannot see what is in the rest of your sketch (and don't need to). Perhaps there is an hidden type error. If you just try the example sketch:
https://github.com/adafruit/Adafruit_MPR121/blob/master/examples/MPR121test/MPR121test.ino

Same issue?

 

You could also run the I2C scanner that is not using special other libraries other than the Wire.h:
https://github.com/PaulStoffregen/Wire/blob/master/examples/Scanner/Scanner.ino

Your sensor device should pop up as MPR121 (if address is 0x5A)

 

Yep. Example sketch is the same problem. It had been working.

Output from the uno:

Scanning...
Device found at address 0x5A (MPR121)
done


Output From the 101:

I2C Scanner
Scanning...
No I2C devices found


This one doesn't hang, but it doesn't detect the board. I'm sure we're in the realm of highly unlikely that a bus goes bad, but I think that's where I'm at (story of my life )

 

You could open a customer care support ticket to see what they can do. Perhaps they can repair it (under guarantee).

 

Thanks @waltervl I did do that. Also too, thanks for being such an active member of the forum. People like you make the world go round!