Modify examples to facilitate I2C bus testing

Author: nseidle

Firmware/Test Sketches/GNSS_GetPosition/GNSS_GetPosition.ino

@@ -21,17 +21,22 @@ long lastTime = 0; //Simple local timer. Limits amount of I2C traffic to u-blox
 void setup()
 {
   Serial.begin(115200);
-  delay(500);
+  delay(1000);
   Serial.println("u-blox high precision example");
 
   Wire.begin();
+  //Wire.setClock(400000);
 
   //i2cGNSS.enableDebugging(Serial); // Uncomment this line to enable debug messages
 
   if (i2cGNSS.begin() == false) //Connect to the u-blox module using Wire port
   {
     Serial.println(F("u-blox GNSS not detected at default I2C address. Please check wiring. Freezing."));
-    while (1) ;
+    while (1)
+    {
+      if(Serial.available()) ESP.restart();
+      delay(10);
+    }
   }
 
   i2cGNSS.setI2COutput(COM_TYPE_UBX); //Set the I2C port to output UBX only (turn off NMEA noise)
@@ -92,4 +97,6 @@ void loop()
 
     Serial.println();
   }
+
+  if(Serial.available()) ESP.restart();
 }

Firmware/Test Sketches/GNSS_Serial_Test/GNSS_Serial_Test.ino

@@ -26,12 +26,13 @@ void setup()
   Serial.println("GNSS UART2 Connection Test");
 
   Wire.begin();
+  //Wire.setClock(400000);
 
   if (i2cGNSS.begin() == false) //Connect to the u-blox module using Wire port
   {
     Serial.println(F("u-blox GNSS not detected at default I2C address. Trying again"));
 
-    //The ESP32 controls the power to the ZED. During power cycles, the ZED can take up to ~1000ms to respond to I2C pings.
+    //On the RTK Facet the ESP32 controls the power to the ZED. During power cycles, the ZED can take up to ~1000ms to respond to I2C pings.
     //delay(400); //Bad
     delay(500); //Good - may be a combination of startup delay of 200ms