Closed cdeerinck closed 3 years ago
I was playing around with trying to isolate the problem. It appears as though the problem is when anything tries to print more than 64 bytes in a single print statement.
void setup() {
pinMode(LEDR, OUTPUT);
pinMode(LEDG, OUTPUT);
pinMode(LEDB, OUTPUT);
digitalWrite(LEDR, HIGH); digitalWrite(LEDG, HIGH); digitalWrite(LEDB, HIGH); // turn the LED black
Serial.begin(115200);
digitalWrite(LEDR, LOW); digitalWrite(LEDG, HIGH); digitalWrite(LEDB, HIGH); // turn the LED red
delay(1000);
while (!Serial);
Serial.println("Serial opened");
digitalWrite(LEDR, LOW); digitalWrite(LEDG, LOW); digitalWrite(LEDB, HIGH); // turn the LED yellow
delay(1000);
Serial.println(" 1 2 3 4 5 6");
Serial.println("1234567890123456789012345678901234567890123456789012345678901234");
Serial.println(".........this works fine........................................");
digitalWrite(LEDR, HIGH); digitalWrite(LEDG, HIGH); digitalWrite(LEDB, LOW); // turn the LED blue
delay(1000);
Serial.println(".........this causes a crash.....................................");
digitalWrite(LEDR, HIGH); digitalWrite(LEDG, LOW); digitalWrite(LEDB, HIGH); // turn the LED green
}
Produces this output, and then the crash occurs. The LED light sequence should be black/red/yellow/blue/green, but what occurs is black/red/yellow/blue and then the crash of 3X long, 3X short blink pattern.
10:58:37.047 -> Serial opened
10:58:38.066 -> 1 2 3 4 5 6
10:58:38.066 -> 1234567890123456789012345678901234567890123456789012345678901234
10:58:38.066 -> .........this works fine........................................
I tried another Arduino to see if the problem is with the unit, and it happens on the second one as well. Both of them are Arduino Nano 33 BLE. My next step will be to break your longer displays into shorter lines, just so I can get the IMU calibrated.
Any insight as to why that crash is occurring would be appreciated.
I captured this one time (MBed OS crash info). Not sure exactly what sequence allowed me to capture it:
10:11:51.879 -> Serial opened
10:11:51.879 -> 1 2 3 4 5 6
10:11:51.879 -> 1234567890123456789012345678901234567890123456789012345678901234
10:11:51.879 -> .........this works fine........................................
10:13:09.420 -> <.<..=console>tty?nullle@zeroleAklogleBoslogeCoslog_streamDfdoE
10:13:09.420 -> stdinstF
10:13:09.420 -> stdouttG
10:13:09.420 -> stderrtSerial opened
I also ran the code on a PC (all previous activity was on a Mac) and got the same results.
Recognizing that your Github is not the Arduino forum, I opened a post there at: https://forum.arduino.cc/index.php?topic=713904.new and will close this. But I thought it might be helpful to others that run into the same problem. FYI, I have fixed and run the Gyro and Acc calibration programs, with lines like this, until I can get to the root of the problem.
Serial.print(F(" Before calibrating choose the Full Scale (FS) setting and ")); Serial.println(F("Output Data Rate (ODR). The accelerometer and the"));
Thank you very much for the hard work you put into writings this. My Gyro is now usable!
Hi Chuck, Its always nice to know that people are using my code. Yes, the forum is the best place to get help. I'm not always available reading here. I found a new job in the midst of corona, but it takes an awful lot of time off :) . Good to know that the problem is not in the library and I've never heard of it. I hope you solve it.
Femme.
I can get the three "Simple" examples to run fine, but when I try to run any of the three calibration examples, they print the first line to the Serial Monitor, and then they freeze. If I try to rerun the program a second time, the entire Arduino IDE freezes up.
When they freeze, I get the 3X long, 3X short blink pattern indicating that the Mbed OS has crashed. If I power the Arduino down, and replug it in, it does the same thing.
when I run the Register Test, I get the following:
I'm pretty sure it is something wrong with my setup, and not your code, but I can't seem to figure out what. Any ideas?
Also, when compiling, I get the following warnings: